Cannot log into NI1742 after it is set to automated inspection

[Reneance]

Hi Brad,

Thanks for this very informative explanation.

Question:  I I use labview to make a supervisory interface, do i need a runtime license or does it use the VBAI/smart camera license/runt time license?

I have another variation that im working on but not yet on actual target.  It uses select inspection and I separated the User UI from the main inspection program.  Also the inspection per device was also broken down.

Please see attached and comment if this would be a good one instead of doing the labview code.  I tested one main vision program (5x5) and noticed delay when switching between inspection. also concern is if the user turn off the select inspection icon on inspection interface.

Hope to get more info.

By the way your comment on VI running in background and showing no front panel conflict with discussions in this forum.  I read somebody recommended to use front panel properties to reveal the front panel and i tested it and does not work.  Ill check if it comes from NI, if it is then it confuses use users.

thanks for the great help.

Regards

Bobot

[Reneance]

Hi Brad,

this link tells of showing front panel of a VI.

http://digital.ni.com/public.nsf/allkb/EA5EEEBB773A81A2862572D0001BF85F

please verify if this is possible because i used together with instructions on transferring VI to RT via llb.

just to clarify things for us users.

Thanks

Bot

[Reneance]

Hi brad,

to correct previous message, the link instruction did not work for front panel open.

I tried the vbai api example using local host (the smart cam is with the customer).  

what i intend to do is run the inspection continously and not run once.  I  cannot get the image out if run continuous.  can only get it if run once.

thanks

bot

[Brad]

The Front Panel open will only work when the inspection is run on Windows (or Simulation mode). When the inspection is run on the target, so is the VI, and the VI's front panel is opened on the target, but there's no way to see it since RT targets don't display VI front panels like Windows does.

The product select could work as well, but as you mentioned there will be some delay when switching inspections, and the Stop Product Select button will be available to users in the VBAI Inspection mode. But even if you don't do product select, the stop button will still be available in the VBAI Inspection Mode, so if you're worried about other users pushing buttons they shouldn't, maybe a LV UI is a better choice anyway.

The reason the image probably isn't returned when you're free running is that the target doesn't have enough bandwidth to send it. You could consider changing to a Run Once model, get the image, and then immediately run once again in a loop. This would ensure the target isn't so busy with inspection that you can't communicate with it and I would imagine you wouldn't see too much of a reduction in parts per second, and then you could also remove several of the delay steps that aren't involved in looping on a state until something happens.

Hope this helps,
Brad

[Reneance]

Hi Brad,

This is of great help.  Im now becoming to appreciate more the strength and weaknesses of the system.

Im now doing an LV to just handle the UI and running once and loop and have shared variables to communicate.

Final question, if i use LV and part of it is to have imaq create, do i need a runtime vision license if i deploy to my target host which doe snot have labview installed?

thanks

bobot

[Brad]

Good question. When you create your LabVIEW exe for deployment to other PCs, one of the options is to include any shared variables your LV app uses and automatically deploy them. If you create an installer for your LV app, you can select which other installers to include. Vision Builder AI API is an option as well as Vision Shared Resources. Both of these are free for deployment and cover controlling VBAI, and creating/disposing images, using the image display control, and reading/writing images to disk. Anything that involves image analysis/processing would require the vision run time engine which does have a fee, so as long as you do all your image processing in VBAI on the target, you won't have to pay to deploy your UI that controls VBAI to other PCs.

Hope that helps,

Brad

[Reneance]

when you say "so as long as you do all your image processing in VBAI on the target, you won't have to pay to deploy your UI that controls VBAI to other PCs.", if i use vbai-interface get inspection image its free with vbai?  what about if i use imaq create and imaq copy, is this covered with VBAI run time license as you mentioned "Both of these are free for deployment and cover controlling VBAI, and creating/disposing images, using the image display control, and reading/writing images to disk."

So anything that will require functions under "image processing" and machine vision" will need run time license while NI Imaq, imaqdx and imaq io is free to use together with VBAI API?  how about vision assistant?  or only the image display control with imaq create?  if i use imaq copy?

thanks

bobot

[Brad]

You can get images from the VBAI API in your deployed LV app for free. NI-IMAQ deployment is free, but IMAQdx requires a license for each deployed system since it doesn't require any NI hardware. If you are using Smart Camera though, you don't need any drivers installed on your deployed PCs. Here is a link to a list of VIs you can use for free in a deployed app:

http://digital.ni.com/public.nsf/allkb/392E8F10F049918986256A3B005D484A 

Vision Assistant uses image processing/analysis VIs so you would need to purchase a Vision Run Time Engine to use any of those VIs in a deployed app. Feel free to try what you want and see how it works to better understand what you and can't do.

Hope this helps,

Brad

[Reneance]

Hi Brad,

Thanks for the reply.  Im now trying my new LV and works as I wanted (simulation).  Ill test this today on the target.

thanks agagin.

Regards

Bot

---

@Brad wrote:

You can get images from the VBAI API in your deployed LV app for free. NI-IMAQ deployment is free, but IMAQdx requires a license for each deployed system since it doesn't require any NI hardware. If you are using Smart Camera though, you don't need any drivers installed on your deployed PCs. Here is a link to a list of VIs you can use for free in a deployed app:

http://digital.ni.com/public.nsf/allkb/392E8F10F049918986256A3B005D484A 

Vision Assistant uses image processing/analysis VIs so you would need to purchase a Vision Run Time Engine to use any of those VIs in a deployed app. Feel free to try what you want and see how it works to better understand what you and can't do.

Hope this helps,

Brad

---