Topics created by rohitpillai

@rohitpillai Sure it would be the same process as any other linux machine.

Just run:

sudo passwd

Hi @rohitpillai
The intent of the power module is to take direct 2S-6S battery via the XT-60-M, and then pass that power input to two places:

a 5V DC/DC for VOXL / VOXL 2 using the Molex 4-pin with MCBL-00001 (https://docs.modalai.com/cable-datasheets/#mcbl-00001), not the XT-60 Output using the XT-60-F to an ESC/Other VBAT based item in your platform.

Both are measured by the sense resistor when connected properly as we instruct.

In some instances, as in the case of a VOXL 2 Mini, we have configured the Power Module to not output a downstream VBAT using the XT60-F (https://docs.modalai.com/voxl2-mini-power/#voxl-power-module), but a user is easily able to do so.

Hope this helps!

@rohitpillai For remote ID, you need a wifi or bluetooth radio on board. voxl-remote-id uses WiFi. If you deviate from what we support, you will need to implement on your own or find another solution.

I found out that the WiFi dongles were broken which is what was causing the issue 🙂

Thanks for the info! Just to confirm, I am asking about this post ModalAI made on LinkedIn - https://www.linkedin.com/posts/modal-ai_voxl-tof-pmd-activity-7010997849232474112-VV6a?utm_source=share&utm_medium=member_desktop

This update is almost a year out?

Thanks.

It was a custom PCB that we do not have available as a product

Hi,

VOXL Portal doesn't look at anything related to the extrinsics, it's just a debug tool to help visualize the data that's being passed around between the services. Any services that use the data coming from the tof sensor will use the data in the extrinsics config file to reorient the pointcloud to whatever frame that service is using (you can find examples of this in voxl-mapper and voxl-vision-px4).

Thanks will do!

@rohitpillai You can also try to play with the *VEL* parameters from QGC.

I changed a few PX4 params stated in the link you posted. I stopped most voxl services. And then did voxl-calibrate-imu-temps first followed by voxl-calibrate-imu. Rebooted the drone and started/configured all the necessary voxl-services. Now I am able to switch to Position and Altitude. But not Offboard mode. Same error as earlier Check for a valid position estimate The drone is stationary on my desk and not flying. Can I only switch to offboard mode when the drone is in the air? Are there any params that I might be missing to make sure it switches to Offboard mode? Will installing a newer voxl version fix the issue?

Cool I will bring it in today

Thanks for the quick response. This helps a lot!

Yes it should work -- I haven't explicitly tried pointing directly downwards myself. https://docs.modalai.com/flying-without-gps/ has some insight and a nice video about the subject of using VIO outdoors.

It does work at 45* reasonably well especially with enough altitude to pick out features.

Thanks for the reply! Good to know.

Hi Rohit,
Accept my apologies for a delayed response here.

We currently do not offer a combo card that supports both Mythic and Microhard simultaneously.
We do have an architecture that could support Mythic directly, with Microhard as a stand-alone config through our USB Hub. https://www.modalai.com/products/mh-sa
However, we have not had enough interest to make this a formal product as of yet. We do have a proof of concept working for Mythic, but it needs some refinement. We would be looking at a few months to complete that design and get it for sale.

If this is something that you think can be of interest to you, please let us know using our "contact" form so you can reach us to talk about potential volumes and if we could support this for you.

Thanks!

I dropped the faulty VOXL Flight Deck last Monday to your office with the RMA Order number. Is there any update on this?

Thanks!