Connect the VOXL 2 I/O using the UART port on the 5G modem

SMRazaRizvi

Thanks @Alex-Kushleyev and @Eric-Katzfey

To avoid the complexity, I've now connected my RTK-GPS to the configuration described here: https://docs.modalai.com/voxl2-guides-onboard-offboard-sensors/#external-gps-mag--gnss

I'm getting the coordinate position and I am now in the process of setting the correct parameters to be set for the new GPS.

To confirm, I only have to adjust PX4 parameters, right?

Eric Katzfey

@SMRazaRizvi We have not integrated an RTK GPS receiver before so cannot comment on the steps needed to get it working properly. Perhaps the manufacturer of the RTK GPS unit can provide some guidance on how to use it with PX4? Or the PX4 community? But if you are seeing valid data from the unit then at least the hardware seems to be connected properly.

SMRazaRizvi

@Eric-Katzfey I see.

Actually connecting my RTK-GPS to the configuration described here: https://docs.modalai.com/voxl2-guides-onboard-offboard-sensors/#external-gps-mag--gnss was not giving me RTK corrections so I am now using the J9 connector on the 5G modem, and that works fine.

But another problem that I am facing is Compass Sensor 0 missing.
Do you think there's some setting of the default compass that was being picked up by PX4 with the M8N GPS that came with the drone? Where can I configure the compass?

Alex Kushleyev

@SMRazaRizvi ,

compass driver is started inside the voxl-px4 start-up script : /usr/bin/voxl-px4-start

# Auto detect the magnetometer. If one or both of these devices
# are not connected it will fail but not cause any harm.
/bin/echo "Looking for qmc5883l magnetometer"
qshell qmc5883l start -R 10 -X -b 1
/bin/echo "Looking for ist8310 magnetometer"
qshell ist8310 start -R 10 -X -b 1

please note that both of these drivers are expecting the compass to be connected to the DSP i2c ports. We currently don't have compass driver that can run on the cpu side (unlike GPS). However, you could potentially splice the connection for GND, SDA, SCL and connect the i2c bus to J19 on VOXL2, so that you can use the DSP driver for the compass.. Is that an option for you?

Alex Kushleyev

Regarding the RTK corrections not working while GPS is connected to the DSP, I am assuming you have an RTK service that downloads the data from internet and sends a mavlink message with the corrections. That mavlink message needs to be consumed by the gps driver and rtk corrections forwarded to the GPS receiver via UART. If this is not happening, then perhaps the mavlink message never gets to the GPS driver inside the DSP, potentially being filtered out somewhere (mavlink manager?). I don't have deep enough knowledge there, maybe others can comment.

SMRazaRizvi

@Alex-Kushleyev But the RTK corrections come in when I connect the RTK to the 5G modem over J9. What do you think makes a difference here?

Alex Kushleyev

@SMRazaRizvi When you connect the GPS to J9, you start the GPS driver on the cpu side, so there is probably nothing that filters out the mavlink messages with corrections between the rtk mavlink service and your gps driver.

When starting GPS driver on the DSP, there may be a filter somewhere that prevents the rtk corrections mavlink message from reaching the DSP.

That is my guess

SMRazaRizvi

@Alex-Kushleyev I see.
I'll try to splice the connection for GND, SDA, and SCL and connect them to the J19 on VOXL2.

In this case, should the GND, SDA, and SCL pins be connected to both the J9 on the 5G modem and the J19, or just to the J19?

Alex Kushleyev

@SMRazaRizvi just J19 for gnd, sda and scl.

Then you still have gnd, 3.3V, rx, tx going to GPS.

SMRazaRizvi

@Alex-Kushleyev Works like a magic!!
Thank you so much

Alex Kushleyev

@SMRazaRizvi awesome..

I want to look into why running the GPS driver on the DSP did not result in RTK corrections getting through.. This would simplify your setup.

Can you please help me by telling me the topic name that is published by the RTK (rtcm) publishing app? I think it is just not going through to the DSP (being filtered out) for some reason. Also, just curious what app are you using to publish the mavlink messages with RTK (rtcm) corrections?

Alex

SMRazaRizvi

@Alex-Kushleyev Sure.

But currently, I've crashed my drone after it suddenly flipped 180 roll, and crashed on the ground while I was flying.

For some Here's the log:

https://review.px4.io/plot_app?log=2a41a57f-5028-4619-88dd-cebdde721026

Can you see what's the issue here?

Alex Kushleyev

@SMRazaRizvi ,

I took a quick look, at the very end it looks like motor 2 (green) was commanded zero output

If the PWM range on VOXL2_IO is not calibrated properly, if the mixer is outputting zero, it could result in VOXL2_IO commanding low enough PWM to motor that can cause it to stop.

Can you please let me know if your motors are spinning right after you arm the vehicle (but before you raise the thrust), or they spin up only after you arm AND then raise the throttle stick?

SMRazaRizvi

@Alex-Kushleyev The motors were all working fine since the start. I flew the drone for a while actually and then it suddenly crashed.

Alex Kushleyev

@SMRazaRizvi , As I mentioned in my previous post, the plot shows that for some reason there was a command for Motor 2 to go to zero (which would convert to the minimum PWM value of 1000). Do you remember if you have performed some aggressive maneuver at the end, which would trigger this?

Also, can you please perform acuator test using GCS and figure out at which actuator output value, your motors actually spin up?