6. REDUNDANCY WITH NX3030 CPU
Direct Variable
AT Variable
DG_NX4010.tRedundancy.
RedDgnLoc.sNETB_Diag.*
Description
Variable Bit
3 bTimeoutFailure
TRUE – This failure is reported in case
a synchronization service hasn’t been fin-
ished successfully within a specific time-
out and failures from the type bInternal-
Failure or bLinkDownFailure haven’t been
found to justify that.
FALSE – The NX4010 module is working
properly.
4 .. 7 bReserved[4..7] Reserved.
Table 211: NETB Interface Specific Diagnostics
The “sNET_Stat” substructure has service success and failure statistics. The local and remote PLCs statistics can be
restarted through commands:
//Local PLC
DG_NX4010.tRedundancy.RedCmdLoc.bResetNETStatisticsLocal := TRUE;
//Remote PLC
DG_NX4010.tRedundancy.RedCmdLoc.bResetNETStatisticsRemote := TRUE;
The substructure has the following counters:
Direct Vari-
able
AT Variable
DG_NX4010.tRedundancy. Red-
DgnLoc.sNET_Stat.*
Description
%QW(n+35) wSuccessExchDgCmdSync
Success counting of the Diagnostics and
Commands service (0 to 65535)
%QW(n+37) wFailedExchDgCmdSync
Failure counting of the Diagnostics and
Commands service (0 to 65535)
%QW(n+39) wSuccessRedDataSync
Success counting of the Redundant Data
Synchronization service (0 to 65535)
%QW(n+41) wFailedRedDataSync
Failure counting of the Redundant Data
Synchronization service (0 to 65535)
%QW(n+43) wSuccessRedForceSync
Success counting of the Redundant Forc-
ing List Synchronization service (0 to
65535)
%QW(n+45) wFailedRedForceSync
Failure counting of the Redundant Forcing
List Synchronization service (0 to 65535)
Table 212: Interface Specific Diagnostics
Note:
Counters: All counters return to zero when its limit value is exceeded.
The substructure “sGeneral_DiagExt” owns the following fields to general redundancy diagnostics:
341