I'm pretty sure that I'm using the correct setup on the radio. It's the same one I use successfully on many other planes and helis with "simple" receivers.
The screenshot shows the setup. The most important thing is that throttle says "HOLD".
In my testing with spirit, I did the following:
- Took blades off
- Connected to spirit PC software
- Spin up heli
- Turned off the radio
This caused motor to stop. What I wanted was throttle hold (motor keeps running)
Then I tried a second experiment.
- Spin up heli
- Clicked "Set failsafe" in the spirit PC software
- Turned off radio
Now the motor keeps running. So the third experiment:
- Turn on radio
- Spin down motor
- Turn off radio
Now the motor spins up. Not what I want.
The spirit seems to be ignoring my failsafe settings on my radio in favor of what I chose when I clicked "Set Failsafe" in the spirit software. This is possible in SBUS because failsafe has a dedicated bit in the packet. From https://github.com/bolderflight/SBUS
Byte[0]: SBUS Header, 0x0F
Byte[1-22]: 16 servo channels, 11 bits per servo channel
Byte[23]:
Bit 7: digital channel 17 (0x80)
Bit 6: digital channel 18 (0x40)
Bit 5: frame lost (0x20)
Bit 4: failsafe activated (0x10) <----
Bit 0 - 3: n/a
Byte[24]: SBUS End Byte, 0x00
So it's possible to get all the digital channels (e.g. throttle hold) and still know that failsafe is activated. I'm wondering how the spirit logic handles this case and if there is a way to change it.
| Attachments: |
failsafe.jpg [ 236.8 KiB | Viewed 370 times ]
|
|