-
Notifications
You must be signed in to change notification settings - Fork 46
Pod Lot and TID numbers
Some more background info from @itsmojo on Slack, https://omniaps.slack.com/archives/C0B2X08AW/p1506852654000024
@yeagerm, the leading L and leading T that are sometimes used in front of the Lot and TID values are just a formatting thing that Insulet probably created so these values can be more easily reported and tracked as they are not anywhere in the pod firmware. Both the Lot and TID are 4-byte values stored in pod flash at manufacturing time and given to the PDM during pod pairing. We use TID to refer to this value since this is what the PDM uses in alarm reports for this value, but it doesn’t seem that the T in the name would correspond to anything having to do with the Transmitter of the pod when you see how this value is actually used. These TID values do correspond to the small numbers print next to the Lot # on the side of each pod, but we have seen cases where this wasn’t actually the case (perhaps a manufacturing glitch?). The TID is completely different than the 4-byte value used for low level packet identification that we called pod_address_1 and pod_address_2 in our packet traces that the pod actually receives from the PDM it gets bound to. These “pod addresses” are actually programmed into the S08 chip on both the pod and the PDM and so they are involved with the actual packet communication. Sorry for the misleading names, but the TID is just a unique ID that is stored in each pod and reported to the PDM while the “pod address” is something generated by the PDM for each new pod being paired with it.