running multiple instances of VBAI does not work

[Brad]

Have you had a chance to try acquiring from all 4 cameras in a single inspection or VI? Let us know what error you get or if it works. What is the networking difference between the two systems, just to make sure I have the latest details. If you put the 4 cameras that aren't working in the system that does work, can you still acquire from all 4? Are they the same camera model as the ones that do work?

Thanks,

Brad

[Vasileios.T]

Hello Tom,

The main two differences I can see from the MAX reports are the operating system and the firmware version.

The working computer has Microsoft Windows 7 Professional and its firmware version is L01 v02.57,
whereas the non-working machine has Microsoft Windows 7 Professional (Service Pack 1) and L01 v02.65 firmware version.

Since, from my understanding, all of the cameras work individually I do not think it is a driver problem.  

Another difference was at the system resources as your working machine has more physical memory.
I do not think this difference is affecting your application as your application does not seem to use all of the memory resources.

Please follow Brad’s suggestion and keep us posted.

Kind regards,
Vasileios

[declercq_tom@waak.be · Accepted solution]

Hello Brad and Vasileios,

Thanks for the continuous support!

Today has been an interesting day:

• We have made a program, as requested, that simply acquires an image from the 4 cameras. Between each acquisition step we've added a 1000ms delay.
• When running the program on our programming laptop (cameras connected over a switch) it worked!
• Then we connected the 4 cams to our other computer (4-port NIC), the program didn't work anymore. We discovered that for some reason the acquisition steps alle referred to the same camera.

So I think we might have found the problem.

Then we opened our 4 programs individually and saw that in thode programs the acquire step also referred to the same camera.

After that we connected everything back to our old computer (over a switch) and all the acquire steps referred to 4 different (correct) camera's.

Only question is: Why do the 'acquire image'-steps refer to other cameras on when we open the programs on our new computer?

Tomorrow we will:

Open all our programs on the new computer (4-port NIC) and change all the cameras to the correct ones (in all our acquiqition steps and all our read/write steps).

Hopefully this will solve the problem. We will let you know as soon as possible.

Any thought on why the cams are changed? They all have a specific ip-adress.

With kind regard,

Tom Declercq