Swiwin Turbines
07-20-2022, 11:42 PM
#226
Junior Member
Futaba SBUS2 telemetry issue continued
Hi guys,, sorry to drag this thread back to the SBUS2/Telemetry/throttle topic,, but!!!!
I'm installing a SW140b into a model with a BoomaRC Smoothflite16,, this uses 2X Futaba 7008 RX's for redundancy...
The problem: if you run a throttle cable from the Smoothflite16 to the PPM port, you get throttle input working fine, if you turn off the Tx, the Smoothflite16 sends a failsafe signal to the ecu to say stop, that's fine. Now you plug in your cable from the telemetry port to SBUS2 port, the telemetry works fine, but the engine has (as we know) a built in SBUS decoder, and picks out the throttle channel data streaming out of the SBUS2 port on the Rx, which over-rides the signal coming in from the PPM port. you still get throttle input, but now only from that one Rx, it stops the use of the Smoothflite16 Rx redundancy.. you are not supposed to use failsafe on the Tx, as apparently that can cause "jitters" to the Smoothflite16... so now, if I turn the Tx off, the engine won't stop, it just "Holds" idle... (by our regulations, it must stop).
Is there a way to stop the ECU from looking at the SBUS data stream for throttle input, while still streaming out the telemetry data??? OR preferencing PPM input over SBUS2 input?
I tried the SBUS Thr channel setting, hoping you could disable it,, but all you can do is select another channel...
I can't be the only one using a Swiwin with a Smoothflite16/26 or Powerbox etc etc????
Has anyone worked this one out???
Cheers
Bob Flint
I'm installing a SW140b into a model with a BoomaRC Smoothflite16,, this uses 2X Futaba 7008 RX's for redundancy...
The problem: if you run a throttle cable from the Smoothflite16 to the PPM port, you get throttle input working fine, if you turn off the Tx, the Smoothflite16 sends a failsafe signal to the ecu to say stop, that's fine. Now you plug in your cable from the telemetry port to SBUS2 port, the telemetry works fine, but the engine has (as we know) a built in SBUS decoder, and picks out the throttle channel data streaming out of the SBUS2 port on the Rx, which over-rides the signal coming in from the PPM port. you still get throttle input, but now only from that one Rx, it stops the use of the Smoothflite16 Rx redundancy.. you are not supposed to use failsafe on the Tx, as apparently that can cause "jitters" to the Smoothflite16... so now, if I turn the Tx off, the engine won't stop, it just "Holds" idle... (by our regulations, it must stop).
Is there a way to stop the ECU from looking at the SBUS data stream for throttle input, while still streaming out the telemetry data??? OR preferencing PPM input over SBUS2 input?
I tried the SBUS Thr channel setting, hoping you could disable it,, but all you can do is select another channel...
I can't be the only one using a Swiwin with a Smoothflite16/26 or Powerbox etc etc????
Has anyone worked this one out???
Cheers
Bob Flint
07-21-2022, 04:40 PM
#227
Originally Posted by BobFlint
Hi guys,, sorry to drag this thread back to the SBUS2/Telemetry/throttle topic,, but!!!!
I'm installing a SW140b into a model with a BoomaRC Smoothflite16,, this uses 2X Futaba 7008 RX's for redundancy...
The problem: if you run a throttle cable from the Smoothflite16 to the PPM port, you get throttle input working fine, if you turn off the Tx, the Smoothflite16 sends a failsafe signal to the ecu to say stop, that's fine. Now you plug in your cable from the telemetry port to SBUS2 port, the telemetry works fine, but the engine has (as we know) a built in SBUS decoder, and picks out the throttle channel data streaming out of the SBUS2 port on the Rx, which over-rides the signal coming in from the PPM port. you still get throttle input, but now only from that one Rx, it stops the use of the Smoothflite16 Rx redundancy.. you are not supposed to use failsafe on the Tx, as apparently that can cause "jitters" to the Smoothflite16... so now, if I turn the Tx off, the engine won't stop, it just "Holds" idle... (by our regulations, it must stop).
Is there a way to stop the ECU from looking at the SBUS data stream for throttle input, while still streaming out the telemetry data??? OR preferencing PPM input over SBUS2 input?
I tried the SBUS Thr channel setting, hoping you could disable it,, but all you can do is select another channel...
I can't be the only one using a Swiwin with a Smoothflite16/26 or Powerbox etc etc????
Has anyone worked this one out???
Cheers
Bob Flint
I'm installing a SW140b into a model with a BoomaRC Smoothflite16,, this uses 2X Futaba 7008 RX's for redundancy...
The problem: if you run a throttle cable from the Smoothflite16 to the PPM port, you get throttle input working fine, if you turn off the Tx, the Smoothflite16 sends a failsafe signal to the ecu to say stop, that's fine. Now you plug in your cable from the telemetry port to SBUS2 port, the telemetry works fine, but the engine has (as we know) a built in SBUS decoder, and picks out the throttle channel data streaming out of the SBUS2 port on the Rx, which over-rides the signal coming in from the PPM port. you still get throttle input, but now only from that one Rx, it stops the use of the Smoothflite16 Rx redundancy.. you are not supposed to use failsafe on the Tx, as apparently that can cause "jitters" to the Smoothflite16... so now, if I turn the Tx off, the engine won't stop, it just "Holds" idle... (by our regulations, it must stop).
Is there a way to stop the ECU from looking at the SBUS data stream for throttle input, while still streaming out the telemetry data??? OR preferencing PPM input over SBUS2 input?
I tried the SBUS Thr channel setting, hoping you could disable it,, but all you can do is select another channel...
I can't be the only one using a Swiwin with a Smoothflite16/26 or Powerbox etc etc????
Has anyone worked this one out???
Cheers
Bob Flint
07-21-2022, 04:50 PM
#228
Junior Member
Originally Posted by more
You have to choose between redundancy(by PPM port from SF16) or telemetry(by S.Bus2 port from one receiver).
I’d love it, if in an upcoming firmware update, that you could turn the (SBUS) Thr CH parameter to “invalid” just like the SBUS Aux CH parameter,, that way you could run throttle into the PPM port from your powerbox/Smoothflite and still have telemetry flowing out of ECU and into SBUS2 port, WITHOUT it picking off Throttle Channel data…
Futaba Telemetry…. It never ceases to trip me up,,, one way or another….
