
The Allen-Bradley 1738-AENT ArmorPOINT EtherNet/IP Adapter provides network communication between a compatible industrial controller and distributed ArmorPOINT I/O modules. When the adapter experiences a communication fault, power problem, configuration error, or POINTBus failure, the controller may lose access to remote input and output data. These conditions can interrupt machine operation, generate PLC alarms, or prevent the I/O assembly from entering its normal operating state.
This troubleshooting guide explains how to diagnose common Allen-Bradley 1738-AENT faults, interpret status indicators, investigate EtherNet/IP communication failures, check power and POINTBus conditions, and verify corrective actions. The procedures are intended for maintenance engineers and industrial automation technicians working with existing ArmorPOINT installations.
Product lifecycle consideration: The 1738-AENT is a discontinued model. Before arranging repairs or purchasing a replacement, verify the exact part number, series, firmware requirements, and compatibility with the existing controller project.
The 1738-AENT is an EtherNet/IP adapter rather than a standalone programmable controller. Its operation depends on several interconnected elements:
A failure in any one of these areas may produce symptoms that appear to indicate an adapter fault. For example, an adapter may respond on the network while its I/O connection remains unavailable. Likewise, the adapter may be powered correctly but unable to establish normal operation because a module is missing from the POINTBus assembly.
Industrial control equipment may be connected to hazardous electrical supplies and machinery capable of unexpected movement. Follow the site’s electrical safety, process isolation, and maintenance procedures throughout troubleshooting.
Where live measurements are necessary, they should be performed only by qualified personnel using properly rated equipment and an approved risk-controlled procedure.
The adapter’s front-panel indicators provide a useful starting point for fault diagnosis. The table below summarizes documented diagnostic meanings for the 1738-AENT family. Exact behavior can vary by series and firmware, so confirm the indicator definitions for the installed unit before taking corrective action.
| Indicator | Observed state | Likely meaning and recommended check |
|---|---|---|
| Adapter Status | Off | Adapter power may be absent. Check the supply and power connections. |
| Adapter Status | Flashing green | The adapter may require commissioning because its configuration is missing, incomplete, or incorrect. |
| Adapter Status | Solid green | Normal adapter operation is indicated. |
| Adapter Status | Flashing red | A recoverable fault may be present. Review configuration, address-switch changes, and documented firmware-related diagnostics. |
| Adapter Status | Solid red | An unrecoverable fault may have occurred, such as a self-test or firmware fatal error. |
| Network Activity | Off | No Ethernet link is established. Inspect the cable, connector, and upstream network device. |
| Network Activity | Flashing | Network transmission or reception activity is present. |
| Network Activity | Solid green | An Ethernet link is established. |
| Network Status | Off | The adapter may not have initialized or may not have an IP address. |
| Network Status | Flashing green | An IP address may be present, but no CIP I/O connection is established. |
| Network Status | Solid green | The adapter has an IP address and active CIP connections. |
| Network Status | Flashing red | One or more CIP connections may have timed out. Check the controller and I/O modules. |
| Network Status | Solid red | A duplicate IP address may have been detected. |
| POINTBus Status | Off | The adapter or local I/O assembly may not be powered. Check power indicators. |
| POINTBus Status | Flashing red | A recoverable local I/O fault may exist, such as a missing module or a connection timeout. |
| POINTBus Status | Solid red | An unrecoverable POINTBus fault may be present. |
| POINTBus Status | Flashing green | A firmware or nonvolatile-memory update may be in progress. Follow the documented procedure and do not interrupt it. |
| POINTBus Status | Solid green | The local I/O adapter is online with established connections. |
| System Power | Off | The internal 5 V system supply may be unavailable. Check adapter power and the documented power budget. |
| System Power | Solid green | The internal system supply is active. |
| Adapter Power | Off | The adapter’s 24 V input may be absent. |
| Adapter Power | Solid green | Adapter power is present. |
Interpret the indicators together rather than in isolation. For example, an active Ethernet link with a flashing green Network Status indicator suggests that the physical network link exists but the expected CIP connection has not been established. The next step is to inspect the controller project and connection configuration rather than immediately replacing the adapter.
If the Adapter Status and Adapter Power indicators are off, investigate the supply circuit before concluding that the adapter has failed.
Do not repeatedly cycle power without first recording the initial indicator pattern and checking the external supply. Repeated resets may conceal an intermittent wiring fault or remove useful evidence.
This pattern can indicate a problem with the internal DC-DC converter or the system power path. First confirm that the input supply is stable and that the installation is within its specified electrical limits. Then check the POINTBus current budget and connected modules.
If the external supply, wiring, and load budget are verified but the System Power indicator remains off, the adapter may require professional inspection or replacement. Do not attempt to probe internal circuits or modify the PCB without appropriate documentation and qualifications.
Intermittent resets can result from unstable power, poor connector contact, excessive electrical noise, environmental problems, or an internal fault.
If Network Activity remains off, the adapter may not have an established physical Ethernet link.
Because the 1738-AENT is a single-port adapter, it should not be diagnosed as if it were the dual-port 1738-AENTR. Confirm the correct network topology and cable route for the installed model.
If Network Activity indicates a link while Network Status flashes green, the adapter may have an IP address but no established CIP connection.
Check the following items:
A flashing red Network Status indicator can indicate that one or more CIP connections have timed out. Investigate the controller, adapter, local I/O assembly, and network path.
A solid red Network Status indicator on the documented 1738-AENT/B adapter may indicate a duplicate IP address.
Do not change network addressing on a production system without authorization. A replacement address must be reflected in the controller project and network records where required.
The POINTBus connects the adapter to the local ArmorPOINT I/O assembly. Problems with the module arrangement, a missing I/O module, or an internal bus fault may prevent the adapter from establishing normal local I/O operation.
Possible causes include a missing module, a difference between the expected and installed module count, or an I/O connection timeout.
A solid red POINTBus indicator may indicate an unrecoverable local bus fault. First rule out obvious external causes such as an incorrect assembly, missing termination, or a power problem. If the condition persists after approved checks, the adapter or local I/O hardware may require further evaluation.
Do not repeatedly remove and reinstall modules while energized. Isolate the system and follow the documented procedure before changing the physical assembly.
If the adapter is online but one or more local I/O modules do not operate correctly, inspect the affected modules and their configuration.
Do not assume that a single failed I/O channel necessarily means that the adapter has failed. The fault may be limited to the individual I/O module, its wiring, its field supply, or its configured data mapping.
The 1738-AENT includes address switches on the adapter. The behavior of these switches depends on the installed series and the documented addressing method. Record the original settings before making changes and use the correct instructions to determine the intended address.
A flashing green Adapter Status indicator can indicate that commissioning is required because configuration is missing, incomplete, or incorrect.
Review the controller project and confirm that:
A flashing red Adapter Status indicator may be associated with a recoverable fault, while a solid red indicator can indicate an unrecoverable self-test or firmware fault. Consult the documentation for the installed series to determine the exact meaning.
Firmware updates should be performed only when required and supported by the hardware, using the approved procedure and compatible firmware files. Ensure that the equipment is in a safe state and that power and communication conditions are suitable before beginning. Do not interrupt a firmware update unless the official recovery procedure specifically instructs you to do so.
Document the time of failure, controller fault messages, adapter indicator states, affected I/O points, and recent maintenance or configuration changes. If the fault is intermittent, record the conditions under which it occurs.
Confirm that the adapter power and system power indicators show the expected states. If power is missing, investigate the supply and wiring before troubleshooting network communication.
Confirm that the physical link is established. Inspect the cable, connector, upstream switch, and network path. If the link is active, continue with addressing and CIP connection diagnostics.
Verify that the adapter’s actual address matches the controller configuration and does not conflict with another device. Correct discrepancies using the authorized network configuration procedure.
Review the controller’s fault and I/O connection status. Confirm that the controller is in the intended operating mode and that the adapter’s device profile and I/O configuration are correct.
Compare the physical I/O assembly with the configured module list. Check for missing modules, poor seating, incorrect termination, and power-budget issues.
If the problem remains, determine whether it is associated with the power supply, network infrastructure, controller configuration, local I/O modules, or adapter hardware. Change only one variable at a time and record the outcome.
If power, network, configuration, and assembly checks have been completed but the adapter continues to indicate an unrecoverable fault, arrange qualified inspection or replacement with a verified compatible unit.
Record fault messages and LED states
|
v
Check adapter and system power
|
v
Is Ethernet link established?
/ \
No Yes
| |
Inspect cable and Check IP address
network hardware and CIP connection
|
v
Check POINTBus status
|
v
Verify modules and project
|
v
Correct fault and retest
This flow is a general troubleshooting aid, not a substitute for the manufacturer’s detailed diagnostic procedures.
Replacement may be appropriate if the adapter has a persistent unrecoverable hardware fault, visible physical damage, or an internal power problem that remains after the external supply and wiring have been verified. Before replacing the unit, confirm the root cause as far as practical to avoid damaging the replacement with the same external fault.
Confirm all of the following:
Do not assume that the 1738-AENTR or another adapter in the same product family is a direct replacement. The number of Ethernet ports and supported network architecture differ.
Before removing the original adapter, record its network settings, switch positions, controller project details, and relevant diagnostics. Apply the approved configuration to the replacement and validate communication before restoring normal production operation.
After a repair, configuration correction, or replacement, verify the entire communication path rather than checking only whether the adapter powers up.
Do not return the system to production solely because the fault indicator clears. Confirm that the affected I/O data and field-device behavior are correct and that the machine can operate safely.
A preventive maintenance plan can reduce recurring communication and power faults affecting the 1738-AENT installation.
The Ethernet link and IP address may be working while the CIP I/O connection remains unestablished. Check the controller project, adapter configuration, connection parameters, module list, and controller operating mode.
For the documented adapter, it generally indicates that an IP address is present but no CIP connections are established. Check the controller configuration and the expected I/O connection.
It can indicate a duplicate IP address on the documented 1738-AENT/B adapter. Verify the addressing plan and correct the conflict using the approved procedure.
Check the configured and installed module counts, module seating, local I/O diagnostics, connection timeouts, and the documented termination arrangement.
This can indicate a problem with the internal DC-DC converter or system power path. Verify the external supply, wiring, and permitted load budget first. If the condition persists, arrange qualified hardware evaluation.
Do not assume that live removal is supported. Isolate the equipment and follow the approved maintenance procedure unless the exact hardware and documented system design explicitly permit otherwise.
Not automatically. The 1738-AENTR has a different Ethernet-port arrangement. Verify the network architecture, hardware compatibility, controller configuration, and replacement guidance before selecting a substitute.
Record the complete part number, series, IP address, rotary-switch positions, controller configuration, indicator states, fault messages, and the results of completed diagnostic checks.
Troubleshooting the Allen-Bradley 1738-AENT ArmorPOINT EtherNet/IP Adapter requires a structured approach to power, Ethernet connectivity, IP addressing, CIP connections, POINTBus status, and local I/O configuration. The front-panel indicators provide useful diagnostic clues, but their meaning should always be interpreted in the context of the installed hardware series and controller configuration.
Begin by recording the fault condition, then verify power and the physical network link before investigating addressing, controller configuration, and the local I/O assembly. If the problem persists after external causes have been excluded, arrange qualified hardware evaluation or use a verified compatible replacement. Complete functional testing and document the result before returning the system to service.