Jump to content

Can't include a vision library .vi in a deployment


Recommended Posts

Hi,

I'm deploying a vision application (LabVIEW 7.1.1, Vision development module 7.1.1)

I have both the LabVIEW and Vision run time engines at 7.1.1

When running the installed application on the target PC many NI vision vi's used are not found.

Most are solved by including libraries in the build, but one isn't.

imgCopyAreaWithOccur.vi (used in IMAQGrabAcquire.vi) can be found in DLLcalls.llb.

However, if I include either imgCopyAreaWithOccur.vi or the full library DLLcalls.llb in the installer, the vi is still listed as missing.

Any ideas where I'm going wrong? :headbang:

(As you may have spotted by now this is a duplicate of a post on the NI discussion forums.)

Its my first deployment of a vision application, though I have successfully deployed non-vision LabVIEW apps before.

Thanks

Bandit.

Link to comment
Hi,

I'm deploying a vision application (LabVIEW 7.1.1, Vision development module 7.1.1)

I have both the LabVIEW and Vision run time engines at 7.1.1

When running the installed application on the target PC many NI vision vi's used are not found.

Most are solved by including libraries in the build, but one isn't.

imgCopyAreaWithOccur.vi (used in IMAQGrabAcquire.vi) can be found in DLLcalls.llb.

However, if I include either imgCopyAreaWithOccur.vi or the full library DLLcalls.llb in the installer, the vi is still listed as missing.

Any ideas where I'm going wrong? :headbang:

(As you may have spotted by now this is a duplicate of a post on the NI discussion forums.)

Its my first deployment of a vision application, though I have successfully deployed non-vision LabVIEW apps before.

Thanks

Bandit.

Did you install the NI-IMAQ drivers on the target PC?

Link to comment
Did you install the NI-IMAQ drivers on the target PC?

Yes, but since my post I noted this...

On my development machine IMAQ is at 3.5.0, but on the target machine it's at 3.1.0.

I don't actually want to go as far as 3.5.0 as it doesn't support Win NT. In the end one of the targets for my app is an NT4.0 machine.

I don't know why my development machine has IMAQ 3.5.0, as the vision development module 7.1.1 CD installed to it only has IMAQ 3.1.0.

I think I should roll back the development machine, but I'm not sure if this could cause a further problem. These are just the hardware drivers, right?

Link to comment
Right.

Job done. Driver mismatch was the problem. Installations on NT and XP now work.

But I'm getting the NT target replaced with another XP target to ease deployment of the next release , and enable me to use latest vision dev tools and drivers.

Thanks to Jacemdom and Crelf :thumbup:

Bandit

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.