Skip to content

ZipNav Watchdog General Troubleshooting

published Last Updated: Oct 9, 2026 HW: all
Applicable alarms (1)
ZIPNAV_WATCHDOG
Likely outcomes (0 missions) — click to expand

Based on 0 missions where this alarm fired in the last 90 days as of 2026-10-13

Aggregated from fleet operations and refreshed daily. Individual outcomes may vary by site and configuration.

This issue may also be described as “Watchdog(s) Inactive: ZipNav”

This watchdog fires when navigation is not publishing necessary information on Compute A or B. This is usually due to required services (like GNSS, IMU, etc) not providing required information to navigation.

Can we see satellites with both receivers?

Section titled “Can we see satellites with both receivers?”

Check gnss_residuals.cn0 from the debug.gpsins topic, along with num_satellites_used from fusion_engine.gnss_info topic, from Compute A and B.

Is there a clear drop in cn0 values?

Steps

There is likely a source of interference nearby, or an electrical/antenna issue.

Refer to troubleshooting steps in this guide: GNSS_A_DEGRADED and GNSS_B_DEGRADED | Troubleshooting Steps

Example investigation

This plot shows a clear loss of signal for the Compute B receiver, indicating an issue with it’s antenna.

newplot (12).png

If not, continue to the next section.

Examine debug.gpsins.update_flags from Compute A and B.

Is HAS_PIM_FOR_EVERY_EPOCH false?

Steps

The IMU on the corresponding compute is likely misbehaving.

If the IMU_TIMESTAMP_ERROR_HIGH alarm is set, follow IMU_TIMESTAMP_ERROR_HIGH.

Otherwise, escalate to Linux Embedded.

Is HAS_ALL_SIGNALS_ON_STARTUP and/or HAS_ALL_SIGNALS_ON_STARTUP_SECONDARY true?

Steps

There is an issue with one or more GNSS receiver.

Determining which receiver(s)

HAS_ALL_SIGNALS_ON_STARTUP points to the receiver local to the compute the message is from. HAS_ALL_SIGNALS_ON_STARTUP_SECONDARY points to the other compute’s receiver.

  • /compute_a.debug.gpsins.update_flags
    • HAS_ALL_SIGNALS_ON_STARTUP: Compute A’s GNSS receiver
    • HAS_ALL_SIGNALS_ON_STARTUP_SECONDARY: Compute B’s GNSS receiver
  • /compute_b.debug.gpsins.update_flags
    • HAS_ALL_SIGNALS_ON_STARTUP: Compute B’s GNSS receiver
    • HAS_ALL_SIGNALS_ON_STARTUP_SECONDARY: Compute A’s GNSS receiver

Did this guide help you get unblocked?

Open suggestions

There are no open suggestions.

Open pull requests

There are no open pull requests.