ControlLogix, DASABCIP, and Wonderware issues

[defcon.klaxon]

Hi guys,

I'm working with my AB ControlLogix PLCs and my task today has been trying to get the PLC to talk to my Intouch HMI. I started out with RSLinx but found out it doesn't support DDE, so I began down the path of installing DASABCIP. I've got it installed but can't seem to get everything lined up for communications, and after triple/quadruple checking everything and lots of Google searching, I thought it would be worth it to post the question here.

So here are screen grabs of SMC, and of InTouch:

http://imgur.com/a/46jTA

I'm working with a LOGIX5572 in a 13 slot chassis with an 1756-ENBT Ethernet/IP module. The IP address is set to 192.168.1.199, and BOOTP has been disabled. I can ping the PLC from my desktop PC, and with RSLinx I can see the data just fine so I think the network settings are correct. My Device Group under the LOGIX5000_CLX_000 object is "ABTEST" and I've included a screen grab of that Access Name defined in InTouch, as well as the discrete tag I'm trying to observe in a simple test screen.

What happens is that I've put an ArchestrA graphic as an indicator of the boolean state of the tag, and when I go to runtime the graphic will either have the clockface/"initialzing" status, or downright red x/"bad" status.

At this point I've pretty much exhausted everything and I don't know where the error could be. If you guys wouldn't mind taking a look I'd certainly appreciate it!

 

[defcon.klaxon]

UPDATE:

I talked to a Wonderware service rep and it looks like things are squared away. A couple things to note:

1. I did not need the "New_PORT_END_000" under the Backplane, just the LOGIX5000 oject.
2. Once that was fixed, we took the DAServer out of service, then brought it back. Then, it was fixed. I tried this and of course it didn't work, but for some reason when Wonderware Tech Support was on the line, it was successful.
3. We tried using the WWClient and while that was helpful to determine connectivity, we noticed that it has a character limit when you query statuses and with the full address of the bit I was trying to query (Program:MainProgram.DiscreteTest), it was one character too long for the WWClient and it wouldn't properly query the tag. If we mapped the tag in the DAServer as a Device Item, it would then respond properly; I only mention this in case someone comes across this thread when troubleshooting, so that they don't have the same issue we did.