ModalAI Forum

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/

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.

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

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

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!

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 .

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

@Kyungtaek-Oh-0 In your first screenshot PX4 is not crashing. It is trying to detect if an external px4io board is connected on one of the serial ports. In this case it is not detecting it (so you see all of those error messages) and it goes on to start a Spektrum RC driver instead. In the second screenshot PX4 is not crashing. The first error about client not being able to reset all parameters is actually mis-classified as an error. It is really just an informational message and can be safely ignored. The script is assuming you have an external Holybro GPS / Magnetometer / LED unit attached and those i2c failure messages are indicating that it isn't detecting the Holybro unit. In the third screenshot PX4 is not crashing either. When you start PX4 for the first time it will look for the standard parameters file in /data/px4/param/parameters. If it does not find that file it will set a bunch of default parameters for you but it will not start the DSP portion of PX4 to do this and so you see those timeout errors which are completely expected for this process. All of this behavior is controlled by the files /usr/bin/voxl-px4 and /etc/modalai/voxl-px4.config. Both of these are bash scripts and are only provided as reference. You can modify these however you want to fit your particular use case.

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

[image: 1671029064348-whatsapp-image-2022-12-14-at-15.29.48.jpeg] Here is the weight in a balance with and without power module. [image: 1671029207466-whatsapp-image-2022-12-14-at-15.46.24.jpeg] For our application, we will change the huge 12AWG cables and XT60 connectors for short 18AWG cables and XT30 connectors. Eloi Vilalta

Hi @Tamas-Pal-0 , You can calibrate outside of the system fully using something like this: https://www.youtube.com/watch?v=OOplk52R4no I've not done this myself.... but it's the original way to do this from what I understand

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]

Hi @Mark-Lee , Chad is correct in that we have not tried it, but my idea is that if you wanted to access the Linux shell on the modem card, you would need a modem development platform from Quectel. Here is an example I found online (please do your research to ensure this will work for you, but I do see they mention serial port access): https://www.aliexpress.us/item/3256803611119964.html?gatewayAdapt=glo2usa4itemAdapt&_randl_shipto=US In our architectures, we do have a mechanism to talk to the serial port over software using one of the QUPs, but there has been no need to do so, and would be a costly SW expense to develop it. If you are willing to void your warranty (not recommended), I can show you which resistors have it and you could try to solder on to them, but you are better off with the Dev Kit IMHO.

@Vinny Sounds good, I'll look at the expansion board for J3. In the past, I've had issues maintaining 40MB/s write speeds over USB2, not sure if it was hardware or software, but thus my jump to USB3. Thanks for the info about the Mythic, I'll reach out regarding that.

I've been meaning to get this into a user guide as well, but for the applications processor GPIO, here's an example of setting IO programmatically, in this case GPIOs 46/159: https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-bind/-/blob/master/src/voxl-bind.c#L58 https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-bind/-/blob/master/src/voxl-bind.c#L147

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