Hello Team,

This page indicates that the the IMX214 M0025-2 hires cam was tested at full resolution (4208x3120) on the VOXL2. Unfortunately, we can't seem to access images at that resolution with the latest VOXL 2 image. Are we missing anything? More details below

Test configuration:
system-image: 1.4.1-M0054-14.1a-perf
kernel: #1 SMP PREEMPT Thu Oct 13 17:48:16 UTC 2022 4.19.125
hw version: M0054
voxl-suite: 0.9.5

After running "voxl-configure-cameras" and changing the "preview_width" and "preview_height" entries of /etc/modalai/voxl-camera-server.conf to 4208 and 3120 respectively for the hires camera:

"name": "hires",
"enabled":      true,
"frame_rate":   30,
"type": "imx214",
"camera_id":    3,
"preview_width":        4208,
"preview_height":       3120,
"snapshot_width":       3840,
"snapshot_height":      2160

Running "voxl-camera-server" throws the following error:

ERROR:   Camera 3 failed to find supported preview config: 4208x3120
ERROR:   Failed to start camera: hires, exiting

We could verify that 4208x3120 is listed as a supported resolution when running "voxl-camera-server --list"

Stats for camera: 3:
ANDROID_SCALER_AVAILABLE_RAW_SIZES:
        4208x3120, 4096x2160, 2104x1560, 1920x1080, 1280x720,
ANDROID_SCALER_AVAILABLE_PROCESSED_SIZES:
        4208x3120, 4096x2160, 2104x1560, 1920x1080, 1280x 720,

Hello,

I need to access the VOXL2 cameras from a ROS2 node running within a docker container on the VOXL2.

While I am familiar with how to access these cameras in ROS1 in the native Ubuntu image using voxl-mpa-to-ros, I am facing two obstacles here:

1/ The "Qualcomm proprietary 32-bit libraries and services [...] are not available in the Docker environment" (source: https://docs.modalai.com/docker-on-voxl/#running-a-docker-image-with-the-voxl-docker-tool)

2/ the voxl-mpa-to-ros command does not exist for ROS2 (source: https://forum.modalai.com/topic/1168/voxl2-mpa-to-ros2?_=1675704230453)

One possible work-around I thought of could be to:
1/ run voxl-mpa-to-ros in the native Ubuntu host environment to publish the MIPI camera streams in ROS1
2/ run a ROS1->2 bridge to publish the streams on the ROS2 network (e.g.: https://github.com/ros2/ros1_bridge)
3/ subscribe to the new ROS2 camera topics from the ROS2 node running in Docker.

Is this the approach you would recommend, or is there a simpler way to do this?

Thansk @Eric-Katzfey . Do you know if any other similar terminal multiplexer has been tested?

@Eric-Katzfey @plusk01

Curious if you are still using tmux and able to run automatic tmux (or tmuxp) scripts. I have the issue explained here: https://forum.modalai.com/topic/1248/issue-running-tmux-or-tmux-scripts-on-voxl2

which seems related.

Hello,

Is anyone able to run tmux or tmuxp scripts on the VOXL2?

We get the following error message in every terminal we attempt to create automatically. In contract, tmux runs normally when run manually.

"resize: unknown character, exiting"

I tried applying the fix described here: https://forum.modalai.com/topic/312/tmux-and-locale-en_us-utf-8

since it seemed related to tmux and character encoding, but it didn't solve the problem.

Thanks,
Jeff

@Jeff-Delaune said in cannot connect usb camera over USB - C adb port:

MCBL-00022

The cable is available here: https://www.modalai.com/products/usb3-10-pin-jst-cable

Thanks @modaltb . Do you know if the MCBL-00022 cable is still planned to be released this week?

What is the recommended configuration to run the FLIR Boson then, since it is listed in the feature matrix of the VOXL2? https://docs.modalai.com/voxl2-feature-matrix/#specifications

I am having the same issue as @Jagatpreet-Singh-Nir on the USB C with the Boson 640. It seems that I can get the camera recognized on the USB-A port of the VOXL USB Expansion Board, but then I can't use this port for the wifi dongle any more. USB hubs don't seem to work to split this USB-A port between the dongle and the camera.

Thank you Alex!

Hello,

When using the voxl-wifi station command to set up wifi on voxl2, the VOXL was unable to connect to my router until I switched the router security's version and encryption settings to anything else than auto. I was able to repeat the issue on two different routers.

I tested using the Alfa AWUS036ACS 802.11ac AC600 dongle connected through the VOXL USB Expansion board, using either tp-link or a teradec router.

Hope the fix helps others having the same problem, and the problem can be addressed in future voxl images.

Jeff