02-25-2008 01:28 PM
02-28-2008 12:21 PM
03-03-2008 12:23 PM
Hello NH,
Thanks for your reply, and I'm glad that you don't see any impediments with using LabVIEW to complete the applications I'm planning to use it for.
As far as the cameras go, I was having massive problems just trying to get them to work with Cam2Net, the software with which they are supposed to connect simply. So before I got any further on the firmware updating, I sent them to an out-of-town associate to get them hooked up in his lab, so that we'd be able to at least get some images from them. This means that they are now working with Cam2Net 2.3.1 and are acquiring images without issue. However, the first few steps of the camera frimware update manual involve doing a few steps in Cam2Net 2.2.x, before you uninstall it and install 2.3.1. The reason for this being that 2.2.x has a "driver installation tool" that can perform ceratin tasks that nothing in 2.3.1 seems to be able to do. I assume that my associate did not complete these steps before installing 2.3.1. The steps are as follows:
1) Change the Intel Pro 1000 card from a Grabber Device to an Ethernet Controller
2) Uninstall any filter drivers
Once it gets past these steps, the updater manual requires you to install Cam2Net 2.3.1, and thus everything from that point on I should, barring any unforeseen tragedies, be able to complete the rest of the steps and update the firmware. But in order to proceed with the confidence of someone who is not going to destroy their boss' $4000 cameras, I'd like to make sure that my drivers are in an acceptable configuration.
When I open the "Driver Installation Tool" that is on my computer now with 2.3.1 (much different from the tool of the same name in 2.2.x), it lists my driver as a "Cam2Net High-Performance IP Device Driver". This brings up a few issues:
1) Does this mean that the driver is already an Ethernet Controller, and can perform all the necessary updating tasks I need it to?
2) If so, which of the 4 ports do I use? (in the manual they suggest that you write down the MAC address of the driver you change to Ethernet Controller, and make sure it matches in this new "Driver Installation" window...but then again, the NIC they use only has one port)
3) If I try to proceed in the hopes that this configuration is correct, is my worst case scenario that nothing happens, or is it that I open an all-encompassing black hole that destroys the universe and ruins my day, or somewhere in between?
So this confusing pile of words is where I stand in the Firmware Updating world.
Anything you can think of to help keep me heading in the right direction would be wildly appreciated.
Thanks again,
Cheers,
W
03-04-2008 06:42 PM
03-05-2008 10:36 AM
NH,
no problem...i wasn't exprecting that the NI forum would be able to extend into the realms of Cam2Net, but i thought i'd try. However, there is something I think you might be able to hlep me with. After installing LabVIEW 8.5 on my computer, the cameras I was using with such carefree jubilance through Cam2Net have stopped being able to connect to the software. The Cam2Net program now crashes any time I try to connect to the cameras, and occasionally heeds warnings of "subnets do not match!". Aftter looking into the problem, and noticing that the problem seems to have coincided with the installation of LabVIEW, my only thought is that perhaps LabVIEW installs its own driver for the GigE interface, and that is conflicting with the Cam2Net software.
any idea on whether this is true, and how to get around it if it is?
W
03-06-2008 06:19 PM
03-12-2008 10:23 AM
03-13-2008 02:37 PM
03-14-2008 08:46 AM
Nate,
I had the same problems in trying to locate this "iPort" driver, and figured that it was likely not the way to go, seeing as I could find no mention of it pretty much anywhere. So I'm glad to see that we are in agreement there. As for the firmware upgrade, I have started to go ahead with that, as it seems to be the only easiest option for interfacing the cameras with LabVIEW (the Cam2Net software has a sample LabVIEW VI in its documentation that is a sample of how to export images to LabVIEW, but obviously the two programs have trouble running on the same computer...and this also seems like an over-complication I could do without). However, as with every other step of this project (sigh), I have been running into problems in just trying to upgrade the firmware. After following the upgrade manual step by step, the whole thing fell apart at the last step before the upgrade actually begins, where an IP Engine Selection window is supposed to give you the option to upgrade once you have given the camera a unique IP address...but instead, with my luck, the window appears blank. So right now I am concentrating my efforts on trying to rectify that situation. But once I get the firmware upgraded (assuming I eventually do...grrrrrrrr), I'm sure that I will be back on here probing your expertise once again.
Thanks for everything, talk soon, no doubt.
Cheers,
W
04-04-2008 10:13 AM
hello again!
after being sidetracked by a few other projects, i reloaded windows on my computer, and things seem to be working out way way better. i managed to upgrade the firmware on the cameras so that they are GigE Vision compliant, and managed to get the IMAQdx program to recognize that the cameras are plugged in. My only issue, one that i hope you will be able to help with, is that once i get into the Measurement & Automation Explorer, the acquisition field is blank, and when i try to change any parameters (packet size, region of interest, timeout, etc.) a warning comes up that says "Error 0xBFF69012 Attribute Value is Out of Range" and i can't seem to find anything in the help section, or online to tell me what to do to change this. I assume, or pray rather, that there is a simple solution to this problem, and maybe you know it!
i'd love to install LabVIEW and start programming the system ASAP, so if you ahve any pointers they will be very helpful.
cheers,
W