Professional Documents
Culture Documents
Instruction
Weight indicator 47-20 Basic
Revisions
Date Revision Notes Signed
2009-10-08 1.0 First edition TK
2009-10-20 1.1 Minor changes of example images. TK
2010-08-23 1.2 Changed all images to new colour scheme, added TK
information about new features: dosing and setpoint
quick access. Revised other functions that have been
modified.
2011-03-24 1.3 Revised settings due to changes in functionality. Added TK
information about preset tare, multiple indicators and
PLC block.
2011-04-28 1.4 Incorrect pin designations on Excitation+/- in section TK
10.1. Polarity was reversed, corrected.
Updated printout examples with tare values.
2011-12-15 1.5 Added information about subtypes 47-20-02/03 in TK
section 10.
Added subtypes 47-20-02 /03 in section 12.2.
2012-03-29 1.6 Added information about multi-range, id-prompt and TK
new serial protocols Modbus, Toledo8530 and PrintLog.
New options for I/O interface (external power).
2012-06-28 1.7 Incorrect pin designation on COM1 RS485 interface TK
corrected.
Contents
1 Introduction ......................................................................................................... 11
1.1 General ................................................................................................................................ 11
3 Start-up sequence................................................................................................ 19
1 Introduction
Thank you for choosing a Flintab weight indicator.
Flintab scales and indicators combine weighing functions and features to
provide exceptional flexibility, user friendly operation and reliability.
The 47-20 weight indicator can be configured to suit most applications.
The integrated interfaces enable problem free data transmissions to and from
peripheral equipment and due to its rugged construction the weight indicator
can be installed in most environments.
By carefully studying this manual, all the features offered by the weight
indicator can be fully appreciated.
1.1 General
Weight indicator 47-20 is the latest generation of Flintab instruments which
combines modern technology with flexible design, making it suitable for most
weighing applications. Weighing capacity, filtering and other weighing
parameters are fully selectable and can be configured to suit any scale and
weighing requirements. The main features are:
• Compact and rugged construction for industrial applications.
• Very high speed (28000 samples/s) 4 channel loadcell interface
• Integrated interfaces (some optional)
• Up to 3 serial ports, RS232 and/or RS485
• Native fieldbus support; Modbus, Profibus, CANopen, DeviceNet,
Modbus-TCP, Profinet-IO, EtherCAT and many more.
• 100MB Ethernet
• 4 channel opto-isolated NPN outputs and 3 channel opto-isolated
inputs
• USB host and slave interfaces
• 4.3” colour touch screen with large easy-to-read indications and a ‘finger-
friendly’ touch screen adapted interface
• Optional integrated DSD (data storage device, ALIBI) for up-to10 million
transactions.
Current indicator
(Press to change) Log
active
Operator info
button
(Press to read)
Max, Min and Avg, shows the maximum, minimum and average value
of the raw low-filtered high resolution weight value. By pressing the
button on the plug-in, start values are set to current weight value. See
image:
Max, Min and Std, shows the maximum, minimum and running
(approx 1 seconds of data) standard deviation of the raw low-filtered
high resolution weight value. By pressing the button on the plug-in,
start values are set to current weight value. See image:
Scale parameters
(Capacity nameplate)
OIML R76
(also M symbol)
TAC counter
Lock / Unlock
weighing functions
Current weighing
function group no.
Lock / Unlock
Depending on current
state
Cancel
Restart, only
available when
calibration mode is
active
3 Start-up sequence
Power on will initiate the following sequence steps:
Boot sequence; initializing hardware, Flintab logotype shown on the
display. Up to 20 seconds.
The weight indicator will then show the main weight display and enter
normal weight indicator mode. If configured for automatic initial zero
setting at power-on the display will blink at about 0.5-1 Hz while
waiting for the weight value to be within specified range and stable
during the required interval. In that case the zero will automatically be
set. However if the weight value is outside allowed range, the
automatic power-on zero function can be aborted by pressing the
<Start> button. See images below:
• If the sum is to be printed then press the <Print Total> button. The
sum will automatically be cleared/reset after the printout.
If more than four indicators are available, the next block of four indicators
can be displayed by pressing on the alternate button, bottom right.
Press to return to
normal nameplate
On the dose module all buttons are of the press and hold type to avoid
unintentional operation. I.e. to activate a button it must be pressed for a
minimum of 1 second.
Depending on if the selected dose module is setup for batching or normal
dosing, different tools will be shown.
Press to exit dose I/O status Current target weight Press during dosing
module to pause
Press to view batch Press within frame to change Press to start dosing or
status mode and/or target stop during dosing
Batch towards a Batch without target weight Opens both inlet and outlets valves
target weight i.e. continuous dosing i.e. no dosing or batching
Press to cancel Press to set batch Press to set batch Press to save
settings and return to target weight start weight settings and return to
batch tool batch tool
Dose status
The utility has individual buttons for changing each set point value and a
visual indication of current weight is below or over set value. The label
entered for the set point is shown a heading above the value. See image
below:
Green arrow = weight Edit this set point Set point value Press 1 second to
below set point return to normal
button panel.
Red arrow = weight
above set point Next four set points
(if available).
5.3 ID-Prompt
Id-prompt is a configurable sequence handler for operator input and printing.
Number of steps, the length and type of data for input is setup through the
settings editor.
If no ID-prompt is defined, then the button will be displayed greyed-out else
see images below:
6 Utility functions
To access utility functions, the operator need to press the <Alternate
Weighing Function Group> button twice, see images below:
*2
The DSD, when installed, has a capacity of about 10’000’000 unique weight
transactions, after this number of transactions has been stored; the number of
the oldest transaction is re-used (wrap-around).
The indicator also has a feature called instrument ID number, where a two
digit prefix can be attached to each alibi number, generating a 9 digit number.
When reading the DSD the alibi number should always be entered without
this prefix, i.e. use only last 7 digits.
Start log
The settings controlling the level (error, warning, info, verbose) of status
information to be logged is set through the settings editor.
The display will alternate between, all segments on and all segments off,
about 10 seconds before automatically returning to normal weight display.
Note: the display test does not alternate the display plug-in.
! !
the operator to carefully assess that outputs does not operate on machinery or
systems that can pose a threat to personal safety or cause machine faults. By
operating this tool, the user acknowledges full responsibility.
Normally this tool is only accessible when ButtonPanel4 is activated, see
section 8.5.3.
Note: If an output is coupled with a currently running process such as dosing,
set points etc. the output will be continuously regulated even during the usage
of this tool as the indicator is still in operation. This means that these outputs
will always revert to the state dictated by the process, even if the user tries to
set other states.
To start the tool press the <I/O> button, see image below:
The available I/O’s are shown with the current status, colorized (orange)
means that the respective input or output is activated.
In addition to the available physical I/O signals (standard is four inputs and
four outputs) 32 so called markers are available. Markers are internal
memory only I/O signals; they can be used by any process that requires inputs
or outputs but does not require an actual physical signal to be used.
To allow user manipulation of outputs and markers, press the <Yes> button
for 2 seconds. See image below:
When the <Yes> button is lit red, the corresponding signal can be alternated
by pressing on it. However if the signal is controlled by an active module
such as set points, the signal can behave erratically as there are two possibly
competing states wanting to act on it. For test purposes its advices that all
modules acting upon I/O signals are disabled when operating this tool. See
image below:
When finished with the tool, press the <Exit> button for more than 1 second.
Note: Outputs and markers will keep the state they currently have when
exiting the tool, i.e. they will not be reset to the state they were in when the
tool was started, unless an active module is operating on it.
SCALE
LOADCELLS GND COM3
12VDC
USB-A
USB-B
Fieldbus (COM2) ETH0
I/O COM1
CAL
Calibration mode active is indicated on the main display with the upside-
down triangle, se image below:
Make sure the USB-memory stick is inserted into the indicator before
proceeding.
Press the <Update Application> button to start the update procedure. When
finished, the indicator will restart.
When the indicator has restarted, the update procedure is finished and the
USB-memory stick can be removed from the indicator.
Press the right arrow on the left pane, to proceed to the next step.
7.4.2 Step 2, Division size and decimal point
Select division, for multi-interval scales select the interval to be used in the
lowest interval (smallest). Then select number of decimals to be used. Note
the previous unit selection and division size. Example: selecting unit = ‘kg’,
division = ‘10’ and decimals = ’0.00’ means that one division (the smallest
weight possible) will be shown as: 0.10 kg.
On the right pane the current scale parameters are displayed, they will be
modified in the following steps and therefore can temporarily show incorrect
data.
Press the right arrow on the left pane, to proceed to the next step.
Press the right arrow on the left pane, to proceed to the next step.
7.4.4 Step 4, Enter multi-interval/range settings
The weight indicator can be setup to use up-to three intervals; here the
breakpoints between the intervals are set. When the weight passes a
breakpoint, division size is automatically switched to the next larger size.
When unloaded the division size will switch back to the smaller sizes at the
configured breakpoints
Alternatively the indicator can be setup to use a dual range scheme, in this
mode the indicator will likewise switch to the next larger division size when
the weight passes the breakpoint, however the larger division will be retained
until the scale is unloaded. I.e. the indicator will operate as two scales, each
with a different division size; the indicator will automatically choose the
appropriate range depending on current and previous load. This mode will
also round tare values to the scale interval in the highest activated range.
If multi-interval or dual-range is not to be used, then leave both interval
settings at zero
Interval 1 is the lowest breakpoint and interval 2 is the highest. The order
must be zerointerval 1interval2maximum weight. If only two intervals
are to be used, then leave interval 2 at zero.
Press the right arrow on the left pane, to proceed to the next step.
7.4.5 Step 5, Review scale configuration
The parameters that define the scale are now set-up and the new configuration
will be shown in the right pane. If the settings are correct then proceed by
pressing on the right arrow. Otherwise press the left arrow and correct the
settings as needed before continuing.
Press the right arrow on the left pane, to proceed to the next step.
Choose test weight calibration if you have a scale and test weight available,
else make sure indicator is normalized and you have the datasheets for the
loadcells, before choosing data sheet calibration. Data sheet calibration is
covered in section 7.4.11to 7.4.16.
7.4.7 Step 7, Set zero level (calibrate zero)
Make sure that the scale is empty of all foreign material (containers etc) and
that the dead-load (platform etc.) is mounted on the scale. Then press the <Set
zero level> button and wait for the zero sampling to be completed.
When the zero level has been successfully acquired, the calibration sequence
will automatically proceed to the next step.
When the calibration point (test weight) has been successfully acquired, the
calibration sequence will automatically proceed to the next step.
Press the right arrow on the left pane, to proceed to the next step.
When all loadcells are entered, press the Exit, then Yes button:
Review the summary and make sure it matches the scale before proceeding to
the next step by pressing the right arrow in the left pane.
When the zero level has been successfully acquired, the calibration sequence
will automatically proceed to the next step.
7.4.15 Data sheet Step 10-2, Calculate scale zero level
To calculate zero level, enter the deadload of the scale platform into the field,
then press the next button.
The value entered will be used as a zero level reference and respond to
displayed weight value of zero.
7.4.16 Data sheet Step 11, Preview calibration result, save settings
Before the calibration is accepted and the settings are saved, the preliminary
result can be reviewed. The weight is shown with increased resolution (10x)
to give an indication of the quality of the calibration. The current input signal
from the scale (loadcells) as mV/V is also shown. The operator can now
choose to either accept the setting by pressing the <Save settings> button, or
to go back to redo any of the previous steps by pressing the left arrow on the
left panel.
If the calibration has been done by calculation and/or loadcells are not
connected then the displayed weight and input values have no relevance.
Save graph
y-axis units
Settings for save graph Save current settings, requires a new graph-start
to come into affect
8 Settings editor
The indicator is very versatile and can be setup for most weighing
applications, some settings are set by a dedicated tool such as <Full
Calibration> other requires the use of the so called settings editor.
Also by starting the settings editor, the software version and date of the
indicator can be viewed.
The settings editor is activated by pressing the <Settings editor> button, see
images below:
Navigate in tree
Settings tree Expand/Collapse tree or
Edit setting (if possible)
There are different types of settings nodes indicated by the symbol in the tree
view and repeated in bottom right corner of the info pane;
Collection branch, a group of settings, can also be further nested with
additional branches under current level. Serves only as a container
object, can not be changed or edited.
Always non editable. Example; calibration weight. These settings
cannot be directly altered by the operator, unless through the use of
dedicated tools.
Protected access parameters. These settings are normally related to
the meteorological aspect of the indicator. Settings controlling filters,
zero levels etc. These can only be changed when calibration mode is
activated (lock open).
General access parameters. Settings controlling other portions of the
indicator, such as set-points, communication etc. These settings are
always editable.
Apart from the different types of settings nodes, each parameter is also of a
specific value type. For example, numeric, string, option etc. Each of these
value types has an associated editor. See images below:
Number editor Text editor
Max. and min. values Input keypad, shift key to Input keypad, shift key to
Parameter info access additional pad Parameter info access capitals pad
Value with unit
! !
Important: Care must be taken when restoring data as incorrect settings will
rend your indicator inoperable. I.e. only restore settings that you know are
compatible with your application.
Note: restoring indicator settings containing meteorological data requires
calibration mode to be active.
To access the tool, start the settings editor:
Then press and hold (minimum 3 seconds) on the text where indicator version
and checksum is displayed:
After the correct recovery point is selected, the settings group must be
selected by highlighting and pressing <Ok> button. Note: IndicatorSettings is
only available when calibration mode is active. After the group is selected
press <Ok> button again, after a brief pause where the settings are restored, a
confirmation is shown. See image below:
Select the recovery point that is not needed any more and press <Ok>, a
confirmation is shown where the operator must confirm with <Ok> a second
time before the recovery point is actually deleted. When the deletion process
if finished, a final confirmation is shown, see image below:
When finished editing the backup folder name, press the <Ok> button to
return to the folder browser
The operator must select the appropriate root folder and eventual subfolders
by navigating in the folder browser, when finished press the <Exit> button. A
confirmation dialog is shown; press <Yes> if the selection is correct. See
image below:
Select the settings group to be restored by highlighting and then press the
<Ok> button to open the folder browser. See image below:
The operator must select the appropriate root folder and eventual backup
subfolder by navigating in the folder browser, then select the correct settings
file by highlighting, confirm by pressing the <Ok> button. In the confirmation
dialog shown, press <Yes> if the selection is correct. See image below:
Select the settings group where the node we want to backup is located by
highlighting and then press the <Ok> button to open the settings browser. See
image below:
After the operator confirms selection by pressing <Yes>, the folder browser is
shown.
The operator must select the appropriate root folder and eventual subfolder by
navigating in the folder browser, when finished press the <Ok> button to
select the folder, then confirm by pressing <Yes> to create the
group/parameter backup. The file name for the backup will be composed of
its full path in the settings file to allow for easy identification in the case it
needs to be used later. See image below:
The operator must select the appropriate root folder and eventual subfolder by
navigating in the folder browser. Finally select the backup file of the node to
be restored and press <Exit>. Confirm opening backup file by pressing
<Yes>. Finally accept the replacement of the previous node/parameter by
pressing <Ok>. See image below:
8.2 Indicator
This group contains all data relevant to the meteorological function of the
internal, external and virtual indicators. Such as calibration data, weighing
unit, filters etc. To edit these settings, most parameters requires calibration
mode to be activated (protected access). However some settings are only set
by an associated tool or read-only.
8.2.1 PrimaryIndicator
The parameter PrimaryIndicator works like a shortcut to an internal, external
or virtual indicator. I.e. once all indicators have been created (see following
sections) this parameter can be setup to point to the indicator that will be
selected on start-up.
In addition, the PrimaryIndicator shortcut can be used everywhere where an
indicator must be selected. This means that, changing the PrimaryIndicator,
will also change the indicator for all modules that are using the shortcut.
See example below, initially PrimaryIndicator is set to Sum1, if we change
PrimaryIndicator to Int1; the source for Setpoint1 will also be indirectly
changed:
Initial Setting Internal Indicators
Setpoint1 module Indicator->PrimaryIndicator Indicator->Sum1
Indicator = PrimaryIndicator PrimaryIndicator = Sum1 Sum1 = Int1 + Int2
New Setting
Indicator->PrimaryIndicator Indicator->Int1
PrimaryIndicator = Int1 Int1 = Channel1
Indicator->Int2
Int2 = Channel2
Note: The only module that is default set to use the PrimaryIndicator is the
Communication->Protocol->Flintab->Proto1.
8.2.2 NumInternalIndicators
This setting controls how many internal analogue indicators that are to be
activated. By internal means that the scale/loadcells is connected to one of the
four Ad-channels through the loadcell connector on the back panel of the
indicator. Only internal indicators can be legal for trade and pass
verification by a national notified body.
Maximum is four separate indicators. Default is only one indicator, connected
to Ad-channel one. If more indicators are needed, then set this parameter
accordingly, and then restart the instrument before any other changes are
made. After adding new indicator/s and restart of the instrument, each of the
new indicators must run through a full calibration sequence before they can
be used.
8.2.3 NumExtIndicators
This setting controls how many external indicators that are to be activated. By
external means that a remote indicator is connected through a communication
media such as serial port or network to the 47-20 instrument. The input from
the remote instrument is then used internally to create a virtual local
indicator. Therefore some limitations apply, such as no means to locally set
zero etc.
Restart of the instrument is required when this setting has been changed.
External indicators cannot be legal for trade.
After adding new indicator/s and restart of the instrument; first the VirtualAD
settings must be setup, then each of the new indicators must run through a full
calibration sequence before they can be used.
Parameter / Tool Data Values Comment
type
Default
NumExternalIndicators 0-6 How many external indicators to
activate.
8.2.4 NumSumIndicators
This setting controls how many summing indicators that are to be activated.
By summing indicator means that this indicator sums the output from 2 to 8
other local indicators (internal or virtual such as external, sum, flow or pulse)
and creates a new virtual indicator that displays the aggregated sum.
Therefore some limitations can apply such inhibition of setting zero etc.
It is also possible to cascade summing indicators, such that a output from one
summing indicator can be used as input to another summing indicator.
Restart of the instrument is required when this setting has been changed.
Summing indicators cannot be legal for trade.
After adding new indicator/s and restart of the instrument; first the VirtualAD
settings must be setup, then each of the new indicators must run through a full
calibration sequence before they can be used.
Parameter / Tool Data Values Comment
type
Default
NumSumIndicators 0-6 How many summing indicators to
activate.
8.2.5 NumPlaybackIndicators
This setting controls if a single playback indicator is to be available. By
playback means that this indicator will use a file as input data, the file should
previously been acquired by using the WeightBuffering mode in one of the
InternalIndicators. The playback indicator will then loop the data in the file
to repeatedly simulate the exact sequence of the measured analogue signal.
The playback indicator can then be used to fine-tune filters and other related
parameters without needing to perform a real world weighing sequence.
Restart of instrument is required when this setting has been changed.
Playback indicator cannot be legal for trade.
Parameter / Tool Data Values Comment
type
Default
NumPlaybackIndicators 0-1 How many playback indicators to
activate.
8.2.6 NumPulseIndicators
This setting controls how many pulse indicators that are to be activated. By
pulse indicator means that the instrument measures accumulated pulses from
a digital input signal and creates a virtual indicator that shows a calculated
weight value based on pulses/volume and density. As a pulse indicator have
no means for ‘unloading’, this means that zero set behaves different from a
normal indicator, a zero set command will reset the pulse indicator so it will
always start at ‘gross’ zero.
Restart of the instrument is required when this setting has been changed.
Pulse indicators cannot be legal for trade.
After adding new indicator/s and restart of the instrument; first the VirtualAD
settings must be setup, then each of the new indicators must run through a full
calibration sequence before they can be used.
Parameter / Tool Data Values Comment
type
Default
NumPulseIndicators 0-6 How many pulse indicators to
activate.
8.2.7 NumFlowIndicators
This setting controls how many flow indicators that are to be activated. By
flow indicator means that the instrument measures instantaneous pulses from
a digital input signal and creates a virtual indicator that shows a calculated
weight value based on pulses/volume, density and time. In contrast to the
pulse indicator, that accumulates each pulse, the flow indicator will only
show a value when there is a stream of pulses; the time between two pulses is
translated to an instantaneous flow measurement.
Restart of the instrument is required when this setting has been changed.
Flow indicators cannot be legal for trade.
After adding new indicator/s and restart of the instrument; first the VirtualAD
settings must be setup, then each of the new indicators must run through a full
calibration sequence before they can be used.
Parameter / Tool Data Values Comment
type
Default
NumFlowIndicators 0-6 How many flow indicators to
activate.
8.2.8.6 Loadcells__
Holds data related to data sheet calibration or for virtual indicators a single
loadcell with 1.8mV/V output and capacity set to indicator max capacity.
The settings editor can not be used to change this data, it can only be set by
the FullCalibration tool and data is entered through the associative functions
in the tool.
8.2.8.7 ADConverter
Holds parameters related to the effective sampling rate (measuring speed) of
the indicator and final FIR (Finite Impulse Response) filter.
To understand the relevance of the filter and sampling speed, the measuring
chain of the indicator must be visualized. See figure below:
Input x(n)
n=1-4
Decimator 5:1 Moving average FIR1 filter
28800 Hz 5760 Hz
z-1 z-1 z-1
5
…
∑ 1:1 – 128:128
y(n)
∑ 1-128 ∑ 1-128
tap
∑ 1:1 -128:128
v(n)
z-1 z-1
∑
Indicator Weight display
For a normal non-automatic indicator the full flexibility of the input stage is
not needed and the settings for the filtering- and decimation-blocks are
simplified. The FIR1 filter is fixed at 1:32, following cascaded decimation
stage is set by the parameter ConversionRate. The output from this stage is
the so called effective sampling rate usable by the indicator, and only a subset
of settings for the conversion rate will be available.
For virtual indicators the ConversionRate if default set to 11.25 hz and should
not be changed unless requested by Flintab. This as the stages before the
second FIR filter (FIR2) are virtualized and does not have a real world
analogue.
8.2.8.8 IIRFilter___
The IIR (Infinite Impulse Response) filter in the 47-20 indicator is an
advanced adaptive filter with pass-through functionality. It has a very fast
step response yet achieves a level of filtration (damping) comparable to very
wide FIR filters. This filter is not suitable for scales subject to high vibration
and is not used during data collection in automatic weighing mode.
8.2.8.9 Automatic
This group contains the settings for the automatic portion of the indicator, at
the moment this functionality is not fully supported and should be considered
experimental. Automatic weighing tests can only be temporarily activated on
the main button panel while calibration mode is activated.
Automatic weighing is only available for normal analogue indicators, not
virtual.
In automatic mode, a data collection sequence is triggered by either a physical
start signal and/or a specific weight level. After a specified time or when a
physical stop signal triggers, the collected data is passed trough a calculation
module to calculate an automatic-mode weight value. The weight value can
then be gain compensated before being displayed or sent on the
communication interfaces.
When used for automatic weighing, a different set of settings for sampling
rate and FIR filters are used after the start trigger. Therefore this group has its
own AdConverter subgroup setting the conversion rate while data collection
is active; see section 8.2.7.6 for explanation of the settings. Normally the
conversion rate is increased during data collection to generate more weight
samples for the calculation modules.
Parameter Data Values Comment
type
Default
StartSignal Input The physical input signal that
triggers a start data collection
sequence. Note: as standard only
None 0-3 are available on the indicator.
8.2.8.9.2 Trigglevel
When the scale is not subject to extensive amount of vibration or when the
object to be weighted is much heavier than the dead-load, it can be easier to
use the actual weight value as a trigger for the automatic data collection.
8.2.8.10 WeightBuffering
This group contains the settings for a weight buffer associated with the
indicator. When enabled the weight buffer will keep a, in-memory, time
limited ‘record’ of the raw analogue values measured by the ad-converter,
then at command (trigger) the content of the buffer can be saved to a file. The
files can then be used by the PlaybackIndicator to evaluate the effect of
various filters and related data, see section 8.2.5 for more information.
8.3 Application
This group contains miscellaneous settings for the instrument.
8.3.1 Log_______
This group contains the settings for the Status Information log (see section
6.3). This log can be configured to log application messages, warnings and
errors. Do not confuse with the weight data recorder log, see section 6.2. The
subgroup Sections contains settings for the type and level of application data
to log.
Normally this log should not be activated; it should only be used by
experienced technicians while analyzing performance or problematic
weighing applications. After changing settings for the application log, the
indicator must be restarted.
8.3.1.1 Sections_____
This group sets what type and level of information the application log will
store. As default only critical errors are logged.
Error
Settings Option Information about the settings
Error editor and associated files.
Dynamic Option Information about the automatic
Error indicator operation.
Static Option Information about the non-
Error automatic indicator operation.
Communication Option Information about the
Error communication interfaces.
Anybus Option Information about the fieldbus
Error interface.
Log Option Information about the weight data
Error recorder log.
Dose Option Information about the dosing-
Error module.
8.3.2 Alibi______
The indicator has a possibility to add a two digit instrument ID to the alibi
number. This is normally used in installations with several instruments to
discern between the generated alibi numbers. The ID number is displayed in
the DSD reader utility, but should be excluded when entering an alibi
number.
8.3.3 WatchDog
Contains settings for supervision logic and a hardware ‘watchdog’ that will
re-start the instrument if detecting an task that takes an abnormal amount of
time (lock).
Parameter Data Values Comment
type
Default
Default->PeriodMs Numeric How often the watchdog must be
signalled, else the watchdog will
enter supervision and take
control of the system. Zero
0 means the watchdog is disabled.
Default->RefreshMs Numeric How long the watchdog will wait
when in supervision mode before
re-starting the system. During
this time critical data will be
1000 ms saved.
8.4 Communication
The indicator has advanced module based communication interfaces; this
means that the communication device (serial port, TCP) is not directly
coupled with the protocol module. The only exception is the Anybus fieldbus
module that always uses serial port COM2 when enabled.
The protocol modules communicates through ‘logical’ devices, by using the
settings editor function AddRemoveDevice, new devices can be added and
coupled with physical hardware interfaces.
Currently there are three different types of protocol modules, Anybus
(fieldbus), Flintab and printout.
The fieldbus module uses a file for controlling the layout and content
of the data to be exposed on the external fieldbus interface (connected
to COM2). There are several different types of physical fieldbus
interfaces available (Profibus, Modbus Lonworks etc). The fieldbus
protocol (mapping) and interfaces are described in a separate
document.
The Flintab module uses the standard Flintab protocol (shared
between 47-04 and 47-10 families). It does not use any of the
extended functionality introduced in the 47-10 family.
Printout has a module for simple totalizing ASCII printing
functionality.
Parameter Data Values Comment
type
Default
AddRemoveDevice Tool used to add (or remove)
logical communication devices.
After adding a device, it is
configured or changed under the
group Devices. The available
logical devices will be selectable
in the protocol modules.
8.4.1 Protocol__
This group holds the available protocol modules. Further details on the
Anybus (fieldbus) protocol and interfaces are found in document 4-55235
Weightindicator 47-20 fieldbus interface description. The protocol for the
Flintab module is described in Appendix B – Flintab standard protocol. As
the indicator is subject to continuous development, your instrument may have
more protocols available, in such cases consult Flintab for more information.
8.4.1.1 Anybus[COM2]
The Anybus protocol module is to be used with a fieldbus interface board
connected to the (internal) COM2 serial port. The protocol module is not
dependant on the actual hardware interface used. Fieldbus device address
(where applicable) is set through the settings editor but mapping of indicator
data exposed on the fieldbus interface is controlled by parameters read from a
configuration file.
Parameter Data Values Comment
type
Default
SerialNumber Numeric Read only parameter, serial
number taken from Anybus
interface board.
ModuleType String Read only parameter, module
type read from Anybus
interface board.
DeviceAddress Numeric Fieldbus interface device
126 address (where applicable).
Enabled Boolean If the Anybus protocol module
is activated. Note: must also
be activated when using
False native Modbus support.
ResetModule Boolean True, will reset the fieldbus
board when exiting the
False settings editor.
ConfigFile Path Path and name of the protocol
configuration file. See
\FlashDisk\ separate documentation of
DefaultADIConfig file parameters.
8.4.1.2 Flintab___
This protocol module is a legacy ASCII based command-reply protocol,
compatible with previous generations of Flintab indicators (47-04 and
47-10 families). See Appendix B – Flintab standard protocol for details. Up
to eight separate Flintab protocols can be active at the same time.
8.4.1.2.1 Proto1-Proto8___
Flintab standard protocol is described in Appendix B – Flintab standard
protocol. However some key components are controlled by settings such as
inclusion of weighing unit etc. See table below:
8.4.1.3 Printout__
This module support simple ASCII printouts. Currently only totalizing
printouts are possible. See also Appendix C – Printout examples.
8.4.1.3.1 Totalizing
The totalizing module supports adding weights to accumulated sum, then at
operator command, print all individual weight values with alibi numbers and
end with the sum value. See section 4.3.
8.4.1.4 PrintLog___
This module support simple ASCII line based printouts for example used
when dosing and/or batching.
8.4.1.5 Toledo8530
This protocol emulates the indicator protocol most often referred to as Toledo
Continuous used by the company Mettler Toledo. Toledo8530 is one of the
instruments using this protocol but many other instruments and software
packages are also supported.
For a more detailed description of the protocol see Toledo 8530 service
manual.
8.4.1.5.1 Proto1-Proto8
Parameters for setting up the Toledo8530 continuous protocol emulation:
8.4.1.6 Modbus___
The indicator has a limited native Modbus support when not using a
dedicated Anybus hardware module. By limited means that only a small
subset of the available commands are implemented. Currently the only
following function codes are acknowledged:
• 0x03 – Read holding registers
• 0x05 – Write single coil
• 0x06 – Write single register
• 0x10 – Write multiple registers
To enable native Modbus the Anybus[COM2] fieldbus module must also be
activated, see section 8.4.1.1 (Enabled). Native Modbus and dedicated
fieldbus module will always share the same address (ID), see 8.4.1.1
(DeviceAddress).
Typical response time is <100ms.
For more information about fieldbus and Modbus see 4-55235
Weightindicator 47-20 fieldbus interface description.
8.4.1.6.1 Proto1-Proto8
Parameters for setting up native Modbus support:
Parameter Data Values Comment
type
Default
Enabled Boolean If this native Modbus handler is
False enabled.
8.4.2 Devices____
This group contains all available logical communication devices. Adding or
removing devices is done through the AddRemoveDevice tool.
The indicator has three serial ports (COM1-3), USB and Ethernet hardware
interfaces, logical devices for COM1 and COM3 are always created at factory
reset, COM2 is normally reserved to be used by fieldbus module. However if
the Anybus fieldbus module is disabled, COM2 can also be used to create a
logical communication device. Other logical devices using USB and Ethernet
as medium communicates by using TCP as either a host or slave and needs to
be added when required.
Additionally basic USB printer support is included, if a USB printer is
available during start of the instrument, a device labelled ‘USB
Printer1:LPT1’ is added to the list of available devices. Note: the port
designation (LPT1) can vary between installations.
As this functionality means that the operator can add their own devices, the
parameter table below only provides information about the factory default
devices, these cannot be removed.
8.5 UserInterface
This group holds the parameters for the visual appearance and functionality of
the button panels.
8.5.1 Display___
Settings for automatic backlight dimming and display-plugin.
8.5.2 MapIoToFunction___
This group contains parameters for using digital inputs to activate weighing
functions such as zero setting, tare etc.
Note: When using inputs to activate instrument functions, weighing related
functions will operate on the default indicator however functions starting
various modules, such as dosing and quick setpoints etc., will operate on the
currently selected indicator. This means that this function is dubious when
multiple indicators are accessible. In this case, use with caution.
Parameter Data Values Comment
type
Default
NumOfMapIoFunction Numeric How many weighing functions we
want to control by input signals.
Require restart of instrument to
0 take affect!.
For each I/O mapped to function the following settings are required:
Parameter Data Values Comment
type
1-16 Default
Enabled Boolean If this mapped I/O is active.
False
Function Option Which function to activate when
the input signal is detected. Will
always operate on the default
indicator.
Note: some functions may require
None calibration mode to be active.
Signal Option The signal that will activate the
IO Signal function.
Note: Some functions are not suited to be externally controlled, it’s up to the
installer to assess and determine if a specific mapped I/O gives the desired
outcome.
8.5.3 Buttons___
Parameters controlling the behaviour and functionality of the button panels.
Most settings require calibration mode to be active as they control which
functions that are available to the operator, this is not allowed to be changed
after verification by a notified body.
8.5.4 PowerOn___
For some installations it’s desirable that the indicator always start with a
specific function activated such as dose module etc. This parameter will
execute the selected function as soon as the power-on sequence is finished on
the PrimaryIndicator.
8.6 SetPoints
Setpoints are used when a digital signal state should relate to a specific
weight level, i.e. change their status when a certain weight level has been
reached. It can for example be used for simple dosing or overweight
detection.
Setpoints can operate on any available external I/O or memory markers. See
section 9 Instrument digital I/O for more details and examples of using the
I/O facilities of the instrument.
Parameter Data Values Comment
type
Default
NumOfSetPoints Numeric How many software setpoints to
activate.
Require restart of instrument to
0 take affect!.
8.7 Conveyor
During tests the indicator can be setup to control a conveyer system so that a
parcel/object can be continuously driven back and forth over the system. This
allows, for example, a conveyer with an integrated scale to be used for
automatic weighing repeatedly with the same weight. This group controls the
settings for this functionality.
8.8 PLC______
For larger installations or installations with special requirements a simple
digital I/O interface is most often not sufficient. To provide necessary safety
interlocks and I/O flexibility the instrument has a PLC (Programmable Logic
Controller) group.
The group consists of various logic building blocks that operate on digital I/O
signals similar to PLC ‘ladder’ programs.
Additional examples of usage and more information about I/O’s are
found in section 9 Instrument digital I/O.
Parameter Data Values Comment
type
Default
NumOfLadders Numeric How many PLC ‘ladder’ blocks to
create.
A single ladder block, can
logically bind up to 16 individual
I/O signals with selectable AND,
OR or INV logic to one single
output.
Require restart of instrument to
0 take affect!
NumOfSRFlipFlops Numeric How many SetReset FlipFlops to
create.
A SetReset FlipFlop is a stored
state gate with optional delays
for both set and reset events.
Can be used to generate a single
pulse from an input signal.
Require restart of instrument to
0 take affect!
NumOfTFlipFlops Numeric How many Toggle FlipFlops to
create.
A Toggle FlipFlop is a stored
state gate which toggles its state
at each set event.
Can be used when a single input
shall be used for both start and
stop events.
Require restart of instrument to
0 take affect!
NumOfIndicatorLadders Numeric How many IndicatorLadders to
create.
An IndicatorLadder logically
binds indicator status, such as
stable, zero etc. to digital I/O’s.
Also has ladder functionality.
Require restart of instrument to
0 take affect!.
The basic logical operations that can be evaluated on signal pairs, or sub-
blocks of signals are:
AND – Output true if all inputs are true.
OR – Output true if one of the inputs is true.
NOT – Output is true if input is false.
Some operations are combined, see table below of available functions, PLC
equivalents and comments:
Function PLC Comment
equivalent
Input_0 Marker_0
Ladder
Output
Input_1 Marker_1
Input_2
Example 2:
OutputSignal = ((Input_0 AND Marker_0) OR (Input_1 AND (NOT(Marker_1)))) OR
(Input_2 AND Input_3))
Equivalent ladder diagram:
Input_0 Marker_0
Ladder
Output
Input_1 Marker_1
Input_2 Input_3
Input_0
Input_1
1000 ms
Output_0
Settings:
Example 2:
A two second pulse on Output_0 triggered by Input_0 positive edge:
State diagram:
Input_0
Output_0 2000 ms
Settings:
SRFlipFlopGate Parameters Setting Comment
Input_0
Input_1
Output_0
Settings:
8.9 FileLogs
During installation or weighing performance analysis it is sometimes
necessary to use a weight data recorder, i.e. a log apparatus. The weight
indicator comes equipped with a versatile file log module that allows logging
of weight values and related status information.
8.9.1 DefaultLog
This log stores data as ASCII data in a text file, the file should be located on a
non-volatile media such as ‘FlashDisk’ (internal) or USB drive. When
logging is done, the file should be transferred to PC for reviewing.
Parameter Data Values Comment
type
Default
StartEnabled Boolean If the log should automatically
False start when indicator starts.
LogDirectory Path The path to where the log file will
be created. Use ‘\FlashDisk\’ to
use the internal memory, or
\FlashDisk\ ‘\USB HD\’ for USB memory.
LogFileName String The name of the log file. The
module will automatically
DefaultLog append the extension ‘log’.
AppendExistingLog Boolean If an existing file is found, then
True we add new data at the end.
OverwriteExistingLog Boolean If a file is already found, we
delete it and create a new empty
False file.
CreateInfoFile Boolean If true an additional file named
LogFileName but with extension
‘txt’ will be created when log
starts. This file contains current
False indicator settings for filters etc.
ObjectsToLog Option Collection of items that will be
logged. The order of the items is
also given. For example: Time,
Time, Max. gross weight, Avg. gross
MaxGross, weight etc. These items will all
AvgGross, be logged as a single line at
MinGross, each log event, see also
NumSamp. LogSeparator.
ResetAvgEachLogEvent Boolean If the running average variables
should be reset when a log
event expires. Note: average is
calculated for every weight
update even if actual logging
False events are further apart.
8.10 Dose_____
Dose modules are advanced versatile function blocks for dosing or batching a
single product to or from a container. Batching refers to when multiple dosing
cycles are automatically run in sequence until a preset accumulated (batch)
sum is reached.
For dosing of multiple products, see RecipeDose.
In contrast to a simple setpoint setup, a dose module has features to
compensate for variation in flow, overswing and inflight parameters. The
module also has an automatic tare or alternatively a zero check function. To
adapt the module to a specific installation, various settings need to be
configured. It’s advised that the dose parameter checklist, is used as a guide
during installation.
When all parameters are correctly setup, only the target value needs to be
changed between dosing cycles.
Note: Operational parameters such as target weight and batch weight are
normally set outside the settings editor through the use of dedicated tools.
Therefore, only system configuration parameters such as inputs/outputs,
limits and time intervals needs to be setup through the setting editor.
The 47-20 indicator can have several dosing or batching modules activated,
each operating on either the same or separate scales. Each module will dose
one single product.
Note: When RecipeDose is used, i.e. dosing of multiple products with
parameters from a recipe, the first dose module (Dose1) is required and used
by the RecipeDose as a framework for dosing functionality. However the
settings in the dose module will then be dynamically overridden by data taken
from the recipe database.
m PostDose (optional)
Target Value
Stop dosing
Flow control
t
Pre-Start check
Start
Check zero / Calculate tare
Pre-fill / Fine-fill
Course fill delay
Course fill
Overswing control
Inflight delay
Calc. weight. and inflight correction
Ready
Empty
(Pre-Start check)
8.10.1 LogSettings
This group contains settings for the dose or batch database. When activated,
each dose or batch cycle, will save the weight results into a database. The
database can then later be reviewed or transferred to a computer system for
statistical analyses.
8.10.2 Dose_____
This group and subgroups contain the parameters for the product to be dosed
or batched.
Parameter Data Values Comment
type
Default
Enabled Boolean If the dose module is active.
True
Indicator Option Which indicator (scale) is used
None for dosing.
IsBatchMode Boolean If this module should be used for
False batching.
DoseIn Option If dosing should be into (DoseIn)
or out from (DoseOut) from the
Dose In scale.
DoseValue Numeric The dose target weight, will
normally be set outside the
1 (kg) settings editor.
MinDoseDivisions Numeric The minimum number of divisions
5d that is allowed to dose.
AllowBackgroundDose Boolean When using the Dose module
interface tool, see section 5.1. If
the dose module is allowed to
keep running in the background
False even if we exit the tool.
8.10.2.1 DoseModuleStarted
It is possible to have a dedicated output signal indicating that the dose module
is running. I.e. this signal does not indicate active dosing, only that the
module controlling dose has started and is running.
8.10.2.2 Batch______
If this module is set to batch mode ( IsBatchMode = true, see previous page)
then the parameters in this group are valid.
8.10.2.3 Start_____
Input signal that triggers a start dose cycle, if not used set to <None>. This
signal should be removed before the dosing cycle has finished avoiding an
unintended re-start.
8.10.2.4 Stop_____
Input signal that triggers a stop dosing cycle, if not used set to <None>. The
stop signal de-activates course and fine outputs and calculates the weight that
was dosed when stop condition occurred; the dosing cycle is then ended.
Parameter Data Values Comment
type
Default
InputSignal Input Input signal to trigger a stop
None dose sequence.
SignalState Active, In which state the signal triggers.
NotActive
Active
8.10.2.5 Pause_____
Input signal that triggers a pause in the dosing cycle, if not used set to
<None>. By pausing means that course and fine outputs will be de-activated,
and that dosing is temporarily halted while the signal remains. As soon as the
signal is removed, dosing continues where it left off.
8.10.2.6 Abort_____
Input signal that triggers a abort of the dosing cycle, if not used set to
<None>. By aborting means that course and fine outputs will immediately be
de-activated, no result will be calculated, empty cycle will be skipped and the
dosing cycle will be aborted.
8.10.2.7 PreDose_____
This group sets the amount of pre-dosing that will be put in the container
before regular dosing starts. The dose module will use the fine output to reach
the required amount. Pre-dose is most commonly used to make sure a small
barrier of dosed product exists in the bottom of the holding container, this can
minimise splashing and kinetic energy transfers from the in-flight product
during normal fine/course dosing. After PreDose state the dose module
continues to the CourseDose state where both course and fine outputs are
activated.
8.10.2.8 ZeroCheck
This group sets conditions that regulate if the scale must be at (or close to)
zero before proceeding with dosing. Note the stability conditions are
recursive, this means that if the scale has been stable and within the allowed
limits before, and up to, function activates then the criteria’s are considered
fulfilled, zerocheck will then pass the dose module then continues directly to
Tare state.
8.10.2.9 Tare_____
This group sets conditions that regulate if the scale should be tared before
proceeding with dosing. By tared means that the weight of a container or
product from previous dosing will be automatically deducted from the dosing
that is about to start. I.e. the dosing will then use a net weight value.
Note the stability conditions are recursive, this means that if the scale has
been stable and within the allowed limits before, and up to, function activates
(after eventual delay) then the criteria’s are considered fulfilled, the tare will
be calculated the dose module then continues directly to PreDose state.
8.10.2.10 CourseDose
This group sets the conditions and output signal for the course dose portion of
the dose sequence. During course dose both FineDose and CourseDose
outputs will be activated. The exact amount of product that will be dosed
during CourseDose is only indirectly set by the FineDose value; therefore
course dose does not itself have a set value. In practice course dose will be
active from start normal dosing (after PreDose) and until (TargetValue -
FineDoseValue) is reached. To change the amount of product dosed during
CourseDose state, change the pre-dose or fine-dose values.
8.10.2.11 FineDose_
This group sets the conditions, amount and output signal for the fine dose
portion of the dose sequence. During fine dose only the FineDose output will
be activated. This stage has an OverSwing interval, during this time the fine
dose output will be active without comparisons between target and current
weight. I.e. the fine dose will be running ‘blind’. The OverSwing interval is to
bridge the kinetic energy introduced on the scale from product in free-fall
from the previous course dose stage, unless compensated this energy can
cause the scale to temporarily overshoot the target value and stop the dosing
sequence prematurely. After FineDose the dosing module normally continues
with the Target state, however for installations where the weight always
should be at or above target (i.e. not below) an optional PostDose stage can
be activated.
8.10.2.12 PostDose_____
This group sets the parameter for the optional postdose stage. By postdose
means that, after finedose is finished and inflight delay has expired, then the
current weight is checked against target, if the weight is still below target then
the postdose is activated. Postdose will in this case activate the FineDose
output for a set amount of time before the module continues with weight and
in-flight calculations.
This feature is normally only used in installations where weight should
always be at or above target, never below.
8.10.2.13 Target_____
This group sets the conditions for the in-flight and target weight calculation
portion of the dose sequence. In-flight refers to the amount of product that
enters the container even after dosing has been signalled to stop. The effect is
influenced by external factors such as pressure variation, product viscosity,
valves, pipes, etc. and these factors will affect the accuracy of the achieved
target weight.
In practice, to be able to reach the target value with highest accuracy, the in-
flight value controls the trip point before target value where the fine dosing
must stop. The in-flight value can be manually entered and remain fixed, until
changed by operator or alternatively be allowed to be automatically adjusted
after each dosing cycle.
Pulsating or inconsistent product flow will never be fully compensated by the
in-flight mechanics. The key to consistent and accurate weighing results
always relies on that external systems are linear and repeatable.
Note the stability conditions for weight calculation are recursive, this means
that if the scale has been stable and within the allowed limits before, and up
to, in-flight interval expires, then the criteria’s are considered fulfilled, the
weight and in-flight adjustment will be calculated the dose module then
continues to the Ready state
8.10.2.14 WaitCalcWeight
This group contains the parameters for an input optionally delaying the
weight calculation after dosing is finished.
8.10.2.15 Ready_____
This group sets the interval and optional output that will be activated after a
dosing sequence is finished, i.e. after calculation of weight result and inflight
correction. After the ready interval has expired the dosing sequence continues
with the Empty state.
Parameter Data Values Comment
type
Default
Time Numeric The minimum amount of time
after calculation of weight result
and in-flight adjustment are done
before the dosing module
proceeds to the next state. If an
output is defined, this will be
active for the full duration of this
1000 ms interval.
Output->Signal Output Which output that will be set to
true when ready is active.
None
Output->ActiveState Active, If output is active (high) or not
NotActive active(low) when;
Active Output state is true.
8.10.2.16 Empty_____
This group sets the interval and optional output that will be activated after the
Ready state has expired. It can be used to automatically trigger a discharge
cycle of the holding container. After the weight is below trip point and Empty
interval has expired the dosing module resets to the Start state.
Note: Empty stage is not applicable to DoseOut applications where dosing is
done by loss in weight.
8.10.2.17 Error_____
This group sets the optional output that will be activated whenever an error is
detected during the dosing cycle. When an error is detected the dosing is
stopped and the dosing module enters Error state. When entering Error state
all dosing related outputs are deactivated. Dosing does not automatically re-
start when the error condition clears, instead the operator has to manually re-
start a new dosing cycle after making sure that the cause has been eliminated.
Potential causes for Errors are:
Loss of weighing signal or weighing data out of bounds.
The dosing module is stopped (by external command).
If alarms are treated as errors, see next section.
8.10.2.18 Alarm_____
This group sets the optional output that will be activated whenever an alarm is
triggered during the dosing cycle. When Alarm state is entered dosing is most
often paused as the module waits for a condition that is not meet. Normally
dosing will automatically continue when the alarm condition is cleared.
However, thru setting a parameter, it is instead possible to treat Alarm
conditions as errors in which case the dosing is stopped, see previous section.
Potential causes for alarms are:
No or to low flow into the container during dosing, if the NoFlow
check is activated. Meaning that dosed product does not enter/leave
the container in the expected flow rate.
ZeroCheck state fails, meaning that the amount in the container
exceeds specified amount or that the weight is not within the desired
stable window (i.e. weight is unstable) for the zero to be examined.
Tare state fails, meaning that the weight is not within the desired
stable window (i.e. weight is unstable) for the tare to be acquired.
Target state fails, meaning that the weight is not within the desired
stable window (i.e. weight is unstable) for the dosing result to be
acquired.
8.10.2.19 NoFlow_____
This group sets the minimum amount of product that must enter/leave the
container during a specific interval, i.e. flow rate. When activated, flow rate is
checked during normal course- and fine-dose sequence. If the flow is not
sufficient an alarm is triggered, and the dosing is temporarily paused.
8.10.2.20 IsDosing
This group sets an output connected to the state where the dose module is
actively dosing, i.e. course- or fine- dose, wait target or calculating target.
Emptying does not affect the IsDosing output.
8.11 IdPrompt
IdPrompt is a configurable sequence handler for operator input and printing.
The operator controlled sequence will use fixed-, input-, weight-data and send
these to the PrintLog printer at command. See section 8.4.1.4 for more
information.
This group activates the IdPrompt, restart the instrument to enable
configuration.
Parameter Data Values Comment
type
Default
NumOfIdPrompts Numeric How many IdPrompts that should
be active (only one is allowed).
Require restart of instrument to
0 take affect!.
8.11.1 IdPrompt1
This group sets number of steps in the IdPrompt, then in each step the length
and type of data for input must be configured separately.
8.11.1.1 Step1-StepX
Each step in the IdPrompt sequence must be configured to match the operator
workflow by first setting the StepType and PromptText for all steps.
Initially each step will only have the following parameters:
Parameter Data Values Comment
type
Default
StepType Option What type of action this step in
the sequence will represent. See
None table below for available options
PromptText String The text presented to the
<Insert> operator for this step.
Then exit and re-start the settings editor to populate each step with settings
associated with the StepType. I.e. the parameters for each step depends on the
setting of StepType.
Each step can be setup to require operator confirmation before proceeding to
next step or alternatively be silent (automatic increment).
Table with available StepTypes:
StepType Comment
None No action
Text Used for fixed (operator cannot change) or operator
input text/data field, can also be setup for minimum
length.
Weight The currently displayed weight will be added to the
sequence.
PrintLog Print (send) the sequence data to the PrintLog printer
DateTime Add current date and/or time to the sequence
Weighing applications Or
Legacy I/O
3 – Relay outputs, Output_4..6
PLC, Dosing, batching, setpoints etc. 4 – Opto-isolated inputs, Input_4..7
See section 9.6 Digital I/O examples for examples of using a combination of
PLC gates, memory markers and set-points to create flexible weighing
applications.
Above tolerance
LimitHigh
Weight OK and stable 3s Within tolerance, weight OK
LimitLow
Below tolerance
Setpoint->SP2:
Stable OutOfRAnge
Marker_2
Function: When the weight is below both Setpoints we want this output to be
true (active).
Equivalent ladder diagram:
SP1:Marker_0 SP2:Marker_1
Output_0
PLC->Ladder->2:
Parameter Data Value Comment
type
SP1:Marker_0 SP2:Marker_1
Output_1
PLC->Ladder->3:
Parameter Data Value Comment
type
Function: When the weight above both Setpoints we want this output to be
true (active).
Equivalent ladder diagram:
SP1:Marker_0 SP2:Marker_1
Output_2
The final ladder is needed to gate the internal IndicatorLadder output (Stable
and InRange) with the WeightOk output.
PLC->Ladder->4:
Function: When the weight is between Setpoints and Stable and InRange the
output shall be true (active). We already have the signal for weight between
setpoints (WeihtOk) and indicator flags:
WeightOk AND (Stable AND InRange) = Output_1 AND Marker_2
Condition: Setpoint1 < Sepoint2.
Equivalent ladder diagram:
Output_1 Marker_2
Marker_3
The seond SRFlipFlop will only generate a one second pulse for the buzzer
when the output from the first SRFlipFlop has triggered.
PLC->SRFlipFlop->2:
10 Connections
The connectors for loadcells (scale), communication interfaces, I/O and
power are located on the back panel of the instrument. See images below:
Standard 47-20-01 without optional boards:
12VDC
USB-A
USB-B
Fieldbus (COM2)
ETH0
I/O COM1
CAL
10.1 Loadcells
The indicator has a single supply, single sense, four channel load cell
interface. This means that each channel (load cell input) has a dedicated input
stage and can be individually digitized, but the excitation (power supply) and
sense is shared between all channels.
Next to the load cell connector is a terminal for scale ground connection, it is
vital for the functionality and signal integrity of the indicator that a low ohm
connection between the scale platform and the indicator is made through this
terminal. Ideally this should also be connected to mains ground (earth) for
minimizing sources of measurement errors such as mains 50/60 Hz induced
EM fields. For the load cell signals, always use a shielded cable, with shield
connected to housing/platform in both ends.
The excitation is 10V regulated DC voltage biased around +2.5V, i.e. polarity
is +7.5V and -2.5V. Therefore make sure that no connections or signal paths
to ground or housing are made to the load cell power supply.
The connection to the load cell interface is made by a 15-pin d-sub male
connector (female/socket on indicator). Pin-out according to table below:
Socket number Signal Abbreviation
8 Load cell 1, signal + SIG_1+
7 Load cell 1, signal - SIG_1-
15 Load cell 2, signal + SIG_2+
14 Load cell 2, signal - SIG_2-
1 Load cell 3, signal + SIG_3+
9 Load cell 3, signal - SIG_3-
2 Load cell 4, signal + SIG_4+
10 Load cell 4, signal - SIG_4-
6 Sense+ SEN+
11 Sense- SEN-
4,12 Excitation- (-2.5V) EXC-
5,13 Excitation+ (+7.5V) EXC+
Housing Shield SHD
INPUT_1 4
+12V 3
OUTPUT_0 1 -
+12V 3 +
EX_OUT_A_x_NO
4k7 EX_IN_A_x
EX_OUT_A_x_NC
EX_IN_A_x_COMMON
EX_OUT_A_x_COMMON
3V3
Specification inputs:
high@min. 0.2mA, V in > 5VDC, V max < 36VDC
low@max. 0.04mA, V in < 3VDC
Specification outputs:
min. switching voltage 12VDC/AC
min. switching current 10mA
max. 6A@12DC
max. 0.8A@48VDC.
typical response time 5ms
J0T J1T
1 7 1 10
Inputs Outputs
1 7 1 10
J0B J1B
Inputs Outputs
Connector Pin Function Connector Pin Function
number number
J0T 1 EX_IN_A _1 J1T 1 EX_OUT_A_1_NC
J0T 2 EX_IN_A _2 J1T 2 EX_OUT_A _1_NO
J0T 3 EX_IN_A _3 J1T 3 EX_OUT_A _1_2_COMMON
J0T 4 EX_IN_A _4 J1T 4 EX_OUT_A _2_NC
J0T 5 EX_IN_A _1_4_COMMON J1T 5 EX_OUT_A _2_NO
J0T 6 GND J1T 6 EX_OUT_A _3_NC
J0T 7 12V_FUSED J1T 7 EX_OUT_A _3_NO
J0B 1 EX_IN_A _5 J1T 8 EX_OUT_A _3_4_COMMON
J0B 2 EX_IN_A _6 J1T 9 EX_OUT_A _4_NC
J0B 3 EX_IN_A _7 J1T 10 EX_OUT_A _4_NO
J0B 4 EX_IN_A _8 J1B 1 EX_OUT_A _5_NC
J0B 5 EX_IN_A _5_8_COMMON J1B 2 EX_OUT_A _5_NO
J0B 6 GND J1B 3 EX_OUT_A _5_6_COMMON
J0B 7 12V_FUSED J1B 4 EX_OUT_A _6_NC
J1B 5 EX_OUT_A _6_NO
J1B 6 EX_OUT_A _7_NC
J1B 7 EX_OUT_A _7_NO
J1B 8 EX_OUT_A _7_8_COMMON
J1B 9 EX_OUT_A _8_NC
J1B 10 EX_OUT_A _8_NO
Output_4-6_NO
4k7 Input_4-7
Output_4-6_NC
Input_4-7_CM
JP2 (Default) Output_4-6_CM
3V3
Specification inputs:
high@min. 0.2mA, V in > 5VDC, V max < 36VDC
low@max. 0.04mA, V in < 3VDC
Specification outputs:
min. switching voltage 12VDC/AC
min. switching current 10mA
max. 6A@12DC
max. 0.8A@48VDC.
typical response time 5ms
47-04:Photocell I/F
47-04:I/O Interface
47-04:COM1 (COM3)
The 4-55043 board (rev-1 or later) has three jumpers that needs to be setup
before use.
JP1 JP2 Jumpers
JP3 Designation Comment
JP1 Connects 47-04:COM1 pin 12 (RX I-) to
internal ground.
Default:Not Installed
JP2 Connects input common to internal ground.
Required for legacy operation.
Default:Installed
JP3 Connects current loop receiver to internal
COM3:RX. I.e. selects interface to CL. Must be
removed if RS232 is to be used.
Default:Installed (Use current loop)
1Hz
4Hz
Automatic weighing mode errors can generate a two digit error code.
The code will be display instead of the weight result. A list of
available error codes is found in the Flintab standard protocol
description. The status information log can also be viewed to read a
verbose description of the error.
12 Technical specifications
12.1 Electrical
General
Display 480x272 High visibility colour TFT with LED
backlight and resistive touch-screen.
Interfaces Standard: RS232/RS485 (2W or4W),
Ethernet, USB, opto-isolated I/O (3I, 4O).
Option: Fieldbus, RS232x2
Power supply 12VDC (1.5A,18W ) EIAJ-5320 Class IV
Load cell interface
Topology 1-4 channels simultaneous sampling
Load 60Ω-1200Ω combined load on all 4
channels
Excitation 10VDC regulated, 2.5VDC biased (-2.5V -
+7.5V). Short circuit protection,
Sense Regulative (cable 6 wire + shield)
Input range 0.0 – 1.98 mV/V per channel
AD-conversion rate 28800x4/second, 5760x4/second available
Specifications
Accuracy class OIML III
Max. number of scale 10’000 – Compliant mode single interval
intervals 3x4000 – Compliant mode, triple interval
Signal dependant in non-compliant mode
Minimum verification 1µV
scale interval, e
Number of intervals 1, 2 or 3
Internal resolution 24bits/channel
Temperature range -10C° - +40C°
Relative humidity Max. 85%, non condensing
Zero drift Typ. 5 nV/C°
Linearity Typ. 0.00013 %
Temp drift Max. 5ppm/C°
Warm-up time Typ. 5 min. (300 s)
12.2 Mechanical
47-20-01 (panel mount)
240
Recommended
Side view clearance
Connectors+cables
110 (70)
Recommended 100
panel cut-out:
USB-A
USB-B
12VDC
Fieldbus (COM2)
ETH0
222x102 mm
I/O COM1
CAL
220
\\F1\Avd\85\Produkter\VIKTINDIKATOR\Handhavande\47-20\4-54935 rev 1-7 Instruction 47-20 basic 120628.doc
Page 202 (232)
Flintab AB Tel 036-314 200 Fax 036-18 50 79 Vat No (Org.nr) SE556208398901
Kabelvägen 4 mail@flintab.se www.flintab.se Bankgiro 349-2170
553 02 JÖNKÖPING Postgiro 85 73 20-6
INSTRUCTION 4-54935
2012-06-28 / Tony Kübek Edition 1.7
185
Front view
224
74
Side view
(70)
Recommended
clearance
Connectors+cables
Rear view
no Navigate up
no Navigate down
no Save changes
no Navigate down
no Pause dosing.
Function buttons;
Button icon Calibration mode Function
required
• Power-on is not finalised (The weight indicator has not finished its start-up
sequence.):
Character
1 2 3
Power-on not finalised ‘!’ CR LF
• Zero-track/zero-set performed:
Character
1 2 3
Zero-track, -set performed ‘Z’ CR LF
’4’ 0x34 Respond with displayed weight value. Gross or net depending on tare
status. Will start continuous transmissions until a new request is
received.
’5’ 0x35 Respond with displayed weight value and include the stability status
byte. Gross or net depending on tare status.
’6’ 0x36 Respond with displayed weight value and include the stability status
byte. Gross or net depending on tare status. Will start continuous
transmissions until a new request is received.
’7’ 0x37 Respond with gross weight and include the stability status byte..
’8’ 0x38 Respond with gross weight value and include the stability status byte.
Will start continuous transmissions until a new request is received.
’V’ 0x56 Respond with weight indicator type and program version.
’M’ 0x4D Respond with scale max. capacity and one scale interval.
‘S’ 0x53 Responds with ‘S’<cr><lf> as non-automatic mode info.
‘D’ 0x44 Responds with ‘D’<cr><lf> if the indicator can switch back to
automatic mode. If this is not possible (automatic mode not enabled)
the indicator will respond with ‘S’<cr><lf> instead .
‘A’ 0x41 Same as “1” (displayed weight) but if weight indicator is equipped
with alibi memory a seven digit sequence number will be sent
accompanying the weight. I.e. first the sequence number will be sent
and then the weight. The weight is also saved in the alibi memory. See
section 6.1 how to retrieve a stored weight from alibi memory. An
error code can be sent instead if saving is not possible. See section
A.B.4.
‘G’ 0x47 “G” Same as “3” (always gross weight) but if weight indicator is
equipped with alibi memory a seven digit sequence number will be
sent accompanying the weight. See “A” telegram above.
‘Lxxxx - If weight indicator is equipped with alibi memory this telegram
xxx’ request a retrieval of a previously stored weight from the memory.
The seven ‘x’s should be replaced with the seven digit sequence
number of the wanted weight. If the weight is found it will be
displayed on the display during three seconds, if the weight is not
found only a minus sign will be shown instead.
If equipped with alibi memory (or ‘dummy’ sequence number is enabled in no-
alibi version), the weight indicator first sends the seven or nine (if ID is
enabled) digit sequence number:
Without ID number Character
1 2 3 4 5 6 7 8
Sequence number: 7 digits Sp
After the sequence number the weight indicator will follow with the ‘normal’
weight message according to table below. If the request was “1”,”2”,”3” or “4”
then weight indicator will respond one of these message only ( without
sequence number ):
Numbers slanted ‘1’ with–out Character
sequence number .
Regular is with sequence number 1/9 2/10 3/11 4/12 5/13 6/14 7/15 8/16 9/17
and without ID, increase by two if
ID is included.
Weight value with decimal ‘B’ Sp -/Sp 5 digits + dp
point:
Weight value without decimal ‘B’ Sp -/Sp 5 digits
point:
The weight indicator will then end the message with one of the following
terminators:
If the weight is outside weighing range, the overload message is sent instead:
Character
1 2 3 4
Overload message ‘O’ ‘L’ CR LF
Second example weight indicator is equipped with alibi memory; the scale is in
stable state and inside weighing range. Weight indicator is also set-up to include
unit (kilo) in the response (example weight 1.50 kg and sequence number 105).
• The weight indicator receives the message:
Character
1 2 3
Register/request displayed weight: ‘A’
Character
9 10 11 12 13 14 15 16 17 18 19 20 21 22
(continued) ‘B’ Sp Sp ‘0’ ‘0’ ‘1’ ‘.’ ‘5’ ‘0’ Sp ‘k’ ‘g’ CR LF
The weight indicator will then end the message with one of the following
terminators:
• The result of weighing is sent automatically as soon as the parcel leaves the
scale. The synchronisation with the parcel and communication is controlled
by the photocell interface (or an equivalent external signal).
• The weight indicator receives the message “(“‘hold weight in memory’
during, or just before a data collection sequence. The weight indicator will
then hold the transmission until the message “)” ‘retrieve weight from
memory’ is received or until three seconds has passed since last weighing
sequence. The message “)” must be received during the three seconds after
an ended weighting sequence else an error code will be transmitted instead.
The synchronisation with the parcel is still accomplished by the photocell
interface but the host controls when the result is sent.
Following messages (ASCII character) can be received:
• ”D” Sends ”D”, CR, LF as in motion info ( also telegrams “1” to “8” ).
• ”(” Disable spontaneous sending of weighing result ‘hold result in memory’.
I.e. if this message is received just before or during a data collection
sequence the weight indicator will not spontaneously send the result when
sequence is finished. The weight indicator will instead temporary store the
result in memory during three seconds after ended sequence. To retrieve the
weighing result during these three seconds send the “)” message.
A.B.3.4 Messages sent in automatic mode after data collection has ended
In automatic mode, when data collection stops, the weight indicator either
automatically sends the result or sends the result when the command “)” is
received.
The weight message from the weight indicator can have some different
compositions depending on current set-up.
• The inclusion/position of decimal point will follow the display.
• The inclusion of weighing unit will depend on setting.
• If equipped with alibi memory, the weight can be preceded with the seven
digit sequence number. It is also possible to set-up an weight indicator
without alibi memory to send an ‘dummy’ sequence number containing
only 9’s, i.e. ‘9999999’. See section 8.4.1.2.
• A 2-digit ID number can also precede the sequence number. See section
8.4.1.2.
If equipped with alibi memory (or ‘dummy’ sequence number is enabled in no-
alibi version), the weight indicator first sends the seven or nine (if ID is
enabled) digit sequence number:
Without ID number Character
1 2 3 4 5 6 7 8
Sequence number: 7 digits Sp
After the sequence number the weight indicator will follow with the ‘normal’
weight message according to table below. If the weight indicator is not equipped
with alibi memory the message will start with this table.
Numbers slanted ‘1’ with–out Character
sequence number.
Regular is with sequence number 1/9 2/10 3/11 4/12 5/13 6/14 7/15
and without ID, increase by two if
ID is included.
Weight value with decimal Sp 5 digits + dp
point:
Weight value without decimal Sp 5 digits
point:
Continued on next page
Parcel flow
Photocell,between
infeed and scale belt.
Parcel
• Parcel front-end is just leaving the scale belt. The weight indicator will
update the display with parcel weight. The weight will also be sent on the
communication port according to table below:
Parcel flow
Photocell,between
infeed and scale belt.
Parcel
Character
1 2 3 4 5 6 7 8 9
‘In-motion’ weight Sp ‘0’ ‘0’ ‘1’ ‘.’ ‘5’ ‘0’ CR LF
Note! If a new parcel is introduced on the scale belt before the previous has
started to leave. The weight indicator will end the current weighing sequence
and send the result immediately. In this case the weighing time can be to short
and an error code will be transmitted instead. Therefore care should be taken
that parcels are separated/spaced with front-end to front-end the same distance
as the scale length. Contact Flintab if smaller spacing is wanted.
Second example: The weight indicator includes alibi memory, is set-up to
include unit ‘kg’ in the weight message and the host sends messages “(“and “)”
to synchronise the communication, further; the weight indicator does not send
an ID number preceding the sequence number. Example weight ‘1.50’ kg and
sequence number ‘105’.
• The parcel is introduced on the scale belt, as soon as the back end is on the
belt; the photocell input triggers start data collection sequence. The weight
indicator will show the letter ‘d’ on the display.
Parcel flow
Photocell,between
infeed and scale belt.
Parcel
• The weight indicator receives the message “(“ ‘hold result in memory’
during the weighing sequence.
Character
1 2 3
Hold weighing result in memory ‘(’
• Parcel front-end is just leaving the scale belt. The weight indicator will
update the display with parcel weight. The weight will not be sent on the
communication port.
Parcel flow
Photocell,between
infeed and scale belt.
Parcel
• The weight indicator receives the message “)” ‘get result from memory’ and
transmits the weighing result on the communication line
Character
1 2 3
Get result from memory ‘)’
Character
9 10 11 12 13 14 15 16 17 18 19 20
If the message “)” ‘get result from memory is received during the data
collection sequence or after the three second time-out period an error code will
be transmitted instead.
E04 Mode switching to non-automatic while data Operator switched off automatic mode during a weighing
collection was active. sequence.
E05 To few weight values accumulated during data The time between start and stop triggers was below
collection. minimum time.
E06 Zero has not been set. Scale was not zero when Scale must be unloaded at power-on and periodically
switching to automatic mode or the zero- during weighing when switching to automatic mode. See
tracking has not been active for a while. also section 8.2.7.
E13 Negative weight in automatic mode. Possible incorrect zero or weight to low.
E40 Weighing time to short. The time between start and stop triggers was below
minimum time.
E47 Incomplete weighing sequence Telegram “(“- hold weight in memory received but the
previous weight has not been requested by telegram “)”-
get weight from memory.
E48 Request “)”- get weight from memory received Telegram “)”-get weight from memory is received too
before weighing sequence was finished. early, before the current weighing sequence is finished.
E49 Request “)” – get weight from memory received Telegram “)”-get weight from memory is received too late,
when no weight is present in memory. after the result from the last weighing sequence is
discarded ( normally three seconds ).
Totalizing printouts:
SUM: 59.01 t
SUM: 4026 kg
LOCATION 123;ABC12345AB;1000kg
Weight
Fixed text