-
Notifications
You must be signed in to change notification settings - Fork 46
Pod Progress State
The Omnipod keeps an internal Progress State variable that starts at 0 and advances to a maximum value of 15. Internally this value is stored as a set of 16 bits, but this value is always accessed by using a routine that finds the highest bit that is set to indicate the progress of the Pod. This 4-bit Pod Progress State value is included within many of the responses: 01 Version Response, 02 Type 2 Fault Response and 1D Status Response.
- 0: Initial value
- 1: Tank power activated
- 2: Tank filled & activation alert set
- 3: Pairing success
- 4: Purging
- 5: Ready for injection
- 6: Injection done
- 7: Priming cannula
- 8: Running with > 50U in reservoir
- 9: Running with <= 50U in reservoir
- 10: Not used (except for possible debug use)
- 11: Not used (except for possible debug use)
- 12: Not used (except for possible debug use)
- 13: Fault event occurred, shutting down
- 14: Failed to initialize in time, shutting down
- 15: Pod inactive
A Pod will pass through states 1 thru 7 during the Pod initialization process and then will be in state 8. The vast majority of a typical Pod's active lifetime is spent in states 8 and perhaps 9.
For many commands, the Pod must be at one of the correct Pod Progress States for that command or the command will fail or the Pod will fail, typically with a $31 fault.