Identify the Failure Boundary
The reduced test system is CK3E → NX-ECC202 → ID5442. Network activation completes the master, slave, clock, and network checks, then stops while checking whether activation succeeded. The network never reaches OP state, and the reported coupler diagnostic is AL-Status Code: 0x001E: “An error was detected in the TxPDO settings.”
A CK3E → Xenus XEL configuration reaches OP state, so the evidence narrows the fault to the NX-ECC202 branch, its attached ID5442 configuration, or the process-data mapping generated for that branch. It does not prove that the CK3E master configuration is correct for every slave.
Separate Confirmed Settings from Unknowns
| Item | Evidence | Engineering decision |
|---|---|---|
| Update and servo clock | Configured for 1 kHz
|
Retain initially; no evidence ties this value to the TxPDO error. |
| Clock configuration | Distributed-clock synchronization and Master Shift are configured. | Do not change clock settings until the PDO configuration is checked. |
| NX configuration | Created in Sysmac Studio. | Confirm the configuration stored in the coupler matches the attached ID5442 arrangement. |
| Master mapping | Network scanned and mapping loaded in PowerPMAC IDE. | Regenerate the scan and mapping after confirming the coupler configuration. |
| Reported fault |
0x001E, TxPDO settings error |
Treat transmit process-data configuration as the primary diagnostic path. |
Rebuild the Configuration in a Controlled Order
Manually matching PDO offsets is not a confirmed remedy. An offset comparison is meaningful only when the master and coupler use the same process-data layout; changing offsets alone can preserve the underlying layout mismatch.
- In Sysmac Studio, verify that the NX-ECC202 configuration contains only the physically attached ID5442 and that the stored configuration matches the reduced test system.
- Apply the verified configuration to the NX coupler using the existing Sysmac Studio workflow.
- In PowerPMAC IDE, scan the reduced network again instead of retaining mapping data created for an earlier arrangement.
- Load the newly discovered mapping into the PMAC, then activate the network.
- If
0x001Eremains, compare the transmit process-data entries expected by the master with those configured for the coupler. Check entry presence, order, size, and resulting offsets; do not force offsets until the differing entry is identified.
Verify the Result
A successful correction must satisfy both endpoints: activation must finish in PowerPMAC IDE, and the NX-ECC202 must enter OP state without 0x001E. If activation still freezes at the final status check, record whether the coupler continues to report 0x001E. The same code keeps the investigation on TxPDO layout; a different code establishes a new failure boundary.
Preserve the reduced CK3E → NX-ECC202 → ID5442 topology until it reaches OP state. Add removed components only after this baseline passes, rescanning and regenerating the mapping whenever the configured process-data layout changes.
FAQ
What does NX-ECC202 AL-Status Code 0x001E mean?
The reported diagnostic states that an error was detected in the TxPDO settings. Check the transmit process-data layout shared by the NX coupler configuration and the CK3E master mapping.
Should I manually change PDO offsets to clear 0x001E?
Not until you identify a difference in entry presence, order, or size. Regenerate the master mapping from the verified reduced configuration before forcing offsets.
How do I verify the CK3E and NX-ECC202 correction?
Activate the rescanned mapping and confirm that PowerPMAC IDE completes its activation check, the NX-ECC202 enters OP state, and 0x001E is no longer reported.