Skip to Content

Register Login

Industry Online Support

Technical Forum

Navigation

WinCC automatic change over between 2 LAN cards

Created by: Nil96 at: 1/12/2012 9:15 AM (8 Replies)

Rating (0)

Thanks 1

9 Entries

1/12/2012 9:15 AM	Rate (0)
Nil96 Posts: 325 Rating: (14)	Hi all, Need bit of advice on the following scenario : Got a PCS7 417-4-2H CPU and an ES/OS connected to it. The ES/OS PC has 2 LAN cards attached. Can we have WinCC detect and automatically change to either of LAN cards during failure of any one. Regards Nil
Nil96 Posts: 325 Rating: (14)
Suggestion To thank Quote Answer

1/13/2012 4:46 PM	Rate (0)
KhalDrogo Posts: 71 Rating: (12)	About automaticaly switching between two LAN cards, please try to consider a posibility of using *teaming: http://support.automation.siemens.com/WW/view/en/25413238 What exactly cards do you using? Are plant bus* and terminal bus separated in your system?
KhalDrogo Posts: 71 Rating: (12)
Suggestion To thank Quote Answer

1/14/2012 9:42 AM	Rate (0)
Nil96 Posts: 325 Rating: (14)	Hi KhalDrogo, Thanx for ur feedback. We are planning to use normal ethernet LAN cards, but the only criteria is that WinCC should be able to change over upon failure of any one. Regards Nil
Nil96 Posts: 325 Rating: (14)
Suggestion To thank Quote Answer

1/16/2012 12:53 PM	Rate (0)
CBo Gold Member Joined: 4/5/2006 Last visit: 10/10/2024 Posts: 917 Rating: (63)	Hi Nil96, Nil96 ...We are planning to use normal ethernet LAN cards... PCS7 connection with AS400-H is possible with CP16x3 only; by redconnect is possible to configure redundant connection in Netpro without addition effort by developer. Follow the link of previuos Tread with same topic Redundant connection between PLC and WinCC Redundant connection plc <-> WinCC Follow a link that explain why you shouldn't have the wizard in WinCC Explorer (you don't need maybe...just in case? Some time i see the option "create redundant connection" in dynamic wizard window and some time it disappears Hope can help regards

Suggestion To thank Quote Answer

1/16/2012 2:49 PM	Rate (0)
Nil96 Posts: 325 Rating: (14)	Hi CBo, Good to see u after quite some time. Anyway the only reason for me not choosing CP1613 and Red-Connect is "COST". Actually we are working on a project where in, there are 4 systems that are communicating to AS. Client wants dual redundancy for each of these systems and by all means we need 2 CP1613 and 1 Redconnect for each system. I was just wondering the price impact because of 8 nos of CP1613 and 4 nos of Redconnect. More over we got stiff competition from ABB and other suppliers & these guys dont go in for special cards.. Any idea how to over come this ?? Hi KhalDrogo, I think "teaming" option is with Intel NIC cards. Plz correct if I am wrong !! Also can we use teaming between 2 different card manufacturers ?? Regards Nil
Nil96 Posts: 325 Rating: (14)	Last edited by: Nil96 at: 1/16/2012 3:43 PM
Suggestion To thank Quote Answer

1/18/2012 12:06 AM	Rate (0)
KhalDrogo Posts: 71 Rating: (12)	Also can we use teaming between 2 different card manufacturers ?? Maby it is possible but I don't think that is a good Idea. Please, get more specific on the Communication / Networks forum I think "teaming" option is with Intel NIC cards. Plz correct if I am wrong !! I'm not sure that I understand the question but for example I used Broadcom Netxtreme cards with teaming. There are lot of venodors wich provides hardware with a teaming option.
KhalDrogo Posts: 71 Rating: (12)
Suggestion To thank Quote Answer

1/18/2012 11:23 AM	Rate (0)
Nil96 Posts: 325 Rating: (14)	Hi, Thanx for info. Anyway I procured Intel NIC card with dual ports. Was able to configure "teaming" successfully. Since I didn't have any of the 400 hardware, just connetced one of the Modbus TCP/IP converter to the PC with Intel dual port card and tried running WinCC. The driver connection was showing as success in WinCC. Tried removing one of the LAN cable attached to Intel NIC dual port and still WinCC was ok. Later removed both the LAN cables attached to Intel NIC dual port card ( winCC connection was shown as disconnected ). When both cables were reinserted, wincc driver conenction was shown as "success" after couple of seconds. But the only problem was when the LAN cable was disconnected and again reinserted on the Modbus TCP/IP convertor ( wincc always shows the connection as disconnected ). Only upon the Modbus TCP/IP convertor Power switched off and on, wincc again was showing connection as "Ok". At this point I am confused if the above mentioned problem of wincc continuously showing driver disconnect forcable removal and insertion with Modbus TCP/IP covertor, is all because of TCP/IP convertor OR WinCC inherent behavior. Regards
Nil96 Posts: 325 Rating: (14)
Suggestion To thank Quote Answer

1/28/2012 6:25 AM	Rate (0)
Nil96 Posts: 325 Rating: (14)	Hi, Today I got a chance to test "teaming" functionality of dual port intel make NIC card with an 412-3H system. It worked perfect. Infact it worked in all ways ( plugging & unplugging of cbale between the dual port NIC cards. Also switching either of the 412-3H CPUs ). Well... on a long run I am not very sure how good this works. Regards Nil
Nil96 Posts: 325 Rating: (14)
Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users KhalDrogo

9/3/2013 5:49 PM	Rate (0)
Blue Moderator Platinum Member Joined: 4/21/2006 Last visit: 10/15/2024 Posts: 510 Rating: (24)	New question was splitted to a new thread: connect quantum DCS (2 redundant quantum CPU's) with WinCC thr...

Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Follow us on