ModalAI Forum

@SmittyHalibut That page may be outdated. You definitely can set a static IP on eth0, it is required for Microhard usage. For example voxl-modem uses the interfaces file here for setting a static IP: https://gitlab.com/voxl-public/utilities/voxl-modem/-/blob/master/config/interfaces It does require pulling down / up the interface on boot: https://gitlab.com/voxl-public/utilities/voxl-modem/-/blob/master/scripts/voxl-modem#L516 which may be a solution for @Sem-Andeweg

Oke, so it worked! The issue was this in the installation script it is described that there must be create a directory not the file in the /usr/local path which is called sbin ... but every time it will create a file instead of creating a directory. I manually created the directory as per script and then the script will easily install and copy its required files and the services will works properly. We have tested the function with Virtualhere, and they work perfectly! Now we encountered one extra problem, but I will go and start a new topic for this.

@Chad-Sweet Hi, the utility shows the same CPU usage if I add usr & sys.

For VIO use voxl-inspect-qvio For GPS use voxl-inspect-gps The source code for those is here

@amitga The only thing we use over the B2B on our add-on boards is USB 2.0 and some GPIO. If you give us some idea of what you are trying to accomplish we may be able to offer some suggestions.

Those services look correct. voxl-vision-px4 is the main service that would be routing MAVLink packets from a network interface into the flight controller

Port 14550 is meant for external connections to different IP addresses such as multiple ground control instances. Only one connection to localhost is supported on port 14551. To support multiple local IP connections a separate port and thread would likely need to be opened. You can also have multiple local processes communicate through the "vvpx4_mavlink_io" pipe using libmodal_pipe instead of UDP.

Missed that part, thank you, it seems to do the trick.

Perfect! I know how to run those. Thank you

Hi, Thank you very much. I've check EKF2_AID_MASK,it was a problem with my setup (Flight core wasn't configure well). Now I'm working with VOXL FLIGHT and on QGroundControl I see ODOMETRY message as well. Maybe could you help me with understanding the following issue?: With VOXL flight I want to execute the outdoor flights without GPS. But on QGroundControl ,I didn't see DO_SET_HOME button(request) like with GPS flights and therefore i couldn't execute auto flights. How i could did it? Thanks again

hello @colerose how do u get all these topics by launching just roslaunch voxl_mpa_to_ros voxl_mpa_to_ros.launch because when i launch it i get just these topics : MPA to ROS app is now running Found new interface: hires Found new interface: qvio_overlay Found new interface: stereo Found new interface: tracking Found new interface: imu0 Found new interface: imu1 Found new interface: voa_pc_out Found new interface: qvio Thank u in advance for your reply

Thank you so much!

In theory two VOXLs networked together are possible. We have not actually done that ourselves though. You could potentially use the UART side port to send data back and forth with libvoxl_io, that might be the most straightforward.

@modaltb Using USB 2. Got my hands on an OTG adapter, seems to be doing the trick.

Great to hear! Feel free to create a pull request if you would like to get the feature into the mainline so you don't need to maintain a fork.

Wanted to update this by saying I experienced same issue, but I resolved this by disconnecting tracking camera that had been installed upside down. So, if anyone is reading this in the future....try disconnecting your cameras attached to the board

Those are the specs from the vendor, we don't have any more information, sorry. The intensity image is published in MPA so you could perform a calibration on it to find out more details.

@Chad-Sweet how many ekf_imu instances would you suggest running on a VOXL-FLIGHT in general, considering a decent workload already on the VOXL -part? cheers

Hi Parisa, A number of the gnu standard tools are defined explicitly to our architecture on voxl: arm-oemllib32-linux-gnueabi. If you tab out that (or just tab out "arm") you'll see a number of the standard tools like gcc, gdb, ld, objdump, etc. To run gdb on voxl would thus be arm-oemllib32-linux-gnueabi-gdb