Hi @gauravshukla914 , Thanks for the help with this. We've released a new beta version of the voxl-hal3-tof-cam-ros that supports auto detection of ToF and defaults the persist.camera.modalai.tof setting properly. It will be in out next voxl-suite release, but is available from our dev channel here if you are interested in using this link The updated readme is here. Thanks!

Hi Bobby, I did some more testing and it seems i can get the IMX377 camera to produce green-ish shades under some lighting conditions. I believe that this is due to AWB somehow incorrectly detecting the scene / lighting type. Let me play with this, I think the solution can be to force a particular scene type so that AWB does not try to guess. In my tests, I pointed the camera at a light gray wall and depending on the angle, it would show up as gray or sometimes a bit green-ish. I will follow up soon.. Alex

@Daniel-Ryu Great to hear! I appreciate your patience with this.

@Alex123 I just realized right now when I was powering up my m500 that I said to use 24VDC in an email.... this is OK for that power module, but the max is 25.2VDC, so no problem dropping it to say 16VDC!

Sorry for the slight delay. I was finally able to get back to this this morning. Killing voxl-rtsp fixed this issue. voxl-cam-ros will launch without issue. Thank you for the help.

@Alex123 here is the exact command I tested with on a VOXL. docker run -it --rm --privileged --net=host --name roskinetic -v /home/root:/root/yoctohome/:rw -v /sdcard:/sdcard -w /root/ roskinetic-xenial:v1.0 /bin/bash Can you try this?

Resetting the parameters to outdoor mode seemed to have worked! The GPS acquired a signal and I am able to fly in Mission mode. Thank you!

pls help me soon. we can set up an online support via teamview to make the problem more clearly.

@Alex123 Glad I could help!

Not exactly familiar with that parameter. Have you seen how we implement mavros here https://docs.modalai.com/mavros? That might help. You might be able to use our voxl-vision-px4 to communicate with the flight controller, vio and mavros code: https://gitlab.com/voxl-public/ros/mavros_test

I tried it with swapped SSRX/TX as you posted in the pinout graphic but unfortunately it is still detected as usb2 device. Any other thoughts? Do I have to adjust some config or should it work out of the box after swapping? Maybe the cable quality or my wiring skills are not good enough, I will try it again with another cable.

Thanks for reporting! We definitely recommend a 6A regulator like the APM ships with the boards. The board will typically use <2A but there are transient peaks when frequencies are changed and definitely on boot.

Configuring to run on boot is documented here For peripherals, you can configure for privelaged mode. voxl-camera-server and voxl-imu-server run on the yocto layer and output their data to pipes which can be accessed inside of the Docker. That's all coming online right now but should be working. For the rest of the peripherials it comes down to what you expose at docker run

@Chad-Sweet oh my godness. My mistaken, i didn't realise that before that i had configured UAV off board mode. when I check the /etc/modalai/voxl-vision-px4.conf the offboard_mode ="figure_eight" => so that's why it's cause the problem here. anyway, it's work again, thank you so much for the effective support

Should I be worried that the US carrier does not cover B7 band?

Thank you, this helped a lot.

As I'm working on this issue, I noticed the following. yocto:/# ifconfig lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:32 errors:0 dropped:0 overruns:0 frame:0 TX packets:32 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2224 (2.1 KiB) TX bytes:2224 (2.1 KiB) wlan0 Link encap:Ethernet HWaddr ::::: inet addr:192.168..** Bcast:192.168..*** Mask:... inet6 addr: :::::**/** Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:467 errors:0 dropped:0 overruns:0 frame:0 TX packets:88 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:3000 RX bytes:40293 (39.3 KiB) TX bytes:10317 (10.0 KiB) https://stackoverflow.com/questions/64028448/error-during-connect-get-http-2fvar2frun2fdocker-sock-v1-40-containers-jso It's not showing any IP address for docker0. How to configure the IP address that will listen to docker daemon on voxl-core board?

@Vũ-Văn-Long wow amazing goodjob

@Chad-Sweet @Alex-Kushleyev We are using voxl_cam_ros, found here https://docs.modalai.com/voxl-cam-ros/ We are running the camera at 1920x1440 Can we even "turn on" AWB when using voxl_cam_ros? As of now we have not found out how to do so. Our team needs to continue with ROS, so we cannot switch to another framework.

I'm sure that's it. I remember now that I had selected a different airframe last time, though I'm not really using the airframe for my code.