You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The scope of this issue is to create good reproducible scripts (ideally within crazyflie-link-cpp) that demonstrate the unreliable unicast communication. One idea could also be to add a new testing feature in the firmware of a counter: when a new message is received, a counter is increment and the counter value can be reset with a param, and read out with a logging variable. Then the counter value should be at least as high as the number of acks we receive (or higher, since CPX doesn't guaranty exactly-once semantics, but at-least-once semantics).
Ultimately, this script should lead to firmware and/or crazyflie-link-cpp fixes that avoid the issues described in the above discussion.
The text was updated successfully, but these errors were encountered:
Discussed in #247
The scope of this issue is to create good reproducible scripts (ideally within crazyflie-link-cpp) that demonstrate the unreliable unicast communication. One idea could also be to add a new testing feature in the firmware of a counter: when a new message is received, a counter is increment and the counter value can be reset with a param, and read out with a logging variable. Then the counter value should be at least as high as the number of acks we receive (or higher, since CPX doesn't guaranty exactly-once semantics, but at-least-once semantics).
Ultimately, this script should lead to firmware and/or crazyflie-link-cpp fixes that avoid the issues described in the above discussion.
The text was updated successfully, but these errors were encountered: