The P1-550 refuses to enter RUN and reports that none of the rack modules are present. Treat an all-module failure as a rack-level problem first: verify the power-supply module limit, the configured-versus-physical layout, backplane continuity, and startup enumeration before replacing more hardware.
Stop repeating the quick fixes
Several common recovery attempts can change the symptom without removing its cause. Use their results as diagnostic evidence.
| Attempt | Observed result | What it means |
|---|---|---|
Replace the P1-550
|
A second CPU produces the same error. | The CPU is unlikely to be the primary fault. Move attention to the supply, rack connections, physical layout, and project configuration. |
| Replace module 1 | The complete rack still appears absent. | A single bad first module is not proven. An all-module indication points toward a shared bus, power, or configuration problem. |
| Return from 12 modules to the former 11-module layout | The error remains. | Removing the added module does not necessarily restore connector seating, the downloaded configuration, or the state used during the next rack scan. |
Try versions 4.6 and 4.7 with current firmware |
The behavior remains. | Do not make software reinstallation the next move. Collect the system report and inspect the hardware/configuration boundary. |
| Start with one module and add a few at a time | An 11-module arrangement previously started. | This can locate a breakpoint, but a temporary startup does not override the supply's module limit or prove adequate power margin. |
Get it running, then fix it properly: once a reduced rack starts, record exactly which physical and configured change makes the failure return.
Apply the supply limit before chasing modules
| Power supply | Module-count information | Decision |
|---|---|---|
P1-01AC |
Hard limit of 8 modules | Stop troubleshooting an 11- or 12-module arrangement as though it were a valid full rack. Reduce the rack or change the power architecture. |
P1-02AC |
Specified in this case to reach 15 modules; a 15-module configuration was also reported operating with it | Use this supply for the stated 11- or 12-module arrangement, then investigate power loading, layout, and bus integrity if enumeration still fails. |
Confirm what is being counted. Match the physical I/O-module positions against the engineering project and the system report rather than relying on a visual total that may include components counted differently by the software.
Module-count capacity and power capacity are separate checks. The rack contains five modules and three modules. That mix was not identified as the cause, but the module-count rating alone does not prove that every installed load fits the supply's power budget. Read the published consumption for each installed module, total it by the required power rail, and compare each total with the supply rating. Do not substitute module quantity for that calculation.
Use the failure pattern to locate the common cause
If one module is absent, inspect that module, its slot, and its configuration entry. If every module is reported absent, start with the parts shared by the whole rack:
- Correct supply type and a supply that reaches its normal operating state
- Rack/base connectors, alignment, and backplane continuity
- Exact agreement between configured module order and physical module order
- A complete download containing the intended hardware configuration
- Rack enumeration during the transition to
RUN
The fact that two P1-550 CPUs show the same symptom increases the value of these common-path checks. It does not prove that every individual module is good, but it makes another blind CPU replacement a poor next step.
Go online with the CPU and create a system report before disturbing the rack again. Preserve the reported module inventory, supply information, firmware identification, configured layout, and active diagnostics. Photograph the complete rack so slot order and supply type can be compared with the report.
Rebuild the known configuration under control
- Save an offline copy of the working logic and hardware configuration. Record the exact error shown when the controller is commanded to
RUN. - Place the machine in a safe maintenance state and remove power using the site's electrical procedure. Do not reseat modules on an energized rack.
- Write down the physical order of all modules, including the five and three units. Compare that list, position by position, with the project.
- Read the supply label. If it is a
P1-01ACand the counted arrangement exceeds 8 modules, stop here. Install the correctly sized architecture before continuing. - If a
P1-02ACis fitted, inspect every mating connector and base junction. Look for incomplete engagement, shifted modules, damaged contacts, debris, and mechanical strain introduced while the twelfth module was installed or removed. - Restore the exact 11-module physical arrangement that previously ran and make its project configuration match. Download that complete configuration, cycle power as required by the normal commissioning procedure, and command the CPU to
RUN. - If all modules still appear absent, isolate the rack using an offline copy of the project. Reduce the configured and physical rack together to one known module, then add modules in small groups. Never download a stripped diagnostic configuration over the only copy of production logic.
- At the first failing addition, remove power and separate the variables: test the suspect module in a known position, inspect the newly extended rack connection, and confirm that the project's slot order changed with the hardware.
- Add the twelfth module only after the 11-module baseline passes repeatedly. Update the hardware configuration before startup and recalculate the supply load using the module data.
If production logic cannot compile or operate with the reduced configuration, do not improvise around its I/O references. Use the system report and physical inspection first, then perform rack isolation in a controlled maintenance copy or with official technical support.
Verify more than one successful transition
A single entry into RUN is not enough after an intermittent rack-enumeration fault. Verify the repaired baseline before expanding it:
- The physical supply is
P1-02ACfor the stated 11- or 12-module requirement. - The online module list matches every configured position and catalog identifier.
- No module-present or configuration-mismatch diagnostic remains active.
- The controller enters
RUNafter repeated controlled power-up and download tests. - The input indications and commanded output behavior match the machine's safe functional test.
- A new system report shows the complete rack. Retain it with the project archive and rack photograph.
Test the 11-module baseline and the 12-module expansion as separate configurations. If the baseline is stable but the twelfth addition immediately removes the entire rack, inspect the expansion connection, added module, configured slot, and calculated power load before changing the CPU or software again.
Use remote expansion only for a defined reason
A P1-RX may be part of a redesigned layout, but it is not a diagnostic cure for an unresolved local-rack fault. Splitting the rack can change the power and communication architecture while leaving a bad connector, incorrect project layout, or undersized supply undiscovered.
Choose remote expansion only after confirming the supported module arrangement, required supply capacity, communications path, and how the production logic maps the relocated I/O. Establish a stable local baseline first so the new architecture is not commissioned on top of the original fault.
FAQ
Why does a P1-550 say none of the modules are present?
When the whole rack disappears, check the shared path: power-supply selection, rack connectors, configured module order, the downloaded hardware configuration, and startup enumeration. Generate a system report before replacing individual modules.
Why did 11 modules work until I added a twelfth?
Installing the twelfth module can alter connector seating, rack continuity, power loading, or the configured-versus-physical layout. Returning to 11 modules will not fix those conditions automatically; rebuild and verify the exact former layout.
Why does swapping the P1-550 CPU not clear the error?
If two CPUs report the same all-module failure, the common rack hardware and project configuration remain the stronger suspects. Check the supply, module order, backplane connections, and system report before trying another CPU.
Why is the P1-02AC required for this module count?
The P1-01AC has a hard limit of 8 modules. The P1-02AC was specified for configurations up to 15 modules, but the installed modules' power consumption still requires a separate calculation.
Stop here if a correctly assembled P1-02AC rack that matches the downloaded project still reports every module absent, or if the system report cannot identify the physical rack. Contact AutomationDirect through its official technical-support channel and provide the system report, full-rack photograph, project configuration, supply type, firmware identification, and the exact change that triggers the failure.