Onboard_Trigger_Motion.vi

[peterk3]

Hello Everyone,

There is a program Onboard_Trigger_Motion.vi code that I found in the forums.  Unfortunately I want to run axis 2 off of a UMI 7764 controller, when I switch the vi commands to axis two and then run it, the program automatically switches the settings back while running to axis one.  So I suppose my question is how do I run axis two off of this program.

The example can be found at this link.

[link removed]

Thank you in advance for your time.

-Keith

[Jochen]

Keith,

I have checked the example you are referencing to thoroughly but I couldn't find a problem there that could cause the issue that you are experiencing. What exactly do you mean by "the program automatically switches the settings back while running to axis one"? The vi provides a control to select the axis that should be used. The default value is "Axis 1" but of course you can change that to "Axis 2". So I don't really think you are referring to this setting, do you?

Please provide additional information:

1. Which motion controller are you using? The UMI-7764 is just the connector block.
2. What version of NI-Motion are you using?

Best regards,

Jochen Klier
National Instruments Germany

[peterk3]

Hello and thank you for your help.

When I run the program with the settings on axis two, no motion is occuring from the motor driver (it is in another building but I will find out what the driver and motor is being used and let you know).  At first I thought that the problem might be the sub-vi's in the block diagram so I went through and changed them all from axis one settings to axis two.  While it is running when I open the sub vi's and try and change them it says axis one and it is greyed out.  I am not sure if I actually need to change anything in the block diagram or if I should be able to just change the front panel to axis 2.  When I run the simple one axis motion example and switch it to axis two on the front panel it works properly. 

-Keith

[Jochen]

You don't need to change anything in the block diagram as the value from the axis control is passed through all subvis.
I remember dimly that there was an older NI-Motion version that mixed up the axis settings in a subvi. My recommendation is

1.) to debug the vi in highlight mode and using probes to see if the correct axis number is passed to all vis and
2.) to fix any wiring problems inside the subvis if you find some or even better upgrade to the latest version of NI-Motion which is 7.2 with the update to 7.2.1.

Jochen

[peterk3]

So I updated it and then changed the axis on the front panel to two.  There is still no motion though.  Axis one is still working fine when run off the trigger box with the code, axis two runs fine off of the simple one axis motion but cannot run off of the same triggering code.  When I probed it all axis read two as well.

Thanks

Keith

[Jason N]

Keith,

Were you able to determine the version of the Motion driver you were using?  Perhaps this could still be a factor here.

Jason N

[Jochen]

Keith,

here is another question: Have you changed the wiring for your trigger signal when you switched to axis 2?

By default each trigger input is assigned to the corresponding axis. That means if you use the high-speed capturing trigger feature with axis 2 you will also have to wire your trigger signal to trigger input 2.

Does this solve your problem?

Jochen