Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Override RC inputs topic #22

Closed
vooon opened this issue Jun 5, 2014 · 24 comments
Closed

Override RC inputs topic #22

vooon opened this issue Jun 5, 2014 · 24 comments

Comments

@vooon
Copy link
Member

vooon commented Jun 5, 2014

No description provided.

vooon added a commit that referenced this issue Jun 6, 2014
Topics:
* ~/rc/in -- FCU RC inputs in raw microseconds
* ~/rc/out -- FCU Servo outputs

Fix #17.
Partiall #22.
@vooon vooon added this to the Versoin 0.5.0 milestone Jun 7, 2014
vooon added a commit that referenced this issue Jun 14, 2014
@vooon
Copy link
Member Author

vooon commented Jun 14, 2014

Need some tests.

@vooon vooon closed this as completed Jun 14, 2014
@vooon vooon reopened this Jun 14, 2014
@vooon
Copy link
Member Author

vooon commented Jun 15, 2014

Tested. APM responds only to GCS sysid.

@vooon vooon closed this as completed Jun 15, 2014
@DasRegal
Copy link

Sorry for the stupid question - how to use it? And how set arm/disarm?

@vooon
Copy link
Member Author

vooon commented Jul 23, 2014

Arm/disarm via arming service, or using mavsafety (see it's --help).

RC override via it's topic, http://wiki.ros.org/mavros#rc_io

@DasRegal
Copy link

Service /mavros/cmd/arming unavailable.

I type
$ roslaunch px4.launch
$ rosrun mavros mavsafety arm
service [/mavros/cmd/arming] unavailable

$ rosservice list
/mavros/get_loggers
/mavros/param/get
/mavros/param/pull
/mavros/param/push
/mavros/param/set
/mavros/rc/override
/mavros/set_logger_level
/mavros/set_stream_rate
/rosout/get_loggers
/rosout/set_logger_level

@DasRegal
Copy link

I type
$ rosservice call /mavros/rc/override "{channels:[2000,0,0,0,0,0,0,0]}"
success: True

but

$ rostopic echo /mavros/rc/in
header:
seq: 3335
stamp:
secs: 1406647307
nsecs: 829219775
frame_id: ''
rssi: 0
channels: [0, 0, 0, 0, 0, 0, 0, 0]

@vooon
Copy link
Member Author

vooon commented Jul 29, 2014

Because #48, i blacklist command and waypoint plugins. Now i have pixhawk, but i want close previous issues before trying it.

Override should work, but maybe it requires arming or correct target ids.

@DasRegal
Copy link

But RC should work without arming. Or I'm wrong?

@vooon
Copy link
Member Author

vooon commented Jul 30, 2014

Does it work from GCS? APM for example silently drops override message not from GCS system id (parameter).

@tonybaltovski
Copy link
Contributor

Can the RC input be converted to a topic rather then a service?

@pmukherj
Copy link

pmukherj commented Jan 9, 2015

Quick question for @vooon on this! Do you know if there is a way to override just a few channels, while leaving the other channels under RC or autonomous control?
I have a gimbal I'd like to control from mavros (connected to the pixhawk PWM out), but don't really want to override the other RC outputs.
If the current plugin doesn't support single channel override, I'm thinking mavlink does and this plugin can be extended, I can look into that!

@tonybaltovski
Copy link
Contributor

@pmukherj If you publish 0 for the channel, it will give control back to the RC. Similarly, -1 for a channel means no change should be made to that channel. In order to send the -1, you need to send the maximum of the uint16_t which is 65535 (2^16 - 1). From what I understand, the pixhawk doesn't support rc override.

@pmukherj
Copy link

pmukherj commented Jan 9, 2015

Amazing! That's perfect.

@tonybaltovski
Copy link
Contributor

Are you using the RC override with the pixhawk?

@mhkabir
Copy link
Member

mhkabir commented Jan 9, 2015

This won't work. We don't handle RC override in PX4 stack.

@pmukherj
Copy link

pmukherj commented Jan 9, 2015

Yea, I noticed that conversation in the joystick plugin ticket. Boo!
For now, I may just hack my companion computer(Tk1 + odroid) to output the PWM into the gimbal. I have to stick with the px4 stack for testing the setpoint control.
Eventually though centralized method to control it all through the pixhawk will be awesome.

@mhkabir
Copy link
Member

mhkabir commented Jan 9, 2015

We can do it via the FMU auxiliary pins. I'm already working on getting the pins started up by default, as they are currently totally "dead"
Simple to add a handler and passthrough.

@LorenzMeier
Copy link
Member

They are already enabled. Check the rcS / firefly script for the logic how to load a mixer in there.

@pmukherj
Copy link

pmukherj commented Jan 9, 2015

My bad, I have the 3DR IRIS, so the gimbal connection is by default through the Aux out port (1 and 6 = roll and pitch of the gimbal). I was going to move them to the RC out so I can control it through mavros, but this would potentially work much cleaner.

@pmukherj
Copy link

pmukherj commented Jan 9, 2015

If this is easy to pass through, I can give this a test as well!
PS: I tested the RC on the APM stack. Works well, after the sysid change suggested here(#93). I'll make a note to add that to the wiki.

@vooon
Copy link
Member Author

vooon commented Jan 9, 2015

@pmukherj Look constant CHAN_RELEASE in http://docs.ros.org/indigo/api/mavros/html/msg/OverrideRCIn.html

But as mentioned by @mhkabir this message not supported by PX4.

@LorenzMeier it is possible to add messages for gimbal controller? Maybe it exist BGC with mavlink support?
I bought EvvGC and motors, but don't have working camera (camwrt stuck on video subsystem startup) and mounts for that. Also EvvGC seems dead, but it incredibly cheap...

nmichael pushed a commit to rislab/mavros that referenced this issue Mar 19, 2016
@bduva002
Copy link

This won't work. We don't handle RC override in PX4 stack.

Do you know if px4 support rc_channel_override yet ?

@fazlurnu
Copy link

fazlurnu commented Mar 4, 2020

This won't work. We don't handle RC override in PX4 stack.

Do you know if px4 support rc_channel_override yet ?

Yes, now you can use simply by publishing to mavros/rc/override topic

@W4li8
Copy link

W4li8 commented Jul 26, 2023

This still doesn't work on PX4, does it?
rostopic pub -r 10 /mavros/rc/override mavros_msgs/OverrideRCIn "{channels: [1789, 65535, 65535, 65535, 65535, 65535, 65535, 800, 900, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 65535]}"
yields
[ WARN] [1690398217.820133869]: RC override not supported by this FCU!
I see some stuff about this only working from GS but that doesn't seem to help

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

9 participants