Hi All,
While I appreciate the following problem has a lot variables, and as such, we are currently proposing alternative solutions to the end user, should anyone be able to shed any light on what I've experienced I would be most grateful!
I was tasked to carry out some expansion on an existing system provided by another vendor, the system basically consisted of;
Taking all this, and more, into consideration, it did sorta work!
Anyway, in order to expand, we need to add more CNBR's into racks already containing CNBR's. Rockwell, in it's infinite wisdom has decided that Series 'D' modules are no longer available, and we could only have Series 'E'. However, this would also mean a full firmware upgrade to redundancy pack V15.X, and an upgrade of RSLogix to V15 in order that we could mix Series 'D' & 'E' in same chassis.
While this was a pain, it went ahead, trouble free, I re-scheduled the network and all fine, expansion installed, all tested, faster, no problems....Until I switched the SCADA back on!
The SCADA would NOT communicate with the PLC's, no modifications had been made to the SCADA or communication paths or the tags, and RSLinx continued to see the whole network.
After a couple of days, and nights, nights with an anxious client on my back, and numerous Wonderware tech support I was advised to drop FSGateway in favour of DASABCIP and install 1756-ENET cards in the racks, which I did, still no joy.
Wonderware tech support arrived on site, immediately said go back to FSGateway, spent two days messing around then left site with it still not working.
I then took the decision to roll-back all AB PLC firmware to redunancy pack V13.x and remove the expansion, re-schedule the network, boot everything up and hey-presto, it all works again!!!
The outcome to date is...
WonderWare do not believe it is their problem and do not intend to investigate, they claim it must be an AB issue.
AB do not believe it to be their problem, and say it is WonderWare who is at fault.
We have currently recommended to the client that in the short term, we fully audit the system and clean up the comms, and long-term, replace ControlNet with redundant Ethernet, and InTouch with RSView.
I just want to know if anyone else has had a similar issue with CLX 15.X and InTouch, and if so, what has been found please.
Any and all help would be appreciated. Thanks.
Shaun
While I appreciate the following problem has a lot variables, and as such, we are currently proposing alternative solutions to the end user, should anyone be able to shed any light on what I've experienced I would be most grateful!
I was tasked to carry out some expansion on an existing system provided by another vendor, the system basically consisted of;
- Multiple redundant ControlLogix L55 V13.X processors (c/w SRM's & CNBR's - Series 'D')
- Redundant ControlNet network
- Dual redundant InTouch V9.0 SCADA servers (kinda hot-standby as far as DRaX will allow) using FSGateway 1.5 OPC through RSLinx 2.51 and PCICS cards straight onto ControlNet.
- Multiple client SCADAs on Ethernet.
Taking all this, and more, into consideration, it did sorta work!
Anyway, in order to expand, we need to add more CNBR's into racks already containing CNBR's. Rockwell, in it's infinite wisdom has decided that Series 'D' modules are no longer available, and we could only have Series 'E'. However, this would also mean a full firmware upgrade to redundancy pack V15.X, and an upgrade of RSLogix to V15 in order that we could mix Series 'D' & 'E' in same chassis.
While this was a pain, it went ahead, trouble free, I re-scheduled the network and all fine, expansion installed, all tested, faster, no problems....Until I switched the SCADA back on!
The SCADA would NOT communicate with the PLC's, no modifications had been made to the SCADA or communication paths or the tags, and RSLinx continued to see the whole network.
After a couple of days, and nights, nights with an anxious client on my back, and numerous Wonderware tech support I was advised to drop FSGateway in favour of DASABCIP and install 1756-ENET cards in the racks, which I did, still no joy.
Wonderware tech support arrived on site, immediately said go back to FSGateway, spent two days messing around then left site with it still not working.
I then took the decision to roll-back all AB PLC firmware to redunancy pack V13.x and remove the expansion, re-schedule the network, boot everything up and hey-presto, it all works again!!!
The outcome to date is...
WonderWare do not believe it is their problem and do not intend to investigate, they claim it must be an AB issue.
AB do not believe it to be their problem, and say it is WonderWare who is at fault.
We have currently recommended to the client that in the short term, we fully audit the system and clean up the comms, and long-term, replace ControlNet with redundant Ethernet, and InTouch with RSView.
I just want to know if anyone else has had a similar issue with CLX 15.X and InTouch, and if so, what has been found please.
Any and all help would be appreciated. Thanks.
Shaun