From 04:00 PM CDT – 08:00 PM CDT (09:00 PM UTC – 01:00 AM UTC) Tuesday, April 16, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Kill Function not working properly
Arbidus
Member
02-17-2013 08:44 PM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
I am running custom motors that are monitored with optical encoders. These motors are able to be moved and repositioned when not being currently controlled by labview and I have had no problems with this setup until recently. Previously when I used the kill function from labview or the motion and automation program the motors would remain off until I re-enabled them from labview and I would be able to move them to a new position. My current problem is that sometimes when I reposition the motors they will turn back on and hold position. If I kill the motors from the motion and automation program it will display that the motors have been killed, but after moving the motor arms around the motors turn back on and it no longer displays that the motors have been killed. I have tested this with only the motion program running on the computer and no labview to tell the motors to turn on. Any help on why the motion program is re-enabling the motors without any user input would be great.
The_Hunt
NI Employee (retired)
02-18-2013 04:01 PM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
Arbidus,
Which "motion program" are your referring to? What is your current software/hardware setup? Are you killing the motor from Measurement and Automation Explorer (MAX)?
After the axis and motion is killed, is there a defined pattern related to the motor's position of when they turn back on?
You also mention that your current application used to work just fine. What has changed since then? Anything in the encoders?
Huntington W
National Instruments
Applications Engineer
***Don't forget to give Kudos and Accepted as Solution where it is deserved***
National Instruments
Applications Engineer
***Don't forget to give Kudos and Accepted as Solution where it is deserved***
02-18-2013 04:17 PM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
The problem occurs when using both MAX and labview to disable the motors. The motor moves the arm back and form in a 60 degree arc and the program ends with the arm roughly 30 degrees away from the initial position. The motors will sometimes turn themselves on when being manually moved back to the initial position. This problem has also happened when the motors are first being turned on for the day and moved to the initial position. However, this problem can be hard to reproduce. The motor might be repositioned 10 times before they turn back on, or they might turn back on imidiately after being disabled. One of the optical encoders was replaced reciently with what should be a direct replacement from the manufacturer. Both MAX and labview are able to properly read the motor position from the new encoder and it has worked seemlessly with the existing program until this problem.
Thanks,
Arbidus
