Motion Control and Motor Drives

cancel
Showing results for 
Search instead for 
Did you mean: 

The motion control PCI-73xx generate an error 70165 when any switche is reached

US VERSION:

Hello, After having configured mu board PCI-7344 under MAX software (1axis activated because 1 only axis used, standard of stepper in open Loop...), I configure a sequence (in the sequence tab"Find Reference Settings )that the motor finds my" home switch ". I make apply the parameters followed by the stage Initialisation and the motor is put to move without never finding the home switch.  It stop as soon as it finds a switch (home, limit reverse or limit forward) on his travel and marking the error message following in the window "Initializing the controller...": -70165(NIMC_FindReferenceError) Find Reference was not successful because the motor stopped before the reference was found.

After have tested different parameters & options in the sequence tab "find reference setting" such as the option "smart Enable" notched and stripped...  I don't understand why the motors doesn't find any switches. The Pb is the same if I ask a sequence to finds another switch limit (revertse or forward) If I seek the reverse switch:  MAX turns over me the same message of erreur_70165 as soon as it meets the switch limit reverse.  There is only when I ask for a sequence to find the center of the axis that  I have a coherent thing: the motor move in direction forward, as soon as he meets the switch limit forward, it is reversed direction and leaves in mode transfers BUT as soon as he meets the switch limit reverse, I receive again the message of erreur_70165.

THANK YOU for your assistance

PS: IF I use the VI example "find reference" under LABVIEW 7.0, I obtain the same error as soon as my motor arrives on a sensor / switches 

Hereafter, the detail concerning my configuration: version MAX version 3.1.1 Ni Hardware:  Motion Control device PCI-7344 Driver Version:  NI Motion driver 6.1.4 Operating system:  Windows XP

0 Kudos
Message 1 of 3
(3,628 Views)
Hi,
 
Here it is a solution : do not configure high speed capture as one of the two digital input modes. Instead, run find index first. Then configure high speed capture for digital input programmatically.
 
Hope its help.
 
Regards,
Isabelle
Ingénieur d'applications
National Instruments France
0 Kudos
Message 2 of 3
(3,586 Views)
Hi,
 
I don't have a index in my application and i use the stepper in the open loop (because the rotary encoders don't function and generate an error in closed loop).
 
The only way that I found to avoid to have this error, it's to use the stepper at low speed and to put an OFFSET when my stepper find the differents switchs but it's not a good solution !....
 
- Which type of interface you recommend between the switchs and your board PCI-7332? 
- Would you have  the chronograms concerning detections of the switch?
 
Thank you for your assistance
 
PS: If you want you can to reply in french...
 
 
0 Kudos
Message 3 of 3
(3,567 Views)