Help! 2009 took out my ability to make vision applications for production floor.

[muks]

*****message deleted*******

Message Edited by muks on 08-25-2009 08:46 PM

[FooFooFoo]

Ok, so I just got called out on the floor again.  Production couldn't use one of my applications on the machine.  I use PCI-1411 cards for image acquisition and the 2009 drivers deleted the 1411 drivers but didn't reinstall new ones.  The line was down again.  All I had to do was go to device manager and update driver and it suddenly found the 1411 driver and started working.  The card said it had a Multimedia driver installed and was happy to sit there and not work.

Lesson learned, check every device in the computer after loading the 2009 drivers, they may not load properly.  This is the first time I have ever seen this.

Also if you are looking into the include problem for install let me clarify exactly what I did:

I loaded labview 2009 trial version and 2009 drivers on a machine that 8.6 vision/acquisition and drivers.

I went back to 8.6 and compiled my application.

It reported missing vis when I installed it on a machine that previously worked great with 8.6 runtime and application.

I recompiled my application with includes for:

     NI Vision Runtime8.6

     NI-IMAQ 4.3

I ran this installer on my deployment machines and I got no video in them.

I then installed IMAQ Acquisition 2009 on the deployment machines and everything started working with the above caveat with the 1411 card.

Best wishes for a brighter future.....

[JesseD]

---

MGould wrote:
I don't think you understand observation 1.  He installed 2009 in parrallel with the 8.6 toolset.  He didn't use 2009 to develop the application.  He was only trying 2009 as an experiment, but when he went back to 8.6 to work on a piece of code that was developed in 8.6 it automatically pulled inthe 2009 vision VIs.  When compiling with 8.6 it used the 2009 VIs for vision runtime/acq rather than using the 8.6 VIs.  If this is intended, it makes no sense.  Why would NI would allow different version to be installed at the same time if they always use the newest vis rather than the ones they came with?  Why wouldn't they just remove older tool sets forcing you to go to the new tools?

---

Thanks for the clarification.  He should be able to use LabVIEW 8.6, Vision Development Module 8.6, and Vision Acquisition Software 2009 to create an application that works with the Vision Run-Time Engine 8.6.  If Vision Development Module 2009 is installed, then the application will require the Vision Run-Time Engine 2009 as well.  I'll do some additional testing of this situation on the machines I have set up.

Perhaps this will help answer some of the other questions. Both Vision Acquisition Software 2009 and Vision Development Module 2009 install support VIs to LabVIEW versions 8.2, 8.5, 8.6, and 2009 as well as upgraded system DLLs (to get bug fixes and new functionality).  By installing Vision Acquisition Software 2009, the LabVIEW 8.6 VIs and the system DLLs were also upgraded.  These are still LabVIEW 8.6 VIs, but now they reference the new versions of the DLLs.  Vision Acquisition Software 2009 only contains a subset of the Vision VIs. The VIs specific to the Vision Development Module will continue to work with the new versions of the support VIs and the system DLLs, which is why we don't force an uninstall of the older version of Vision Development Module.

Regards,
Jesse

[BlueCheese]

---

FooFooFoo wrote:

Ok, so I just got called out on the floor again.  Production couldn't use one of my applications on the machine.  I use PCI-1411 cards for image acquisition and the 2009 drivers deleted the 1411 drivers but didn't reinstall new ones.  The line was down again.  All I had to do was go to device manager and update driver and it suddenly found the 1411 driver and started working.  The card said it had a Multimedia driver installed and was happy to sit there and not work.

---

Any chance you were installing software over remote desktop?

Eric

[FooFooFoo]

No unfortunately I do everything the old fashioned way... with a thumb drive and shoe leather.  I've been thinking about it and I'm trying to recall if maybe I failed to reboot that machine because it worked on all the others.  Oh well...... water under the bridge, hopefully I'm good for a year.

[Philip B]

I had a similar issue when trying to work simultaneously on a legacy branch of an application (in LV 6.1) and the development branch (in LV 8.5).  I found the following Developer Zone article to be helpful:

http://zone.ni.com/devzone/cda/tut/p/id/6524

However, the conclusion, "use a separate computer for each toolset", was not feasible.  Instead, I partitioned my hard drive using Acronis and setup a separate boot partition for each incompatible toolset.

Foo, I think the main relevant point here is that you can't assume backwards compatibility with any major revision of any toolkit or driver from NI.   They have a history of maintaining "somewhat" backwards compatible toolsets, but there are enough differences that you can get yourself into trouble.  In your case, I'd recommend building hard drive images, including the OS, and deploying those instead of user-driven installations.  That way, you could potentially "experiment" with 2009, by loading the new disk image with 2009.  If that doesn't work, you can reimage the hard drive with the working 8.6 configuration, without even having to worry in real time about why the experiment isn't working.

-Phil

[JesseD]

I have performed several tests, but I have not been able to reproduce the issue.

I started with a system running LabVIEW 8.6, Vision Development Module 8.6, and Vision Acquisition Software 8.6 and built an application using both Vision and NI-IMAQ VIs. I built this application into an installer including NI-IMAQ 4.2 and the Vision Run-Time Engine 8.6 and installed it on a clean machine. The application ran as expected.

I then installed LabVIEW 2009 and the Driver DVD (which included Vision Acquisition Software 2009 drivers) on the development system. At this point, I was still able to open, run, and build the test project in LabVIEW 8.6.

I built another installer for the application in LabVIEW including NI-IMAQ 4.3 (new for Vision Acquisition Software 2009) and the Vision Run-Time Engine (still version 8.6).  I ran this new installer on the same machine as the previous version, and the application ran as expected (displaying and processing images). I then tried the new installer on a clean machine, and it ran as expected there as well.

 I'm glad that you are up and running now, though I wish I knew why the images did not display after you rebuilt and redeployed the application with NI-IMAQ 4.3.  Let me know if I can test anything else out for you while I have these machines set up.

Regards,

Jesse