11-20-2015 07:19 AM - edited 11-20-2015 07:20 AM
Edit - apologies, the title should have been IMAQdx Discover Ethernet Cameras - Timeout...guess I forgot to change it from my keyword search!
A nice little Friday morning problem.
I'd developed and tested a vision module using IMAQdx that's part of a calibration routine in an executable. Works absolutely fine on the development PC, works absolutely fine on my local deployment PC...then has a couple of niggly issues on one of my production deployment systems. After a little bit of head scratching, I realise that the camera initialisation is taking longer on the latter.
After a bit of probing, it turns out that IMAQdx Discover Ethernet Cameras has a little feature with its timeout. Have a run of this snippet:
This takes twice as long to execute on the production deployment system. Turns out, it's because that PC has two network interface cards on two separate subnets, so it looks as though the Timeout applies per subnet, rather than globally.
Thought it might be of use to someone else one day.