@Moderator Pin 8 is not needed. The USB on Voxl/Voxl2 J13/J3 is always a HOST. Previous gen designs used this for OTG selection, so we manage this directly on Voxl2. For all intents and purposes, pin 8 is a "dead pin" and should be N.C. (no connect). Let us know if you have any other questions. Thanks

Thanks alot @Chad-Sweet for guidance. I will look into rangefinder server for further integration.

Have you used an oscilloscope to probe the line from the flight controller to VOXL2 to make sure the flight controller is sending data at the correct baudrate? Also note that the logic level of that UART connector on M0125 is 3.3V, I'm not sure if that matches the expected logic level of the port you are using on the CubeOrange. Also note PX4 requires some serial port configuration. We normally use mavlink channel 1 with the Telem2 port on our flight core set to 921600 and 'onboard' mode. This translates to the following px4 param settings, note that yours will most likely be different due to using a different flight controller in a different configuration. MAV_1_CONFIG 102 MAV_1_FORWARD 0 MAV_1_MODE 2 MAV_1_RATE 0 SER_TEL2_BAUD 921600

We normally do a 'proper' voxl-camera-server update to add meta data (e.g. this commit) but I've used the imx214 with updated preview_width etc for a different sensor and it seemed to run OK for me for testing. Let me see about IMX377, seems like if we sell it we SHOULD support it already!!! But need to see what's up.

Hi @modaltb Thanks for sharing that information. It happened today and changing the power cable fixed it.

It is probably worth upgrading the software to the latest release. The version you have is really old. I guess I can't say for sure that it will fix the problem, but it's likely to match the docs better for getting going https://docs.modalai.com/voxl2-system-image/

Can you try to run the server manually: voxl-dfs-server and see what the output says

@Alex-Gardner Thank you for the update. Will be testing this pretty soon.

Hi @Vinny Thank you for prompt response. I understand the current state of development of TDK Mezzanine on VOXL2. Noted. No further information needed. Thank you

@Kevin-Racktoo Glad we can help. If you would like us to review your schematic for Voxl2 integration before you tape-out, just let us know! You can use our contact form to reach out and we'll respond back. https://www.modalai.com/pages/contact-us Thanks!

On my setup yes that was all I needed to do, but we are still going to do a "full proper tune" on our S500 based frame (Sentinel dev drone) and I will confirm with you that we are getting performance as expected after this and share a video. Our flight test team will be doing that this week, thanks for the patience!!!

@Alex-Kushleyev I am making a quadcopter with voxl2 and the modalai esc. I am trying to calibrate the esc. I am able to run the script but having this issue while scanning the esc with ftdi cable although I am able to run the motors with voxl2 J18 port. /voxl-esc/tools$ python voxl-esc-scan.py INFO: Device and baud rate are not provided, attempting to autodetect.. Scanning for ESC firmware: /dev/ttyUSB0, baud: 250000 Scanning for ESC firmware: /dev/ttyUSB0, baud: 2000000 Scanning for ESC firmware: /dev/ttyUSB0, baud: 921600 Scanning for ESC firmware: /dev/ttyUSB0, baud: 57600 Scanning for ESC firmware: /dev/ttyUSB0, baud: 115200 Scanning for ESC firmware: /dev/ttyUSB0, baud: 230400 Scanning for ESC bootloader: /dev/ttyUSB0, baud: 38400 Scanning for ESC bootloader: /dev/ttyUSB0, baud: 230400 Scanning for ESC bootloader: /dev/ttyUSB0, baud: 921600 ERROR: No ESC(s) detected, exiting. Is there any way to calibrate esc using voxl2?

https://docs.modalai.com/modal-esc-datasheet/

Hi @mlarsen , If you're familiar with QGroundControl, similar to the pixhawks, you can use the Analyze > Logs feature to grab them (over an IP network not USB...) [image: 1667487221073-f8c31789-b1a1-4aa9-a498-d789ade3d86c-image.png] We are also saving this on disk here on VOXL2, eg: voxl2:/$ cd /data/px4/log/ voxl2:/data/px4/log$ ls sess001 sess003 sess005 sess007 sess009 sess011 sess013 sess015 sess002 sess004 sess006 sess008 sess010 sess012 sess014 voxl2:/data/px4/log$ ls sess001 log001.ulg log002.ulg log003.ulg Using the USB connection over adb, you can pull from device to your host system, eg: adb pull /data/px4/log/sess001/log001.ulg .

Same as every PX4 quadX: https://dev.px4.io/master/en/airframes/airframe_reference.html#quadrotor-x [image: 1666970979497-b3515d73-ffea-40c8-bacd-3c2584cfc059-image.png]