The Yocto OS uses opkg which is similar to, but not compatible with, aptitude

Aptitude is used in Debian/Ubuntu distros. You can run one on VOXL using Docker as documented here: https://docs.modalai.com/docker-on-voxl/

@FourPointTwoMm Interesting, I was under the impression that the Microhard modems would auto-reconnect to each other when they came back in range. This is something we will have to test.

@Alex-Gardner thank you!

@Chad-Sweet voxl-dfs-server is for voxl-vision-px4 ver 0.8.1.

version 0.6.8 is not used voxl-dfs-server.

could you please let me know based of voxl-vision-px4 ver 0.6.8?

Thanks,

@Alex-Kushleyev great!

That’s a point what I need. I’ll try it

Thanks,

@gauravshukla914 no problem, glad it helped

@Chad-Sweet Hey, I updated my voxl to the newest system image and after doing so my docker is using docker-start.service while before it was using docker-daemon.service.

Not sure why this has changed, but I have updated the above instructions and wanted to let you know so you could change this in the documentation.

Is there a reason why this would have changed after flashing a new system image onto the device? Both times I configured my docker by using voxl-configure-docker-support.sh

@Daniel-Ryu thanks for posting the resolution!

Also, you could do a quick test on DSP side, just write more data to UART port than the baud rate can handle and see what the write() function returns and how much time it takes. Usually the write() function is non-blocking, as it will hand off data to underlying layers to take care of UART writing. But I suspect that if the SDSP UART system runs out of buffers to put your data in, it will probably block until buffer space for writing frees up instead of dropping data. I have not confirmed this, but that's my expectation.

I was able to resolve this issue by trial and error of the camera orientation, it seems like the documentation is outdated and does not provide an accurate reference for a starting point to obtain the proper values.

It all depends on your setup. With our flight deck setup we can run all 4 cores at 100% with just the fan. A fan is much more effective than a heat sink. Still might require a little experimentation though

Hi, I am facing the same issue

1a3fbb9a-05ba-4660-8b39-9e658f6a2d35-image.png
ca2512c7-9c2e-4b01-864d-c55f02b944f3-image.png

Also, I don't have a USB Expander and Debug Add-On Board (https://docs.modalai.com/usb-expander-and-debug-manual/)
Is there any other way so we can Force VOXL into Fastboot Mode. (like any onboard button/ any other technic) please let me know.

Thanks this fixed it. It was connected backwards. Maybe this can be marked a bit clearer in the docs, I think it’s quite unintuitive having the cable going inwards the board when not using the extension.

@Kasum-Hussain actually sorry my mistake i thought i saw video2 but no if i go into dev folder there is no video2 only video0 video1 video32 video33

Hi @a-w ,

If you're running on target, you'll need an arm64 container flavor (not x86/64), see this docker file as an example:

https://gitlab.com/voxl-public/voxl-docker-images/voxl-docker-mavsdk-python/-/blob/master/Dockerfile#L1

You'd need to download yourself and then push to the target (or if VOXL is connected to the internet, download it and manually install).

There's not an 'apt-get' like setup for opkg unfortunately. Sometimes this means you need to build from source.