Machine Vision

cancel
Showing results for 
Search instead for 
Did you mean: 

Does the vision builder run time license only allow a single session?

Solved!
Go to solution

I have created several VBAI routines to this date.

One of the facilities wants to use 2 of them at once.

 

It seems that they can run a single VBAI at a time though.

What options do I have?

 

1) Will an additional run-time license allow 2 sessions at once?

2) Create a hybrid VBAI that incorporates the functions of both?

 

Thanks

Jonathan Cliffen

0 Kudos
Message 1 of 7
(4,755 Views)

I am not aware of a limitation on the number of instances you can run at once. Just to be clear, are you launching the Vision Builder AI executable to run your inspections. If you double click on the executable again, it will launch a new instance of the Vision Builder AI that can run at the same time as the first one. One important restriction is that both instances can't use the same inspection and if you are using two different inspections, they can't use a resource that is exclusive (i.e. like a camera, framegrabber, or serial port).

 

The other way you can have multiple instances of Vision Builder AI run your inspections is to use LabVIEW/C/dotNET and the Vision Builder AI API to launch a VBAI Engine (you can call this function multiple times with different names and get a different session to each engine), and then each engine can load a different inspection and run them simultaneously. You will get load errors if you try to open the same inspection or if the inspection uses a resource that is already in use as mentioned above.

 

If you are doing something else to try and launch multiple instances, or if one of these methods isn't working, let me know.

Thanks,

Brad

0 Kudos
Message 2 of 7
(4,751 Views)

The applications are using independant hardware and are used for different purposes.  So no conflicts there.

 

The first session is being launched using the Vision Builder AI 2010 executable.

When we relaunch the executable, the previous session receives focus from the OS (Win7) instead of launching a new Welcome screen.

I am sure it is a Run-Time license since the configure inspection option is very limited and can only adjust some parameters, not add/delete process steps.

 

This is completely different to the Developer License I have on my machine (Win7) which will launch a new Welcome screen/Inspection with each command.

 

Hope we can shed light on the issue!

Jonathan

 

 

 

0 Kudos
Message 3 of 7
(4,740 Views)

This is not expected. Could you please double check your Vision Builder.ini located in your Vision Builder folder and verify you have the following key in the [Vision Builder] section:

allowmultipleinstances = True

Make sure this token is only listed once and it has the value True in the ini.

 

If this is the case, let me know.

Thanks,

Brad

0 Kudos
Message 4 of 7
(4,738 Views)

Please find the <Vision Builder.ini> attached

The file is markedly different from the file on my Development PC.

 

 

0 Kudos
Message 5 of 7
(4,724 Views)
Solution
Accepted by topic author JCliffen

Not sure how your INI got into this state. You can just copy the INI from your dev machine and that will fix the problem.

 

Sorry I don't have a better explanation for what happened to your INI, but at least this explains why you couldn't launch multiple instances.

Thanks,

Brad

0 Kudos
Message 6 of 7
(4,718 Views)

The INI file replacement corrected the issue.

Thanks for your help,

Jonathan

0 Kudos
Message 7 of 7
(4,709 Views)