Motion Control and Motor Drives

cancel
Showing results for 
Search instead for 
Did you mean: 

error -70149 axes tht are part of a vector space...

I am using one motor to perform the following:
 
When the "Home" button is pressed on the front panel, the motor finds the forward limit, reverses direction then finds home.(See Screen shot 2)
 
When the "Run Test" button is pressed, the motor rotates 45 degrees.( See Screen shot 1)
 
 Here's where I run into a problem. After homing THEN pressing Run, I get the following error: error -70149 occurred at Blend Coordinate 1. Axes that are part of a vector space are either in velocity mode or have different operation modes.( see attached screen shot 4-17-07) I do not see the error in the homing sequence, only during the Run test sequence.
 
However, if I launch the VI and press "Run Test" without homing first, the motor rotates without error.
 
I placed a circle on sreen shots 1 and 2 of how the axis is configured for homing and run test.  I think I am performing two different axis configurations, but I am not sure on how to fix my problem.
 
One thing I'm not sure of is what "vector Space" is. Is this the settings from MAX?   
 
 
 
 
 
0 Kudos
Message 1 of 5
(3,835 Views)

Poba,

could you please provide some more information about your system configuration? Here are some questions:

  1. What type of motion control board are you using?
  2. What's the NI-Motion driver version (the latest is 7.5)
  3. You have mentioned some more screenshots but your post contains only the screenshot of the error message.
  4. Could you please provide some sample code? This would make things much easier.

In general a vector space is a group of axes that can contain up to 3 axes (X, Y, Z). You can perform moves on a vector space as you would on a single axis. All axes in a vector space start and stop at the same time. E. g. this allows you to perform linear vector moves in a 3D space.
You can add axes to vector spaces in MAX but I recommend to configure vector spaces in your application if required. This makes it easier to avoid errors as your application keeps the full control over the operating modes for your axes.

Best regards,

Jochen Klier
National Instruments Germany

 
0 Kudos
Message 2 of 5
(3,832 Views)

I have a PCI-7344 board , driver version is 7.0.03002.  About three years ago I set up a 3 axis application that works well.  Actually I was surprised that I got it working since it was my first attempt at Labview and motion. I copied a lot of code from the 3 axis application to the current 1 axis app.

 

Attached is my code.  I apologize in advance if it looks sloppy, as I am learning as I go. 

 

Thanks for your help.

 

 

0 Kudos
Message 3 of 5
(3,828 Views)

I found my problem.  I was using VI's that read vector space. When I replaced those with read position, everything worked.

 

 

0 Kudos
Message 4 of 5
(3,820 Views)
Great. In fact that was my assumption before you have posted your code but I wanted to be sure.

Have a great day!

Jochen
0 Kudos
Message 5 of 5
(3,814 Views)