![Novexx AP 5.4 Gen II User Manual Download Page 326](http://html1.mh-extra.com/html/novexx/ap-5-4-gen-ii/ap-5-4-gen-ii_user-manual_1712055326.webp)
06/15 Rev. 10
USER + SERVICE MANUAL
/Status Reports
64-xx – DPM – PEM – ALX 73x (PMA) – LPA 81x (Printer) – ALX 92x – AP 5.4 – AP 5.6
75
9017
RTC read failed
Status
Error, while trying to read the realtime clock (RTC). Happens, if an Easy-
Plug command to read out the RTC is sent, but no RTC is built in.
Measure
Check, if the printer is supplied with a RTC. To do so, print a status
printout.
See parameter
INFO PRINTOUT > Printer status
You find the actual date on the printout, below the header „Systemversion“,
if a RTC is installed.
Check, if the error occurs repeatedly or sometimes.
If it occurs repeatedly:
AP 5.4
: replace the CPU board.
64-xx / ALX 92x / DPM / PEM
: Replace the RTC. If the error still occurs,
replace the CPU board.
If the error occurs sometimes, please refer to the notes in section
General
software errors
.
9018
#!CA wrong Pos.
Status
The #!CA command is placed at an inadmissible position – the Easy-Plug
interpreter can not proceed the command at this position (e. .g during the
loading of files onto a memory card).
Measure
Call the #!CA command at an admissible position.
9020
Param. ID wrong
Status
A not existing parameter ID was used
.
Measure
Correct the parameter ID.
9022
No network link
Status
This message can only occur, if the Ethernet address assign is set to
DHCP. The cause is nearly always a badly connected network connector.
Measure
Check, if the network connector is plugged in properly.
9023
Filename: Functionname() Line: xxx
Status
This status message indicates a software error. The error source is located
in the source file “Filename” in function “Functionname()” in line xxx.
Measure
Switch device off and on again.
If the error occurs repeatedly:
Contact the manufacturer.
When doing so, it is important to be able to reproduce the error. Gather the
following informations before calling the technical support of the
manufacturer:
-- Displayed information about the error source
-- Label layout, logfiles, etc. as described in chapter
Unspecific errors