VBAI 2009 and its Activex

[Median9]

It didnt work either:

Error -1967390711 occurred at LabVIEW:  (Hex 0x8ABC0009) Network operation timed out.

Possible reason(s):

LabVIEW:  (Hex 0x8ABC0009) Network operation timed out.

I dont know why it mentions Network while we are connecting local?? One thing, i am using LV 2009 to access the VBAI 2010 API. Or should it be LV 2010? 

[JtotheB]

Try to access the API in LabVIEW 2010 and see if the error clears up. You can find LabVIEW 2010 here.

[Median9]

Hi. Thanks but 2010 doesnt work as well.

[Brad]

That's strange that the INI didn't help...did the VI actually wait for 150 seconds before timing out? What if you change the INI to 200000 (i.e. 200 seconds), do you still get a timeout even though it waits for 200 seconds?

[Median9]

Brad !!!

I tried a lot of things including increasing the time to 200 sec, but nothing worked. 

Why does it mention network timeout when the target is the local PC with the camera attached? In the task manager, i noticed that the CPU usage goes to 100% for as long as i don't receive the error message, i.e. for about 120 sec. Does this mean that the PC Processor is not at all capable of handling the initializations etc. within VBAI which is resulting in such behavior?

[Brad]

I would expect you'd see the same behavior with task manager when you open the camera in MAX or the regular VBAI executable. The reason there is network timeouts is because we use TCP to communicate between processes (LV app and VBAI engine). So just to be clear, when you set the timeout in the INI to 200 seconds, you actually wait at the open inspection VI for 200 seconds before getting the timeout? When you open the same inspection in the VBAI executable, it takes about a minute, but after that it is fine? I really think something is wrong with the camera because it should not take a minute to initialize...it's also weird that it takes much less time on Windows 7...are you using the same IMAQdx driver on both machines? Do you see a really long load time in MAX as well?

Thanks,

Brad

[Median9]

Thanks for the response Brad, my answers in Blue:

I would expect you'd see the same behavior with task manager when you open the camera in MAX or the regular VBAI executable.

Not at all. MAX opens the camera like a charm. In VBAI, it takes a couple of minutes to open but once open everything runs just fine.

The reason there is network timeouts is because we use TCP to communicate between processes (LV app and VBAI engine).

Ok understood.

So just to be clear, when you set the timeout in the INI to 200 seconds, you actually wait at the open inspection VI for 200 seconds before getting the timeout?

Yes.

When you open the same inspection in the VBAI executable, it takes about a minute, but after that it is fine?

Yes.

I really think something is wrong with the camera because it should not take a minute to initialize...it's also weird that it takes much less time on Windows 7

Yes But with Windows 7 running on another, more powerful machine. As i mentioned before, Windows 7 on the target Touch PC still takes about 2 minutes to load in VBAI. But MAX runs well with both XP and Win 7 on the target Touch PC.

...are you using the same IMAQdx driver on both machines? 

Yes.

Do you see a really long load time in MAX as well?

Yes. 

[Median9]

Thanks for the response Brad, my answers in Blue:

I would expect you'd see the same behavior with task manager when you open the camera in MAX or the regular VBAI executable.

Not at all. MAX opens the camera like a charm. In VBAI, it takes a couple of minutes to open but once open everything runs just fine.

The reason there is network timeouts is because we use TCP to communicate between processes (LV app and VBAI engine).

Ok understood.

So just to be clear, when you set the timeout in the INI to 200 seconds, you actually wait at the open inspection VI for 200 seconds before getting the timeout?

Yes.

When you open the same inspection in the VBAI executable, it takes about a minute, but after that it is fine?

Yes.

I really think something is wrong with the camera because it should not take a minute to initialize...it's also weird that it takes much less time on Windows 7

Yes But with Windows 7 running on another, more powerful machine. As i mentioned before, Windows 7 on the target Touch PC still takes about 2 minutes to load in VBAI. But MAX runs well with both XP and Win 7 on the target Touch PC.

...are you using the same IMAQdx driver on both machines? 

Yes.

Do you see a really long load time in MAX as well?

Yes. 

[Median9]

When you open the same inspection in the VBAI executable, it takes about a minute, but after that it is fine?

Yes.

I really think something is wrong with the camera because it should not take a minute to initialize...it's also weird that it takes much less time on Windows 7

Yes But with Windows 7 running on another, more powerful machine. As i mentioned before, Windows 7 on the target Touch PC still takes about 2 minutes to load in VBAI. But MAX runs well with both XP and Win 7 on the target Touch PC.

...are you using the same IMAQdx driver on both machines? 

Yes.

Do you see a really long load time in MAX as well?

Yes. 

[Brad]

Your last answer said MAX takes a long to load, but previous answers seemed to imply MAX loaded "like a champ", which I interpreted as fast (i.e. less than 5-10 seconds). Does MAX take the same amount of time to load the camera as VBAI executable? To really test this since MAX caches things, make sure to restart MAX and time how long after clicking on the camera you can acquire an image. Does using a Touch Panel affect the timing (i.e. using a normal PC works faster?) Have you tried another camera than the Korea GigE one? Would you be willing to send the camera here so we can reproduce this and see where the bottleneck is?

Thanks,

Brad

[Median9]

Your last answer said MAX takes a long to load, but previous answers seemed to imply MAX loaded "like a champ", which I interpreted as fast (i.e. less than 5-10 seconds).

My last answer said MAX Loads like a Charm, meaning, it takes less than 30 seconds to load the cameras on the target Touch Panel PCs.

Does MAX take the same amount of time to load the camera as VBAI executable?

No. MAX loads quick (less than 30 seconds). VBAI takes a couple of minutes.

To really test this since MAX caches things, make sure to restart MAX and time how long after clicking on the camera you can acquire an image.

I will test that shortly to be more specific on MAX timing.

Does using a Touch Panel affect the timing (i.e. using a normal PC works faster?)

Yes. Using a Corei3 PC makes it much more fast. This is the reason that surprised us at the 11th hour when we finally tried to test the cameras on the Touch Panel PCs. Otherwise, we were all set that things will work just fine.

Have you tried another camera than the Korea GigE one?

Like i said, the only option we had were the USB cameras which didnt work on the TPCs. We do have a Firewire camera but the TPCs do not have a Firewire port.

Would you be willing to send the camera here so we can reproduce this and see where the bottleneck is?

This is a good option that we could work on at a later stage. It was just that we are already 2 weeks past the deadline for this project and wanted to have a quick solution. For now, we have decided to go with the VBAI executable at startup with a batch file using the limited amount of information available for the switches. But here also we do face some troubles like fixing the window position and removing the menu bar etc.

[Median9]

One more thing Brad:

On the Windows 7 Machine (with Core i3 Processor, where things run smooth without any troubles), we have VBAI Versions 3.6, 2009 and 2010 with their relevant IMAQdx drivers. Where as on the target Touch Panel PCs, VBAI Version 3.6 with its IMAQdx driver is not installed. They only have 2009 / 2010 IMAQdx / VBAI.

Do you think this could be something important? Maybe these older cameras were meant for a previous version of IMAQdx driver? I am just guessing. We bought these GigE / USB cameras about 2 years ago.