Open PieterGit opened 7 years ago
Getting same error with 3 receivers. I'll append the message and Firmware info for each.
Here's the first (oldest):
pi@Raspi3:~/myopenaps-cgm-loop $ openaps use cgm GetFirmwareHeader { "DexBootVersion": "3", "RFVersion": "1.0.0.27", "ApiVersion": "2.3.0.0", "ProductName": "Dexcom G4 Receiver", "SoftwareNumber": "SW10557", "TestApiVersion": "2.4.0.0", "SchemaVersion": "1", "PortVersion": "4.6.4.50", "FirmwareVersion": "2.0.1.192", "ProductId": "G4Receiver" }pi@Raspi3:~/myopenaps-cgm-loop $
]pi@Raspi3:~/myopenaps-cgm-loop $ openaps use cgm calibrations
Traceback (most recent call last):
File "/usr/local/bin/openaps-use", line 63, in
The second receiver gives similar output. Here's the firmware header message:
$ openaps use cgm GetFirmwareHeader
{
"DexBootVersion": "3",
"RFVersion": "1.0.0.27",
"ApiVersion": "2.3.0.0",
"ProductName": "Dexcom G4 Receiver",
"SoftwareNumber": "SW10557",
"TestApiVersion": "2.4.0.0",
"SchemaVersion": "1",
"PortVersion": "4.6.4.50",
"FirmwareVersion": "2.0.1.192",
"ProductId": "G4Receiver"
}pi@Raspi3:~/myope
And here's the output from use cgm calibrations:
pi@Raspi3:~/myopenaps-cgm-loop $ openaps use cgm calibrations
Traceback (most recent call last):
File "/usr/local/bin/openaps-use", line 63, in
I think it's ApiVersion 2.3.0.0 related. Here is my info:
# openaps use cgm GetFirmwareHeader
{
"DexBootVersion": "6",
"RFVersion": "1.0.0.28",
"ApiVersion": "2.3.0.0",
"ProductName": "Dexcom G4 Receiver",
"SoftwareNumber": "SW10324",
"TestApiVersion": "2.4.0.0",
"SchemaVersion": "1",
"PortVersion": "4.6.4.60",
"FirmwareVersion": "2.0.1.216",
"ProductId": "G4Receiver"
}
@danamlewis (or others): Could you post your firmware / api version for which calibrations work fine?
With current oref0@dev and Dexcom G4 connected to USB (
CGM=G4-upload
) I get the following stack trace.This seems like a dexcom_reader issue. Reading the calibration records with a G4 Dexcom Reader with AndroidUploader app works fine, and the Dexcom G4 can also be read with Dexcom Studio fine. So I think there is a bug in the dexcom_reader logic but I'm incapable of finding the root cause.
@bewest or @LorelaiL or somebody else: Can you help me debug/fix this issue?
References which might be usefull: