absolute position won'[t work

[shalloras]

Matt,

Thanks for the reply.

This behaviour occurs for both axes, so I am leaning to your idea of the MAX installation needing to be repaired. 

Let me throw in one more wrinkle.  We recently purchased LabVIEW 2011.  The project we have been talking about was developed in LV8.5.  Since I am intending to repair, would it be too big a leap to go ahead and recompile this project in the 2011 environment, which would install the latest MAX, etc.

Sean

[shalloras]

Matt,

Tried repairing the MAX installation but it did not fix the problem.  Repair ran to completion with no errors so I assume I have a good installation of MAX at this point.  Could there be some kind of incompatibility between MAX (4.8) and Motion 8?

Sean

[Matt_McLaughlin]

Hi Sean,

There should not be an issue with compatibility between your versions of MAX and NI-Motion. You should be able to open and compile the VI in LabVIEW 2011 without many troubles. There may be some small problems here and there as with any software version upgrade, but it will certainly be simpler to upgrade now than to wait for an even larger jump in versions.

I think that this may be a very good idea as it sounds like there are some considerable problems with the current system if you are unable to perform an absolute move in LabVIEW and unable to perform any sort of movement in MAX.

[shalloras]

Matt,

Uninstalled LV8.5 and installed LV2011.  Checked in MAX that all the software versions were updated, so MAX 5.0, MOTION 8.3.

Had the same problem.  So, doesn't look like a driver/MAX problem.  Is it possible I have a setting in MAX that is preventing me from making this move?

Sean

[Matt_McLaughlin]

Hey Sean,

From the screenshots you attached above, the settings in the 1D Interactive tab look fine. Could you please include a screenshot of the Motion I/O Settings tab for the axis you are working with? Also, just clarify, which of the following do and do not work?

In MAX: Relative Position move, Absolute Position move, Velocity move

In LabVIEW: Relative Position move, Absolute Position move, Velocity move

This info may give us some mopre specific ideas of where the problem is coming from.

[shalloras]

Matt,

Here are the screenshots, X axis first, followed by Y axis.

What works in MAX:  cannot make any move in MAX, have tried Velocity, Relative and Absolute. 

What works in LV:  can make Velocity moves and can find reference and make an offset move from the reference, which I believe is either relative or absolute.  Cannot make absolute or relative position moves in LV.  Have tried the example programs for motion and they can't make the absolute move either.

[shalloras]

Matt,

Tried something else.  Set up a new computer with a fresh install of LV2011 and drivers and Motion 8.3.  I didn't load any of the VI's I have been working with.

I was able to get the absolute move to work fine in MAX and in the example VI's.  Worked with relative move and velocity move in MAX as well. 

Then I loaded the VI I have been working with, which had the same old problem, absolute move would not work.  Then I tried it in MAX again and it DID NOT WORK!  The example program wouldn't work either!  Just like before, it just goes through the Start Motion VI and doesn't do anything, no errors, no indication that anything is moving.

So now I am thinking that there is a conflict with one of the VI's I am using and I believe it is the Joystick.VI.  That is the only difference in this code and code on three other tools that work just fine.

Is it possible that the Joystick VI is somehow setting something that inhibits absolute and relative position moves 'permanently' on this computer.

Sean

[Matt_McLaughlin]

Hi Sean,

I saw that you've opened up an email service request regarding this issue as well. Is the VI that seems to be causing this problem the one you passed along in that email? If there are any updates to the VI, please pass it along either by email or the discussion forums. Larry and I will be working to test this VI and determine whether we can reproduce this issue and why you are seeing this unusual behavior.

Let us know if you have any additional questions or updates.

Thanks!

[shalloras]

This is the VI that is causing the trouble.  Thanks for looking at this!

Sean

[Matt_McLaughlin]

Hi Sean,

I think you forgot to attach it here, but Larry and I are looking into the issue with what you sent him. Thanks for your patience!