1 Create custom equipment in ApplicationBuilder
6 Modbus EIA-232/485
To...this kind of value...
use this type of integration point...
with this register type...
and a Modbus register address in this range...
1
0 or 1 Discrete (binary) input
BNI Di 1000119999
0 or 1 Input register Holding register
BNI BITn (where n 3000139999 or 4000149999
is a value 0-15 defined in points list)
0 to 65,535 Unsigned 16-bit integer Holding register
Write ANO Uint (not Unit) 4000149999
32,768 to +32,767 Signed 16-bit integer Holding register
ANO Sint 4000149999
Value with decimal point Holding register
ANO Float 4000149999
2
0 or 1 Coil Discrete (binary) output
BNO Do 19999
0 or 1 Holding register
BNO BITn (where n 4000149999 is a value 0-15 defined in points list)
1
If the Modbus register address (sometimes called register, address, code, or parameter) is not in this range, take the number given, then add 1 to coils; add 10,001 to discrete inputs; add 30,001 to input registers (sometimes given as 3X); and add 40,001 to holding registers (sometimes given as 4X).
The Modbus register address must be a decimal value. If you see the letters AF in register addresses anywhere in a points list, use a scientific calculator to convert these hexadecimal values to decimal values.
In rare cases, the number given is not in the range shown above and is greater than 9999. Type a 4 (function code) at the beginning of an input register or a 3 at the beginning of a holding register. For example, to read holding register number 313567, type 413568. (Add 1 as described in the paragraph above.)
2
*NOTE When defining Modbus TCP/IP address strings in ApplicationBuilder you can use generic placeholder text instead of actual data to make setup quicker. Then, in i-Vu CCN, you can use the Search/Replace feature to make global changes to the Modbus TCP/IP address strings rather than setting them up one at a time.
Each Float has 2 consecutive Modbus register addresses. Use the lower number in the integration point address.
Example: Building a custom equipment to talk to an ABB variable speed drive, with three identical ABB drives on the project, (and their Modbus TCP/IP slave addresses are 1, 2, and 3). They will all be using the same custom equipment file. The only difference is that the Modbus TCP/IP address strings will be set up differently, because the Modbus slave addresses of each drive will be different. So in your custom equipment file, instead of entering:
modbus://UINT/40001/1 (where 1 is the Modbus TCP/IP slave address of the ABB drive),
you could enter:
modbus://UINT/40001/devaddress
Later, in i-Vu CCN, you could use the Search/Replace tool on the Properties page>Network Points tab to replace the generic term "devaddress" with the actual Modbus TCP/IP slave address of the ABB drive (1, 2, or 3).