@aashry Follow this link: https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-mpa-to-ros. Catkin_ws -> src -> msg and you will find AiDetection.msg, which you can use to build a ros custom message package (ROS has a tutorial on it I believe). You can do that in whatever workspace you are working in in your docker container. Once that is built and you source devel/setup.bash, you should be able to echo the topic and if you want to subscribe to it in a node you will need to import the message header similarly to any other message type
Best posts made by jonathankampia
-
RE: how to access tflite_data published by voxl_mpa_to_ros from local machine?
Latest posts made by jonathankampia
-
Voxl flight - cannot run voxl-configure-mpa after flashing new system image 0.9.5, 0.9.0, etc.
Hi,
When i try to run voxl-configure-mpa --factory-reset after flashing a new image onto the VOXL flight board, I get the error: "Cannot run factory reset without saved factory mode!". Obviously, this implies some config file is missing, but I've never had this problem before, especially after a fresh system image flash. So far I have tried 0.9.5, 0.9, and 3.8.0, all with the same result. Additionally, no services can be started (voxl-configure-vision-px4 configures the service but does not actually start it, and systemctl start voxl-vision-px4 does nothing). The reason I'm using a VOXL flight board instead of the VOXL + flight core v2 combo is because the flight core v2 on this drone got fried somehow, and also the v2 doesn't support 1.12.3 firmware, and 1.13 firmware seems to be incompatible with several devices (lightware lidar, pixycam).
-
RE: how to access tflite_data published by voxl_mpa_to_ros from local machine?
@aashry Follow this link: https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-mpa-to-ros. Catkin_ws -> src -> msg and you will find AiDetection.msg, which you can use to build a ros custom message package (ROS has a tutorial on it I believe). You can do that in whatever workspace you are working in in your docker container. Once that is built and you source devel/setup.bash, you should be able to echo the topic and if you want to subscribe to it in a node you will need to import the message header similarly to any other message type
-
VOXL - Issues with docker load storage space
Hi, we have one docker image onboard our drone that is taking up about 2.5 GB, and /data is about 45% full. This means there is more than enough space to hold more docker images, but when we try to docker load new ones or even commit changes to the one that's already on there we get an error along the lines of "no space left on device". Is there some memory somewhere else that docker needs to access in order to create / commit changes to new images that I need to clear, and if so, where is it? Most documentation on regular docker online doesn't help as the layout appears to be completely different.
-
RE: lightware i2c lidar - voxl m500 with flight core v2
@jonathankampia I would also like to mention this is hooked up to a flight core v2 on firmware version 1.13.2. One of my mentors said this might be the problem, as the previous firmware version we used with the original flight cores did not have this issue
-
RE: lightware i2c lidar - voxl m500 with flight core v2
@Eric-Katzfey So the parameter you mentioned contains the models of the lidar in QGC, and after selecting the correct model and looking at the i2c buses we figured out that for some reason you have to unplug and plug back in the lidar after you start up the drone. Then, it will appear as a device, and we can start it manually with lightware_laser_i2c start -X -b 2. Not sure why it's necessary to do this manually and it's pretty annoying, though.
-
lightware i2c lidar - voxl m500 with flight core v2
Hi,
Looking at the datasheet, it appears the external i2c connector on the flight core v2 is j14 (the 12 pin connector) with pins 6 and 7 being SDA and SCL respectively. Assuming I have that correct, I wired up a lightware LW20/C lidar and connected it to the m500, but nothing appears to have changed in the mavros topics the drone outputs. Of course there's some possibility of a loose / faulty connection / bad soldering, but I checked and there is properly 3.3V across the J14 power pins, so I can assume the SDA and SCL pins are also properly connected. Is there any additional setup I need to do to get the lidar working? From reading other posts about i2c setup on the voxl, it seemed like on startup the lidar should be recognized and drivers should be started.
Thanks!
-
m500 local positioning problems
Hi,
The gps module on the surface appears to be working okay (drone has GPS lock, gps is reporting data to correct mavros topics etc). However, when I actually observe that data, some component of the drone is feeding in absolute garbage. /mavros/local_position/pose, which to my understanding references the GPS and a few other components on the drone to form a composite local position, has major drift in the x and y directions (while sitting completely still on the ground, the topic will register the drone moving at about half a meter per second) and the z direction reads in as the drone being 800 meters below 0.
I have performed all of the calibrations I could find on QGC, like the compass and the accelerometer, and before that reset the drone to factory settings and configured everything with the command it prompts you to run upon reflashing the board.
Do you have any ideas what the problem might be? I have tried swapping out multiple GPS modules and this problem is consistent across several m500s we have right now.
-
missing camera config ID - VOXL board on Seeker drone
Hi, I just reflashed the VOXL board on a Seeker development drone to 0.9.5 or whatever the exact version of the latest release was. All the other services seem to run / enable
correctly, except voxl-camera-server throws up errors when I try to run and configure it.Specifically, voxl-configure-cameras returns:
"missing camera config ID" and
voxl-camera-server returns:
"WARNING Failed to set priority, errno = 1
This may be because the FIFO scheduler is not available when running in a console.
It should work properly when run as a systemd background process on boot.
WARNING: failed to set scheduler"As far as I know all the hardware on the drone should be functional, and this is right after a system image flash. Am I forgetting some part of the setup?
Thanks
-Jonathan -
VOXL 2 tflite & mpa to ROS topic issues
So tflite works perfectly fine, and outputs correctly to the tflite and tflite_data topics. However, the tflite_detections topic that appears after running mpa to ros is just empty and doesn't contain data while a simultaneous echo of tflite_data shows detections are in fact occurring.