-
Notifications
You must be signed in to change notification settings - Fork 80
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement TDoA anchor protocol 2.0 #17
Comments
Proposed packet format: typedef struct rangePacket_s {
uint8_t type;
uint8_t seqs[NSLOTS]; // Packet id of the timestamps
uint8_t timestamps[NSLOTS][TS_TX_SIZE]; // Relevant time for anchors
uint16_t distances[NSLOTS];
} __attribute__((packed)) rangePacket_t; Assuming the current anchors is of ID anchor_id
|
ataffanel
added a commit
that referenced
this issue
Nov 29, 2017
ataffanel
added a commit
that referenced
this issue
Nov 29, 2017
ataffanel
added a commit
that referenced
this issue
Dec 4, 2017
ataffanel
added a commit
that referenced
this issue
Dec 5, 2017
ataffanel
added a commit
that referenced
this issue
Dec 5, 2017
It is now possible to set the anchor position while in TDoA2 mode
ataffanel
added a commit
that referenced
this issue
Dec 11, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The current TDoA protocol does not contain packet sequence number which makes it hard to verify TDoA integrity in case of lost packet on the tag side. A new TDoA protocol should then include packet sequence number.
Calculating the distance to other anchors and including it in the packet will also simplify a bit the tag implementation and could increase robustness to lost packet.
The text was updated successfully, but these errors were encountered: