Posts made by Zachary Lowell 0

@all - you can just change the SYS_ID of each drone and this should solve the port confliction.

@tomverstappen I am unable to recreate the issue with a starling running 1.5.0 - the output from voxl-vision-hub shows the relative coordinate frame from the tag relative to the camera and was able to get the drone to offset correctly.

Are there any logs you can paste in here or video?

Hello All - I will be trying to recraete this issue in the coming days - will keep you all posted.

Detections is pertinent to voxl-tflite-server and onboard computer vision on yolo, NOT on april tags.

@taiwohazeez I am not fully convinced you are running the right command still

Running voxl-inspect-tag shoudl show the following headers:

ID | XYZ | RPY | SIZE_M | CAM

As shown in the code below:
printf("\n"); printf("id:%3d name: %s\n", d.id, d.name); printf("XYZ: %6.2f %6.2f %6.2f \n", (double)d.T_tag_wrt_cam[0], (double)d.T_tag_wrt_cam[1], (double)d.T_tag_wrt_cam[2]); printf("RPY: %6.1f %6.1f %6.1f \n", (double)roll, (double)pitch, (double)yaw); printf("size_m: %4.2f latency_ms: %6.2f\n", (double)d.size_m, latency_ms); printf("cam: %s type: %s\n", d.cam, pipe_tag_location_type_to_string(d.loc_type)); printf("\n");

https://gitlab.com/voxl-public/voxl-sdk/services/voxl-tag-detector/-/blob/dev/clients/voxl-inspect-tags.c?ref_type=heads

Just run voxl-inspect-tags and that will output the right data.
Zach

Class confidence and detection confidence are pertinent towards voxl tflite server not voxl-tag-detector - are you sure this is the right output?

Hi @taiwohazeez - can you paste the output? Usually you get NANS or unknown when the locations.txt file isnt filled out meaning the tag detector service is referencing an empty file. Once you paste the output of voxl-inspect-detections I will be able to give you better guidance.

Thanks!
Zach

@Evan-Hertafeld said in Using MPA within voxl-docker-mavsdk-cpp:

libmodal_pipe

@Evan-Hertafeld @Jetson-Nano

You need to share all those files via a volume mount alongside with the /run/mpa directory to allow docker to probe the data and grab from an MPA pipe.

so in your docker run something like -v /usr/include/modal_start_stop.h:/usr/include/modal_start_stop.h needs to be done - the other option is you just download the actual MPA debian inside your docker image and call it a day - then you will have all the necessary headers, libs, binaries, and you just need to share /run/mpa as a volume to access the data.

Zach

@Jetson-Nano you could just use the CPP mavsdk instance to grab the TOF data from a MPA pipe and then leverage that to do your controls via mavsdk (I am assuming just offboard movement). You can connect over port 14551 just ensure you have localhost comms set to true in voxl-vision-hub.

@nikolahm is your drone PID tuned? How are you flying in position mode? GPS based flight, VIO based flight, etc. What is the environment you are testing in, can you paste a log in here please?

Hi @GlennTee you need to do a git submodule update --init --recursive on the voxl mpa ros2 code base to pull in px4 ros msgs

Zach

You need to push the install folder as thats where the executables live in ros2 once you run colcon build. src folder is just the code you wrote with zero executables after colcon build is run.

@tahawaru said in How to build-compile FOXY ROS2 packages and nodes for RB5:

pushing your docker instance to the voxl2, then deploying the docker container, and running ros2 run command inside the docker container correct?

I build my docker container on the voxl2 and then run everything inside. I am unsure I am following what you are doing. If its easiest, just install docker on your voxl2, then build your container on there and call it a day.

The other option is to run on disk outside of a docker instance. The voxl2 supports ros2 foxy natively on disk. To install this you can just do apt-get install voxl-ros2-foxy - lmk if that helps.

@claw said in VOXL2 ROS2 Starling Code Inconsistencies:

@Zachary-Lowell-0 Thank you for your help and guidance. Is there a way to get the status information like battery voltage using Python?

Reply

@claw yes you can follow this post to get battery over the DDS: https://forum.modalai.com/topic/4353/voxl2-px4-ros2-mpa-to-ros2-for-battery-voltage-problems/12?_=1745355297145

Did you ever install voxl-ros2-foxy?

You should be doing cross compilation for things like this - aka on your computer running voxl-docker -i qrb5165-emulator and then building the debian and flashing to the voxl2.

So what I currently do to build is:

1. clone mpa to ros2 on your parent computer
2. cd into repository
3. run voxl-docker -i qrb5165-emulator:1.5
4. run ./install_build_deps.sh qrb5165 dev
5. run ./build.sh qrb5165
6. run ./make_package.sh

Push via adb or scp the deb from parent computer to voxl2 and then unpackage the deb and source the right directory.

LMK if that helps at all - if you need to install nlohmann json btw you should be doing it via voxl-configure-mpa-to-ros2

Zach

@tahawaru said in How to build-compile FOXY ROS2 packages and nodes for RB5:

_find_and_load_unlocked

to confirm @tahawaru you are pushing your docker instance to the voxl2, then deploying the docker container, and running ros2 run command inside the docker container correct? Prior to running the ros2 command in the docker instance you are sourcing the right packages? Usually the rosidl typesupport error occurs because you have not build the right package and if you have you never sourced the right directory - so in your case its necessary to run source /opt/ros/foxy/setup.bash (if you installed px4 msgs via apt-get) if you build them directly from the colcon env then you need to source the directory you built those messages in!

LMK if this helps.
Zach

@GlennTee have you sourced the right directories? If you run source /opt/ros/foxy/mpa_to_ros/install/setup.bash that should tell your package manager that the px4 messages type exists. I also notice you are running this on your local machine - have you install the necessary packages there? If you instantiate the voxl-cross or qrb5165 emulator image and then use vscode inside the docker then you should be able to see the px4 messages just fine.

LMK if that helps!
Zach

@GlennTee one step ahead of you!

https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-mpa-to-ros2/-/blob/dev/colcon_ws/src/voxl_mpa_to_ros2/src/interfaces/tag_interface.cpp?ref_type=heads

Going to be rleased on the next sdk release - if you want it now, feel free to build and install the package.

Also @GlennTee build this branch of px4 and then flash onto your voxl2 - it exposes battery_status over the uorb topic through the dds bridge, so now when you run ros2 topic list you still see /fmu/out/battery_status: https://github.com/modalai/px4-firmware/tree/zach/battery_status_ros2

This is also a PR currently into voxl-dev branch of PX4 so most likely will be a feautre of the next release.

Zach