11-20-2008 12:27 PM
11-20-2008 01:01 PM
I was actually running it in VB 6 I believe.
I currently don't have VB 08 on my computer, and was using a test computer to try to replicate your problem.
11-24-2008 01:18 PM
Chris,
Any comments on my thread before my VB version thread?
11-24-2008 02:30 PM - edited 11-24-2008 02:39 PM
Hey, sorry for the delayed response, I have been running into quite a bit of trouble with this. After some digging, I did get some useful information from our documentation:
LoadInterfaceDefaults is a NI-IMAQ function used with PXI/PCI frame-grabbers and you have the NI-IMAQ 1394 driver. You will have to make calls to the IMAQ-1394 driver dll instead. You can create a IMAQ-1394 language interface .BAS module for Visual Basic containing predefined constant declarations, routine and function prototypes that you are using in your code based on the 1394 driver API.
You were using the 1394 driver, correct?
11-24-2008 07:50 PM
Yes, I am using the 1394 driver, and I have no idea how to create an IMAQ1394 interface that you mentioned. Is there a FAQ or tutorial on how to do this?
Also, LoadInterfaceDefaults is a function used with PXI/PCI framegrabbers. Is SaveImageToDisk associated with IMAQ 1394 and not also with the PXI/PCI framegrabbers?
11-24-2008 10:00 PM - edited 11-24-2008 10:06 PM
Actually I'm using the IMAQdx driver which supposedly replaced the IMAQ 1394 driver correct?
I've noticed that neither the IMAQ 1394 or IMAQdx dll's have the function SaveImageToDisk
11-25-2008 11:17 AM
Yes, the IMAQdx driver replaced the IEEE 1394, but still includes support for it as a legacy driver.
Give me a little more time today, and hopefully I will have working code for you. I now have the same version of VB as you, so that won't be a problem anymore. I did realize that one of my OLD examples I gave you was for IMAQ, not IMAQdx, so I apologize for that retroactively.
I am now trying to integrate the SaveImage to disk or WriteImage to file methods with the IMAQdx Snap example. Hopefully I will have a solutionsoon for you.
11-25-2008 03:48 PM
timmkish,
I now have a complete replicate of your setup and am working on a solution. I am trying to avoid any usage of VDM or CWIMAQ to save it and am running into troubles. I am now waiting to talk to R&D tomorrow to see if this is possible with an ActiveX workaround, or what we need to do.
Thanks for all of your patience.
11-25-2008 03:59 PM
Thanks for all your help Chris.
If I went back to a VB 2006 compiler, would this solve our issues? I don't want to, but I'll do it if I absolutely have to.
11-25-2008 04:07 PM
No, VB 6 shouldn't make a difference. My example that worked in VB 6 was not using dx, just IMAQ. This was before I had done a ton of research into this problem and realized that it isn't an easy transfer.
I will try to rush the answer from R&D as fast as possible, because we will be out of the office Thursday and Friday, so I would liek a solution for you by tomorrow. If not a solution, at least some sort of path we can begin to follow.