UM982 isn't providing heading data

MuhammadBilal1 · November 8, 2023, 11:10am

Hi,
We bought H-RTK Unicore UM982 (Dual Antenna) from Holybro a few months ago to use in our UAV.

Purpose of using UM982:
The purpose of buying this item was to fix the YAW problem (UAV not turning in Mission flight) which was due to the higher amount of EMF around the GPS module (M8N) and the Pixhawk 4.

UAV Setup details:

GPS Module: H-RTK Unicore UM982 (Dual Antenna)
AutoPilot: Pixhawk 6C (GPS port 1)
Firmware: PX4 (1.14.0 stable)
Antennas Configuration: Primary Antenna (Nose), Secondary Antenna (Tail) (distance among both is almost 50cm)

We followed all the installation instructions on the PX4 and Holybro UM982 websites.

Issue:

We aren’t getting the data of the heading. Moreover, we are losing the GPS position data as well.
Our UAV shows it’s in position flight mode, but the logs show the position data is missing during the flight (Position mode).
We tried to do a mission flight, but it immediately went to Altitude mode because of no global position. Here (flightreview) is the log of that flight.

Verification of Heading Data on Uprecise application:
To verify the heading data from the UM982, we connect the UM982 directly with laptop using the USB C type cable and installed the Uprecise application.

Upon checking the heading information from the “Messages” tab under the “NMEA” section, we found out that the “HDT” & “TRA” are disabled and no heading data is available in the “VTG” tab also.

We checked the configurations under the “Receiver Configurations - Message configuration” and found out that all “NMEA Message” protocols are unchecked.

Upon enabling all options under the “NMEA Message” and HEADING/HEADING2 options under “Unicore Message”, we found out that now heading information is appearing in the “Message - VTG”. After seeing the data of heading in “Message - VTG”, we connected the UM982 with Pixhawk as told above, but still the heading data isn’t available in the mavlink inspector section.

We then again connected the UM982 with laptop via USB C cable, and found out that the “Message - VTG” is again not showing the data.

Upon disconnecting and connecting the UM982 again to laptop after saving the “NMEA Message”, the heading data goes away. (Maybe an EPROM issue)

Tried solutions?
1- We reset the UM982 module using the Uprecise application and the instructions from the Holybro documentation. But the result is same.
2- Tried the command UNIHEADINGA COM1 0.2 in Uprecise. But still the result is same.
3- Tried the following commands, but the solution is still not working.

FRESET
GPGGA COM1 0.2  
GPRMC COM1 0.2
AGRICA COM1 0.2
UNIHEADINGA COM1 0.2
config com1 230400
saveconfig

All the detailed snapshots are attached with this post.
Please do let us know if you need more information.

JulianOes · November 10, 2023, 10:12pm

One comment on “heading: nan”. This is because the heading field is always immediately set back to nan after a value is published. So when you do gps status, it’s likely nan.

This means that heading should still work even if you see NaN there.

Now, do you have a flight log, or just a log outside where it logs GPS data? If so, please upload it with logs.px4.io and share the link here, and I’ll take a look.

MuhammadBilal1 · November 11, 2023, 6:27am

Yes, I do have the logs.

Here are the links of flight logs we carried with the installation of UM982.

Log # 1 - Mission flight:
https://review.px4.io/plot_app?log=ad2586c0-763f-4b6f-b5e5-98e8bfcb896b

Log # 2 - Position flight:
https://review.px4.io/plot_app?log=b8b0652c-2c53-4df4-b1b6-8685845aac8c

Log # 3 - Position flight:
https://review.px4.io/plot_app?log=d470865e-2b65-4d76-b51f-9dc459acb7be

JulianOes · November 12, 2023, 7:54pm

Right, I don’t see any heading information in the log.

Can you try building from latest release/1.14 branch (not tag) which includes this [BACKPORT v1.14] gps: update submodule by julianoes · Pull Request #22019 · PX4/PX4-Autopilot · GitHub.

So it would be something like:

git switch release/1.14
git pull
git submodule update --init --recursive

And then clean build and flash.

MuhammadBilal1 · November 16, 2023, 11:46am

@JulianOes
I created the new build from the branch that you gave.
Performed a flight from that build and the log is given below.

Log: https://review.px4.io/plot_app?log=a01230a5-f710-4b05-a89f-248c8e557762

I didn’t feel any difference in the performance, but actually, the behavior was aggressive.

JulianOes · November 17, 2023, 1:57am

Thanks for testing. I still don’t see it.

I will have to test this next week.

JulianOes · November 20, 2023, 10:39pm

Ok, I’m trying to reproduce this.

I have flashed latest release/1.14 branch (not the v1.14.0 tag).

And I see this:

    heading: nan
    heading_offset: 0.00000
    heading_accuracy: 0.01496

So heading is nan because it gets overwritten after publishing with NaN each time, however, heading_accuracy is set and tells me it’s working.

And actually, in one of your screenshots above I can see it working as well!

JulianOes · November 20, 2023, 10:54pm

I did a quick test flight and you can see that the heading accuracy is logged but heading itself is not. (I will create a pull request to fix logging of heading for the future.)

You can also see that heading is used in the estimator though.

MuhammadBilal1 · November 21, 2023, 2:00am

Ok.
I will also try to test again in a couple of days hopefully, but what about the test I had done with my drone?

Log # 1 - Mission flight:
https://review.px4.io/plot_app?log=ad2586c0-763f-4b6f-b5e5-98e8bfcb896b

It just rejected the Mission flight mode from the arming and went to Altitude mode.

JulianOes · November 21, 2023, 4:56pm

But it’s in position mode?

MuhammadBilal1 · November 21, 2023, 6:25pm

Sorry, sent the wrong log.
Here is the correct log link:
https://review.px4.io/plot_app?log=778ab7a8-7553-4c9a-b3b8-405423cb188e

We gave a mission and the drone immediately switched to the “Altitude” mode.
Message is visible in the Log messages.

JulianOes · November 23, 2023, 3:55pm

I had a look at the log and I see estimator_status.filter_fault_flags go from 0 to 65536. This means bit 16 is set which is:

github.com

PX4/PX4-Autopilot/blob/a99a7d2abdad4c8f804aabc3bbcddadff0ed8fda/msg/EstimatorStatus.msg#L67


      
          # 6 - true if fusion of the synthetic sideslip constraint has encountered a numerical error
          # 7 - true if fusion of the optical flow X axis has encountered a numerical error
          # 8 - true if fusion of the optical flow Y axis has encountered a numerical error
          # 9 - true if fusion of the North velocity has encountered a numerical error
          # 10 - true if fusion of the East velocity has encountered a numerical error
          # 11 - true if fusion of the Down velocity has encountered a numerical error
          # 12 - true if fusion of the North position has encountered a numerical error
          # 13 - true if fusion of the East position has encountered a numerical error
          # 14 - true if fusion of the Down position has encountered a numerical error
          # 15 - true if bad delta velocity bias estimates have been detected
          # 16 - true if bad vertical accelerometer data has been detected
          # 17 - true if delta velocity data contains clipping (asymmetric railing)
          
          float32 pos_horiz_accuracy # 1-Sigma estimated horizontal position accuracy relative to the estimators origin (m)
          float32 pos_vert_accuracy # 1-Sigma estimated vertical position accuracy relative to the estimators origin (m)
          uint16 innovation_check_flags # Bitmask to indicate pass/fail status of innovation consistency checks
          # 0 - true if velocity observations have been rejected
          # 1 - true if horizontal position observations have been rejected
          # 2 - true if true if vertical position observations have been rejected
          # 3 - true if the X magnetometer observation has been rejected
          # 4 - true if the Y magnetometer observation has been rejected

→ # 16 - true if bad vertical accelerometer data has been detected