Hi @Riley-Dove ,

Want to try to do a screen share tomorrow AM? I'll send an email to what's registered on this account.

Some of the errors looked like config file parsing, but the first one was truncated a bit.

If the device is in the failed currently, and you don't mind, you can throw the output of systemctl status voxl-vision-px4 -l here in preps.

Thanks, we'll figure out what's going on!

@Chad-Sweet
This works, thanks. When will this be fixed?

I think you mean you would prefer that VOXL supports PCA9865 natively.

We have an I/O library ready to go, libvoxl_io. voxl-i2c is an application that is an example of using libvoxl_io for i2c commands.

One would need to implement the PCA9865 i2c protocol using libvoxl_io to control that part externally from VOXL.

As mentioned previously, Flight Core has native PWM support if you were to send over MAVLink

Yes, I tried apparently master and v0.68 of the code are different while in master is not hardcode the udp port. For v0.68 it is hardcode. So I assumed my version is hardcode because nothing seem to change.

Do I need to delete my voxl-vision-px4? To install a new custom version?

@Aldo-Castro-Freire Great to hear!

@Ruijie-Geng Yes, you certainly can. However, using WIFI usually results in local IP addresses which are not routable over the Internet. For someone to connect to your WIFI video stream from the Internet you will need to make your IP address visible to the Internet. There are different ways to accomplish this but we usually use a VPN for this purpose. We have some documentation on VPN use with Voxl here: https://docs.modalai.com/voxl-vpn/

We offer an add-on board that exposes USB2.0 but not 3.0 as the add-on connector is a 2.0 port.

VOXL has the option to be used as a USB3.0 HOST port using a custom cable, but it's not a cable that is easily found... it's somewhat of a fringe setup --> this cable pinout using this port, here's some more info

@modaltb I don't required VIO for the whole flight rn. I just wanted to test the landing. I would assume for my flights they all would be gps enable. But what gps lacks is precision on landing mostly, so I have been wanting to test how reliable is landing on top of Apriltag because we have some landing platforms and we need precision.
I saw the the apriltag video and it didn't seem I needed to setup the precision landing mode, it just triggers the VIO

There shouldn't be a conflict, main 'trick' is to have UDP ports setup --> https://docs.modalai.com/mavros/#configure-voxl-vision-px4

Hey @gus ,

We have not performed comprehensive environmental testing, but expect this to perform similar to other consumer-grade electronics.

VOXL/VOXL-Flight (boards with Snapdragon 820) 0-55C Ambient (validated by test), Non-VOXL stuff (e.g. Flight Core standalone), 0-70C max operating by design.

Thanks!

Hi @Aldo-Castro-Freire ,

Local frame is centered wherever the drone was when it boots up aligned with wherever the drone was facing when it booted up.

Body frame is centered at the drone's center of mass and points XYZ->forward right down.

Looks like we used the 7" one here

@Alex-Kushleyev I see. It works and I was able to get the calibration files so it's all good!

Thanks!

The ipk is available here now : http://voxl-packages.modalai.com/stable/voxl-hal3-tof-cam-ros_0.0.5.ipk - you should be able to use the launch file to choose between two modes (5=short range and 9=long range) and fps, which are listed in the launch file.

WOW! Thanks @Lynn-Koudsi for the help, when we setup the forum this is the kind of interaction we were hoping for, just awesome!!

Sorry for the setup and 'wonkyness' right now, we've been somewhat caught with getting pre-release software out there without all the setup/docs lined up.... so we're doing a little catchup it seems.

@Liping there until we have our docs updated, if this is working, I'd say this is a good approach!

Thank you both for the details, we'll relay this through the team.

This is how mavros behaves going from PX4 coordinate frame to ROS coordinate frame when viewed in RViz. We just supply examples of how to use mavros on our platform with open code for people to change and use as they see fit. If you have suggestions on how this code might be improved, we would happily accept a merge request.