PreArm: Hardware Safety Switch

Hi

I’m using a CubePilot Orange V4.5.7 and I’m getting the safety switch warning. I’ve tried disabling the parameters. Wondering what is causing the message

This is a new heavy rover setup so I have done the simple accel cal and large vehicle magcal. I’ve also done a number of power down / reboots etc

image

image

Many thanks
Michael

Either press the “Hardware safety switch” on the GPS unit or, if you do not have it, configure it correctly, changing the respective parameter.

I just went here: Correctly configure ArduPilot for your vehicles on your first attempt | MethodicConfigurator and asked the AI:

I use ardurover and do not have an hardware safety switch connected. What parameter should I change to disable it?

And got this:

How to disable hardware safety switch in ArduRover?

To disable the hardware safety switch in ArduRover, you need to modify the BRD_SAFETY_DEFLT parameter. This parameter controls the default state of the safety switch at startup. Setting it to 0 will disable the safety switch, meaning it will start in the unsafe state (solid) at startup. Here is how you can do it:

  1. Connect to your ArduRover using a ground control station like Mission Planner.
  2. Navigate to the Full Parameter List or Full Parameter Tree.
  3. Find the BRD_SAFETY_DEFLT parameter.
  4. Set its value to 0.
  5. Save the changes and reboot the system for the changes to take effect.

For more details, you can refer to the Complete Parameter List — Rover documentation.

Do you have that parameter ? I only have the ones I posted

I do not understand your question:

https://ardupilot.org/rover/docs/parameters-Rover-stable-V4.5.7.html#brd-safety-deflt-sets-default-state-of-the-safety-switch

https://ardupilot.org/rover/docs/parameters-Rover-stable-V4.5.7.html#brd-safetyoption-options-for-safety-button-behavior

What I am trying to say is If you look at all parameters in ardupilot can you see a parameter BRD_SAFETY_DEFLT ? Because I don’t have it . Is it possible the documentation is not current

Wierd I don’t have it

It’s a Cube Orange?
Set brd_safetyoption,0
I see you did that already.

Thanks all for your responses. Any further suggestions? I did a complete parameter reset and all the calibration stuff again and still have the issue.

Set log_disarm,1 Restart it and post a link to the log created.

Here’s the log - thanks

The parameter exists in that log. Not sure what’s going on with your connection to Mission Planner. I always recommend updating MP to the latest beta release (on the HELP tab). Maybe that will help.

Not sure what to tell you here. These are the parameters extracted from that file with Mission Planner. The parameters is there.

So, if you want to try something this parameter file has only 1 parameter in it and it will disable the safety switch. From Mission Planners Full Parameter list select “load from file” and choose it.
safety.param (20 Bytes)
It will do nothing else.

1 Like

Thanks I’ll try the beta and load from file . Is there a reset I can do ? I don’t mind wiping Mission Planner and ardupilot .

In the Full Parameter List hit the Reset to Default button. Then you may as well load V4.6.0-beta4 and see if that makes a difference.

I reinstalled mission planner and set parameters to default with 4.5.7 still no BRD_SAFETY_DEFLT

But I think its a software issue. BRD_TYPE was defaulted to 3 when I setup the CubeOrange and Mission Planner . But when I changed BRD_TYPE to 0 (Auto) refreshed parameters and wrote them , and then set BRD_TYPE from 0 back to 3 I get BRD_SAFETY_DEFLT and it perists after a number of reboots etc

Default setup BRD_TYPE 3 missing BRD_SAFETY_DEFL

Setting the board to BRD_TYPE 0 I get BRD_SAFETY_DEFLT

Then back to BRD_TYPE 3 we have BRD_SAFETY_DEFL and it sticks around after reboots

It’s a CubeOrange not a “+” version?
If it is download the .apj file from here and use Mission Planners “load custom firmware” to flash it. Reset to default before doing so.
You should not be manually changing that parameter.

yes its the orange not orange+ just tried and I got his

When loading

and i lost the BRD_SAFETY_DEFL ( I reset the parameters to default )

Huh. Well, perhaps it is actually a problem with the CubeOrange Rover firmware target.
Maybe @rmackay9 can take a look.

1 Like