Status Packets

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

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