Cadac F-Type - Manual (Page 103)

APP-VII
Revision F2005-2 F-Type
5;#%XII#2YHUIORZ
5;#%ORFN#WRR#ELJ
'HOD\#GXULQJ#5;
%DG#&6XP#LQ#5;
%DG#3&#+HDGHU#QQ
%DG#3&#&RPPV
This is not actually an error but it is used to report the status of the Fast Copper
Comms. The Comms warning LED is lit and the ERR button flashes when the CCM
is not communicating with an automaton system.
-%DG#&38#FORFN-
This error may occur if the micro-processor crystal clock is not a recognized fre-
quency i.e. not 11.0592MHz or 16MHz.
%DG#&RPPV#6WDWXV
A status has been received from the “motor fader communications processor” that
does not match any of the known status reports.
+RVW#EXIIHU#HUU;
This error is reported when the CCM tries to pass a command to the “motor fader
communications processor” and experiences a problem. The following error codes
are defined:
X=0 Command Queue is full
8VHU#$FWLRQV
Sometimes you may log a particular action requested by the user (or performed by
the system) so that later, if an error is reported, we can try to trace the sequence of
events and see if a particular function could have been the cause of the error.
7LPH2'DWH#5HVHW
When the CCM first communicates with the PC that is running the automation soft-
ware a message is received to set the Time and Date. This is because the CCM
does not have its own real-time clock. This event should be recorded in the Error
Log, so that you know when communications started or was reset.
+RVW#LV#6HDQFH
If the PC is running the SAM software, then you will record a message to say that the
CCM is communicating with a Seance box. This lets you know about the system con-
figuration if an error is reported.
1HZ#&ORFN=#Q0+]
The CCM is able to work with older CADAC automaton software that requires serial
RS232 communications. To do this, we have to change the crystal clock frequency of
the micro-processor in the CCM. This is recorded in the Error Log with one of two
possible frequencies:
1HZ#FORFN=440+]
used for serial RS232 communications
1HZ#FORFN=490+]
used for Fast Copper Communications
(UU1#ORJ#FOHDUHG
The user has cleared the Error Log. This event should be recorded so that you know
when the system started recording events.
6WDUW#0RGXOH#0DS
(QG#0RGXOH#0DS
$ERUW#0RGXOH#0DS
The user has requested to Start, End (and store) or Abort (don’t store) Module map-
ping information.