Flags are missing in accuChekUSB.js

[N0ury]

Flags like "before meal", "after meal", "sleep"... are missing
Is it possible to add them ?

[gniezen]

Hi @N0ury ! It should be possible to add them. I've logged your request and hope it can be prioritized in future: https://tidepool.atlassian.net/browse/UPLOAD-1522

Roche uses the USB PHDC and IEEE 11073 standards for their protocol implementation, so if anyone finds the time to implement this, I'd be very happy to accept a pull request! 😉

[N0ury]

Hi @gniezen If someone can point me to detailed messages exchange, I will try to do that.
I have searched, probably not well. I have found only general descriptions, not detailed one.
I have also tried with no success to reverse engineer using USBPCAP, or debug mode.
I haven't found where these data are. But I'm sure there are, because Windows app shows them.

[gniezen]

The standards they used are:

• IEEE 11073-10417
• IEEE 11073-20601

Unfortunately these standards are not freely available, and different country-specific standards bodies charge different prices for them. If you're not able to obtain them through your work, university or library, my understanding is that the Estonian standards body (https://www.evs.ee/en) has the most reasonable pricing. Or you could just wait until we find the time to implement it.

[N0ury]

hi @gniezen I'm not sure if this can help.
Here's what I've found by analyzing communication between accu-chek Smart Pix Software and accu-chek Guide device:

e7000010000e00080107000800050c1c00020007 out

e7000012001000080207000a00050c1c000400070000 in

e70001b001ae021c010101a80005ffffffff0d21019e0007000000000000002880000190 in
20251010150630000002
20251012141955000001
20251013081013000001
20251013154407000001
20251014053303000004
20251014075932000001
20251014092824000002
20251014122741000001
20251014145025000002
20251014184752000001
20251016224703000003
20251017195724000002
20251017213042000003
20251020104802000004
20251020141947000001
20251021080647000001
20251021201259000001
20251022064337000004
20251022205552000002
20251023063328000004
20251023072024000001
20251023072125000002
20251023072328000003
20251023074312000005
20251023074619000000
20251024141755000001
20251030072306000001
20251031082414000001
20251031130732000001
20251031190651000001
20251103185156000001
20251104083909000001
20251104193117000000
20251106183950000001
20251107085429000001
20251108083241000001
20251116085949000001
20251120123735000001
20251121120658000002
20251121122959000002

e700001e001c021c020100160005ffffffff0d21000c000700000000000000280080 out

e70000ca00c8021d010100c20005ffffffff0d2100b800070000002800000011400000aa in
20251121125213000002
20251125093139000001
20251125135548000001
20251126090848000001
20251127090150000001
20251128184138000000
20251130081010000001
20251130134824000001
20251202090711000001
20251203085517000001
20251203133017000001
20251204085622000001
20251204143024000001
20251204193114000001
20251206084905000001
20251206134951000001
20251206195826000001

This shows clearly that position 9 (starting at 0) is the flag.

Values i've found are:
00: nothing
01: before meal
02: after meal
03: bet time
04: fasting
05: other

out is the communication from computer to device. I don't know how build this at this time.
in is response from device.
Position 31 (starting always at 0) is the number of flags.

I'm sure 100% of this.

What I don't know is the request and the response structure with codes and else.