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
I have never tried the current implementation, but I can imagine some Problems with it:
RSSI value seems a bit inaccurate to precisely track Drone position
not enough data to determine the passthrough Direction of a gate.
This, I would love to hear some feedback on the following idea:
Put one antenna before and another after the Gate.
Ideally, when the RSSI values are in the same region the drone should be pretty much in between the two antennas.
Also, using the history of the delta the passthrough direction can be determined.
My questions to anyone who has experience with Chorus and the used method in general:
Would there be any precision benefit from my solution?
Would my solution make it possible to track the direction?
Are those benefits worth the added hardware?
How extensible is the current implementation? Is the UI and higher level logic encapsulated from the RSSI calculation, so that my suggestions could easily be added in?
The text was updated successfully, but these errors were encountered:
I have never tried the current implementation, but I can imagine some Problems with it:
This, I would love to hear some feedback on the following idea:
Put one antenna before and another after the Gate.
Ideally, when the RSSI values are in the same region the drone should be pretty much in between the two antennas.
Also, using the history of the delta the passthrough direction can be determined.
My questions to anyone who has experience with Chorus and the used method in general:
The text was updated successfully, but these errors were encountered: