EasyManuals Logo

ALTUS Nexto NX3004 User Manual

ALTUS Nexto NX3004
388 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Page #347 background imageLoading...
Page #347 background image
6. Redundancy with NX3030 CPU
339
Table 6-8. 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
Representation
Variable
AT Variable
DG_NX4010.tRedundancy.
RedDgnLoc.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 Forcing List
Synchronization service (0 to 65535)
%QW(n+45)
wFailedRedForceSync
Failure counting of the Redundant Forcing List
Synchronization service (0 to 65535)
Table 6-9. Interface Specific Diagnostics
Note:
Counters: All counters return to zero when its limit value is exceeded.
The sub structuresGeneral_Diag” owns the following fields to general redundancy diagnostics:
Direct Representation
Variable
Variável AT
DG_NX4010.tRedundancy.RedDgn
Loc.sGeneral_DiagExt.*
Description
Variable
Bit
%QB(n+47)
0
bFailedPBUS3A
TRUE This PLC can’t communicate in
the master state (active or passive) in the
PROFIBUS 3 A network. The master mode
(communicating with slaves) is assumed
by the Active PLC. The passive mode
(communicating with the active master) is
assumed by the Non-Active PLC. This
failure can also be indicated in case the
NX5001 module has a microprocessor
failure, or in case it can’t communicate with
the NX3030 CPU via bus.
FALSE There aren’t failures in the
PROFIBUS 3 A network.
1
bFailedPBUS3B
TRUE This PLC can’t communicate in
the master state (active or passive) in the
PROFIBUS 3 B network. The master mode
(communicating with slaves) is assumed
by the Active PLC. The passive mode
(communicating with the active master) is
assumed by the Non-Active PLC. This
failure can also be indicated in case the
NX5001 module has a microprocessor
failure, or in case it can’t communicate with
the NX3030 CPU via.
FALSE There aren’t failures in the
PROFIBUS 3 B network.

Table of Contents

Questions and Answers:

Question and Answer IconNeed help?

Do you have a question about the ALTUS Nexto NX3004 and is the answer not in the manual?

ALTUS Nexto NX3004 Specifications

General IconGeneral
BrandALTUS
ModelNexto NX3004
CategoryProcessor
LanguageEnglish