MotoSAT J1 User And Installation Manual page 73

1. Power cycle the controller and check connections at the mount and on the controller.
2. Perform nvclear command from the J1boot% prompt in a telnet session power cycle the unit
and reconfigure the controller.
3. Perform ucbupdate command from the DATASTORM% prompt in a telnet session.
4. Contact MotoSAT support for possible parts replacement.
-8 Handshake error
Issue: This message should only be displayed in debug mode for use when compiling newer
versions of software if this massage appears during normal use:
Resolutions:
1. Power cycle the controller and check connections at the mount and on the controller.
2. Perform nvclear command from the J1boot% prompt in a telnet session power cycle the unit
and reconfigure the controller.
3. Perform ucbupdate command from the DATASTORM% prompt in a telnet session.
4. Contact MotoSAT support for possible parts replacement.
-9 Operation timeout
Issue: Can bus error. (UCB to J1 communication error)
Resolution:
12volt PS on 15 Volt System
1. Ensure the J1 power supply is supplying the correct voltage and amperage for the specific
mount it is controlling.
2. Power cycle the controller and check connections at the mount and on the controller.
3. Perform nvclear command from the J1boot% prompt in a telnet session power cycle the unit
and reconfigure the controller.
4. Perform ucbupdate command from the DATASTORM% prompt in a telnet session.
5. Using the mounts wiring diagram perform an OHMS test and ensure the system is within
tolerances.
6. Contact MotoSAT support for possible parts replacement.
-10 "PC Serial timeout",
Not used obsolete.
-11 Mount A/D failure
Issue: UCU is not functioning properly
1. Power cycle the controller and check connections at the mount and on the controller.
2. Perform ucbupdate command from the DATASTORM% prompt in a telnet session.
3. Contact MotoSAT support for possible replacement.
-12 Invalid pointer
Issue: N/A = This message should only be displayed in debug mode for use when compiling
newer versions of software if this massage appears during normal use:
Resolutions:
1. Power cycle the controller and check connections at the mount and on the controller.
2. Perform nvclear command from the J1boot% prompt in a telnet session power cycle the unit
and reconfigure the controller.
73