Hardy HI 3010 Filler/Dispenser Controller - Manual (Page 90)

HI-3010 Filler/Dispenser/IBC 74
Service Manual
Local Output
Outputs interface with indicators, motor starters, solenoids,
and other actuators connected to the HI 3010. Remember
Outputs can be a Destination and a Source. (See Destination
definition in the Glossary of Mapping Terms)
FIG. 6-38 OUTPUT FUNCTION
• Each output has an address associated with
it.
• This address describes the physical loca-
tion that the output device is connected to.
• This address also describes the data table
location where the desired state of the out-
put device is stored.
• The desired state of each output is trans-
ferred from the output image table to the
output point during the I/O Scan every 1/
55th of a second. (See Fig. 6-38)
• For Example: Relay out #3 = FAST FILL
means assign the desired state (Open (0) or
Closed (1)) located at the Fast Fill Address
in the input image table and move it to the
Relay out #3 address in the Output Image
Table. (See Fig. 6-38)
Volatile and Non-Volatile Memory
It is important to understand that the data stored in the Out-
put and Input Image Tables is stored in volatile memory.
This means, when you power off you lose the data. The
Addressing I/O (Mapping) is saved in non-volatile memory
and is not lost when you power off.
A Definition of Mapping
Mapping (Addressing I/O) is the same as using an Assign-
ment Statement. The Destination is located on the left hand
side of the equals (=) sign and is a memory address (vari-
able). The Source is the data located on the right hand side of
the equals (=) sign at a memory address. So when you refer
to the right hand side of the Assignment Statement you are
referring to the data only and not the address even though the
address is listed.
• Memory Address (Variable) = Data (Val-
ues, states)
The equals (=) sign assigns the data on the right side of the
Assignment Statement to the Memory Address on the left
side of the Assignment Statement.
This is exactly what you are doing when you map a source to
a destination.
The things that can be mapped are organized into Input
Image Tables and Output Image Tables, which are arrays of
variables (i.e. memory locations of a certain size based on
the type assigned to the variable) with addresses where data
is stored.
A table is called an “output” image table if the items in the
table are permitted to be on the left hand side of an Assign-
ment Statement. The Output variables are also further identi-
fied by the first two letters of the variable:
• HO - Hardy Output Image Table
• DO - DeviceNet Output Image Table
• RO - RIO Output Image Table
• CO - ControlNet Output Image Table or
Profibus Output Image Table.
NOTE: You won’t use ControlNet and Profibus at the
same time so they can both use the same tables.
If the items in the table are only permitted on the right hand
side of an Assignment Statement, we call it an “input” image
table:
• HI - Hardy Input Image Table
• DI - DeviceNet Input Image Table
• RI - RIO Input Image Table
• CI - ControlNet Input Image Table or Pro-
fibus Output Image Table.
For example, the digital inputs on the Filler/Dispenser are
found in an input image table, as are the items in the Devi-
ceNet input image table.
The HI 3010 scans through the I/O image tables 55 times a
second and reads any values that are contained in the tables.
If there is nothing stored in the tables the controller does
nothing with it. If there are state values or other values stored
in the tables, the firmware processes the data and outputs it
to an output device or the screen.
Local Mapping Example
Local Mapping Output
You hardwired a Valve Actuator to Output Relay #1. When
the Filling process gets an OK to Fill the Filler changes the
Fast Fill value (which is stored in the Input Image Table)
from 0 to 1 which means, close the output relay to begin a
fast fill. You need to map the Fast Fill to Output Relay #1.
Data Table
0 1 2 3 4 5 6 7
0
1
2
3
4
5
0
1
2
3
Output
Output Device
Address
0/3
Input Image
Output Image