-
Notifications
You must be signed in to change notification settings - Fork 13.8k
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
New PX4/ROS Interface Support Thread #21120
Comments
Working with real hardware (pixhawk 6C), looks like the client is not automatically started... Does anybody know how start the microdds_client ? is it via mavlink? I am trying to do it but if I work with mavlink I can not simultaneously work with the xrce-dds birdge !! I tried to open the mavlink console in the QGroundControl, start the client, so I close the QGround and in the sequence I start the Agent. Following it I just have the following in the agent terminal: [1676258724.774920] info | TermiosAgentLinux.cpp | init | running... | fd: 3 Looks like there is not any ROS topic being published. How do you manage it to see the topics? |
Hi @ViniciusAbrao , the documentation is WIP but you can already have a taste of it. For example, your issue: https://github.com/PX4/PX4-user_guide/blob/d88460a7594d3930f621d645b461750a29d61cad/en/middleware/xrce_dds.md#xrce-dds-client-setup-for-flight-controllers But how are the pixhawk and the companion computer connected? You need a free serial link; therefore, if you are using TELEM1, you have to stop mavlink and then activate the microdds_client. You can do that changing the parameters:
to disable mavlink on TELEM1,
to start microdds_client on TELEM1 and Or you can put custom commands on the microSD. |
@bperseghetti thank you ... I was trying to connect via USB: In the MavlinkConsole: microdds_client start -t serial -d /dev/ttyACM0 -b 921600 In my laptop: ./MicroXRCEAgent serial --dev /dev/ttyACM0 -b 921600 So, the results are as I mentioned before, the client started, the agent started, but I can not see any Topic. I am going to test it with serial /dev/ttyS3 in raspberry pi and see the results using the TELEM2. |
@beniaminopozzan I have tested it in TELEM2, with raspberrypi, and it worked as expected. Thank you for your attention. XRCE_DDS_0_CFG = TELEM2 |
@ViniciusAbrao Did it not started autonomously once you set |
@beniaminopozzan I double checked it now as following: 1- I turned off the raspberry and the pixhawk and in the sequence turned on both again. I can see that it is already running, it means, it is not necessary to start it again. So maybe the reason is because I set XRCE_DDS_0_CFG = TELEM2 or because I already started it in the past (I do not know if it is related to automatically change some other parameter), the fact is that is not necessary to start it again. |
@ViniciusAbrao that is the expected behavior, |
@beniaminopozzan great!!! ... so maybe it would be interesting to mention that in the documentation section "XRCE-DDS Client Setup for Flight Controllers". |
Sory for my question but i'm newbee, how to pass this paramaters ? via parameters in qgroundcontrol ? Is it impossible to do this work via usb and ttyACM0 ? @beniaminopozzan if i understant if i put this parameter |
yes, you can do it in Qgroundcontrol
With Qground the pixhawk will be connected with laptop via USB, but as I explained you in the link bellow you need a companion computer:
yes, as we were talking in the comments here above. |
@beniaminopozzan I can see here: That would have an option to make with depth camera: make px4_sitl gazebo_iris_depth_camera But, here in the airframes, there is not the correspondent build target: https://github.com/PX4/PX4-Autopilot/tree/main/ROMFS/px4fmu_common/init.d-posix/airframes Also I can see there is the model, but without the gazebo's plugin implemented in the sdf for the RGBD camera: Is the gazebo simulation with depth camera in development or should I use a different make? |
@ViniciusAbrao could you open a new issue for this? Let's keep this thread for the micro XRCE-DDS interface :) |
Ok @beniaminopozzan , I did it here: |
Hey everyone I'm closing this issue, our docs have been merged thanks everyone for your help https://docs.px4.io/main/en/ros/ros2.html if you still have issues with those docs please open a new issue |
Hey folks please drop any issues or questions on this thread and we will try to address them, just be aware that this feature is still in beta until it's part of a stable release.
Link to WIP documentation PX4/PX4-user_guide#2259
The text was updated successfully, but these errors were encountered: