10-19-2006 11:00 AM
10-20-2006 08:34 AM
Hello,
It sounds like this could be a problem with the drivers installed on the machine you're targetting. In your post you didnt mention if you had IMAQ drivers installed in addition to your LV Vision modules.
If you havent got the IMAQ drivers installed try doing this, otherwise post back with more information about your system where we can take the resolution of the problem further.
Good Luck!
Tom.
NIUK
10-20-2006 09:04 AM
Hi Tom, Thanks for your reply. It's turned up an anomaly and I don't know why
On my development machine IMAQ is at 3.5.0, but on the target machine it's at 3.1.0.
I don't actually want to go as far as 3.5.0 as it doesn't support Win NT. In the end one of the targets for my app is an NT4.0 machine.
The thing is I don't know why my development machine has IMAQ 3.5.0, as the vision development module 7.1.1 CD installed to it only has IMAQ 3.1.0.
I should probably try to roll back my development PC to using IMAQ 3.1.0 - can you advise if this is likley to cause me any difficulties?
As for system info, the situation is as follows.
We have a Dalsa Spyder linescan camera we have used for a while, with a PCI 1424 acquisition card on a windows NT system.
We then got a Dalsa Piranha camera and a PCI 1428 card, which is paired with a Win XP system.
My current task is to upgrade my linescan application to enable the use of either camera (done) and make it distributable (doing that now).
The Piranha becomes the main system (it's faster) and the Spyder gets mothballed. Should we have enough work to need 2 camera's we then purchase a second license and bring that system back into use.
Let me know if you need any further info. I have this thread set to notify my e-mail account inthe event of a reply.
Regards,
Bandit
10-20-2006 09:06 AM
One more thing - I'm currently trying to install on the Piranha/PCI1428.Win XP system - that's where the problems are. I'll test operation on Win NT afterwards.
Bandit
10-24-2006 03:28 AM
Issue now resolved. Developmen machine rolled back to V3.1.0 IMAQ drivers. Testing on Win NT and Win XP targets with associated hardware proves problem is cleared.
Thanks for help and advice.
Bandit