Top Border
Home | About us | Contact us | FAQs | Log in

Products

> Bench Scales

> Indicators

 

Applications

Documentation

> Literature

> Approvals

 

Resources

> Manuals

> Calibration

> Software

> Firmware

 

       
Top Bar

 

Frequently Asked Questions

 

 

Below we have listed many frequently asked questions. Most browsers provide a search feature by pressing Ctrl+F - try this to find your FAQ.

GSE Range

CAUTION - before opening any indicator to connect or disconnect cables or perform any fault finding or diagnosis, ALWAYS disconnect the power.

> Entering and exiting set up model

> Defaulting an indicator

> Calibration

> Code 02, code 03, code 08

> Calibrating with code 02, code 03 errors

> No response from load cell

> Code 57, code 59, code 26, "dbLncError"

> "Mode 91msg"

> Setting/changing capacity and division size

> Code 34, code 35, code36, code 37 resolution error

> Loading a program modification file

> Over-run error "OvernError"

> frmg error

> Entry error

> Code 11 wrong code

> ">Max Entry"

> Firmware not recognised (Rabbet & Wedge)

> Entering alpha-numeric values

> What order should 60-series SBM modules be connected?

> How many optional modules can I fit to an indicator?

> What are the connections on IO modules?

> What are the connections for PDIO channels

> Serial cable connections

> Configuring a 350 or 355 for a remote button

> Trap error or watchdog error

> Printer not working

> Setting the label length on an Intermec C4 or PC4 printer

> Setting the label length on a TSC printer

> FTP error

> Setting date & time

 

 

 

Entering and exiting setup mode

Most parameters over 100 require an access code and so the general method of entering setup mode is to key in 100<Select> followed by the access code and then the <Enter> key.There are two passcodes, one for full access and another for limited access. Note that older versions of firmware on the 60-series required the <ID> to be pressed after the access code. To exit setup, press the <Zero> key and follow the prompts pressing <Enter> for yes and <Clear> for no as appropriate.

 

Back to top

 

Defaulting an indicator

To reset an indicator to it’s default settings, enter setup mode and select either parameter 65001 for a full default or 65002 to default all except the calibration.

 

Back to top

 

Calibration

To access the calibration an access code is required. There are then several different methods of calibration with a zero and span being the default. Full instructions are in the technical manuals but simplified zero/span calibration instructions can be found by following this link (you will need a logon name and password).

 

Back to top

 

Code 02, code 03, code 08

These codes are all indications that the load cell signal is outside the normal range of operation. Code 02 = underload, code 03 = overload, code 08 = high signal. For code 02 and code 03 errors, perform checks for loading and/or re-calibrate. Code 08 errors are nearly always indicative of a failure in the connection, cabling or load cell.

 

Back to top

   

Calibrating with code 02, code 03 errors

A code 02 or code 03 error can interfere with the calibration process. This is often the case when connecting to a different platform from the one that was used to perform the initial calibration. The recommended method of resolving this is to reset the calibration and then re-calibrate with the new platform. To do this, enter calibration mode in the normal way and either press the Select key repeatedly until the Reset Cal prompt is shown and then press Enter, or press the Clear key.

 

Back to top

   

No response from load cell

If there is no response in the displayed weight when the applied load is changed then this may be caused by the jumper settings being positioned for 6-wire load cell when a 4-wire load cell is connected. On the main board, next to the terminal block for the load cell connections, ensure both jumpers are in the correct position; “Int” for a 4-wire load cell and “Ext” for a 6-wire load cell.

 

Back to top

   

Code 57, code 59, code 26, "dbLncError"

Error codes 57 and 59 indicate a problem with data stored in the database memory. The error messages are displayed when power is applied to the indicator as it performs checks on the memory and reports any discrepancies. When the error message is displayed, press any key to continue in operation. In many cases, the indicator will then operate normally with no other ill-effects. Erros can be cleared by performing a database reset at parameter 65010 but this will require the data to be backed up first and then once the reset has been performed the database structure will need to be reloaded in to the indicator before then reloading the backed-up data. Also, if the program has been stored in database memory then the whole program may need to be reloaded. It is recommended to seek advice before performing this operation.

 

Back to top

   

"Mode 91msg"

If the indicator shows “Mode 91Msg” then this is most likely to have been caused by the indicator being configured as a slave. This can happen with a new indicator when first powered up as the user is prompted to select one of the factory programs and it is possible to inadvertently select the slave program that is intended for connection to a master indicator. In this mode, the indicator will not respond to key presses because the key presses are redirected to the master. To resolve this, turn off the power to the indicator, hold down the Clear key and turn the power on. You will be prompted first to inform you that it is disabling macros and then to ask whether to disable com 1. Once macros have been disabled, you will then be able to access setup mode and reset the indicator to a standard default operation at parameter 65002.

 

Back to top

   

Setting/changing capacity and division size

There are generally three types of setup parameters; free entry, index (pick from list) or enable/disable. Good examples are the basic scale set up; scale capacity is a free entry parameter and the user can key in any value and press Enter, division size is selected from an internal list by an index, and each scale can be enabled or disabled. When specifying the division size, a common mistake is to try and key in the division size required; however, the entry is interpreted as the index in the selection list so, for example, keying in 1 will result in a division size of 0.0001 as this corresponds to the entry specified by index number 1. The easiest method of changing the division size is to repeatedly press the Enter key to scroll through the available selections until the required division size is achieved. Alternatively, key in the index of the required division size (by either referring to the manual, trial and error, or noting the index of the current selection).

 

Back to top

   

Code 34, code 35, code 36, code 37 resolution error

When exiting setup, the indicator checks the resolution specified for each scale. If the resolution is greater than 25,000 divisions, a warning message “RES> 25K!” will be displayed; if this resolution is intentional then the warning message can be ignored. Other errors (> 100,000, < 100, < 1) are normally caused by a mistake in entering the division size; the user will have to check the entries for scale capacity and division size. Unintentionally selecting the incorrect division size is a common mistake – see the instructions for setting capacity and division size for more information..

 

Back to top

   

Loading a program modification file

A file containing program modifications can be loaded from any terminal program such as the one in Rabbet, CommPlus or HyperTerminal. Make sure that the com port settings match those of the indicator (9600, 8, N, 1 by default) and send the file. In most cases, the indicator should finish showing parameter 64102 which will indicate if an error occurred; if successful, it will show “1stEr None!”. If errors have occurred, it is sometimes worthwhile checking the number of errors by pressing the <Scale Select> button to show parameter 64101. Exit setup either saving or undoing changes as appropriate. Click here for more information.

 

Back to top

   

Over-run error "OvernError"

An over-run error is normally caused when the receive buffer on the indicator is full and the handshaking is not working correctly resulting in data clashing. Ensure that handshaking on the host PC matches that in the indicator (Xon/Xoff by default) and if using CTS/RTS handshaking that the handshaking lines are connected on the RS232 port. There is a known problem with some USB to RS232 convertors that do not handle handshaking properly. One possible workaround is to specify a line delay in the serial port settings on the host PC; a typical value would be 50ms if using Rabbet, CommPlus or a terminal program or 1 if using Wedge.

 

Back to top

   

frmg error

This message is an abbreviation of “framing error” and normally indicates that the baud rate of the host computer is different to that of the indicator.

Back to top

   

Entry error

Although this is a generic error message it can be caused by either a value incorrectly keyed in if entering values manually or an incorrect baud rate if communicating from a host computer.

 

Back to top

   

Code 11 wrong code

The code 11 error is caused by entering the wrong code when trying to enter setup mode. Apart from a mistake in entering the code, this could also be because the access code has been changed from the default or that the indicator is running an older version of firmware and the key has been omitted.

 

Back to top

   

"> Max Entry"

Some programs, notably the factory program on the 675 bench scale and some custom firmware, use a %K command when the unit is powered up. This command restricts the size of the entry buffer and if a program is then downloaded to the indicator, entries are likely to generate the error message “> Max Entry”. This will be seen at parameter 64102 and the number of errors at parameter 64101 will be very high. To avoid this problem, send a %K command before sending the program file, either from a terminal program or by adding it to the file.

 

Back to top

   

Firmware not recognised (Rabbet & Wedge)

When Rabbet and Wedge send data to the indicator, the programs first check the version of the firmware to ensure that it is compatible. If there is a problem with the communication then an error message will be generated.

In Rabbet:

“Unable to Read FirmWare Revision. This may be a Port Error, or the Indicator is not turned on or connected.”

And in Wedge:

“Desired Version 540 or Higher. You may wish to Reflash the Indicator’s Firmware?”

 

If you see one of these error messages then check the connections and com port settings.

 

Back to top

   

Entering alpha-numeric values

The ability to enter alpha-numeric characters through the numeric keypad was only added in later versions of firmware. For those programs that were developed on older firmware, alpha-numeric characters are entered through the cursor keys; F1/F2/Units/Tare on the 56x and F1/F4/F3/F5 on the 66x and 675. More details can be found by following this link.

 

Back to top

   

What order should 60-series SBM modules be connected?

The only restriction for connecting 60-series SBM modules is that any IO modules must be the last in the chain; otherwise the modules can be connected in any order. The IO modules can be connected in any order themselves, the first will be allocated setpoints 1-4, the second setpoints 5-8 and so on.

 

Back to top

   

How many optional modules can I fit to an indicator?

The maximum number of modules that can be connected depend on the specification of the indicator. The maximum number of modules that can be fitted internally to an indicator is limited to; 1 for 46x models, 8 for the 665 indicator, 2 for other 66x and 56x models. Additional modules can be housed in a separate enclosure and it is recommended to use round-sheathed ribbon cable that can pass through the cable gland.

 

Back to top

   

What are the connections on IO modules?

Input channels are active high. Connections are:
+ input signal
- 0V
Output modules require an external power supply and will return the switched voltage when the corresponding setpoint is activated. Connections are:
+ supply voltage (from the external power supply)

- switched voltage (to the device to be switched)

 

 

Back to top

   

What are the connections for PDIO channels?

PDIO channels are active at 0V and when unconnected they are pulled up to +5V.
The maximum voltage that can be applied to a PDIO channel is 30V and the maximum current that an output can sink is 30mA DC.
Input channels should be connected to provide 0V to indicate an active state; e.g. for a simple switch input, connect one contact to the PDIO terminal and the other to 0V.

Output channels should be connected so that when the PDIO is driven to 0V the device is activated; e.g. for a simple lap output, connect one lamp terminal to +V and the other to the PDIO.

 

 

Back to top

   

Serial cable connections

Connections for serial cables depend completely on the device being connected to. The terminal block on the main board of the indicator has a legend identifying each terminal. Also note that if hardware handshaking is not used then CTS/RTS need not be connected and if the device is only communicating on way with a device, e.g. a printer (transmit only) or a scanner (receive only) then the other conductor does not need to be connected. Typical connections are as follows:
Generic terminal connection


Indicator

DB9 male connector

Gnd

5 - Gnd

Rx

2 – Rx

Tx

3 - Tx

This type of connection can be useful if the connector is going to be used for multiple purposes because then a standard connecting cable can be used; e.g. a null modem cable to a PC port or a standard printer cable to a printer.
Direct PC connection


Indicator

DB9 female connector

Gnd

5 - Gnd

Rx

3 - Tx

Tx

2 – Rx

Printer (25-way connector)


Indicator

DB25 male connector

Gnd

7 - Gnd

Tx

3 – Rx

CTS

20 - DTR

Printer (9-way connector) (note for some printers, pin 4 DTR and pin 6 DSR need to be connected)


Indicator

DB9 male

Gnd

5 - Gnd

Tx

3 – Rx

CTS

8 - RTS

 

 

Back to top

   

Configuring a 350 or 355 for a remote button

It is common to configure a 350 or 355 for a filling application with a remote button to both tare and start the fill. However, the options in the filling configuration only give the options for either one or the other.  To achieve this functionality, set the fill to start on tare and then in the general section, set the remote button function to perform a tare.

 

 

Back to top

   

Trap error or watchdog error

A trap error or watchdog error is an internal processor error and is usually indicative of a significant problem at processor level. There is no defined procedure for recovering from this type of error other than to try and reset the system by cycling the power, defaulting and reloading an application or in the worst cases, reflashing the unit with new firmware.

 

Back to top

   

Printer not working

Printer failure can be caused by a variety of problems but there are a few basic checks to carry out.

  • Firstly, check the connections; even if a printer has been working in the past, ensure that the cable has not been damaged and that the wires are all intact and connected and there are no short circuits.
  • If using a printer for the first time or if using a different size label, the printer may need to be configured for the label length. See separate instructions for doing this.
  • Another common cause is that the label gap sensor has been knocked out of position. This is a small sensor inside the printer that detects the gaps between the labels – if this has been knocked to one side then it will not be able to detect the gaps and this will produce an error condition.
  • Some printers can be configured to wait until a label is removed before the next label is printed. The “label taken sensor” is position in the opening of the printer where the label comes out. Try removing any labels that have already been printed.
  • When a printer does go in to an error condition it can indicate this through a display if it has one or by an LED on the casing. Check the manual for documentation on the causes of any errors.

 

Back to top

   

Setting the label length on an Intermec C4 or PC4 printer

Turn the power off, hold the feed key down and then turn the power on and then release the feed key. The printer should print a test label and then feed on to detect the gap. Tap the feed key again to put the printer in to a label printing mode. NOTE: holding the feed key down in this state will reset all the default printer settings so is not advisable.

 

 

Back to top

   

Setting the label length on a TSC Printer

Although this is a generic error message it can be caused by either a value incorrectly keyed in if entering values manually or an incorrect baud rate if communicating from a host computer.

 

Back to top

   

FTP error

Response codes >99 relate to general FTP server error codes. Response codes from 0-99 are generated by the ethernet option board. Please click her for futher information.

 

Back to top

   

Setting date & time

For futher information on setting the date and time please click here.

 

Back to top