In PAC Suite 3.12.1.21 Simulator mode, a monitored Copy Array (CPA) instruction may fail to display the status of the first several array locations. Expanding the array in DataView can make those locations render. Available evidence indicates a monitoring/display defect rather than failed array execution: an external C-more project read the expected array values while the CPA instruction display remained incorrect.
Identify the observed CPA behavior
| Condition | Observed result | Interpretation |
|---|---|---|
| PAC Suite 3.12.1.21 in Simulator mode | The first several CPA locations do not display status | Confirmed display symptom |
| Array expanded in DataView | The affected locations render | DataView access changes the visible symptom |
| Array values read by a C-more project | Expected values are present | Supports a GUI rendering defect rather than a failed copy |
| Other code accesses the array, including CPD instructions | The issue may no longer appear | These accesses can mask the reproduction condition |
Separate execution from display status
Do not use the monitored CPA graphic as the only proof that the copy failed. The reported test showed correct array data through C-more even when the CPA instruction did not render it. This supports, but does not independently prove in every project, that the underlying copy completed while the Simulator interface displayed stale or incomplete status.
The PAC Suite 3.9.0.26 release notes separately identify a CPA Copy Binary issue in the PLC Simulator. The evidence does not establish whether that earlier Copy Binary defect and the 3.12.1.21 rendering symptom share the same root cause, so treat them as distinct observations unless AutomationDirect confirms otherwise.
Reproduce the rendering defect
- Run the project in Simulator mode and monitor the CPA instruction without expanding its array in DataView.
- Remove other code methods that access the array tag values, including DataView entries and CPD instructions, because those accesses can prevent the symptom from appearing.
- Observe whether the first several CPA locations fail to render.
- Expand the array in DataView and check whether the missing status appears.
AutomationDirect technical support reproduced the behavior from the supplied procedure and reported it to the Productivity Engineering team.
Verify the copied data independently
Confirm the destination array through an independent consumer instead of relying exclusively on CPA animation. The reported investigation used a C-more project and received the expected array values. If an independent read returns correct data while the CPA display remains incomplete, classify the immediate problem as a Simulator monitoring discrepancy and retain the reduced reproduction project for AutomationDirect support.
FAQ
Why does PAC Suite 3.12.1.21 Simulator hide the first CPA array locations?
The evidence supports a rendering defect: the locations can appear after the array is expanded in DataView, and AutomationDirect reproduced the behavior.
Does a blank CPA status mean the array copy failed?
Not necessarily. A C-more project read the expected array values while the monitored CPA instruction failed to render them, so verify the destination data independently.
How can I reproduce the CPA Simulator display issue?
Monitor the CPA instruction with no DataView entries, CPD instructions, or other code accessing the array, then compare the display before and after expanding the array in DataView.