Status Packets

Unpaired

When unpaired, the address fields appear to be set to 0xff:

158ms: ffffffffa3ffffffff040607041f01482b037f8d
457ms: ffffffffa3ffffffff040607041f01482b037f8d
756ms: ffffffffa3ffffffff040607041f01482b037f8d
1055ms: ffffffffa3ffffffff040607041f01482b037f8d
1353ms: ffffffffa3ffffffff040607041f01482b037f8d
1652ms: ffffffffa3ffffffff040607041f01482b037f8d
1951ms: ffffffffa3ffffffff040607041f01482b037f8d
2250ms: ffffffffa3ffffffff040607041f01482b037f8d
2549ms: ffffffffa3ffffffff040607041f01482b037f8d
2848ms: ffffffffa3ffffffff040607041f01482b037f8d
3146ms: ffffffffa3ffffffff040607041f01482b037f8d

Paired

When paired status packets appear as triplets. The first packet is from the PDM, the next one is from the POD, and the last is from the PDM.

1f01482bbf1f01482b30030e010002ef04
1f01482be01f01482b340a1d18002640000000abff835bb5
1f01482b411f01482bc9

==============
1f01482ba81f01482b08030e0100815b4f
1f01482be91f01482b0c0a1d180037c0000001d3ff83cf34
1f01482b4a1f01482b76

This one is interesting, because in the last packet the second address copy is all zeros. Did the PDM not hear the pod, and indicate so in the last packet (which seems like it might be a kind of ack)?

1f01482bb21f01482b04030e0100035ec0
(response from pod too loud)
1f01482b5400000000ea

Status packets from @dan:

1f02d5adb11f02d5ad0c030e010002bf48
1f02d5ad531f02d5ad27

==============
1f02d5ada91f02d5ad0c030e010002bf65
1f02d5ad4b1f02d5ad0c0489e2

Packets from @t1djoe

###Start New Pod

ffffffffaeffffffff000607041f0218c303a53b ffffffffaeffffffff000607041f0218c303a53b ffffffffefffffffff0417011502070002070002020000a4be0004 ffffffff501f0218c31e ffffffffb1ffffffff001503131f0218c31404060c100d2f0000a4be0004e4a1038653 ffffffffb1ffffffff001503131f0218c31404060c100d2f0000a4be0004e4a1038653 ffffffff531f0218c3b8 ffffffff941f0218c38165a4 ffffffff551f0218c3f3

1f0218c3b61f0218c3080c190a0a711c2c4c000190010200a980 1f0218c3b61f0218c3080c190a0a711c2c4c000190010200a980 1f0218c3f71f0218c30c0a1d0300001000000003ff810b89 1f0218c3b91f0218c3100c190adaca31d278370005080201dd20 1f0218c3b91f0218c3100c190adaca31d278370005080201dd20 1f0218c3fa1f0218c3140a1d0300002000000003ff809a59 1f0218c35b1f0218c34c 1f0218c3bc1f0218c3181f1a0e6e36830c02010a0101a000340034170d000208000186a05d 1f0218c3bc1f0218c3181f1a0e6e36830c02010a0101a000340034170d000208000186a05d 1f0218c39e000000000000806829 1f0218c3ff1f0218c31c0a1d4400003034000003ff0393ed 1f0218c3ff1f0218c31c0a1d4400003034000003ff0393ed 1f0218c3401f0218c3c1

Finished Priming

1f0218c3a11f0218c3200c190a991cff6b38000ff00302836410 1f0218c3e21f0218c3240a1d050016c000000007ff037d87

Insert and Start Pod

1f0218c3a41f0218c3a8421a18aeeb88b00004701b139000077012481300158814a014d82b 1f0218c3451f0218c32c1f126f2ad10e85b6da2203b7 1f0218c3a61f0218c3a8421a18aeeb88b00004701b139000077012481300158814a014d823 1f0218c3a61f0218c3a8421a18aeeb88b00004701b139000077012481300158814a014d823 1f0218c3471f0218c3e8 1f0218c388131326400304f6004c4b4005a00098968003cf008cd9b107350085fac7096003 1f0218c3491f0218c3ba 1f0218c3eb1f0218c32c0a1d160016d00000000bff029544 1f0218c3ad1f0218c3b0181916feb6268b79a410de0502280012820602020f00000202826d 1f0218c3eb1f0218c32c0a1d160016d00000000bff029544 1f0218c3ad1f0218c3b0181916feb6268b79a410de0502280012820602020f00000202826d 1f0218c34e1f0218c393 1f0218c38f6a49 1f0218c3f01f0218c3340a1d160016e00000000bff03042d 1f0218c3b21f0218c3381f1a0e8ed57ed5020065010050000a000a170d000064000186a055 1f0218c3531f0218c355 1f0218c3f51f0218c33c0a1d570016f00a00000bff8262af 1f0218c3561f0218c3b8

Post-Insert Status Check

1f0218c3b71f0218c300030e01008195cf 1f0218c3f81f0218c3040a1d18001bf00000000fff80f6d6 1f0218c3591f0218c388

Status check, no temp basal running

1f0218c3b41f0218c310030e010002bdaa 1f0218c3f51f0218c3140a1d180184c000000743ff81f1fa 1f0218c3561f0218c3b8

1f0218c3a01f0218c334030e010080249c 1f0218c3e11f0218c3380a1d180187c000000767ff0003d2 1f0218c3421f0218c305