bolus ack #14
Open
bolus ack #14
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mmeowlink and Carelink stick do slightly different things:
* Carelink always returns a payload, even when no payload exists,
apparently to convey error status?
* Mmeowlink exposes the acks per frame, but we observe no payload
in the RF, therefore we generate a fictitious 64 byte null
payload.
I've seen following successful fictious payloads from Carelink usb:
0x00 0x00
0x00
0x0c
0x00 0x0c
I've seen the following unsuccessful failure payloads from
Carelink usb (eg exceeding the max bolus limit):
0x09
0x09 0x09
Try to fix spelling of receive.
Changed spelling of recieve to receive.
|
We should probably test this with SMB. |
|
Looks like this will require updating the various bits of oref0 that accommodate the mis-spelling of |
|
Turns out the "recieve" hack was already removed from oref0. Created https://github.com/openaps/decocare/tree/0.1.0-dev and https://github.com/openaps/oref0/tree/decocare-0.1.0 to test this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
mmeowlink and Carelink stick do slightly different things:
apparently to convey error status?
in the RF, therefore we generate a fictitious 64 byte null
payload.
I've seen following successful fictious payloads from Carelink usb:
0x00 0x00
0x00
0x0c
0x00 0x0c
I've seen the following unsuccessful failure payloads from
Carelink usb (eg exceeding the max bolus limit):
0x09
0x09 0x09
Please do special testing on this, it's related to #4