User guide
eWON 500-2001-4001-4002 User Guide - IO Servers Configuration
eWON 500®2001®4001®4002® Version 4_3_0 - User Guide - 10/5/05 - ©ACT'L sa - Page 93
Three topics can be used for the IO Server. These topics are used to give a common property to a group of DF1 Tags like:
• Enable/Disable
• Poll rate
• Destination Device Type and Address
6.6.2.2.1 DF1 : serial link
The Destination Device Type and address is always of type :
• SLC500-x (where x is the address of your Device (0'254))
i.e.: Topic A Destination = SLC500-1
6.6.2.2.2 DF1 : Ethernet routing
Thanks to the ABLogix IOServer, eWON is now able to poll data on SLC500 devices by its ethernet link. Even SLC500 connected behind your
ControlLogix Network became available for polling.
With these use of DF1 IOServer, the Serial config can be left unconfigured (baudrate=disabled), only one Topic enabled is required.
You need to use the same Device syntax than in ABLogix IOServer.
IP Address, Port, Link.
•
IP Address = address on your Ethernet network (i.e.: 10.0.0.50)
•
Port = value from 1 to 3 representing: 1 = Backplane, 2 = Channel A, 3 = Channel B
•
Link could be:
¤ Slot: representing the Slot on the Backplane (0=CPU)
¤ Node ID: value from 0 to 99 (for ControlNet and DH+)
¤ IP address
To reach a SLC500 with Ethernet address 10.0.0.60:
Topic A Destination =
10.0.0.60
To reach a SLC500 connected behind a ControlLogix :
Topic A Destination =
10.0.0.80,1,3,2,45
• 10.0.0.80 = IP address of the ControlLogix
•
1 = BackPlane
•
3 = Slot 3 (DH+ card)
•
2 = Channel A (of the Card present in Slot 3)
•
45 = NodeID of the SLC500 (in the DH+ network)
Topic configuration item Description
Topic enabled Enables or disables polling of all the Tags in the topic
Destination Device Type and
Address
The Destination Device Type and Address is a global parameter for all the Tags of the topic.
See below for the Device Address syntax. If an address is specified here,
it will replace (overload) the address defined Tag by Tag
Poll rate
Defines the refresh rate of the Tag name. In a complex application, we can imagine that some
Tag name must be refreshed every second – typically for digital input - and other every minute
– typically: temperature-
Table 64: DF1 topics configuration setup