LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Image acquisition not functioning after upgrading computer

Hi all,

 

I've run into a bit of a snag with our LabVIEW program. This program was written by someone that no longer works at my company and his VI scripts and installer do not exist, at least no where that we can locate. We've migrated the executable as well as the LabVIEW runtime environment over to a new Windows 7 PC (the original computer was running Windows XP). The program loads as it should but when it comes to the image acquisition within the program, the camera image is garbled and basically useless.

 

Using NI MAX, I am able to detect the camera and I can set it to the settings from the original PC but the image is even scrambled inside NI MAX. The camera in question is an ATV Oscar F810C which is detected as such by NI MAX. I've updated the Vision runtime to the February 2014 build available on NI.com (about a 2GB download). Here are some screenshots of the original PC's settings in NI MAX:

 

XP Camera Driver in MAX.jpg

 

 

XP Camera Settings in MAX.jpg

 

 

In reality, the image in NI MAX should look like this:

 

XP Camera Image.jpg

 

 

On the new system with the same settings it looks like this:

 

Scrambled Image NI MAX Win7a.jpg

 

 

And when running the program on Windows 7 it looks like this:

 

Scrambled Image Win7a.jpg

 

 

If I change the Video Mode to one of the lower res ones, such as the first greyscale 1024 x 768 option, the image stops being scrambled inside NI MAX and I'm able to see the image properly. However, the image acqusition inside the program still does the same thing. Without having any information on the contents of the program or access to the original files, it would appear to be some kind of driver issue since the setup works fine on the old system.

 

Any ideas on what may be the issue?

0 Kudos
Message 1 of 11
(2,797 Views)

Don't you need to still install the camera's Windows 7 driver?

 

 

0 Kudos
Message 2 of 11
(2,792 Views)

Is your LabVIEW version compatible with your Windows version?

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
0 Kudos
Message 3 of 11
(2,789 Views)

The camera's Windows 7 driver is installed. That was one of the first things we did as well as checking Windows 7 compatibility.

 

I'll review it again just in case.

0 Kudos
Message 4 of 11
(2,786 Views)

According to this post here, my version (2012 DS2) is compatible with both Windows XP (x86) and Windows 7.

 

Sorry, I should have posted my software version in my original post Smiley Sad

0 Kudos
Message 5 of 11
(2,778 Views)

It may be that you have to download a WIn7 driver for the camera.  Dll(s) might be incompatible.

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
0 Kudos
Message 6 of 11
(2,755 Views)
This is probably data loss due to interactions by the OS/CPU/BIOS regarding power saving modes combined with the isochronous transfer mode used by FireWire.

Point Grey put out a great app note about this issue: http://www.ptgrey.com/support/downloads/documents/TAN2010003_Image_tearing_causes_and%20_solutions.p...

Eric
0 Kudos
Message 7 of 11
(2,739 Views)

@billko wrote:

It may be that you have to download a WIn7 driver for the camera.  Dll(s) might be incompatible.


Sorry, I did not see that that was one of the first things you did.  😞

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
0 Kudos
Message 8 of 11
(2,722 Views)

@Bluecheese

 

Great, I'll give that a shot and see what works. We were using a system with an integrated video card whereas the XP system had a separate graphic card and we were thinking that may be a part of the issue. We've also had some issues with other software not installing properly on the Windows 7 PC so we're moving to a different one to see if we can eliminate all those variables as well.

 

@biilko

 

No worries! It makes sense to double check the small stuff, it's easy to overthink a problem at times!

0 Kudos
Message 9 of 11
(2,709 Views)

We've tried a few suggestions that are applicable to our setup from that PDF you sent. We were able to get the system to run for about 5 minutes before the issue re-appeared. We shut down the system and took the old Firewire card and installed it in the new system which also helped reduce but not eliminate the problem. The new system is running much better - we think the old one had some drive issues potentially. However, the issue still exists.

 

I'm not sure what to try at this point. Based on that PDF it would seem like the buffers are filling quicker than the PC can access them but that seems very odd considering all the hardware is newer and should have better performance than the old.

0 Kudos
Message 10 of 11
(2,694 Views)