-
Notifications
You must be signed in to change notification settings - Fork 46
Command 0E Status Request
The PDM uses a $E Command to request status from the Pod. The only parameter is this command is a single byte that contains the type of status to be returned. The command format is as follows:
OFF 1 2
Oe 01 TT
- byte
0e
: mtype of0e
- byte
01
: length, fixed 1-byte command length - byte
TT
: request type-
$00
1D Status Response - standard status response -
$01
02 Response, Type 1 - unacknowledged alert status -
$02
02 Response, Type 2 - detailed (fault) status -
$03
02 Response, Type 3 - up to the last 60 pulse log entries and other info -
$05
02 Response, Type 5 - various information including the Pod initialization time -
$07
1D Status Response - DASH only standard status response using special message # handling -
$50
02 Response, Type 80 - the last 50 pulse log entries -
$51
02 Response, Type 81 - like Type 80 ($50), but up to the last 50 entries before the last 50 entries
-
The usual PDM status request for type 0 (or for type 7 with a DASH) yields a Command-1D-Status-response response from the Pod. This is the same response that the pod returns for all for non-fault & non-error commands after pairing. All of the other $0e command type requests will generate a Command-02-Pod-Information-Response from the Pod of varying different formats depending on the request type.
Request type 0 example:
Oe 01 TT
0e 01 00 PDM request type 0
1d SS 0PPPSNNN SSTTTTRR
1d 19 061f6800 044295e8 Pod responds with $1D status
Request type 1 example:
Oe 01 TT
0e 01 01 PDM request type 1
02 13 01 XXXX VVVV VVVV VVVV VVVV VVVV VVVV VVVV VVVV
02 13 01 0000 0000 0000 0000 0000 0000 0000 0000 0000 Pod responds with $02 Pod information type 1
More Examples can be found here:
A type 7 request is a DASH specific type which returns the standard status response just like type 0 request, but doesn't use the same Omnipod message number handling as the other Omnipod commands. Normally the 4-bit message sequence # (the CCCC
bits in the "B9" byte in the generic Omnipod message header as described here) is incremented for each command and for each response (resulting in consecutive commands having their message #'s incremented by 2), while with the type 7 get status command, this message # is only incremented once for each command/response (resulting in consecutive commands having their message #'s incremented by 1). The DASH PDM uses type 7 requests for general connection and status requests and uses type 0 requests only as part of certain operation sequences. It is not understood at this time if there are any other semantics for a type 7 request or what are the potential benefits of using a type 7 request instead of a type 0 request.
DASH PDM example:
Type 7 get status command CCCC=1101=13 08202EAB 3403 0E0107
CCCC=1101=14 08202EAB 380A 1D1802742800001BDBFF
Type 7 get status command CCCC=1110=14 08202EAB 3803 0E0107
CCCC=1110=15 08202EAB 3C0A 1D180274A800001BEFFF
Type 7 get status command CCCC=1111=15 08202EAB 3C03 0E0107
CCCC=0000= 0 08202EAB 000A 1D180277A800001C4FFF
Type 0 get status command CCCC=0000= 0 08202EAB 0003 0E0100
CCCC=0001= 1 08202EAB 040A 1D180277A800001C53FF
bolus command CCCC=0010= 2 08202EAB 0821 1A10494E532E020227020B6000B600B6004E 170D00071C00030D40030C0023366C
CCCC=0011= 3 08202EAB 0C0A 1D5802779104001C53FF
Type 7 get status command CCCC=0011= 3 08202EAB 0C03 0E0107
CCCC=0100= 4 08202EAB 100A 1D58028690E6001C57FF
Type 7 get status command CCCC=0100= 4 08202EAB 1003 0E0107
CCCC=0101= 5 08202EAB 0101 1D1803019000001D67FF
Type 7 get status command CCCC=0101= 5 08202EAB 0101 0E0107
This command can only be used when the current Pod Progress State is between 3 and 14.
This command can be successfully used on a faulted (screaming) pod, but request types 0 and 7 will return a Type 2, Pod Info 02 Response on the faulted pod while all other request types will return the requested Command-02-Pod-Information-Response information.