Troubleshooting the "NO res. Mainboard!" Error on the AOR AR-DV1
This guide addresses a specific bug affecting the AOR AR-DV1 radio, identified by the "NO res. Mainboard!" message.
Understanding the "NO res. Mainboard!" Error
The "NO res. Mainboard!" error typically arises when the radio's firmware is updated to version 2107A, and the receiver system's date (specifically the year) is set to a value earlier than 2014, either before the update or mistakenly afterward. This issue does not stem from a hardware fault.
Fixing the Error: Step-by-Step Instructions
The solution requires precise timing and involves entering a new, valid date and time that is later than 2014. No tools are necessary, but quick actions are essential.
- Turn on the radio.
- Listen for two alternating plops: one lower pitch and one higher pitch. Immediately after the higher pitch plop, a one-second window opens for key presses.
- During this one-second window, quickly press the $F+3$ keys to access the clock setting menu.
- Once in the clock setting menu, rapidly use the down arrow key to navigate to the 4th line, which displays the system date and time.
- Enter a valid date and time in the format
yy-mm-dd hh:mm. For example, enter2211111111. - Press the ENT key to confirm.
Upon successful entry of the correct date and time, the radio should resume normal operation.
Important Notes:
- Steps 3 and 4 must be executed very quickly. There is only a few seconds before the radio locks up again. If this happens, wait for the next high pitch plop to get another chance. The system will continue to loop at this menu until the correct input is provided within the time window. There is no need to power the radio off and on repeatedly.
Personal Experience and Resolution
This issue was encountered after an accidental year change to 2012, which triggered the bug. Following the procedure outlined above successfully restored the functionality of the AR-DV1. It is recommended to update the firmware after resolving this issue, as AOR has implemented a fix for this bug in later firmware versions.
Thanks are extended to Jeff Marlbrook for his expertise on the AR-DV1, which was instrumental in resolving this problem.
73 and good luck.
Janne / SM0OFV
