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
For logfile analysis is a usual task to verify parametric setup between multiple flights. The current approach by manual comparing of parameters between multiple versions of firmware (Where parameters set is not the same) is somewhat time-consuming.
The good solution to that problem would be expanding the flight_review by parameter comparison tool.
It should work by one of those ways:
From currently opened log file select a compare tool from top.
Log browser should be opened (currently implemented)
select the other already uploaded log file to compare.
The another option
In the current existing log-browser implement the compare checkbox.
User select checkbox of multiple logs
clicks on the "compare logs" button.
In both cases, the table with different parameters should be displayed.
A nice option would be filtering of obviously different parameters, like battery calibration, RC mapping, status parameters, and sensor ids, or calibration.
Also would be nice if each parameter could be linked with the corresponding Description in Parameters Reference document.
The text was updated successfully, but these errors were encountered:
For logfile analysis is a usual task to verify parametric setup between multiple flights. The current approach by manual comparing of parameters between multiple versions of firmware (Where parameters set is not the same) is somewhat time-consuming.
The good solution to that problem would be expanding the flight_review by parameter comparison tool.
It should work by one of those ways:
The another option
In both cases, the table with different parameters should be displayed.
A nice option would be filtering of obviously different parameters, like battery calibration, RC mapping, status parameters, and sensor ids, or calibration.
Also would be nice if each parameter could be linked with the corresponding Description in Parameters Reference document.
The text was updated successfully, but these errors were encountered: