Topics created by gauravshukla914

@gauravshukla914 I also noticed it. Somehow on the drone's ROS indigo system. roslaunch voxl_mpa_to_ros voxl_map_to_ros.launch won't honor the existing ROS_MASTER_URI, it always source ROS_MASTER_URI etc from my_ros_env.sh

Please see email thread in progress, if possible let's use one channel for communications.

Thanks @Chad-Sweet for your reply. So I did not try the PID method, but instead used a new 3S lipo battery to replicate the previous flight behaviour. The first test was a huge success and the drone flew well even while facing the other sides. But further tests, the power avionics issue has come back again and the tests are now inconsistent. Sometimes it flies well and sometimes its going haywire, but almost getting the avionics power low issue every time.

Could this be the power module issue? Anyway I've ordered power module and my next step is to replace with a new power module and test. But is there anything that you could suggest?

Hi Gaurav, please refer to QGroundControl's documentation on the battery monitoring setup here

It is glued to hold the focus. Turn gently, but forcefully, and the glue will break

Thank you @Chad-Sweet for your reply.

Hi @Alex-Gardner,

I followed to tune params which you suggested in above, but still am not able get optimal dense pointcloud points. Is there any alternative approach in need to follow or i need combine any other depth sensor along with existing stereo..

@gauravshukla914

voxl_bug.png

i have this issue, how switching to imu1? thanks

@Prasad-Antervedi Try following these: https://docs.modalai.com/calibrate-cameras/

@gauravshukla914 no problem, glad it helped

Do you have a GPS/Mag plugged in? If not please try plugging in a GPS/Mag and set the PX4 parameter SYS_HAS_MAG to 1. There is a PX4 bug that prevents VIO-only operation if a magnetometer is missing, even if the magnetometer is not in use.

We've been trying to get the bugfix approved and merged into PX4 master for over a year now but it seems to be a lost cause. For now our own branch of PX4 has the bugfix along with some custom tools for our ESCs. If your system starts working again with the magnetometer then we know somehow a standard PX4 image got onto your flight core instead of one of our own.

Regards,
James

@modaltb Yes you're right. Its not connecting to QGC via usb too.

The only lower bound I've seen is 20cm here:
https://gitlab.com/voxl-public/modal-pipe-architecture/voxl-vision-px4/-/blob/master/src/voa_manager.c#L165

So I'm still puzzled.

If you debug stereo, what kind of data are you seeing? https://docs.modalai.com/voxl-vision-px4-collision-prevention/#debug-tools

@gauravshukla914 ,

I for the first time got the "avionics power low" message! I turned off the ADCs on FlightCore for a test and got this error.

PX4 monitors the 5VDC rail (and 3.3VDC), and this makes sense now, as the output of that power module was lower than expected.

Anyhow, I remembered this post so figured I'd put some details here while I saw it 😉

@gauravshukla914
Great, thanks for the response. Glad we could help.
Just FYI, that 2A 5V BEC will not properly power a Voxl, nor would any 5V supply though any of the JST or Hirose connectors, although you may see Voxl try to power up.
In those conditions, be sure to use our Power Module as the main 5V so it has a successful power up. This is the only connector that was designed to support the current demand Voxl needs during power up: https://docs.modalai.com/voxl-flight-datasheet-connectors/#j1013---5v-dc-power-input-i2c3-to-power-cable-apm
https://docs.modalai.com/power-module-v3-datasheet/

Be sure to reach out with any additional questions.
Thanks!
Vinny

Looks like we used the 7" one here