@JB1 Our voxl-remote-id software with WiFi dongle is intended only for reference and is not meant to be a commercially ready system for our customers who need a remote id solution for their VOXL2 based drone products. Integration, testing, validation, and FAA registration with desired hardware is up to the end user. At a minimum the manufacturer id would need to be changed from ModalAI's id to your companies issued manufacturer id.

@Alex-Kushleyev

I updated the correct kV and uploaded the params to the ESC. I increased the spin-up time from 0.5s to 1s; and spin-up power from 90 to 110 and then to 120. There was a bit of improvement but still the motor spins very intermittently. Previously, it would just barely move and stop. I swapped motors on ESC channel 1 (good channel) and ESC channel 2 (bad channel). So the motor working nicely on channel 1 stopped working when moved to channel 2. And the motor that was not working on channel 2, worked fine when moved to channel 1. So it is definitely not the motor (or short in winding). We have made sure the ESC is free of any debris and not touching anything.

Is there a good way to share video? I can share a folder with you if you give me an email pls.

Thanks.
Regards.

@jon And you can find a lot of detailed information about the agent, including the start options, here: https://docs.px4.io/main/en/middleware/uxrce_dds

@RoyAzriel ,

you can back up your voxl-camera-server.conf and then run voxl-configure-cameras 29 and the following will happen:

all the existing sensormodule files will be wiped from /usr/lib/camera to avoid confusion only those sensormodules that belong in C29 config will be copied from /usr/share/modalai/chi-cdk to /usr/lib/camera the camera server config file (/etc/modalai/voxl-camera-server.conf) will be overwritten with the defaults for C29 configuration -- you can then see the config entry for TOF sensor and copy/paste that into your old config file, if you wish or use the new config file as is.

Alex

@Eyal , sorry for the delay. Here is some additional information regarding Stinger FPV:

https://docs.modalai.com/stinger-vision-datasheet/ base weight with battery : ~570g maximum thrust per motor : 650g @ 15V, 2600g total theoretical theoretical max thrust to weight ratio: 4.5:1, lots of extra margin, but if you add a LOT of weight, will need to check motor temps, etc. CAD model for stinger (may be slightly outdated) : https://forum.modalai.com/topic/5180/looking-stinger-fpv-cad-models -- you can attach your payload to carbon fiber I think that Stinger will be easier to tune up with additional payload because of more responsive and powerful propulsion system than Starling 2. i dont know what your sensor package is so, it is hard to comment about which platform is better. Starling 2 has landing gear that offsets it from the floor. Stringer is much lower to the ground.

Alex

@Alex-Kushleyev Thank you that fixed it for J6. Is there a reason the same config doesn't work on J7? Ideally was hoping to use J7 since it works better for our layout purposes.

I can get J6U-ar0144 and J6L-imx412 to work but not J7U-ar0144 and J7L-imx412 or J7U-imx412 and J7L-ar0144. For both it cannot find the lower sensor.

Also is there a reason the imx412 driver does not exist for J6 upper?

I was able to get the visual odometry message updating the PX4 EKF2 and that seems like the better path. Just to make sure I've got this set up correctly, I put the application processor time (CLOCK_MONOTONIC) into the timestamp field and the mavlink server updates the message with the appropriate PX4 kernel time before forwarding it to PX4?

@Eric-Katzfey I’m looking for the voxl-emulator Docker image referenced in the documentation:

VOXL Emulator Documentation: https://docs.modalai.com/voxl-emulator/#install-the-voxl-emulator-docker-image

However, in the Development Sources / Developer Portal there doesn’t seem to be any Docker image available for voxl-emulator.

Could you please confirm if the image is still available, or if there is an updated download location for it?

Thanks @Eric-Katzfey ! Here is the pinout for the dev board "UART" port that includes i2C_SCL and I2C_SDA.

0cda71eb-2c0f-4b1b-ba91-8b3862fc9763-image.png

The dev board pins 1-6 matching to J19 pins 1-6

We will give the COMPASS_DISBLMSK parameter a shot and see if that works.

@jon That looks like the DSP portion of PX4 didn't exit completely / cleanly from the previous run. What version of the SDK are you running?

@Barry-Hammond https://docs.modalai.com/voxl-streamer/#how-to-stream-video-with-rtsp-on-voxl

Quality greatly depends on your LTE coverage and VPN performance. I recommend lowering the bitrate in /etc/modalai/voxl-streamer.conf until you're happy with the response rate.

Tailscale can add overhead as well and our recent LTE testing has involved hosting a custom WireGuard server.

@Vinny @Eric-Katzfey @Alex-Kushleyev @modaltb
Hi Guys,
Any update would be great appreciated.

@Michael-Hatton When you arm the drone it is in flight mode and the motors start to spin. It's that spinning of the motors that you don't want while plugged into a power supply. Only use your battery to actually spin the motors and fly.

@Jskim This is the repo we use for support of UVC cameras: https://gitlab.com/voxl-public/voxl-sdk/services/voxl-uvc-server. I don't think it will work directly with Seek cameras but you can try. In my experience each new camera requires a bit of integration work and updates to that code.

@mkriesel It's possible the kernel you're flashing is incorrect. Can you provide the full terminal output of the install?

Hi Cbay,
There is a small clock buffer on the edge of the PCB. An RMA can only replace the whole board, not replace a single device. The part to check would be here: image (1).png

@chinlee5 Which drone do you have? Which versions of software are you using? Are those messages appearing on QGC? Also, do not try to arm the drone or fly the drone while attached to a power supply. Only use a battery for that. If you take the drone outside with a full view to the sky so that GPS can acquire satellites do the messages go away?

Hi Kim,

There are a couple changes required here that will make this work:

1. Rebuilding Kernel with SPI14 enabled
You're going to have to rebuild and flash the kernel with QUP14 enabled as SPI. There is also a directional level shifter on GPIO67 that needs to be set to high in order for SPI on QUP 14 to work. I created this branch for you that should have the kernel changes that you need:

feature/voxl2-mini-spi-qup14 (link)

In order to actually build and flash the kernel please follow the instructions from our public docs on how to build the kernel

https://docs.modalai.com/voxl2-kernel-build-guide/

When building the kernel, after syncing but before building, make sure to go to the cloned meta-voxl2-bsp directory and checkout the branch that I created (feature/voxl2-mini-spi-qup14).

Also there is a chance you may need to build a kernel variant depending on your device so also make sure to check this document to see if you have a -2 device which would require building the kernel with the -v var02 flag

https://docs.modalai.com/m0054-versions/#m0054-1-and-m0054-2

2. Configuring Trustzone with Correct QUP
I would recommend using the devcfg binary that comes from the `voxl2-mini_SDK_1.0.0.tar.gz. In order to flash devcfg you'll want to run the following command

fastboot flash devcfg <path/to/voxl2-mini_SDK_1.0.0/devcfg>/devcfg.mbn

You should flash the kernel and devcfg (Trustzone) during the same fastboot session to avoid running into any issues with the device booting.

Let me know if you have any additional questions or run into any issues!

@Matt69 , Do you need the additional PWM outputs to be connected via PX4? If not, perhaps connecting M0065 to a cpu uart and communicating directly would be the simplest (i can help you with that).

Do you have spare SLPI UARTs?

Not sure if PX4 would support multiple voxl2-io drivers running, i guess that should work? I don't think we have tried it. if you have spare slpi uart ports, just give it a shot? There may be a problem with two actuator drivers having the same name.

Alex

Hi @mtcbj
That is the flex stiffener. Our older image modules used stainless steel. Some of our newer modules use laminate.
Those holes are likely just flex/FPC air escapes during the backer lamination process. They do not provide any functional purpose after assembly.
I see no issue filling them with epoxy.
Hope that helps!