1.When trying to communicate with a device, users must be sure that it is not communicating with another application. It is common that users configure a device with RS Linx and then do not deactivate its communication with that PLC when finished communicating.

2.In case of trying to read or write a non-existent element, the system indicates a communication error. This also happens in case of trying to read a Block with more Words than the specified file contains.

3.Users can only configure a Tag to communicate with a bit if the sub-element of a file is equal to 0 (zero), because when configuring the N2 or B2 parameter to access that bit, this Driver considers that this sub-element is equal to 0 (zero). If users want to retrieve these bits and the sub-element is different from 0 (zero), it is advisable to configure a Tag to retrieve the entire data and then access these bits with the existing Elipse E3, Elipse Power, Elipse Water, or Elipse SCADA functions.

4.When trying to read or write directly to inputs and outputs, that is, to O0 and I1 files, depending on the model and version of a device, there may have some problems in the number format for addressing, generating communication errors that are registered in the log with a message "AB_command returned error in status = 10!". It is advisable to map inputs and outputs to integers, as described in the article Address issues when accessing input and output files (O0 and I1) with Allen-Bradley ABDF1 Driver on Elipse Knowledgebase.

5.When trying to communicate with a MicroLogix 1100 device using a local Ethernet port and communication fails, change the PLC Type configuration to MicroLogix 1500. Some firmware versions of that device require this configuration on this Driver.