ModalAI Forum

Hello, @Nicolas-Brissonneau: I am trying to do the same thing as you and am stuck with the same problem. Did you manage to solve it?

@張為超 Great, glad to hear it is working for you now!

Check out the troubleshooting tips here for future referenec https://docs.modalai.com/flying-with-vio/#position-mode-rejected

Hi, After inspecting services, this was the output. I can see the mavlink server is neither enabled nor running. voxl:/$ voxl-inspect-services Service Name | Enabled | Running | CPU Usage --------------------------------------------------------------- docker-autorun | Disabled | Not Running | docker-daemon | Disabled | Not Running | modallink-relink | Disabled | Not Running | voxl-camera-server | Disabled | Not Running | voxl-cpu-monitor | Disabled | Not Running | voxl-dfs-server | Disabled | Not Running | voxl-imu-server | Disabled | Not Running | voxl-mavlink-server | Disabled | Not Running | voxl-modem | Disabled | Not Running | voxl-portal | Disabled | Not Running | voxl-qvio-server | Disabled | Not Running | voxl-streamer | Disabled | Not Running | voxl-tag-detector | Disabled | Not Running | voxl-tflite-server | Disabled | Not Running | voxl-time-sync | Disabled | Not Running | voxl-vision-px4 | Enabled | Not Running | voxl-wait-for-fs | Enabled | Completed | I tried starting the service using systemctl and this was the output. voxl:/$ systemctl start voxl-mavlink-server voxl:/$ voxl-inspect-services Service Name | Enabled | Running | CPU Usage --------------------------------------------------------------- docker-autorun | Disabled | Not Running | docker-daemon | Disabled | Not Running | modallink-relink | Disabled | Not Running | voxl-camera-server | Disabled | Not Running | voxl-cpu-monitor | Disabled | Not Running | voxl-dfs-server | Disabled | Not Running | voxl-imu-server | Disabled | Not Running | voxl-mavlink-server | Disabled | Running | 0.0 voxl-modem | Disabled | Not Running | voxl-portal | Disabled | Not Running | voxl-qvio-server | Disabled | Not Running | voxl-streamer | Disabled | Not Running | voxl-tag-detector | Disabled | Not Running | voxl-tflite-server | Disabled | Not Running | voxl-time-sync | Disabled | Not Running | voxl-vision-px4 | Enabled | Not Running | voxl-wait-for-fs | Enabled | Completed | after configuring the voxl in softap mode, and connecting to it, the issue persists. Would downgrading the software release to VOXL Platform 3.6.0-0.5.0 help? Thanks

@Moderator I just tried running those instructions for VOXL1 build, but have an issue downloading the manifest package from codeaurora. I posted an issue here about it. Please let me know if there is an update!

Hello, The driver you are looking for (SMSC95XX) was recently added to our kernel build. It has not made its way to a platform release yet so you'll have to build kernel and flash your device with it. From the information given, I believe you are on the VOXL2 platform. If this assumption is incorrect let me know and I'll link the instructions for building the VOXL1 kernel. Here are the instructions for building the VOXL2 kernel. In order to build the kernel, you'll want to clone this qrb5165-kernel-build-docker repository. This project builds a docker image that we then use in order to build the kernel for the qrb5165 (VOXL2) device. For instructions on how to do so, you can look at our VOXL2 Kernel Build Guide. Once the kernel is flashed, you'll have the driver enabled on your device. Please let me know if you run into any issues.

@Chris-P to answer my own question, I checked the voxl-vision-px4 code and the system time will be set once from gps time (when valid) if it has not been set yet by ntp or manually.

@Matt-Turi Wow, thank you for updating me. I will try these models now

Thanks Steve, I went to compile the source code with the voxl emulator and it compiled without issues.

@ryan-langlois1 Seems as though you've answeredthe question yourself but by default /etc/network/interfaces doesn't exist. It is created in certain configurations i.e. using Microhard with voxl-modem

@ James-Strawson Im sorry but is note the case…. While just activation voxl vision px4 service from fredh resceived voxl cam, voxl output local frame pos and velocitys via mavlink. so how to activate local to body frame velocity transformation? Maybe with px4 this work but with ardupilot i check on mavlink analys and i make simple translations and i can ensure you that voxl send out local frame pos and vels. Maybe you can tell me ou to force voxl to output local frame pos but body frame vels to ardupilot ? Thank you so much.

Ok great! Thanks for the info!

Oh no, sorry to hear that. Let's see what we can do to resolve that. So as not to be redundant and streamline the process, what have you attempted already to unbrick the VOXL's? Could you also provide further information on the board as well as what you were attempting to do before the VOXL's bricked? eg. software version, setup, camera config, computer setup, usb cables, power management, etc. The more information you can provide, the better we can help you.

I figured it out! I was following the gitlab page to install the cross docker, which is incorrect when using the prebuilt image from the modalai website. (https://gitlab.com/voxl-public/support/voxl-docker) following this documentation actually works: https://docs.modalai.com/voxl-cross/ Eli

@serge said in autostart voxl-streamer: @Alex-Gardner said in autostart voxl-streamer: systemctl enable voxl-stream thank you

Looks like this was being caused by something on our end. Sorry about that! -Drew