I still haven't had any reply from Enhanced Radio Devices via email about the lipo charge function of the board not working on one of my boards, to see if I can fix myself or needs a swapout. Is there any other way to contact them......?
@danamlewis With help :) nano pump.ini (thats not right but I don't have the notes infront of me) I had some assistance, thanks Simon, I ended up running the script again and everything starting going to NS. But...., I'm now sitting in front of the rig cursing again. Anyone have any trouble logging into the rig? ssh just goes nowhere, change cables, turn off, unplug, have a beer (only one), no good. Im away from home and wanted to setup the hotspot wifi so NS will update. I'm medtronic cgm. bit painful crabs don't go into the system unless online.
I have multiple rigs setup and have initially synced up autotune results. My question is why would autotune results get out of date between the rigs. They are both using the same data to calculate autotune results correct?
If anyone is using Medtronic CGM in their loop, I could use your help in adding MDT CGM support to the Go code used by the dev branch of openaps (so far it only handles Dexcom). I'd need you to run some commands on your rig to capture "raw" glucose history pages, plus the openaps command that decodes those pages; I can provide more details if you PM me.
Anyone have any updates on progress with the Tandem t:slim and OpenAPS or the open API initiative that as announced from JDRF? I haven't seen much activity on the Tandem Slack channel and haven't heard anything new from JDRF. We got the t:slim X2 a few months ago as a hedge in anticipation of hopefully moving off Medtronics and back to the t:slim. Would be great to have choices other than Medtronic.
@danamlewis is in a room right now with FDA, JDRF, and a bunch of pump manufacturers discussing the JDRF Opening Protocols initiative. So it's moving forward, but I wouldn't expect it to move quickly enough to produce something useful for any existing hardware that isn't already loopable. (On that note, the Roche Combo is loopable with AndroidAPS, and already has 100 active users. It's FDA-approved in the US, but hard to get here since Roche pulled out of the market.)
The predictions don't make sense to me. I see that these line up with the purple lines and they all seem to goto down really quick., but why would zero-temping line go down faster than the IOB purple line?
I have used this system a lot, and its worked wonderful(thanks). Just trying to understand and fine tune it.
@scottleibrand Thanks for the update Scott. I'm not sure i understand your comment, "...I wouldn't expect it to move quickly enough to produce something useful for any existing hardware that isn't already loopable." Seems to me that this is primarily a software issue not hardware and I would think an over the air update from Tandem could make the pump loopable if they included the APIs (Open Protocol). I understand that any major update would likely require FDA approval but I don't see any need to make hardware modifications--esp since the X2 is the platform for their future AP software.
@cbrenner I'm talking more about what I expect they will do than what they could do. We'll see what comes out of the FDA/JDRF meeting, but I expect the path between those discussion and actual software updates to existing pumps, or new pumps, will be long.
Possibly corrupted incoming data, possibly corrupted old data that got stored in Nightscout's database at some point
I think the next thing to try would be deleting everything from NS's database, or pointing it at a fresh database, to eliminate any junk that might've gotten in there during install or on a previous debugging attempt