ModalAI Forum

Moved to https://forum.modalai.com/topic/1481/5g-add-on-board-accessing-the-quectel-module-linux-shell

Hi, we have it on our roadmap but not defined release, we're hoping to do this over summer time. There's a pending Ubuntu 20 release from Qualcomm that we can use but need to port it over to our platform etc.

Thanks for your reply! I got it working. Thank you!

Hi @ComputerDev , The Microhard Modem Carrier Addon (M0048-1 internally) has a USB hub in it already (USB2514Bi), so I'm wondering if we have something funky going on with chaining... Does this only show up with the second hub attached? Good that you are independently powering as that was my next line of though.

It is normal for the CPU to throttle. It cannot run full speed indefinitely without turning down. It is by design and not necessarily a problem unless you need to do more. Any airflow will help though reduce thermal load so you can get more performance out of the system

Hi @Jose-Alfredo-Rosas-Cordova , Sorry for the confusion, "native" meaning nothin special "extra" should be needed when compared to desktop Ubuntu, e.g. --> you should be able to follow this: https://docs.docker.com/engine/install/ubuntu/ For VOXL1, we needed to do some special sauce for Docker, but VOXL2 it should work like you're used to on desktop (from my experience).

@Vinny It's all good. They work fine with soldering. It's more of a pain getting the headers off than anything else. We do stuff like that all the time. I've done 6 or 7 of them already.

@Chad-Sweet Hi, I was able to specify front stereo camera using the below command, 'voxl-calibrate-camera stereo_front -s 7x9 -l 0.02' Thank you!

@Mia-Thomas said in VOXL2 Flir Boson Image Type: YUV422 The first width x height bytes of NV21 and NV12 are the 8-bit luminance values (mono). So, you should be able to publish MONO8 pretty easily with a little extra code.

Hi, Is there any news about ros2 ? Best, Aya

We resolved offline, but ended up have Zach use an STLink. How to build FW is here: https://docs.modalai.com/voxl2-io-firmware/ And here's an example using STLink (download from ST's site...) BL_FW_FILE="modalai_voxl2_io_bl.bin" BL_FLASH_START_ADDR="0x8000000" APP_FW_FILE="modalai_voxl2io-v2.bin" APP_FLASH_START_ADDR="0x08001000" if ! [ -f "${BL_FW_FILE}" ]; then exit 10 fi if ! [ -f "${APP_FW_FILE}" ]; then exit 11 fi echo "erasing..." sleep 1 STM32_Programmer_CLI -c port=SWD -e all echo "programming bootloader..." sleep 1 STM32_Programmer_CLI -c port=SWD -w "${BL_FW_FILE}" "${BL_FLASH_START_ADDR}" -v echo "programming application..." sleep 1 STM32_Programmer_CLI -c port=SWD -w "${APP_FW_FILE}" "${APP_FLASH_START_ADDR}" -v echo "resetting..." sleep 1 STM32_Programmer_CLI -c port=SWD -hardRst

@I_Dwyer Great! Sounds like that VOXL had been run through the voxl-modem-configure setup and the others had not. One other thing I would check is see if the voxl-modem service is enabled with systemctl status voxl-modem, if it's enabled on that one and disabled on the others you may want to disable it with systemctl disable voxl-modem as you may see some network inconsistencies between VOXLs otherwise.

@tom thanks

This page may be useful as well https://docs.modalai.com/voxl2-rc-configs/

If it's one of our 4G modems, then it will be off J3 (you were close !) https://docs.modalai.com/voxl2-connectors/#j3---legacy-board-to-board-connector-b2b For example, here's an image: https://docs.modalai.com/voxl2-hardware-setup/#4g-cellular-connectivity

Thank you. I just realized it said "standard Manufacturer lead time: 34 weeks" but they have plenty in stock. Appreciate it!

Hi, The hardware only supports 2 "processed" streams at a time. This includes color debayering/chromatix/auto exposure/etc. This means you could set up 2 fully processed streams and a third raw stream where you're have to use a third party AE algo (we provide options already through libmodal-exposure in the latest voxl-camera-server) and either just use black and white or do your own color debayer/chromatix job. The last stable packaged release for camera server on VOXL doesn't provide a good support infrastructure for this, but the latest on the master branch of voxl-camera-server has a major rewrite of the code that would support this almost out of the box (you'd just have to add a configuration field for which one is raw). This code has been extensively tested on all of our normal ov7251/9782/imx214/377 and is only not released because we haven't finished support for the TOF sensor (which doesn't seem to be a part of your use case). Lastly, we've only ever used the hires cam in slots 0 and 1, so there's not a pipeline in place for the tracking camera slot, but all you'd have to do to add this is modify the camera_config.xml file in the voxl-camera-server package to copy the IMX214 block once more and change the cameraID to 2. I'll add this in our next release either way, but if you need it sooner that's how to add the pipeline.

Hi @Baylordelrey , Nothing to share at this time, but we'll post info when we can. In general we have bash/python scripts that operate over adb that can test various subsystems.