Hello.
I found bug on the mission planner log viewer.
I tried to analyze weird action on copter with companion computer, and found “hold” in battery failsafe parameter description in mission planner log viewer.
params in log viewer
params actual
Rover does “Hold” for some failsafe actions.
I see in your screenshots the critical voltage is different - could the actual value have been changed since the log was generated?
Can you upload the log somewhere and add the link here?
EDIT:
wait…
Are you only worried about the Hold option?
In MissionPlanner, press Control F then click on “Param gen” (near top left, 7 down)
Or you can do Setup / Advanced / Param gen
The log I viewed was from the hexacopter, not the Rover. I did not operate or record the Rover’s log.
However, I experimented with Rover(Boat) SITL yesterday as I was programming some mission planner plugins.
Perhaps there was some internal confusion that caused the error.
is there still no clear explanation of this situation?
it was not my mistake, I believe.
the hexacopter log folder was sperate and can’t be confused with other folders. because I didn’t save or play ardurover’s log at all.
I just used Rover(Boat) SITL before using log viewer.
If it is algorithm’s problem, I want this problem to be fixed because I should connect ArduRover(Boat) and VTOL simultaneously to mission planner, on south pacific for important mission.
Thank you for notifying me “Hold” is Rover’s parameter. it helped me a lot.