duplicate perhaps, see https://forum.modalai.com/topic/2313/no-gps-lock-for-vehicle

@Eric-Katzfey Oh, ha. I could have sworn it wasn't outputting my custom module status message. Checking again I see it though. That's silly.

@Aaky I sent you a link in email

@wilkinsaf Yup, this guy: https://www.modalai.com/products/voxl-lte?variant=39300535681075

Hi @Abdullah01 I can try to help you with the hardware side. The FrSky RC receivers are a little confusing. They have several SBUS denoted ports on the module. This diagram shows which pins are utilized for our setup with the Voxl2 I/O board: https://docs.modalai.com/cable-datasheets/#mcbl-00065 Apologies we do not have the MCBL-00065 for sale yet (it had an error we have yet to address), but if you are handy with a set of tweezers, and are willing to try these steps here to make your own, it's not that hard to pin the side needed for Voxl2 I/O with a 4-pin JST GH shroud. https://docs.modalai.com/cable-userguides/ You can use a cable like this for starter material: https://docs.modalai.com/cable-datasheets/#mcbl-00015 and splice into the FrSky cable that came with your unit. Hope this helps!

@Aidan-Dempster You are correct on the mavlink console. This is not currently supported on VOXL2. You would have to log into the VOXL2 directly using adb (on the benchtop) or ssh (while flying) in order to interact directly with px4 shell.

@wilkinsaf This is good insight, thanks!

JK found it https://forum.modalai.com/post/4746 (with a link to the quectel AT commands) https://forum.modalai.com/topic/401/lte-modem-works-but-cannot-ping/23 Had to change my search topic to title AND posts

@tom Thank you. A factory reset did fix the problem.

@Zachary-Lowell-0 Ah, yes I see what you mean. The secondary steps of updating gazebo's plugin path and loading a world with a model that uses the sitl plugins. Ok, well in that case my only roadblock is building PX4 on my mac which, as far as I can tell, is a PX4 problem and not a VOXL problem so thank you for your help.

We do not have any feature to share at this point.

@tom Thank you. It works well now with above workaround. Also on seperate I have opened one more ticket regarding voxl-streamer over here, please respond on that as well since it is also related to new beta image.

@Abdullah01 Leave SENS_BOARD_ROT as the default value. You are specifying the rotation of the board by giving the IMU driver the -R 4 option.

@Vaibhav-Usapkar Your ls showing it in the file system is showing it outside of the docker container. You will need to run the base docker container and do ls there to see what is in that directory. How did you get the gcc-linaro-7.5.0-2019.12-x86_64_aarch64-linux-gnu.tar file? That shouldn't be in your local directory.

@afdrus My best guess is 2-4 weeks

@Aidan-Dempster Yes, HITL support will be migrated to the voxl-dev branch as well.

@Jyotish-Kumar i have faced the same issue. the record pipe name has changed in dev branch, try to use hires_large_encoded or hires_small_encoded based on your resolution requirement. Can find more config parameters in /etc/modalai/voxl-camera-server.conf

@relevinsky The VOXL SDK projects aren't meant to be built on VOXL2 itself. We offer a few different docker images to build on a PC, voxl-qvio-server on VOXL2 is built using qrb5165 emulator: https://docs.modalai.com/voxl-emulator/#install-the-voxl-emulator-docker-image while some other projects are built using voxl-cross: https://docs.modalai.com/voxl-cross/#install-pre-built-voxl-cross