Topics created by DarkKnightCH

@DarkKnightCH Use a flat tipped screwdriver or similar device to slowly pry it out. Take your time working both sides of the the Hirose connector. Take care as the pins can get bent if too much force is applied

Hey the answer is yes.
I use DroneBridge for ESP32 but I believe there's a ton of other similar mavlink apps for ESPs.
cheers

@Anubhav and @DarkKnightCH: Was there any movement on this?

We have 7 drones with FCv2 (all of our other m500 drones have different FC's) that were also sent to us with the wrong radios. We were able to reconfigure the PX4 for the desired radios (and confirm RC connection to QGC), but running voxl-mavlink-server manually shows a UART error on the console. We are RMA'ing the 7 units with the bad mavlink back to ModalAI for a fix, but it would be great to save the shipping if a fix was found here.

I think you'll need to create a new service that behaves like voxl-qvio-server ? That might be the easiest if you want to drop it. Maybe try copying qvio-server and modifying to publish mocap data?

Hello @DarkKnightCH , the mixer file does not only define the AUX1 and AUX2. Please note this line, which specify the configuration of a quadrotor in X orientation : https://github.com/modalai/px4-firmware/blob/1.11.3/ROMFS/px4fmu_common/mixers/quad_x.main.mix#L1 , specifically R: 4x

I tried another way to implement this. Currently my flight core is disconnected to the VOXL. I use my laptop as the companion computer, and then I add a ESP Wifi module to Flight Core TELEM1, so my laptop will get the motion capture pose by using vrpn_client_ros, the mavros will transfer the motion capture pose to mavlink data and then send to flight core.

In this case, my EKF2 will converge. The new issue is that the modalAI cannot hover at it's height on flight mode or hold mode, and the modalAI will drift. Also, the mavros terminal will show:"RTT too high for timesync: 78 ms". I am not sure if this is the reason that the modalAI will drifting in position mode.

Any suggestion?

sorry for the slow reply. We have a bunch of data from our dyno bench here

Hi @DarkKnightCH ,

We offer other receivers to be installed on the m500 as well, but roughly:

weight and size, indoor flying was a primary first use case, spectrum is good for that. For outdoor it works but the range isn’t great, so you could use another receiver. The satellite receiver 100 percent works as we’ve shipped hundreds in this config, but please choose from the options that fit your need for longer range. If you need BVLOS, consider LTE instead, but you should be savvy to setup a VPN server!

No main reciever needed. The satellite receiver is put into binding mode via a button in QGC. We’ve bound hundreds of vehicles this way. After pressing the button, the reciever flashes it’s LED quickly to indicate it’s in binding mode.

Please note, there are knock offs “spektrums” in the world that may not work.

Hi @DarkKnightCH ,

It's likely something you can setup in your transmitter, or perhaps reset the transmitter to default state. What make and model do you have?

Also, is it possible to log the IMU data of PX4? Will you provide some library functions to implement that?

Thank you for your reply. I have checked the code link that you shared, and Could I know the shared code runs in companion computer(based on linux) or the processor in PX4? What's more, currently I have a Motion Capture(Optitrack), and they provide a python SDK for data streaming. Is it possible that I run the python code to get the pose data of quadcopter and then integrate it with vio_manager.c ?

Another question is that is there a display device interface in companion computer(based on linux)? I really want to do programming in graphical Linux interface