@Chad-Sweet That is what I was thinking. I'll check in with the boss and see what he wants to do. Thanks!

@張為超 voxl-emulator is a docker image that emulates the environment https://docs.modalai.com/voxl-emulator/.

Have you looked at this doc? https://docs.modalai.com/voxl-streamer/#streaming-uvc-cameras-from-voxl-uvc-server $ lsusb usually helps as well

Oh wow, I totally overlooked the fact that the mavlink server seems to have been disabled during upgrade. Anyway thanks for the more up to date repo link, that might be very useful

Hi Joe! We're most of the way through a big update that'll make all of our packages able to run on multiple architectures, this release will be paired with a system image update. If you'd like to manually build the latest from our gitlab in the meantime, simply add the line arch arm64 7 to /etc/opkg/arch.conf and then run opkg update on voxl.

The VOXL is an open, Linux-based platform. You can change almost anything in software you would like. The source at https://code.modalai.com is provided for reference, and our customers often modify to their use case.

Thanks for the answer, I found another solution as well that worked for me. It is probably more intuitive for experts, but i noticed that in the third party from your git you should also imply git submodule init and git submodule update . After doing that, the old instructions worked semi-properly, and I could reinstall the voxl-portal package with not farther problems. It's just the README files that were not so obvious in explaining so.

Fixed it forgot to turn Fastboot of when installing.

Yeah, all systemd-journal-flush.service is doing is running journalctl --flush which is not doing anything when run manually

@Jae-Park You should ship out the entire drone so that the team can verify that all of the components are functional, fix anything else that you may not have seen, and do a final flight test before sending back.

Hi Vinny, Thank you for such a detailed set of answers! In response to your points: We will just make a super short connector between the daughterboard and J1. I did like the elegance of a single board that snapped on and did everything we wanted but this really won't add much to the footprint. We are running 12v passive power over ethernet so we will make sure that per the docs there is a nice supply of 5v 6a for the j1 port. Yep just making sure, this will be shunted strait into a usb-to-ethernet setup (based on the rtl8153-cg chip), depending on how annoying the GPIO stuff might be we did think about simply putting a tiny powered usb hub onto the daughterboard and breaking out a usb connection in order to do those tasks (a little more effort to implement but more flexibility) Ooof that is a bit of a minefield isn't it? The BLSPs do look to be the best choice if we go with the GPIO idea. In light of this it might not be that bad an idea to go with the USB microhub idea, that way it would not be hard to implement another discreet microcontroller to deal with any realtime/gpio tasks and simply package that up into a nice neat message to pass upstream. We will do a bit of planning and let you know where we got to. Regards, Thomas

@Alex-Gardner I see why you created a separate tool for checking the connected cameras as the code in that tool is implemented in much lower level files on voxl-camera-server. I did quickly put together a flag option that would list cameras if they are setup in /etc/modalai/voxl-camera-server.conf I created a pull request here Let me know if this is useful. If the needed feature requires all cameras to be listed let me know and I can see what I can do. Also, I was trying to find a way to get some form of id off of the cameras, but I see in code that we compare the resolutions and that is how we distinguish a stereo from a tracking. Was trying to find some HAL3 data member that could give more of an "id". I found this ANDROID_REQUEST_ID variable in this documentation, but I could not get it working

Switching tack: I've configured voxl-camera-server to encode H.265 and write to /data/misc/camera: Mem: 1396848K used, 2464472K free, 17096K shrd, 16692K buff, 318292K cached CPU0: 32.2% usr 21.0% sys 0.0% nic 42.8% idle 0.2% io 2.1% irq 1.4% sirq CPU1: 22.3% usr 29.8% sys 0.0% nic 46.5% idle 0.0% io 0.8% irq 0.4% sirq CPU2: 53.7% usr 1.2% sys 0.0% nic 44.5% idle 0.0% io 0.2% irq 0.2% sirq CPU3: 50.6% usr 0.4% sys 0.0% nic 48.7% idle 0.0% io 0.2% irq 0.0% sirq Load average: 5.62 4.10 3.21 3/582 3801 PID PPID USER STAT VSZ %VSZ CPU %CPU COMMAND 3600 1 root S 850m 22.4 0 30.1 /usr/bin/voxl-camera-server 1966 1 root S 665m 17.5 0 19.6 /system/bin/mm-qcamera-daemon 2321 1 root S 3988 0.1 1 0.9 /sbin/leprop-service 2159 1 system S 372m 9.8 1 0.7 /sbin/logd 7 2 root SW 0 0.0 1 0.4 [rcu_preempt] 3445 2 root SW 0 0.0 1 0.3 [kworker/u8:14] And the CPU is in good shape: Name Freq (MHz) Temp (C) Util (%) ----------------------------------- cpu0 480.0 66.3 25.86 cpu1 480.0 65.6 22.50 cpu2 2150.4 70.1 81.82 cpu3 2150.4 66.9 22.68 Total 70.1 38.21 10s avg 38.38 ----------------------------------- GPU 0.0 60.3 0.00 GPU 10s avg 0.00 ----------------------------------- memory temp: 62.1 C memory used: 1376/3770 MB ----------------------------------- Flags CPU freq scaling mode: auto GPU freq scaling mode: auto ----------------------------------- And this is voxl-camera-server encoding H.265, at 3840x2160x30fps, writing to flash. So either voxl-streamer is doing software encoding very poorly, or something about the network stack is VERY broken. I'm inclined to think the former.

@Chad-Sweet Right on. I will take a look at it. See what I can do

@SmittyHalibut I updated my previous response to be more clear.

@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.

@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.

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