ProSoft Technology ProSoft i-View - Manual (Page 21)

ProSoft i-View ♦ Mobile Process Monitoring and Control Application Data Source Files
Version 2.0.2 User Manual
ProSoft Technology, Inc. Page 21 of 106
September 29, 2011
The following memory areas and prefixes are supported.
PROTOCOL AREA PREFIX REMARKS
Modbus TCP/IP I: Input Discrete (read only)
C: Coil
IR: Input Register (read only)
HR: Holding Register
To access Coil number 10, specify C10. To
access Holding register 1, specify HR1.
Individual bits in HRs can be accessed for
reading or writing using a dot notation. For
example, HR1.3 would refer to bit 3 in HR1.
EIP/Native
(Allen Bradley) TAG (deprecated, do not use) Actual symbolic tag name is given in column
A. See Variable Names (page 16). However,
"TAG" must still be specified in column C.
EIP/PCCC
(Allen Bradley) O0: Outputs
I1: Inputs
S2: Status
B3: Binary
T4: Timer
C5: Counter
R6: Control
Nn: Integer
Fn: Floating Point
STn: String Tags are specified by file type, file number and
offset in the regular way. Individual bits in
words can be accessed using the usual slash
notation.
Examples:
B3:5 would access word 5 on file 3 of type B
N7:0 would access value at position 0 in N7
file
N7:0/3 would access bit 3 in N7:0
Accessing Data Types Longer Than One Register
For data types requiring more than one register or memory location, the lower address in
their range must be specified. For example, a variable of type DINT addressed by HR100
will use HR100 and HR101 because 2 Modbus registers (16 bits) are required to
accommodate the complete variable (32 bits). Integrators must be aware of this to avoid
overlapping tag values. This applies to all protocols except EIP/Native.
Accessing a Register as a BOOL
It is possible to specify a BOOL type for a register or memory location even if it is
not meant to hold a BOOL. For example, you specify on a row that HR1 is a
writable BOOL. In this case, ProSoft i-View will use a switch control for that row,
and will write a value of one (1) or zero (0) to the register depending on user
interaction on the switch. This applies to all protocols except EIP/Native
.
EIP/Native does not allow a non BOOL PLC Tag to be treated as BOOL due to
the strict type checking that this protocol encourages. You can use the ‘bool’
style instead to force the same effect.