@tom Thank you. I'll look it up.

@czarsimon When you run through the QDL process how long does it take for the flash to finish? seconds? minutes?

Also, are you able to ADB onto functional devices on this machine? Want to rule it weird permission issues

@RSAUser1 yeah i'd probably pass to @tom . The modem is seems connected, otherwise you wouldnt see wwan0 come up. Once I had access to AT commands I ditched QMI which I think is more or less a wrapper for those commands anyway.

@jcai, yes you are correct regarding the connections that will work on Voxl2 and Voxl2 mini.

Please reach out to https://modalai.com/contact and we will create a custom order for you. You should add a link to this thread. I will work with our team to get the right hardware for you.

You will need

M0159 M0181 two specific coax cables between those teo boards (18cm length?). M0155 (assuming you already have M0161 with a coax, but is your M0161 connected to M0173 camera front end?

You should also get a tool for removing coax connectors - check at the bottom of this guide: https://docs.modalai.com/micro-coax-user-guide/ . I dont think we sell the tool, but it looks like the tool is out of stock (Mouser) - you will need it to disconnect your M0161 from M0173.. i will check if we can provide it.

Regarding length, it looks like the longest cable we sell is 18cm : https://www.modalai.com/products/mcbl-00084?variant=48956821733680 , and this is what i am using for testing Hadron.

Alex

@Alex-Kushleyev The new board works well now after updating the firmware. We'll also update the original board soon and see if that resolves the issue with it, too. Thanks for your help!

@bendraper Mini can get power via USB so it's not out of the question

@Mohammad-Goli I had a really hard time building it. This is basically what I did:
mavsdk.png

I had to manually build it.

After that, I just followed the instructions and this is what I got, but I found an error at the end.
mavsdk2.png

I had to use this command to be able to import the image:
cat /data/tmp/voxl-mavsdk:v1.2.tar.gz | docker import - voxl-mavsdk:v1.2

But now I can't run it. Hopefully, someone on here can help with this.

@Samuel-Lehman , Not sure what is going on but i was able to build your example with the following command on VOXL2. I had to comment out #include "hello_cross.h" because i did not have it.

voxl2:~$ gcc -O2 -Wall voxl_io_uart_test.c -o voxl_io_uart_test -lmodal_pipe -lvoxl_io -L/usr/lib64 voxl_io_uart_test.c:14:12: warning: 'opt' defined but not used [-Wunused-variable] static int opt = 0; ^~~ voxl2:~$

I am not sure what's going on, you can enable verbose CMake file to see what compile command CMake is generating and compare that to the above.

Alex

@Jetson-Nano Here's some example code: https://gitlab.com/voxl-public/voxl-sdk/services/voxl-vision-hub/-/blob/master/src/autopilot_monitor.c?ref_type=heads#L514

@antenna-eng Are you running linux natively on your machine or are you using a VM?

Agreed! thanks for noticing, Tom. Definitely should be tested on a recent SDK..

Alex

@Alex-Kushleyev Thank you for the detailed breakdown! I am fairly certain OP is from another team on the same project and I believe we are describing the same event. He has custody of the drone/logs so I will let him follow up with you

@tom thank you for reverting , I sorted out the issue, the file name in the voxl-qvio-server was opencv_tracking_front_intrinsics.yml instead of opencv_tracking_intrinsics.yml
and in the voxl-vision-hub the name was tracking_front which i renamed in tracking. After the above mentioned changed the voxl-qvio-server is working fine.
thank you for the support.

@mkriesel Great, thanks for the update

@tkddnjs825 , since you already have M0062, you should be able to use it. As you already identified, J9 on M0062 has /dev/ttyHS2 Linux UART device.

You can also find more information here : https://docs.modalai.com/voxl2-external-flight-controller/ regarding configuring mavlink server.

It looks like you are doing the right things here. However, the use case for "autopilot_uart_bus" maybe different from what you need - in your case your autopilot (px4) is actually on VOXL2 and the uart connection is for the path to GCS.

You may need to modify mavlink server depending on what you want to pass on this UART connection.. This goes beyond my knowledge of mavlink server - please try to see if you can get it to work, otherwise post a follow up question with details of what you would need to be sent using the UART connection.

Alex

Hi @Alex-Kushleyev ,
Thank you very much for such a detailed reply, we will carefully refer to your suggestions to make the purchase.

thanks again!

@VSK said in Stuck installing ros-melodic-pcl-conversions:

configure python-twisted-core:all 17.9.0-2ubuntu0.3 <none>
status half-configured python-twisted-core:all 17.9.0-2ubuntu0.3

Maybe that package got corrupted on the install. Can you try running sudo apt-get clean?

If that doesn't work, you could also try removing both of the packages and do the install again.

$ sudo apt remove python-twisted-core:all $ sudo apt remove ros-melodic-pcl-ros ros-melodic-pcl-conversions

@Jetson-Nano It should be no different than with any other flight controller hardware running PX4. The PX4 documentation should be able to explain how to do that.

Hi @tkddnjs825,

In addition to Alex's question above, could you also please share which version of voxl-elrs is being used on each voxl2? The voxl-version command should list the versions of each installed package.

Can you also please confirm that in the voxl-px4 configuration file on the voxl2 that is not able to communicate with the ELRS receiver that the RC type is set to CRSF_RAW, like this: RC=CRSF_RAW.

Furthermore, if you could share the output of voxl-elrs --scan from the voxl which is unsuccessful that would be helpful.

Thanks,
Max

@teng , you should be able to run multiple independent instances of QVIO, but our scripts are not set up to do that. You would need to do the following (the list may not be complete..):

create a second voxl qvio server config and populate it with appropriate changes calibrate the second camera and update the path to intrinsics in the second qvio server config update the extrinsics calibration file for second camera and use it in qvio server config you will probably need to change the qvio output message / pipe names, otherwise they will conflict with the first instance. there is also a check if the process is already running (in qvio server main.cpp), so you would need to bypass that check.

Alex