Applies To: |
|
Summary: |
Question: How do I configure a redundant disk PLC? |
Solution: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Configure two disk PLCs - one on the hard
drive of each I/O Server. In normal operation, each IO Server will
be reading and writing to the disk PLC on the hard drive of the
other PC. In the event of a failure by one of the IO Servers, the
working IO Server will start communicating with the disk PLC on its
own hard drive. The following examples show how to configure the
units databases:
* The D drive (on IOServerA) must be mapped to the C drive on IOServerB. Communication, Units database
* The D drive (on IOServerB) must be mapped to the C drive on IOServerA.
Whenever Citect writes to the PLC, it must be made to write to both disk PLCs. You must duplicate each PLC address (in the Variable Tags database) that Citect needs to write to (this will not effect the IO count) and configure two commands, Cicode functions, reports, etc that write to the disk PLCs. The following example defines a Variable Tag and keyboard command to write to both disk PLCs.
If you have several occurrences of this double command, it will probably be easier to assign a label or write a Cicode function for each command. The above configuration will work if Citect is shutdown - but not if the PC is switched off. To allow for shutdown of the PC, a Cicode function will be required to restore the stale PLC file. The function will first check which IO Server is being started up, and will then set the correct disk PLC values. The following is a sample function: FUNCTION
END To automatically run the Cicode function, use the startup parameter [CODE] Startup, for example [CODE] Startup=RestorePLC. Note: Redundant Disk PLCs will be supported directly in Citect version 3.00. |
Keywords: |
Related Links
Attachments