EroriBizerba PDF

SW 7.0, SC–Serie 1.
Statusmessages
6.126.98.1.01.70
Erstellt von:
VS–TB
L. Collerius
Juli / 98
Alle Rechte vorbehalten

All rights reserved
Tous droits réservés
Resevados todos los derechos
Tutti i diritti riservati
©1996
BIZERBA GmbH & Co. KG, 72336 Balingen
BIZERBA GmbH & Co. KG, Postfach 10 01 64

72301 Balingen / Germany, Tel. (07433) 12–0, Fax (07433) 122696
Statusmessages SW
1. Status messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 – 1
1.1 Text messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–1

1.2 General information about status messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 – 37
1.3 Status numbers of basic BOS software, numbers 1 – 24999 . . . . . . . . . . . . . 1 – 37
1.4 Status numbers of application software SWCom, numbers 25000 – 25200 . 1 – 73
1.5 Status numbers of basic BOS software, numbers 40001 – 49999 . . . . . . . . . 1 – 82
1.6 Status numbers of SC application software . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 – 85
Last page of section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 – 129
6.126.98.1.01.70 3
Satusmessages SW
1. Status messages
1.1 Text messages
In force up to field test program version 1998/03/30.
In most cases the scales of the SC series react to incorrect operation or error conditions by outputting a text
message which is indicated on the vendor’s display. Such text messages are listed hereunder by cause and
recommended remedial measures. These procedures are numbered and the sequence given should be
strictly adhered to. If the prescribed measures do not produce results in the correction of any particular mal-
function, carry on with the next number. The errors are listed in alphabetic order.
Text message Cause/remedial action
A
Action not possible, learn mode cur- Cause:
rently without function. appears during the creation of functions when selecting LEARN
OFF and the creation of function was not started with LEARN
ON.
ADC error Appears during the selection of menu point CALIBRATION.

Remedial action:
1.) There is no ADC connected (SC 100 K).
2.) Check connecting cable ADC and CPU card.
3.) Plug calibration jumper SB 201.
4.) Check jumper settings on the ADC.
5.) Replace weighing system.
6.) Replace CPU card.
3
Already cancelled or cancel ticket
Apply commodity Appears if the operating mode SELF–SERVICE is activated.
Apply weight Appears in sales mode.

Remedial action:
a weight–dependent article is only recorded after a load change
has taken place.
Archive error Appears during selection of menu point CALIBRATION.

Remedial action:
1.) There is no ADC connected (SC 100 K).
2.) Check connecting cable ADC and CPU card.
3.) Plug calibration jumper SB 201.
4.) Check jumper settings on the ADC.
Article not created ! Appears in ARTICLE MAINTENANCE.

Create new article ! Cause:
a non–existing PLU has been called up in PRICE MODIFICA-
TION.
Remedial action:
1.) Enter correct PLU No.
2.) Create PLU via GENERAL MODIFICATIONS.
6.126.98.1.01.70 1
Statusmessages SW

Article type / Appears in ARTICLE MAINTENANCE under menu point
price type combination invalid PRICES.
Cause:
only logic combinations of article type and price type are permit-
ted.
Unlogic is for example:
Article type: money–saving stamp
Price type: graduated price
A special offer record being Cause:

changed ! ! appears in ARTICLE MAINTENANCE when changing the price
basis or the article type if a special offer of the article to be chan-
ged is activated. The special offer is then adjusted to the same
settings.
Attention !! Switch on all deactivated Cause: scales are inactive.

scales. Remedial action:
1.) Switch on all scales.
2.) Check connecting cables, connector receptacles, T–pieces
and interfaces.
Attention: Max. number of XXX Appears during concatenating of functions.

functions exceeded. A maximum of 20 functions may be active at the same time and
be concatenated with one another.
Remedial action:
1.) Check functions created for being concatenated with
one another (endless loops).
2.) Change structure of function concatenations.
Attention: Only XXX Appears during the creation of functions.
3 keys available to accept function ! Cause:

the function LEARN OFF is not stored.
The number of key activations related to a function is limited. The
message appears when the memory for the function is only ca-
pable of accepting another 5 key activations.
Remedial action:
1.) Terminate the creation of function with LEARN OFF.
Cancel the function just created.
Reconsider the procedure of your function.
Keep the number of key activations to a minimum or divide
the procedure into several functions and link them to one
another.
Attention: Switched off scales ! Cause:

one or more scales are not switched on when selecting menu
point REPORTS.
Remedial action:
2.) Check cabling.
3.) Check system bus interfaces.
Attribute type incorrect Appears in sales mode.

Cause: database error.
Remedial action:
submit scale for inspection.
2 6.126.98.1.01.70
Satusmessages SW
B
Bar code allocation not created Cause:
appears during scanning of an article the EAN No. of which has
not been created in the bar code allocation table.
Remedial action:
assign an article to the EAN No. via the department No./PLU
No. in menu point ARTICLE MAINTENANCE / BAR CODE AS
SIGNMENT.
Bar code allocation not possible Cause:

appears in menu point ARTICLE MAINTENANCE / BAR CODE
ASSIGNMENT during the allocation of an instore code structure
which has not been created in the code content with the place
holder X. All placeholders other than X must not be used.
Remedial action:
use placeholder X for the code content of the code structure
used in menu point DATA MAINTENANCE / BAR CODE DATA.
Bar code allocation table not crea Appears during the selection of menu point ARTICLE MAINTE
ted NANCE / BAR CODE ALLOCATION.
Remedial action:
ARTICLE DATA /ACCESSORIES / NUM. OF DA. IN BAR CO.
TAB. not set in COMMISSIONING. Recommission unit if neces
sary.
Bar code information cannot be Appears during scanning of instore bar codes.
evaluated ! Remedial action:
1.) Check the code structure data used for disallowed inputs in
the menu point DATA MAINTENANCE / BAR CODE DATA.
3
Pay special attention to the placeholders used for the code
content.
2.) Check the settings for the connected scanner type in the
menu point CONFIGURATION / COM1 by observing the
code identifier used.
Bar code menu incorrect
Bar code type unknown Cause:

the scanner connected transmits an unknown code type. Only
the EAN8, EAN13, UPC A and UPC E codes used in trade are
permitted.
Remedial action:
1.) Check the programming of scanner to ensure that the code
types used are correct.
2.) Check the code identifiers set in the menu point
CONFIGURATION / INTERFACES / COM1 for
being correct.
BVBT reference to BOKA

invalid,has been cancelled.
By–Count deselected Appears in sales mode on SC scales commissioned with PCS.

PER PACKAGE NO and into which articles with the setting BY–
COUNT were loaded via the EDP or data backup.
Remedial action:
1.) Check scale nework and EDP (CWS) for uniform data
organization.
6.126.98.1.01.70 3
Statusmessages SW
C
Call locked Cause:
EDP call active while an EDP call is active there is no possibility of evaluating a
report on the SC.
Remedial action:
wait for the report to be terminated on the EDP and subse
quently start the evaluation.
Call not initialized

Initialization task signals error
Cancel at printer synchronization Cause: internal error.
Cashier has not determined Appears in cashier’s reports.

POS balance i. h. ! Remedial action:
1.) Ensure that {POS BALANCE I. H. COMPULS.}
is set in the menu POS in the CONFIGURATION.
Cashier’s report printouts are not made if a cashier does
not determine the actual contents of POS before
he starts such printouts.
Each cashier must establish a POS balance prior to the
printout of reports or the reports are to be evaluated with the
following range settings:
FROM CASHIER 001
TO CASHIER 999
TOTAL CASHIERS ONLY YES
Check digit incorrect Appears during scanning of an article.
Remedial action:
3 check the input if the EAN number was manually entered via the
keyboard.
Check the print image of the bar code for DOT failures.
Replace the printer.
Checkdigit overflow in department Appears if PRINT {CHECK DIGIT} is set in menu point CONFI-
or selling price GURATION / PRINTER / PRINTER X / LABEL.
Remedial action:
1.) Check department No. which must not exceed 2 digits.
2.) Check selling price determined which must not exceed
6 digits.
Checksum of POS report incorrect
Check tolerance Appears in sales mode when using assortment PLUs.

Cause:
the weight applied to the scale or the number of pieces entered is
outside the tolerance preset for the article of the assortment. The
article may only be recorded when the weight value or the num-
ber of pieces lies within the tolerance.
Remedial action:
1.) Check the tolerance value in ARTICLE MAINTENANCE /
ASSORTMENT OFFER.
4 6.126.98.1.01.70
Satusmessages SW

Code structure not created Cause:
appears during scanning of an article the code digit of which
(e. g. 21........ ) refers to a code structure number which is not
created in the menu point DATA MAINTENANCE / CODE
STRUCTURES.
Remedial action:
correct the code digit or create a code structure according to
that created in menu point DATA MAINTENANCE / CODE
STRUCTURES.
Coding error Appears during printing of bar code.

Remedial action:
1.) Check the settings for the bar code used for correctness in
DATA MAINTENANCE under BAR CODE DATA.
Coding of negative value Cause:

an attempt was made to encode a negative value in a bar code.
Remedial action:
negative values in a bar code cannot be encoded.
If a PLU with a negative unit price is to be called up, use a piece
count code.
Command invalid Cause: internal error.
Commissioning data does not agree Cause:

with system ! ! appears when adding a scale to an active system.
Recommission scale ? The database structure of the added scale does not agree with
Yes / No that of the current system. Scales having a different database
structure within a system are not permitted.
Remedial action:
1.) Acknowledge request with YES.
The recommissioning function is activated. 3
Adjust the commissioning data to the current system.
There is the possibility of copying the commissioning data
from a scale connected to the system.
Acknowledging with NO causes the message REMOVE SCALE

FROM SYSTEM to be output.
Commissioning data has been Appears from CPU program version 3.06 after loading of com-
loaded. Recommission scale. missioning data with SW_DASI.
Remedial action:
1.) Select START COMMISSIONING directly.
Copying to the scale–own station address is no longer
necessary.
Commissioning data loaded could Appears after loading of a data backup.

not be adopted ! Remedial action:
1.) Reload COMMISSIONING data with SWDasi.
Switch scale OFF and back ON.
Readopt COMMISSIONING data.
Conf. identifier not clear Cause: configuration data destroyed.

Remedial action:
1.) Check the battery on the CPU card. Replace battery
if necessary.
6.126.98.1.01.70 5
Statusmessages SW

Configuration being processed Appears during loading of configuration data with SWDasi.
Cause:
at the time of loading, an attempt was made to call up the menu
point CONFIGURATION or the data transmission was started
while the scale ranged in the menu point CONFIGURATION.
Configuration data loaded could not Appears after loading of a data backup.
be adopted ! Remedial action:
1.) Reload CONFIGURATION data with SWDasi.
Readopt CONFIGURATION data.
Created partition(s) wrong Appears during commissioning.

Remedial action:
1.) The partition No. in menu point CREATE PARTITIONS
must appear in ascending order.
E. g.: incorrect correct
partition 1 6 4
partition 2 5 5
partition 3 4 6
Create new ticket Internal message.
Cust. No. occup. by vend.: XXX Appears in continuous sales mode with customer/vendor linkage.
Cause:
the customer No. used is occupied by another vendor.
Customer not created Cause:

3 appears during establishing of delivery notes and purchase or-
ders when the customer number is input via key [DELIVERY
NOTE] or [PURCHASE ORDER].
Remedial action:
1.) Check the commissioning data.
OTHERS / CUSTOMER RECORDS.
2.) Check the customer data in DATA MAINTENANCE /
CUSTOMER DATA.
6 6.126.98.1.01.70
Satusmessages SW
D
Database error XXXXX Remedial action:
Action was not executed refer to indicated error number.
Database key incorrect
Database not existing Cause: internal error.
Database table not created Appears in sales mode.

Remedial action:
1.) Check the values for the database table used in
COMMISSIONING.
If error recurs:
2.) If necessary submit the SC scale for inspection.
Database table not found Appears in sales mode.

Remedial action:
if necessary submit the SC scale for inspection.
Appears in POS mode.

Remedial action:
1.) Check the commissioning values for MARKUPS/
DEDUCTIONS.
Data loaded. Modify data if Appears after data backup.

necessary and start commissioning !
Data of report menu inconsistent Appears during the selection of the menu point SCALE RE-
3
PORTS.
Cause:
the settings made for the ranges or sortings for the reports are
incorrect.
Remedial action:
1.) Reselect the report menu. This causes all incorrect settings
to be automatically reset to standard. Repeat the procedure
until the error message disappears. Redefine the
report settings.
Check the battery. This is absolutely necessary.
If error recurs:
2.) Recommission unit.
DBM error during cancellation
Del. note disabled ! Cause: appears during the creation of delivery notes
when the customer No. is entered via key [delivery note].
Remedial action:
aheck the setting in menu point DATA MAINTENANCE / CU-
STOMER DATA.
If necessary, activate ENABLE DELIVERY NOTE in the custo-
mer data.
6.126.98.1.01.70 7
Statusmessages SW

Different accounting mode Appears during establishing of DELIVERY NOTES, PURCHASE
ORDERS, INVENTORIES, WASTAGE WEIGHINGS and RE
TURNS.
Remedial action: a sales mode in which a ticket has been star
ted cannot be changed. The ticket currently processed must
first be terminated via the total [*] key.
Different ticket type Appears in

– inventory mode
– returns mode
– wastage weighing mode
Remedial action:
1.) A vendor has started operations in one of the above
sales modes and a second vendor wishes to operate
in normal sales mode. A sales mode can only be changed
when the first vendor has terminated his mode via the total
[ * ] key or if he interrupts his mode.
Two different sales modes cannot be used at the same time.
Digit overflow in value coding Appears during printing of bar codes.

Remedial action:
1.) Check the settings for the bar code used for correctness in
DATA MAINTENANCE under BAR CODE DATA.
Disconnected/incorrectly configured Cause: appears when selecting ARTICLE MAINTENANCE if not

equipment all scales connected to the system are activated.
Error number 4552 Remedial action:
2.) Carry out menu point CONFIGURATION / RESTORE
3 SYSTEM NETWORK.
3.) Check cabling.
Disturbances in data transmission Appears during printing.

to printer. Remedial action:
Continue with <Enter> key 1.) Acknowledge the message with the <Enter> key.
If message recurs:
2.) Check the connecting cable of CPU card and printer
controller.
3.) Replace printer controller.
Double address in system ! Appears during activation of an additional scale.

Remedial action:
1.) Check the station addresses of scales in menu point
CONFIGURATION / SYSTEM.
Each address in the system must not exist more than once.
Double initialization for total sales

calculation
Dpf magic number incorrect Cause: memory management destroyed.

Remedial action: recommission unit.
8 6.126.98.1.01.70
Satusmessages SW
E
EDP connection not existing ! Appears during continuous ticket call via EDP.
Remedial action:
1.) Check connecting cable between SC and PC.
2.) Check PC connection.
EDP interface active ! Appears after recommissioning of unit.

Load configuration tables now. Remedial action:
1.) The data for COMMISSIONING and CONFIGURATION
may now be loaded with the SWDasi program.
EDP protocol changed ! Appears during loading of the KFLO table with a modified proto-
Device being restarted ! col and after reloading of data backup with SWDasi. The SC
scale is automatically restarted and initialized with the new para-
meters for the EDP interface.
EDP requests report Appears during sales calls via EDP.

A simultaneous attempt has been made to carry out evaluations
on the SC.
Remedial action:
1.) Wait for the EDP to terminate its call.
End of paper ! Cause:

Automatic paper ejection and paper appears on ticket printer if the printer runs out of ticket paper du-
feed ring the printout.
Remedial action:
1.) The paper is automatically ejected.
Insert new paper.
The paper is automatically injected.
The printout is repeated.
2.) Ensure that the paper is correctly inserted.
3
3.) Check the light barrier in the paper chute and clean it.
4.) Carry out LEARN MODE FOR END OF PAPER.
5.) Check the connecting cable between printer controller and
light barrier.
6.) Replace printer.
End of paper ! Cause:

Continue with label print, ticket print appears on label printer if the printer runs out of labels during the
or label print on tally roll ? printout.
Remedial action:
1.) Insert new label or ticket roll.
Depending on the paper used, select the following by means
of cursor:
– label printing in conjunction with labels
– ticket printing in conjunction with ticket paper
– label printing on ticket paper in conjunction with
adhesive continuous forms.
2.) Ensure that the paper is correctly inserted.
3.) Check the light barrier in the paper chute and clean it
4.) Carry out LEARN MODE FOR END OF PAPER.
light barrier.
6.126.98.1.01.70 9
Statusmessages SW

Enter at least one partition ! Appears in commissioning during the creation of a partitioning
list for:
– PLU DATA
– GENERAL TEXTS
– LOGOS
– FREELY PROGRAMMABLE LABELS
Remedial action:
1.) A partition starts with 0.
Correct the setting.
Entered scale No. not existing ! Appears during copying of configuration settings.
Remedial action:
1.) Scale number entered is incorrect and must be corrected.
2.) Specified scale is deactivated and must be switched on.
and interfaces.
Error during loading of counter label Appears during printing of counter labels.
layout Remedial action:
1.) Check the actually available memory via display or print out
the RAM status.
The print data is edited in the currently available memory. If
the capacity does not suffice to edit this data, the above
error message will be output.
Error during loading of freely pro- Appears during printing of freely programmable labels.
gram. label layout Remedial action:
1.) Check available memory via display or print out the RAM
status.
3 the capacity does not suffice to edit this data, the above
2.) The setting in CONFIGURATION/PRINTER/LABELS is
already on FREELY PROGRAMMABLE LABEL, the SC
has, however, not yet stored a freely programmable label.
The layout must be edited in the CWS and transmitted
accordingly.
3.) The files transmitted by the CWS for the freely
programmable label were corrupt. Repeat transmission.
Ensure that the SC program version is compatible with that
of the CWS.
Error during loading of layout Appears during printing of labels.

Remedial action: see error messages.
– Error during loading of standard label layout
– Error during loading of counter label layout
– Error during loading of a freely programmable label layout
– Error during loading of a logo
– Error during loading of a region
10 6.126.98.1.01.70
Satusmessages SW

Error during loading of logo Appears during printing of logos (pictures).
Remedial action:
1.) Check currently free memory via display or print out the
RAM status.
The print data is edited in the currently free memory. If its
capacity is insufficient to edit this data, the above error
message will be output.
Logos for the SC should not exceed 40kB per logo.
2.) The files transmitted for the logos by the CWS were corrupt.
Repeat transmission.
Ensure the SC program versions are compatible with those
of the CWS.
Error during loading of region Appears during printing of freely programmable labels.
Regions are fields defined in the CWS having a preselected con-
tent.
Example of region:
Price frame Price frame on small label
Remedial action:
1.) Check available memory via display or print out the RAM
status.
Error during loading of standard Appears during printing of standard labels. 3

label layout Remedial action:
1.) Check the actually available memory via display or print out
the RAM status.
Error during setting of automatic cu- Appears in continuous sales mode with customer No. and auto-
stomer number. Retry. matic assignment of customer No.
CONFIGURATION / DEVICE SETTINGS / SALES MODES /
SALES MODE {CUST./VENDOR NO. AUTOMATIC}
Remedial action:
if error recurs:
Software problem on system bus.
Error in accessing hardware ID Appears during the activation of licence modules.

Cause:
the ID module on the CPU is defective or is not existing.
Remedial action:
1.) Plug the ID module on the CPU card or replace the same.
6.126.98.1.01.70 11
Statusmessages SW

Error in accounting task on call of Cause:
total or amount tendered the SC operates only with drawer connection, but without
amount tendered/change operation.
Remedial action:
1.) Connect the drawer or change the configuration.
Cause: error in foreign currency conversion and accounting

of sales.
Database error.
Remedial action: 1.) Recommission unit.
Error in accounting task on call of Cause:

total without amount tendered/ the SC operates only with drawer connection, but without
change op. amount tendered/change operation.
Remedial action:
1.) Connect the drawer or change the configuration.
Cause: error in foreign currency conversion and accounting

of sales.
Database error.
Error in database accessing Appears in sales mode.

Cause: database error
1.) If necessary submit scale for inspection.
Error in foreign currency conversion
Error in POS drawer accessing Cause:

drawer does not open. Reread contact not detected.
3 Remedial action:
1.) Check connecting cable between SC and drawer.
2.) Check drawer interface.
3.) Replace drawer.
Evaluation active at other station Cause: an identical report is started simultaneously on several
SC scales.
Remedial action:
first wait for the current evaluation to be terminated on the active
SC and then start the report.
F
Fatal: no more memory / Appears in ARTICLE MAINTENANCE during the creation of
PLU table overflow PLUs.
Cause:
the PLU table PLST has no more free memory and is incapable
of storing new PLUs.
Remedial action:
1.) Delete all PLUs and all special offer PLUs which are no
longer required.
2.) Check the commissioning values for the number of PLUs.
The values selected might be too low.
Carry out data backup.
Recommission unit with the corrected values.
Reload data backup.
12 6.126.98.1.01.70
Satusmessages SW

Fatal data error Appears in ARTICLE MAINTENANCE.
Cause: internal data error.
Remedial action:
Reload data backup.
Fatal error in evaluation task.
Forced cancel. not possible
Foreign currency selected not Appears in POS mode.

created Remedial action:
1.) Check the values for the currency used in
DATA MAINTENANCE / FOREIGN CURRENCIES.
2.) Check the keyboard programming.
DATA MAINTENANCE / FOREIGN CURRENCIES
/ FOREIGN CURRENCY KEY.
Foreign currency table not created Appears in POS mode.

Remedial action:
Enter the relevant value in COMMISSIONING / OTHERS /
FOREIGN CURRENCIES.
Foreign currency value menu

incorrect
Fraction/oz range overflow Appears in conjunction with an incorrect fraction/oz input for tare,
manual weight and fixed weight values, e. g. 9/8 oz.
3
Function disabled Appears during starting of functions via menu point
START FUNCTION.
For this function, FUNCTION DISABLED is set via menu EDIT
FUNCTION.
Function no longer possible during Appears in conjunction with the use of the HDLC interface.
this month ! Cause:
the HDLC service interface is limited to 5 connections per month.
This limit has been reached.
Remedial action: advance the month in the menu point DATE /
TIME. 5 connections then again become available. Set the month
back to the valid month after termination of transmission. 5 con-
nections are then offered again.
Function not permitted Appears in

– inventory mode
– returns mode
– wastage weighing mode
– price group mode 1, 2 or 3.
Remedial action:
1.) If a ticket was started in one of the above modes, there is
no possibility of switching to a different mode during the
current sales procedure.
Terminate ticket with total [ * ] which permits a different
mode
to be selected for the next ticket.
6.126.98.1.01.70 13
Statusmessages SW

Function not yet created in Appears when
database ! ! ! – starting functions
– clearing functions
– printing functions
– editing functions
if functions are not yet created.
G
General internal configuration error Cause: configuration data destroyed.
Remedial action:
1.) Check battery on CPU card.
General manager error
H
I
Identifier invalid Cause: internal error.
Incorrect entry in code structure Cause: use of an invalid code structure for the instore code.
Remedial action:
check the data of the code structure used for disallowed inputs in
menu point DATA MAINTENANCE / BAR CODE DATA.
Pay special attention to the placeholders used for the code con-
tent.
3 Input incorrect! Appears in conjunction with the input of the licence number.
Remedial action:
1.) Enter correct licence number. If necessary, contact the
person in charge of licences or select the hotline in Balingen.
Internal database error Appears in sales mode.

If error recurs:
Internal DBM error Appears in sales mode.

K
Key not permitted ! Appears in sales mode.
Cause:
the function assigned to the key cannot be executed at this point.
Remedial action:
1.) Check operating procedure for correctness.
2.) Check keyboard programming for correctness.
Key occupied by vendor with open Appears in sales mode during log on/off of vendors.
ticket Remedial action:
the vendor indicated must teminate his ticket by drawing the total
[*] and log off afterwards.
14 6.126.98.1.01.70
Satusmessages SW

Key switch position wrong ! Appears on the SC when selecting a menu point which can only
be carried out in a certain position of the key switch.
Remedial action:
1.) Set the key switch to the correct position.
2.) Check the settings in the menu point
CONFIGURATION / KEYBOARD / KEY SWITCH.
L
Learn mode terminated! Appears automatically after RAM clearing or when menu point
Reinsert paper ! LEARN MODE FOR END OF PAPER is carried out.
Learn mode unsuccessful ! Cause:

appears when menu point LEARN MODE FOR END OF PAPER
was carried out.
Remedial action:
1.) Print bar open? Close it.
2.) Mechanical printer parts blocks. Correct it.
Load capacity code invalid Cause:

appears ON SWITCH–ON after calibration. An incorrect or non–
permitted load capacity code was entered during calibration.
1.) Carry out calibration with the correct load capacity code.
Loaded data adapted to range of Appears when loading an older data backup version into a
values. current program version.
Cause:
if values were cleared in the commissioning or configuration data
of the current program which are still present in the data backup
version, the data loaded during backing up is automatically
3
adjusted to the values of the current program version.
Load scale Cause: when switched on, the scale is in the underload range.
Remedial action:
1.) Attach the meat pan if necessary.
2.) Check load plate for being in contact with the housing.
3.) Check load cross for correct installation.
4.) Check weighing system for correct functioning.
5.) Replace weighing system and recalibrate the unit.
Log on cashier Appears in POS mode.

Cause:
the SC operates with log–on/log–off and a cashier is not logged
on.
Remedial action:
1.) Log on cashier.
Key [LOG ON/OFF VENDOR]
2.) Check the values set for the relevant vendor in DATA
MAINTENANCE / VENDOR DATA.
The setting CASHIER should be activated.
Log on vendor Appears in sales mode when log on/off is compulsory.

CONFIGURATION / DEVICE SETTINGS / SALES MODES /
LOG ON/OFF VENDOR YES.
Cause:
a vendor has not yet logged on to the vendor key selected.
M
6.126.98.1.01.70 15
Statusmessages SW

Main department XX Appears in DATA MAINTENANCE during the creation of depart-
not created ! ments.
Continue with <Enter> key Remedial action:
1.) First create the main departments. Only then create
the departments.
Main product group XX Appears in DATA MAINTENANCE during the creation of product
not created ! groups.
Continue with <Enter> key Remedial action:
1.) First create the main product groups. Only then create
the product groups.
Make up frequency report with clea- Appears in DATA MAINTENANCE during the change of range
ring settings for a frequency report.
Remedial action:
1.) For the frequency report which is to be modified, sales
figures are entered in the various reports. Modifications
can only be made if such sales figures are cancelled in
the report beforehand or if these figures are equal to zero.
Make up ticket! Appears in POS mode.

Function [no sale].
Cause:
a vendor who has opened a ticket cannot open the POS drawer
via the function [no sale]. Terminate ticket by first pressing the
total [ * ] key and then key [no sale].
Make up ticket ! Remedial action:

Articles from other dept. not menu point CONFIGURATION / DEVICE SETTINGS / SALES
permitted ! MODES / DEPARTMENT SPANNINGS is set to {TERMIN. ON
3 DEPT. CHANGE}.
This setting does not permit PLUs from different departments to
be called up and to be recorded on a ticket.
Markup/deduct. menu incor.
Max. value exceeded Appears in sales mode.

Remedial action:
check the settings of the sales limits for the totals in CONFIGU-
RATION / DEVICE SETTINGS / SALES LIMIT.
Mechan. printer part blocks ! Cause:

Eliminate disturbance or contact the paper feed blocks during printing.
after–sales service. Remedial action:
Continue with <Enter> key 1.) Ensure that the mechanical part of printer does not jam.
Remove jamming paper or labels.
Activate <Enter> key.
2.) Replace printer, the motor might be defective.
Menu position incorrect ! ! Appears in conjunction with functions during the selection of
Return to sales mode and press LEARN ON:
C–key. Remedial action:
1.) The LEARN ON function is only possible when keys
[Shift] + [Mod] are pressed to activate the function
menu in SALES PROCEDURES. The message appears
if [Shift] + [Mod] are activated somewhere in the menu.
16 6.126.98.1.01.70
Satusmessages SW

Monthly balancing still active ! Cause:
an active monthly evaluation was interrupted by switching off the
scale in conjunction with time recording.
Remedial action:
1.) Release monthly balancing in menu point OTHER
FUNCTIONS / TIME RECORDING / MONTHLY
BALANCING.
Multiplication invalid Appears in quick service mode.

Cause:
multiplications are only possible in conjunction with piece articles.
N
No access to vendor Cause:
appears in continuous sales mode if MULTI–VENDOR OPERA-
TION, SALES MODE are not identically set within the system.
Remedial action: check the settings on each SC.
No authorization for this department! Appears on log on/off of vendors.

Remedial action:
1.) Check the setting of the department number for the vendor
used in DATA MAINTENANCE / VENDOR DATA.
No counting PLU permitted Appears in sales mode.

Cause:
in the operating mode selected, a counting PLU is not permitted.
Remedial action:
1.) Check the article data of the PLU called up in ARTICLE
MAINTENANCE.
No customer data Appears during the input of the customer No. printed out in con
3
tinuous sales mode VEN. WITH CONS. CUST. NO.
Remedial action:
the customer No. printed out serves only to count the custo
mers. It does not offer access to the ticket data. Select continu
ous sales mode CUST./VENDOR NO. MAN. or CUST./VENDOR
NO. AUTO. in menu point CONFIGURATION / DEVICE SET
TINGS /SALES MODE.
No customer number Appears in continuous sales mode with customer/vendor linkage.

Cause:
the vendor used is not yet concatenated with a customer num-
ber.
No data loaded Appears during the EDP commissioning procedure.

Remedial action:
the text message PLEASE LOAD CONFIGURATION AND COM
MISSIONING DATA VIA EDP has been acknowledged too early
with the [ENTER] key. Load data via the PC with SWDasi befo
rehand.
Restart commissioning procedure.
No demo/test licence available Cause: appears when activating licence modules as test licences
which can be activated via the menu point OTHER FUNCTIONS / LICENCES / DEMO-
LICENCE as soon as the operating hour counter has reached the
operational counter value.
6.126.98.1.01.70 17
Statusmessages SW

No exchange rate entered Appears in sales mode or POS mode.
Remedial action:
1.) Check the values for the foreign currency used in DATA
MAINTENANCE / FOREIGN CURRENCIES.
No fixed weight permitted ! Appears in sales mode.

Cause:
a fixed weight PLU has been used which is only permitted in
price labeling mode.
Remedial action:
1.) Check the article data of the called up PLU in ARTICLE
MAINTENANCE.
No foreign currency configured Appears in POS mode.

Remedial action:
Enter relevant value in COMMISSIONING / OTHERS /
FOREIGN CURRENCIES.
No free record Appears in sales mode.

Cause:
ticket/journal memory full.
Remedial action:
1.) Terminate started tickets to obtain free memory and to
ensure further operations.
2.) Check the size of the ticket/journal memory in menu point
COMMISSIONING.
Recommissioning of unit may become necessary.
No free ticket number
3 No further data available,

scale error
Cause:
an SC has been switched off whilst an evaluation was active.
Bus disturbance.
Remedial action:
1.) Check cabling.
No general text under this number ! Appears in sales mode during calling up of a general text by
means of key [CALL GENERAL TEXT].
Remedial action:
1.) Check the text number entered.
2.) Check the input for the text No. used in menu point DATA
MAINTENANCE / TEXTS / GENERAL TEXTS.
No items Appears in sales mode.

Cause:
at the time the total is printed out, the vendor has not yet made
any sales.
No key assignment ! Cause:

First assign article to key. appears in ARTICLE MAINTENANCE when selecting a PLU
number via a direct PLU key. This key has no PLU assigned.
Remedial action:
1.) Check the settings for the direct PLU key in ARTICLE
MAINTENANCE / ARTICLE KEY ASSIGNMENT.
18 6.126.98.1.01.70
Satusmessages SW

No markups/deductions created un- Appears in sales or POS mode.
der this number Remedial action:
1.) Check the values for the markup/deduction used in DATA
MAINTENANCE / MARKUPS/DEDUCTIONS.
CONFIGURATION / CREATE KEYS
DATA MAINTENANCE / MARKUPS/DEDUCTIONS /
MARKUP/DEDUCTION KEY.
No module licence provided Cause:

appears when attempting to use a licensed function. Acquire a
licence number for this function.
No more record available Appears during the creation of frequency data.

Cause:
the 30 setting possibilities provided for hours or weekdays are
occupied.
No overwrite Cause: appears in sales mode.

PLU is locked in ARTICLE MAINTENANCE for price overwriting.
No recording Appears in sales mode.

Cause:
general error. Recording is refused.
Example:
Unit price 0,00 DM
Selling price 0,00 DM.
No software licence available ! Cause:

appears when selecting a function which has to be activated as a
licence module.
Remedial action:
to make use of the function, apply for a licence code and enter it
3
in the menu point OTHER FUNCTIONS / LICENCES / ACTI-
VATE SOFTWARE MODULE.
No subtotal in ticket sorting Cause:

appears in continuous sales mode in conjunction with ticket sor-
ting according to department, but only when using key [subtotal
with printout].
Subtotals may be displayed.
Not enough memory ! ! ! Appears after START COMMISSIONING.

Database cannot be created Cause:
the database cannot be set up with the commissioning values set
in menu point MODIFY COMMISSION. DATA.
Remedial action:
1.) Check the values set for correctness.
2.) Reduce the values if possible.
3.) Is there the possibility of partitioning the data?
Commission the system with partitionings.
4.) Install a memory extension card.
Clear the RAM and recommission the unit.
Not enough storage capacity in un- Appears in conjunction with multiple line text editors
buffered heap Cause:
Multiple line text editors cannot be set up in the unbuffered RAM
range.
Remedial action:
1.) Switch the SC OFF and back ON. This causes the
unbuffered RAM range to be cleared and redefined.
6.126.98.1.01.70 19
Statusmessages SW

Not enough ticket memory
No ticket data available Appears in sales mode during the input of the ticket No. via key
[Enter ticket number].
Remedial action:
1.) Check ticket No. entered for correctness.
Reenter the same if necessary.
2.) The ticket copy is no longer contained in the ticket/journal
memory.
Check the size of ticket/journal memory in
COMMISSIONING.
Check the settings for the ticket/journal memory in the
CONFIGURATION.
No ticket fr. ass. sales mode
No total markup/deduction Appears in POS mode.

Cause:
in the AMOUNT TENDERED menu, only the total markup/deduc-
tion key is accepted. The activation of any other markup/deduc-
tion keys causes this message to be output.
Not permitted ! Cause: an attempt was made to operate the unit in amount ten-
dered/change operation which is not permitted.
Remedial action:
1.) An activation of keys [Cheque], [Credit card], [Voucher]
immediately after a foreign currency conversion is not
permitted.
2.) A total discount granted on a negative total is not permitted.
3.) A total discount on a total equal to zero is not permitted.
3 Not possible in ticket sorting Appears in continuous sales mode with ticket sorting according
to department.
Cause:
in ticket sorting according to department, the following functions
are not possible:
– amount tendered/change function
– total discount
– assortment sale
No unit commissioned in system ! Cause:

unit in offline state.
COPY COMMISSIONING DATA or COPY CONFIGURATION
DATA is carried out directly after RAM clearing.
Remedial action:
1.) Switch OFF/ON SC on which the copy function was
carried out.
Number exceeds range. Please Appears during commissioning when creating a partitioning list
correct. for
– GENERAL TEXTS
– LABELS
Remedial action:
check all input values for correctness.
Incorrect, for example: from 1 to 200
Number: 300
Number of nutrients should not be Appears during COMMISSIONING. Special program for USA.
greater than number of PLUs !
20 6.126.98.1.01.70
Satusmessages SW
O
Offline Cause: problems in the system bus connection.
Remedial action: check the system bus cabling.
See index 6, ”Installation guidelines”.
One or more scales not in system Appears during creating, modifying or clearing of functions.
Remedial action:
and interfaces.
Open ticket still in system Cause:

appears on log–on of a vendor who has still an open ticket in the
system.
Remedial action:
1.) Terminate ticket with [total] or [partial ticket].
After that, logging off of vendor is possible.
Outside tare range Appears in sales procedures.

Remedial action:
scale is in underload range while an attempt is made to carry out
a taring operation.
Overflow during total forming Cause:

overflow in total sales calculation for POS or cashier’s report.
There is no need to react to it.
Overload Appears in sales mode.

Cause:
the scale is in the overload range when an attempt is made to
start recording.
3
Remedial action:
1.) Apply a smaller weight to the scale which is within the
weighing range of the SC.
6.126.98.1.01.70 21
Statusmessages SW
P
Partitioning list incorrect ! Appears during commissioning when creating a partitioning list
Please correct for
– PLU DATA
– GENERAL TEXTS
– LOGOS
Remedial action:
1.) Ensure that the values within a partitioning list do not
overlap.
E. g. incorrect correct
partition 1 from 1 to 5 partition 1 from 1 to 3
Partitions ascending, Appears during commissioning.

create only once ! Remedial action:
1.) The partition No. must be in ascending order in menu point
CREATE PARTITIONS,
e. g.: incorrect correct
partition 1 6 4
partition 2 5 5
partition 3 4 6
Password incorrect Appears on log on/off of vendor.

Cause:
the password used is incorrect.
Remedial action:
1.) Enter correct password.
The password may be read off in DATA MAINTENANCE /
3 VENDOR DATA under the relevant vendor No. When
printing out the vendor list, the password is not printed.
Please check input data
Please close POS drawer Cause:

appears in amount tendered/change operation if the next custo-
mer is to be served via key [ESC] with the drawer open and if
”drawer compulsory” is set.
Remedial action:
1.) Check the menu point CONFIGURATION /
POS / RECRD. W. DRAWER OPEN.
2.) Check the reread contact of drawer.
Please close POS drawer. Appears in POS mode.

Remedial action:
1.) Check reread contact of drawer.
2.) Check connecting cable of SC, POS drawer.
3.) Check connecting cable of CPU card
and POS drawer interface.
4.) Check fuse on POS drawer interface.
5.) Replace POS drawer interface.
Please load configuration and com Appears during the EDP commissioning procedure.
missioning data via EDP and conti
nue with <ENTER> key.
22 6.126.98.1.01.70
Satusmessages SW

Plug calibration jumper Appears in the SERVICE menu when selecting CALIBRATION or
LINEAR CALIBRATION.
Remedial action:
1.) Ensure that the calibration jumper SB201 on the
ADC 90 is closed when selecting the above menu points.
PLU not created Appears during the creation of assortments.

Cause: the PLU selected is not created.
Remedial action:
1.) Enter the correct PLU No.
2.) Create the PLU via ARTICLES / GENERAL
MODIFICATION.
PLU not found Appears in sales mode.

Remedial action:
1.) Check the PLU selected in ARTICLE MAINTENANCE.
2.) Enter the correct PLU No.
Pay attention to the department organization.
PLU not stored / Cause:

inactive scales appears during the selection ARTICLE MAINTENANCE if some
of the scales connected to the system are inactive.
Remedial action:
2.) Carry out CONFIGURATION / RESTORE SYSTEM
NETWORK
3.) Check cabling.
POS From program version 4.0 onward

Cause: appears in POS mode when the limit set for the mone-
tary holdings is reached. This message indicates that an uplift
has to be made.
3
Remedial action:
1.) Check the settings in menu point CONFIGURATION /
DEVICE SETTINGS / SALES LIMITS.
POS drawer X Appears in POS mode.

not connected Remedial action:
1.) Check the values set for the relevant vendor in DATA
2.) Check the connecting cable between SC and drawer.
3.) Check the connecting cable between backplane and POS
drawer interface.
4.) Check the fuse on the POS drawer interface.
5.) Replace the POS drawer interface.
6.) Replace the POS drawer.
POS sales available ! Appears during the modification of the station address in menu
Draw up POS report with clearing. point CONFIGURATION / SYSTEM.
Remedial action:
POS sales is data specifically stored for the relevant device. The
SC does not permit the station address to be modified as long as
this data is stored. POS reports are to be evaluated ”with clea-
ring”. The station address may be changed afterwards.
6.126.98.1.01.70 23
Statusmessages SW

POS sales tables not created. Cause: appears during the evaluation of POS reports on an SC
which was commissioned without POS reports.
Remedial action:
1.) Evaluate the POS report on an SC which has POS
reports created.
2.) Check the commissioning data.
Preset tare error Appears in sales mode.

Remedial action:
ensure that the input of a known tare made on a two–interval
scale lies in the lower partial weighing range.
Press commod. key Appears if the operating mode SELF–SERVICE is activated.
Price basis invalid Appears in sales mode.

Remedial action:
1.) Check the setting of price basis for the PLU selected in
ARTICLE MAINTENANCE. The price basis (kg, lb,
oz) set must be identical to that used for the calibration
of scale.
Price group wrong Cause: appears if a second price group is to be used within a
ticket which has been opened with another price group. This is
not permitted.
Remedial action: within a ticket, there is no possibility of
changing to another price group. Terminate the ticket and pro-
cess the new ticket with the price group desired.
Primary printer inactive Cause:

3 the primary printer selected in menu point
CONFIGURATION / PRINTER / GENERAL is wrong. This might
happen after copying of configuration data from an SC 800 TE.
Print. of old tickets Cause:

when switched on, scale prints tickets which were not terminated
via total [ * ] at the time the scale was switched off.
Remedial action:
1.) There is the possibility of suppressing the printout of
old tickets.
CONFIGURATION / DEVICE SETTINGS /
BAS. SELLING PRICE SETTINGS / PRINTOUT OF OLD
TICKETS.
Print bar open ! Appears during printing with label printer.

Continue with label print, ticket print Remedial action:
or label print on tally roll ? 1.) Close print bar.
2.) Check reflex light barrier on printer.
3.) Check connecting cable between printer controller and
light barrier.
24 6.126.98.1.01.70
Satusmessages SW

Printer does not respond ! Cause:
Continue with <Enter> key appears if the printing procedure is started and the printer does
not respond.
Remedial action:
printer.
Ensure that the program versions of the printer controller and the
CPU card are correct.
Printer setting incorrect ! Cause:

Switch scale OFF/ON, adjustment carried out during self–adjusting procedure of printer
continue with <Enter> key is incorrect,
e. g.: no paper inserted or the printer has run out of paper during
the adjustment.
Remedial action:
1.) Switch unit OFF/ON which causes the adjusting procedure
to be automatically repeated.
If message recurs:
Printer stack overflow on Cause: internal error.

changeover !
Printhead overheated ! Appears during printing.

Continue with <Enter> key Cause:
the maximum temperature of 60° has been reached.
Remedial action:
1.) Allow printhead to cool down.
3
2.) Check connecting cable on printhead for proper seating.
If necessary secure with adhesive.
If error recurs:
R
RamE error Cause: hardware error in RAM range.
Remedial action:
Recommission unit.
Record not created Appears in sales or POS mode.

Remedial action:
1.) Check the keyboard programming by ensuring that the
markup/deduction assigned to the key is correct.
– CONFIGURATION / CREATE KEYS
– DATA MAINTENANCE / MARKUPS/DEDUCTIONS /
MARKUP/DEDUCTION KEYS
2.) Check the markup/deduction used is created in DATA
MAINTENANCE under MARKUPS/DEDUCTIONS.
6.126.98.1.01.70 25
Statusmessages SW

Red. ticket in journal Cause:
appears in continuous sales mode with ticket include after input
of the ticket No. via key [Enter ticket No.].
The ticket called up is stored in the journal in a reduced form
only, i. e. it consists only of the total line and may not be used for
the include function.
Remedial action:
1.) For the use of the include function, the setting must be as
follows:
CONFIGURATION / JOURNAL / TICKET / TICKET ITEMS
{COMPLETE WITHOUT TEXT}.
Reduced by relevant items
Related database table not created Appears during the creation of assortments in ARTICLE
MAINTENANCE.
Remedial action:
1.) Check the settings NUM. OF ASSORTM. OFFERS and
NUM. OF ART. ASSORTMENT in COMMISSIONING / PLU
DATA. Ensure the values entered are correct and start
commissioning.
Remove paper from printer, close Cause:

print bar and appears if the menu point LEARN MODE FOR END OF PAPER
continue with [ENTER] is carried out.
Repeat recording ! Appears in continuous sales mode after the change of place of
installation and the first recording on the scale.
Cause:
error in the transmission of ticket data from scale to scale.
3 Remedial action:
only the last recording must be repeated.
If error recurs:
2.) Carry out CONFIGURATION / RESTORE SYSTEM
NETWORK.
3.) Check cabling.
Report being established by other Appears during the printout of a report.

scale. Cause:
the printout of an identical report has already been started
on another scale.
1.) Wait for the SC to terminate the current evaluation and
successively restart the printout of report.
The evaluation of an identical report has been started via

the EDP.
1.) Wait for the EDP to terminate the current evaluation and
successively restart the printout of report.
RomE error Cause: hardware error in ROM range.

Remedial action:
1.) Replace CPU–EPROMs.
Recommission unit.
26 6.126.98.1.01.70
Satusmessages SW
S
Scale management error Appears during calibration.
Remedial action: 1.) Ensure correct zero load.
Scale not commissioned on system. Appears when adding a scale to an active system.
Add scale to system ? Cause:
Yes / No the database structure of the scale added does not agree with
that of the active system. The scale is however not entered in the
supertable of the active system.
Remedial action:
1.) Acknowledge request with YES.
The scale is recorded in the supertable of the active
system.
2.) Check the database structure for uniformity.
Acknowledging the message with NO causes the unit to be re-
commissioned.
Scale not suitable for counting Appears in POS mode if an attempt is made to count the cash in
the POS balance i. h. with COUNTING HELP BY WEIGHING.
Cause:
the weighing system connected must be provided with a scale
interval of at least 2 g.
Scale unstable Cause:

when switched on, the scale is in an unstable environment
(draught, vibrations).
Remedial action:
1.) Change the place of installation.
2.) Reset the sensitivity of scale (market scale program)
CONFIGURATION / SCALE. 3
Script not initialized Remedial action:
1.) Check battery and replace if necessary.
Selected vendor key occupied by Appears in sales mode on log on/off of vendors.
vendor X. Remedial action:
Select other key. 1.) The vendor key selected is already occupied by another
vendor. Any other vendor key may be activated to which
the vendor is then logged on.
Selection range invalid Appears when calling up sales via the EDP.
Remedial action:
1.) An invalid range was specified in the selection parameters.
Correct selection ranges.
Restart call.
Semaphore received, but evaluation Cause: table inactive.

active in system Remedial action:
1.) Modify commissioning data and restart commissioning.
Simultaneous evaluation on more Appears in conjunction with reports if identical POS reports are
than one scale not permitted ! ! ! evaluated on several SC scales.
6.126.98.1.01.70 27
Statusmessages SW

Sort. inactive Cause:
appears in sales mode when using assortment PLUs
and activating keys [call assortment PLU] and [vendor].
The vendor selected has not yet started an assortment sale.
Sort. not created Appears in sales mode when using assortment PLUs
and after the input of the assortment No. with key [assortment
sale].
Remedial action:
1.) Enter the correct assortment No.
2.) Check whether or not an assortment has been created for
the assortment number entered in ARTICLE
MAINTENANCE / ASSORTMENT OFFER.
Sort. not opened Appears in sales mode when using assortment PLUs and after
activation of keys [call assortment PLU] and [vendor].
Cause:
the vendor selected has not yet started an assortment sale.
Sort. still active Appears in sales mode when using assortment PLUs
and after the input of the assortment No. with keys [assortment
sale] and [vendor].
Cause:
The vendor selected already operates with another assortment
which must first be terminated before the next assortment can be
called up.
SP too high Appears in sales mode.
3 Remedial action:
check the settings for the sales limit in CONFIGURATION /
DEVICE SETTINGS.
Storage management destroyed ! Appears in START COMMISSIONING.

Clear all data and recommission Remedial action:
scale ??? 1.) Acknowledge message with YES.
YES/NO
Storage management destroyed ! Cause: the RAM content is in an undefinable state.

Recommission scale. Remedial action:
1.) Check the battery voltage on the CPU card.
U > 2,6 V. Replace the battery if necessary.
3.) If the error recurs, replace the CPU card.
Switch off scale and remove calibra- Appears after termination of the calibration procedure.
tion jumper !
System error
28 6.126.98.1.01.70
Satusmessages SW
T
Table element not created
Table from g–database unknown Cause: internal error.
Table not configured Appears during the selection of menu point

FREQUENCY REPORT.
Remedial action:
1.) Check commissioning values for the frequency reports.
Start commissioning.
Appears during sales recalls via the EDP.
Remedial action:
1.) A report with a special sales period 0 must not be created in
COMMISSIONING. All reports must be activated.
Modify commissioning data and restart.
Table not created Appears in DATA MAINTENANCE.

Remedial action:
1.) Check commissioning values for the data used.
Tare occupied Appears in sales mode.

Cause:
a preset tare must not be overwritten with a fixed tare value.
Taring not ok Appears in sales mode.

Cause:
PLU tare, fixed tare value and preset tare must not be mixed with
one another.
Text XXX
characters too long ! ! !
Appears in ARTICLE MAINTENANCE during the input of article
text.
3
Remedial action:
Text not stored ! ! ! to permit the storage of text, shorten the latter by the indicated
number of characters. The text length should not exceed 500
characters / 20 lines.
Both messages appear in succession.
Ticket entered for forced

cancellation
Ticket of cancelled vendor still in Appears in sales mode during log on/off of vendors.
system Cause:
an open ticket started by a vendor who was cancelled in DATA
MAINTENANCE is still in the system. The key assigned to the
vendor cancelled is thus not released for a new vendor.
Remedial action:
1.) Create the cancelled vendor once again, terminate
the open ticket with the total [ * ] key and cancel vendor
again.
Ticket already included in another Appears in continuous sales mode with consecutive ticket No.
ticket! Cause:
the ticket number selected has already been included in an
other ticket.
Remedial action:
search for the ticket No. via the menu point REPORTS / JOUR
NAL / TICKET JOURNAL to determine the ticket in which the
ticket selected has been included.
6.126.98.1.01.70 29
Statusmessages SW

Ticket already made up !
Ticket cannot be called up at Cause: bus overloading.

present. Remedial action: repeat ticket call.
Please repeat !
Ticket cannot be cancelled
Ticket data incorrect ! Cause: ticket data is incorrect.

Repeat recording ! Remedial action: the ticket memory is full.
1.) Check setting CANCEL TICKET in menu point
CONFIGURATION / JOURNAL / TICKET.
If {no} is selected here, it should be ensured that the ticket
memory is evaluated and cleared at regular intervals.
If not, set menu point to {automatic}.
Evaluate the ticket memory via REPORTS / JOURNAL /
TICKET JOURNAL with clearing.
Transmission error in continuous sales mode

1.) Check system cabling.
2.) Check system interface.
Ticket incomplete,
transmit error record !
Ticket item could not be accounted. Cause: item could not be entered in sales tables.
Remedial action: repeat recording procedure.
Ticket made up Appears in sales mode.

3 Remedial action:
repeat ticket printout by activating keys [ * ] [vendor key].
Ticket not found Appears in sales mode during the input of ticket No. via key [en-
ter ticket No.].
Remedial action:
1.) Check ticket No. entered for correctness.
2.) Ticket copy no longer contained in ticket/journal memory.
Check size of ticket/journal memory in COMMISSIONING.
Check settings for ticket/journal memory in
CONFIGURATION / JOURNAL / TICKET.
Ticket not processed,

transmit error record
Ticket sorting acc. to dept. Am. Appears in sales mode.

tend./change op. n. permit. Remedial action:
1.) The two settings CONFIGURATION /
DEVICE SETTINGS / SALES MODES /
TICKET SORTING TO DEPT. YES and CONFIGURATION /
POS / AMOUNT TEND./CHANGE OP. YES
cannot be activated at the same time.
Ticket status invalid
30 6.126.98.1.01.70
Satusmessages SW

Ticket to be included already can Appears in continuous sales mode with consecutive
celled ! ticket number.
Cause:
the ticket number selected has already been cancelled via
menu point TICKET CANCEL or REPORT / CANCEL TICKET
and may no longer be called up in SALES MODE.
Ticket type invalid Appears in price group mode 1, 2 or 3.

Remedial action:
1.) A ticket started with one of the above price groups may not
be changed to another price group during sales procedures.
Terminate ticket by drawing the total [ * ] and start new
ticket with the price group desired.
Ticket without reference,

has been cancelled.
Timeout
Too many incor. entries ! Cause:

Switch device off/on ! appears during the activation of licence modules, in the event
that the licence code was five times incorrectly entered.
Total overflow Appears in POS/cashier’s report.

Cause:
the values in the report exceed 9 999 999 which prevents a
total report from being printed.
Total w. soon be neg. Appears in sales mode.

Cause:
ticket with a negative total not permitted.
Remedial action: 3
check the setting of the sales limits in
CONFIGURATION / DEVICE SETTINGS / NEGATIVE RESULT.
Transmisssion parameters for Remedial action: 1.) Switch SC OFF/ON.

creation of menu incorrect
6.126.98.1.01.70 31
Statusmessages SW
U
Unbuffered heap corrupt Appears in conjunction with multiple line text editors.
Cause:
the text editor cannot be set up in the unbuffered RAM range.
Remedial action:
1.) Switch SC OFF/ON. The unbuffered range is cleared and
redefined.
Unbuffered heap too much Appears in conjunction with multiple line text editors.
fragmented Cause:
the text editor cannot be set up in the unbuffered RAM range.
Remedial action:
1.) Switch SC OFF and back ON. This causes the unbuffered
RAM to be cleared and redefined.
Unit price invalid Appears in sales mode.

Cause:
a unit price of 0,00 DM is only permitted in price labeling mode or
sales mode SALE W/O PRICE.
Unit price too high Appears in sales mode.

Remedial action:
check the settings of the sales limits in CONFIGURATION /
DEVICE SETTINGS / SALES LIMITS.
Unload scale Cause:

when switched on, the scale is in the overload range.
Remedial action:
1.) Withdraw any load which might be applied to the load plate.
3 2.) Check load plate for free movement.
3.) Check load cross for correct installation.
5.) Replace weighing system and recalibrate the unit.
Appears when the operating mode ”Self–service operation”

is activated.
32 6.126.98.1.01.70
Satusmessages SW
V
Value invalid Cause:
appears in sales mode in conjunction with incorrect fraction–oz–
weight values for tare and manual weight input in the fraction–
oz–range.
Example: 9/8 Oz.
Vendor dept. menu incorrect
Vendor invalid Appears in sales mode.

Cause:
the SC is set to ”WITHOUT MULTI–VENDOR OPERATION” in
CONFIGURATION / DEVICE SETTINGS.
Remedial action:
if a vendor has started a ticket on the device, the next vendor
may only start operations after the first one has drawn the
total [ * ].
Vendor is not a cashier The SC is operated with the settings CONFIGURATION / POS /
AMOUNT TEND./CHANGE OP. YES. Only vendors created as
cashiers are authorized to terminate tickets on this SC via the
total key [*].
Remedial action:
check the settings of the relevant vendor in the menu point DATA
Vendor not permitted as a cashier Appears in POS mode or in menu point OTHER
FUNCTIONS / POS.
3
Remedial action:
1.) Check the values for the vendor used in DATA
2.) Check the keyboard programming
DATA MAINTENANCE / VENDOR DATA /
VENDOR KEY.
Vendor not permitted as a cashier Appears in POS mode or in menu point OTHER
on this device FUNCTIONS / POS.
Remedial action:
1.) Check the values for the vendor used in DATA
2.) Check the keyboard programming
DATA MAINTENANCE / VENDOR DATA /
VENDOR KEY.
Vendor number invalid
Vendor occupied Appears in sales mode.

Cause:
the vendor used is busy with another transaction on another SC
scale, e. g. he prints out a ticket, carries out a paging function or
similar. He will only be released when the function has been ter-
minated.
Vendor on scale occupied
6.126.98.1.01.70 33
Statusmessages SW

Vendor selected not created Appears in sales mode in conjunction with ’log on/off vendor’.
Remedial action:
1.) Check the values for the relevant vendor in DATA
DATA MAINTENANCE / VENDOR DATA / VENDOR
KEY. Ensure that the vendor No. assigned to the vendor key
is correct.
Vendor table not created Appears in POS mode.

Remedial action:
W
Warning ! ! Cause: the scale has reached the minimum value for the main
Main memory full ! memory.
Remedial action:
if the menu point ARTICLE MAINTENANCE is cancelled, carry
out data backup and recommission the unit by reloading the data
backup. Deselect database tables which are no longer used du-
ring commissioning or install a RAM extension card.
Weighing not possible Appears in POS mode if an attempt is made to count the cash in
POS BALANCE I. H. with COUNTING HELP BY WEIGHING.
Remedial action:
1.) The SC used is not provided with a weighing system.
2.) If a weighing system is installed check the same for correct
functioning.
3 You have pressed wrong foreign Appears in POS mode.
currency key ! Remedial action:
1.) The amount to be paid was converted into a foreign
currency and the amount tendered had to be reconverted
into another foreign currency. This is not permitted.
Z
Zero tracking error Appears in sales mode.
Cause:
error in zero tracking. Scale is above the country–specific, per-
mitted automatic zero setting range.
Remedial action:
1.) Check load receptor for correct assembly.
34 6.126.98.1.01.70
Satusmessages SW
6.126.98.1.01.70 35
Statusmessages SW
36 6.126.98.1.01.70
Satusmessages SW
1.2 General information about status messages
Valid up to field test program version 1998/03/30.

The error messages of the SC are generally indicated together with texts which are self–explanatory .
The various error conditions are displayed by 1 to 5–digit error numbers. These are listed hereunder by their
cause and recommended remedial measures. The procedures are numbered and the sequence given
should be strictly adhered to. If the prescribed measures do not help in the correction of any particular error,
carry on with the next number. If the problem cannot be solved, contact your product manager.
Contact your product manager only in respect of error messages appearing on the display of
the SC which cannot be corrected with the aid of this list.
A 1 to 5–digit status number may occur on the SC in conjunction with a text message. Text messages are
listed from page 1 onwards.
A 1 to 5–digit status number may appear in the log of the SC. The log serves to analyze errors which might
occur. It may be printed out and cleared via menu point SERVICE / LOG.
A 1 to 5–digit status number may appear on the PC in the two log files SWC_ERR.LOG and
SWC_BAT.LOG. Both files are automatically created by the PC program SWCom.
1.3 Status numbers of basic BOS software, numbers 1 – 24999
BOS represents the basic software on which the application software is based.
The error messages normally appear in the log only. If messages are transmitted to the application software
by BOS, they are filtered by the application software and output to the vendor’s display.
There is, however, also the possibility of outputting BOS error messages directly to the display. 3
Status No. Cause / remedial action
1 Cause: task ID error.
2 Cause: no TCBs available.
3 Cause: no memory available.
4 Cause: not a memory block.
5 Cause: mailbox in use.
6 Cause: zero message.
7 Cause: buffer full.
8 Cause: WAITC in progress.
9 Cause: invalid system call.
10 Cause: timeout.
6.126.98.1.01.70 37
Statusmessages SW
11 Cause: no message present.
12 Cause: queue ID error.
13 Cause: queue full.
14 Cause: partition ID error.
15 Cause: fatal initialization error.
16 Cause: no character present.
17 Cause: invalid configuration table parameter.
18 Cause: invalid input parameter.
32 Cause: component vector table not present.
33 Cause: undefined component.
34 Cause: undefined opcode for component.
48 Cause: no control blocks available.
49 Cause: ev flag group or semaphore ID error.
50 Cause: tasks pending on ev flag group / semaphore.
51 Cause: ev flag group or semaphore deleted.
3 52 Cause: ev flag already set or semaphore overflow.
78 Cause: continuous sale with vendor discount.

An attempt is made to include several tickets in the same ticket by granting a discount
to different vendors. This is not possible.
150 Cause: general system error.
151 Cause: NIL address.
152 Cause: function No. invalid.
153 Cause: module number invalid.
154 Cause: configuration not found.
155 Cause: error during the creation of USER_HB.
156 Cause: error during the creation of USER_HU.
157 Cause: error during the creation of SYS_HB.
158 Cause: error during the creation of SYS_HU.
159 Cause: bus error during test.
160 Cause: invalid parameters.
161 Cause: EPROM error during test.
162 Cause: RAM error during test.
38 6.126.98.1.01.70
Satusmessages SW
163 Cause: battery on CPU defective.
204 Cause: resource init. error.
250 Cause: general resource error.
251 Cause: resource not existing.
252 Cause: method wrong. Caution !
253 Cause: resource path name invalid.
254
255 Cause: resource incorrect.
256 Cause: resource map full.
304 Cause: initialization error.
351 Cause: queue not created.

Error during entry in log.
352 Cause: task not started.

Remedial action: see status No. 351.
353 Cause: write error in queue.

354 Cause: read error from queue.
355
Cause: log not found.

3
356 Cause: log full.

Error during entry in log.
Remedial action: 1.) Clear log.
357 Cause: log update error.

358 Cause: log update error.

359 Cause: error in Ptr list of log.
401 Cause: overflow error.
403 Cause: error in parameter.
405 Cause: device driver function error.
407 Cause: device driver ID error.
450 Cause: general error.
6.126.98.1.01.70 39
Statusmessages SW
450 Cause: error during repetition of print command. Printer error.

Disturbance in transmission path CPU card, printer controller.
Remedial action:
1.) Check plug connections, connecting cables.
451 Cause: timeout error.

Printer error.
Remedial action:
452 Cause: LRC error.

Printer error.
Transmission path CPU card/printer controller interfered by external source.
Remedial action: 1.) Check environment for interfering influences and eliminate them.
453 Cause: warning, too many LRC errors. Printer error.
454 Cause: idleloop table full.
455 Cause: pointer in the idleloop.

Contact your product manager.
456 Cause: grid error (1st or 2nd display).

Display error.
Display on vendor’s or purchaser’s side defective.
Remedial action:
3 1.) Carry out display test or visual inspection.
Replace defective display.
457 Cause: grid error (2nd display absent), display error.
458 Cause: Anode error.

Display error.
Remedial action:
1.) Carry out display test or visual inspection.
Replace defective display.
459 Cause: timeout.
460 Cause: drive not ready.
461 Cause: CRC error.
462 Cause: seek error.
463 Cause: sector not found.
464 Cause: write error.
465 Cause: generic error.
466 Cause: hardware error.
467 Cause: check condition.
480 Cause: basis No. for memo and flash.
40 6.126.98.1.01.70
Satusmessages SW
491 Cause: sector length of flash chips too large.
492 Cause: flash range too small.
493 Cause: invalid cache parameters in DDfldCreate.
494 Cause: error during writing of byte in flash memory.
495 Cause: error during deleting of sector in flash memory.
496 Cause: flash module type unknown.
497 Cause: internal error in flash device driver.
498 Cause: no dirty block in cache. Status message.
499 Cause: job request invalid.
500 Cause: disk block number invalid.
501 Cause: function code invalid.
502 Cause: info for DDfldCreate.
1001 Cause: overflow.

Error on component bus, system bus, general bus error.
Remedial action:
1.) Check plug connections within the scale.
2.) Check cabling and bus terminating resistors.
3.) Replace interface card. 3
4.) Check +5V LAN supply voltage.
5.) Observe the maximum cable length.
1005 Cause: function not available.
1006 Cause: fatal error.
1011 Cause: handle not existing.
1015 Cause: handle timer not existing.
1022 Cause: timeout expired.
1051 Cause: parameters incorrect.
1052 Cause: ISR vector absent.
1053 Cause: condition not reached.
1054 Cause: double address in system.
1055 Cause: error in remote station.
1056 Cause: error in own station.
1057 Cause: confirmation handle absent.
1075 Cause: station moves to ring.

Appears after swich ON/OFF of unit.
6.126.98.1.01.70 41
Statusmessages SW
1091 Cause: function Pb2MacReInit.
1094 Cause: function Pb2MacError.
1097 Cause: function Pb2Stop.
1110 Cause: handle error.
1111 Cause: queue ID wrong.
1113 Cause: taskID incorrect.
1115 Cause: memory error.
1119 Cause: initialization parameters incorrect.
1150 Cause: cache overflow.
1151 Cause: parameter error.
1152 Cause: semaphore occupied by local application.
1153 Cause: semoaphore requested by local application.
3 1154 Cause: semaphore was not occupied, should, however, be activated.
1155 Cause: error by reinitialization of cache.
1156 Cause: transition of condition to be executed not permitted.
1157 Cause: request by external source at non–locally managed semaphore.
1158 Cause: protocol error, change of holder during local occupancy.
1159 Cause: semaphore not occupied after a transaction.
1161 Cause: profibus error.
1162 Cause: semaphore could not be occupied.
1163 Cause: PDU coding incorrect.
1164 Cause: unexpected service primitive from layer 2.
1165 Cause: confirmation mailbox in use.
1166 Cause: indication mailbox in use.
1170 Cause: status request, holder locally known.
1171 Cause: status request, holder locally unknown.
42 6.126.98.1.01.70
Satusmessages SW
1204 Cause: component bus not initialized. Error on component bus.

Remedial action:
1.) Switch scale OFF/ON.
2.) Check all plug connections within the SC.
1205 Cause: function not implemented.

Remedial action: internal message.

No unbuffered memory available or no memory available for operating system.
Remedial action:
2.) If error remains:
Clear RAM and recommission unit.
1219 Cause: component bus parameters not in order.

1271 Cause: LSAPs not created.
1272 Cause: gap range has been changed.
1273 Cause: polling list could not be defined.
1274 Cause: polling not possible because of insufficient memory.
1275 Cause: FDL parameters could not be set.
1276 Cause: no data available.
1381 Cause: hardware error on system bus. 3

Remedial action:
1.) Check cabling and interfaces.
1404 Cause: interface already initialized in Edvinit.

Error on EDP connection.
Appears in log of SC or in log files SWC_ERR.LOG and SWC_BAT.LOG of SW_COM.
Remedial action:
1.) Check connecting cable between PC and SC.
2.) Replace interface.
1415 Cause: connection setup not possible. Unit not ready to receive or not enough space
available.
1451 Cause: parameters not permitted.

Parameters in menu point CONFITURATION/SERIAL INTERFACE incorrectly set.
Remedial action:
1.) Ensure that parameters are correctly set.
6.126.98.1.01.70 43
Statusmessages SW
1452 Cause: handle wrong.

1453 Cause: no free handle or in conjunction with EdvPut: high–priority job already active.
An attempt was made to modify the transmission parameters during data transmission.
Remedial action:
1.) Repeat data transmission.
1454 Cause: connection or high–priority job active.

Appears on EDP connection.
1455 Cause: waiting state.
1456 Cause: waiting state and remote station not ready to receive.
Remedial action:
1.) Scale failed during data transmission or interruption of modem connection.
1457 Cause: put not executed. Cancel since remote station is not ready to receive.
Remedial action:
1.) Repeat transmission.
2.) Check cable between SC and PC.
3.) Check interface settings in SC.
Menu point CONFIGURATION / SERIAL INTERFACE.
4.) Check modem.
3 1458 Cause: cancel by user.

Job cancelled by EdvDisc.
1459 Cause: connection cannot be set up.

Remedial action:
1.) Switch on SC.
2.) Check connecting cable and connectors. Ensure cable is correct and secured.
3.) Check channel number, block check procedure (CRC or LRC) and baud rate.
4.) Replace EDP interface on SC.
5.) Ensure interface in PC is correctly set and configured.
6.) Replace interface card in PC.
1460 Cause: CTS failure.

Remedial action:
1.) Check connecting cable and connectors on PC. Ensure cable is secured.
2.) Check channel number.
3.) Ensure modem is switched on.
1461 Cause: cancel due to HDLC protocol error.

1462 Cause: no connection active.

44 6.126.98.1.01.70
Satusmessages SW
1463 Cause: ID with incorrect length from remote station.

1464 Cause: incorrect response to TEST telegram.

1465 Cause: no VRTX queue for receive WS.

1466 Cause: UI telegram lost.

1467 Cause: UART cannot be assigned.

1468 Cause: error in timer manager.

1469 Cause: network connection interrupted.

1470 Cause: transmission with EdvKillHdl unsuccessful.

1471 Cause: kill–handle unsuccessful.

1472 Cause: identifier incorrect.

3
1473 Cause: telegram too large.
1474 Cause: put already started.



1485 Cause: FRMR received.

1487 Cause: modem has no connection.
1496 Cause: modem error.

1497 Cause: baud rate incorrect.

1498 Cause: interface error.

1499 Cause: system cannot be initialized.

1651 Appears on EDP connection.
6.126.98.1.01.70 45
Statusmessages SW
1705 Cause: function not available,

see status No. 1404.

No more resource memory available.

Parameters in menu point CONFIGURATION / SERIAL INTERFACE incorrectly set.
Remedial action:
1.) Adjust parameters.
1751 Cause: acknowledge error.

Remedial action:
1.) Check connecting cables.
2.) Replace interfaces.
1752 Cause: telegram error.

Remedial action:
1.) Check connecting cables.
2.) Replace interfaces.

3 Error on system bus.
Remedial action:
1810 Cause: SAP handle incorrect.

Error on system bus.
1819 Cause: parameter incorrect.

1851 Cause: packing cancel.
Bus overloading, bad bus connection.
Remedial action:
2.) Replace interface card.
3.) Ensure that the maximum total cable length is not exceeded.
1852 Remedial action: see status No. 1810.
46 6.126.98.1.01.70
Satusmessages SW

1853 Cause: no telegram received.
Bad bus connection.
Remedial action:
3.) Ensure that the maximum total cable length is not exceeded.
1854 Cause: error on system bus.

Bus overloading.
1855 Cause: checksum error incorrect.

1856 Cause: internal bus overloading.

ADC error.
Remedial action:
1.) Check ADC plug connections.
2.) Replace weighing system and recalibrate unit.
2005 Cause: software function not available.

ADC error.
2006 Cause: manager not operating.
2007
Cause: indicated ID incorrect.

3

2016 Cause: component bus error.

ADC errror.
Remedial action:
1.) Check plug connections on CPU card and ADC.
2.) Replace weighing system. Recalibrate unit.
2019 Cause: incorrect parameters.

2051 Cause: calibration incorrect.

ADC error.
Remedial action:
1.) Recalibrate unit.
2052 Cause: queue error.

2053 Cause: ADC can no longer be addressed.

ADC error.
Remedial action:
1.) Check plug connections on CPU card and ADC.
6.126.98.1.01.70 47
Statusmessages SW
2054 Cause: execution of function not permitted in this mode.

ADC error.
Remedial action:
1.) Jumper SB201 for calibration not yet removed.
2055 Cause: identifier not permitted.

ADC error.
Weighing system used incorrect.
Remedial action: 1.) Use correct weighing system.
2056 Cause: checksum error.

2057 Cause: timeout error, ADC error.

Remedial action:
1.) Check plug connections to ADC.
2104 Cause: not initialized.

ADC error.
Remedial action:
1.) Check plug connections to ADC.

2107 Cause: ID incorrect.
3 2119 Cause: incorrect parameters.

2151 Cause: checksum incorrect, ADC error.

EEPROM on ADC defective.
2152 Cause: command incorrect,

2153 Cause: no write right,

2154 Cause: transmission incorrect,

2155 Cause: ADC90 mode incorrect,

2304 Cause: heap too small to initialize.

Error in storage management.
2306 Cause: error in heap management,

2351 Cause: memories full.

If error occurs during creation of master data:
1.) Clear texts which are no longer used.
Volume of data to be stored too large.
2.) Check commissioning values.
48 6.126.98.1.01.70
Satusmessages SW
2352 Cause: polling error,

2353 Cause: pointer in disallowed range,

2354 Cause: indicated heap incorrect,

2355 Cause: heap too much fragmented,

2357 Cause: heap too small to create,

2382 Cause: indicated data not fully transmitted,

2383 Cause: error in heap management.

1.) Check all master data for completeness and correctness.
Carry out backup if data is still correct.
2.) Recommission scale.
2401 Cause: maximum number of timers reached.

Timer error on CPU.
2404 Cause: timer task not installed.

3
2405 Cause: no action function available.
2410 Cause: timer handle not existing.

2451 Cause: parameters not in order.

2550 Cause: generic error.
2551 Cause: no such device.
2552 Cause: read error.
2553 Cause: write error.
2554 Cause: partition error.
2555 Cause: buffer error.
2556 Cause: password incorrect.
2558 Cause: wrong mode.
6.126.98.1.01.70 49
Statusmessages SW
2560 Cause: no partition error.
2561 Cause: not the owner.
2561 Cause: disk_full error.
2563 Cause: no such process.
2566 Cause: no such device or address.
2573 Cause: permission denied.
2577 Cause: file exists.
2582 Cause: invalid argument.
2584 Cause: too many open files.
2592 Cause: broken pipe.
2595 Cause: operation would block.
2596 Cause: operation now in progress.
2597 Cause: operation already in progress.
2598 Cause: socket operation on non–socket.
3 2599 Cause: destination address required.
2600 Cause: message too long.
2601 Cause: protocol wrong type for socket.
2602 Cause: protocol not available
2603 Cause: protocol not supported.
2605 Cause: operation not supported on socket.
2607 Cause: address family not supported.
2608 Cause: address already in use.
2609 Cause: can’t assign request address.
2610 Cause: network is down.
2611 Cause: network is unreachable.
2613 Cause: software caused connection abort.
2614 Cause: connection reset by peer.
2615 Cause: no buffer space available.
2616 Cause: socket is already connected.
2617 Cause: socket is not connected.
50 6.126.98.1.01.70
Satusmessages SW
2620 Cause: connection timed out.
2621 Cause: connection refused.
2624 Cause: host is down.
2625 Cause: no route to host.
2640 Cause: illegal scall parameter in config.
2641 Cause: not enough local memory.
2642 Cause: ARP table cannot hold all.
2643 Cause: host unknown.
2644 Cause: bad internet address.
2645 Cause: bad net part in internet address.
2646 Cause: not enough global memory.
2647 Cause: bad block parameter in config.
2648 Cause: fail to lock global lock.
2649 Cause: missing CDT in configuration table.
2650 Cause: panic; in – in_control.
2651 Cause: panic; icmp – icmp_error.

3
2652 Cause: panic; icmp – length.
2653 Cause: panic; ip – init.
2654 Cause: panic; raw – user req.
2655 Cause: panic; route – free.
2656 Cause: panic; tcp – pull oob.
2657 Cause: panic; tcp – output.
2658 Cause: panic; tcp – output REXMT.
2659 Cause: panic; tcp – usrreq.
2660 Cause: panic; udp – usrreq.
2661 Cause: panic;m_get.
2662 Cause: panic; m_free.
2663 Cause: panic; m_copy.
2666 Cause: panic; sofree.
6.126.98.1.01.70 51
Statusmessages SW
2667 Cause: panic; soclose.
2668 Cause: panic; soaccept.
2669 Cause: panic; sorecv.
2673 Cause: panic; soisconnected.
2674 Cause: panic; sbappendrights.
2675 Cause: panic; sbflush.
2676 Cause: panic; sbflush.
2677 Cause: panic; sbdrop.
2678 Cause: panic; accept.
2679 Cause: panic; arp – no free entry.
2680 Cause: panic; synch mechanism.
3 2682 Cause: panic; synch mechanism.
2688 Cause: panic; gm_send.
2804 Cause: error during initialization of AEDP.
2815 Cause: not enough memory.
2819 Cause: parameters not permitted.
2856 Cause: no connection to external master.
2857 Cause: protocol layer not ready to send.
2858 Cause: protocol error during transmission.
2859 Cause: send job already active.
2860 Cause: no send job active.
2950 Cause: sector length of flash chips too large.
52 6.126.98.1.01.70
Satusmessages SW
2951 Cause: flash range too small for flash disk.
2952 Cause: error during writing of byte in flash memory.
2953 Cause: error during deletion of sector in flash memory.
2954 Cause: unknown flash module type.
2955 Cause: internal error in flash device driver.
2956 Cause: no dirty block in cache. Status message.
2957 Cause: job request invalid.
2958 Cause: disk block number invalid.
2959 Cause: function code invalid.
2960 Cause: DDHD_H.
3001 Cause: outside range.

ADC, weight value, display error.
3007 Cause: scale ID invalid.

3101 Cause: overflow, keyboard error.
3103 Cause: keyboard level invalid, keyboard error.
3104
3105
Cause: manager not initialized, keyboard error.
Cause: function error, keyboard error.

3
3106 Cause: fatal error, keyboard error.
3122 Cause: timeout error, keyboard error.
3150 Cause: general error, keyboard error.
3151 Cause: error in STATUS function.

Keyboard error.
Remedial action:
1.) Switch OFF/ON scale.
2.) Check plug connections to keyboard.
3.) Replace keyboard controller.
3152 Cause: error in INIT function.

3153 Cause: error in CTRL function.

3154 Cause: error in FLUSH function.

3155 Cause: error in component bus.

3156 Cause: keyboard queue full, keyboard error.
3157 Cause: tone ID not defined, keyboard error.
6.126.98.1.01.70 53
Statusmessages SW
3158 Cause: reinitialization, keyboard.
3301 Cause: coordinates outside range.

Layout manager error.
3303 Cause: input parameters invalid.



3312 Cause: resource ID invalid.

3331 Cause: maximum number of layouts or fields reached.



3350 Cause: general graphics error.

3351 Cause: polygon error.
3
3352 Cause: handle invalid.

3353 Cause: ID invalid.

3354 Cause: error in graphics memory.

Error in layout manager.
Unbuffered RAM full.
Remedial action:
1.) Evaluate RAM status.
3356 Cause: font error (graphics).
3380 Cause: general text error.

3380 Cause: font index detected.

3380 Cause: line feed detected.


3385 Cause: text too long.

54 6.126.98.1.01.70
Satusmessages SW
3386 Cause: font error.

3387 Cause: parsing error.

Layout manager error.
Remedial action:
1.) Check texts for undefined characters.
3401 Cause: receive buffer too small, printer error.
3404 Cause: init. not in order.

3405 Cause: function not existing.
3407 Cause: printer not mounted.

3422 Cause: printer task timeout.

3450 Cause: general printer manager error.

3451 Cause: printer timeout error, printer error.

Remedial action:
1.) Check plug connections to printer.
3452 Cause: no block request.

3
3453 Cause: job in ready queue.
3454 Cause: LRC error.
3455 Cause: error in conjunction with several repetitions.
3456 Cause: too many LRC errors.
3504 Cause: tone manager init. error.
3507 Cause: tone ID invalid.
3603 Cause: parameters invalid.

Error in POS drawer connection.

Remedial action: 1.) Switch scale OFF/ON.
3607 Cause: port ID invalid.

3650 Cause: general PIO error.

3701 Cause: time invalid.
3702 Cause: time invalid.
6.126.98.1.01.70 55
Statusmessages SW
3719 Cause: parameter incorrect, clock module.
3751 Cause: module defective.

Clock module error on CPU card.
Remedial action: 1.) Replace CPU card.
3752 Cause: data invalid.

Clock error on CPU card.
3753 Cause: resource not found.

3754 Cause: task not installed.

3755 Cause: internal time incorrect.

3756 Cause: wrong telegram received, clock module.
3757 Cause: maximum number of functions reached, clock module.
3801 Cause: too many menu levels.

Menu manager error.
3802 Cause: no menu available.


3 3804 Cause: initialization incorrect.


3810 Cause: menu handle incorrect.


3904 Cause: initialization incorrect.

3910 Cause: control handle incorrect.

3951 Cause:
3952 Cause:
4001 Cause: event overflow.

4003 Cause: data error.

56 6.126.98.1.01.70
Satusmessages SW

4101 Cause: editor manager full.

4103 Cause: transmission data incorrect.



4118 Cause: access not permitted.

4201 Cause: maximum number of layouts or fields reached, display error.
4203 Cause: data not in order.



4218 Cause: message not available.
3
4250 Cause: general layout error.

4251 Cause: cursor at string end.






4271 Cause: bus not ready.
4272 Cause: display not ready.
4273 Cause: task not ready.
4274 Cause: received telegram invalid.
6.126.98.1.01.70 57
Statusmessages SW
4275 Cause: error in transmission.
4276 Cause: error in receiving.
4277 Cause: transmission mode not existing.
4278 Cause: no device on component bus available.
4279 Cause: no more memory available.
4280 Cause: no semaphore received.
4281 Cause: display 1 not available.
4282 Cause: display 2 not available.
4283 Cause: no display available.
4284 Cause: additional display in system.
4285 Cause: no printer connected to system.
4286 Cause: printer reconnected to system.
4287 Cause: printing error.
4288 Cause: status function not available.
4404 Cause: database not created.

Database error.
3 Remedial action:
Carry out commissioning according to commissioning instructions applicable to the
relevant program version.

Database error.
Remedial action:
Carry out commissioning according to commissioning instructions applicable to the
relevant program version.
4406 Cause: fundamental error in database manager.

Database error.
Remedial action:
1.) Check master data for completeness and correctness.
Carry out data backup.
Recommission scale.
4451 Cause: error during file opening, database error.

4452 Cause: program version incorrect.
4455 Cause: attribute configuration incorrect.

Database error.
Configuration data transmitted by the PC incorrect.
Remedial action: 1.) Repeat transmission.
58 6.126.98.1.01.70
Satusmessages SW
4456 Cause: attribute not available.

4457 Cause: table already created.

4460 Cause: table not available.

Database error.
Remedial action:
on data transmission by PC
The master data transmitted was not activated during commissioning. Check
commissioning data.
With partitioning
An attempt was made to modify master data in a range which does not exist
in the partitioning list.
Check partitioning list for correct structure.
Also check partition allocated.
4461 Cause: attribute type incorrect.

4462 Cause: partition not existing.

Remedial action:
1.) Check set partitioning lists for completeness. If uncomplete, recommission unit.
2.) Ensure that the numbers used (PLU No., general text No., logo No., layout No.)
are within the partitioning range. Use correct number.
4466 Cause: record 1 < record 2.
4467 Cause: record 1 > record 2.

3
4468 Cause: record 1 == record 2.
4470 Cause: no extension configured.

Database error.
Remedial action:
PLU table full
1.) Check commissioning data for PLU table.
On data transmission by PC
1.) Non–extendable table full. Volume of data transmitted too large.
Print out table status. Check occupancy of table and commissioning data.
2.) Error in supertable:
Switch off all SCs except for that having a PC connection.
Activate menu point CONFIGURATION/RESTORE SYSTEM NETWORK.
Successively reactivate all SCs.
Repeat data transmission.
In the SC menu
1.) Error in supertable:
Switch off all SCs except for that having a PC connection.
Activate menu point CONFIGURATION/RESTORE SYSTEM NETWORK.
Successively reactivate all SCs.
6.126.98.1.01.70 59
Statusmessages SW
4471 Cause: key characteristics violated.

Database error.
Remedial action:
in the SC menu
1.) Call or clear non–existing master data.
On data transmission by PC
1.) Data error in data fields declared as keys.
Check data and retransmit them.
4472 Cause: string error.

4473 Cause: memory full.

Remedial action:
on data transmission by PC
1.) Storage capacity for index generation insufficient.
After commissioning of the SC, the buffered storage capacity must be at least
30 KB. Check buffered storage for available capacity.
Clear tables with VARSTRING fields on the PC (ATST, KFST and
LFST).
Recommission scale with smaller table sizes, so that enough buffered storage
capacity is available.
In the SC menu
See status No. 4451.
4474 Cause: telegram full.

3 4475 Cause: no (more) record available.

Database message.
Message that all data available has been output, e. g. in the case of a list printout.
4476 Cause: no such index available.

60 6.126.98.1.01.70
Satusmessages SW
4477 Cause: syntax error in selection formula.

4478 Cause: semantics error in selection formula.

4479 Cause: error during code generation.

4480 Cause: error during execution.

4481 Cause: index reference incorrectly set.

4482 Cause: index not yet/already created.

4483 Cause: record temporarily cancelled.
4484 Cause: balancing error in index tree.

Remedial action:
4485 Cause: no commit possible, database error.

Remedial action: 1.) Reprocess and store modified data.
4486 Cause: access mode in log file incorrect.

4487 Cause: no transaction possible.

3
4488 Cause: commit interrupted by power failure.
4489 Cause: pointer error in index tree.

4490 Cause: table not global, incorrect parameters.

4503 Cause: input parameter incorrect.

Error in one of the system databases.
Program statuses of scales differ from one another.
Remedial action:
All program statuses of scales used within a system must be identical.
4504 Cause: initialization error in vDbm.

Error in one of the system databases (network).
Remedial action:

4506 Cause: fatal error in vDbm.

6.126.98.1.01.70 61
Statusmessages SW
4522 Cause: timeout during receiving.

4551 Cause: record too long for telegram.

4552 Cause: remote station not responding.

Error in one of the system databases.
Remedial action:
when modifying global data
One or more scales connected to the system network are inactive.
2.) Activate menu point CONFIGURATION/RESTORE SYSTEM NETWORK.
3.) Check cabling.
4.) Check interfaces.
When copying configuration or commissioning data

1.) Ensure the scale address is correct.
When partitioning
A scale solely using partitions inactive (switched off, OFFLINE). Master data of this
partition has been changed.
1.) Switch on scale.
2.) Check cabling.
3.) Check interface.
System bus overloaded.
When transmitting data by the PC

1.) Switch on scale having PC connection.
2.) Check connecting cables and connections. Cables correct? Cables secured?
3 3.) Check channel number and baud rate.
3.) Replace EDP interface on SC.
4.) Interface card in PC correctly set, configured?
5.) Replace interface card in PC.
4553 Cause: no table information available.

Databases within system not identical.
Remedial action: 1.) Recommission scale with correct commissioning values.
4554 Cause: unknown attribute type.

4555 Cause: incorrect parameter.

4556 Cause: telegram incorrect.
4557 Cause: update ready.

4558 Cause: update started.

4559 Cause: error in update action function.

Disturbance in system bus.
Remedial action:
3.) Ensure the maximum total cable length is not exceeded.
62 6.126.98.1.01.70
Satusmessages SW
4560 Cause: no update required.

4561 Cause: no update required.

4562 Cause: internal error in update function.
4563 Cause: no update station available.
4570 Cause: station in OFFLINE state.

Entry in update function. Update is automatically restarted.
4580 Cause: error in supertable structure/log.

4590 Cause: non–global table.

Resource memory full.
4611 Cause: queue ID incorrect.

Error in data transmission on system bus.
Bus overload.
3
4613 Cause: task ID incorrect.
Bus overload.
4619 Cause: initialization parameters incorrect.

4650 Cause: connection cannot be cleared down.
4651 Cause: connection cleared down or defective.

Bus overload.
4652 Cause: telegram too long.

4653 Cause: telegram type wrong.

Remedial action: 1.) Check all scales connected to the network for being active.
6.126.98.1.01.70 63
Statusmessages SW
4653 Cause: telegram type wrong.
4654 Cause: operating means of receive station insufficient.

Remedial action:
4654 Cause: protocol type wrong.
4655 Cause: send station does not transmit telegram to def. LSAP
4655 Cause: queue full.
4656 Cause: software error in bus.

4656 Cause: system bus error, system bus overflow.

System bus operates incorrectly.
Remedial action:
If the error occurs frequently, e. g. more than 1000 times within 1 hour:
4657 Cause: receive station not acknowledging.

3 4657 Cause: component bus error.
4658 Cause: telegram not yet terminated.

4658 Cause: error in LSV1 protocol.
4659 Cause: LSAP full.

4659 Cause: error during acknowledging.
4660 Cause: protocol error.

4660 Cause: checksum in unpacking incorrect.
4661 Cause: telegram manager not initialized since system bus manager not initialized.
4662 Cause: priority for telegram task incorrect.

4662 Cause: send/receive cancelled.
4663 Cause: station list could not be determined.

Error in data transmission to system bus.
Remedial action:
1.) Switch OFF complete system.
Reactivate system units successively.
4663 Cause: timeout selected too short.
64 6.126.98.1.01.70
Satusmessages SW
4664 Cause: action task not started because of too many action tasks.
4664 Cause: LSAPs could not be created.
4665 Cause: no acknowledgement received after timeout.

4665 Cause: LSAP request/activation not possible.
4666 Cause: PROFIBUS in OFFLINE state.

4667 Cause: queues could not be created.
4668 Cause: queue request/activation not possible.
4669 Cause: station inactive.
4670 Cause: LSAP request in remote station not possible.
4671 Cause: TID management could not be initialized.
4672 Cause: action task ID incorrect.
4673 Cause: station list error.
4674 Cause: acknowledge error of level 2.
4675 Cause: scale number incorrect.
4676 Cause: HDLC protocol error. 3

4677 Cause: error in queue of remote station.
4678 Cause: timeout.
4679 Cause: not enough resources.
4680 Cause: resource not exisisting.
4681 Cause: station not responding.
4682 Cause: station not responding.
4683 Cause: local profibus error.
4684 Cause: SRD utility error.
4685 Cause: VRTX task could not be started.
4686 Cause: connection cleared down by watchdog.
4687 Cause: mutilated telegram eliminated.
4688 Cause: status not permitted.
4689 Cause: connection description incorrect. CTRL channel.
4690 Cause: Attention ! Send handle went lost.
6.126.98.1.01.70 65
Statusmessages SW
4691 Cause: telegram addressing incorrect.

Appears on recommissioning of system.
Remedial action:
1.) Check program versions. Use only identical program versions within a
system
4692 Appears only in conjunction with profibus PC card.
4693 Cause: repeated communication initializing after startup.
4694 Cause: communication software overloaded.

Too many procedures to be carried out simultaneously within the system.
Remedial action:
1.) Possibly too many function menus which are started at the same time.
Make PC call, make call in ’less busy’ times.
4695 Cause: status message.

Overloading of an individual SC. The unit is to process too many transactions at the
same time.
4697 Cause: local profibus error.
4701 Cause: code does not match square.

Error in bar code data.
Remedial action:
freely programmable label.
1.) Check setting of bar code height in menu point
CONFIGURATION / PRINTER / LABEL. The height set must be identical or less
(also selected on the creation of the bar code field on the CWS).
3 4703 Cause: data incorrect.


4707 Cause: code not available.

4750 Cause: general code error.

4751 Cause: check digit incorrect.


4802 Cause: underflow.

4850 Cause: general arithm. error.

Error in tool programs.
4851 Cause: less than.

66 6.126.98.1.01.70
Satusmessages SW
4852 Cause: greater than.

4853 Cause: equal to.

4854 Cause: comparison not in compliance.

4855 Cause: division by zero.

4901 Cause: character occupies more than 2 bytes.

4902 Cause: size smaller than source string.

4903 Cause: error in mem. functions.

4906 Cause: zero pointer.

4907 Cause: string data error.
4950 Cause: general string error.
4951 Cause: string format error.
3
4952 Cause: country resource absent.

5004 Cause: error in initialization.


5050 Cause: general utility error.

5051 Cause: less than.

5052 Cause: greater than.

5053 Cause: error in conversion.

5072 Cause: flash type unknown.
5073 Cause: programming voltage incorrect.
5074 Cause: block cancel error.
5075 Cause: flash block not cancelled.
6.126.98.1.01.70 67
Statusmessages SW
5076 Cause: command sequence incorrect.
5077 Cause: error during check.
5078 Cause: programming error.
5079 Cause: record length incorrect.
5080 Cause: record checksum incorrect.
5081 Cause: record marking incorrect.
5082 Cause: sequential address incorrect.
5083 Cause: buffer write error.
5085 Cause: command wrong.
5086 Cause: busy condition.
5087 Cause: TX interrupt.
5088 Cause: RS status error.
5089 Cause: marking incorrect.
5090 Cause: program size incorrect.
3 5091 Cause: program checksum incorrect.
5092 Cause: buffer full.
5305 Cause: action function not found.

Appears on evaluation of log.
Remedial action:
1.) Repeat log printout.
5319 Cause: error in action function.

5351 Cause: diagnosis active on this scale.
Two scales ask simultaneously for the log of one and the same scale.
Remedial action:
1.) Repeat log printout successively on each scale.
5352 Remedial action: all scale procedures processed. Internal message.
5353 Cause: station absent.
Remedial action:
1.) Check input of scale number. Use correct scale number.
68 6.126.98.1.01.70
Satusmessages SW

5354 Cause: profibus error.
Remedial action:
5355 Cause: internal message.

1.) Check scale from which the data was requested.
Switch scale OFF/ON.
5359 Cause: queue.


5361 Cause: mail box overflow.

5362 Cause: queue overflow.

Appears on evaluation of log. 3
5363 Cause: data length incorrect.
6.126.98.1.01.70 69
Statusmessages SW
5364 Cause: diagnosis type incorrect.

5365 Cause: manager type incorrect.

Remedial action: 1.) Ensure that program versions are compatible with one another.

5367 Cause: module already entered.
5370 Cause: BSL timeout active.
5451 Cause: freeTab error.
5452 Cause: aloc error.
5453 Cause: partFull error.
5454 Cause: backup error.
5455 Cause: no DatBer.
5460 Cause: no Tab error.
5461 Cause: tab error.
5462 Cause: request error.
3 5463 Cause: dba error.
5464 Cause: para error.
5465 Cause: noExt. error.
5475 Cause: noRec error.
5476 Cause: rec error.
5551 Cause: configuration data not found.
5552 Cause: no free space found in space list.
5562 Cause: request for free configuration range unsuccessful.
5601 Cause: receive overflow.
5659 Cause: error during sending.
5662 Cause: framing error.
70 6.126.98.1.01.70
Satusmessages SW
5666 Cause: length error.
5667 Cause: package error.
5668 Cause: system bus error.
5669 Cause: Uart occupied.
5715 Cause: no memory.
5950 Cause: general text eror.
5950 Cause: font index detected.
5950 Cause: line feed detected.

3
5957 Cause: parsing error.
5962 Cause: text not found.
6251 Cause: buffer overflow.
6252 Cause: message invalid.
6360 Cause: cancel of send squence from master.
6361 Cause: length incorrect or too short.
6362 Cause: semaphore timeout expired.
6363 Cause: automatic send unit stopped.
6364 Cause: memory not initialized.
6365 Cause: EC terminal transmits processing error.
6366 Cause: EC terminal processes transaction.
6367 Cause: EC terminal signals status information.
6.126.98.1.01.70 71
Statusmessages SW
6368 Cause: EC terminal signals cancel of transaction.
6451 Cause: no more free block memory.
6452 Cause: polling error.
6453 Cause: block unit not available.
6651 Cause: hardware Id invalid.
6652 Cause: error in mem. access.
6654 Cause: code invalid.
6656 Cause: module No. invalid.
6657 Cause: month invalid.
6658 Cause: year invalid.
6661 Cause: no counter for operating minutes.
6662 Cause: no random figure.
3 6663 Cause: cancellation error.
72 6.126.98.1.01.70
Satusmessages SW
1.4 Status numbers of application software SWCom, numbers 25000 – 25200
These messages are used for the transmission of data between the SC and the PC. They are entered in the
LOG files SWC_BAT.LOG and SWC_ERR.LOG on the PC.
SWC_BAT.LOG = records all procedures during data transmission.
SWC_ERR.LOG = records only the error states during data transmission.
The severity of errors is classified according to various levels, i. e. from level 0 to 5.
E_LEVEL: error stage

0 = no error
1 = warning (transmission may be continued)
2 = error at record level (transmission may be continued)
3 = error at file level (transmission of current file is cancelled)
4 = fatal error (cancelling of HDLC connection)
5 = fatal error [cancelling of DFÜ (remote data transmission) connection]
6 = fatal error (program cancel)
9 = error without context (no relation to current transmission)
An additional error text with a maximum of 231 characters may also be transmitted.
Error status (Q x,x = number) and error stage (L y,y = stage) are stored in the files SWC_BAT.LOG and
SWC_ERR.LOG on the PC.
The additional error text is only contained in the file SWC_ERR.LOG.

25004 Cause: initialization error. 3
25015 Cause: error in memory management.
25051 Cause: incorrect parameters.
25052 Cause: handle incorrect.

Remedial action:
2.) Check modem.
25053 Cause: no handle or high–priority job active.

25054 Cause: connection or high–priority job active.


– Pay attention to error entries in the SC log.
6.126.98.1.01.70 73
Statusmessages SW
25056 Cause:
waiting state. Remote station not ready to receive.
Remedial action:
see status No. 25052
or
1.) scale failure during data transmission.
2.) Interruption of cable or modem connection.
– Pay attention to error entries in SC log.
25057 Cause: cancel. Remote station not ready to receive.

Remedial action: see status No. 25052 or
1.) scale failure during data transmission.
2.) Interruption of cable or modem connection.
– Pay attention to error entries in SC log.
25058 Cause: cancel of HDLC connection by the user.

Remedial action: internal error. Contact your product manager.
25059 Cause: connection cannot be set up.
25060 Cause: CTS failure.

25061 Cause: cancellation because of HDLC protocol error.

25062 Cause: no connection active.

3 25063 Cause: no or incorrect ID from remote station.

25064 Cause: no or incorrect response to test frame.

25065 Cause: block check incorrect.

Remedial action: check setting of block protection method (LRC or CRC).
25066 Cause: receive queue for high–priority telegrams full or no more buffer available.
25068 Cause: general write error.

Remedial action:
1.) Brief line interruption.
2.) No more control signals.
25069 Cause: general read error.

25070 Cause: no control cables.

Remedial action:
3.) Check modem.
25071 Cause: time exceeded.

Remedial action:
3.) Check SC and modem.
74 6.126.98.1.01.70
Satusmessages SW
25072 Cause: modem: no response to AT commands.

Remedial action:
1.) Check connecting cable between modem and PC.
2.) Check modem. Configuration correct? Modem switched on?
3.) Replace modem or interface.
25073 Cause: remote station occupied.

Remedial action: check installation of remote station.
1.) Check modem. Configuration correct? Modem ready to call?
2.) Check telephone system. Parallel switched terminating equipment active?
25074 Cause: remote station does not respond.

Remedial action:
1.) Check telephone number used.
2.) Check dialing procedure. Multifrequency or pulse dialing procedure?
3.) Waiting time for connection message adequate?
Checking the installation of the remote station:

1.) Check modem. Configuration correct? Modem switched on?
2.) SC switched on?
3.) Check connecting cable between modem and SC.
4.) Check connecting cable between modem and telephone.
5.) Replace modem.
25075 Cause: modem: telephone number locked.

Remedial action:
2.) Switch modem OFF / ON.

From 3.07/4.0 onwards
Modem: no dialing tone. 3
Remedial action:
2.) Check connecting cable between modem and telephone line socket.
3.) Check telephone system.
25077 Cause: invalid character in ’W’ command.

Remedial action:
2.) Use permitted special characters (see modem manual).
25078 Cause: modem: general error.

25079 Cause: modem: speed incorrect.

Remedial action: 1.) Check modem. Configuration correct?
25080 Cause: no data.

Cause: modem: connection interrupted.

Remedial action: transmit information about omission of carrier signal.
25081 Cause: receiver not ready.

Remedial action: internal error.
Cause: no data available.

6.126.98.1.01.70 75
Statusmessages SW
25083 Cause: CTS not ready (applies to OS4680 only).

Remedial action:
25084 Cause: interface occupied (applies to UNIX only).

Remedial action:
2.) Wait for end of data transmission.
3.) Try again to carry out transmission.
25085 Cause: incorrect transmission frame is repeated.

Remedial action:
1.) Check cables. Pay attention to length. Any interfering influences?
2.) Bad modem connection.
3.) Check UART. Characters lost?
4.) Reduce transmission speed (baud rate).
25086 Cause: transmission error.

25087 Cause: transmission error (no STX character).

25088 Cause: initialization of interface incorrect (general).

Remedial action:
1.) Check the device name.
2.) Check access rights.
3.) Contact system administrator.
3 25089 Cause: initialization of interface incorrect (general).

25090 Cause: telegram too large.

Remedial action:
1.) Check package size.
2.) Adjust package size between device and SWCom.
25091 Cause: block counter incorrect.

Remedial action:
1.) Activate cyclic redundancy check (CRC).
2.) Sequence error of an incorrect HDLC dialog.
3.) Internal error. Contact your product manager.
25092 Cause: internal action handle incorrect.

25093 Cause: action identifier incorrect.

Remedial action: check program call, user and regulation files.
25094 Cause: sequential identification incorrect.

25095 Cause: file name incorrect.

25096 Cause: too many field identifiers.

25097 Cause: destination address incorrect.

76 6.126.98.1.01.70
Satusmessages SW
25098 Cause: error level incorrect.

25099 Cause: attribute type not permitted.

25100 Cause: all attributes deselected.
25101 Cause: current block length too large.
25102 Cause: VARSTRUCT not permitted.
25103 Cause: VARDATA length too large.

25104 Cause: not enough field identifiers.

25105 Cause: no useful data available.

Remedial action: check contents of SC file.
25110 Cause: record length incorrect.

Remedial action: check data editing.
25111 Cause: value outside MIN/MAX of DBMATT.

25112 Cause: value outside MIN/MAX of data filter.
25113
Cause: key attribute not identical.

3
Remedial action:
1.) Filter file incompatible with useful data file.
2.) Create new filter file.
25114 Cause: all values outside MIN/MAX of data filter.
Remedial action: check data editing.
25115 Cause: different key.
Remedial action: check key fields in filter file.
25116 Cause: all records outside MIN/MAX.
Remedial action: check MIN/MAX fields in filter file.
25117 Cause: error in INT64 conversion.
Remedial action: check values of all INT64 fields.
25120 Cause: file name absent.

25121 Cause: program invalid.

25122 Cause: ignore subsequent commands after error.

25123 Cause: parameter unknown.

25124 Cause: parameter absent.

6.126.98.1.01.70 77
Statusmessages SW
25125 Cause: parameter for incorrect file.

25126 Cause: parameter length incorrect.

25127 Cause: environment variable SWC_INIT not defined.

Remedial action:
1.) Define environment variable SWC_INIT.
2.) Create initialization directory.
25128 Cause: program cancel by user (CTRL–BREAK key).
25129 Cause: SC version incorrect.

Remedial action: program version SC < 2.XX is no longer supported.
25130 Cause: address type not ”S” or ”D”.

Remedial action: see error No. 25120.

25132 Cause: parameters incorrect.

25133 Cause: file cannot be opened.

Remedial action:
1.) Check program call, user and regulation files.
2.) Check system environment (access rights, free file handle).
3.) Disk capacity insufficient.
3 25134 Cause: error while writing in file.

25135 Cause: file error (name / channel / etc. ).

25136 Cause: log file SWC_BAT.LOG.

Remedial action: error during opening of above file.
25137 Cause: error file SWC_ERR.LOG.

Error during opening of above file.
25138 Cause: regulation file SWC_VOR.DAT.

25139 Cause: batch file SWC_BAT.BAT.

25140 Cause: user file name.ANW.

25141 Cause: password file SWC.PWD.

Error during opening of above file.
Remedial action:
25142 Cause: EOF regulation file SWC_VOR.DAT.

Remedial action: error during reading of above file.
78 6.126.98.1.01.70
Satusmessages SW
25143 Cause: error in regulation file SWC_VOR.DAT.

25144 Cause: EOL regulation file SWC_VOR.DAT.

25145 Cause: EOF user file name.ANW.

25146 Cause: error in user file name.ANW.

Remedial action: error during reading above file.
25147 Cause: EOL user file name.ANW.

25148 Cause: error in password file SWC.PWD.
25149 Cause: EOF useful data files.
25150 Cause: data received > data buffer.
25151 Cause: EOF parameter file.
Error during reading of above file.
Remedial action:
25152 Cause: version error in parameter file.
25153 Cause: error in initialization file SWCINIT.* 3

25157 Cause: EOF initialization file SWCINIT.*
25158 Cause: error in device file.
25159 Cause: EOF device file.
25160 Cause: EOL device file.
25161 Cause: error in useful data file.
25162 Cause: device file incomplete.
25163 Cause: device file created.


Remedial action: check system memory for available capacity.
25182 Cause: parameter not permitted.

25183 Cause: exit function has been called up.

25184 Cause: sending unsuccessful or no send data available.

6.126.98.1.01.70 79
Statusmessages SW
25185 Cause: receiving unsuccessful.

25186 Cause: handle incorrect.

25187 Cause: no data within timeouts.

25188 Cause: job cancelled.



25191 Cause: error during transmission.



25194 Cause: frame error.


3 Remedial action: internal error. Contact your product manager.


25198 Cause: length error.

25199 Cause: package error.

25210 Cause: LAN connection.

Socket error.
Remedial action: TCP/IP configuration error. Contact network administrator.

Host name unknown.
Remedial action: enter host name of SC or terminal server on HOST file.

Connection error. Connection to host not possible.
Remedial action:
1.) Switch on SC or host terminal server.
2.) SC or terminal server has no connection to network.
Diagnosis possible via command: ping <Hostname>
80 6.126.98.1.01.70
Satusmessages SW

25220 Cause: error in file editing.

Remedial action:
1.) Check SC file.
2.) Internal error.
6.126.98.1.01.70 81
Statusmessages SW
1.5 Status numbers of basic BOS software, numbers 40001 – 49999

40001 ADC 100:
Cause: write/read error during RAM check.
Remedial action: 1.) If error recurs, replace weighing system.
40002 ADC100:
Cause: checksum error in program code check.
40050 ADC 100:

Cause: checksum error during balancing/calibration data check.
40051 ADC 100:

Cause: test value error.
Remedial action:
1.) Recalibrate unit.
2.) Replace weighing system
40053 ADC 100:

Cause: division by 0.
40054 ADC 100:

Cause: program status incorrect.
Remedial action: 1.) Recalibrate unit.
40055 ADC 100:

3 Cause: error in activation table.
40056 ADC 100:

Cause: EEPROM checksum error in 1st block (recall).
EEPROM on ADC defective.
Remedial action: 1.) Replace weighing system
40057 ADC 100:

Cause: EEPROM checksum error in 2nd block (recall).
Remedial action: see status No. 40056
40058 ADC 100:

Cause: EEPROM checksum error in 3rd block (recall).
40059 ADC 100:

Cause: EEPROM checksum error in 4th block (recall).
40060 Cause: EEPROM checksum error in 1st block (transmission).

Remedial action:
1.) Check connecting cable between ADC 100 and backplane.
2.) Replace backplane.
3.) Replace weighing system
40061 ADC 100:

Cause: EEPROM checksum error in 2nd block (transmission).
82 6.126.98.1.01.70
Satusmessages SW
40062 ADC 100:

Cause: EEPROM checksum error in 3rd block (transmission).
40063 ADC 100:

Cause: EEPROM checksum error in 4th block (transmission).
40064 ADC 100:

Cause: command not permitted.
ADC program and CPU program incompatible.
Remedial action: 1.) Use compatible program versions.
40065 ADC 100:

Cause: identifier not permitted.
40066 ADC 100:

Cause: not in linear calibration mode.
Remedial action:
The ADC 100 may currently not be used in split design versions.
40067 ADC 100:

Cause: EEPROM cannot be programmed.
Remedial action: 1.) Replace weighing system.
40068 ADC 100:

Cause: cancel command in automatic calibration delayed.
Remedial action:
1.) Switch scale OFF/ON. Repeat calibration.
2.) If error recurs, replace weighing system.
3
40069 ADC 100:
Cause: disturbance in minibus or parity or wrong command.
40070 ADC 100:

Cause: no ADC interrupt.
40071 ADC 100:

Cause: EEPROM write–protected.
40072 ADC 100:

Cause: temperature sensor defective.
40073 ADC 100:

Cause: error in C–reference.
40074 ADC 100:

Cause: error in A–reference.
40075 ADC 100:

Cause: temperature sensor defective.
6.126.98.1.01.70 83
Statusmessages SW
40076 ADC 100:

Cause: error in B–reference.
40077 ADC 100:

Cause: odd number of characters. Internal message of ADC 100.
40078 ADC 100:

Cause: not a hexadecimal number. Internal message of ADC 100.
40079 ADC 100:

Cause: odd address. Internal message of ADC 100.
40080 ADC 100:

Cause: UART overrun. Internal message of ADC 100.
40081 ADC 100:

Cause: UART parity. Internal message of ADC 100.
40082 ADC 100:

Cause: UART frame. Internal message of ADC 100.
40083 ADC 100:

Cause: jumper wrong.
3 Remedial action:
1.) Check jumper settings on ADC 100 using the component plan.
40084 ADC 100:

Cause: array framing error. Internal message of ADC 100.
84 6.126.98.1.01.70
Satusmessages SW
1.6 Status numbers of SC application software
Status No. Cause/remedial action

50151 Cause: pressed key invalid.
A key was incorrectly operated during sales procedures.
50152 Cause: app–Magic invalid.

Remedial action: 1.) Reconfigure, recommission scale.
50153 Cause: LwKonfCmd (hold caused error)

Error on startup, system asks for reconfiguration.
Remedial action: 1.) Reconfigure, recommission scale.
50154 Cause: international not created.

Error in initialization of country option.
50155 Cause: error in creation of Vb–Task.

Software error.
Remedial action:
1.) Check EPROMS by means of checksum. Replace CPU program.
50156 Cause: error in BvBonSinit.

50157 Cause: error in AwTellInstall.

50158 Cause: error in DbTesti.

50159 Cause: load capacity code not permitted.

Remedial action: see text messages. 3
50160 Cause: corrupt ticket has been cancelled.
In continuous sales mode, ticket data was not completely copied to scale. After restart
of unit it is detected that ticket data is incomplete and the ticket is cancelled.
50161 Cause: ticket data incorrect.

Remedial action:
ticket memory full
1.) Check setting CANCEL TICKET in menu point CONFIGURATION/JOURNAL/
TICKET.
If {NO} is selected here, it should be ensured that the ticket memory is
evaluated and cleared at regular intervals. Otherwise the unit should be set to
{automatic}.
Evaluate ticket memory via REPORTS/JOURNAL/TICKET JOURNAL WITH
CLEARING.
Transmission error in continuous sales mode

2.) Check system interface.
50162 Cause: timeout during ticket call.

50163 Cause: general BDV error.

Remedial action: 1.) Switch SC OFF/ON.
6.126.98.1.01.70 85
Statusmessages SW
50164 Text message: print. of old tickets.

Log entries only.
1.) When switching the SC OFF/ON, open tickets are printed and successively
cancelled.
50165 Text message: repeat recording.

Cause:
appears in continuous sales mode after change of working place and first recording on
the scale.
Error in the transmission of ticket data from scale to scale.
Remedial action:
the last recording must be repeated.
If error recurs:
2.) Activate CONFIGURATION/RESTORE SYSTEM NETWORK.
3.) Check cabling.
50166 Text message: make up ticket! Articles from other dept. not permitted.
Cause:
appears if TERMIN. ON DEPT. CHANGE is set in menu points CONFIGURATION/ DE-
VICE SETTINGS/SALES MODES/DEPARTMENT SPANNINGS.
50167 Text message: EDP connection not existing.

Cause: appears when continuously calling tickets via the EDP.
Remedial action:
1.) Check connecting cable between SC and PC.
2.) Check PC connection.
50168 Text message: create new ticket

3 Remedial action: internal message.
50169 Text message: no general text under this number.

Cause: appears in SALES PROCEDURES when calling a general text by means of key
[CALL GEN. TEXT].
Remedial action:
1.) Check entered text number.
2.) Check input for text number used in menu point DATA MAINTENANCE /
TEXTS / GEN. TEXT.
50170 Text message: customer not created.

Remedial action:
1.) Create customer under the customer number used in menu point
DATA MAINTENANCE / CUSTOMER DATA.
50171 Text message: different ticket type.

Cause:
the sales modes ASSIST. SALE, DELIVERY NOTE, PURCHASE ORDERS, INVEN-
TORY, WASTAGE WEIGHING or RETURNS cannot be mixed within a ticket.
Remedial action:
terminate ticket with total [*] key and make up next ticket in the desired sales mode.
50172 Cause: error during the creation of GJ task.

Remedial action: internal status message.
86 6.126.98.1.01.70
Satusmessages SW
50177 Text message: not authorized to grant staff discount.

Remedial action:
check setting for markups/deductions and staff discount of the relevant vendor in menu
point DATA MAINTENANCE/VENDOR DATA.
50180 Text message:

ticket contains POS data – cannot be cancelled.
Cause:
appears in conjunction with the function [TICKET CANCEL] if a POS ticket already ter-
minated with the drawing of total [*] has been included in a further ticket.
Remedial action:
[TICKET CANCEL] is not possible here since the included ticket has already been ac-
counted.
50181 Text message: fidelity point overflow! Cancel item if necessary.

Cause: limit for fidelity points reached.
50182 Text message: function not executed. Ticket cancelled.
50184 Text message:

Cause: fixed tare value error.
50185 Text message:

Cause: error during cancellation of tare.
50251 Cause: Dpf magic number incorrect.

No more free RAM.
Remedial action:
For commissioning, a memory capacity of approximately 30 kB should be
available. This can be found out via ”STORAGE CALCULATION”. 3
50251 Cause: Dpf Init error.
50252 Cause: printer error.

Printer defective.
Remedial action: 1.) Replace printer.
50253 Cause: error when an attempt was made to effect a printout.

50254 Cause: menu op. dept. incorrect.

Control incorrect.
Remedial action:
50255 Cause: menu bar code incorrect.

Control incorrect.
Remedial action:
50256 Cause: control incorrect.

Remedial action:

Remedial action:

Remedial action:
6.126.98.1.01.70 87
Statusmessages SW

Remedial action:
50260 Cause: markup/deduction menu incorrect.

Control incorrect.
Remedial action:
50261 Cause: foreign currency value menu incorrect.

Control incorrect.
Remedial action:
50262 Cause: general manager error.

Fatal error.
Remedial action:
50263 Text message: no more record available.

Cause: appears during the creation of frequency data.
All 30 setting possibilities for hours and days are fully used.
50264 Remedial action: log entry only.
50265 Cause: fatal error in customer data.

Remedial action: log entry only.
50266 Text message: make up frequency reports with clearing.

Cause:
appears in DATA MAINTENANCE when changing the range settings for a frequency
report.
Remedial action:
1.) For the frequency report which is to be modified, sales figures are entered in
3 the reports. Settings can only be changed when the sales data of the
reports is cleared prior to the intended change or when the sales figures are
zero.
50267 Text message: table not created.

Appears in DATA MAINTENANCE.
Remedial action:
1.) Check commissioning values for data used.
See also BOS error 4460.
50351 Text message: error on initialization of assortment.

Cause: software error or storage management destroyed.
Remedial action:
the appearance of menu point NEW CONFIGURATION after switch OFF/ON of scale is
an indication of a destroyed storage management.
1.) Check battery voltage on CPU card.
50352 Text message: nutrition not initialized.

Special program for USA.
Remedial action:
nutrients have not been considered in COMMISSIONING.
1.) If nutrients are required, release PLU DATA in menu point MODIFY
COMMISSION. DATA.
START COMMISSIONING.
50353 Cause: special offer PLU not available.
88 6.126.98.1.01.70
Satusmessages SW
50451 Text message: data of report menu inconsistent.

Cause:
appears after selection of menu point SCALE REPORTS. Ranges and sortings for the
reports are incorrectly set.
1.) Reselect REPORT menu. Incorrect settings are automatically
brought to standard settings. Repeat procedure until error message
disappears. Redefine REPORT settings.
Check battery.
If error recurs:
2.) Replace CPU card. Appears during evaluation of report.
50551 Text message: configuration data invalid.

Cause:
appears when interconnecting scales of current program statuses and programs older
than 2.03.
Remedial action:
1.) Use only scales with an identical program status within a system.
50552 Cause: identifier incorrect.

50553 Remedial action: internal status message.
50553 Cause: command invalid.

50554 Text message: commissioning data does not agree with system.
Cause:
scales within the system must contain logical commissioning data. 3
Remedial action:
Copy them from a suitable scale or modify them.
50555 Text message: scale not commissioned on system.

Cause:
appears when adding a scale to a system currently in operation.
The database structure is compatible with that of the active system, the scale is, howe-
ver, not entered in the supertable of the system in operation.
Remedial action:
1.) Acknowledge enquiry by entering YES.
This causes the scale to be entered in the supertable of the active system.
Entering NO causes the unit to be recommissioned.
6.126.98.1.01.70 89
Statusmessages SW

50556 Text message: partitioning list incorrect! Please correct!
Cause:
appears when creating a partitioning list in COMMISSIONING for
– PLU DATA
– GENERAL TEXTS
– LOGOS
– LABELS
Remedial action:
1.) Within the partitioning list, values should not overlap.
50557 Text message: created partition(s) incorrect. Please correct !
Cause:
the partitions must be created only once and in ascending order.
Appears in COMMISSIONING.
Remedial action:
1.) The sequence of the partition numbers in menu point
CREATE PARTITIONS must be in ascending order.
partition 1 6 4
partition 2 5 5
partition 3 4 6
50558 Text message: number exceeds range! Please correct!
Cause:
appears in COMMISSIONING when creating a partitioning list for
– GENERAL TEXTS
– LABELS
3
Remedial action:
1.) Ensure that the values entered under NUMBER do not exceed those entered via
the range.
E. g.: incorrect range: 100 – 500 number: 500
50559 Text message: enter at least one partition !
Cause:
appears in COMMISSIONING when creating a partitioning list for
– PLU DATA
– GENERAL TEXTS
– LOGOS
Remedial action:
1.) A partition starts with 0. Correct setting.
50560 Text message: storage management destroyed! Recommission scale!
Appears on START COMMISSIONING.
Remedial action:
1.) Acknowledge message with YES.
50561 Text message: check input data.
50562 Text message: double address in system!

Appears on activation of an additional scale.
Remedial action:
1.) Check station addresses of scales in menu point
CONFIGURATION/SYSTEM
Each address should not exist more than once in a system.
50563 Text message: database different from program version.
50564 Text message: program version contains no Ethernet driver.
90 6.126.98.1.01.70
Satusmessages SW
50565 Text message: commissioning data different from database.
50566 Text message: configuration data different from database.
50567 Text message: EDP protocol changed! Device being restarted!

Cause:
appears when loading KFLO with a modified protocol
and after reloading of data backup with SWDasi. The SC is automatically restarted and
initialized with the new parameters for the EDP interface.
50568 Text message: no unit commissioned in system.

Cause:
device in OFFLINE state.
COPY COMMISSIONING DATA or COPY CONFIGURATION DATA is carried out di-
rectly after RAM clearing.
Remedial action:
1.) Switch OFF/ON SC on which the copy function was carried out.
50568 Text message: device in offline!

Cause:
appears when copying COMMISSIONING or CONFIGURATION data from SC to SC.
Remedial action:
1.) Switch scale OFF and back ON.
50569 Text message:

please load configuration and commissioning data via EDP and
continue with <ENTER> key.
Cause: EDP commissioning is carried out.
50569 Text message: EDP interface active. Load configuration tables now.
Appears after recommissioning.
Remedial action:
3
1.) The data for COMMISSIONING and CONFIGURATION may now be loaded
via the SWDasi program.
50570 Cause: general internal configuration error.

Configuration data destroyed.
Remedial action:
1.) Check battery on CPU card.
50571 Cause: configuration identifiers not clear.

50572 Text message: checksum error of configuration.

Cause: configuration data destroyed.
Remedial action:
error in copying configuration data from one scale to another.
1.) Repeat copying procedure.
Commissioning data was loaded into scale with SW_DASI, but commissioning
data was neither copied to the own station address nor was commissioning star-
ted afterwards.
50573 Cause: table from g_database unknown.

50574 Cause: database not existing.

6.126.98.1.01.70 91
Statusmessages SW
50575 Text message: not enough memory. Database cannot be created.

Cause: appears on activation of START COMMISSIONING. Storage capacity does not
suffice to create the database.
Remedial action:
1.) Reduce commissioning values
If data cannot be reduced, partition the same or install RAM expansion.
50576 Text message: entered scale number not existing.

Cause: appears when copying configuration settings.
Remedial action:
1.) Entered scale number incorrect. Correct it.
2.) Entered scale switched off. Switch on.
3.) Check connecting cables, sockets, T–pieces and interfaces.
50577 Text message:

remove paper from printer 1, close print bar and continue with [Enter] key.
Cause:
menu point LEARN MODE FOR END OF PAPER has been selected.
This learn mode is automatically carried out after each RAM clearing.
Remedial action:
before acknowledging with the [ENTER] key, it is absolutely necessary to remove the
ticket paper or labels from the paper chute, otherwise the message END OF PAPER is
continuously output because the threshold value for the light barrier is not correctly
recognized.
50577 Text message: remove paper from printer, close print bar and continue with [Enter].
Cause:
appears when menu point LEARN MODE FOR END OF PAPER is executed.
50578 Text message: learn mode terminated! Reinsert paper!

3 Appears when menu point LEARN MODE FOR END OF PAPER is executed.
50579 Text message: commissioning data loaded could not be tansferred!

Remedial action:
1.) Reload COMMISSIONING data via SWDasi.
Adopt new COMMISSIONING values.
50580 Text message: configuration data loaded could not be tansferred!

Remedial action:
1.) Reload CONFIGURATION data via SWDasi.
Adopt new CONFIGURATION values.
50581 Text message: loaded data adapted to range of values!

Cause:
appears after loading of data backup of an ’older’ program status into a current version.
If values have been taken out of the current program version in the commissioning or
configuration data, the loaded data of the data backup will automatically be adjusted to
the values of the current program version.
50582 Text message: modify data if necessary and start commissioning!

Cause: EDP commissioning is carried out.
50582 Text message:

data has been loaded ! Modify data if necessary and start commissioning!
Cause: appears after loading of data backup.
50584 Text message: number of nutrients should not exceed number of PLUs!
Cause: appears in COMMISSIONING. Special program for USA.
92 6.126.98.1.01.70
Satusmessages SW
50585 Cause: status EDP commissioning of configuration tables.

50586 Text message: no data received.

Cause:
EDP commissioning is carried out. The SC has not received new commissioning or
configuration data after loading.
Remedial action:
1.) Check the station address.
Check whether or not commissioning and configuration data is stored in the
customer directory of SWDasi under the station address selected.
2.) If no commissioning and configuration data is stored for the SC,
do not commission the SC with the EDP commissioning data,
but clear the RAM and subsequently copy it from another SC connected to
the system.
50587 Text message: configuration being processed.

Cause:
appears during loading of configuration data with SWDasi.
At the time of loading, an attempt was made to call up the menu point CONFIGURA-
TION or the data transmission is started while the scale is at the menu point
CONFIGURATION.
50588 Text message:

remove paper from printer 2, close print bar and continue with [Enter] key.
Cause:
menu point LEARN MODE FOR END OF PAPER has been selected.
Remedial action:
Before acknowledging with the [ENTER] key, it is absolutely necessary to remove the
ticket paper or labels from the paper chute, otherwise the message END OF PAPER is
continuously output because the threshold value for the light barrier is not correctly re- 3
cognized.
50589 Text message:

POS sales are available. Draw up POS report with clearing.
Cause:
appears during modification of the station address in the menu point CONFIGURATION
/ SYSTEM.
Remedial action:
POS sales are data stored specifically for the relevant device. The SC does not permit
the station address to be modified as long as this data is stored. POS reports are to be
evaluated ”with clear”. The station address may be changed afterwards.
50590 Text message: electronic cash not contained in program code.

Cause: module not linked. BOS error message.
6.126.98.1.01.70 93
Statusmessages SW
50591 Cause: commissioning data cannot be loaded.

Remedial action:
commissioning values can only be loaded immediately after RAM clearing via SWDasi.
If the database has already been set up via the menu point START COMMISSIONING,
the commissioning values will be rejected.
For new installations, use the menu point EDP COMMISSIONING if possible.
50651 Text message: plug calibration jumper.

Cause: appears in the SERVICE menu when selecting CALIBRATION or LINEAR
CALIBRATION.
Remedial action:
1.) When selecting the above menu points, ensure that the jumper SB201
on the ADC 90 is closed.
50652 Text message: no stabilization on linear calibration.

Appears during linear calibration of an external load cell.
Remedial action:
1.) Select place of installation which is free of vibrations.
If error recurs:
2.) Replace ADC 90.
3.) Replace load cell.
50654 Text message: ADC error.

Cause: appears when selecting the menu point CALIBRATION.
Remedial action:
1.) No ADC connected (SC 100 K, SC 800 K).
2.) Check connecting cable between ADC and CPU card.
3.) Ensure that calibration jumper SB 201 is plugged.
4.) Check jumpers on ADC.
3 6.) Replace CPU card.
50655 Cause: archive error.

50656 Text message: scale management error.

Appears during calibration.
Remedial action: 1.) Ensure correct zero load.
50657 Text message: switch off scale and remove calibration jumper.
Appears after termination of calibration procedure.
50658 Text message: function no longer possible during this month.

Cause: appears when the HDLC service interface is in use. The HDLC service inter-
face offers not more than 5 connections per month. This limit has been reached.
Remedial action: advance the month in the menu point DATE / TIME. 5 connections
then again become available. Set the month back to the valid month after termination of
transmission. 5 connections are then offered again.
94 6.126.98.1.01.70
Satusmessages SW
50751 Cause: error in accounting task on call of total without amount tendered/change op.
Remedial action:
the SC operates only with drawer connection if the unit is set to ”without amount
tendered/change operation”.
1.) Connect drawer or change configuration.
Error in foreign currency conversion and accounting of sales.

Database error.
50752 Cause: error in POS drawer accessing.

Drawer does not open. Reread contact not recognized.
Remedial action:
1.) Check reread contact on drawer.
3.) Check drawer interface.
4.) Replace drawer.
50753 Cause: error in accounting task on call of total or amount tendered.

50754 Cause: database table not found in foreign currencies, markups/deductions.

Remedial action:
50755 Cause: attribute type incorrect in foreign currencies, markups/deductions.

Error during database call.
Remedial action if error recurs:
50756 Cause: internal database error (foreign currencies, markups/deductions).

Remedial action: see status No. 50755. 3
50757 Text message: double initialization for total sales calculation.
Cause: appears on evaluation of POS and cashiers’ reports.
Remedial action:
1.) Switch OFF/ON scale. Thereafter, the system might ask for a reconfiguration.
50758 Cause: overflow on total forming.

The total sales accounting for POS or cashiers’ reports resulted in an overflow. There is
no need to react to it.
50759 Cause: checksum of POS report incorrect.

Remedial action:
1.) Switch OFF/ON scale. Thereafter, the system might ask for a reconfiguration.
50760 Text message: vendor not allowed as a cashier.

Cause: appears in POS mode or in OTHER FUNCTIONS/POS.
Remedial action:
1.) Check the values set for the relevant vendor in
DATA MAINTENANCE/VENDOR DATA.
2.) Check keyboard programming
CONFIGURATION/CREATE KEYS
DATA MAINTENANCE/VENDOR DATA/VENDOR KEY.
6.126.98.1.01.70 95
Statusmessages SW
50761 Text message: POS drawer 1 not connected.

Remedial action:
1.) Check the values set of the relevant vendor in DATA
MAINTENANCE/VENDOR DATA.
3.) Check connecting cable between backplane and POS
drawer interface.
4.) Check fuse on POS drawer interface.
5.) Replace POS drawer interface.
6.) Replace POS drawer.
50762 Text message: POS drawer 2 not connected.

50763 Cause: error in database accessing.
50764 Text message: foreign currency selected not created.

Remedial action:
1.) Check values for foreign currency used in DATA
MAINTENANCE/FOREIGN CURRENCIES.
2.) Check keyboard programming.
DATA MAINTENANCE/FOREIGN CURRENCIES/FOREIGN
CURRENCY KEY.
50765 Text message: foreign currency table not created.

Remedial action:
Enter relevant value in COMMISSIONING/OTHERS/
3 FOREIGN CURRENCIES.
50766 Text message: vendor selected not created.

Appears in sales procedures LOG ON/OFF VENDOR
Remedial action:
1.) Check values for relevant vendor in DATA MAINTENANCE/VENDOR DATA.
2.) Check keyboard programming.
DATA MAINTENANCE / VENDOR DATA / VENDOR KEY.
50767 Text message: vendor table not created.

Remedial action:
50768 Cause: table element not created.

Remedial action: check the commissioning values. Recommission scale if necessary.
50769 Cause: database table not created.

Remedial action: check the commissioning values. Recommission scale if necessary.
50770 Text message: no authorization for this department.

Appears on log on/off of vendors.
Remedial action:
1.) Check settings of department No. for the vendor used in
96 6.126.98.1.01.70
Satusmessages SW
50771 Text message: password incorrect.

Appears on vendor log on/off.
Remedial action:
1.) The password used is incorrect. Enter correct password again.
The password may be read off in DATA MAINTENANCE/
VENDOR DATA under the relevant vendor number.
It does not appear on the printout of the vendor list.
50772 Text message: ticket of cancelled vendor still in system.

Appears in sales procedures on log on/off of vendors.
Cause:
an open ticket pertaining to a vendor already cancelled in DATA MAINTENANCE is still
in the system with the consequence that the key assigned to the cancelled vendor will
not be released for a new vendor.
Remedial action:
1.) Create cancelled vendor again, terminate open ticket with total [ * ] key and
cancel vendor if required.
50773 Text message: key occupied by vendor with open ticket.

Appears in sales procedures log on/off of vendors.
50774 Text message: drawer does not open in training mode.

Remedial action:
1.) The vendor selected is set to TRAINING in
The opening of drawer may also be released in training mode via menu point
CONFIGURATION/POS.
50775 Text message: weighing not possible.

Cause: appears in POS mode when an attempt is made to count the cash in POS BA-
LANCE I. H. via COUNT. HELP BY WEIGHING.
The connected weighing system should use a scale interval of at least 2g. 3
50776 Text message: scale not suitable for counting.
50777 Text message: open ticket still in system.

Cause: appears on log–off of a vendor who has still an open ticket in the system.
Remedial action:
1.) Terminate ticket with [total] or [partial ticket].
Thereafter, the vendor can log off.
50778 Cause: error in foreign currency conversion.
50779 Text message: cheque limit exceeded.

Cause: cheque amount too high.
Remedial action:
1.) Check settings for the cheque limit in menu point CONFIGURATION/DEVICE
SETTINGS/SALES LIMITS.
50780 Text message: credit card limit exceeded.

Cause: credit card amount too high.
Remedial action:
1.) Check settings for the credit card limit in menu point
CONFIGURATION/DEVICE SETTINGS/SALES LIMITS.
50781 Text message: limit.

The limit of the cheque and credit card is indicated here.
Remedial action:
the limits may be set in the menu point CONFIGURATION / DEVICE SETTINGS /
LIMITS.
6.126.98.1.01.70 97
Statusmessages SW
50781 Text message: limit.
50782 Text message: please close POS drawer.

Cause: appears in amount tendered/change operation if the next customer is to be ser-
ved by means of key [ESC], with the drawer open and DRAWER COMPULSORY set.
Remedial action:
1.) Check menu point CONFIGURATION/POS/
RECORD. W. DRAWER OPEN.
2.) Check reread contacts of drawer.
50783 Text message: not permitted.

Cause: disallowed attempts to serve customers in AMOUNT
TENDERED/CHANGE OPERATION.
Remedial action:
1.) The [cheque], [credit card], [voucher] keys cannot be
activated immediately after a foreign currency conversion.
2.) Granting a total discount on a negative sum is not possible.
3.) Granting a total discount if the sum is equal to zero is not possible.
50784 Text message: vendor on scale occupied.
50785 Text message: vendor number invalid.
50786 Text message: ticket made up.
50787 Text message: no ticket data available.

Cause:
appears in sales procedures when entering the ticket No. via the key [input of ticket
No.].
Remedial action:
3 1.) Check entered ticket number for correctness. Enter the same again.
2.) Ticket copy is no longer existing in ticket/journal memory.
Check size of ticket/journal memory in COMMISSIONING.
Check settings for ticket/journal memory in
CONFIGURATION.
50788 Cause: system error.

Severe error in accounting task in AMOUNT TENDERED/CHANGE OPERATION.
Error in currency conversion.
General database error.
50789 Text message: no exchange rate entered.

Appears in sales procedures or POS mode.
Remedial action:
1.) Check values for foreign currency used in DATA
MAINTENANCE/FOREIGN CURRENCIES.
98 6.126.98.1.01.70
Satusmessages SW

50790 Text message: you have pressed wrong foreign currency key.
Remedial action:
1.) The amount to be paid has been converted into a foreign
currency and the amount tendered is to be reconverted into
another foreign currency. This is not permitted.
50791 Text message: no markups/deductions created under this number.
Appears in sales procedures or in POS mode.
Remedial action:
1.) Check values set for the markup/deduction used in DATA
MAINTENANCE/MARKUPS/DEDUCTIONS.
2.) Check keyboard programming
CONFIGURATION/CREATE KEYS
DATA MAINTENANCE/MARKUPS/DEDUCTIONS/
MARKUP/DEDUCTION KEY.
50792 Text message: no total markup/deduction.
Cause:
in the amount tendered menu, only the total markup/deduction key is accepted. The
above message will be output as soon as other markup/deduction keys are used.
50793 Text message: log on cashier.
Appears when operating with log on/off of vendors.
Remedial action:
1.) At the time a vendor logs on, he must already be created as a cashier in
DATA MAINTENANCE/VENDOR DATA
50794 Text message: ticket sorting to dept. and
am. tend./change op. n. permitted
Remedial action:
1.) The two settings CONFIGURATION / DEVICE SETTINGS / 3
OPERATING MODES / TICKET SORTING TO DEPT. YES and
CONFIGURATION / POS / AMOUNT TEND./CHANGE OP. YES
cannot simultaneously be activated.
50796 Text message: connected POS drawer not configured.
Remedial action: set unit to DRAWER CONNECTED YES in the menu point CONFI-
GURATION/POS.
50797 Cause: error during setting of automatic customer No. Retry!
50798 Text message: cashier has not determined POS balance i. h.

Cause: appears in POS reports.
Remedial action:
1.) {POS balance i. h.} is set under menu point
POS in the CONFIGURATION.
If this menu point is not activated prior to a printout of the
cashier’s reports, a printout will not be made.
Before reports can be printed out each cashier must have
acquired the POS balance.
50799 Text message: POS.

Cause: appears in POS mode if the limit set for the money stock of the POS drawer is
achieved. This message indicates that an uplift must be made.
Remedial action:
1.) Make the uplift via the menu point OTHER FUNCTIONS /
POS / UPLIFT
2.) Check settings in menu point CONFIGURATION / DEVICE SETTINGS /
SALES LIMITS / LIM. MONEY STOCK.
6.126.98.1.01.70 99
Statusmessages SW
50800 Cause: error in AwZDGet.

Appears on printout of POS and cashier’s reports.
Database error in R–counter.
50801 Cause: cashier trains in AMOUNT TENDERED/CHANGE OPERATION.

Remedial action: make entry in log for checking purposes.
50853 Text message: price group wrong.
50854 Text message: E–Cash terminal not ready. Cancel !

Appears during log–on of the EC terminal, use of the disbursement types EC–SECU-
RED PAYMENT, DEBIT NOTE – ONLINE and DEBIT NOTE – OFFLINE or CANCEL
E–CASH.
Remedial action:
1.) Check the connecting cable between SC and EC terminal.
2.) Check the entered dealer password for correctness in the menu point
CONFIGURATION / SERIAL INTERFACE / {E–CASH}.
3.) Check the dealer password which might be necessary for being correctly entered.
50855 Cause:
initialization of E–Cash unsuccessful.
Appears on automatic log–on of EC terminal.
The SC automatically logs on the EC terminal during switch–on.
50856 Text message:

electronic cash – cancel because of error, payment has not been effected.
Cause: the EC terminal was not able to carry out the payment.
Remedial action:
3 1.) Check the EC terminal for correct functioning.

2.) Repeat the payment transaction.
50857 Text message:

transaction unsuccessful despite of repetition. Cancel !
Cause: the EC terminal was not able to carry out the payment.
50882 Cause: no more memory available.
50883 Cause: no record available.
50884 Cause: file not available.
50885 Cause: file cannot be created or creation of file not permitted.
50886 Cause: modification of date was not permitted.
50951 Text message: no module licence available.
50952 Cause: module No. not available.
50953 Text message: too many incor. entries.

Remedial action:
switch device off/on.
100 6.126.98.1.01.70
Satusmessages SW
50954 Text message: error in accessing hardware ID.

Appears during the activation of licence modules.
Cause:
the ID module on the CPU card is defective or absent.
Remedial action:
1.) Plug ID module on the CPU card or replace it.
50955 Text message: no demo/test licence available which can be activated.
51051 Cause: appears during the creation of accounting regulations. There is no memory for
VAST accounting records.
51052 Appears during the creation of accounting regulations.

Cause:
there is no memory for VAST master records.
51090 Cause: ticket not entered, no suitable VA record found.
51094 Cause: type of payment and foreign currency conflicting, disbursement type not
entered.
Remedial action:
1.) Check the number of foreign currencies set on each scale in the menu point
COMMISSIONING. The number set must be identical on all SCs.
51095 Cause:
type of payment and foreign currency conflicting, disbursement type not
entered.
51096 Cause: action task cancel incorrect – TastTDelete error.
51097 Cause: ticket has no reference, has been cancelled.

3
51098 Cause: BVBT reference to BOKA invalid, has been cancelled.
51099 Cause: ticket item could not be booked.

Item could not be entered in sales table.
Remedial action: repeat recording procedure.
51147 Cause: semaphore received, but evaluation active in system.

Table inactive.
Remedial action:
1.) Modify commissioning data and restart unit.
51151 Cause: report not initialized.
51152 Cause: initialization still active.
6.126.98.1.01.70 101
Statusmessages SW
51153 Text message: report being established by other scale.

Appears on printout of report.
Remedial action:
an identical report printout has been started on another scale.
1.) Wait for the SC to terminate its evaluation and restart
printout.
An identical report printout has been started via EDP.

1.) Wait for EDP to terminate its evaluation and restart printout.
51154 Cause: stop/exit function still active.
51155 Cause: function not permitted here.
51156 Text message: report type unknown.

Appears on sales call via EDP.
Remedial action:
1.) Report for unknown sales table requested.
Correct selection parameter in parameter file.
51157 Text message: selection range invalid.

Remedial action:
1.) Invalid range entered in selection parameters.
Correct selection ranges.
Restart call.
51158 Cause: clearing still active.
51159 Cause: function not yet terminated, still active.

3 Appears on sales call via EDP.
Remedial action:
1.) Scale network has not enough time to process an EDP job.
Increase timeout period (with N TIME).
Restart call.
51160 Cause: data not yet available.

51161 Cause: no more data available.

Appears when calling up sales via EDP.
Remedial action:
1.) Indication of a sales call which has been made.
No error.
51162 Cause: no more data available/scale error.

Remedial action:
1.) During a sales call it was detected that at least one SC failed from which not
all sales data was called up.
Switch on all scales.
Restart call to get the remaining sales data.
Ignore error.
51163 Cause: clearing not permitted.
102 6.126.98.1.01.70
Satusmessages SW
51164 Text message: table not configured.

Appears when selecting the menu point FREQUENCY REPORT.
Remedial action:
1.) Check commissioning values for frequency reports.
Appears when calling up sales via the EDP.

Remedial action:
1.) A report with sales period 0 is not allowed to be created
in COMMISSIONING. All reports must be released.
Activate MODIFY COMMISSION. DATA and restart.
51165 Text message: sales period not configured.

Remedial action:
1.) Check report accounting regulations for correctness.
51169 Cause: requested scale(s) inactive.

Remedial action:
1.) If an SC is addressed which is not in the system or switched off.
Switch on all SCs.
Correct selection parameters.
Restart evaluation.
51170 Cause: system error, no control block for semaphore.
51171 Cause: fatal error in evaluation task.
51172 Cause: telegram not sent to scale. General error.
51173 Text message: evaluation active at other station.

Cause: 3
an identical report is evaluated on several SC scales at the same time.
Remedial action:
first wait for the evaluation to be terminated and then start evaluations.
51173 Cause: semaphore occupied by other application.

Appears when reports are simultaneously printed out on several SCs.

Remedial action:
1.) A sales report is currently established on an SC.
Wait until the report is terminated.
Restart call.
51174 Cause: EDP asks for report.

51175 Cause: sales totals not restorable.

Remedial action:
1.) After a sales call cancellation (with sales clearing) a non–transmitted sales data
block could not be reentered into the sales table.
51176 Cause: counter readings differ from one another.

One SC was not in the system during evaluation via the EDP. Thus, the R–counter and
report counter differ from those of the remaining SC scales connected to the
system.
51177 Cause: general put routine from task 54.
6.126.98.1.01.70 103
Statusmessages SW
51178 Cause: error from task 54 on external scale.
51179 Cause: error from action task in evaluating scale.
51181 Cause: action task Init/exit + responses.
51182 Cause: response telegram read was incorrect.
51183 Cause: action task selection.
51184 Cause: action task sales transmission.
51186 Cause: action task sales received.
51187 Cause: action task PLU R/P sales selection.
51188 Text message: no telegram received after timeout.

Appears during evaluation of reports.
Remedial action:
1.) Restart evaluation.
2.) Switch complete system OFF/ON.
51188 Cause: telegram received after timeout.
51189 Cause: telegram arrived too late.
51190 Cause: sales report called up.
51191 Cause: sales report terminated.

3 51192 Cause: scale number of telegram incorrect.
51194 Cause: own station ready, inactive in ring system.
51195 Cause: remote station in offline state.
51196 Cause: remote station ready, inactive in ring system.
51197 Cause: station address invalid.
51198 Cause:
sales table unknown.
Appears during evaluation of reports.
On one or more SCs the NUMBER OF SALES PERIODS has been set to {0} under
REPORT during commissioning.
Remedial action:
1.) Set correct commissioning values. Recommission unit.
51199 Cause: report type not yet defined.
51551 Cause: call disabled.
51251 Text message: no function for table.
104 6.126.98.1.01.70
Satusmessages SW
51252 Text message: data length in telegram incorrect.

Cause:
Remedial action:
51253 Text message: sales loss by commit error.

Cause:
Remedial action:
51254 Text message: possibly double sales with commit error.

Cause:
Remedial action:
51255 Text message: sales clearing by change of VAST.

Cause:
Remedial action:
51256 Text message: test and clearing of sales holding times terminated.
Cause:
Remedial action:
51300 Text message: general table identifier.

Cause:
Remedial action:
51552 Cause: EDP call active.

Appears on activation of report on a scale while a report is already active via the EDP.
Remedial action:
1.) Wait until report is terminated on the EDP and successively restart evaluation
on SC.
51553 Cause: call not initialized.

3
51554 Cause: initialization task signals error.
51556 Cause: No more data available. Scale error.

1.) An SC scale was switched off during the time a report was active.
2.) Bus malfunction.
51558 Cause: ticket not processed, transmit error record.
51559 Cause: ticket incomplete, transmit error record.
51560 Cause: counter readings differ from one another.
51561 Cause: journal ticket called up.
51562 Cause: journal call terminated.
51563 Cause: ticket recorded for forced cancellation.
51564 Cause: forced cancellation not possible.
51565 Cause: ticket cannot be cancelled.
51566 Cause: internal error from JbHoVeTicket.
6.126.98.1.01.70 105
Statusmessages SW
51567 Cause: forced cancellation of non–called up tickets from EDP journal range.
51568 Cause: forced cancellation of non–called up tickets from ABV journal range.
51569 Cause: ticket status invalid.
51570 Cause: no ticket from assisted sales mode.
51571 Cause: already cancelled or cancel ticket.
51572 Cause: reduced by relevant items.
51573 Cause: ticket included.
51574 Cause: ticket contains no items.
51575 Cause: error in ticket accessing.
51576 Cause: error in processing of original ticket.
51577 Cause: not enough ticket memory.
51578 Cause: no more free ticket number available.
51579 Cause: DBM error during cancellation.
51580 Cause:
master journal synchronization active, no call possible.
Appears in systems using ”COMPLETE JOURNAL” in backup operation.
Remedial action:
3 a higher–order system cannot request data at this time. Wait for the synchronization to
be completed and retransmit the request.
51581 Cause:
master journal changeover from backup scale to master scale requested.
51582 Cause:
master journal changeover to master scale requested.
51583 Cause:
master journal changeover not carried out.
51584 Cause:
master journal call changed to normal call.
An unknown ticket type has been queried via the connected EDP. This request is trea-
ted like a call made for a ticket in assisted sales mode.
106 6.126.98.1.01.70
Satusmessages SW
51585 Text message: vendor is not a cashier !

Cause:
the SC is operated with the setting CONFIGURATION / POS / AMOUNT TEND./
CHANGE OP. YES. Tickets can only be made up on this SC via the total [*] key by ven-
dors who are created as cashiers.
Remedial action:
check the settings of the vendor used in the menu point DATA MAINTENANCE / VEN-
DOR DATA.
51586 Text message: POS sales tables not created.

Cause: appears during evaluation of POS reports on an SC which has been commis-
sioned WITHOUT POS REPORTS.
Remedial action:
1.) Evaluate the POS report on an SC which has POS
REPORTS created.
2.) Check commissioning values. Recommission scale.
51590 Cause: only the master is active. Other scales cannot be addressed.
Remedial action:
51591 Cause: journal carries out a new start as a master or a slave unit.
Remedial action:
51592 Cause: BOKA table full. Ticket data is no longer fetched.

Remedial action:
3
51593 Cause: normal scale looses master information.
Remedial action:
51595 Cause: transmission of tickets was not acknowledged.

Remedial action:
51596 Cause: ticket already contained in master unit.

Remedial action:
51597 Cause: ticket request error – ticket gen. / internal timeout.

Remedial action:
51598 Cause: connection error, internal system.

Remedial action:
51651 Cause: function AwInit 1.

Remedial action:

Remedial action:

Remedial action:
51654 Cause: function AwInit 4

Remedial action:
6.126.98.1.01.70 107
Statusmessages SW
51655 Cause: function AwCheck.

Remedial action:
51656 Cause: function AwStart

Remedial action:
51657 Cause: function AwUmsDel.

Remedial action:
52050 Cause: forced cancel in Work2.
Remedial action:
1.) Restart of a cancelled transmission by means of another table.
Error is recovered by transmitting the password telegram several times.
Ignore error.
52051 Cause: forced cancel in Error.

52052 Cause: forced cancel in Work2.

52053 Cause: SWCOM program version incorrect.

Remedial action:
1.) SWCOM is incompatible with SC CPU program status. Update SWCOM.
52054 Cause: SWCOM program revision incorrect.

3
52055 Cause: SWCOM program date incorrect.
52056 Cause: password required.

Remedial action:
1.) Check password set on SC.
CONFIGURATION / INTERFACES / SERIAL INTERFACE / PARAMETERS.
Check password set on EDP.

See status No.52056.
52058 Cause: no action in Admin.

52059 Cause: no action in Work 1.

52060 Cause: no action in Work2.

52061 Cause: scale No. invalid.

52062 Cause: local scale absent.

Appears on sales call via EDP,
Remedial action:
108 6.126.98.1.01.70
Satusmessages SW
52063 Cause: table inactive.

52064 Cause: buffer not enough capacity.

52065 Cause: fatal error in file 1.

52066 Cause: no message in file 1.

52067 Cause: no message in file 2.

52068 Cause: no file in Delete.

52069 Cause: no file in Read.

52070 Cause: block number incorrect.

52071 Cause: cancel parameter error.

52072 Cause: no file in Write.

52073 Cause: fatal error in Write.

Error on EDP connection. 3
52074 Cause: buffer overflow in CheckGet.
52075 Cause: error from CheckGet.

52076 Cause: message invalid.
Remedial action: 1.) Check message.
52077 Cause: message parameter incorrect.
52078 Cause: message not executed.
52079 Cause: report.
52080 Cause: report.
Appears on sales call via EDP. Scale absent.
Remedial action:
1.) Switch on all scales
52081 Cause: fatal error in Util2.


6.126.98.1.01.70 109
Statusmessages SW
52083 Cause: size used incorrect.

52084 Cause: watchdog in ComExit incorrect.

52085 Cause: watchdog in ComCheck incorrect.


52087 Cause: task post error.

52088 Cause: general error in COM.

52089 Cause: task initialization error 1.

52090 Cause: task initialization error 2

52091 Cause: no parameter in ComDiff.

52092 Cause: parameter in ComDiff incorrect.

52093 Cause: no record in ComDiff.

3 Error on EDP connection.
52094 Cause: fatal error in ComTaskInit.

52095 Cause: parameter in ComFile incorrect.

52096 Cause: message in ComMsgStat incorrect.

52097 Cause: parameter in ComMsgStat incorrect.


52099 Cause: magic number incorrect.

52100 Cause: no file in ComParaStatus.

52101 Cause: last error in COM.

53050 Cause: general error in LS1.

53051 Cause: fatal error in Ls1Task.

110 6.126.98.1.01.70
Satusmessages SW
53052 Cause: no action in Work.

53053 Cause: no valid scale number.

53054 Cause: key error in Ls1Empf.

53055 Cause: no ESC at field end.

53056 Cause: number of offsets in Ls1KopfUmbau.

53057 Cause: number of att. > max.

53058 Cause: number of keys > max.

53059 Cause: attribute type incorrect.


53061 Cause: @–seq. in DeCodeAsciiStr incorrect.

53062 Cause: no integer.

Error on EDP connection. 3
53063 Cause: value overflow.
53064 Cause: field length > max.

53065 Cause: LSV1 buffer not enough capacity.

53066 Cause: parameters in Ls1Send incorrect.


53068 Cause: parameter in Ls1 header incorrect.

53069 Cause: TYdbmAtt structure in Ls1 header incorrect.

53070 Cause: last error in LS1.

53304 Cause: error during initialization of LSV1.

Error on EDP connection with LSV1 protocol.
Remedial action:
6.126.98.1.01.70 111
Statusmessages SW

Remedial action:
53319 Cause: disallowed parameters.

Remedial action:
53351 Cause: transmission being active.

Remedial action:

Remedial action:

Remedial action:
53354 Cause: error in automatic unit.

Remedial action:
53355 Cause: Ctrl function called up.

Remedial action:
53356 Cause: exit function called up.

3 Remedial action:

Remedial action:
53358 Cause: telegram in send queue could not be deleted.

Remedial action:
53359 Cause: cancel.

Remedial action:
53360 Cause: cancel of send sequence by the master unit.

Error on EDP connection with LSV1 protocol
Remedial action:

Remedial action:
53362 Cause: semaphore timeout ellapsed.

Remedial action:
53363 Cause: automatic send unit stopped.

Error on EDP connection with LSV1 protocol
Remedial action:
112 6.126.98.1.01.70
Satusmessages SW
53604 Cause: error during initialization of Wfb.

Message on connection of a Wittenborg card reader.
Remedial action:

Remedial action:

Remedial action:
53619 Cause: disallowed parameter.

Remedial action:
53651 Cause: transmission active.

Remedial action:

Remedial action:

Message on connection of a Wittenborg card reader
Remedial action:

Remedial action:
3
Remedial action:

Remedial action:

Remedial action:

Remedial action:
53659 Cause: repetition error during transmission.

Remedial action:
53660 Cause: Wittenborg terminal transmits error.

Remedial action:
53661 Cause: MIN/MAX value violated.

Remedial action:
6.126.98.1.01.70 113
Statusmessages SW
53704 Cause: error during initialization of G&D.

Message on connection of an EC terminal.
Remedial action:

Remedial action:

Remedial action:
53719 Cause: disallowed parameter.

Remedial action:
53751 Cause: transmission active.

Remedial action:

Remedial action:

Remedial action:

3 Remedial action:

Remedial action:

Remedial action:

Remedial action:

Remedial action:
53759 Cause: repetition error during transmission.

Remedial action:
53850 Cause: general error in COP.
53851 Cause: fatal error in CopTask.
53852 Cause: received buffer too small.
53853 Cause: received buffer too large.
53854 Cause: help string larger than MAX.
114 6.126.98.1.01.70
Satusmessages SW
53855 Cause: input data incorrect.
53856 Cause: cancel error in PLU.
53857 Cause: assortment cancellation requested.
53858 Cause: cancel error in assortment.
53859 Cause: proc. identifier incorrect.
53860 Cause: invalid character in text.
53861 Cause: error in ticket cancellation.
53862 Cause: error in getting the ticket header.
53863 Cause: error in getting ticket items.
53864 Cause: ticket status > 2
53865 Cause: ticket status ==1, STYP !=1
53866 Cause: ticket status ==2, STYP !=2
53867 Cause: error > 9000 in getting the BOKA record.
55051 Cause: error code from TelBvAktError.
55054 Cause: error code from TelBvAktVbon.
55055
55061
Cause: error code from TelBvAktSbon.
Cause: cancel because of incorrect recording number.

3
55062 Cause: cancel because of incorrect ticket number.
55063 Cause: cancel because of insufficient memory in Boka (dbm error).
55064 Cause: cancel after timeout error.
55065 Cause: cancel because of system error.
55066 Cause: cancel because op. management record absent.
55067 Cause: cancel. Not implemented.
55070 Cause: ticket record cancelled in the interim.
55071 Cause: ticket not processed at remote station.
6.126.98.1.01.70 115
Statusmessages SW
55090 Cause: no free customer number available.
55091 Cause: end–Tel–Broad.
55092 Cause: wrong telegram read on customer/vendor log–on,
55093 Cause:
auto. customer No. semaphore occupied by other scale.
Appears in continuous sales mode CUSTOMER/VENDOR LINKAGE, AUTOM. CU-
STOMER NO. Several vendors create a new customer at the same time.
Remedial action: repeat sales procedure.
55094 Cause:
request for customer No. although semaphore is occupied.
Appears in continuous sales mode CUSTOMER/VENDOR LINKAGE, AUTOM. CU-
STOMER NO. Several vendors simultaneously call up the same customer No.
Remedial action: repeat sales procedure.
55200 Cause: load capacity code incorrect.

Remedial action:
1.) Recalibrate scale with correct code.
55351 Text message: end of paper.

Cause: appears during printing when unit has run out of ticket paper.
Remedial action:
1.) Ensure that paper is correctly inserted.
2.) Check light barrier in paper chute.
3.) Check connecting cable between printer controller and light barrier.
3 55352 Text message: print bar tilted.
Remedial action:
1.) Ensure print bar is correctly closed.
2.) Check reflex light barrier on printer.
3.) Check connecting cable between printer controller and light barrier.
55353 Text message: motor overcurrent.

Remedial action:
1.) Check mechanical unit of printer for jamming.
Remove jamming paper or labels.
2.) Check connecting cable between motor and printer controller.
3 Replace printer, motor might be defective.
2.) Replace printer controller, evaluation of tacho–generator
might be defective.
55354 Text message: printhead overheated.

Cause: the maximum printhead temperature of 60° C has been reached.
Remedial action:
1.) Let printhead cool down.
2.) Connecting cable on printhead might have loosened.
Ensure proper seating. If necessary fix it by means of
adhesive.
If error recurs:
116 6.126.98.1.01.70
Satusmessages SW
55355 Text message: motor blocks.

Cause: paper feed blocks during printout.
Remedial action:
Remove jamming paper or labels
and acknowledge with <Enter> key.
2.) Replace printer, motor might be defective.
3.) Replace printer controller, evaluation of tacho–generator
might be defective.
55356 Text message: no speed adjustment possible.

Cause: adjustment was not correctly made during self–adjustment of printer, e. g.: no
paper inserted, end of paper during adjustment.
Remedial action:
1.) After switching the unit OFF/ON, the adjustment is automatically repeated.
If error recurs:
55357 Text message: printer identification incorrect.

Cause: scale cannot recognize built–in printer.
Remedial action:
2.) Check connecting cable to printer.
55358 Cause: printer initialization unsuccessful.
55359 Cause: no valid layout pointer.

3
55360 Cause: no valid form pointer.
55361 Cause: speed constant received from printer incorrect.

Remedial action:
Remove jamming paper or labels
2.) Replace printer, motor might be defective.
55362 Text message: error during load. of layout.

Appears during printout of labels.
The cause might be as follows:
See error messages.
– status No. 55363
6.126.98.1.01.70 117
Statusmessages SW
55363 Text message: error during loading of standard label layout.

Appears when printing standard labels.
Remedial action:
1.) Check available memory via display or print out the RAM status.
The print data is edited in the currently available memory. If the capacity does
not suffice to edit this data, the above error message will be output.
55364 Text message: error during loading of freely program. label layout.
Appears when printing freely programmable labels.
Remedial action:
2.) The setting in CONFIGURATION/PRINTER/LABELS
is already on FREELY PROGRAMMABLE LABEL, the SC
has, however, not yet stored a freely programmable label.
The layout must be edited in the CWS and be transmitted
accordingly.
3.) The files transmitted by the CWS for the freely programmable label were corrupt.
Ensure that the SC and CWS program versions are compatible.
55365 Text message: error during loading of counter label layout.

Appears when printing counter labels.
Remedial action:
55366 Text message: error during loading of region.

3 Appears on printout of freely programmable labels.
Cause: Regions are defined fields in the CWS which have a predefined content.
Example of region:
Price frame Small label
Remedial action:
118 6.126.98.1.01.70
Satusmessages SW
55367 Text message: error during loading of logo.

Appears when printing logos (pictures).
Remedial action:
Logos for the SC should not exceed 40kB per logo.
2.) The files transmitted by the CWS for the logos were corrupt.
Ensure that the SC and CWS program versions are compatible.
55368 Cause: overflow of printer stack on changeover.

55369 Text message: learn mode unsuccessful.

Appears when menu point LEARN MODE FOR END OF PAPER is carried out.
Remedial action:
1.) Print bar open. Close print bar.
2.) Mechanical unit of printer blocks. Eliminate blockage.
55370 Cause: cancel at printer synchronization.

Internal error.
55371 Cause: index for printer character set table not permitted.
55372 Cause: printer ID not permitted.
55373 Text message: primary printer inactive.

Remedial action:
1.) The primary printer selected in menu point 3
CONFIGURATION/PRINTER/GENERAL is wrong.
55375 Text message: no connection to printhead.

Appears during printout.
Remedial action:
1.) Check connecting cable between printer controller and thermal printhead.
55376 Cause: layout management not initialized.

Not enough unbuffered RAM available for decompression of print layout.
Remedial action:
55381 Cause: extension of layout incorrect.

55451 Cause: range of fraction oz exceeded.

Appears in conjunction with a tare when the value entered in the fraction oz range is
incorrect, a manual weight input and fixed weigth values, e. g.: 9/8 oz.
55452 Text message: coding error.

Cause: bar code data is incorrect.
Remedial action:
1.) Check the code structure used in the DATA MAINTENANCE/BAR CODE DATA.
6.126.98.1.01.70 119
Statusmessages SW
55453 Text message: digit overflow in value coding.

Cause: internal errors of bar code data. The coded value (DM, kg, pcs.) has more digit
places than provided in the DATA MAINTENANCE/BAR CODE DATA for the bar code.
Remedial action:
1.) Check the number of digits for the coded values in the code structure used.
55454 Text message: coding of negative value.

Cause: an attempt was made to encode a negative value in a bar code.
55455 Cause: checkdigit overflow in department or selling price.

Appears if the printout is set to CHECK DIGIT in menu point CONFIGURATION / PRIN-
TER / PRINTER X / LABEL.
Remedial action:
1.) Check department number (a maximum of 2 digits should not be exceeded).
2.) Check determined selling price (a maximum of 6 digits should not be
exceeded).
55456 Cause: weight unit incorrect.

Appears in SALES PROCEDURES.
Special program for USA.
Remedial action:
1.) Check the settings for the used article in menu point GEN. MODIFICATION/
ARTICLE MAINTENANCE. An article set to OZ cannot be processed on a
scale using the kg–unit and vice versa.
55457 Cause: error in code structure No. 0.

Appears in conjunction with a scanner connection.
3 55471 Cause: no scanner configured.
55472 Text message: incorrect entry in code structure.

Cause: code structure used in instore code incorrect.
Remedial action:
check the data of code structure used for disallowed entries in menu point DATA MAIN-
TENANCE / BAR CODE DATA.
Pay special attention to the placeholders used for the code contents.
55472 Cause: check digit incorrect.

Remedial action:
1.) Check print image of bar code for DOT failure and print quality.
2.) Find out scale by means of which the bar code is printed. Check printer on this
scale.
3.) Clean thermal print bar.
4.) Check paper quality.
5.) Optimize printer settings.
6.) Replace printer if defective.
120 6.126.98.1.01.70
Satusmessages SW
55473 Text message: bar code type unknown.

Cause:
the scanner connected transmits an unknown code type. Only the EAN8, EAN13, UPC
A and UPC E codes used in trade are permitted.
Remedial action:
1.) Check the programming of scanner for use of the above code types.
55473 Cause: structure in instore code invalid.

Remedial action:
1.) Check the values set for the bar code used in DATA MAINTENANCE/BAR
CODE DATA. Use only settings which are permitted.
55474 Text message: bar code allocation not created.

Cause:
key error in SCST–table.
The scanned EAN No. is not assigned to a PLU.
55474 Cause: code type unknown.

Remedial action:
1.) Check read–in bar code type.
The following code types are permitted: UPC–A, UPC–E, EAN–8 and EAN–13.
55475 Text message: bar code allocation table not created.

Cause: the SCST–table is not existing.
Remedial action:
a value must be entered in the menu point COMMISSIONING/ARTICLE DATA/ACCES-
SORIES/NUM. OF DA. IN BAR CO. TAB. Recommission unit.
55476 Text message: code structure not created.

Cause: key error in COST–table.
3
Remedial action:
1.) Check whether or not a code structure is created under the code digit used in
menu point DATA MAINTENANCE / BAR CODE DATA.
55477 Cause: COST table not available.

Remedial action: recommission unit.
55478 Cause:
input error in check digit calculation.
Check digit incorrectly computed.
55479 Text message: check digit incorrect.

Cause:
scanned bar code incomplete. Error during manual input.
Remedial action:
check the print image of the bar code for DOT failure. Repeat the manual entry of the
EAN number.
55551 Cause: list entry not found by editor.

Appears when operating with multiple line text editors.
55552 Cause: list without entry.

6.126.98.1.01.70 121
Statusmessages SW
55553 Cause: list cannot be initialized or is already initialized.

55554 Cause: list contains no further data.
55555 Cause: range not in order.
55570 Cause: script not initialized.

Appears when operating with functions.
55571 Cause: script key error.
Remedial action:
If error recurs:
55572 Cause: script management full.
Appears when concatenating functions.
A maximum of 20 functions may be active at the same time and be concatenated with
one another.
Remedial action:
structure the concatenations in a different way.
55572 Cause: script management empty.

55574 Cause: script key memory full.

3 55575 Cause: function not permitted.

55576 Cause: script data error.

Remedial action:
1.) Cancel the function used and create again.
55577 Cause: script delay active.
55578 Cause: script waits for interaction.

55579 Cause: transmission parameters during creation of menu incorrect.
55580 Cause: autostart not possible. Menu level incorrect.

Remedial action:
1.) On start of function, article call still active in sales procedure menu.
2.) The SC is in price labeling mode in which functions are not activated via an
automatic start.
55581 Cause: wrong menu level on autostart.

55582 Cause: privilege violation.

An attempt was made to change to a higher order menu point by means of key [ESC] in
connection with a function which was protected from access.
122 6.126.98.1.01.70
Satusmessages SW
55583 Cause: F menu has been aborted via the keyboard.

An active function has been aborted by means of key [C].
55584 Cause: F menu has been aborted via the software.

The execution of a function has been interrupted by an error message, e. g. ’end of
paper’.
55585 Cause: important control data invalid, processing is cancelled.

55586 Cause: number of function menu starts via autostart ”continuous”.


Appears in conjunction with SWDasi: The transmission of the SCST–table involves
problems.
Remedial action:
1.) Repeat transmission. Check the entries made in the two files ERROR.LOG and
SWC_BAT.LOG.
55651 Cause: database key incorrect.
55652 Cause: no file in ParaStatus.

Appears during transmission of data to EDP.
55653 Cause: parameter in file incorrect.

55654 Cause: parameter not permitted.

55655 Cause: buffer has not enough capacity. 3

The buffer for the EDP transmission in the SC is too small.
55656 Cause: no file available.

Appears when connecting an EDP. The requested files are not available. They might
not have been created during commissioning.
Remedial action:
1.) Check whether or not the requested files have been considered during
commissioning. Recommission scale.
55657 Cause: an attempt was made to access an unknown table.

55658 Cause: interface function not available.

55659 Cause: an attempt was made to access an unknown function parameter.

55660 Cause: entry still active (MIGROS).
Special program for MIGROS–Schweiz AG.
SC evaluation still active.
55661 Cause: Migros master inactive (MIGROS).

Remedial action:
Check menu point COMMISSIONING for the correct setting of the MIGROS
application.
6.126.98.1.01.70 123
Statusmessages SW
55662 Cause: last request not yet terminated (MIGROS).

55663 Cause: rebooking not possible (MIGROS).

55664 Cause: resetting of busy flag forced (MIGROS).

The booking has been reset by the EDP.
55665 Cause: evaluation currently not possible. Another evaluation task active at present.
55666 Cause: an attempt has been made to change the domestic currency.
55751 Cause: data has been written in the PLSJ table although it was not opened.
The OPEN COMMAND was not used in running the price modification journal and
transmitting graduated prices from the EDP.
55752 Cause: PLSJ closed before it was opened or was opened already.
55853 Text message: Attention ! Switch on all deactivated scales!

Remedial action:
1.) Switch on all units connected to the system.
55854 Text message: Attention ! Switched off scales !

Remedial action:
3 1.) Switch on all units connected to the system.
55856 Text message: input incorrect.

Cause: incorrect entry of licence number in menu point OTHER FUNCTIONS/LICEN-
CES/ACTIVATE SOFTWARE MODULE.
Remedial action:
1.) Enter correct number.
55857 Text message: monthly balancing still active.

Cause: interruption of active monthly balancing in conjunction with time recording by
deactivating the scale.
Remedial action:
1.) Reactivate monthly balancing in menu point OTHER FUNCTIONS /
TIME RECORDING / MONTHLY BALANCING. This can also be done on any
other SC scale.
55858 Cause: no further entry records.
55859 Cause: timeout in getting of accounting records!
55860 Cause: cancel of an active monthly balancing procedure.
55861 Cause: bar code information cannot be evaluated.
124 6.126.98.1.01.70
Satusmessages SW
55862 Cause: cancel of error handler via C–key.

Appears if a text message is cancelled via the [C] key.
Remedial action: for control purposes only.
55863 Cause: return of error handler – YES.

Appears if a text message is acknowledged with YES.
55864 Cause: return of error handler – NO.

Appears if a text message is acknowledged with NO.
55865 Text message: key switch position incorrect.

Applies to the SC–C only.
Cause:
appears when selecting menu points which can only be carried out via certain key
switches.
Remedial action:
check the settings in the menu point CONFIGURATION/KEYBOARD/KEY SWITCH.
55951 Cause: file not initialized.
55952 Cause: file incorrect.
55953 Cause: file full.
55954 Cause: file empty.
55955 Cause: file not available.
56053 Text message:

ticket data older than validity period! Adopt ticket data? YES / NO.
3
Cause:
an active ticket remains stored in the ticket/journal memory for a longer time and after a
longer period of time, the consecutive ticket or automatic customer number is repeated
which causes the system to ask whether the new items are to be added to the ”old”
ticket data which is still retained.
Acknowledgement with YES: operations are continued with the existing ticket data.
Acknowledgement with NO: a new ticket is started.
56054 Text message: disturbance in system. Check ticket.

Cause: disturbance on system bus.
Remedial action:
1.) To check the ticket data, have them output to the display in a brief form. If the data
is incorrect, reissue the ticket.
If error recurs:
56055 Text message: data updated? Check ticket !

Cause:
several tickets having an identical consecutive ticket number are stored in the ticket/
journal memory.
Remedial action:
1.) To check the ticket data, have them output to the display in a brief form. If the data
is incorrect, reissue the ticket.
If error recurs:
6.126.98.1.01.70 125
Statusmessages SW
56056 Text message:

data in other scales. Access to own scale only!
[ENTER]
56057 Text message:

scale not connected to bus. Access to own scale only! [ENTER]
56058 Text message:

customer No. conflict. Data cannot be accessed ! [ENTER]
56152 Cause: the disbursement type used is not supported by the EC terminal.
Remedial action: ensure that the disbursement types created in the menu point DATA
MAINTENANCE/DISBURSEMENT TYPES are supported by the EC terminal.
56350 Cause: init of log not in order.

Remedial action:
56351 Cause: init. of ADC not in order.

Remedial action:
56352 Cause: init. of menu not in order.

Remedial action:
56353 Cause: init. of keyboard not in order.

Remedial action:
56354 Cause: init. of graphic devices not in order.

Remedial action:
56355 Cause: init. of configuration not in order.
3 Remedial action:
56356 Cause: init. of printer not in order.

Remedial action:
56357 Cause: init. of VBAW not in order.

Remedial action:
56358 Cause: init. of script not in order.

Remedial action:
56359 Cause: init. of scale not in order.

Remedial action:
56360 Cause: init. of sales procedure not in order.

Remedial action:
56361 Cause: init. of data maintenance not in order

Remedial action:
56362 Cause: init. of article maintenance not in order.

Remedial action:
56363 Cause: init. of reports not in order.

Remedial action:
56364 Cause: init. of service not in order.

Remedial action:
126 6.126.98.1.01.70
Satusmessages SW
56365 Cause: init. of time recording not in order.

Remedial action:
56366 Cause: init. of timer not in order.

Remedial action:
56367 Cause: init. of LW database manager not in order.

Remedial action:
56368 Cause: init. of COM not in order.

Remedial action:
56369 Cause: init. of E–Cash not in order.

Remedial action:
56370 Cause: init. of TCP not in order.

Remedial action:
56371 Cause: init. of POS not in order.

Remedial action:
56372 Cause: init. of scanner not in order.

Remedial action:
56373 Cause: init. of PLU journal not in order.

Remedial action:
56374 Cause: init. of nutrition not in order.

Remedial action:
56375 Cause: init. of Migros not in order.

Remedial action: 3
56376 Cause: init. of EDP interface not in order.
Remedial action:
56377 Cause: init. of ticket maintenance not in order.

Remedial action:
56378 Cause: init. of licence manager not in order.

Remedial action:
56379 Cause: init. of communication; Pb2, Sem, Tel not in order.

Remedial action:
56380 Cause: init. of communication; Tel–Tasks not in order.

Remedial action:
56381 Cause: init. of database not in order.

Remedial action:
56382 Cause: init. of database indices not in order.

Remedial action:
56383 Cause: init. of diagnostics not in order.

Remedial action:
56384 Cause: init. of vDbm not in order.

Remedial action:
56385 Cause: init. of LW licence manager not in order.

Remedial action:
6.126.98.1.01.70 127
Statusmessages SW
56386 Cause: init. of LW scale manager not in order.

Remedial action:
56387 Cause: init. of update manager not in order.

Remedial action:
56388 Cause: init. of currency manager not in order.

Remedial action:
56450 Cause: key switch or key wrong.

Remedial action:
56550 Text message: par. ticket not found or cannot be accessed.

Cause:
Remedial action:
56551 Text message: system error, partial ticket include not possible. Retry.
Cause:
Remedial action:
56552 Text message: system error, partial ticket include not possible.
Cause:
Remedial action:
56553 Text message: partial ticket include not possible in delivery note mode.
Cause:
Remedial action:
56554 Text message: partial ticket include only possible in POS mode.
Cause:
3 56571
Remedial action:
Cause: error during the creation of a TB copy.

Remedial action:
56572 Cause: invalid TB in include.

Remedial action:
56573 Cause: error during activation after cancel.

Remedial action:
56574 Cause: error during the creation of TB info ticket.

Remedial action:
56575 Cause: error in item storage in TB info ticket.

Remedial action:
56576 Cause: error during the creation of cancel ticket.

Remedial action:
56577 Cause: error in item storage of a cancel ticket.

Remedial action:
56578 Cause: error in cancellation of a cancel ticket.

Remedial action:
65000 Cause: general output of scale numbers 65001 – 65032.
65100 Cause: general output of table numbers 65101 – 65150.
65200 Cause: general output of scale number in case of customer/vendor error.
128 6.126.98.1.01.70
Satusmessages SW
6.126.98.1.01.70 129
Satusmessages SW
Ladenwaage SC, SC–H, SW7

POS–Terminal SC–C, SC–CW
Statusmeldungen
System Class 6.126.98.1.00.70
Alle Rechte vorbehalten

All rights reserved
Tous droits réservés
Reservados todos los derechos
Tutti i diritti riservati
© 1999
Bizerba GmbH & Co. KG, 72336 Balingen
6.126.98.1.01.70 1
Statusmessages SW
2 6.126.98.1.01.70

EroriBizerba PDF

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

EroriBizerba PDF

Загружено:

Авторское право:

Доступные форматы

SW 7.0, SC–Serie 1.

Alle Rechte vorbehalten

BIZERBA GmbH & Co. KG, 72336 Balingen

BIZERBA GmbH & Co. KG, Postfach 10 01 64

1.1 Text messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–1

Last page of section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 – 129

1.1 Text messages

In force up to field test program version 1998/03/30.

Text message Cause/remedial action

ADC error Appears during the selection of menu point CALIBRATION.

Apply commodity Appears if the operating mode SELF–SERVICE is activated.

Apply weight Appears in sales mode.

Archive error Appears during selection of menu point CALIBRATION.

Article not created ! Appears in ARTICLE MAINTENANCE.

Text message Cause/remedial action

A special offer record being Cause:

Attention !! Switch on all deactivated Cause: scales are inactive.

Attention: Max. number of XXX Appears during concatenating of functions.

Attention: Only XXX Appears during the creation of functions.

3 keys available to accept function ! Cause:

Attention: Switched off scales ! Cause:

Attribute type incorrect Appears in sales mode.

Text message Cause/remedial action

Bar code allocation not possible Cause:

Bar code menu incorrect

Bar code type unknown Cause:

BVBT reference to BOKA

By–Count deselected Appears in sales mode on SC scales commissioned with PCS.

Text message Cause/remedial action

Call not initialized

Cashier has not determined Appears in cashier’s reports.

Checksum of POS report incorrect

Check tolerance Appears in sales mode when using assortment PLUs.

Text message Cause/remedial action

Coding error Appears during printing of bar code.

Coding of negative value Cause:

Command invalid Cause: internal error.

Commissioning data does not agree Cause:

Acknowledging with NO causes the message REMOVE SCALE

Commissioning data loaded could Appears after loading of a data backup.

Conf. identifier not clear Cause: configuration data destroyed.

Text message Cause/remedial action

Created partition(s) wrong Appears during commissioning.

Create new ticket Internal message.

Customer not created Cause:

Text message Cause/remedial action

Database key incorrect

Database not existing Cause: internal error.

Database table not created Appears in sales mode.

Database table not found Appears in sales mode.

Appears in POS mode.

Data loaded. Modify data if Appears after data backup.

DBM error during cancellation

Text message Cause/remedial action

Different ticket type Appears in

Digit overflow in value coding Appears during printing of bar codes.

Disconnected/incorrectly configured Cause: appears when selecting ARTICLE MAINTENANCE if not

Disturbances in data transmission Appears during printing.

Double address in system ! Appears during activation of an additional scale.

Double initialization for total sales

Dpf magic number incorrect Cause: memory management destroyed.

Text message Cause/remedial action

EDP interface active ! Appears after recommissioning of unit.