Fixes to stop the CNL from going into an error state:
Intercept unexpected messages from the CNL These usually come from pump requests as it can occasionally resend message responses several times (possibly due to a missed CNL ACK during CNL-PUMP comms?) Mostly noted on the higher radio channels, channel 26 shows this the most If these messages are not cleared the CNL will likely error needing to be unplugged to reset as it expects them to be read before any further commands are sent
Showing
- app/src/main/java/info/nightscout/android/medtronic/message/ContourNextLinkMessage.java 51 additions, 1 deletion...out/android/medtronic/message/ContourNextLinkMessage.java
- app/src/main/java/info/nightscout/android/medtronic/message/EHSMMessage.java 10 additions, 0 deletions...nfo/nightscout/android/medtronic/message/EHSMMessage.java
- app/src/main/java/info/nightscout/android/medtronic/message/PumpStatusRequestMessage.java 5 additions, 1 deletion...t/android/medtronic/message/PumpStatusRequestMessage.java
- app/src/main/java/info/nightscout/android/medtronic/message/PumpTimeRequestMessage.java 6 additions, 2 deletions...out/android/medtronic/message/PumpTimeRequestMessage.java
- app/src/main/java/info/nightscout/android/medtronic/message/PumpTimeResponseMessage.java 4 additions, 2 deletions...ut/android/medtronic/message/PumpTimeResponseMessage.java
Please register or sign in to comment