Rover 4.7.1 Can't get "Ignore Throttle in Auto" to work

ArduRover Rover 4.7
1

Hi,

been trying to get my rover to ignore throttle failsafe during auto missions.

But despite setting FS_THR_ENABLE=2 I can not get it to work. The moment RC transmitter is being turned off, it goes into Hold mode.

Can anyone see what might be wrong in my parameters ?

Thanks

Best_Param_Oct2026.param (23.1 KB)

2

Set fs_action,0 ?

3

@dkemxr

Thanks.

But if I set FS_Action=0 then all failsafe actions will be disabled, won’t it?

…the idea is that only throttle value is ignored so RC can be turned off during AUTO.

4

@rmackay9

I did also notice in ArduRover 4.7.1 that the following statement doesn’t appear to be correct:

  • once the transmitter/receiver connection is restored, the user must use the transmitter’s mode switch to re-take control of the vehicle in Manual (or any other mode)

In my case I just turn on RC and rover appears to continue in Auto.

Can you please confirm / check ? …could be linked to the combination of FS settings I have. (i.e. HOLD rather than RTL or SMART_RTL)

5

Hi @Karl_S,

Any chance you could provide an onboard log? This will show us all kinds of information that will help with the diagnoses. In particular it could very well be an issue with the receiver’s built-in failsafe. If its changing the mode channel value sent to the autopilot that might explain why its switch to Hold mode.

6

Fair point.

Will download a .bin file shortly.

Thanks

7

The odd thing is that only channel 4 remains in neutral whilst RC is switched off. Yet that channel is not in use.

Inore_Throttle_input_issue
Inore_Throttle_input_issue1540Ă—862 252 KB

8

Depending on your transmitter and receiver, you need to set “no pulses” as the failsafe action, or probably bind with the channels in the desired positions. Some even allow you to specify channel positions.
You may have to trim throttle way down past it’s normal output before binding to get lower than the throttle failsafe level, then set the trim back to normal after that.

9

Yes, I am aware of that . But this rover was “of the shelf” and then heavily modified to suit my needs.

Besides, …I would have thought that if a channel is set to “DO_NOTHING”, this means exactly that.

But clearly that is not the case.

…my bad. :roll_eyes:

10

Possibly “DO_NOTHING” means dont change ??

11

Well, given all that,…is there a possible workaround ?

12

Thanks to everyone involved.

Have done more research on that RC and appears the failsafe settings can be changed,

Will try a few things and go from there.

13

Problem solved:

Turns out despite CH4=DO_NOTHING, the RC had a failsafe for CH4 set ex factory.This caused the issue.

After finding instructions online (and trying to make sense of the Chinese to English translation), I was able to set Channels 1-4 to a value below the failsafe threshold. → This fixed it.

Hint - “DO-NOTHING” in the settings doesn’t always mean that to the letter.