Solution
This behavior can occur when required NI-XNET and PXI services are not running correctly or when the system state has not fully initialized. Even after closing applications or rebooting, stale service state can prevent XNET sessions from being created and block firmware synchronization.
To resolve the issue, follow these steps:
Ensure PXI Services Are Running
- Open Windows Services and verify that the following services are running:
- NI PXI Chassis Management
- NI PXI Resource Manager
- NI Route Coordinator
- NI XNET IP Stack
- For NI Route Coordinator and NI-XNET IP Stack, right-click each service, select Properties, and navigate to the Log On tab. Ensure they are configured to run under the Local System Account.
- Restart the services if needed, then reboot the PXI system to allow drivers and services to initialize cleanly.
- After reboot, run a Self-Test in NI MAX or run an Automotive Ethernet shipping example in LabVIEW.
- Open LabVIEW, then navigate to Help >> Find Examples.
- In the Example Finder, ensure you are browsing according to Task.
- Navigate to Hardware Input and Output >> Automotive Ethernet to find the shipping examples.
Update the PXIe-8520's Firmware
With NI‑XNET 2026 Q1, if the PXIe‑8520 firmware is out of date, the firmware update may be triggered implicitly during Self‑Test or XNET session creation. In this case, NI MAX may present the following message:

Once the update is complete, the following message appears instead:

The firmware update is then applied automatically during the restart.
After the reboot completes, the PXIe‑8520 should pass Self‑Test and allow Automotive Ethernet sessions to be created successfully.