Nexus RACE BOX, Инструкция по установке и эксплуатации

Страница: 38 / 44

RaceBox English
37
APPENDIX C – ERROR CODES
When things go wrong, the Race Box will flash its red error light. Different patterns of
flash represent different errors.
No SD Card Detected
If the Race Box does not have an SD card installed when it is powered up, the error
light will flash on and off very slowly.
Just insert the SD card. There is no need to power the Race Box off and on again. After
a second the card will be detected and startup will continue.
SD Card Write Protect On
This is not an error, just a notification. You need not take any action.
If the SD card has its write protect switch turned on, the red error light will flash on for
3⁄4 of a second, then off for 1⁄4 second, then on for 3⁄4 second then off for 1⁄4 second.
This pattern will repeat 6 times, then the RP4N will continue to start normally.
If the write protect switch is on, the Race Box will not write a CSV log or an NXB log,
even if it is configured to do so. It will, however, write an MOB log if the MOB function is
triggered.
No Config File Found
If the Race Box can not find its rp4n.cfg file on the SD card, it will signal a fatal error.
The red error light will flash on for 3⁄4 second, then off for 3⁄4 second. This pattern will
continue until the Race Box is powered down.
Check the SD card to make sure that the rp4n.cfg file is present in the top level
directory of the SD cards file system and that the file name is correct.
No polar Table File Found
If the RP4N is configured to use a polar table but no polar table is found on the SD
card, the red error light will flash very rapidly, going on for 150ms then off for 150ms,
repeating until the Race Box is powered down. This is a fatal error.
Make sure the polar table file ends in .nxp and is present in the top level directory of the
SD cards file system.
Failed to Establish FDX Communication
If the red error light turns on and remains on for several seconds or longer with no
flashing, this means that the RP4N failed to establish FDX communications with the
Nexus server. This is a fatal error and the RP4N will need to be restarted.
In this event, the server should also be restarted.