Show connection details

[ajayyy]

Data per second - calculated
Time of last packet - calculated
Packet loss - calculated
Other RSSI data - from RSSI packets

In sidebar

[sebastiengrd]

DOD:

• Create another class - DataProcessor
• This class takes the data and parse it and logs it
• The UI uses dataProcessor to create the update the tables
• The UI uses dataProcessor to create the graphs
• There is only one dataProcessor for all input
• All the telemetry data will be saved in dataHandeler - even the RSSI stuff
• The simulation should work with this new dataProcessor
• Determine if it is possible for RSSI and normal data to get mixed into one
• Fix WebView and google earth to use new config setup
• Allow browsing through history of RSSI without it being directly attached to a real sent data value

Moving these to separate issues:

- [ ] Allow RSSI data to be used in graphs Moved to #50
- [ ] There is one log file for each input + one main log file with just the raw bytes to be used in simulation mode (3 log files per connection) Moved to #51
- [ ] Enable RSSI logging mode when button pressed and connected over serial Moved to #52
- [ ] Add calculated connection info outside of just RSSI data (Maybe not needed?)

[ajayyy]

Info below is not needed, after testing, the radio will not do this kind of thing

RSSI parsing ideas:

For pre-protobuf:
realDaRSSI:saljadskl\ntamorerealdata\n

cut off the first part by searching for RSSI, potentially store for later. Add to the next packet. Since it always is looking for packets up to the next newline character, it should be fine.

For protobuf:
Read first bit and treat that as a anunber of bits of the packet. After recieving each byte, check if the last bytes are equal to "RSSI:", if so, keep going to the newline character instead and ignore the first bytes.
Advantage: this will work with protobuf data that has rssi data in the middle