Access to the network coupler is blocked after station init
A description of this resolution:
- Force redundancy transfer on both stations
Using the RUN/HOLD switch, set the active network coupler to HOLD mode which will force a redundancy transfer.
The redundancy partner becomes ‘active’.
Then switch the RUN/HOLD switch to RUN.
The network coupler goes into ‘passive’ mode.
Proceed in the same way for the redundancy partner.
By taking over the redundancy, the CL coupler is ‘restarted’ software based and the reception channels for system messages are reactivated again.
'Access to the network coupler is blocked after station init' resolves the following:
When an operator station that is set up as the coordinator for network couplers is initialized, access to the system dialog of individual network couplers is blocked sporadically.
The set-up of the station overview of the affected network coupler is incomplete or non-existent. Zeros appear in the RAM distribution, asterisks in the cycle times and dialog error messages such as “Target station not present” are displayed.The problem only occurs in systems with Version 7.1 where there are network couplers in redundancy.
The underlying cause is:
- Redundancy monitoring active on both stations for a brief period
When an operator which itself coordinates redundant network couplers is initialized the redundancy monitoring as determined by the coordinator structure is passed on to another operator station.
If the initialized station is then reloaded and activated via SAVE, it again takes on the coordinator function and redundancy monitoring. For the duration of the switching process, redundancy monitoring is active on bother stations for a brief period. If system messages regarding redundancy monitoring are sent during this period, the reception channel for system messages may be blocked in the network coupler.