I use the Pixhawk cube SBUS out port to control an IR camera. The problem I got is that now we have to use the mini carrier board and not the standard one. This one is not coming with an SBUS port as the standard one.
I am trying to configure the TELEMETRY 2 Port in the the mini carrier board as SBUS servo out.
I have set:
SERIAL2_PROTOCOL = 15
BRD_SBUS_OUT = 1
The way I wired the port was:
Sbus signal to Telemetry 2 TX
Sbus Ground to Telemetry 2 Ground
Now I cannot make it work even with the big carrier board. We have a custom app with switches on the screen. When I push the buttons on the screen I can see on Mission Planer Servo output channels 1 to 5 go low and high, but I am not able to have the SBUS output to work and I could do it with previous versions of Ardupilot and the big carrier board. I dont know if I am missing any step.
For the big carrier board, to turn on the SBUSo what I did:
BRD_SBUS_OUT = 1
Is there anything else I should do? Is 50 hz the correct frequency?
The frame rate should not impact whether data is sent/received. Faster frame rates provide faster updates to the connected servos, but 50Hz is likely fine unless you’re trying to manage some sort of fast control loop.
Check your wiring. Ensure you have power to the servo(s).
Wait a minute…you’re connecting SBus Out to RCIN?!
That’s incredibly backwards logic, and I think you’re seeing differing behavior because there have been changes to prevent/disallow conflicts between multiple RC sources.
Are you just doing this for testing, or are you actually expecting to fly with this bizarre config?
NO!! I did that just for testing, and actually it worked. I just wanted to read the output of the SBUSo port to make sure it was working fine, so i though I could use another flight controller to test, or even plug it in the RCin port of the same cube, and it worked.
I updated the firmware before trying again. Maybe the changes you mentioned in the new firmware are the reason. How could I make it work?
If I plug the SBUSo port to the RC in (for testing) I can see the channels moving, however when I try to use TELEMETRY2 port I am not getting anything.
Digging this topic up, same problems, using a Matek H743. I have a motor I can control independently from a raw SBUS feed from a receiver. When I hook up to Ardupilot as described above, I cannot get the motor to move.
Tried flashing with bdshot firmware, no effect.
Checking some other ideas not discussed here:
-I’m using the Motor Test from mission planner to validate results
-Is SBUS mutually exclusive with existing motors? In my motor tests I have an existing drone connected additionally over SBUS to my test motor. I expect the channel 1 signal to move the motor, as it does indendently from my transmitter.
-My SERVO_BLH parameters are set up with dshot / BLHeli32, I expect this to not conflict with SBUS signal.
I also have the hardware signal inverter recommended on the wiki. Played with software settings toggling INVERT TX to no effect.
I did that just for testing, and actually it worked. I just wanted to read the output of the SBUSo port to make sure it was working fine, so i though I could use another flight controller to test, or even plug it in the RCin port of the same cube, and it worked.