Issue with GNSS Data on ZED Box Orin NX 16GB with ZED-F9P GPS RTK

Hardware ZED Box
,
1

Description: I recently purchased a ZED Box Orin NX 16GB with the GPS Option: GPS RTK U-blox ZED-F9P and am trying to access GNSS data, but I am not receiving any output as expected.

Setup Details:

  • Hardware:
    • ZED Box Orin NX 16GB
    • GPS RTK U-blox ZED-F9P
    • Ublox ANN-MB-00-00 L1,L2 multi-band antenna
  • Software:
    • ZED SDK 4.2
  • Configuration:
    • GPS RTK is enabled and properly wired to the ZED Box

Steps Taken:

  1. Connected the given GNSS module (Ublox ANN-MB-00-00 L1, L2 multi-band antenna) to the ZED Box.
  2. Followed the installation steps as per the official guide: Using GNSS on Linux.
  3. Executed the cat /dev/ttyACM0 command, but did not receive the expected output as shown in the documentation.
  4. Ran xgps , but no GNSS data was displayed.
  5. Cross-checked system timestamp settings, and they appear to be correct.

Issue Observed:

Screenshot 2025-03-06 at 9.12.38 PM
Screenshot 2025-03-06 at 9.12.38 PM1002×926 59.6 KB

Expected Outcome:

  • Running cat /dev/ttyACM0 should display GNSS data output.
  • xgps should show the satellite fix and GNSS data.

Request for Assistance:

  • Are there any additional steps to verify the GNSS module connection and data output?
  • Could there be a driver or permission issue preventing access to the GNSS data?
  • Are there any known compatibility issues with ZED SDK 4.2 and the ZED-F9P module?

Any guidance or troubleshooting steps would be greatly appreciated.

Thank you!

2

Hi @karthikreddy157
have you read our online documentation here?

Does it work for you?

3

You may need to nuke the systemd controlled gpsd service first.

My memory is foggy on it, but I encountered the same issue, where the gpsd socket was being controlled by a non-functional instance of gpsd, and preventing me from launching it properly.

4

Hi Team,

Thanks for your support.

My knowledge of systemd is minimal, but through some research, I learned that it is useful for parallel service startup. It seems that creating another user on the system caused this issue. After removing that user and running the following commands, followed by a system restart, the GPS service started working successfully:

sudo systemctl stop gpsd.socket  
sudo systemctl stop gpsd.service  
sudo systemctl disable gpsd.socket  
sudo systemctl disable gpsd.service

I’d like to understand—did creating another user cause this issue? I haven’t installed or modified systemd directly, so I’m trying to pinpoint the exact reason behind this behavior.

Looking forward to your insights.
Thank You

5

We recommend not using the gpsd with systems:

In any case, did you add the new user to all the required user groups, i.e. dialout?

6

Actually yes, i created new user for that user i run these cmds

sudo adduser $USER dialout
sudo adduser $USER tty
7

systemd is the default service manager, and already exists on your system. It does sometimes create issues like this though where you need to have finer control over the running services.

Killing the systemd gpsd service should probably be part of SL’s install guide.