Hi @Matthew-Howlett ,

No the m500 currently has a BMP388.

Little more detail, we've validated with FrSky X8R reciever and Taranis X7 transmitter with the following setup:

We have a new cable about to come out to assist with this wiring as well:
https://docs.modalai.com/cable-datasheets/#mcbl-00018

Hi @rapit ,

OK we validated that a USB3 device can show up, here's a "guide", but there's no new info really, just an example: https://docs.modalai.com/voxl-as-usb-host/

-Travis

The official product documentation is located at https://docs.modalai.com/

The purpose of this forum is to supplement that documentation, and to update the official docs when we find information missing.

Hi @mrawding ,

The current early release on the EVT hardware relies on gstreamer.... for example:

cd /data/misc/camera
rm *

gst-launch-1.0 -e qtiqmmfsrc camera=0 name=tracker ! video/x-h264,format=NV12,width=640,height=480,framerate=30/1 ! queue ! h264parse ! avdec_h264 ! videoconvert ! pngenc ! multifilesink enable-last-sample=false location="/data/misc/camera/cam0_img_%d_.png"

This will save images to the path specified. We're actively working on getting the same interfacing as VOXL up on this ;). Next few weeks should have some good PUBLIC REPO updates.

@Gaurav-Borade , we have one in the works that should be ready shortly, I'll send a link once we get it posted!

Hi @gauravshukla914,

If voxl-vision-px4 is setup for VOA it will connect to the stereo and 'take over', if that's the case can you try the following before launching?

systemctl stop voxl-vision-px4

FYI for the future, the MPA architecture (https://gitlab.com/voxl-public/modal-pipe-architecture) will provide 'fan out' and allow multiple clients for a given camera.

Hi @mrawding ,

You are correct, there's something wrong, and I'm investigating this now.

The UART is active after bootup but then something fishy is happening.

When used with PX4 (ran on bootup) there's no issue.

I'll post here when there's an update to fix.

Hi @gauravshukla914 ,

Our flight controller is a little unique in that it can't be powered off USB so yes, it will lose power and connection during the standard process. (The reason being our Flight Controller shares the 5V rail with the companion computer and 500mA off USB won't suffice!)

To get around this, we have a tool that has a user guide here:
https://docs.modalai.com/flight-core-pwm-esc-calibration/

This allows you to keep the battery connected during the ESC calibration process.

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 @yu-zhang ,

Short answer: we don't use that button/switch, and 22027 disables the FW from requiring it (as far as I know).

As we use a 6-pin JST connector for our GPS connector, and don't route the actual switch/button line from the mast down to the board, there's no way for that to actual work with the 6-pin version.

Our firmware by default sets that 22027 value to make it so we don't need to press the button (since the wire doesn't actually route, you'd need the 10 pin GSP to do that...).

If someone needs to use this feature, the pin is exposed here instead: https://docs.modalai.com/voxl-flight-datasheet-connectors/#j1011---i2c2-safety-button-input

Thanks for the logs @Jagatpreet-Singh-Nir , we'll need to dig into this. It seems like it's not being detected, we attempted a different device an believe to have replicated what you're seeing. We'll reach out with updates as we have them. Thanks!

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.

@Andrew-Keefe nice one!!!!! I actually hadn't thought of this simple approach! I see no issue here. The "no power via USB" is something that has bugged me for a while.......
The original reason is that this design is shared with VOXL-Flight and we can't power VOXL-Flight off USB, but if/when next rev goes out the door, we'll make a modification to change this.

For now, you mind if I steal these photos and put on our docs?

Hi @janis_blank ,

A quick browse of those range finders showed some with I2C interfaces.

Now, we don't have all drivers possible starting in PX4, so this might not work out of the box. Here's the drivers available: https://github.com/modalai/px4-firmware/blob/modalai-1.11/boards/modalai/fc-v1/default.cmake#L17

There's a spare I2C port though likely available on the hardware for you, J13 on FlightCore:
https://docs.modalai.com/flight-core-datasheets-connectors/#j13---i2c-display--i2c2-bus--safety-switch-connector

You may need to enable drivers and then alter startup to get to work, here: https://github.com/modalai/px4-firmware/blob/modalai-1.11/boards/modalai/fc-v1/init/rc.board_sensors

But in theory using I2C you should be able to get data from the range finders (it wouldn't be integrated into voxl-* tools, rather just used by PX4 though)

Hi @janis_blank ,

In theory yes, it's 3.3V TTL with 5V power supply on that connector.

There are MAVLink baud rate settings and mode that you may need to configure.

We sell the FlightCore stand alone, which is a low cost way to test the theory out as well, but I'm not seeing a huge risk on the system connection.

Hi @janis_blank ,

We haven't integrated this ourselves before.... we had tried some PWM based gimbal controllers and did not like the end result... mainly the control interface was lacking with our PWM setup (8 channel, no extra PX4IO).

The m500 has VOXL-Flight, which has spare TELEM ports available, so the interface should be available.

There could be small tweaks to params for flight performance, but in general I don't think it would affect stability. I can check with the flight guys who know more about that, but I remember slapping a small gimbal on without needing to tweak much....

Are you using this gimbal controller elsewhere with PX4 on another flight controller?

Hi @frafrat ,

Not yet but we are working on it currently. I don't have a hard date for a release, but the plan so far is to get support onto the QRB5165 platform within the next month or two.

Thanks!
Travis

Hi @rohitpillai ,

Sorry I had this queued to send but didn't send it!

If it's VOXL-Flight, you have PWM outputs you might be able to use if you have a quad setup.

See this as a possible option, where you can setup an RC channel (via the controller) to trigger the channel and possibly activate the buzzer (assuming it has a PWM interface).

This looks like PWM interface. Are you using "VOXL" or "VOXL-Flight"? VOXL Flight has PWM outputs, normally 4 are used for the ESCs, but the system can use the 'aux RC passthrough' as a means to trigger this signal. Does the buzzer normally get triggered by the user or automatically via some logic?