Identify the Failure Point
Two errors point to the controller not recognizing one or more configured modules. The first occurs while enabling shunt calibration on an NI 9235 installed in an NI 9144 chassis. The second occurs when the application returns the NI Scan Engine to Active mode because a slave device did not reach Operational state.
| Observed condition | Engineering interpretation |
|---|---|
| Error -66205 at the shunt-calibration Property Node: variable object not found | The deployed controller configuration does not provide the variable object expected by the VI. |
| Error -2147138516 while selecting Active mode | One or more slave devices failed to enter Operational state. |
| Scan Engine remains in Initializing after calibration | Treat this as evidence that the transition did not complete; inspect the affected NI 9144 modules and deployed EtherCAT configuration. |
Enter Config Mode Before Setting Shunt Calibration
Run the VI on the remote NI 9074 target without an IP-address configuration in the VI. Place the Scan Engine in Config mode before changing the shunt-calibration property, whether the NI 9235 is local to the NI 9074 or installed in an NI 9144 EtherCAT chassis. Active mode does not permit the required property change on the NI 9144 chassis.
Redeploy or Rebuild the Target Configuration
- Deploy the controller configuration and EtherCAT master configuration from the LabVIEW project before executing the calibration code.
- If either error persists, deploy the EtherCAT master configuration again.
- If redeployment does not restore the module objects, access the NI 9074 through FTP and delete the contents of
/ni-rt/config. - Reboot the controller, then deploy both the controller configuration and EtherCAT master configuration again.
- Run the VI with the Scan Engine entering Config mode before enabling shunt calibration and returning to Active mode afterward.
Deleting the configuration contents and redeploying corrected the local NI 9235 problem in the reported system. The NI 9144 problem later cleared after the procedure was retried, so the evidence does not isolate a single additional change responsible for recovery.
Verify the Complete EtherCAT Path
Test local and EtherCAT modules separately. Confirm that local NI 9235 modules complete calibration and return the Scan Engine to Active mode, then add the NI 9235 modules on each NI 9144 chassis. Successful recovery means the Property Node completes without errors, every slave reaches Operational state, and the Scan Engine returns to Active rather than remaining in Initializing.
The reported working software set was LabVIEW 2011 SP1 on the development system with NI-RIO 4.1 and EtherCAT 2.3 on the NI 9074. Another reported test used LabVIEW 2011, NI-RIO 4.1, and EtherCAT 2.3. These observations establish tested combinations only; they do not prove that version changes caused or resolved the fault.
FAQ
What causes LabVIEW error -66205 during NI 9235 shunt calibration?
The Property Node could not find its variable object. Redeploy the controller and EtherCAT master configurations, and verify that the project contains the installed NI 9235 modules under the correct NI 9074 or NI 9144 chassis.
Why does Set Scan Engine Mode return error -2147138516?
The Scan Engine cannot enter Active mode because at least one slave device failed to reach Operational state. Rebuild the deployed configuration and check that calibration property changes occur while the system is in Config mode.
How do I clear a stale NI 9074 configuration?
Delete the contents of /ni-rt/config through FTP, reboot the NI 9074, and redeploy both the controller configuration and EtherCAT master configuration. Then verify that the Scan Engine completes its transition to Active mode.