ModalAI Forum

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

More detailed GPS documentation would definitely help, especially for troubleshooting setup issues and understanding configuration differences between modules. Saves a lot of guesswork during integration.

@Ward-Javoronok How is the parameter COM_OBS_AVOID set? If you set it to 0 that disables obstacle avoidance and should get rid of that error.

These are the propellers that were used for that drone https://www.getfpv.com/lumenier-6x4-slow-flyer-propeller-set-of-4-clear.html

That pink hue usually ends up being related to white balance or ISP tuning rather than the sensor itself. I’ve also seen it happen under certain lighting conditions where the auto settings overcompensate a bit. Might be worth checking the raw output vs processed output to narrow it down. If the RAW image looks fine, then it’s probably somewhere in the color pipeline. Also, for comparing the tint between frames, I’ve used https://colorpickerimage.org/ before to inspect the actual RGB values in different areas of the image. Makes it easier to confirm whether the pink cast is consistent or only affecting highlights/shadows.

Adding more cameras can definitely improve robustness, but synchronization and calibration become super important once you go beyond the default setup. Even small timestamp offsets between sensors can throw VIO off pretty badly. I’d also keep an eye on bandwidth and CPU usage because extra camera streams add up fast on embedded systems.

@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: 1779297839725-image-1.png]

@Eric-Katzfey I'm not sure what may have changed, before when setting BATT_MONITOR to 21 the param would write but we wouldn't get the additional parameters that that setting should have enabled. Last week I tried it again to reply to your last message and we got the BATT_I2C_BUS parameter and were able to get it all working. Gotta love when things seem to magically fix themselves, thanks for the support. PS, we have built a parallel system on the latest SDK and will be migrating the current one over to match.

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

You might also want to double check the current rating of the power module versus the full load from your setup. A lot of weird reboot or brownout issues end up being power related, especially once extra peripherals get added. Keeping the wiring short and using a stable regulator helps too.

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

One thing that helped me before was comparing the device tree and driver setup against an already supported sensor with similar specs. A tiny mismatch in clocks or I2C config can stop the sensor from initializing properly.

Thanks @Eric-Katzfey ! Here is the pinout for the dev board "UART" port that includes i2C_SCL and I2C_SDA. [image: 1778773646212-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.