Re: using only ONE limit switch for limit and home?

[Jochen]

Hi Malte, I don't know exactly, what's going on here, but I have some ideas:- You said, that the home switch works in both directions, but not in your application? Does that mean that you have done a test with a move in 1D-interactive in MAX? What's the difference between this move and your moves in your application? Does velocity play a role here? If you reduce the velocity does the axis stop then?
- Is there a chance that your switch is bouncing? The 73xx boards have a devounce filter for limit switches, but maybe the switch is bouncing extremely with a long settling time. Could you check this (e. g. with a scope)?
- Does the problem also occurr when using a very simple example (single axis move)?
Thanks,Jochen

[mfs]

Hi, thanks again for your ideas. I tried a very simple 1d move in LabVIEW and that works fine. So I had a look again on my other (test) program and I found the problem. I placed my 1d move in a while loop so that the target position gets updated when the move is completed and stopped. In this loop is the start.flx so that the move would start and the motor would rotateif the target position is not equal to the current position (as long as a stop latch button is not activated). Therefore a limit switch would stop the move but the while loop would start the move again since target and current position are not the same. I actually didn't expect that behaviour since the limit switch is still activated when the move should start again. I thought that no power can be sent to the motor as long as a limit switch is pushed.This problem is not really important any more because I have to write a niceer and cleaner program and I don't want to use this while loop anway. But I would like to know if/why a move can start as long as a limit switch is activated.Thank you in advance!MaltePS: I attached the old program that doesn't work with the switches.

rotary_move.vi:
http://forums.ni.com/attachments/ni/240/6736/1/rotary_move.vi