search

cagnulein / qdomyos-zwift

Zwift bridge for smart treadmills and bike/cyclette
https://www.qzfitness.com/
GNU General Public License v3.0
426 stars 116 forks source link

Toorx TR with bt key TRX App Gate USB #32

Closed cagnulein closed 3 years ago

cagnulein commented 4 years ago

I found also iConnect+ app that works with Toorx TR for free... I'll update the logs soon

Originally posted by @drainuzzo in https://github.com/cagnulein/qdomyos-zwift/issues/15#issuecomment-715232849

cagnulein commented 4 years ago

@drainuzzo post here the new log when you will be ready in order to keep clean the issue (i would like to keep an issue for every device)

drainuzzo commented 4 years ago

I found also iConnect+ app that works with Toorx TR for free... I'll update the logs soon

Originally posted by @drainuzzo in #15 (comment)

It is iConsole+ app

drainuzzo commented 4 years ago

Here the logs you can check it with Wireshark

hci_snoop_2020_10_23_13_11_34.zip

cagnulein commented 4 years ago

@drainuzzo great! I will check it this weekend. Could you breafly describe me what you did in this session with the app? Speed, inclination, elapsed time...

Thanks

cagnulein commented 4 years ago

ok here i will summarize the info extracted from the logs

16bit UUID service ff f0

16bit UUID characteristic notification ff f1

16bit UUID characteristic write ff f2

init sequence f0 a0 01 01 92 f0 a0 01 d3 64 f0 a1 01 d3 65

polling command every 500ms f0 a2 01 d3 66

sample response N.B. every values start from 1 not from 0 f0 b2 01 d3 01 01 01 01 01 01 01 01 01 0b 01 03 04 03 95 byte3-byte4 = elapsed byte6-byte7 = distance byte8-byte9 = kcal byte13 = inclination? byte15-byte16 = speed?

drainuzzo commented 4 years ago

I am not sure because I had to make different tries before the logs were written in my device..

Checking at the date mybe the activity attached

Btw I changed inclination, speed and had the cardio from the TR

Screenshot_20201023-142840.jpg

cagnulein commented 4 years ago

I am not sure because I had to make different tries before the logs were written in my device..

Checking at the date mybe the activity attached

Btw I changed inclination, speed and had the cardio from the TR

i don't think it was this session because on the log you sent me the session has a duration of 57 seconds

cagnulein commented 4 years ago

@drainuzzo could you try to compile the https://github.com/cagnulein/qdomyos-zwift/commit/6d88cef84cf9da51dddce202cdd95d62d8e7c25f and try? If so, send me the logs that the qdomyos-zwift will generate.

It's just to see if the connection works and if some parameters will be read. Thanks

drainuzzo commented 4 years ago

Then should be this session attached []()Screenshot_20201023-154930.jpg

drainuzzo commented 4 years ago

@drainuzzo could you try to compile the 6d88cef and try? If so, send me the logs that the qdomyos-zwift will generate.

It's just to see if the connection works and if some parameters will be read. Thanks

Ok but next days..

Thank you

drainuzzo commented 4 years ago

Hello these the logs after code compiling:

sudo ./qdomyos-zwift

libEGL warning: DRI2: failed to authenticate
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
qt.bluetooth.bluez: Bluez 5 detected.
qt.bluetooth.bluez: Creating QtBluezDiscoveryManager
qt.bluetooth.bluez: Discovered:  "A4:C1:38:CE:A4:28" "LYWSD03MMC" Num UUIDs 0 total device 0 cached RSSI 0 Class 0
"Tue Oct 27 16:22:11 2020Found new device: LYWSD03MMC (A4:C1:38:CE:A4:28)\n"
qt.bluetooth.bluez: Discovered:  "A4:C1:38:D9:02:06" "LYWSD03MMC" Num UUIDs 0 total device 1 cached RSSI 0 Class 0
"Tue Oct 27 16:22:11 2020Found new device: LYWSD03MMC (A4:C1:38:D9:02:06)\n"
qt.bluetooth.bluez: Discovered:  "C4:FC:E8:A6:95:04" "RunScribe-06FE" Num UUIDs 4 total device 2 cached RSSI 0 Class 0
"Tue Oct 27 16:22:11 2020Found new device: RunScribe-06FE (C4:FC:E8:A6:95:04)\n"
qt.bluetooth.bluez: Discovered:  "FD:61:AE:2F:59:79" "RunScribe-C670" Num UUIDs 4 total device 3 cached RSSI 0 Class 0
"Tue Oct 27 16:22:11 2020Found new device: RunScribe-C670 (FD:61:AE:2F:59:79)\n"
qt.bluetooth.bluez: Discovered:  "FF:90:CE:BE:F5:FC" "TOORX0083" Num UUIDs 1 total device 4 cached RSSI 0 Class 0
"Tue Oct 27 16:22:11 2020Found new device: TOORX0083 (FF:90:CE:BE:F5:FC)\n"
qt.bluetooth.bluez: void QBluetoothDeviceDiscoveryAgentPrivate::stop()
QObject::connect: Cannot connect (null)::disconnected() to bluetooth::restart()
QObject::connect: Cannot connect (null)::debug(QString) to bluetooth::debug(QString)
Segmentation fault
cagnulein commented 4 years ago

@drainuzzo i've just push the fix ( https://github.com/cagnulein/qdomyos-zwift/commit/a162e0dcfb753ad910b043fe6e93dbf43774565c ) could you please retry pulling the changes? thanks

drainuzzo commented 4 years ago

sudo ./qdomyos-zwift

libEGL warning: DRI2: failed to authenticate
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
qt.bluetooth.bluez: Bluez 5 detected.
qt.bluetooth.bluez: Creating QtBluezDiscoveryManager
qt.bluetooth.bluez: Discovered:  "C4:FC:E8:A6:95:04" "RunScribe-06FE" Num UUIDs 4 total device 0 cached RSSI 0 Class 0
"Tue Oct 27 17:51:34 2020Found new device: RunScribe-06FE (C4:FC:E8:A6:95:04)\n"
qt.bluetooth.bluez: Discovered:  "FD:61:AE:2F:59:79" "RunScribe-C670" Num UUIDs 4 total device 1 cached RSSI 0 Class 0
"Tue Oct 27 17:51:34 2020Found new device: RunScribe-C670 (FD:61:AE:2F:59:79)\n"
qt.bluetooth.bluez: Discovered:  "FF:90:CE:BE:F5:FC" "TOORX0083" Num UUIDs 5 total device 2 cached RSSI 0 Class 0
"Tue Oct 27 17:51:34 2020Found new device: TOORX0083 (FF:90:CE:BE:F5:FC)\n"
qt.bluetooth.bluez: void QBluetoothDeviceDiscoveryAgentPrivate::stop()
"Tue Oct 27 17:51:34 2020Found new device: TOORX0083 (FF:90:CE:BE:F5:FC)\n"
qt.bluetooth.bluez: Detecting bluetoothd version
qt.bluetooth.bluez: Using /proc/<pid>/exe
qt.bluetooth.bluez: Detected bluetoothd version 5.50
qt.bluetooth.bluez: Bluetoothd: "5.50"
qt.bluetooth: Using BlueZ LE DBus API
qt.bluetooth.bluez: QLowEnergyControllerPrivateBluezDBus::connectToDevice()
"Tue Oct 27 17:51:34 2020Controller connected. Search services...\n"
"Tue Oct 27 17:51:34 2020serviceDiscovered {00001801-0000-1000-8000-00805f9b34fb}\n"
"Tue Oct 27 17:51:34 2020serviceDiscovered {0000fe59-0000-1000-8000-00805f9b34fb}\n"
"Tue Oct 27 17:51:34 2020serviceDiscovered {0000fff0-0000-1000-8000-00805f9b34fb}\n"
"Tue Oct 27 17:51:34 2020serviceDiscovered {0000180a-0000-1000-8000-00805f9b34fb}\n"
"Tue Oct 27 17:51:34 2020serviceScanDone\n"
QObject::connect: Cannot connect (null)::stateChanged(QLowEnergyService::ServiceState) to trxappgateusbtreadmill::stateChanged(QLowEnergyService::ServiceState)
Segmentation fault
cagnulein commented 4 years ago

sudo ./qdomyos-zwift

libEGL warning: DRI2: failed to authenticate
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
qt.bluetooth.bluez: Bluez 5 detected.
qt.bluetooth.bluez: Creating QtBluezDiscoveryManager
qt.bluetooth.bluez: Discovered:  "C4:FC:E8:A6:95:04" "RunScribe-06FE" Num UUIDs 4 total device 0 cached RSSI 0 Class 0
"Tue Oct 27 17:51:34 2020Found new device: RunScribe-06FE (C4:FC:E8:A6:95:04)\n"
qt.bluetooth.bluez: Discovered:  "FD:61:AE:2F:59:79" "RunScribe-C670" Num UUIDs 4 total device 1 cached RSSI 0 Class 0
"Tue Oct 27 17:51:34 2020Found new device: RunScribe-C670 (FD:61:AE:2F:59:79)\n"
qt.bluetooth.bluez: Discovered:  "FF:90:CE:BE:F5:FC" "TOORX0083" Num UUIDs 5 total device 2 cached RSSI 0 Class 0
"Tue Oct 27 17:51:34 2020Found new device: TOORX0083 (FF:90:CE:BE:F5:FC)\n"
qt.bluetooth.bluez: void QBluetoothDeviceDiscoveryAgentPrivate::stop()
"Tue Oct 27 17:51:34 2020Found new device: TOORX0083 (FF:90:CE:BE:F5:FC)\n"
qt.bluetooth.bluez: Detecting bluetoothd version
qt.bluetooth.bluez: Using /proc/<pid>/exe
qt.bluetooth.bluez: Detected bluetoothd version 5.50
qt.bluetooth.bluez: Bluetoothd: "5.50"
qt.bluetooth: Using BlueZ LE DBus API
qt.bluetooth.bluez: QLowEnergyControllerPrivateBluezDBus::connectToDevice()
"Tue Oct 27 17:51:34 2020Controller connected. Search services...\n"
"Tue Oct 27 17:51:34 2020serviceDiscovered {00001801-0000-1000-8000-00805f9b34fb}\n"
"Tue Oct 27 17:51:34 2020serviceDiscovered {0000fe59-0000-1000-8000-00805f9b34fb}\n"
"Tue Oct 27 17:51:34 2020serviceDiscovered {0000fff0-0000-1000-8000-00805f9b34fb}\n"
"Tue Oct 27 17:51:34 2020serviceDiscovered {0000180a-0000-1000-8000-00805f9b34fb}\n"
"Tue Oct 27 17:51:34 2020serviceScanDone\n"
QObject::connect: Cannot connect (null)::stateChanged(QLowEnergyService::ServiceState) to trxappgateusbtreadmill::stateChanged(QLowEnergyService::ServiceState)
Segmentation fault

Ok understood, it's easy. I will fix it tonight Thanks

cagnulein commented 4 years ago

@drainuzzo ok fixed, try this https://github.com/cagnulein/qdomyos-zwift/commit/9cbd054ab43b4f43000bbfa335397529508fea88 It could be possible that we need another round to complete the gathering of the characteristics Thanks

drainuzzo commented 4 years ago

this time

libEGL warning: DRI2: failed to authenticate
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
qt.bluetooth.bluez: Bluez 5 detected.
qt.bluetooth.bluez: Creating QtBluezDiscoveryManager
qt.bluetooth.bluez: Discovered:  "FF:90:CE:BE:F5:FC" "TOORX0083" Num UUIDs 5 total device 0 cached RSSI 0 Class 0
"Wed Oct 28 11:05:59 2020Found new device: TOORX0083 (FF:90:CE:BE:F5:FC)\n"
qt.bluetooth.bluez: void QBluetoothDeviceDiscoveryAgentPrivate::stop()
"Wed Oct 28 11:05:59 2020Found new device: TOORX0083 (FF:90:CE:BE:F5:FC)\n"
qt.bluetooth.bluez: Detecting bluetoothd version
qt.bluetooth.bluez: Using /proc/<pid>/exe
qt.bluetooth.bluez: Detected bluetoothd version 5.50
qt.bluetooth.bluez: Bluetoothd: "5.50"
qt.bluetooth: Using BlueZ LE DBus API
qt.bluetooth.bluez: QLowEnergyControllerPrivateBluezDBus::connectToDevice()
QMetaObject::connectSlotsByName: No matching signal for on_Inclination_clicked()
qt.bluetooth.bluez: ###### "org.bluez.Device1" QMap(("Connected", QVariant(bool, true)))
qt.bluetooth.bluez: BluetoothManagement: Ignored event: 13
qt.bluetooth.bluez: BluetoothManagement: Ignored event: 13
qt.bluetooth.bluez: BluetoothManagement: Ignored event: b
qt.bluetooth.bluez: ###### "org.bluez.Device1" QMap(("ServicesResolved", QVariant(bool, true)))
"Wed Oct 28 11:06:01 2020Controller connected. Search services...\n"
"Wed Oct 28 11:06:01 2020serviceDiscovered {00001801-0000-1000-8000-00805f9b34fb}\n"
"Wed Oct 28 11:06:01 2020serviceDiscovered {0000fe59-0000-1000-8000-00805f9b34fb}\n"
"Wed Oct 28 11:06:01 2020serviceDiscovered {0000fff0-0000-1000-8000-00805f9b34fb}\n"
"Wed Oct 28 11:06:01 2020serviceDiscovered {0000180a-0000-1000-8000-00805f9b34fb}\n"
"Wed Oct 28 11:06:01 2020serviceScanDone\n"
"Wed Oct 28 11:06:01 2020BTLE stateChanged DiscoveringServices\n"
qt.bluetooth.bluez: Read Desc: "\x00\x00"
"Wed Oct 28 11:06:01 2020BTLE stateChanged ServiceDiscovered\n"
"Wed Oct 28 11:06:01 2020characteristic {0000fff2-0000-1000-8000-00805f9b34fb}\n"
"Wed Oct 28 11:06:01 2020characteristic {0000fff1-0000-1000-8000-00805f9b34fb}\n"
ASSERT: "gattWriteCharacteristic.isValid()" in file trxappgateusbtreadmill.cpp, line 259
Aborted
cagnulein commented 4 years ago

@drainuzzo ok now it should run flawless (i hope :D) https://github.com/cagnulein/qdomyos-zwift/commit/b71ca62110b7dab800754a4907d58151d491b2c4

drainuzzo commented 4 years ago 
libEGL warning: DRI2: failed to authenticate
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
qt.bluetooth.bluez: Bluez 5 detected.
qt.bluetooth.bluez: Creating QtBluezDiscoveryManager
qt.bluetooth.bluez: Discovered:  "A4:C1:38:D9:02:06" "LYWSD03MMC" Num UUIDs 0 total device 0 cached RSSI 0 Class 0
"Wed Oct 28 11:24:18 2020Found new device: LYWSD03MMC (A4:C1:38:D9:02:06)\n"
qt.bluetooth.bluez: Discovered:  "C4:FC:E8:A6:95:04" "RunScribe-06FE" Num UUIDs 4 total device 1 cached RSSI 0 Class 0
"Wed Oct 28 11:24:18 2020Found new device: RunScribe-06FE (C4:FC:E8:A6:95:04)\n"
qt.bluetooth.bluez: Discovered:  "FD:61:AE:2F:59:79" "RunScribe-C670" Num UUIDs 4 total device 2 cached RSSI 0 Class 0
"Wed Oct 28 11:24:18 2020Found new device: RunScribe-C670 (FD:61:AE:2F:59:79)\n"
qt.bluetooth.bluez: Discovered:  "FF:90:CE:BE:F5:FC" "TOORX0083" Num UUIDs 5 total device 3 cached RSSI 0 Class 0
"Wed Oct 28 11:24:18 2020Found new device: TOORX0083 (FF:90:CE:BE:F5:FC)\n"
qt.bluetooth.bluez: void QBluetoothDeviceDiscoveryAgentPrivate::stop()
"Wed Oct 28 11:24:18 2020Found new device: TOORX0083 (FF:90:CE:BE:F5:FC)\n"
qt.bluetooth.bluez: Detecting bluetoothd version
qt.bluetooth.bluez: Using /proc/<pid>/exe
qt.bluetooth.bluez: Detected bluetoothd version 5.50
qt.bluetooth.bluez: Bluetoothd: "5.50"
qt.bluetooth: Using BlueZ LE DBus API
qt.bluetooth.bluez: QLowEnergyControllerPrivateBluezDBus::connectToDevice()
QMetaObject::connectSlotsByName: No matching signal for on_Inclination_clicked()
qt.bluetooth.bluez: ###### "org.bluez.Device1" QMap(("RSSI", QVariant(short, -73)))
qt.bluetooth.bluez: ###### "org.bluez.Device1" QMap(("Connected", QVariant(bool, true)))
qt.bluetooth.bluez: BluetoothManagement: Ignored event: 13
qt.bluetooth.bluez: BluetoothManagement: found random device "73:11:44:0D:97:51"
qt.bluetooth.bluez: BluetoothManagement: found random device "FF:90:CE:BE:F5:FC"
qt.bluetooth.bluez: BluetoothManagement: Ignored event: 13
qt.bluetooth.bluez: BluetoothManagement: Ignored event: 13
qt.bluetooth.bluez: BluetoothManagement: found random device "FD:61:AE:2F:59:79"
qt.bluetooth.bluez: BluetoothManagement: Ignored event: b
qt.bluetooth.bluez: BluetoothManagement: found random device "73:11:44:0D:97:51"
qt.bluetooth.bluez: BluetoothManagement: found random device "C4:FC:E8:A6:95:04"
qt.bluetooth.bluez: ###### "org.bluez.Device1" QMap(("ServicesResolved", QVariant(bool, true)))
"Wed Oct 28 11:24:20 2020Controller connected. Search services...\n"
"Wed Oct 28 11:24:20 2020serviceDiscovered {00001801-0000-1000-8000-00805f9b34fb}\n"
"Wed Oct 28 11:24:20 2020serviceDiscovered {0000fe59-0000-1000-8000-00805f9b34fb}\n"
"Wed Oct 28 11:24:20 2020serviceDiscovered {0000fff0-0000-1000-8000-00805f9b34fb}\n"
"Wed Oct 28 11:24:20 2020serviceDiscovered {0000180a-0000-1000-8000-00805f9b34fb}\n"
"Wed Oct 28 11:24:20 2020serviceScanDone\n"
"Wed Oct 28 11:24:20 2020BTLE stateChanged DiscoveringServices\n"
qt.bluetooth.bluez: Read Desc: "\x00\x00"
"Wed Oct 28 11:24:21 2020BTLE stateChanged ServiceDiscovered\n"
"Wed Oct 28 11:24:21 2020characteristic {0000fff2-0000-1000-8000-00805f9b34fb}\n"
"Wed Oct 28 11:24:21 2020characteristic {0000fff1-0000-1000-8000-00805f9b34fb}\n"
"Wed Oct 28 11:24:21 2020creating virtual treadmill interface...\n"
qt.bluetooth: Using BlueZ kernel ATT interface
qt.bluetooth.bluez: Starting to advertise
qt.bluetooth.bluez: sending command; ogf: 8 ocf: 7
qt.bluetooth.bluez: command sent successfully
qt.bluetooth.bluez: Init CCC change to "0100" "{0000fff1-0000-1000-8000-00805f9b34fb}" "{0000fff0-0000-1000-8000-00805f9b34fb}"
qt.bluetooth.bluez: HCI event triggered, type: e
qt.bluetooth.bluez: command 7 executed successfully
qt.bluetooth.bluez: TX power level is 12
qt.bluetooth.bluez: advertising parameters: "a000a0000000000000000000000700"
qt.bluetooth.bluez: advertising data: "1a020a0c0201060d09446f6d796f73427269646765050326180d180000000000"
qt.bluetooth.bluez: scan response data: "17020a0c0d09446f6d796f73427269646765050326180d180000000000000000"
qt.bluetooth.bluez: sending command; ogf: 8 ocf: 10
qt.bluetooth.bluez: command sent successfully
qt.bluetooth.bluez: HCI event triggered, type: e
qt.bluetooth.bluez: command 10 failed with status 12
qt.bluetooth.bluez: Advertising disable failed, ignoring
qt.bluetooth.bluez: sending command; ogf: 8 ocf: 6
qt.bluetooth.bluez: command sent successfully
qt.bluetooth.bluez: HCI event triggered, type: e
qt.bluetooth.bluez: command 6 executed successfully
qt.bluetooth.bluez: sending command; ogf: 8 ocf: 8
qt.bluetooth.bluez: command sent successfully
qt.bluetooth.bluez: HCI event triggered, type: e
qt.bluetooth.bluez: command 8 executed successfully
qt.bluetooth.bluez: sending command; ogf: 8 ocf: 9
qt.bluetooth.bluez: command sent successfully
qt.bluetooth.bluez: HCI event triggered, type: e
qt.bluetooth.bluez: command 9 executed successfully
qt.bluetooth.bluez: sending command; ogf: 8 ocf: 10
qt.bluetooth.bluez: command sent successfully
qt.bluetooth.bluez: HCI event triggered, type: e
qt.bluetooth.bluez: command 10 executed successfully
qt.bluetooth.bluez: HCI event triggered, type: 13
qt.bluetooth.bluez: Write Desc: "{00002902-0000-1000-8000-00805f9b34fb}" "0100"
"Wed Oct 28 11:24:21 2020descriptorWritten Client Characteristic Configuration 01 00\n"
qt.bluetooth.bluez: BluetoothManagement: Ignored event: c
qt.bluetooth.bluez: HCI event triggered, type: 5
qt.bluetooth.bluez: ###### "org.bluez.Device1" QMap(("Connected", QVariant(bool, false))("ServicesResolved", QVariant(bool, false)))
"Wed Oct 28 11:24:21 2020BTLE stateChanged InvalidService\n"
"Wed Oct 28 11:24:21 2020LowEnergy controller disconnected\n"
qt.bluetooth.bluez: Discovered:  "73:11:44:0D:97:51" "73-11-44-0D-97-51" Num UUIDs 0 total device 0 cached RSSI -41 Class 0
"Wed Oct 28 11:24:21 2020Found new device: 73-11-44-0D-97-51 (73:11:44:0D:97:51)\n"
qt.bluetooth.bluez: Discovered:  "A4:C1:38:D9:02:06" "LYWSD03MMC" Num UUIDs 0 total device 1 cached RSSI -80 Class 0
"Wed Oct 28 11:24:21 2020Found new device: LYWSD03MMC (A4:C1:38:D9:02:06)\n"
qt.bluetooth.bluez: Discovered:  "C4:FC:E8:A6:95:04" "RunScribe-06FE" Num UUIDs 4 total device 2 cached RSSI -94 Class 0
"Wed Oct 28 11:24:21 2020Found new device: RunScribe-06FE (C4:FC:E8:A6:95:04)\n"
qt.bluetooth.bluez: Discovered:  "FD:61:AE:2F:59:79" "RunScribe-C670" Num UUIDs 4 total device 3 cached RSSI -79 Class 0
"Wed Oct 28 11:24:21 2020Found new device: RunScribe-C670 (FD:61:AE:2F:59:79)\n"
qt.bluetooth.bluez: Discovered:  "FF:90:CE:BE:F5:FC" "TOORX0083" Num UUIDs 5 total device 4 cached RSSI -73 Class 0
"Wed Oct 28 11:24:21 2020Found new device: TOORX0083 (FF:90:CE:BE:F5:FC)\n"
qt.bluetooth.bluez: void QBluetoothDeviceDiscoveryAgentPrivate::stop()
QObject::disconnect: No such signal trainprogram::changeResistance(double) in mainwindow.cpp:221
QObject::disconnect: No such signal trxappgateusbtreadmill::bikeStarted() in mainwindow.cpp:223
QObject::connect: No such signal trainprogram::changeResistance(double) in mainwindow.cpp:230
QObject::connect: No such signal trxappgateusbtreadmill::bikeStarted() in mainwindow.cpp:232
trainProgram associated to a device
"Wed Oct 28 11:24:21 2020Found new device: TOORX0083 (FF:90:CE:BE:F5:FC)\n"
qt.bluetooth: Using BlueZ LE DBus API
qt.bluetooth.bluez: QLowEnergyControllerPrivateBluezDBus::connectToDevice()
qt.bluetooth.bluez: BluetoothManagement: Ignored event: b
qt.bluetooth.bluez: HCI event triggered, type: 3e
qt.bluetooth.bluez: received connection complete event, handle: 65
qt.bluetooth.bluez: GATT connection from device "FF:90:CE:BE:F5:FC" "TOORX0083"
qt.bluetooth.bluez: Group "RemoteSignatureKey" not found in settings file
qt.bluetooth.bluez: BluetoothManagement: found random device "FF:90:CE:BE:F5:FC"
qt.bluetooth.bluez: Received size: 3 data: "021e00"
qt.bluetooth.bluez: MTU request from client: 30 effective client RX MTU: 30
qt.bluetooth.bluez: Sending server RX MTU 512
qt.bluetooth.bluez: HCI event triggered, type: f
qt.bluetooth.bluez: HCI event triggered, type: 3e
qt.bluetooth.bluez: HCI event triggered, type: 3e
qt.bluetooth.bluez: HCI event triggered, type: 3e
qt.bluetooth.bluez: ###### "org.bluez.Device1" QMap(("RSSI", QVariant(short, -82)))
qt.bluetooth.bluez: Received size: 9 data: "060100ffff00280d18"
qt.bluetooth.bluez: client sends find by type value request; start: 1 end: 65535 type: 10240 value: "0d18"
qt.bluetooth.bluez: sending response: "0709000c00"
qt.bluetooth.bluez: Received size: 7 data: "0809000c000328"
qt.bluetooth.bluez: client sends read by type request, start: 9 end: 12 type: "{00002803-0000-1000-8000-00805f9b34fb}"
qt.bluetooth.bluez: sending response: "09070a00100b00372a"
qt.bluetooth.bluez: HCI event triggered, type: 13
Segmentation fault
cagnulein commented 4 years ago

@drainuzzo very strange: seems that when the connection starts, the trx disconnects itself. If you restart it, does it happen always the same? are you quite near with the raspberry to the trx? is bluez and raspberry-firmware updated as written in the readme?

drainuzzo commented 4 years ago

Sometimes it lasts 5 - 10 seconds and then crash I tried starting the TR but it doesn't change

cagnulein commented 4 years ago

@drainuzzo when it last 5-10 seconds you see the connection goes on? are you quite near with the raspberry to the trx? is bluez and raspberry-firmware updated as written in the readme? did the connect+ asks for a PIN or similar the very first time?

drainuzzo commented 4 years ago

@cagnulein no when it last some seconds I can push the connection button, and then it crashes, or I can wait some seconds and don't push anything and it crashes the same, or it crashes after 1 sec from the opening (in this case the button isn't active)

yeah it is all updated

cagnulein commented 4 years ago

@drainuzzo which connection button? you don't have to push any connection button on the GUI. Could you please send me a log when the connection stays up? These issues seems related to a weak bluetooth signal

drainuzzo commented 4 years ago

I meant Treadmill Connection Status, so it wasn't a button ok 🥇

this is the log when for a sec the Conn Status becomes blue

libEGL warning: DRI2: failed to authenticate
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
qt.bluetooth.bluez: Bluez 5 detected.
qt.bluetooth.bluez: Creating QtBluezDiscoveryManager
qt.bluetooth.bluez: Discovered:  "A4:C1:38:CE:A4:28" "LYWSD03MMC" Num UUIDs 0 total device 0 cached RSSI 0 Class 0
"Wed Oct 28 13:02:19 2020Found new device: LYWSD03MMC (A4:C1:38:CE:A4:28)\n"
qt.bluetooth.bluez: Discovered:  "A4:C1:38:D9:02:06" "LYWSD03MMC" Num UUIDs 0 total device 1 cached RSSI 0 Class 0
"Wed Oct 28 13:02:19 2020Found new device: LYWSD03MMC (A4:C1:38:D9:02:06)\n"
qt.bluetooth.bluez: Discovered:  "C4:FC:E8:A6:95:04" "RunScribe-06FE" Num UUIDs 4 total device 2 cached RSSI 0 Class 0
"Wed Oct 28 13:02:19 2020Found new device: RunScribe-06FE (C4:FC:E8:A6:95:04)\n"
qt.bluetooth.bluez: Discovered:  "FD:61:AE:2F:59:79" "RunScribe-C670" Num UUIDs 4 total device 3 cached RSSI 0 Class 0
"Wed Oct 28 13:02:19 2020Found new device: RunScribe-C670 (FD:61:AE:2F:59:79)\n"
qt.bluetooth.bluez: Discovered:  "FF:90:CE:BE:F5:FC" "TOORX0083" Num UUIDs 5 total device 4 cached RSSI 0 Class 0
"Wed Oct 28 13:02:19 2020Found new device: TOORX0083 (FF:90:CE:BE:F5:FC)\n"
qt.bluetooth.bluez: void QBluetoothDeviceDiscoveryAgentPrivate::stop()
"Wed Oct 28 13:02:19 2020Found new device: TOORX0083 (FF:90:CE:BE:F5:FC)\n"
qt.bluetooth.bluez: Detecting bluetoothd version
qt.bluetooth.bluez: Using /proc/<pid>/exe
qt.bluetooth.bluez: Detected bluetoothd version 5.50
qt.bluetooth.bluez: Bluetoothd: "5.50"
qt.bluetooth: Using BlueZ LE DBus API
qt.bluetooth.bluez: QLowEnergyControllerPrivateBluezDBus::connectToDevice()
"Wed Oct 28 13:02:19 2020Controller connected. Search services...\n"
"Wed Oct 28 13:02:19 2020serviceDiscovered {00001801-0000-1000-8000-00805f9b34fb}\n"
"Wed Oct 28 13:02:19 2020serviceDiscovered {0000fe59-0000-1000-8000-00805f9b34fb}\n"
"Wed Oct 28 13:02:19 2020serviceDiscovered {0000fff0-0000-1000-8000-00805f9b34fb}\n"
"Wed Oct 28 13:02:19 2020serviceDiscovered {0000180a-0000-1000-8000-00805f9b34fb}\n"
"Wed Oct 28 13:02:19 2020serviceScanDone\n"
"Wed Oct 28 13:02:19 2020BTLE stateChanged DiscoveringServices\n"
QMetaObject::connectSlotsByName: No matching signal for on_Inclination_clicked()
qt.bluetooth.bluez: Read Desc: "\x00\x00"
"Wed Oct 28 13:02:20 2020BTLE stateChanged ServiceDiscovered\n"
"Wed Oct 28 13:02:20 2020characteristic {0000fff2-0000-1000-8000-00805f9b34fb}\n"
"Wed Oct 28 13:02:20 2020characteristic {0000fff1-0000-1000-8000-00805f9b34fb}\n"
"Wed Oct 28 13:02:20 2020creating virtual treadmill interface...\n"
qt.bluetooth: Using BlueZ kernel ATT interface
qt.bluetooth.bluez: Starting to advertise
qt.bluetooth.bluez: sending command; ogf: 8 ocf: 7
qt.bluetooth.bluez: command sent successfully
qt.bluetooth.bluez: Init CCC change to "0100" "{0000fff1-0000-1000-8000-00805f9b34fb}" "{0000fff0-0000-1000-8000-00805f9b34fb}"
qt.bluetooth.bluez: BluetoothManagement: Ignored event: 13
qt.bluetooth.bluez: Write Desc: "{00002902-0000-1000-8000-00805f9b34fb}" "0100"
"Wed Oct 28 13:02:20 2020descriptorWritten Client Characteristic Configuration 01 00\n"
qt.bluetooth.bluez: BluetoothManagement: found random device "46:BA:94:1D:E8:8F"
qt.bluetooth.bluez: HCI event triggered, type: e
qt.bluetooth.bluez: command 7 executed successfully
qt.bluetooth.bluez: TX power level is 12
qt.bluetooth.bluez: advertising parameters: "a000a0000000000000000000000700"
qt.bluetooth.bluez: advertising data: "1a020a0c0201060d09446f6d796f73427269646765050326180d180000000000"
qt.bluetooth.bluez: scan response data: "17020a0c0d09446f6d796f73427269646765050326180d180000000000000000"
qt.bluetooth.bluez: sending command; ogf: 8 ocf: 10
qt.bluetooth.bluez: command sent successfully
"Wed Oct 28 13:02:20 2020 >> f0 a0 01 01 92 // init\n"
qt.bluetooth.bluez: BluetoothManagement: found random device "C4:FC:E8:A6:95:04"
qt.bluetooth.bluez: BluetoothManagement: found random device "FD:61:AE:2F:59:79"
qt.bluetooth.bluez: BluetoothManagement: found random device "C4:FC:E8:A6:95:04"
qt.bluetooth.bluez: HCI event triggered, type: 3e
qt.bluetooth.bluez: HCI event triggered, type: 3e
qt.bluetooth.bluez: HCI event triggered, type: 13
qt.bluetooth.bluez: HCI event triggered, type: 3e
qt.bluetooth.bluez: HCI event triggered, type: e
qt.bluetooth.bluez: command 10 failed with status 12
qt.bluetooth.bluez: Advertising disable failed, ignoring
qt.bluetooth.bluez: sending command; ogf: 8 ocf: 6
qt.bluetooth.bluez: command sent successfully
qt.bluetooth.bluez: HCI event triggered, type: e
qt.bluetooth.bluez: command 6 executed successfully
qt.bluetooth.bluez: sending command; ogf: 8 ocf: 8
qt.bluetooth.bluez: command sent successfully
qt.bluetooth.bluez: HCI event triggered, type: e
qt.bluetooth.bluez: command 8 executed successfully
qt.bluetooth.bluez: sending command; ogf: 8 ocf: 9
qt.bluetooth.bluez: command sent successfully
qt.bluetooth.bluez: HCI event triggered, type: e
qt.bluetooth.bluez: command 9 executed successfully
qt.bluetooth.bluez: sending command; ogf: 8 ocf: 10
qt.bluetooth.bluez: command sent successfully
qt.bluetooth.bluez: HCI event triggered, type: e
qt.bluetooth.bluez: command 10 executed successfully
qt.bluetooth.bluez: Written Char: "{0000fff2-0000-1000-8000-00805f9b34fb}" "f0a0010192"
"Wed Oct 28 13:02:21 2020characteristicWritten f0 a0 01 01 92\n"
"Wed Oct 28 13:02:21 2020 >> f0 a5 01 d3 04 6d // init\n"
"Wed Oct 28 13:02:21 2020 << f0 b0 01 d3 74\n"
qt.bluetooth.bluez: HCI event triggered, type: 13
qt.bluetooth.bluez: BluetoothManagement: Ignored event: c
qt.bluetooth.bluez: HCI event triggered, type: 5
qt.bluetooth.bluez: ###### "org.bluez.Device1" QMap(("Connected", QVariant(bool, false))("ServicesResolved", QVariant(bool, false)))
"Wed Oct 28 13:02:21 2020BTLE stateChanged InvalidService\n"
"Wed Oct 28 13:02:21 2020LowEnergy controller disconnected\n"
qt.bluetooth.bluez: Discovered:  "46:BA:94:1D:E8:8F" "46-BA-94-1D-E8-8F" Num UUIDs 0 total device 0 cached RSSI -39 Class 0
"Wed Oct 28 13:02:21 2020Found new device: 46-BA-94-1D-E8-8F (46:BA:94:1D:E8:8F)\n"
qt.bluetooth.bluez: Discovered:  "A4:C1:38:CE:A4:28" "LYWSD03MMC" Num UUIDs 0 total device 1 cached RSSI 0 Class 0
"Wed Oct 28 13:02:21 2020Found new device: LYWSD03MMC (A4:C1:38:CE:A4:28)\n"
qt.bluetooth.bluez: Discovered:  "A4:C1:38:D9:02:06" "LYWSD03MMC" Num UUIDs 0 total device 2 cached RSSI 0 Class 0
"Wed Oct 28 13:02:21 2020Found new device: LYWSD03MMC (A4:C1:38:D9:02:06)\n"
qt.bluetooth.bluez: Discovered:  "C4:FC:E8:A6:95:04" "RunScribe-06FE" Num UUIDs 4 total device 3 cached RSSI -78 Class 0
"Wed Oct 28 13:02:21 2020Found new device: RunScribe-06FE (C4:FC:E8:A6:95:04)\n"
qt.bluetooth.bluez: Discovered:  "FD:61:AE:2F:59:79" "RunScribe-C670" Num UUIDs 4 total device 4 cached RSSI -81 Class 0
"Wed Oct 28 13:02:21 2020Found new device: RunScribe-C670 (FD:61:AE:2F:59:79)\n"
qt.bluetooth.bluez: Discovered:  "FF:90:CE:BE:F5:FC" "TOORX0083" Num UUIDs 5 total device 5 cached RSSI 0 Class 0
"Wed Oct 28 13:02:21 2020Found new device: TOORX0083 (FF:90:CE:BE:F5:FC)\n"
qt.bluetooth.bluez: void QBluetoothDeviceDiscoveryAgentPrivate::stop()
QObject::disconnect: No such signal trainprogram::changeResistance(double) in mainwindow.cpp:221
QObject::disconnect: No such signal trxappgateusbtreadmill::bikeStarted() in mainwindow.cpp:223
QObject::connect: No such signal trainprogram::changeResistance(double) in mainwindow.cpp:230
QObject::connect: No such signal trxappgateusbtreadmill::bikeStarted() in mainwindow.cpp:232
trainProgram associated to a device
"Wed Oct 28 13:02:21 2020Found new device: TOORX0083 (FF:90:CE:BE:F5:FC)\n"
qt.bluetooth: Using BlueZ LE DBus API
qt.bluetooth.bluez: QLowEnergyControllerPrivateBluezDBus::connectToDevice()
qt.bluetooth.bluez: BluetoothManagement: Ignored event: b
qt.bluetooth.bluez: HCI event triggered, type: 3e
qt.bluetooth.bluez: received connection complete event, handle: 65
qt.bluetooth.bluez: HCI event triggered, type: f
qt.bluetooth.bluez: HCI event triggered, type: 3e
qt.bluetooth.bluez: HCI event triggered, type: 3e
qt.bluetooth.bluez: HCI event triggered, type: 3e
qt.bluetooth.bluez: HCI event triggered, type: 3e
qt.bluetooth.bluez: HCI event triggered, type: 3e
qt.bluetooth.bluez: BluetoothManagement: found random device "FF:90:CE:BE:F5:FC"
qt.bluetooth.bluez: HCI event triggered, type: 3e
qt.bluetooth.bluez: ###### "org.bluez.Device1" QMap(("RSSI", QVariant(short, -79)))
qt.bluetooth.bluez: HCI event triggered, type: 3e
qt.bluetooth.bluez: GATT connection from device "FF:90:CE:BE:F5:FC" "TOORX0083"
qt.bluetooth.bluez: Group "RemoteSignatureKey" not found in settings file
qt.bluetooth.bluez: Received size: 3 data: "021e00"
qt.bluetooth.bluez: MTU request from client: 30 effective client RX MTU: 30
qt.bluetooth.bluez: Sending server RX MTU 512
qt.bluetooth.bluez: HCI event triggered, type: e
qt.bluetooth.bluez: HCI event triggered, type: f
qt.bluetooth.bluez: Received size: 9 data: "060100ffff00280d18"
qt.bluetooth.bluez: client sends find by type value request; start: 1 end: 65535 type: 10240 value: "0d18"
qt.bluetooth.bluez: sending response: "0709000c00"
qt.bluetooth.bluez: Received size: 7 data: "0809000c000328"
qt.bluetooth.bluez: client sends read by type request, start: 9 end: 12 type: "{00002803-0000-1000-8000-00805f9b34fb}"
qt.bluetooth.bluez: sending response: "09070a00100b00372a"
qt.bluetooth.bluez: HCI event triggered, type: 13
qt.bluetooth.bluez: Received size: 7 data: "080c000c000328"
qt.bluetooth.bluez: client sends read by type request, start: 12 end: 12 type: "{00002803-0000-1000-8000-00805f9b34fb}"
qt.bluetooth.bluez: sending error response; request: 8 handle: 12 code: 10
Segmentation fault

and this log is another one for the same test but the log is different

libEGL warning: DRI2: failed to authenticate
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
qt.bluetooth.bluez: Bluez 5 detected.
qt.bluetooth.bluez: Creating QtBluezDiscoveryManager
qt.bluetooth.bluez: Discovered:  "A4:C1:38:CE:A4:28" "LYWSD03MMC" Num UUIDs 0 total device 0 cached RSSI 0 Class 0
"Wed Oct 28 13:03:53 2020Found new device: LYWSD03MMC (A4:C1:38:CE:A4:28)\n"
qt.bluetooth.bluez: Discovered:  "A4:C1:38:D9:02:06" "LYWSD03MMC" Num UUIDs 0 total device 1 cached RSSI 0 Class 0
"Wed Oct 28 13:03:53 2020Found new device: LYWSD03MMC (A4:C1:38:D9:02:06)\n"
qt.bluetooth.bluez: Discovered:  "FD:61:AE:2F:59:79" "RunScribe-C670" Num UUIDs 4 total device 2 cached RSSI 0 Class 0
"Wed Oct 28 13:03:53 2020Found new device: RunScribe-C670 (FD:61:AE:2F:59:79)\n"
qt.bluetooth.bluez: Discovered:  "FF:90:CE:BE:F5:FC" "TOORX0083" Num UUIDs 5 total device 3 cached RSSI 0 Class 0
"Wed Oct 28 13:03:53 2020Found new device: TOORX0083 (FF:90:CE:BE:F5:FC)\n"
qt.bluetooth.bluez: void QBluetoothDeviceDiscoveryAgentPrivate::stop()
"Wed Oct 28 13:03:53 2020Found new device: TOORX0083 (FF:90:CE:BE:F5:FC)\n"
qt.bluetooth.bluez: Detecting bluetoothd version
qt.bluetooth.bluez: Using /proc/<pid>/exe
qt.bluetooth.bluez: Detected bluetoothd version 5.50
qt.bluetooth.bluez: Bluetoothd: "5.50"
qt.bluetooth: Using BlueZ LE DBus API
qt.bluetooth.bluez: QLowEnergyControllerPrivateBluezDBus::connectToDevice()
QMetaObject::connectSlotsByName: No matching signal for on_Inclination_clicked()
qt.bluetooth.bluez: ###### "org.bluez.Device1" QMap(("Connected", QVariant(bool, true)))
qt.bluetooth.bluez: BluetoothManagement: Ignored event: 13
qt.bluetooth.bluez: BluetoothManagement: found random device "46:BA:94:1D:E8:8F"
qt.bluetooth.bluez: BluetoothManagement: Ignored event: 13
qt.bluetooth.bluez: BluetoothManagement: Ignored event: b
qt.bluetooth.bluez: ###### "org.bluez.Device1" QMap(("ServicesResolved", QVariant(bool, true)))
"Wed Oct 28 13:03:54 2020Controller connected. Search services...\n"
"Wed Oct 28 13:03:54 2020serviceDiscovered {00001801-0000-1000-8000-00805f9b34fb}\n"
"Wed Oct 28 13:03:54 2020serviceDiscovered {0000fe59-0000-1000-8000-00805f9b34fb}\n"
"Wed Oct 28 13:03:54 2020serviceDiscovered {0000fff0-0000-1000-8000-00805f9b34fb}\n"
"Wed Oct 28 13:03:54 2020serviceDiscovered {0000180a-0000-1000-8000-00805f9b34fb}\n"
"Wed Oct 28 13:03:54 2020serviceScanDone\n"
"Wed Oct 28 13:03:54 2020BTLE stateChanged DiscoveringServices\n"
qt.bluetooth.bluez: Read Desc: "\x00\x00"
"Wed Oct 28 13:03:55 2020BTLE stateChanged ServiceDiscovered\n"
"Wed Oct 28 13:03:55 2020characteristic {0000fff2-0000-1000-8000-00805f9b34fb}\n"
"Wed Oct 28 13:03:55 2020characteristic {0000fff1-0000-1000-8000-00805f9b34fb}\n"
"Wed Oct 28 13:03:55 2020creating virtual treadmill interface...\n"
qt.bluetooth: Using BlueZ kernel ATT interface
qt.bluetooth.bluez: Starting to advertise
qt.bluetooth.bluez: sending command; ogf: 8 ocf: 7
qt.bluetooth.bluez: command sent successfully
qt.bluetooth.bluez: Init CCC change to "0100" "{0000fff1-0000-1000-8000-00805f9b34fb}" "{0000fff0-0000-1000-8000-00805f9b34fb}"
qt.bluetooth.bluez: HCI event triggered, type: e
qt.bluetooth.bluez: command 7 executed successfully
qt.bluetooth.bluez: TX power level is 12
qt.bluetooth.bluez: advertising parameters: "a000a0000000000000000000000700"
qt.bluetooth.bluez: advertising data: "1a020a0c0201060d09446f6d796f73427269646765050326180d180000000000"
qt.bluetooth.bluez: scan response data: "17020a0c0d09446f6d796f73427269646765050326180d180000000000000000"
qt.bluetooth.bluez: sending command; ogf: 8 ocf: 10
qt.bluetooth.bluez: command sent successfully
qt.bluetooth.bluez: HCI event triggered, type: e
qt.bluetooth.bluez: command 10 failed with status 12
qt.bluetooth.bluez: Advertising disable failed, ignoring
qt.bluetooth.bluez: sending command; ogf: 8 ocf: 6
qt.bluetooth.bluez: command sent successfully
qt.bluetooth.bluez: HCI event triggered, type: e
qt.bluetooth.bluez: command 6 executed successfully
qt.bluetooth.bluez: sending command; ogf: 8 ocf: 8
qt.bluetooth.bluez: command sent successfully
qt.bluetooth.bluez: HCI event triggered, type: e
qt.bluetooth.bluez: command 8 executed successfully
qt.bluetooth.bluez: sending command; ogf: 8 ocf: 9
qt.bluetooth.bluez: command sent successfully
qt.bluetooth.bluez: HCI event triggered, type: e
qt.bluetooth.bluez: command 9 executed successfully
qt.bluetooth.bluez: sending command; ogf: 8 ocf: 10
qt.bluetooth.bluez: command sent successfully
qt.bluetooth.bluez: HCI event triggered, type: e
qt.bluetooth.bluez: command 10 executed successfully
qt.bluetooth.bluez: HCI event triggered, type: 13
qt.bluetooth.bluez: Write Desc: "{00002902-0000-1000-8000-00805f9b34fb}" "0100"
"Wed Oct 28 13:03:55 2020descriptorWritten Client Characteristic Configuration 01 00\n"
qt.bluetooth.bluez: HCI event triggered, type: 13
"Wed Oct 28 13:03:55 2020 >> f0 a0 01 01 92 // init\n"
qt.bluetooth.bluez: Written Char: "{0000fff2-0000-1000-8000-00805f9b34fb}" "f0a0010192"
"Wed Oct 28 13:03:55 2020characteristicWritten f0 a0 01 01 92\n"
"Wed Oct 28 13:03:55 2020 >> f0 a5 01 d3 04 6d // init\n"
"Wed Oct 28 13:03:55 2020 << f0 b0 01 d3 74\n"
qt.bluetooth.bluez: HCI event triggered, type: 13
qt.bluetooth.bluez: Written Char: "{0000fff2-0000-1000-8000-00805f9b34fb}" "f0a501d3046d"
"Wed Oct 28 13:03:56 2020characteristicWritten f0 a5 01 d3 04 6d\n"
"Wed Oct 28 13:03:56 2020 >> f0 a0 01 d3 64 // init\n"
"Wed Oct 28 13:03:56 2020 << f0 b5 01 d3 04 7d\n"
qt.bluetooth.bluez: HCI event triggered, type: 13
qt.bluetooth.bluez: HCI event triggered, type: 13
qt.bluetooth.bluez: BluetoothManagement: Ignored event: c
qt.bluetooth.bluez: HCI event triggered, type: 5
qt.bluetooth.bluez: ###### "org.bluez.Device1" QMap(("Connected", QVariant(bool, false))("ServicesResolved", QVariant(bool, false)))
"Wed Oct 28 13:03:56 2020BTLE stateChanged InvalidService\n"
"Wed Oct 28 13:03:56 2020LowEnergy controller disconnected\n"
qt.bluetooth.bluez: Discovered:  "A4:C1:38:CE:A4:28" "LYWSD03MMC" Num UUIDs 0 total device 0 cached RSSI 0 Class 0
"Wed Oct 28 13:03:56 2020Found new device: LYWSD03MMC (A4:C1:38:CE:A4:28)\n"
qt.bluetooth.bluez: Discovered:  "A4:C1:38:D9:02:06" "LYWSD03MMC" Num UUIDs 0 total device 1 cached RSSI 0 Class 0
"Wed Oct 28 13:03:56 2020Found new device: LYWSD03MMC (A4:C1:38:D9:02:06)\n"
qt.bluetooth.bluez: Discovered:  "FD:61:AE:2F:59:79" "RunScribe-C670" Num UUIDs 4 total device 2 cached RSSI -84 Class 0
"Wed Oct 28 13:03:56 2020Found new device: RunScribe-C670 (FD:61:AE:2F:59:79)\n"
qt.bluetooth.bluez: Discovered:  "FF:90:CE:BE:F5:FC" "TOORX0083" Num UUIDs 5 total device 3 cached RSSI 0 Class 0
"Wed Oct 28 13:03:56 2020Found new device: TOORX0083 (FF:90:CE:BE:F5:FC)\n"
qt.bluetooth.bluez: void QBluetoothDeviceDiscoveryAgentPrivate::stop()
QObject::disconnect: No such signal trainprogram::changeResistance(double) in mainwindow.cpp:221
QObject::disconnect: No such signal trxappgateusbtreadmill::bikeStarted() in mainwindow.cpp:223
QObject::connect: No such signal trainprogram::changeResistance(double) in mainwindow.cpp:230
QObject::connect: No such signal trxappgateusbtreadmill::bikeStarted() in mainwindow.cpp:232
trainProgram associated to a device
"Wed Oct 28 13:03:56 2020Found new device: TOORX0083 (FF:90:CE:BE:F5:FC)\n"
qt.bluetooth: Using BlueZ LE DBus API
qt.bluetooth.bluez: QLowEnergyControllerPrivateBluezDBus::connectToDevice()
qt.bluetooth.bluez: BluetoothManagement: Ignored event: b
qt.bluetooth.bluez: HCI event triggered, type: 3e
qt.bluetooth.bluez: received connection complete event, handle: 65
qt.bluetooth.bluez: GATT connection from device "FF:90:CE:BE:F5:FC" "TOORX0083"
qt.bluetooth.bluez: Group "RemoteSignatureKey" not found in settings file
Segmentation fault
cagnulein commented 4 years ago

@drainuzzo it's very clear from the 2nd log that you have an issue of weak signal. Infact, look these lines

"Wed Oct 28 13:03:55 2020 >> f0 a0 01 01 92 // init\n"
qt.bluetooth.bluez: Written Char: "{0000fff2-0000-1000-8000-00805f9b34fb}" "f0a0010192"
"Wed Oct 28 13:03:55 2020characteristicWritten f0 a0 01 01 92\n"
"Wed Oct 28 13:03:55 2020 >> f0 a5 01 d3 04 6d // init\n"
"Wed Oct 28 13:03:55 2020 << f0 b0 01 d3 74\n"
qt.bluetooth.bluez: HCI event triggered, type: 13
qt.bluetooth.bluez: Written Char: "{0000fff2-0000-1000-8000-00805f9b34fb}" "f0a501d3046d"
"Wed Oct 28 13:03:56 2020characteristicWritten f0 a5 01 d3 04 6d\n"
"Wed Oct 28 13:03:56 2020 >> f0 a0 01 d3 64 // init\n"
"Wed Oct 28 13:03:56 2020 << f0 b5 01 d3 04 7d\n"

You see that the lines with << is the TRX Gate answering back to the raspberry. So the communication is in progress but after few moments, it drops.

Could you please try to put the raspberry more near to the TRX? You had always value of RSSI below -80, so is very very weak

drainuzzo commented 4 years ago

Ok I put the pi to a 1m from the bt key.. so now it is impossible that was far (before was at about 3mt)

libEGL warning: DRI2: failed to authenticate
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
qt.bluetooth.bluez: Bluez 5 detected.
qt.bluetooth.bluez: Creating QtBluezDiscoveryManager
qt.bluetooth.bluez: Discovered:  "A4:C1:38:CE:A4:28" "LYWSD03MMC" Num UUIDs 0 total device 0 cached RSSI 0 Class 0
"Wed Oct 28 14:22:01 2020Found new device: LYWSD03MMC (A4:C1:38:CE:A4:28)\n"
qt.bluetooth.bluez: Discovered:  "A4:C1:38:D9:02:06" "LYWSD03MMC" Num UUIDs 0 total device 1 cached RSSI 0 Class 0
"Wed Oct 28 14:22:01 2020Found new device: LYWSD03MMC (A4:C1:38:D9:02:06)\n"
qt.bluetooth.bluez: Discovered:  "C4:FC:E8:A6:95:04" "RunScribe-06FE" Num UUIDs 4 total device 2 cached RSSI 0 Class 0
"Wed Oct 28 14:22:01 2020Found new device: RunScribe-06FE (C4:FC:E8:A6:95:04)\n"
qt.bluetooth.bluez: Discovered:  "FD:61:AE:2F:59:79" "RunScribe-C670" Num UUIDs 4 total device 3 cached RSSI 0 Class 0
"Wed Oct 28 14:22:01 2020Found new device: RunScribe-C670 (FD:61:AE:2F:59:79)\n"
qt.bluetooth.bluez: Discovered:  "FF:90:CE:BE:F5:FC" "TOORX0083" Num UUIDs 5 total device 4 cached RSSI 0 Class 0
"Wed Oct 28 14:22:01 2020Found new device: TOORX0083 (FF:90:CE:BE:F5:FC)\n"
qt.bluetooth.bluez: void QBluetoothDeviceDiscoveryAgentPrivate::stop()
"Wed Oct 28 14:22:01 2020Found new device: TOORX0083 (FF:90:CE:BE:F5:FC)\n"
qt.bluetooth.bluez: Detecting bluetoothd version
qt.bluetooth.bluez: Using /proc/<pid>/exe
qt.bluetooth.bluez: Detected bluetoothd version 5.50
qt.bluetooth.bluez: Bluetoothd: "5.50"
qt.bluetooth: Using BlueZ LE DBus API
qt.bluetooth.bluez: QLowEnergyControllerPrivateBluezDBus::connectToDevice()
QMetaObject::connectSlotsByName: No matching signal for on_Inclination_clicked()
qt.bluetooth.bluez: ###### "org.bluez.Device1" QMap(("RSSI", QVariant(short, -55)))
qt.bluetooth.bluez: ###### "org.bluez.Device1" QMap(("Connected", QVariant(bool, true)))
qt.bluetooth.bluez: BluetoothManagement: Ignored event: 13
qt.bluetooth.bluez: BluetoothManagement: found random device "30:B7:55:2E:79:AF"
qt.bluetooth.bluez: BluetoothManagement: found random device "FF:90:CE:BE:F5:FC"
qt.bluetooth.bluez: BluetoothManagement: Ignored event: 13
qt.bluetooth.bluez: BluetoothManagement: Ignored event: 13
qt.bluetooth.bluez: BluetoothManagement: found random device "FD:61:AE:2F:59:79"
qt.bluetooth.bluez: BluetoothManagement: Ignored event: b
qt.bluetooth.bluez: BluetoothManagement: found random device "30:B7:55:2E:79:AF"
qt.bluetooth.bluez: BluetoothManagement: found random device "C4:FC:E8:A6:95:04"
qt.bluetooth.bluez: ###### "org.bluez.Device1" QMap(("ServicesResolved", QVariant(bool, true)))
"Wed Oct 28 14:22:03 2020Controller connected. Search services...\n"
"Wed Oct 28 14:22:03 2020serviceDiscovered {00001801-0000-1000-8000-00805f9b34fb}\n"
"Wed Oct 28 14:22:03 2020serviceDiscovered {0000fe59-0000-1000-8000-00805f9b34fb}\n"
"Wed Oct 28 14:22:03 2020serviceDiscovered {0000fff0-0000-1000-8000-00805f9b34fb}\n"
"Wed Oct 28 14:22:03 2020serviceDiscovered {0000180a-0000-1000-8000-00805f9b34fb}\n"
"Wed Oct 28 14:22:03 2020serviceScanDone\n"
"Wed Oct 28 14:22:03 2020BTLE stateChanged DiscoveringServices\n"
qt.bluetooth.bluez: Read Desc: "\x00\x00"
"Wed Oct 28 14:22:03 2020BTLE stateChanged ServiceDiscovered\n"
"Wed Oct 28 14:22:03 2020characteristic {0000fff2-0000-1000-8000-00805f9b34fb}\n"
"Wed Oct 28 14:22:03 2020characteristic {0000fff1-0000-1000-8000-00805f9b34fb}\n"
"Wed Oct 28 14:22:03 2020creating virtual treadmill interface...\n"
qt.bluetooth: Using BlueZ kernel ATT interface
qt.bluetooth.bluez: Starting to advertise
qt.bluetooth.bluez: sending command; ogf: 8 ocf: 7
qt.bluetooth.bluez: command sent successfully
qt.bluetooth.bluez: Init CCC change to "0100" "{0000fff1-0000-1000-8000-00805f9b34fb}" "{0000fff0-0000-1000-8000-00805f9b34fb}"
qt.bluetooth.bluez: HCI event triggered, type: e
qt.bluetooth.bluez: command 7 executed successfully
qt.bluetooth.bluez: TX power level is 12
qt.bluetooth.bluez: advertising parameters: "a000a0000000000000000000000700"
qt.bluetooth.bluez: advertising data: "1a020a0c0201060d09446f6d796f73427269646765050326180d180000000000"
qt.bluetooth.bluez: scan response data: "17020a0c0d09446f6d796f73427269646765050326180d180000000000000000"
qt.bluetooth.bluez: sending command; ogf: 8 ocf: 10
qt.bluetooth.bluez: command sent successfully
qt.bluetooth.bluez: HCI event triggered, type: e
qt.bluetooth.bluez: command 10 failed with status 12
qt.bluetooth.bluez: Advertising disable failed, ignoring
qt.bluetooth.bluez: sending command; ogf: 8 ocf: 6
qt.bluetooth.bluez: command sent successfully
qt.bluetooth.bluez: HCI event triggered, type: e
qt.bluetooth.bluez: command 6 executed successfully
qt.bluetooth.bluez: sending command; ogf: 8 ocf: 8
qt.bluetooth.bluez: command sent successfully
qt.bluetooth.bluez: HCI event triggered, type: e
qt.bluetooth.bluez: command 8 executed successfully
qt.bluetooth.bluez: sending command; ogf: 8 ocf: 9
qt.bluetooth.bluez: command sent successfully
qt.bluetooth.bluez: HCI event triggered, type: e
qt.bluetooth.bluez: command 9 executed successfully
qt.bluetooth.bluez: sending command; ogf: 8 ocf: 10
qt.bluetooth.bluez: command sent successfully
qt.bluetooth.bluez: HCI event triggered, type: e
qt.bluetooth.bluez: command 10 executed successfully
qt.bluetooth.bluez: HCI event triggered, type: 13
qt.bluetooth.bluez: Write Desc: "{00002902-0000-1000-8000-00805f9b34fb}" "0100"
"Wed Oct 28 14:22:03 2020descriptorWritten Client Characteristic Configuration 01 00\n"
"Wed Oct 28 14:22:04 2020 >> f0 a0 01 01 92 // init\n"
qt.bluetooth.bluez: Written Char: "{0000fff2-0000-1000-8000-00805f9b34fb}" "f0a0010192"
"Wed Oct 28 14:22:04 2020characteristicWritten f0 a0 01 01 92\n"
"Wed Oct 28 14:22:04 2020 >> f0 a5 01 d3 04 6d // init\n"
"Wed Oct 28 14:22:04 2020 << f0 b0 01 d3 74\n"
qt.bluetooth.bluez: HCI event triggered, type: 13
qt.bluetooth.bluez: Written Char: "{0000fff2-0000-1000-8000-00805f9b34fb}" "f0a501d3046d"
"Wed Oct 28 14:22:04 2020characteristicWritten f0 a5 01 d3 04 6d\n"
"Wed Oct 28 14:22:04 2020 >> f0 a0 01 d3 64 // init\n"
"Wed Oct 28 14:22:04 2020 << f0 b5 01 d3 04 7d\n"
qt.bluetooth.bluez: Written Char: "{0000fff2-0000-1000-8000-00805f9b34fb}" "f0a001d364"
"Wed Oct 28 14:22:04 2020characteristicWritten f0 a0 01 d3 64\n"
"Wed Oct 28 14:22:04 2020 >> f0 a1 01 d3 65 // init\n"
qt.bluetooth.bluez: HCI event triggered, type: 13
"Wed Oct 28 14:22:04 2020virtualtreadmill connection error\n"
"Wed Oct 28 14:22:04 2020 << f0 b0 01 d3 74\n"
qt.bluetooth.bluez: Written Char: "{0000fff2-0000-1000-8000-00805f9b34fb}" "f0a101d365"
"Wed Oct 28 14:22:04 2020characteristicWritten f0 a1 01 d3 65\n"
"Wed Oct 28 14:22:04 2020 >> f0 a0 01 d3 64 // init\n"
qt.bluetooth.bluez: HCI event triggered, type: 13
"Wed Oct 28 14:22:04 2020 << f0 b1 01 d3 02 15 02 01 10 9f\n"
qt.bluetooth.bluez: Written Char: "{0000fff2-0000-1000-8000-00805f9b34fb}" "f0a001d364"
"Wed Oct 28 14:22:04 2020characteristicWritten f0 a0 01 d3 64\n"
"Wed Oct 28 14:22:04 2020 >> f0 a3 01 d3 01 15 01 02 51 01 51 23 // init\n"
"Wed Oct 28 14:22:04 2020 << f0 b0 01 d3 74\n"
qt.bluetooth.bluez: Written Char: "{0000fff2-0000-1000-8000-00805f9b34fb}" "f0a301d30115010251015123"
"Wed Oct 28 14:22:05 2020characteristicWritten f0 a3 01 d3 01 15 01 02 51 01 51 23\n"
"Wed Oct 28 14:22:05 2020 >> f0 a4 01 d3 01 01 01 01 01 01 01 01 01 01 01 73 // init\n"
qt.bluetooth.bluez: HCI event triggered, type: 13
"Wed Oct 28 14:22:05 2020 << f0 b3 01 d3 01 15 01 01 b5 01 51 96\n"
qt.bluetooth.bluez: Written Char: "{0000fff2-0000-1000-8000-00805f9b34fb}" "f0a401d3010101010101010101010173"
"Wed Oct 28 14:22:05 2020characteristicWritten f0 a4 01 d3 01 01 01 01 01 01 01 01 01 01 01 73\n"
"Wed Oct 28 14:22:05 2020 >> f0 af 01 d3 02 75 // init\n"
qt.bluetooth.bluez: HCI event triggered, type: 13
"Wed Oct 28 14:22:05 2020 << f0 b4 01 d3 01 01 01 01 01 01 01 01 01 01 01 83\n"
qt.bluetooth.bluez: Written Char: "{0000fff2-0000-1000-8000-00805f9b34fb}" "f0af01d30275"
"Wed Oct 28 14:22:05 2020characteristicWritten f0 af 01 d3 02 75\n"
"Wed Oct 28 14:22:05 2020 << f0 bf 01 d3 02 85\n"
"Wed Oct 28 14:22:05 2020virtualtreadmill connection error\n"
qt.bluetooth.bluez: Written Char: "{0000fff2-0000-1000-8000-00805f9b34fb}" "f0a201d366"
"Wed Oct 28 14:22:05 2020characteristicWritten f0 a2 01 d3 66\n"
"Wed Oct 28 14:22:05 2020 << f0 b2 01 d3 01 01 01 01 01 01 01 01 01 01 01 01 04 02 88\n"
"Wed Oct 28 14:22:05 2020Current speed: 25.9\n"
"Wed Oct 28 14:22:05 2020Current incline: 0\n"
"Wed Oct 28 14:22:05 2020Current heart: 0\n"
"Wed Oct 28 14:22:05 2020Current KCal: 256\n"
"Wed Oct 28 14:22:05 2020Current Distance: 25.6\n"
"Wed Oct 28 14:22:05 2020Current Distance Calculated: 0\n"
qt.bluetooth.bluez: HCI event triggered, type: 13
qt.bluetooth.bluez: HCI event triggered, type: 13
qt.bluetooth.bluez: BluetoothManagement: Ignored event: c
qt.bluetooth.bluez: HCI event triggered, type: 5
qt.bluetooth.bluez: ###### "org.bluez.Device1" QMap(("Connected", QVariant(bool, false))("ServicesResolved", QVariant(bool, false)))
"Wed Oct 28 14:22:06 2020BTLE stateChanged InvalidService\n"
"Wed Oct 28 14:22:06 2020LowEnergy controller disconnected\n"
qt.bluetooth.bluez: Discovered:  "30:B7:55:2E:79:AF" "30-B7-55-2E-79-AF" Num UUIDs 0 total device 0 cached RSSI -46 Class 0
"Wed Oct 28 14:22:06 2020Found new device: 30-B7-55-2E-79-AF (30:B7:55:2E:79:AF)\n"
qt.bluetooth.bluez: Discovered:  "A4:C1:38:CE:A4:28" "LYWSD03MMC" Num UUIDs 0 total device 1 cached RSSI 0 Class 0
"Wed Oct 28 14:22:06 2020Found new device: LYWSD03MMC (A4:C1:38:CE:A4:28)\n"
qt.bluetooth.bluez: Discovered:  "A4:C1:38:D9:02:06" "LYWSD03MMC" Num UUIDs 0 total device 2 cached RSSI -75 Class 0
"Wed Oct 28 14:22:06 2020Found new device: LYWSD03MMC (A4:C1:38:D9:02:06)\n"
qt.bluetooth.bluez: Discovered:  "C4:FC:E8:A6:95:04" "RunScribe-06FE" Num UUIDs 4 total device 3 cached RSSI -77 Class 0
"Wed Oct 28 14:22:06 2020Found new device: RunScribe-06FE (C4:FC:E8:A6:95:04)\n"
qt.bluetooth.bluez: Discovered:  "FD:61:AE:2F:59:79" "RunScribe-C670" Num UUIDs 4 total device 4 cached RSSI -77 Class 0
"Wed Oct 28 14:22:06 2020Found new device: RunScribe-C670 (FD:61:AE:2F:59:79)\n"
qt.bluetooth.bluez: Discovered:  "FF:90:CE:BE:F5:FC" "TOORX0083" Num UUIDs 5 total device 5 cached RSSI -55 Class 0
"Wed Oct 28 14:22:06 2020Found new device: TOORX0083 (FF:90:CE:BE:F5:FC)\n"
qt.bluetooth.bluez: void QBluetoothDeviceDiscoveryAgentPrivate::stop()
QObject::disconnect: No such signal trainprogram::changeResistance(double) in mainwindow.cpp:221
QObject::disconnect: No such signal trxappgateusbtreadmill::bikeStarted() in mainwindow.cpp:223
QObject::connect: No such signal trainprogram::changeResistance(double) in mainwindow.cpp:230
QObject::connect: No such signal trxappgateusbtreadmill::bikeStarted() in mainwindow.cpp:232
trainProgram associated to a device
"Wed Oct 28 14:22:06 2020Found new device: TOORX0083 (FF:90:CE:BE:F5:FC)\n"
qt.bluetooth: Using BlueZ LE DBus API
qt.bluetooth.bluez: QLowEnergyControllerPrivateBluezDBus::connectToDevice()
qt.bluetooth.bluez: BluetoothManagement: Ignored event: b
qt.bluetooth.bluez: HCI event triggered, type: 3e
qt.bluetooth.bluez: received connection complete event, handle: 65
qt.bluetooth.bluez: GATT connection from device "FF:90:CE:BE:F5:FC" "TOORX0083"
qt.bluetooth.bluez: Group "RemoteSignatureKey" not found in settings file
qt.bluetooth.bluez: ###### "org.bluez.Device1" QMap(("RSSI", QVariant(short, -59)))
qt.bluetooth.bluez: Received size: 3 data: "021e00"
qt.bluetooth.bluez: MTU request from client: 30 effective client RX MTU: 30
qt.bluetooth.bluez: Sending server RX MTU 512
Segmentation fault
cagnulein commented 4 years ago

ok, so things are moving now:

"Wed Oct 28 14:22:05 2020Current speed: 25.9\n"
"Wed Oct 28 14:22:05 2020Current incline: 0\n"
"Wed Oct 28 14:22:05 2020Current heart: 0\n"
"Wed Oct 28 14:22:05 2020Current KCal: 256\n"
"Wed Oct 28 14:22:05 2020Current Distance: 25.6\n"
"Wed Oct 28 14:22:05 2020Current Distance Calculated: 0\n"

the value are not ok, but there is a comunication between them.

The RSSI goes to -55 that is very good. Are you sure that you don't have any device that tries to connect to the TRX App GATE in addition to the raspberry?

Anyway i will study the log and i will think about it. For the moment, thank you, you're dismiss 😆

cagnulein commented 4 years ago

@drainuzzo did the iConsole+ asks for a PIN or similar the very first time? i guess it disconnects because i'm not authorized, is it possible?

drainuzzo commented 4 years ago

no, any key or pin :(

cagnulein commented 4 years ago

@drainuzzo when it's possible, could you please try https://github.com/cagnulein/qdomyos-zwift/commit/d5ddc4cabd1eb11da97a9c3859507f9323fec7cd ?

i fixed the parsing of the values and i reduced the polling time from 500ms to 200ms: i'm hoping that the TRX goes to timeout because it doesn't receive anything in time from the raspberry.

After try this, could you please rerun the software with gdb, i would like to understand the Segmentation fault. Run it with gdb, so

$ gdb ./qdomyos-zwift

c

...when it hangs...

bt

and put me here the log

Thanks in advance

drainuzzo commented 4 years ago

Ok I will try soon, just a question is there a way to compile only the last changes without delete folder and recompile all?

cagnulein commented 4 years ago

Ok I will try soon, just a question is there a way to compile only the last changes without delete folder and recompile all?

yes on the folder, do

$ git pull $ cd src $ qmake $ make -j5

drainuzzo commented 4 years ago

OK I tried the new code and now the App doesn't crash!! Great achievement bravo! 💯

Now the app starts, when I start the TR and try to change speed or inclination with the TR these values don't change on the app, the other shown values as you checked before aren't correct

I did a couple of run so you can see the 2 debug files, I tried to start Zwift from my phone but it could not discover the TR-Bridge for now

debug-TR-AppGate-1.zip

Note: the bt input for gdb didn't work because it didn't find a stack or something like that after gdb commnand I had to give a start command then I exit gdb just closing the running app, I hope that was ok

cagnulein commented 4 years ago

Wonderful! So it was all about timing! Great to know!

ok so:

I tried to start Zwift from my phone but it could not discover the TR-Bridge for now

are you 100% sure that you run

sudo apt update && sudo apt upgrade && reboot

?

the bt input for gdb didn't work because it didn't find a stack or something like that after gdb commnand I had to give a start command then I exit gdb just closing the running app, I hope that was ok

ok, now gdb is useless, we haven't crashes anymore 😆

Now the app starts, when I start the TR and try to change speed or inclination with the TR these values don't change on the app, the other shown values as you checked before aren't correct

ok i'm checking the log. I will let you know when i will be ready for another run :)

the pull && make commands work?

cagnulein commented 4 years ago

@drainuzzo i saw in the first log, that speed has about 5.1 Km/h and inclination goes from 1.0 to 2.7 is it correct? when you make some test and post me the log remember always to write me that you did because otherwise i can connect the number to your actions. Thanks

drainuzzo commented 4 years ago

@cagnulein

i saw in the first log, that speed has about 5.1 Km/h and inclination goes from 1.0 to 2.7 is it correct?

I increased the speed I think max to 4 on my TR I don't know if it is 5.1km/h and I really would like to know these matches in the future to understand better my speed as well 😄

About that do you think it is possible to insert a pace/km value also? Would be nice even if probably not so accurate...

I am sure I changed the inclination from 0 to 1 to 2 and then back, there isn't a 2.7 value on my TR I don't know if it would indicate a degree of the inclination

are you 100% sure that you run

sudo apt update && sudo apt upgrade && reboot

I haven't reboot today after the updates but the I haven't found so much stuff

remember always to write me that you did because otherwise i can connect the number to your actions

ok next times I will be more accurate with my report,I have been more focused on the connection side so far 😃

the pull && make commands work?

yes they worked well

Good job Roberto 👍

cagnulein commented 4 years ago

@drainuzzo

About that do you think it is possible to insert a pace/km value also? Would be nice even if probably not so accurate...

yes, absolutely, i will create an issue ad hoc

I increased the speed I think max to 4 on my TR I don't know if it is 5.1km/h and I really would like to know these matches in the future to understand better my speed as well 😄

did you keep the speed constant during all the session? don't you see the speed on some console on your treadmill? could you please send me a pic of your setup (usb+treadmill) i'm really curious 😄

I haven't reboot today after the updates but the I haven't found so much stuff

mmm... did you wait some seconds (10 or 20) in zwift looking for the bridge (clicking on speed button to searching a device)? it's really strange that you didn't see the bridge, it's the first time that i heard this issue.

ok next times I will be more accurate with my report,I have been more focused on the connection side so far

hahah thanks, yeah you did a great job on debug it too!

cagnulein commented 4 years ago

@drainuzzo this is the graphic from your log. Do you recognize a pattern? the dark green one i guess is the inclination Immagine

this is the full excel file extracted from your 1st log trx.xlsx

from this log i extracted also the elapsed time, that i will push in a moment

drainuzzo commented 4 years ago

@cagnulein

mmm... did you wait some seconds (10 or 20) in zwift looking for the bridge (clicking on speed button to searching a device)? it's really strange that you didn't see the bridge, it's the first time that i heard this issue.

yes I tried a lot, if you check at the 2nd log you can see a message Thu Oct 29 11:06:12 2020virtualtreadmill connection error

maybe this is the message regarding the zwift issue?

Let me know today I can run a test reporting all metrics better, let me know if you want me to active some debug or other stuff before I start

cagnulein commented 4 years ago

@drainuzzo

maybe this is the message regarding the zwift issue?

yes, it says that no one zwift client is connected to my bridge. But it's not releated to the bridge itself. Could you please download also nrfconnect ( https://play.google.com/store/apps/details?id=no.nordicsemi.android.mcp&hl=it&gl=US ) anche check if the DomyosBridge appears there? This is a bluetooth simple sniffer.

If you want, today i'm in smart working, we can connect eachother in a debug session on teamviewer or something like this.

cagnulein commented 4 years ago

@drainuzzo the bridge appears only when the connection to the treadmill has established

drainuzzo commented 4 years ago

@cagnulein

yes, it says that no one zwift client is connected to my bridge. But it's not releated to the bridge itself. Could you please download also nrfconnect ( https://play.google.com/store/apps/details?id=no.nordicsemi.android.mcp&hl=it&gl=US ) anche check if the DomyosBridge appears there? This is a bluetooth simple sniffer.

I found an interesting thing: with sudo your app doesn't connect to the TR, without it the connection is fine even at bigger distance (3mt)

Now I tried the nrfconnect but id doesn't discover any DoymosBridge (the connection has established)

If you want, today i'm in smart working, we can connect eachother in a debug session on teamviewer or something like this.

I have some calls in the next hours better if I can make some spot tests

Thanks!!

cagnulein commented 4 years ago

@drainuzzo

I found an interesting thing: with sudo your app doesn't connect to the TR, without it the connection is fine even at bigger distance (3mt)

maybe just a spot case. Is it deterministic? On raspberry bluetooth doesn't work without sudo...so i guess it's quite strange

Now I tried the nrfconnect but id doesn't discover any DoymosBridge (the connection has established)

do you have any other phones to test? i'm start thinking it's something about the phone...

drainuzzo commented 4 years ago

@cagnulein

maybe just a spot case. Is it deterministic? On raspberry bluetooth doesn't work without sudo...so i guess it's quite strange

seems deterministic on my raspberry 3b

do you have any other phones to test? i'm start thinking it's something about the phone...

not at the moment but the nrfconnect sees the toorx and my other bt devices also so it is strange that is my phone's fault 😃

cagnulein commented 4 years ago

@drainuzzo could you please try to run

$ sudo hciconfig hci0 leadv 0

before starting my program?

drainuzzo commented 4 years ago

@cagnulein

done but no result from the command

instead

sudo hciconfig 
hci0:   Type: Primary  Bus: UART
    BD Address: B8:27:EB:2C:B2:A8  ACL MTU: 1021:8  SCO MTU: 64:1
    UP RUNNING PSCAN 
    RX bytes:114717 acl:3424 sco:0 events:2398 errors:0
    TX bytes:37555 acl:1777 sco:0 commands:636 errors:0
cagnulein commented 4 years ago

@drainuzzo no output is ok from that command. but what if you run that command and start the software? does the gateway appear?

drainuzzo commented 4 years ago

@cagnulein

nothing appears on Zwift, btw I checked on BT devices on the phone and with nrfconnect and there I can se the Bridge!

But if I try to connect to him I can't

cagnulein commented 4 years ago

so please @drainuzzo

1) run hciconfig hci0 leadv 0 2) run my app with sudo 3) try to connect with nrfconnect

if it doesn't work, close my app and repeat from step 1

if it doesn't work

1) run hciconfig hci0 leadv 0 2) run my app without sudo 3) try to connect with nrfconnect

if it doesn't work, close my app and repeat from step 1

we need to know the correct flow on your side. I don't understand which is the difference from all the other raspberry that advertises correctly the bridge, but we have to discover it!

drainuzzo commented 4 years ago

Great worked!

if it doesn't work run hciconfig hci0 leadv 0 run my app without sudo try to connect with nrfconnect

and I discovered it with Zwift, so starting the prog without sudo seems the way