search

StephenBlackWasAlreadyTaken / xDrip-Experimental

Experimental Branches for Collaboration on DexDrip
GNU General Public License v3.0
25 stars 62 forks source link

Can't set TXID on xbridge #399

Closed danpowell88 closed 7 years ago

danpowell88 commented 7 years ago

I've reflashed a wixel and have tried to setup xdrip beta/xdrip+ with my transmitter ID (6GQ6X).

Watching the console I can see they neither of them are ever sending the reply to the wixel for the transmitter ID.

Settings as follows:

Hardware Data Source:  xBridge Wixel
Dexcom Transmitter ID: 6GQ6X

Logs for xdrip show: DexCollectionService: setSerialDataToTransmitterRawData: TXID wrong. Expected 6840542 but got 0

and the wixel is showing

Processing Status Command
xBridge v2.46
dex_tx_id: 0 (00000)
initialised: 0, sleep_ble: 1, dont_ignore_ble_state: 1, xBridge_hardware: 1, send_debug: 1, do_leds: 1
dex_tx_id_set: 0, got_packet: 0
battery_capacity: 0
current ms: 398108
No dex_tx_id.  Sending beacon.
400345: sending beacon Now
Sending: ▒
Response: ▒▒`hNo dex_tx_id.  Sending beacon.
410402: sending beacon Now
Sending: ▒
Response: ▒▒`h

The wixel does show up when I scan for BT devices and allows me to connect to it.

It was previously working on this phone and then I got a new receiver and was not able to get the transmitter ID updated so flashed the wixel and removed xdrip and reinstalled.

danpowell88 commented 7 years ago

Not quite sure how but eventually it seemed to update the ID

jstevensog commented 7 years ago

The first thing i would suggest is to check the wiring between the wixel and the HM1X module. It seems to me that something is amiss here, as it appears that xBridge2 is sending the beacon packet to xDrip/xDrip+, but it is not getting a response (or wasn't). So, you may have a dry solder joint or other problem.

I have had HM-1X modules go "bad" and start to spam the wixel serial lines with noise, and that corrupts the ACK and other packets. I have also had (on older rigs) warn out wiring causing similar issues. I have switched to heavier cable as it is more robust. Hope this helps. Cheers

On Tue, Dec 6, 2016 at 5:33 PM, Daniel Powell notifications@github.com wrote:

I've reflashed a wixel and have tried to setup xdrip beta/xdrip+ with my transmitter ID (6GQ6X).

Watching the console I can see they neither of them are ever sending the reply to the wixel for the transmitter ID.

Settings as follows:

Hardware Data Source: xBridge Wixel Dexcom Transmitter ID: 6GQ6X

Logs for xdrip show: DexCollectionService: setSerialDataToTransmitterRawData: TXID wrong. Expected 6840542 but got 0

and the wixel is showing

Processing Status Command xBridge v2.46 dex_tx_id: 0 (00000) initialised: 0, sleep_ble: 1, dont_ignore_ble_state: 1, xBridge_hardware: 1, send_debug: 1, do_leds: 1 dex_tx_id_set: 0, got_packet: 0 battery_capacity: 0 current ms: 398108 No dex_tx_id. Sending beacon. 400345: sending beacon Now Sending: ▒ Response: ▒▒hNo dex_tx_id. Sending beacon. 410402: sending beacon Now Sending: ▒ Response: ▒▒h

Any ideas

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/StephenBlackWasAlreadyTaken/xDrip-Experimental/issues/399, or mute the thread https://github.com/notifications/unsubscribe-auth/AIQs80PiK9mypNdqmA0QIwnKrhg4-SOUks5rFQHIgaJpZM4LFEmM .

-- John Stevens "You are how you live, not what you have."