Does NI-MAX version need to match a certain VAS version?

[sdmadman]

See also http://forums.ni.com/t5/Machine-Vision/How-do-I-get-LV2009-to-see-my-PCIE-1433/td-p/3132887. Possibly this issue is related. In that discussion, I was trying to get the driver for the PCIe-1433 installed. We found that even though I'm using LV 2009, I needed VAS 2010 March to get the driver.

So: now Device Manager sees the framegrabber, which is progress, and the VI I got from a vendor loads without complaining (an earlier problem - the VI couldn't find any of the IMAQ vi's).  But, two symptoms:

1. When I start the VI (or run the executable the vendor provided) I get a message in IMAQ Init.vi "The requested FPGA bitstream file could not be found." The string wired into IMAQ Init is "Img0". I'm guessing this is something I need to configure in NIMAX, so I try to start it, BUT...

2. NI-MAX either goes away while/after "loading plugins" or it pops up a message that is has "detected an unexpected error". Details box says the exception occurred in NIMax process in function (unknown). It directs me to a log (I'll attach the log and dump file). I click continue and it again goes away while/after loading plugins.

I just noticed another thing: when the error pop-up points me to a log file, it's directing to a file that it created the LAST time it failed, then it creates a new.dmp and .txt file. When it fails AGAIN, it renames the .txt file .log.

Anyway all this looks to me like a version compatibility issue. I'm downloading the system driver set for August 2010, thinking I need to attempt to match the VAS version. That download is at least 2 hours from completing, so I thought I'd see if I'm on the right track.

Thanks!

MADman

[sdmadman]

Updating to SDS-Aug10 changed behavior some, but it's still broken. MAX has trouble starting, but it does start, throwing exceptions up left and right, and still doesn't see the PCIE1433.

The application the vendor provided still throws up the same message "The requested FPGA bitstream file could not be found."

OK, esteemed forum. Tell me what I broke! :manembarrassed:

MADman

[nikale]

Hi MADman,

What camera are you using? It's worth looking into the camera file settings. 

In the meantime here are some resources I found while looking into this issue.

NI Vision Acquisition Software Release Notes March 2010:

http://download.ni.com/support/softlib//vision/Vision%20Acquisition%20Software/March%202010/visionac...

NI System Driver Ser August 2010:
http://www.ni.com/white-paper/12083/en/

What Version of MAX Is Installed with the NI-DAQ and NI-DAQmx Drivers?:

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

MAX 4.7.x Known Issues:

http://www.ni.com/product-documentation/11485/en/

I hope this information helps!

- Kale

[sdmadman]

Hi Kale

Hmm - does it matter if the camera is connected?  After I broke everything by uninstalling / reinstalling drivers, I just left the camera unpowered, with the goal of talking to the framegrabber before even bothering with the camera. At the moment, MAX doesn't see the framegrabber even though Device Manager does.

The camera is a very custom thing - a sensor vendor's evaluation system. I'll ask them about the camera file settings.

I have to return the system for an update, so I'll check out those links, but I won't be able to act for a couple weeks.

Thanks for the links!

MADman

AKA Mike Doyle