Since the redundancy capabilities are built-in, all the clients will naturally switch over if for some reason the main server dies. Server #5: Offline SQL server backup (also used as a test bed for SQL stuff). Also designated as an offline backup for servers 3 & 4. Supports both a higher end management interface and a sort of "backup" interface so that if a client node craps out, you can get to a web-based interface to get by. So it might be easier using iFix or other (any other suggestions?) but then Supervisor might be able to save you a sum *IF* you don't mind a bit of hard graft Bertie. Data Logging, Alarm History and acknowledgement, Error log) so still may not be what you are looking for. Even then, remember that many systems are local to each client (e.g.
#Make a square in ifix scada code#
But my point is that you would need to develop your own failure detection system and switchover code to achieve this. by calling 'EnableGroup()' for points defined for the other machine, or changing the PC Name on the CX-Supervisor ActiveX Communications Control etc). I imagine you could have 2 CX-Supervisors acting as servers (or use OPC Servers) with the client machines programmed to detect a failure and switch to the other machine (e.g.
#Make a square in ifix scada manual#
I read the User Manual chapter which does describe some basic topography concepts including redundant server although I haven't seen any specific features for this. Yes I've heard for larger SCADA with multiple stations and redundant stations iFix is easier (therefore more suitable) than CX-Supervisor.
0 kommentar(er)
