Troubleshooting

Here are some common issues that you could face with your ZED Box 2 Max.

If you are unable to resolve your issue using the following suggestions, please reach out to us at support@stereolabs.com for further assistance.

ZED Box 2 Max not booting

If your ZED Box 2 Max does not turn on after a shutdown, follow these steps to diagnose the issue.

1. Check Power Connection

• Make sure that only one power input is connected: the DC terminal block or the USB Type-C power input. The first source connected is the one used.
• With the DC terminal block:
  • Switch off the power source and unplug the terminal block.
  • Check with a voltmeter that the voltage of the power source is between 9V and 36V, and that the polarity matches the power input pinout.
  • Check that the wires are firmly tightened in the terminal block.
  • If the voltage is correct, replug the terminal block and switch on the power source, otherwise fix your power source.
• With the USB Type-C power input, check that your USB PD power supply provides at least 40W at a voltage between 9V and 28V. This power input is not recommended for now: prefer the DC terminal block.
• If your own power source is wired to the terminal block, check that the supply is connected to DC IN (pin #1), not to ACC (pin #3).
• Press the PWR button on the front panel.

2. Check the Serial Console

Connect to the device through the Serial Console and power it on:

• Boot messages are displayed: this indicates a software issue. The ZED Box 2 Max software may have been corrupted due to an improper shutdown, or the internal disk may be full.
  • If you can log in, use df -h to verify if the internal disk is full, and free up some space.
  • Otherwise, contact StereoLabs Support for further assistance.
• No boot message is displayed: this suggests a possible file system or hardware failure.
  • Contact StereoLabs Support for further assistance.

The device shuts down or throttles when powered through USB Type-C

The USB Type-C power input is not recommended for now. It provides up to 130W, which is not enough for the 120W and MAXN power modes of the T5000 module, nor for the PoE+ ports.

• Power the ZED Box 2 Max through the DC terminal block.
• If you must use the USB Type-C power input, select the 90W or the 70W power mode, and use a USB PD power supply that provides the highest power available, up to 130W.

The GMSL2 cameras are not detected

If one or more GMSL2 cameras are not detected by the ZED SDK:

• Check that the cameras were connected before powering on the ZED Box 2 Max. GMSL2 cameras are not hot-pluggable: after any change, reboot the device or restart the ZED X daemon with sudo systemctl restart zed_x_daemon.service.
• Check that each FAKRA connector is fully inserted, with a “click”.
• Check that the GMSL2 driver is installed and matches your L4T version: dpkg -l | grep stereolabs. Reinstall it if needed, as described in Using GMSL.
• List the detected cameras with ZED_Explorer --all.

The CAN interface does not receive any frame

• The CAN FD buses are available on the T5000 model only.

• Check that the interface is up, with the correct bit rates: ip -details link show type can.

• Check that CANH and CANL are not swapped, and that the ground of the bus is connected: ISO_GND (pin A5) for the isolated CAN 0 bus, GND for the CAN 1 to CAN 3 buses. Read the Expansion I/O pinout.

• Check that both ends of the bus are terminated with a 120 Ω resistor.

• Check that all the nodes of the bus use the same mode, classic CAN or CAN FD, and the same bit rates.

• Check that at least one other node acknowledges the frames on the bus: on a bus with no other active node, the interface enters the error-passive or bus-off state. Reset it with:

  sudo ip link set can0 down
  sudo ip link set can0 type can bitrate 500000 dbitrate 2000000 fd on restart-ms 100
  sudo ip link set can0 up

The WiFi does not work anymore after a system update

After daily operating system updates, the WiFi module on the ZED Box 2 Max may stop working.

This issue occurs when the Ubuntu Software Updater or apt installs an incorrect WiFi driver.

Solution

Follow these steps to remove the incorrect firmware file and reload the correct driver:

Remove the incorrect firmware file

Run the following command to delete the problematic firmware file:

sudo rm /lib/firmware/iwlwifi-ty-a0-gf-a0-66.ucode

Now you can reboot the device (sudo reboot) to automatically load the correct driver, or load it manually without rebooting.

Unload the incorrect driver

Unload the currently loaded (incorrect) WiFi driver:

sudo modprobe -r iwlwifi

Load the correct driver

Reload the correct default WiFi driver:

sudo modprobe iwlwifi

After completing these steps, your WiFi module should function properly again.

Contact Support

If you are unable to resolve your issue, please visit our community forum or contact support@stereolabs.com for further assistance.