Specifications

18 RSLinx – Training Guide
Application Notes and Suggestions
• With a ControlLogix 5550, unsolicited messages work on only an Ethernet
network or a DH+ network.
• To receive unsolicited DDE messages from a processor through a DHRIO
module, and through an ENET module over an Ethernet network, select your
DDE topic from the DDE/OPC Topic Configuration dialog box. Then, select
Advanced Communication, click Remote, and manually enter the Remote Link ID
of the DHRIO channel through which the message is being sent.
• Newly created DDE topics default to 20 for Limit Maximum Packets. This makes
the updates more symmetrical for the group of optimized packets for each topic.
For the same functionality on older DDE topics, set Limit Maximum Packets on
the DDE/OPC Topic Configuration dialog box, Data Collection tab to 20, or the
best value for the PLC and access method.
• When configuring DDE/OPC topics to receive unsolicited messages from a
ControlNet device, from the DDE/OPC Topic Configuration dialog box, select the
Advanced Communication tab and select Local route for Local or Remote
Addressing.
• To ensure that unsolicited messages coming to RSLinx work properly when
setting up a DDE topic to a remote processor via ControlLogix Gateway, set the
Remote Link ID to match the Link ID of the remote module (such as DHRIO).
• Block reads and writes do not work with user defined types -
(ControlLogix 5550).
• In Windows NT, the PIC/AIC+ and the DF1 Polling Master / Slave drivers (with
RTS control enabled only) drivers need their own serial driver (RSSERIAL.SYS
rather than SERIAL.SYS) and cannot therefore share an interrupt with another
serial device.
• When using auto configuration on a 1770-KF2/KF3 device, you must set the
Station Number to that of the KF2/KF3 before clicking Auto-Configure.
Otherwise, Auto-Configure tries to detect the device at the currently selected
station, and if the device is a PLC, Auto-Configure configures to the PLC rather
than the KF2/KF3.
• If you restore a Windows NT configuration, and you have a configured KTC(X) or
PCMK driver, you must reboot the computer to start the driver.
• After the first time you configure a PCC driver in Windows NT, you must reboot
your computer before using the driver.
• When you install RSLinx, DTL32.DLL remains in the system directory if it is
locked by another application.
• You must have Windows NT Administrative privileges to install RSLinx and/or
configure RSLinx drivers.