Where in the codebase is the closed loop stuff I'm mostly finding communication stuff and main loop on a cursory look
sorry, I haven't pushed the closed loop code to github out of concern for liability etc. But there's code to fetch pump history, and pump commands like set_temp_basal, for someone who wants to experiment on their own
Ah fair enough
Hey all! is anyone here well versed in using the G6 Receiver's serial command grammar? I'm trying to understand the "System Time" and "Display Time", and why they might be different than the time set on the receiver
@ijustlovemath if it's the same approach that the G4 used, then it's based on this:
@juehv thanks for that! There may be something in there I can use :) So did they change the CRC between transmitter firmware revisions? Or did they just change the data format and use the same CRC? I see there's some kind of switch in there for a certain revision triggering different code
I have no idea .. didn't have the time to check the code yet :D
It currently only displays the current value without Trend - I don't understand the trend and status variable...
My plan is to add a Nightscout rest-api call if the esp32 did not get any data for 5,5 Minutes and get the data from there
So there is currently at least one ESP32 with ePaper in the world which displays the G6 Data via direct Bluetooth readout - before that I only fetched the data from NS
Does anyone know what part number and location to buy for the Micro USB surface mount on the Edison Explorer board? I have two that the OTG have broken off and would like to repair them. I've also have two boards that get extremely hot whenever they are plugged in, Does anyone know what is the likely cause of that, and is it anything that is fixable. I'm not too shabby at soldering, So if possible would like to try to repair them.
@Bender1061 The explorer board's charging circuit eventually fails, and it stops charging. Also, there is a different rate-of-charge through each of the connectors - the UART port charges slower (less stress) than the OTG one....
I've had one explorer board die by mechanical failure of the micro-USB connector. There's also a failure mode where if you put 5V into the OTG port instead of the charge port, one of the chips on the board promptly overheats and smokes; I've destroyed two that way.
Update from ITB - the Pi Zero 2 has excellent performance, but about 50% less battery life (eg, runs for ~12hrs rather than a day-and-a-half on a 6000mah 3p 18650 pack) compared to Edison or the original Pi Zero.
I've been running it with three cores disabled, and (accidentally) got about 16-17 hours from unplugging to total poweroff on two 18650s
was getting similar to you numbers with all four cores enabled
Only conclusion I have from my Zero 2 so far is "soldering headers on is harder than I expected given no soldering experience and a $20 soldering kit". Oh well.
Is there any prior work on attaching a speaker to a Pi Zero's GPIO at the same time as an Explorer Board?
no, but it shouldn't be a problem as long as there are no pin conflicts
you could even attach it to the bottom, or get tall headers and shim the wires in that way