Joe Moran

The 049 fault codes use a different format (TT-XXX-YYYY-FFFFF) as they represent a controller problem, not a pod problem. It turns out that these format errors are a fixed value...

We have never found any evidence that Loop is issuing any incorrect commands that can cause a 0xCB (203) fault (along with many other fault types) other than producing a...

See latest comments on [LoopKit 2195](https://github.com/LoopKit/Loop/issues/2195). [OmniBLE PR #125](https://github.com/LoopKit/OmniBLE/pull/125) and [OmniKit PR #36](https://github.com/LoopKit/OmniKit/pull/36) might eliminate the possibility of this happening any more. But if this is not sufficient, Loop should...

Thank you for the detailed observations and capturing the log right after it happened @live4sw. Here’s a summary of the basic pod commands at the end of the comms log...

Going back and looking at the Loop Report from @DavidRYL on July 21st, here’s a summary of the boluses from the comms log around the time of the bogus HUD...

It appears that if Loop is put in the background while displaying an in-progress bolus and then put into the foreground later in the middle of some other bolus, Loop...

``` // 0.20 auto bolus start at 16:30:04 which should finish at 16:30:04 + (4 pulses * 2 sec/pulse) = 16:30:12 COMMAND: 2023-09-30 16:30:03 Message(175c3dea seq:12 [SetInsulinScheduleCommand(nonce:494e532e, bolus(units: 0.2, timeBetweenPulses:...

Thanks for running this one down & generating a PR for this Marion. From the provided Loop pics I personally prefer using a lineWidth of 2 for these open circles...