Motion assistant: Cannot convert to LabView file

[James James]

Hello,

I would like to ask for help on problem:  the file generation from Motion assistant to Labview

Background:
1.  Use Motion assistant to generate 2 or 3 steps of motion.

2.  Save it.

3.  Inside Motion assistant, Use Tools>>Generate Code>>LabView Diagram.

Result:

After I doing this, the LabView file is generated.  But, it is a file containing a few control switch (without any other key components to produce the motion control function).

Thus, what is the problem behind?   

Thanks

James

[Jochen]

Could you please provide some more information? Which version of LabVIEW and Motion Assistant are you using? Can you see the Motion Assistant palette in LabVIEW? If not please reinstall Motion Assistant.

If you can't solve the issue by reinstalling please post a Motion Assistant script and the resulting LabVIEW code to the forums.

Thanks,

Jochen Klier
National Instruments Germany

[James James]

Hello Jochen,

The Labview version:  7.1

Motion Assistant:         1.3

I found that Labview has a Motion assistant palette which contains the Motion assistant modules(icons)

Could you please tell me where is the option to set such that the software work again?

Regards,

James

[Jochen]

James,

Here is a potential solution:

There is an option in LabVIEW under the Tools » Options dialog called "Treat read only VIs as locked." If a read-only VI is opened, it is opened in the "Run" mode. If a VI is in this "Run" mode, code generation will not work.

By default, this setting is off. However, if you are using Source Control through LabVIEW, when configuring the source control interface in LabVIEW, you are asked if you want to turn this setting on.

Motion Assistant installs its LLBs as read only because they hold the templates that should not be edited. If the Locked setting is set and you are trying to generate code, you will get an empty VI

To generate code, uncheck the setting under the Tools menu or set the LLBs as writable.

If this doesn't help please attach the script and the code that was not generated completely to give me an idea what's going on. Also please try reinstalling Motion Assistant.

Best regards,

Jochen

[James James]

Dear Jochen,

There not exists       Tools » Options dialog called "Treat read only VIs as locked."      

Could you explain a bit much?

Regards

James

[James James]

Dear Jochen,

I had tried what you said.

1.

Treat read-only VI as locked              :  uncheck

Enable window explorer for LLB file  :  check 

Note: basically, I have reset the machine after set the options

2.

Uninstall Ni-motion ->  no-reboot -> install again

After I have do this steps individually,  Nothing has corrected.

What is the problem then?

Regards,

James 

Note:

Attached please find the Motion assistant source file for your reference

[James James]

Dear Jochen,

Attached please find the Motion assistant file ( the previous one is Labview file converted, for your reference)

Regards,

James

[James James]

Hello,

I had re-installed the software, Ni-motion, again.   I have reboot the machine at right times.

Please suggest me how to fix the problem such that the Ni-Motion, Ni-LabView can run in the right manners.

Regards

James

[James James]

Hello,

LabView CANNOT WORK with Ni-Motion to convert file (motion file to Labview file)

Why????

Can any one tell me?????

THANKS in advance

James

[Torba]

Hello James,

Thank you for contacting National Instruments.  I tried to open your script, but I keep getting a prompt that I do not have a motion card installed that supports one of the steps that you are using even though I have all of the virtual drives installed on my machine.  Which motion card are you using?  When you found the "Treat read-only VI as locked" option in LabVIEW, was the option checked when you found it?  Have you accepted the changes, and restarted LabVIEW before generating the script again?  Does any script produce the same problem? 

By default, the Motion Assistant should be able to generate code if no changes are made to any of the settings for LabVIEW and the Motion Assistant.  If nothing else, try reinstalling LabVIEW and then reinstall the Motion Assistant.  Do not change any settings for both programs.  Just try to generate a simple script, and see if code generates.

Regards,

Mike T

National Instruments