Vision Assistant / Vision RunTime License

[Cabman]

Is it possible to force an application to use the Vision RunTime License instead of Vision if it is installed?

We use the NI License Manager to checkout licenses from our server. I have the Vision Development System setup to be checked out as a named user (myself) for development. I have the Vision Run Time engine setup to be checked out as a Computer based license when someone else is logged in. The idea is that I'll use Vision Assistant to develop, but when I release the software, the operator on the production floor will login and a RTE license will be checked out instead.

I use this model with TestStand/LabVIEW. i.e. When I log in and develop I use the TestStand Sequence editor and the LabVIEW development system. When the operator logs in, they use the TestStand Operator Interface and a LabVIEW runtime license. This frees the development system to be used elsewhere while the system is used in production. All I have to do is configure the LabVIEW adapter in TestStand to use the appropriate LabVIEW.

The problem with Vision is even though I have a LabVIEW application that runs with the Vision Run Time engine, if Vision assistant is installed it tries to check out a Vision Development license instead and fails if someone else is logged on.

The only way I know how to make it work currently, is to uninstall Vision Assistant when I want the app to check a RTE license. Not very desirable.

Using Vision Assistant , Vision, Vision Run Time Engine, and Vision Aquisition all 8.5

[wbadry]

Hi Cabman,

     I inferred from your message that you differentiate between your development environment and user environment by users credintials. so based on user his rights to develop or just to use runtime engine is automatically chosen.

    concerning IMAQ, first of all, You should have a runtime licernse as IMAQ requires deployment license on each target machine. So, when user logs in, all what he needs is LABVIEW runtime engine, IMAQ runtime engine and IMAQ runtime License.

[Cabman]

Yes, if I do not have Vision Assistant installed on the machine and a user is logged in, it will checkout a 'deployment license' from the server and use the runtime license to run the vision VIs.

The problem is if Vision Assistant is installed, the system tries to check out a 'development license' and will fail because it is set up only to allow me as a named user to use it.

What I need is a method to select which license to use, similar to how I can set up TestStand to use the LabVIEW development system or the LabVIEW runtime license. I don't know of anyway to do this now except to uninstall Vision Assistant.

Dave

[wbadry]

You may work around this by compiling your peoject using application builder and making your user install your project instead of accessing the VI directly