I am having trouble getting Wonderware Intouch version 10 to communicate to a Allen Bradley SLC 5/05 processor. I have the software loaded onto a Windows XP Professional platform. I have been able to load the "Allen Bradley Ethernet Direct" IO Server from the Device Integration Products CD.

I have the IO server configured for the following:

Topic Name: ABPLC Host Name: 192.171.51.7

PLC Family: SLC-500 Connection Type: Local

Polling: Default Values

______________________________________________________________________

Within the Access Names setup within the InTouch Windowmaker Configuration - This is the following configuration:

Access: ABPLC Node Name: Blank

Application Name: C:\Program Files\Wonderware\IOServer\ABTCP\abtcp Topic Name: ABPLC

Protocol: DDE {I have tried both} When to Advise Server: Advise only active items

______________________________________________________________________

Any information that will get these two communicating would be great.

Ok, I'm not where I can access my wonderware PC so I will try some of this by memory (thats a disclaimer...).

First step with this is to ping your PLC. Make sure you have a good connection. open up the command prompt and type: ping 192.171.51.7 (I assume that is the address of your PLC)

You should receive replies back. If not stop and figure out why both are not communicating. Let me know if this is an issue.

I think there is a problem with your access name appplication setting. I dont think you give it the whole path, just the name of the driver (abtcp.exe). Try that and see if it works. You may not need the ".exe" I would definately choose suitelink for the communication protocol. "Advise only active items" means you will have to have a window open that polls the PLC to see anything happen. If you open up your driver window, you should see the items being polled listed. you can also open up the wonderware logger to see any errors or notifications listed.

I think your problem is in the application name. Here's the deal... That is not the i/o driver I would use to talk with the SLC5/05. I would use the newer DASABCIP driver. It also can talk with the logix and micrologix platforms. It is a little more invloved to install but also more organized on the hardware interfacing. To get started, you would install the DASABCIP driver. Then open the Software Management console (SMC) to configure. At the top you will find the DA servers and you will need to add a new configuration for the SLC you want to communicate with. The help is pretty good on this. You should see something like ArchestrA.DASABCIP.4 on your DAserver list. expand it to find the global parameters and select configuration. right click and add a port. name it something useful. Right click on that object and add the SLC500_EN_000 object. click on the configuration and set it up for your processor. Click on the device groups tab and add a device group (or several if you want different polling speeds). You can start off by adding only one: ABPLC like you have in your current access name. You dont need to add any items as yours will pass through from intouch. Go back to your access name and change the application to DASABCIP and you should be good.

Let me know if you are still having issues.

Issue resolved: Problem was with the type of IO server that was loaded. I had loaded the "ABTCP IO Server 8.1" from Device Integration Disk 1. You were right, the correct driver is in fact "DASABTCP 1.5 SP1" which is located on Device Integration Disk 2. The setup was a little more involved but I have taken good notes to reference for future setups. Thank you very much for your help.