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
After some testing with the default application, we've seen that everything is ok.
But, due to one of our use cases, we found that master is not able to communicate with a considerable amount of anchors when there is a hard NLOS situation (therefore, anchors are unusable due to lack of sync signal). After reviewing the source code, we found there is an option to activate the CCP_RELAY_NODE in the anchors firmware to extend the synchronization.
We found that yellow light / blue light are properly blinking when the RELAY is activated in those anchors, but we can not see any ranges on the tag with anchors when the master is not in tag's range.
What parameters are we missing to configure? We found that rtdoa_node is also using RELAY but we are not sure which parameters are relevant.
The text was updated successfully, but these errors were encountered:
After some testing with the default application, we've seen that everything is ok.
But, due to one of our use cases, we found that master is not able to communicate with a considerable amount of anchors when there is a hard NLOS situation (therefore, anchors are unusable due to lack of sync signal). After reviewing the source code, we found there is an option to activate the CCP_RELAY_NODE in the anchors firmware to extend the synchronization.
We found that yellow light / blue light are properly blinking when the RELAY is activated in those anchors, but we can not see any ranges on the tag with anchors when the master is not in tag's range.
What parameters are we missing to configure? We found that rtdoa_node is also using RELAY but we are not sure which parameters are relevant.
The text was updated successfully, but these errors were encountered: