Communication Settings
- Last UpdatedDec 17, 2021
- 2 minute read
To establish communication with a device, the associated Board, Port and I/O Device need to be configured in Plant SCADA Studio's Topology activity.
If you use the Express Communications Wizard to connect to a device, these settings will be automatically configured for you. If you need to manually configure them, you should use the values outlined below.
Boards
|
Field |
Value |
|
Board Name |
This field is user defined and is not used by this driver. |
|
Board Type |
The type of board. Enter SNMPII. |
|
Address |
Enter 0. |
|
I/O Port |
Leave this field blank. |
|
Interrupt |
Leave this field blank. |
|
Special Opt |
Leave this field blank. |
|
Comment |
This field is user defined and is not used by this driver. |
Ports
|
Field |
Value |
|
Port Name |
This field is user defined and is not used by the driver. |
|
Port Number |
Needs to be unique but is not used in this driver. |
|
Board Name |
Refers to the board previously defined. |
|
Baud Rate |
Leave this field blank. |
|
Data Bits |
Leave this field blank. |
|
Stop Bits |
Leave this field blank. |
|
Parity |
Leave this field blank. |
|
Special Options |
The .DBF file used to store additional tag data, for example, SNMPVARS.DBF. If there is no SNMPVARS.DBF in the project directory, the port will not initialize. |
|
Comment |
This field is user-defined and is not used by this driver. |
Note: From version 2.7.20.0, the SNMPII driver includes new functionality that prevents a device from going online if duplicate indexes exist. This functionality requires every index to be unique at all times. Unique indexes can be achieved by creating multiple ports and splitting the SNMPVARS.DBF into multiple databases (one for each respective port).
I/O Devices
|
Field |
Value |
|
I/O Device Name |
This field is user defined, and is not used by this driver. |
|
I/O Device Number |
Has to be unique, but is not used by this driver. |
|
I/O Device Address |
Use a valid IP address; format is: 'aaa.bbb.ccc.ddd community _string'. The community string has to be correct to enable access to the remote agent. The IP address can also be a device name known by the IP network (the network must have name resolving services running). The 'ping' program can be used to check that names are resolved to the correct IP address. The common community_string used is public; for example, "192.168.1.34 public" If you added your own community "PlantSCADA" into the SNMP service, the address would be "192.168.1.34 PlantSCADA". |
|
I/O Device Protocol |
Enter SNMPII. |
|
Port Name |
Refers to the port previously defined. |
|
Comment |
This field is user-defined and is not used by this driver. |