Hi,
after a upgrade of BlueOS and installing a new firmware on navigator, when I arming the Brov, I get this vocal message: Backup locations parameters are missing or zero…
Someone had the same issue? How I can solve it?
Thanks to everyone for the Help.
Hi @Framau -
The newest firmware versions set the magnetic compass declination based on the position in the world! To set this, adjust the autopilot parameters for ORIGIN_LAT and ORIGIN_LON to your approximate GPS location, only one or two decimals of precision are required (e.g. 22.3 N -118.32 W)
Thanks for your reply… I’ve tried to do do something like downloading the maps… but after 4 years using BR, was the first time that I heard this message!
I tried also to use cockpit instead qground but as you said, is a firmware problem…
The strange fact using cockpit instead aground is that with same controller, on qg everything works very well, with cockpit when I armed the veicle, vertical start to spin for their self… on cockpit there no way to calibrate joystick ( it’s a hand control)… Every new sw carry some problems… I wanna start to use cockpit, I set it everythings for bluos, also fight a little bit with tilt settings… but I cannot solve the controller problem. ( if I armed Brov in manual mode with unplugged joystick nothings happens, jut let plug in and rov got crazy, already try to use window’s calibration, but the joystick is ok)… for sure I hope that bluerobotics add a good tools like qg to calibrate every controller especially with dead band and expo)…
Hi @Framau -
Sorry for the issue!
Downloading maps in Cockpit for offline use is not yet possible…
I don’t suspect a firmware problem. No calibration is necessary with joysticks in Cockpit, this is intentional! In the joystick page in Cockpit, does the position of the joysticks match the reality? I would suspect that your controller is damaged, and maybe you’ve been getting by thanks to the calibration functions in QGC…
Seems no… also checking with windows calibration… all vertical start to run, but running in the same direction… tomorrow I will take a screenshot for you!
I really appreciate your help, thanks!
Hi!
Thanks to your suggestion, I’v solved the location parameters problem, on both app (ground and cockpit)…
As you see on attached images, on both app, joystick seem very good, no axis with strange feedback, but on cockpit if I armed the BR, vertical start to spin at 20-30% with no reason…
I believe, that add a good system to calibrate joystick, like Qground control is mandatory. Especially to set for example dead band, decide if having full throttle in the center or not, exponential… too nice and useful settings on joystick are missing, especially for home mad hand control…
In my situation, I must use qground instead cockpit, because there is no way to calibrate joystick…
Hello Tony,
I tried this solution. I fully restarted the vehicle and now I am getting the following error.
I am not sure what I need to look after when checking the EK3_SRC parameters.
Also. I am not sure if this is related, but after operating the vehicle for some seconds, it automatically disarms. The only errors that show up are these ones.
Hi @Alex_UJI1 -
Those errors are normal for a fresh upgrade to ArduSub 4.5 which introduced location parameters used to set the compass magnetic declination, hence the errors you see. Setting ORIGIN_LAT and ORIGIN_LON parameters to the approximate geographic position of your system should resolve things! You can do this from QGC or BlueOS under Autopilot Parameters.
The vehicle automatically disarming seems unrelated. If this persists, and you’re using a Pixhawk, downgrade ArduSub to 4.1.2. Otherwise, please share autopilot .BIN logs and BlueOS system logs (from gear menu in lower left of BlueOS interface)
the solution no longer works for me either, it continues to give an error, even if lat and long are updated correctly.
Francesco Maurizio
| Tony White Applications Engineer
November 19 |
Hi @Alex_UJI1 -
Those errors are normal for a fresh upgrade to ArduSub 4.5 which introduced location parameters used to set the compass magnetic declination, hence the errors you see. Setting ORIGIN_LAT and ORIGIN_LON parameters to the approximate geographic position of your system should resolve things! You can do this from QGC or BlueOS under Autopilot Parameters.The vehicle automatically disarming seems unrelated. If this persists, and you’re using a Pixhawk, downgrade ArduSub to 4.1.2. Otherwise, please share autopilot .BIN logs and BlueOS system logs (from gear menu in lower left of BlueOS interface)
Hi @Framau -
Please share what you modified the values of ORIGIN_LAT and ORIGIN_LON parameters to be! Also confirm you are running the latest ArduSub
There is an open Issue about this where you can track progress, but it’s not currently something we’re working on.
Are your joystick axes still configured like in this image? And is that how they were configured by default, or did you set them that way?
In the image the Z axis is set as -1 to 1 values, when it should be 0 to 1000. You also don’t have the R axis configured (it should be -1000 to 1000), without which you won’t have yaw (turning) control over your vehicle.
If that doesn’t resolve your issues then it makes more sense to continue the discussion in this thread.
