-
Notifications
You must be signed in to change notification settings - Fork 46
Message sequences
This page lists the messages exchanged for various operations. While the raw traces show the packets, this page condenses that down to show the high-level operations that can be obscured by the details of packet retransmissions and continuations.
The numbers below are the mtype and mlength.
0704 to pod, 0115 response: pairing, config.
0313 to pod, 011b response: config, config.
190a to pod, 1d03 response: command, status. The pod address is now used, message numbering restarts at 2.
190a to pod, 1d03 response: command, status.
1a0e/170d to pod, 1d44 response: command, status.
190a to pod, 1d05 response.
1a22(or 1a12)/0613 to pod, 1d16 response.
? to pod, 1d16 response.
1a03/170d to pod, 1d57 response.
The (?) message to the pod above was missing from 4 separate traces. The message sequence number show there should have been a message 12. It's unclear if the message got lost in the tracing (which occasionally happens) or if the pod sends a response without a request at this point in the sequence.
0e01 to pod, 1d18 response: status request, config.
1a0e/170d to pod, 1d58 response.
1a0e/160e to pod, 1d28 response.
1f05 to pod, 1e28 response.
The above are based on the traces in Pairing 02, Pairing 03, Pod setup with known Lot and TID and Wedding Priming and Deploying New Pod.
0e01 to pod, 1d18 response: status request, config.
1f05 to pod, 1d08 response.
0e01 (arg 1) to pod, 0213 response: status request, config 02.
0e01 (arg 46) to pod, 027c response: status request, config 02.
0e01 (arg 50) to pod, 02cb response: status request, config 02.
0e01 (arg 51) to pod, 02cb response: status request, config 02.
1c04 to pod, 1d0f response.
This operation sends multiple status (0e) requests to the pod and gets large responses back. For some reason, these request/responses don't increment the message sequence numbers but reuse 13/14.