Common FAQs Automation Networks

First change the station node and then the baud rate. The node has to be available and the baud rate has to be the same that the network is working with.

DH+ speeds:
57.6
115.2
230.4

Here is the walkthrough:

1. 1. 1. Open RsLinx.

2. 2. 2. Go to Communications menu…

3. 3. 3. Select Configure drivers…

4. 4. 4. From the drop-down list select EtherNet/IP Driver, and then Add New…

5. 5. 5. Select a Name for the driver and click OK.

6. 6. 6. On the EtherNet/IP settings window select: Browse Remote Subnet.

7. 7. 7. If your ANC-120e Is on 192.168.137.2 address, then select the IP Address 192.168.137.0 to scan all the subnet. Subnet Mask > 255.255.255.0. Then click Apply and OK.

8. 8. 8. After adding the driver successfully select CLOSE from the Configure Drivers window.

9. 9. 9. You will be presented with the new added driver (we call ours AB_ETHIP-1). And at CH A (CHANNEL A) you will be able to see the SLC or PLC.

You have to put in node 00 (double 00) on the HMi configuration page rather than just 0.

Check the IP address of the device you are giving the address to in the HMI tab and confirm you have not a copied IP address. Also confirm that the node you have selected is not being use by the ANC and that the node it is the correct node of the SLC or PLC.

When you start to have communication, and the program start to fail or is not letting you interact with it, restart the computer.

Are 200 bytes or 50 Integers (4 bytes = 50 Integers). When you handle in your program more than 200 bytes in a read then this kind of error could appear.

The ANC-100 and the ANC-120e doesn’t have the option to see beyond its same network. In this case for example, the racks (elements) that are connected to the PLC5/80 are behind a device, it’s like another gateway, so the ANC-120e or the ANC-100 are not able to go beyond. It doesn’t matter if they have another baud rate.

The racks are devices that need specifically PLC5s for them to work. They can’t be connected directly to the DH+ network.

The user is not able to see the PLC or SLC.

One suggestion Is to try different drivers or try a different virtual machine or use a computer with windows xp sp3 but without a virtual machine.

Update**

1. 1. 1. The VM has to be set to NAT, so the adapter appears properly in Linx on both the Win7 and WinXP VMs.

1. 1. 1. That the Windows 10 OS has to be refreshed unplugging and plugging again the unit so any conflict with the drivers or the Windows registry can be updated and eliminated.

1. 1. 1.  Rslinx 2.54v had a bug reported in a Rockwell documentation, so please try with a newer version of Rslinx.

Yes, please review the appnote: RSLinx enterprise configuration and the ANC-100e Application Note

Yes, but it depends. You can send instructions from the Compactlogix to the SLC5/04, but not the other way. The Instructions are sent from the ethernet side to the dh+ side, but not from dh+ to ethernet.

The instruction can be sent FROM the Compactlogix to the SLC504 to get information from it, but the SLC504 cannot send an instruction to the Compactlogix.

About the question of how am i being able to program the SLC from ethernet? that is because a “conversation” is initiated from the ethernet side to the plc, then that same conversation is used to receive/send data from/to the SLC.

So the SLC can retrieve data from the Compactlogix or Controllogix if the Compactlogix or the Controllogix sends to the SLC the MSGs instructions that it can get data from them. But the SLC can’t send them instructions or MSGs because the ANC-100e or the ANC-120e can’t translate the instructions from DH+ to Ethernet.