Errors using IMAQ PCI-1409

I'm getting an error when running a fairly basic VI to acquire a sequence from the PCI-1409 card. It is -1074397110 Exhausted resources (general). It's occurring in the 'generate pulse' bit. As far as resources go, the number of buffers in MAX is still the default 50 and I'm only trying to acquire a sequence of 2 frames at this point. Has anyone got any clues as to where I'm going wrong? If I use grab in MAX it works fine (get's 25fps).
Attachments:
1409capturetriggersub.vi ‏72 KB

Ah, brilliant thank you! That's stopped that error occurring. However, I'm now getting "error -1074397150 in IMAQ Sequence.vi", " Wait timed out; acquisition not complete." I guess this is because my pulse doesn't seem to be being produced as I've got the line trig 0 (and it's associated ground) hooked up to a scope and nothing's happening so the sequence capture is timing out waiting for the pulse. Any ideas what else I'm doing wrong with the pulse to cause this?
Thanks again!
Attachments:
1409capturetriggersub3.vi ‏75 KB

Similar Messages

How to store jpeg images with IMAQ PCI-1409 without vision or labview

I have acquired an IMAQ PCI-1409 card and have it working just fine. However the card is being primarily used to aquire images for display purposes only. The only options with MAX are .tiff, .bmp and .png
It would be nice to be able to store images as .jpeg which would be easier to share with other people.
Is this possible or do I have to compress the images using another software?

Hello,
Thank you for contacting National Instruments.
Unfortunately, as you mentioned, the only save options available in MAX are TIFF, BMP, and PNG. In order to save the image as a JPEG, you will need to use another software program. Microsoft Paint will allow you to save/convert any of these types to JPEG format. Other programs (Adobe Photoshop for example) allow you to customize the compression used, but Microsoft Paint does not.
Best Regards,
Jesse D.
Applications Engineer
National Instruments

Is the IMAQ PCI-1409 compatible with the JAI CV-M30 camera?

Does the IMAQ PCI-1409 support the double speed and partial scan modes of the JAI CV-M30 camera?

In theory the PCI-1409 should work with the JAI CV-M30; however, National Instruments has not tested that particular camera with our PCI-1409. Since the camera can output the pixel clock, if necessary you could put the PCI-1409 in External Lock mode to lock to the camera signals. You may also need to adjust some of the settings in MAX.
If you need more direct assistance on this matter, please contact National Instruments technical support directly.
Best regards,
Dawna P.
Applications Engineer
National Instruments

Internal memory error using IMAQ 1394 ver 2.0

Hi Robert,
I apologize for the much belated response to your e-mail.
- When I was receiving the fatal memory error I was using the GRAB vi
to acquire the data. The problem seems to go away if I switch to
the SNAP acquisition method.
- I am not using the IMAQ vision FFT vi, I am using the FFT Spectrum vi.
- When the image acquisition code is removed I ran the FFT on simulated
data generated within the program not loaded from a stored file.
Thanks,
Ronen
-----Original Message-----
From: [email protected] [mailto:[email protected]]
Sent: Monday, August 01, 2005 8:20 AM
To: Feldman, Ronen (Contractor)
Subject: Re: (Reference#7084698) Phone Support E-Mail
Hi Ronen,
My name is Robert and I am one of National Instruments' IMAQ and Vision
supporters. Eric has forwarded me your email regarding the error
you are receiving as it looks like the problem may be related to the
image acquisition side of things.
In your last email, you noted that the fatal error does not occur if
you remove the FFT code or if you remove the IMAQ code. I was
hoping you could describe for me a couple of things in greater
detail. 1) In your typical code configuration, do you acquire
with a GRAB?
2) The FFT code that you mention, are you using IMAQ FFT VIs from the Vision Development Module?
3) You said if you remove the image acquisition code the program runs
fine. Does this mean that you are running your code on an image loaded
from file?
These answers should help us get to the bottom of the situation.
Additionally, how large is your program? Are all of the various
parts subVIs?
Regarding your other question, data parameters like those that you
mentioned can be changed during program execution, but those changes
are not saved to the camera's configuration file. If you make
these changes through the Measurement and Automation Explorer the
camera configuration file will be updated. This behavior is to
protect the configuration files from being corrupted by the program you
run.
Hope this helps. Let me know how things go with the IMAQ/FFT code.
Regards,
Note: Your reference number is included in the subject field of
this message. It is very important not to remove or modify this
reference number, or your message may be returned to you.

Hi Ronen,
I guess using the forums works for me too! I'm just glad I found it
To clarify, you are first acquiring with a Grab (does not work) or snap (works fine) and then performing an Image to Array. After Image to array you use the intensity information within the FFT Spectrum.vi? When the program errors out, do you know which step you are running?
In addition, you should be able to whittle the program down to just these basic steps, and see if the error continues to occur. If the problem you are having can be consistently reproduced with these three or four steps, I would be interested in seeing if I can reproduce the problem here.
Regarding one of your other questions, changes made to the camera configuration file from Labview will not be permanent. This is to avoid the possible hazard of overwriting the file with a non working configuration.
Hope this helps,
Robert

Pci-1409 cannot use rs-179&NTSC MOde

i have a ccd,panasonic wv-bp330. I use the pci-1408 to link the ccd,then i use MAX to try to get image data.But i find that ccir&pal mode is ok,while rs-170&NTSC mode have problem(see the attachment).But if i use pci-1408 to link the same ccd, all the mode is ok. why!!

Perhaps these notes from NI could be of some help for you:
Notes on Upgrading from the 1408 to the 1409
One of the major differences that can cause a "Can't lock on video source" error for the PCI-1409 and not the PCI-1408 is due to variations in locking circuitry. For non-standard analog cameras, the PCI-1408 and PCI-1409 are designed to lock to these cameras in external lock mode. This means the camera's HSYNC, VSYNC, and pixel clock are supplied to the IMAQ board, which allows the board to bypass its locking circuitry and acquire the non-standard images using the camera's timing signals instead of generating its own. The PCI-1408 could often times acquire from non-standard cameras without being in external lock mode because its locking circuitry was more flexible, but it didn't cover as wide a range of frequencies as the PCI-1409. The PCI-1409 supports standard, discrete locking frequencies that cover a wider range (including VCR), but for frequencies that aren't quite standard frequencies, it won't lock. Operating in External Lock mode will acquire non-standard images for both the PCI-1408 and PCI-1409.
Because the 1409 supports 10-bit images, you may have code written for the 1408 expecting 8-bit images. If you replace your 1408 board with the 1409, your images are now 10-bit images, so your code will give you an error. You can either change the code to accept the higher precision images (i.e., change the "image type" input of the IMAQ Create function from 8 bits to 16 bits), or simply change the 1409 in the Measurement & Automation Explorer to acquire 8-bit images from the property page of the camera.
The camera files are also different. The 1408 had the option to choose Interlaced vs. Non-Interlaced for the standard RS-170, CCIR, NTSC, PAL cameras. The 1409 has that box grayed out (Interlaced being the only option) because the only time you would have Non-Interlaced selected is for Progressive Scan cameras, and there are now four progressive scan camera files you can choose from (25, 30, 50, and 60 Hz). So if you have a PCI-1409, instead of trying to set an RS-170 camera file to Non-Interlaced, select the 30 or 60 Hz progressive scan camera file.
The Area Scan camera file was designed for non-standard cameras, and it would often work with the PCI-1408 without configuring the board in external lock mode, but the PCI-1409 would not lock to non-standard cameras using this camera file. This goes back to the first point, and both boards should be configured in external lock mode to acquire from non-standard cameras.
If you are using the breakout box for the 1409, it requires you to remove a jumper on the 1409 to reduce noise. The 1408 did not have this requirement.
If you are genlocking multiple cameras together (they are synchronized using the same timing signals from a master camera and the others are slaves), you need to set the 1409 up for external CSYNC lock mode. If you don't, your images will be superimposed on top of each other and scrambled. To set the 1409 for CSYNC external lock mode, go to Measurement & Automation and right click on the 1409. Choose Properties>>Operating Mode and select CSYNC External for the Acquisition Mode and select the master camera's channel for the CSYNC Source.
Look at http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/df0f02236f45816f86256a78007afa6d?OpenDocument
Hope that helps,
Michael

Error 30206: IMAQ operation not active

I am using Vision for Visual Basic and have the following code on a form that contains 3 cwimaqviewer controls and 1 cwimaq control. I press cmdStart to start the acquisition process. When I press the cmdStop button, I get Error 30206: IMAQ operation not active. Also, after I press cmdStart, the AcquiredImage event for the cwimaq control never happens. Does anyone know why I am getting these problems? Thanks.
Private Sub cmdStart_Click()
CWIMAQ1.Images.Add (2)
CWIMAQViewer1.Attach CWIMAQ1.Images(1)
CWIMAQViewer2.Attach CWIMAQ1.Images(2)
CWIMAQViewer3.Attach CWIMAQ1.Images(3)
CWIMAQ1.Images(1).Channel = 1
CWIMAQ1.Images(2).Channel = 2
CWIMAQ1.Images(3).Channel = 3
CWIMAQ1.Acquisitio
nType = cwimaqAcquisitionContinuous
CWIMAQ1.Configure
CWIMAQ1.Start
End Sub
Private Sub cmdStop_Click()
Me.CWIMAQ1.Stop
End Sub

Basically, what we're trying to do is acquire and process images from three different cameras continuously (e.g., get an image from camera 1 and process, get an image from camera 2 and process, get an image from camera 3 and process, get another image from camera 1 and process.... and this continues until the user tells it to stop). We currently have this working using the OneShot acquisition method, looping through the cameras, and placing the images in a single viewer control. However, it is not as fast as we would like this to be, so we decided to try the continuous acquisition method.
We are using a PCI-1409 analog board. Note, the cameras we are using are not genlocked.
Hello again.
The following document describes some of the
processes, caveats, etc. of doing multiple camera acquisition.
Multi-Camera Acquisition - Tutorial
The fundamental problem that I believe we are running into is that you cannot simultaneously acquire from 3 non-genlocked cameras at once. If the cameras are not synchronized, then the PCI-1409 must be re-configured between each camera (stop acquisition, change channel, re-start acquisition). As the tutorial mentions, this essentially yields a low frame rate.
Because this is heavily dependent on the computer, the frame rate you get varies greatly.
In general, the way you will still have to do this is sort of in 'one shot' mode, where you are grabbing one image from each channel at a time.
Regards,
Colin C.
Applications Engineering
Colin Christofferson
Community Web Marketing
Blog

Custom confocal question with PCI 1409 based acquisition

We are using a PCI-1409 to acquire a high def and video rate image from a custom confocal system. We use the BNC breakout box to send in luminance, hsync and vsync from the PhotoMultiplierTube and our custom control box.
Because of the way we scan using resonators, we have two corrections that we would like to make to the video stream and are unsure whether it can be done at the camera level, i.e., put code into the .icd file we made, or if it is something that needs to be completed in LabView. Any help would be greatly appreciated.
Distortion One: We acquire luminance information in both scanning directions. Our image is thus one where every other line is reversed. Is there a way to reverse every other line and register? Right now we double the effective width of the image and then have to crop the image two times, reverse one image stack and then interleave.
Distortion Two: The velocity of the scanning mirrors varies sinusoidally and thus there is some stretching that occurrs at the edges. How would one go about filtering the stream to correct for this? I assume that this is something that would have to be done in LabView as the pixel clock is fixed.
Attached is the .icd file we modified from defaults to achieve a stable image with the two distortions already mentioned.
-sb
Solved!
Go to Solution.
Attachments:
Area_Confocal.icd.txt ‏3 KB

Bruce,
Thanks for weighing in on the matter. I suspected as much although I was hoping that there might be a "line-reversal" option through the camera definition file...such an option is available for other video cards that we use.
For previewing and scanning specimens I would like to do real-time...is there an easy way to throw away the odd lines so that I get an image that does not have the pseudo interlacing issue? Then, when I wanted to capture data I could programmatically use another camera definition with the lines and width doubling and then just post-process later?
smb

How do I set up a PCI-1409 and two Sony XC-ST50 cameras for synchronization and asynchronous reset?

Hello! I am using a PCI-1409 with two Sony XC-ST50 cameras. I need to use a single trigger to capture an image from each camera simultaneously. I know I need to gen lock the two cameras and use asynchronous reset. How do I do this specifically? How do I connect the cameras to the PCI-1409 and what settings do I need to set on the cameras and the PCI-1409?

There are a few great tutorials on the NI web site. The first discusses genlocking multiple cameras together. It is in the context of the JAI CV-M1, but all the concepts can be applied to other camera types. It is called "Genlocking Multiple JAI CV-M1 Cameras" (http://zone.ni.com/devzone/conceptd.nsf/webmain/7A6B5853548850E886256C21005B1413?opendocument). Another turtorial I suggest looking at is "Advanced Analog Triggering and Synchronization Techniques" (http://zone.ni.com/devzone/conceptd.nsf/webmain/A387B5C0AC6F6F4E86256C87005FCDDF?opendocument). This tutorial has a section which discusses triggering and synchronizing with multiple cameras. The last tutorial I recommend is "Multi-Camera Acquisition"(http://zone.ni.com/devzone/conceptd.nsf/webmain/D91BAC1317F9D
0A686256C9300769A0D?opendocument) This discusses how to synchronize and program multi camera acquisitions on the 1409.
Hope this helps!

Can't connect JAI CV-M1 camera to PCI-1409. Error: 'Can't lock on video source'

I am connecting a JAI CV-M1 camera to a PCI 1409 card but I can't kill the error message 'can't lock on video source'. Does anybody has the right interface and camera files for me (*.iid and *.icd)? Thanks...

Hi, I had a customer that used that camera , the configuration files are available in NI site , but you need to connect NOT only the BNC but in addition you need to connect PCLOCK pin because Pixel Clock is not standard.

Any known issues with using JAI-CVM10, Rev. D in Random Trigger Mode w/ PCI-1409

I am using a JAI-CVM10, Rev. D camera with a PCI-1409 framegrabber. I am having trouble getting it to work in random trigger mode. I used the example vi for JAI-CVM10, Rev. F and am able to get a picture using the internal trigger. However, I lose the video signal if my acquisition frequency is too low (3 images/sec) or I use an external trigger. Has anyone had this problem and does anyone have a solution?

hi Nan:
I have same problem with you.
can you got clear Image? or you got solution.
Could you tell me how to do.
Thanks.
Yang
[email protected]

Triggering problems with IMAQ PCI 1411 using NI-IMAQ 2.6 drivers

I am having problems with the NI-IMAQ triggering mechanisms. I would like to use imgSessionWaitSignalAsync to register a call-back function to be repeatedly called on rising edges on the external trigger line. Now the external trigger line is connected to a photocell that is low when there are no objects in front of it and is high when there is an object in front of it. Unfortunately, when running my application, the callback function is not always triggered when an object moves in front of the photocell, and it is often triggered when no object is in front of the photocell. The callback function is not called anywhere else in the code.
An engineer at my company hooked up an oscilloscope to the trigger l
ine and we found that the photocell performs as expected. So I am looking for help to ensure that every time an object starts to pass in front of the photocell, the callback function will be triggered.
System Details:
Windows 2000 PC
Visual C++ 6.0
2x IMAQ PCI 1411 installed(one is revision A, the other is revision C.) I have the same problem even if I switch to the other card.
NI-IMAQ 2.60.0 drivers
Thanks in advance,
Michael

Bruce,
In fact that was my problem. The XC-73 operates at 30 Hz. My strobe
lighting was not triggered at 30 Hz. Once they matched, the
interlacing problem I described went away.
-Shehrzad
Bruce Ammons wrote in message news:<506500000005000000634D0000-1004225886000@exchange.ni.com>...
> Shehrzad,
>
> What kind of lighting are you using? I have seen variations like you
> describe when using fluorescent lighting, and also with incandescent
> lighting when the frame rate didn't match the power frequency. I
> suspect you are right about the lighting. I can't think of any other
> reasons for the problem you described.
>
> Bruce

How to achieve image using digital camera of USB-type interface through IMAQ PCI-1424 board.

1.Is it doable?
2.How to connect USB-type interface with IMAQ PCI-1424 board.
Thanks!

See the Developer's Zone (www.ni.com/zone) for specifics on USB (search for "USB").
"1.Is it doable?"
- In short "no".
- USB is similar to FireWire (IEEE 1394), and no framegrabber is required. We offer an IEEE 1394 IMAQ driver to interface FireWire cameras with LabVIEW & CVI.
"2.How to connect USB-type interface with IMAQ PCI-1424 board."
- You will need a USB driver for the camera. The 1424 is not required.

Sony xc hr50 and pci 1409, snap ok with max 4.0 but nothing with labview

Good morning folks,
I have a problem snaping or grabbing image through Labview 8.0 using the analog ccd camera xchr50 from sony.
I installed the pci 1409 correctly and am able to configure the camera, and snap or grab image from it through MAX 4.0.
But when it comes to try to snap or grab within my Labview interface, i just come up with an error message saying :
error 1074397153 occured at imaq snap.vi
ni imaq cannot detect recognizable video source
I can't figure out why this error comes out and how to correct it although i can do the same acquisition through max and it goes perfectly well..
I tried with another camera, same thing.
Has someone ever had that kind of problem?

Hello, Gegurissi
There are a couple of sources available from NI pages for troubleshooting your XC-HR50.
Using the Sony XC-HR50 Camera in Asynchronous Reset Mode With the IMAQ 1409
http://zone.ni.com/devzone/conceptd.nsf/webmain/e4187ea9d216f71d86256c0f0068fb7d
Using the Sony XC-HR50 Camera in Asynchronous Reset Mode With the IMAQ 1409
http://sine.ni.com/apps/we/niepd_web_display.display_epd4?p_guid=B45EACE3E24B56A4E034080020E74861&p_node=DZ52489&p_source=External
Please take a look at the document and the sample program attached to the page.
If you still have a problem, please let us know.
S.Kazuma
Application Engineer
National Instruments Japan

Frame timeout error using Configure Trigger3.vi

Hi all,
I'm triggering the frame capture of an .avi with an RTSI connection. However, I keep getting a frame timeout error when I use the IMAQ Configure Trigger3.vi. I don't get any timeout errors when I just use the IMAQ Generate Pulse3.vi but I am trying to sync the frame capture to an optical switch. If I just use IMAQ Generate Pulse3.vi, I get a .avi but the frames are completely out of sync with the switch, but if I use both IMAQ Generate Pulse3.vi and Configure Trigger3.vi I get nicely separated images but it takes an age and ends up in a timeout error.
I want to capture e.g. 500 frames, over the course of 2 s - so I've set my frame timeout to be 2000. At my current acquisition rate (31680 Hz per line (1024 pixels)) 500 frames corresponds to a total of 1.578 s (images are 100 pxls in height). This is much less than the total scanning time. Where am I going wrong?
Thanks in advance for your help.
Miika
Attachments:
screen.png ‏32 KB

Hey Miika
What are the hardware you are using. These vi's only work with specific hardware and this may be why they are not functioning correctly. For example the Configure trigger3 vi only works with the following PCIe-1427, PCIe-1429, PCe-1430, PCIe-1433.
Matthew Trott
Applications Engineer
National Instruments UK
www.ni.com/ask

IMAQ PCI-1424 compatibility with Labview 8.6

Hi, the computer I used for image analysis work had a broken motherboard problem, and I replaced it with a new one. I removed both the harddisks and the IMAQ board from the old computer to the new one and then installed Labview 8.6, but Labview 8.6 is not compatible with the image processing software programmed using labview 5.0, so I uninstalled Labview 8.6 and re-installed Labview 6.0. I still have some problems to run the image analyzer and processing software. After I uninstalled labview software, the computer cannot start successfully, poping up error information as "Check your hard drive to make sure it is properly configured and terminated. Run CHKDSK /F to check for hard drive corruption, and then restart your computer".
Some basic information about that computer and the image acquisition system (set up in 2000) is as follows:
Windows 2000 operating system;
Labview Base Package 5.0;
advanced IMAQ vision for Labview;
IMAQ PCI-1408, IMAQ-BNC-1 cable, and Ni-IMAQ for Windows NT/95;
IMAQ-A2504-1 (1m);
Sony XC-55 1/3" Interline transfer progressive scan CCD, 659 (H) X 494 (V), C-mount with JB-77, CCXC-12P-02 and DKT503M;
Computar H1212FI 1/2" C-mount 12mm w/focus and iris (10 inch FOV at 24 Working Dist.);
Computar VM100 extension tube kit;
Graftek High Frequency Fluorescent Light 11";
Is the IMAQ hardware I am using compatible with Labview 6.0 or 8.6? Should I install also drivers for IMAQ hardware when I remove IMAQ board? Any solutions for my problems? Thanks very much in advance!!!
Solved!
Go to Solution.

Hi simpra,
Here are two links to articles that list compatability between Windows & LabVIEW and LabVIEW & IMAQ. Why do you say that the image processign software was not compatable with LV 8.6? Did a message appear? Or did it just not work? Also, are you talking about Vision Development Module, by chance?
I'm afraid I can't help with hard drive corruption if that's the case here. Were you able to get past that?
My suggestion is to upgrade to the most recent version possible.
I hope this helps!
Kristen H.

Errors using IMAQ PCI-1409

Similar Messages

Maybe you are looking for