In the Productivity software configuration described, a P3000 main base could not be paired with a P2000 remote chassis through the drag-and-drop remote-unit editor. The editor limited remote selections to the same platform type as the main base, so a mixed P3000/P2000 project could not be represented through that workflow.
Confirm the base and remote types in the editor
Record the main base type first, then inspect the remote chassis choices the installed Productivity software offers. In the reported configuration, a P3000 base could not select a P2000 remote; the editor allowed remote systems of the same type as the main base. That is the operational constraint to plan around when reviewing a project or bill of materials.
Keep the distinction between a requested feature and an available configuration. The mixed-platform behavior was raised as a software feature request, and a response said product engineers had been made aware of it. That response is not a compatibility approval or a release commitment. Since the imported report may be outdated, check the installed software and current product documentation before treating the limitation as current.
Write down the exact base and remote types shown in the project, then compare them with the physical equipment planned for the installation. Check: can the installed editor represent the actual base and remote combination without substituting a different chassis type?
Separate the editor limit from hardware compatibility
A configuration editor controls which hardware combinations an engineer can describe in a project. Its model list can reflect supported combinations, but a missing choice alone does not establish whether two platforms are electrically or operationally compatible. Similarity between the P3000 and P2000 platforms, as cited in the request, also does not establish that their remote chassis can be mixed.
Do not force the project to show a P3000 remote when the cabinet contains a P2000, or the reverse. That makes the project hardware map disagree with the installed system. The result could be an invalid configuration or misleading I/O mapping; the exact behavior depends on the supported hardware and software combination. Resolve that mismatch before commissioning.
| Observed condition | What it tells you | Decision |
|---|---|---|
| The editor offers remote chassis matching the main base type. | The described workflow restricts selection by platform type. | Check current compatibility documentation before designing a mixed system. |
| A P2000 remote is absent with a P3000 base selected. | The project cannot represent that pairing through the displayed choices. | Do not substitute another model in the project to bypass the restriction. |
| The platforms appear similar. | Similarity does not confirm a supported combination. | Use an explicit compatibility statement to approve the pairing. |
Check: confirm whether the question is about what the editor permits, what the hardware supports, or both; get an explicit answer for each before proceeding.
Use a same-type layout for a temporary restore
If production planning requires a project that the described editor can represent, keep the main base and remote chassis within the same platform type. This is the available configuration path described for that software behavior. It is a temporary planning choice, not proof that a mixed installation is impossible or that a same-type substitution fits the machine design.
Wrong fixes can create a project that looks complete but does not match the equipment:
- Do not drag in a different chassis type and assume the software will accept it later in the workflow.
- Do not select a same-type stand-in while leaving a different model in the bill of materials.
- Do not use platform similarity as a substitute for a supported combination.
If the mixed combination is required, hold the mixed chassis portion of the design until you verify a supported configuration path. If the immediate schedule needs a temporary same-type layout, confirm that the substitute model meets the application requirements and obtain the normal design approval before changing procurement or installation plans.
Check: the temporary project, approved equipment list, and physical installation plan must all name the same chassis types.
Check the installed software and current compatibility information
Before deciding that the restriction remains in force, identify the Productivity software version used for the project and review its current hardware configuration documentation. The report describes a 2017 editor limitation, and the imported post itself warns that its information may be outdated. Do not apply that historical behavior blindly to a later installation.
- Open the project in the software version intended for commissioning and select the actual main base type.
- Inspect the remote-unit chassis list and record whether it offers the required remote type.
- Check current official product documentation for an explicit P3000/P2000 mixed-system compatibility statement and the required configuration procedure.
- If the documentation does not answer the question, contact official technical support with the exact base model, remote model, and software version.
A software update or another configuration workflow could change what the editor permits, but do not infer that from a changed screen alone. Confirm the accepted combination in documentation or with official support, then make sure the project can save and reopen with the selected hardware definition.
Check: proceed with a mixed design only after the installed tool and current support information agree on the required pairing and configuration method.
Reconcile project chassis with the physical equipment
Once the combination is confirmed, align the project with the actual installation before commissioning. The evidence describes selecting a remote slave and its chassis in the software, so verify both the remote-unit identity and the chassis type wherever those selections appear in the current workflow. Do not assume that choosing the correct platform family automatically selects the correct remote unit.
- List each main base and remote chassis by the model marking on the equipment.
- Enter the matching chassis type for each remote unit in the project, using the supported workflow.
- Compare the saved project layout against the approved bill of materials and cabinet layout.
- Resolve any model mismatch before downloading or commissioning the configuration.
Keep the project file with the commissioning records so a later maintenance shift can compare the configured hardware against the installed hardware. If a replacement is needed, check the replacement model against the approved combination before installing it; do not use a superficially similar chassis as an unreviewed substitute.
Check: every chassis shown in the saved project matches the equipment installed at the corresponding remote unit.
Evaluate the 15-slot P3000 base as a separate request
The request also asked for a 15-slot base for the P3000 platform to provide more high-speed output capability, while acknowledging that the wider base would consume more space. This is a separate hardware capacity question. Adding a larger base would not, by itself, change the remote chassis choices in the software or establish P3000/P2000 mixed-platform support.
For a design that needs more high-speed outputs, inventory the required output points and compare them with the supported base and module options in current product documentation. Check cabinet width and the approved mechanical layout along with the output requirement. The source gives no slot count beyond the requested 15-slot base, no module capacity, and no confirmation that this base became available; read those details from the current product catalog or obtain them from official technical support.
Keep the two decisions separate in the design review: one concerns a larger P3000 base and output capacity, and the other concerns mixed P3000/P2000 remote chassis. Check: approve the base size and output arrangement only from current product data, independently of the mixed-platform decision.
Prove the complete configuration before release
After the software path and hardware combination are confirmed, verify the complete system as one matched configuration. Compare the project, equipment list, and installed chassis, then review the software's configuration status and any diagnostics presented during commissioning. Use the product-specific commissioning procedure for the controller and remote I/O system; no exact diagnostic code or special timing is identified for this case.
Test representative I/O points from the configured remote units against the connected field devices and confirm the expected state changes in the control system. If a chassis is missing, an I/O point does not respond as mapped, or the editor rejects the combination, stop and resolve the hardware definition or compatibility question before releasing the system. Do not clear the issue by changing the project to a model that is not installed.
Check: release the project only when the software accepts the approved chassis combination, the saved layout matches the installed hardware, and the commissioning checks pass for the required remote I/O.
Frequently asked questions
Why does the Productivity editor reject a P2000 remote with a P3000 base?
The described editor limited remote chassis selections to the same platform type as the main base. Check the installed software's current hardware list and documentation to see whether that restriction still applies.
Why can’t I assume the P3000 and P2000 remote chassis are compatible?
Platform similarity does not establish a supported mixed-system combination. Verify the exact base and remote models against current official compatibility information.
Why shouldn’t I select a P3000 stand-in for a P2000 remote?
The project would no longer describe the installed chassis accurately. Correct the hardware definition before commissioning or releasing the project.
Does a 15-slot P3000 base enable mixed P3000 and P2000 remotes?
No such relationship is described. Treat the requested 15-slot base for additional high-speed output capability as a separate hardware selection and verify its current availability and specifications.
When should I stop and contact AutomationDirect support?
Stop before commissioning if the editor rejects the required pairing or the project chassis do not match the installed equipment. Contact official AutomationDirect technical support with the exact base and remote models and Productivity software version, and request the supported mixed-platform configuration path.