Error 14/10 on a XTL 5000

[123]

Anyone know what this error code means? I never seen it before.

Thanks in advance.

[wa6ylb]

Anyone know what this error code means? I never seen it before.

Thanks in advance.

I didn't see the 14/10 code listed. However, all of the /10 codes are related to hardware issues upon power up.
Its like the radio is expecting to see some hardware, and its not there when the radio boots up.
If you can check the programming on the radio, check to see if optional hardware, such as dual radio /PA/ DEK boxes/ PA stuff like that in the settings might be turned on, but not connected to the radio. The first time I saw an error like this, was when I was working on a dual radio setup. The radios had their programming set to be part of a dual radio setup. When I powered one radio by itself, the radio didn't find the other radio and gave a simular error and then continued on.
I suspect this is the case on your radio there. Its bound to be some optional hardware that the radio can't find on powerup.

05/10 Control head
06/10 Aux control head
08/10 Siren hardware
09/10 Secure hardware (you get this when you click on "hardware secure" and there isn't a board installed.
12/10 VRS hardware
1C/10 Tone Remote Control hardware.

B.

[123]

This is what is disabled so far that could be hardware related in the software.

PA/Siren
VIP control of VRS
Multi control head
Number of DEK boxes "0"


I do not know what else I could do. I know its not the secure or DVRS functions either.

[jpatrou]

This error code is one of the new error codes associated with the DVRS. Error 14/10 tells me that the XTL is already programmed to work with the DRVS and it can not find it.
Look under Radio Wide, Advanced tab, you should see "DVRS hardware Enable" has been checked, uncheck the box and reprogram the radio.

[123]

Ah ! okay. Problem solved. Thanks

[Jim202]

How about letting the rest of us know what you did. These problem resolutions also only help the rest of us if we know the details.

Jim

Ah ! okay. Problem solved. Thanks

[akardam]

Jim,

Read jpatrou's post.