-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed bolus #52
Comments
Hmm looks like the issue is that on the main page it says bolus iob is 12 units which is correct but when you click on the insulin graph. It says only 4.4 iob. It hasn't been low temping because I turned it off and there is no way that removing the basal can cut the iob by 8 units |
Can you show me the reservoir readings? (Tap on the IOB graph) |
https://www.dropbox.com/sc/6avvi5irudbzm51/AADaML0btZaCTpvHMyPP_mq7a Here are 4 screenshots of the main screen plus the reservoir readings. The one at 6:54 pm is the one I think is missing from the iob calculation |
What is the calculated IOB value? There are large chunks of data missing in that reservoir history, as well as a rewind/prime. According to your pump history, what time were the boluses delivered? |
Bolus: Right now the pump says 11.3 units on board. The home screen of the app says 11.475 units on board. But when you click on the insulin graph it shows 8.14 now. When I sent you the earlier screenshots, the main screen showed 12+ and the graph showed 4.4 We changed the reservoir around 8:50 or so because he has been high and we are changing everything out. The issues started before we changed the reservior |
So according to the max insulin delivery of 2.0 U/min, this drop was assumed to be false (e.g. a prime). This is a bug in Loop which is exposed when the phone time and the pump time drift out-of-sync. With x23 pumps, I'm erroneously mixing pump clock (from sentry packets) with phone clock (manual reservoir readings before a bolus). This was identified and fixed in #49, and I'll go ahead and cut this as a release. So sorry you experienced this – thank you for finding it and filing. I'm going to close this as a duplicate as #49. |
No problem. Glad to know it is a bug that already has a solution. Thank you again for developing this implementation. My son loves it and doesn't want to go back to the edison rig. |
* Add timer for marking glucose as stale * Move check for change into didSet
* Add timer for marking glucose as stale * Move check for change into didSet
Tried to bolus through the app. It says it failed. Then tried it again and it went through. The bolus insulin on board correctly shows the right amount but it never showed up in the Nightscout upload.
The problem is that the projected bg levels don't show the impact of that bolus even though it shows 10+ units of insulin on board. His bg projection goes right up to 700.
The text was updated successfully, but these errors were encountered: