-70163(NIMC_invalidLimitRangeError)

[bellet]

When I attempt to initialize my PXI-7350 motion controller in MAX, I keep receiving the error: "-70163(NIMC_invalidLimitRangeError)" and the initialization process does not complete. I looked up this error in the Help and it says the lowerlimit value is greater than the upperlimit value. I do not know what this is referring to or how to fix it (SoftMotion?). I could not find more information on this error in the help, on google, or at ni.com. I tried resetting the controller in MAX then initializing it again which did not solve the problem. I tried powering off the PXI chassis, UMI-7774 and drives entirely, waiting >30 seconds, then powering them back on which did not fix the reoccuring error. I am using LabVIEW 2010 on a Windows 7 machine. The firmware version of the P7350 motion controller is Firmware Version - 68331: 7.40.3003, DSP: 7.32.3003, FPGA1: 7.10.3001, & FPGA2: 6.00.2009. I am connected to a UMI-7774 board and three P70530 Micro-stepping Stepper Drives. Any solutions or insight would be helpful.

Note: Upon not being able to complete initialization of the controller in MAX, in the 1D Interactive tab, Axis 1 or Axis 2 both initially show the motor "Killed" (Axis 1 and Axis 2 are shown disabled). When I click "Halt", the "Motor Killed" status turns off and the axis enables. I am then able to run the motors. However, the physical, pass through (short/open) limit switches connected to the system do not function while the axis is moving to stop the axis. The limit switches are enabled within MAX and have worked fine before this error was ever encountered.

Thank you.

Evan B. 

[ZachAttack]

There are two things I would try.  First is making sure the firmware is up to date.  You can update the firmware in Measurement & Automation Explorer by selecting the controller, going to Firmware tab on the bottom of the window to the right, right-clicking on the PXI-7350 firmware folder, then select "Update All Firmware Sectors" as shown in the image below (for a PCI-7330 controller). 

My other recommendation is to power down the chassis, and remove the card and make sure there are no bent/broken pins in the chassis.  Then replace the card.  Let me know if this does not work.

[bellet]

Zach,

Thank you for your reply. The firmware was updated per your procedure prior to experiencing the error (however, I will double check that all sectors were updated). I have not tried removing and inspecting the motion controller card installed yet (FYI: the card was installed factory).

However, I was able to apparently fix the issue by: in MAX, within the motion controller options, I selected setup mode Default Stepper Open-loop (I cannot remember all the options, but I believe they were: 1) Default Servo Mode 2) Default Stepper Open-loop 3) Default Stepper Closed-loop & 4) Custom). Originally, I started with the Default Stepper Open-loop setting and edited the settings from there which automatically changed the selected radio button to Custom. At some point in time, I apparently changed my settings in such a way (I believe) as to cause the error I was seeing. By the re-selecting the option Open-loop Stepper (which resets the settings) and re-entering my critical settings, I was able to make the error not re-occur (so far). Still, even though the error has not reoccurred, I would like to find out why it occurred and what the error actual means. Note: I did not record all the exact settings everything was set to when the error occurred (which may have been helpful for troubleshooting) since that would have taken extensive time.

If you can provide information regarding what the error means and why it occurs that may be helpful. That way, I can attempt to prevent it in the future. 

Thank you.

Evan T. Bell

Scientist

BMPC

[ZachAttack]

Evan,

The error message correctly identifies the problem.  When the software limit switches are enabled, if the forward limit switch position is less than the reverse limit switch position, you will get error 70163.  I was able to recreate the problem by putting in incorrect values:

To fix this, either disable the software limit switches or ensure the reverse limit is less than the forward limit.  I hope this information is helpful.