Keyboard Shortcuts
Likes
Search
Best way to program for a back up processor
Hi All, The client wants a back up CP4 to take over if the primary CP4 goes down for whatever reason.?
Currently I have loaded the same program on each CP4 and they are both running simultaneously under different IPID¡¯s (03 & 04) on the UC Engine IP Table.? The client only has to swap the com cables and the relay cables.?
|
What I have done several times is to have both processors have the exact same IP, program(s) and settings, then they just move over the Ethernet cable along with the RS-232 and relay connections. Just have 1 Ethernet cable there so they can't hook up both at the same time. Also, I'd recommend having any initialization that happens to be based on both Program1_Start_F AND LinkStatus1_F (from the Ethernet Device Info Device Extender), so the other processor doesn't need to be rebooted after cables are moved over.
|
¿ªÔÆÌåÓý? This is probably too simple, but why not include the network and power cable in the cable routine? If you are moving some cables from one to the other, what difference does it make if you move a couple more? ?Certainly employ a second power supply, but do not connect the power to the backup processor until it is needed (after the rest of the cables have been moved).? This gives you a backup power supply that could also be used if the primary power supply failed. ? Then you only have one processor on at a time.? Your backup is also completely isolated from potential electrical damage until it is actually in use. ? From: <[email protected]> on behalf of Audvizer <Audvizer@...> ? Hi All, The client wants a back up CP4 to take over if the primary CP4 goes down for whatever reason.?
Currently I have loaded the same program on each CP4 and they are both running simultaneously under different IPID¡¯s (03 & 04) on the UC Engine IP Table.? The client only has to swap the com cables and the relay cables.?
|