Help plss..
my problem is that why when my Primary CPU switchover to Standby CPU my Citect SCADA communication lost and resume after 10-15seconds?
[?]: Citect and Quantum HotStandby 67160 with NOE 77101
Quantum HotStandby Communication
Dear which software you are using.
In ProWORX32 / Concept we use address swapping option from configuration extension, in which if Primary controler have X address, then in case of standby the same controler will have X+32 using modbus Plus.
There should be something like that for TCP/IP.
Dont Forget: Put the address of both controllers same and use address swapping on Switching. Sometimes it happen you are getting status from Standby PLC (Primary PLC Updates Standby) and you feel it is working properly, but incase of communication breakup b/w Primary & Standby you will get false values.
Hope you will understand what I want to say.
In ProWORX32 / Concept we use address swapping option from configuration extension, in which if Primary controler have X address, then in case of standby the same controler will have X+32 using modbus Plus.
There should be something like that for TCP/IP.
Dont Forget: Put the address of both controllers same and use address swapping on Switching. Sometimes it happen you are getting status from Standby PLC (Primary PLC Updates Standby) and you feel it is working properly, but incase of communication breakup b/w Primary & Standby you will get false values.
Hope you will understand what I want to say.
Hi
In Unity you dont need change nothing
communicatin TCP/IP is not embedded system Off PLC
MB+ is integrated system of plc ,so if you change bu "Primary" to "Stanby" plc
communication MB+ stay work,
communication TCP/IP(module NOE) need to Restart,plc do this but its need time
all device lose communication in plc in this time (0.1~1 sec.)
you can check this very simple:
1 start command Ping from computer to Plc
2 change Primary/Secondary plc
3 check how much ping you lose(1-2 is standard )
I'm thing you have problem in you SCADA
usually in communication driver you have swiths: "TIME OUT" or "Minimum reconnect time"
you need chenge they to 1-2 seconds
P.s address in MB+ Primary =X Secondary=X+32
address in TCP/IP Primary =xxx.xxx.xxx.xxx Secondary=xxx.xxx.xxx.xxx +1
In Unity you dont need change nothing
communicatin TCP/IP is not embedded system Off PLC
MB+ is integrated system of plc ,so if you change bu "Primary" to "Stanby" plc
communication MB+ stay work,
communication TCP/IP(module NOE) need to Restart,plc do this but its need time
all device lose communication in plc in this time (0.1~1 sec.)
you can check this very simple:
1 start command Ping from computer to Plc
2 change Primary/Secondary plc
3 check how much ping you lose(1-2 is standard )
I'm thing you have problem in you SCADA
usually in communication driver you have swiths: "TIME OUT" or "Minimum reconnect time"
you need chenge they to 1-2 seconds
P.s address in MB+ Primary =X Secondary=X+32
address in TCP/IP Primary =xxx.xxx.xxx.xxx Secondary=xxx.xxx.xxx.xxx +1