@stevet Thanks! We actually do have these, maybe we can just figure out the FOV of each camera from the respective data sheets.

@Moderator

I didn't use docker.
(certainly, the screenshot folder looks like inside docker)

This problem was solved in another way
I made a mistake in the port to insert the micro USB.

スクリーンショット 2022-05-07 143058.jpg

Thank you.

@沈-宏澤 Do you solve your problem?
How to solve it?

Thanks for the heads up!

@Philemon-Benner No problem. But that's exactly why the decimator is there. It's often nicer to see lower frame rate with higher image quality.

In general, yes Microhard is designed for point to point robustness at longer range. Like all radios, your mileage may vary.

We have a px4io board that will be in beta soon. It will enable more RC options. Do you have a specific protocol you are looking for?

@Chuck-Bokath Sounds like you were able to get a connection going? If not, I was going to suggest adding your ground station's IP to the voxl-vision-px4 config file under the qgc_ip setting.

We have posted the Sentinel CAD which has some of the s500 components embedded. We don't have the s500 frame as is.

https://docs.modalai.com/sentinel-functional-description/#3d-step

We have posted the Sentinel CAD which has the flight deck embedded.

https://docs.modalai.com/sentinel-functional-description/#3d-step

@chaitanya Sorry. My goal is that cell phone can control VOXL flight deck.
Therefore, I need a MAVSDK library( e.g. libmavsdk.so) at Android. Then I can use the library to send command to control VOXL flight deck.

Hi @steveb2014 ,

Using a TELEM port should get you the same interface as standard Pixhawks, perhaps some params need to be changed for baud etc.

Do you have specific issues or errors you are seeing?

Thanks!

Also, some info on our use of a gimbal with FlightCore here --> https://docs.modalai.com/voxl-m500-gimbal-user-guide/ although it was using a little 2-axis PWM controlled gimbal.... I think the MAVLink approach is better.

@Alex-Gardner Thank you, that fixed the issue.

Thank you for your reply. Actually, I was using VOXL in a softAP mode and not in Station Mode that's why I was facing this issue.

Thank you so much sir, Its working now

I had the same issue. Updating the voxl_mpa_to_ros package resolved it for me:

opkg update opkg install voxl-nodes

@Djalma-Ribeiro You can create a systemd service file and enable it to run on boot and have it execute the OpenVPN connection command.

Here is an example on how we have used it in the past on a VOXL:

[Unit] After=voxl-time-sync.service Requires=voxl-time-sync.service [Service] Type=forking ExecStartPre=/bin/sleep 2 ExecStart=/usr/sbin/openvpn --script-security 2 --daemon --config /etc/openvpn/KEY_FILE [Install] WantedBy=default.target

Won't be exactly the same as above but that's the general idea.

Dan,

Check out this thread: https://forum.modalai.com/topic/589/flying-in-poorly-lit-conditions?_=1654205018092

TLDR is you need enough features for QVIO to pick points out for VIO. So you either need a diffuse light source that can illuminate features or some other low-light sensor that you would need to integrate with QVIO.

Hi @Matt-Turi !
Thank your information!