Casio Qt 6100 Service Manual

							
— 69 —
ActionMeaningPrompt message
E140  Wrong menu.
E141  Press  
twice before finalization.
E145  Arrangement syntax er-
ror.
E150  Incorrect value entry.
E151  Incorrect Key Pressed.
E152  PGM File or Memory 
number does not Exist.
E164  Employee No. is not 
Found in the Employee 
File.
E165  Employee No. is not 
Clocking-in.
E166  Employee No. is Occu-
pied.
E167  Incorrect Job code.
E168  Your Operation is out of 
Schedule.
  Please Call Manager.
E169  Work Hours Exceeded.
  Please Call Manager.
E170  No Shift Remains in the 
Schedule.
  You cannot Clock-in.
E171  Please Break-out and 
Retry.
E172  Break Hours Exceeded.
  Please Call Manager.
E173  This employee is at work 
now.
E174  This employee is taking 
a break now.
E175  Please Clock-in/Break-
out before you sign on.
  or Please Call Manager.
E176  You cannot Clock-in.
  Please reset Employee 
Report.
E177  Time&Attendance Data 
Communication Error.
  Please Call Manager.
E180  IDC FILE (1) memory 
full.
  Please clear IDC data.
E181  IDC FILE (2) memory 
full.
  Please clear IDC data.
E182  IDC FILE (3) memory 
full.
  Please clear IDC data.
This sheet holder is prohibited by pro-
gram.
 key is not pressed twice 
before finalization.
Arrangement syntax error
Incorrect entry for PGM
Linking is incorrect.
No such file, no such record
Employee No. is not set in the Employee 
File.
Employee has not done CLOCK-IN 
operation yet.
Employee who has done CLOCK-IN 
operation attempts to operate CLOCK-
IN again.
Employee attempts to operate CLOCK-
IN with incorrect JOB code.
Employees operate CLOCK-IN/OUT in 
not allowance time.
Overtime work.
There is no available shift left.
Employee attempts to operate CLOCK-
OUT whilst he/she is in a break time.
Break hours are exceeded.
Employee is at work without break.
Employee who has not done BREAK-
OUT operation attempts to operate 
BREAK-IN.
Sign on after you clock-in or break out.
Employee Report has not been reset.
Time & Attendance Data communication 
error.
IDC FILE (1) memory is full of items.
IDC FILE (2) memory is full of items.
IDC FILE (3) memory is full of items.
Set correct sheet holder.
Follow the prompt message.
Program the arrangement again.
Enter proper value again.
Enter proper key again.
Enter file/record number again.
Enter employee number again.
Perform CLOCK-IN operation.
Enter the proper employee number again.
Enter proper job code.
Follow the prompt message.
Follow the prompt message.
Follow the prompt message.
Follow the prompt message.
Follow the prompt message.
Follow the prompt message.
Follow the prompt message.
Follow the prompt message.
Follow the prompt message.
Follow the prompt message. 
						

							
— 70 —
ActionMeaningPrompt message
E200  Insert CF Card.
E201  Format error.
E203  Insufficient memory.
E205  The file already exists.
  Do you replace?
  YES:Replace the file.
  NO :Input new name.
E240  Customer No. is occu-
pied.
E241  Customer memory full.
E242  Customer not found.
E243  Illegal Site ID.
E244  Credit limit over.
E251  Magnetic card error.
E252  Enter customer name.
E253  Enter address.
E254  Enter phone number.
CF card is not inserted to the slot.
CF card data or formats illegal.
Insufficient memory is remained in CF 
card.
File name duplication error
Attempt is made to set a customer that 
already exists in the customer file.
Customer file becomes full.
This customer does not exist.
The site No. of the file does not coincide 
with the No. of the card.
Attempt to transfer when the balance is 
over than the credit limit
This card cannot be read.
This card format is illegal.
Insert CF card.
Check the CF card.
Format or use a new CF card.
Follow the prompt message.
Enter proper customer No.
Delete unnecessary customer No.
Enter proper customer No.
Swipe the proper magnetic card.
Release credit limit by OPEN2
Make minus, void, or refund operation to 
decrease the balance under the credit limit. 
Perform finalization or cancellation.
Swipe the magnetic card again.
Swipe the proper magnetic card.
Follow the prompt message.
Follow the prompt message.
Follow the prompt message. 
						

							
— 71 —
Data cannot be printed out.
Backup to R/J printer?
Do you want to clear data?
Cancel OK?
Please wait.
Item Consolidation Mode
Non Consolidation Mode
REG Mode
REFUND Mode
REG- Mode
Training
REG2 Mode
Please Sign on.
Enter Check/Table Number.
Enter Table Number.
Enter Number of covers.
Enter Seat Number.
Perform Slip Printing.
Issue Guest Receipt.
Perform Validation Printing.
Perform Check Printing.
Perform Check Endorsement.
Operation Code?
Re_configuration...
Re_configuration end
Clock-in OK?
Clock-out OK?
Break-in OK?
Break-out OK?
Enter cash tip amount and press
 key.
Communication Error
This procedure stops system maximum 60 sec.
OK ?
Enter #
Enter Alphacode!
Items not found!
Request to check the X / Z report data which cannot 
be printedout.
Confirmation to reset displayed report.
Confirmation of all void operation.
Please wait. ECR now processing.
In the item consolidation mode.
Not in the item consolidation mode.
Mode change : REG mode
Mode change : REF mode
Mode change : REG– mode
Mode change : REG2 mode
Signing on a training operator
The terminal is in signed off.
CHK# compulsory
TBL# compulsory
Covers compulsory
Seat# compulsory
Slip compulsory
GUEST RCT compulsory
VLD compulsory
CHK-PRT compulsory
CHK-END compulsory
Enter secret number for REG 2 mode.
During system reconfiguration
System reconfugiration ends
Time and attendance clock-in operation
Time and attendance clock-out operation
Time and attendance break-in operation
Time and attendance break-out operation
Time and attendance tip declaration compulsory
Communication error during clock-in
Alert before flash memory clear.
Registering Non-add after RC / PD.
To search the appropriate item, enter goods name.
Items cannot be found by item searching.
9-2  Operation prompt
All  prompt  messages,  together  with  descriptors  and  symbol  characters  for  displaying  /  printing  are 
contained in the list below. These messages cannot be added, modified or deleted.
MeaningPrompt message 
						

							
— 72 —
9-3  System error code
All error codes are contained in the list below. These error codes are displayed or printed on error log 
report.
  Error code Meaning
  0010  Handler access error (software)
  0011  Cannot execute handler (system configuration)
  0012  Break by PC
  0013  Break by ECR
  0014  DSR off before receiving command packet
  0015  Receive illegal command number of command packet
  0016  Receive illegal character
  0017  Send error (hardware)
  0018  Receive error (hardware)
  0019  Receive illegal data packet
  0020  No response error
  0021  Receive illegal command phase
  0022  Received illegal packet
  0023  CNET receive error
  0024  Illegal termination by sender
  0025  Received illegal packet during receiving data packets
  0026  Not enough data packets received
  0040  No “H” information
  0041  No “I” information
  0042  No “F” information
  0044  Illegal packet format
  0045  No file exists
  0046  Illegal block
  0047  Illegal command packet
  0048  Illegal command No. (Not CMD)
  0049  Illegal command No. (Not DATA)
  0050  Sequence error
  0051  Turn off DSR signal
  0052  Received cancellation
  0053  Retry over while waiting command
  0054  Retry over while waiting EOT
  0055  Retry over while waiting data
  0056  Received EOT
  0057  Retry over while waiting ACK
  0058  Retry over while sending data
  0059  Retry over while waiting “C”
  0060  Retry over while sending response
  0061  Retry over while excluding
  0064  Break end
  0065  Error during printing report header
  0066  Error during printing report data
  0067  Error during printing report data in work file
  0068  Error during printing report data in consolidation file
  0069  Work file clear error
  0070  Consolidation file clear error
  0071  Z lock error
  0072  Z clear error
  0073  Z lock release error
  0074  Error during accumulating to consolidation file
  0075  Error during copying report data from terminal memory to work
  0076  Error during copying stock data to terminal memory
  0077  Z lock error on satellite terminal
  0078  No appropriate file is exist on satellite terminal during collection/consolidation 
						

							
— 73 —
  0079  Z lock release error on satellite terminal
  0081  Check tracking master is removed from system.
  0082  Check tracking backup master is removed from system.
  0128  Parameter error / Maximum length of send error
  0130  Error drive
  0134  Network parameter error
  0138  Detect error in core system
  0140  Parameter error (record length exceeds work buffer)
  0141  EOF over
  0144  Calculation overflow
  0145  Undefined value of n_open () mode
  0146  Mismatch of type when closing network
  0147  Parameter error
  0152  Defined NCB is not network resource
  0153  Retry over by the target busy
  0155  Sequence error
  0156  No port exists
  0158  Target port in use
  0160  Error while getting priority
  0161  Fail to change temporary priority
  0162  Error semaphore operation to keep resource
  0163  Fail to get new sled
  0164  Error while getting semaphore
  0165  Error to operate semaphore
  0166  Error during delay
  0167  Error during termination
  0168  Error when resource return
  0170  Error during getting task ID
  0171  No code is found while search/pick up
  0172  Cannot get work buffer
  0173  File opened/fail to activate task
  0174  No file exists
  0175  ITRON service error
  0176  Cannot create file
  0177  Record number error
  0178  Detect error while memory area opening
  0179  Detect error while returning mail box / double create error
  0180  Detect error while handling memory
  0190  RCB is not mail box resource
  0192  Error send message ID
  0194  Send message length over
  0197  Ending response
  0198  Time out while waiting for ending response / no receive message
  0202  No free FCB
  0204  Memory capacity shortage
  0205  Fail to create mail box
  0209  Cannot find the coincide PCB resource
  0210  Cannot find the coincide RCB resource
  0232  ID collision when network starts
  0233  Cannot find the target ID
  0235  Protocol error
  0247  Stop token
  0248  FTP client can’t open data connection.
  0249  FTP client requested file action not taken.
  0250  FTP client local error in processing.
  0251  FTP client syntax error
  Error code Meaning 
						

							
— 74 —
9-4. OS Fatal Error
When a fatal error occurs during an operation of the operating system, normal operation becomes im-
possible afterwards.
Therefore, the OS displays a message as shown below and stops the operation of ECR.
Such errors include errors of the OS (ITRON) itself, driver system errors, etc.
The values of Error No. and Error Code vary according to errors.
*  These are intentional system halting errors to prevent a system runaway due to software. Types 
of errors may be increased in the future.
OS Fatal Error !!
Error No.1
Error Code -13
 Error No.:
  Indicates the type of the error.
  A different number is allocated to each of the main causes, allowing you to identify the source.
 Error Code:
  Indicates details of the error that occurred, the source device, etc.
  Some codes may not have any meaning depending on the error type.
 Error No./Error Code Correspondence Table
  Error No.  Error Code Description of Error Source of Error
 -1  Error code returned by ITRON  Semaphore acquisition error  Network entry system (Net driver)
  -2  Error code returned by ITRON  Mailbox creation error  TP thread (Net driver)
  -3  Error code returned by ITRON  Mailbox creation error TP thread (Net driver)
  -4  Error code returned by ITRON  Semaphore acquisition error TP thread (Net driver)
  -5  Error code returned by ITRON  Mailbox creation error TP thread (Net driver)
  -6  Error code returned by ITRON  Semaphore acquisition error TP thread (Net driver)
  -7  Error code returned by ITRON  Mailbox creation error TP thread (Net driver)
  -8  Error code returned by ITRON  System error when returning unused  TP thread (Net driver) 
     memory (memory pool) area
  -9  Error code returned by ITRON  System error when returning unused   CGS system (Net driver)
     memory (memory pool) area
  -10  Error code returned by ITRON  System error when returning unused  CGS system (Net driver)
     memory (memory pool) area
  -11  Error code returned by ITRON  System error when returning unused  CGS system (Net driver)
     memory (memory pool) area
  -12  Error code returned by ITRON  System error when returning unused  CGS system (Net driver)
     memory (memory pool) area
  -13  Error code returned by ITRON  System error when returning unused  CGS system (Net driver)
     memory (memory pool) area
  -20  Error code returned by ITRON  Mailbox send error  Network thread (Net driver)
  -21  Error code returned by ITRON  Mailbox creation error Network system (Net driver) 
						

							
— 75 —
 Description of Errors
(1) Semaphore acquisition error
Error No. -1 / -4 / -6
Description of phenomenon:
This is a system error in ITRON.
This phenomenon may occur when the exclusion function of ITRON is used.
Possible causes:
A software bug or an illegal operation of ITRON.
(2) Mailbox creation error
Error No. -2 / -3 / -5 / -7 / -21
Description of phenomenon:
This is a system error in ITRON.
This phenomenon may occur when a function of ITRON called Mailbox is used.
Possible causes:
A software bug or an illegal operation of ITRON.
(3) Mailbox send error
Error No. -20
Description of phenomenon:
This is a system error in ITRON.
This phenomenon may occur when a function of ITRON called Mailbox is used.
Possible causes:
A software bug or an illegal operation of ITRON.
(4) System error when returning unused memory (memory pool) area
Error No. -8 / -9 / -10 / -11 / -12 / -13
Description of phenomenon:
This is a system error in ITRON.
This phenomenon may occur when ITRON frees the reserved memory area.
This  phenomenon  may  occur  when  the  memory  management  system  of  ITRON  is 
used.
Possible causes:
An abnormality of a memory chip, an illegal operation of ITRON, or a software bug.
9-5. CPU Exceptional Error
The functions of the CPU (SH series) include exception handling. If an exception other than reset and 
general  interrupt  (hereafter  called  “general  exception”)  occurs,  the  OS displays  a  message  as  shown 
below and stops the operation of ECR, because the operation after that cannot be guaranteed.
The  example  shown  below  indicates  the  screen  displayed  when  “reservation  instruction  code  excep-
tion” occurs.
The values of error no., error point and access adrs vary according to errors.
 error no.:
  Indicates the exception code of the general exception.
  From this code, the operation that causes the general exception is known.
CPU Exceptional Error !!
error no.  180
error point  ffffd47e
access adrs  0 
						

							
— 76 —
 error point:
  Indicates  the  point  on  the  memory  where  the  operation  instruction  that  causes  the  above  general 
exception is located (program counter).
  However, an illegal address may be displayed depending on the exception code.
 access adrs:
  Indicates the address that is accessed according to the operation instruction that causes the above 
general exception.
  However, the address is 0 (zero) and has no meaning if the access is not the cause.
 Error Code Correspondence Table
 Causes of error occurrence
(1) error no. 40: TLB address comparison results in address mismatch
(2) error no. 60: TLB entry is invalid
Description of phenomenon:
The CPU performs a conversion from logical address to physical address when ac-
cessing the external memory.
TLB is what caches that information.
If an error occurs in the process of the caching, a general exception of the CPU oc-
curs.
Possible causes:
A malfunction of the CPU, because this is an internal operation of the CPU.
(3) error no. 80: Initial page write exception
Description of phenomenon:
This  exception  occurs  if  the  address  conversion  table  of  the  above  TLB  is  illegally 
written.
Possible causes:
A malfunction of the CPU, because this is an internal operation of the CPU.
(4) error no. A0: TLB protection exception (read)
(5) error no. C0: TLB protection exception (write)
Description of phenomenon:
TLB  is  protected  by  setting  access  right.  An  access  that  violates  the  access  right 
causes one of these exceptions to occur.
Possible causes:
A malfunction of the CPU, because this is an internal operation of the CPU.
(6) error no. E0: CPU address error (read)
(7) error no. 100: CPU address error (write)
Description of phenomenon:
This exception occurs if an illegal address is accessed (read or written).
Possible causes:
•  An illegal address is accessed by software (a software bug).
•  The address to be accessed has changed due to insufficient charge of the backup 
battery for RAM.
  error no.  error point access adrs Description of error
  40  Location where error occurs Logical address of comparison source TLB address comparison results in address mismatch
  60  Location where error occurs  Logical address of error source  TLB entry is invalid
  80  Location where error occurs  Logical address of error source  Initial page write exception
  A0  Location where error occurs  Logical address of error source  TLB protection exception (read)
  C0  Location where error occurs  Logical address of error source  TLB protection exception (write)
  E0  Location where error occurs  Address of read destination  CPU address error (read)
  100  Location where error occurs  Address of write destination  CPU address error (write)
  180  Location where error occurs  0 Reservation instruction code exception
  1A0  Location where error occurs  0  Slot illegal instruction exception 
						

							
— 77 —
(8) error no. 180: Reservation instruction code exception
(9) error no. 1A0: Slot illegal instruction exception
Description of phenomenon:
These exceptions occur when an illegal instruction is performed.
Possible causes:
It is hard to think that this phenomenon is caused by software, because these errors 
occur due to an internal operation of the CPU.
This  phenomenon  is  apt  to  occur  when  backup  of  RAM  is  not  performed  normally 
and the memory has been changed.
It is possible that the data in RAM has become illegal data.
9-6. Booster Error
ERR XX
An error in Booster part processing (IPL, INT or FINT) is indicated as follows:
XX: Error No.
Error Code Correspondence Table
  Error No. Description of error
  1  CF card is not inserted.
  2  CF card has no IPL file.
  3  Flash erase error
  4  Flash write error
  5  Reserved (error not occurring this time)
  6  CF card read error (bad CF card)
  7  COM1 open error (bad CPU)
  8  Reserved (error not occurring this time)
  9  Bad read IPL data (IPL data is not valid)
  10  Checksum error (checksum of read IPL data does not match)
  11  Reserved (error not occurring this time)
  12  Communication error on COM1
  13  Communication error on COM1 (same as 12; 12 or 13 occurs depending on timing of occurrence) 
						

							
— 78 —
10. IC DATA
■ MAIN PCB (E820-1 PCB)
  1.  ALVCH16244 (IC13, 17)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
48
47
46
45
44
43
42
41
40
39
38
37
36
35
34
33
32
31
30
29
28
27
26
25
1OE
1Y1
1Y2
GND
1Y3
1Y4
VCC2Y1
2Y2
GND
2Y3
2Y4
3Y1
3Y2
GND
3Y3
3Y4
VCC4Y1
4Y2
GND
4Y3
4Y4
4OE
2OE
1A1
1A2
GND
1A3
1A4
VCC2A1
2A2
GND
2A3
2A4
3A1
3A2
GND
3A3
3A4
VCC4A1
4A2
GND
4A3
4A4
3OE
1OE
1A1
1A2
1A3
1A41Y1
1Y2
1Y3
1Y4
1
47
46
44
43
2
3
5
6
2OE
2A1
2A2
2A3
2A42Y1
2Y2
2Y3
2Y4
48
41
40
38
37
8
9
11
12
3OE
3A1
3A2
3A3
3A43Y1
3Y2
3Y3
3Y4
25
36
35
33
32
13
14
16
17
4OE
4A1
4A2
4A3
4A44Y1
4Y2
4Y3
4Y4
24
30
29
27
26
19
20
22
23
logic diagram (positive logic)
terminal assignments
1 23456
A1OENCNCNCNC2OE
B1Y21Y1GNDGND1A11A2
C1Y41Y3V
CCVCC1A31A4
D2Y22Y1GNDGND2A12A2
E2Y42Y32A32A4
F3Y13Y23A23A1
G3Y33Y4GNDGND3A43A3
H4Y14Y2VCCVCC4A24A1
J4Y34Y4GNDGND4A44A3
K4OENCNCNCNC3OE
NC    No internal connection
FUNCTION TABLE
(each 4-bit buffer)
INPUTSOUTPUT
OEA
OUTPUTY
LHH
LL L
HXZ