Skip to content

Command 01 Version Response

Jump to bottom Edit New page
Joe Moran edited this page Sep 16, 2018 · 19 revisions

01 Version Response

This command is sent by the Pod as a response to certain PDM commands using during startup and has different formats of varying lengths depending on the PDM command. The 01 Command can occur in response to request mtype 07 Assign ID Command and 03 Setup Pod Command in addition to various internal debug commands ($32, $35, $36, $39 & $3A) with varying sizes.

Command 07 response (mlen $15)

The Response 01 message with mlen $15 is returned from 07 Command and has the following format:

OFF 1  2 3 4  5 6 7  8  9 10111213 14151617 18 19202122
01 15 MXMYMZ IXIYZI 02 0J LLLLLLLL TTTTTTTT GS IIIIIIII
  • 01 (1 byte) [0]: mtype value of 01 specifies version response command
  • 15 (1 byte) [1]: mlen of $15 is this format (07 Command response)
  • MXMYMZ (3 bytes) [2:4]: PM MX.MY.MZ
  • IXIYIZ (3 bytes) [5:7]: PI IX.IY.IZ
  • 02 (1 byte) [8]: always 2 (at least for PM == PI == 2.7.0)
  • 0J (1 byte) [9]: Pod progress value between 0 and $F
    • 0: Initial value (or reset by $38 command)
    • 1: Tank power activated
    • 2: Tank fill completed
    • 3: Pairing success
    • 4: Purging
    • 5: Ready for injection
    • 6: Injection done
    • 7: Priming cannula
    • 8: Running (Typical value)
    • 9: Running with <= 50U left in reservoir
    • $A: Not used (except possibly with a $33 command)
    • $B: Not used (except possibly with a $33 command)
    • $C: Not used (except possibly with a $33 command)
    • $D: Error event logged, shutting down
    • $E: Alert expired during initialization, shutting down
    • $F: Pod inactive ($1C Deactivate Pod or packet header mismatch)
  • LLLLLLLL (4 bytes) [$A:$D]: Pod Lot
  • TTTTTTTT (4 bytes) [$E:$11]: Pod TID
  • GS (1 byte) [$12]: ggssssss where gg = two bits of receiver gain, ssssss = 6 bits of rssi value
  • IIIIIIII (4 bytes) [$13:$16]: ID (Pod address) as given in the 07 Command

Example #1 for Command 07 response (mlen $15)

Taken from Pairing 03:

01 15 MXMYMZ IXIYIZ 02 0J LLLLLLLL TTTTTTTT GS IIIIIIII
01 15 020700 020700 02 02 0000a377 0003ab37 9f 1f00ee87
  • PM = 2.7.0
  • PI = 2.7.0
  • Pod progress = 2 (Tank fill completed)
  • Lot = $0000a377 = L41847
  • TID = $0003ab37 = 240439
  • GS = $9f: Receiver Low Gain = 2, RSSI = $1f
  • Pod connection ID (address) = $1f00ee87

Example #2 for Command 07 response (mlen $15)

Taken from Pod setup with known Lot and TID:

01 15 MXMYMZ IXIYIZ 02 0J LLLLLLLL TTTTTTTT GS IIIIIIII
01 15 020700 020700 02 02 0000a640 00097c27 9c 1f08ced2
  • PM = 2.7.0
  • PI = 2.7.0
  • Pod progress = 2 (Tank fill completed)
  • Lot = $0000a640 = L42560
  • TID = $00087c27 = 556071
  • GS = $9c: Receiver Low Gain = 2, RSSI = $1c
  • Connection ID (Pod address) = $1f08ced2

Because this format 01 Response is used to reply to (07 Command, which used as part of a fixed sequence when activating a new Pod, the Pod progress byte 0J should typically be 02 (Tank fill completed).

Command 03 response (mlen $1b)

Response Command 01 with an length of $1b is returned from the Pod for a 03 Command from the PDM.

OFF 1  2 3 4 5 6 7 8  91011 121314 15 16 17181920 21222324 25262728
01 1b 13881008340A50 MXMYMZ IXIYIZ 02 0J LLLLLLLL TTTTTTTT IIIIIIII
  • 01 (1 byte) [0]: mtype value of 01 specifies version response command
  • 1b (1 byte) [1]: mlen of $1b is this format (03 Command response)
  • 13881008340A50 (7 bytes) [2:8]: fixed byte sequence of unknown meaning
  • MXMYMZ (3 bytes) [9:$B]: PM MX.MY.MZ
  • IXIYIZ (3 bytes) [$C:$E]: PI IX.IY.IZ
  • 02 (1 byte) [$F]: always 2 (for PM == PI == 2.7.0)
  • 0J (1 byte) [$10]: Pod progress value between 0 and $F
    • 0: Initial value (or reset by $38 command)
    • 1: Tank power activated
    • 2: Tank fill completed
    • 3: Pairing success
    • 4: Purging
    • 5: Ready for injection
    • 6: Injection done
    • 7: Priming cannula
    • 8: Running (Typical value)
    • 9: Running with <= 50U left in reservoir
    • $A: Not used (except possibly with a $33 command)
    • $B: Not used (except possibly with a $33 command)
    • $C: Not used (except possibly with a $33 command)
    • $D: Error event logged, shutting down
    • $E: Alert expired during initialization, shutting down
    • $F: Pod inactive ($1C Deactivate Pod or packet header mismatch)
  • LLLLLLLL (4 bytes) [$11:$14]: Pod Lot
  • TTTTTTTT (4 bytes) [$15:$18]: Pod TID
  • IIIIIIII (4 bytes) [$19:$1C]: Connection ID (Pod address)

Example for Command 03 response (mlen $1b)

Taken from Pod setup with known Lot and TID:

01 1b 13881008340A50 MXMYMZ IXIYIZ 02 0J LLLLLLLL TTTTTTTT PPPPPPPP
01 1b 13881008340a50 020700 020700 02 03 0000a377 0003ab37 1f00ee87
  • PM = 2.7.0
  • PI = 2.7.0
  • Pod progress = 3 (Pairing success)
  • Lot = $0000a377 = L41847
  • TID = $0003ab37 = 240439
  • Pod address = $1f00ee87

There is actually no additional information contained in this format 01 Command with mlen $1b for a 03 Command response than there is for the 01 Command format with mlen $15 for a (07 Command response since the unknown byte sequence of 13881008340a50 is fixed value (at least for PM == PI == 2.7.0). Since 03 Command is used by the PDM to complete the Pod pairing & activation operation, the Pod progress byte 0J should typically be 03 (Pairing success).

Other 01 Version Response Lengths for Debug Commands

  • mlen $02 for Commands $39 and $3A
  • mlen $04 for Command $35
  • mlen $0c for Command $36
  • mlen $17 for Command $32
Add a custom footer

Communications

Reference

Message decoding

Device drivers

Hardware

Clone this wiki locally