wildswing
Member
Hi,
Sorry, but I thought I had posted this before but could not find it. I appologize for the possible duplication. If you know the whereabouts of my original post, please post a link. Thanks.
Until recently I've been running InTouch v9.0 P2 and DASABCIP v3.0 P1 on XP Pro SP2. Itouch was upgraded to v9.0 P3 last week. My nodes are grouped into pairs, each running the same app. Each Intouch pair talks to a pair of AB PLC5s via one of two a ControlLogix ethernet/dh+ bridges consisting of an ENBT and two DHRIO modules. I have 4 apps, so 4 pairs of Intouch nodes with 4 pairs of PLCs. The 57k DH+ networks are separate although each connects to one of the two DHRIO modules in each of the two bridges. They are still logically separate. The following pictures may clarify that...
6 of 10 HMIs are connected to the same switch. The last 4 are connected to another switch in another part of the facility and the 2 switches are connected with a gig fibre connection. Tag counts in each app range from 1600 to 2400. Our new IT department has declared that all Ethernet is to be V-LANed. The 4 nodes are on a V-LANed switch shared with one general pc and printer. The entire switch to which the 6 are connected is set up for process control ip addresses. Sorry, I'm not very fluent in IT talk.
Ocassionaly we find that an IO discrete tag's item (bit in plc) is stuck, that is, is ON all the time where it should be off. The Intouch buttons that activate these tags are set as direct acting. It's as if the initial ON (1) makes it to the PLCs data table but the subsequent OFF (0) gets lost somewhere. I have no idea if this is a WW or AB issue.
The problem began when we upgraded from IT v7.11 with KT card IO servers on NT4 to v9.0 P2 on XP Pro SP2 with DASABCIP 3.0 P1. This never happened back in the KT card days even though each node polled the two PLCs independanly (redundant and doubled the traffic but it worked fine). We thought the problem was isolated to one particular set of nodes. We knew we had network traffic volume issues with that pair (expanded to 4 IT nodes) that was experiencing the stuck bits.
We changed that Intouch app to read from only one node's DAServer in that group of 4, thereby reducing the DH+ traffic to 1/4 of what it was when each node talked to the PLCs independantly. Not only did that speed up update time significantly but the stuck bit issue became much less frequent but not entirely gone. It still happens every few weeks.
I've gone through this with tech support and have applied their hotfix to ITv9.0 P2 to all my apps and nodes where I added "ForceWriteForDiscreteIOTags=1" to the app's ini file and view's intspt.dll was updated with a new version dated 2/18/2005 3:54 pm. Even then it still happens occassionaly. WW tech has since suggested applying Intouch patch 3, which I did last week, but it happened agian the other day.
We've found a stuck bit on another of the apps so it's not isolated to the 4 node/2 plc system I described earlier.
Is anyone else running into this? I have no idea how do I figure out what's causing this? Your assistance would be greatly appreciated. Thanks in advance.
Sorry, but I thought I had posted this before but could not find it. I appologize for the possible duplication. If you know the whereabouts of my original post, please post a link. Thanks.
Until recently I've been running InTouch v9.0 P2 and DASABCIP v3.0 P1 on XP Pro SP2. Itouch was upgraded to v9.0 P3 last week. My nodes are grouped into pairs, each running the same app. Each Intouch pair talks to a pair of AB PLC5s via one of two a ControlLogix ethernet/dh+ bridges consisting of an ENBT and two DHRIO modules. I have 4 apps, so 4 pairs of Intouch nodes with 4 pairs of PLCs. The 57k DH+ networks are separate although each connects to one of the two DHRIO modules in each of the two bridges. They are still logically separate. The following pictures may clarify that...
6 of 10 HMIs are connected to the same switch. The last 4 are connected to another switch in another part of the facility and the 2 switches are connected with a gig fibre connection. Tag counts in each app range from 1600 to 2400. Our new IT department has declared that all Ethernet is to be V-LANed. The 4 nodes are on a V-LANed switch shared with one general pc and printer. The entire switch to which the 6 are connected is set up for process control ip addresses. Sorry, I'm not very fluent in IT talk.
Ocassionaly we find that an IO discrete tag's item (bit in plc) is stuck, that is, is ON all the time where it should be off. The Intouch buttons that activate these tags are set as direct acting. It's as if the initial ON (1) makes it to the PLCs data table but the subsequent OFF (0) gets lost somewhere. I have no idea if this is a WW or AB issue.
The problem began when we upgraded from IT v7.11 with KT card IO servers on NT4 to v9.0 P2 on XP Pro SP2 with DASABCIP 3.0 P1. This never happened back in the KT card days even though each node polled the two PLCs independanly (redundant and doubled the traffic but it worked fine). We thought the problem was isolated to one particular set of nodes. We knew we had network traffic volume issues with that pair (expanded to 4 IT nodes) that was experiencing the stuck bits.
We changed that Intouch app to read from only one node's DAServer in that group of 4, thereby reducing the DH+ traffic to 1/4 of what it was when each node talked to the PLCs independantly. Not only did that speed up update time significantly but the stuck bit issue became much less frequent but not entirely gone. It still happens every few weeks.
I've gone through this with tech support and have applied their hotfix to ITv9.0 P2 to all my apps and nodes where I added "ForceWriteForDiscreteIOTags=1" to the app's ini file and view's intspt.dll was updated with a new version dated 2/18/2005 3:54 pm. Even then it still happens occassionaly. WW tech has since suggested applying Intouch patch 3, which I did last week, but it happened agian the other day.
We've found a stuck bit on another of the apps so it's not isolated to the 4 node/2 plc system I described earlier.
Is anyone else running into this? I have no idea how do I figure out what's causing this? Your assistance would be greatly appreciated. Thanks in advance.