generate train pulse-cont on RTSI cable

[Martin V.]

Hi,
can you tell me, how should I modify the Gen Dig Pulse Train-continous.vi if I want to send the generated signal via RTSI cable to IMAQ PCI 1428 or how is this problem possible to solute.

I use Labview 8.2, Win XP, PCI 6070, PCI 1428.

Thank you very much Martin

[Robert_F]

Hello Martin,

You can use the DAQmx Connect Terminals.vi to connect the internal output of the counter to one of the RTSI lines.  I cannot simulate the PCI-6070E in the Measurement & Automation Explorer (MAX) to verify that route.  (Device Routes Tab)  I was able to simulate the PXI-6070E and that board can route the internal output of counter 0 to any of the RTSI lines.  (Represented by a Green Square)However, the internal output of counter 1 has an indirect route to all of the RTSI lines. (Represented by a Yellow Square)  So before you try this out, I would suggest verifying that this route can be made.

Before you start the DAQmx task, use the DAQmx Connect Terminals.vi.  The source should be the internal output of the counter and the destination should be the RTSI pin.  After you stop the DAQmx task, make sure that you disconnect the route.

Message Edited by Robert F on 10-26-2007 02:01 PM

[Martin V.]

Hello Robert,

thank you very much it works greatly :-)))
you really helped me...

thank you again...

Yours sincerely Martin V.

[Neil_S.]

Martin V.

Connect and disconnect will work well as Robert pointed out.  Even easier is to just set the CO.Pulse.Term channel property.  This property specifies where the counter output should be routed to and makes it so you do not have to remember to disconnect the terminals:



Regards,

Neil S.

Message Edited by Neil S. on 10-30-2007 09:50 AM

[Martin V.]

Good afternoon Neil S.
thank you very much for your reply it helped me too and thank you for the helpful links.
I am grateful to you.

I have one more problem similar to previous.
I wil try to explain my superior problem because i am quite desperate with it... i have read many manuals and articles but i didnt found what i need.

I have two boards... one is PCI 6070E we talked about and the another is IMAQ PCI 1428.
I need to trigger my camera with this signal witch you helped me to get to RTSI.
So to my PCI 1428 is going the signal from RTSI 0 and I need to get this signal to cameralink 22,9 pins because those pins are external trigger for the camera and it is able to work triggered by this signal.

I am able with my aplication to trigger each buffer as it is shown in VHA ring example but i need to trigger each line with the signal from the RTSI. There is only one example for trigger each line in IMAQ driver and in this example there is used encoder but i dont have encoder and i have to use the signal from RTSI.

If you can help me with any advice or link i would be most grateful.
I am sorry for my english I am just student of it.

Yours sincerly Martin V.

[michaeld]

Martin,

In order to use the signal on your RTSI 0 line to trigger a line, you will simply need to configure the trigger to "Trigger each line (linescan)" To do this with the LL VHA Ring.VI, you may need to delete this constant, and recreate it by right clicking the input terminal and selecting Create >> Constant. This will then allow you to set this option.

[Martin V.]

Thank you Michaeld for your reply,
but when I use "trigger each line (linescan)" mode it seems to be working like simple grabing... the application is displaying non triggered lines...

When I choose trigger each buffer it works fine and the application is showing every acquired buffer but in the trigger each line mode it doesn't work fine. I need to display just the triggered lines a nothing else. I use storbe to light the place what I am acquiring so I can see when the trigger switches because the strobe is triggered with the same signal. So I should see only the lightened lines.

Maybe I am using wrong example as a template but I tried to modify trigger each line from encoder (without the encoder) and it doesn't work to. Both examples works fine only in trigger each buffer mode. Please do you have any idea how to trigger each line and display only the triggered lines?

I also found some parameters I don't understand or I don't know the exact meaning and I didn't find any answer in help files or manuals (I tried LabView help, NI-IMAQ VI reference help, IMAQ User reference, NI-IMAQ Function reference):
    1) in IMAQ Configure list.vi there is continous vs. one-shot
    2) in IMAQ Configure list.vi there is system vs. onboard memory location and I don't know how to use it. I need to get to quite                         high frequencies and it should be helpful not to send useless data
    3) in IMAQ Configure list.vi there is imgBufferElement.vi with implicit value buffer comand and there is  posibility  trigger but I don't konw         it
    4) in IMAQ Configure list.vi there is acquire to system memory... the same problem
    6) and the last in IMAQ Extract buffer.vi in the center of the block diagram there is IMAQ Attribute.vi with many possibilities and I didn't             find them

Please can you tell me where can I find some information about those attributes and parameters? I tried NI-IMAQ Function Reference for LabWindows/CVI too with no result.

Maybe I should establish new thread because this topic is now about IMAQ...

Best Regards,
Martin V.

[michaeld]

David,

Can you please clarify for me what happens whenever you use the "trigger each buffer" mode? Are you seeing all of the images, and not just the triggered ones? If so, I suspect that your camera isn't configured properly for triggering. It seems like it is using an internal clocking signal, as opposed to the signal you are routing to it over RTSI. A couple of suggestions:

1) In Measurement and Automation Explorer, did you specify the camera mode as triggered? This may be dependent on your camera file.

2) Your camera itself, may have to be configured to operate in triggered mode such that your counter signal can trigger each line. You often have to configure this with a serial command sent to the camera. Is this possible with your camera/camera file?

3) Try sending only enough trigger pulses to obtain a single frame or half of a single frame. Does the acquisition still run continuously, or does the acquisition stop after the specified number of lines or after a single frame is completed?


Regarding your question about the innards of IMAQ Configure List.VI: There are not more detailed help files to be found because this particular VI is meant to be a high-level VI, and the code deeper within is not meant to be modified. The settings that you can manipulate with this VI are configurable through the terminals of the subVI. You can check the IMAQ VI reference help for more info on how to use this VI in a higher level.

[Martin V.]

Hello Michael,
thank you for your interest.

My camera (Basler L101k-1k) can work in five modes free-run, programmable; free-run, edge-controlled; exsync, level-controlled; exsync, programmable; exsync, edge-controlled. I use the free-run, programmable because any of the exsyncs doesn't work at all. When I use any of exsyncs timeout error occurs. In the free-run, programmable mode I can get those pictures that I attached.

On the first picture is what I see when I am just grabbing in MAX.
On the second picture is what I see when I am grabbing in MAX and triggering the strobe with 100Hz (image resolution is 256 x 256 and camera is now set to acquire 5000 lps).
And on the third picture there is what I see when I use VHA ring acquisition. When the trigger comes it switches to another buffer so in every buffer there is only one lightened line.

So I thought that when I use trigger each line I will  see just  the lightened lines and nothing more but I can see the grabbing. And I found out that if I switch in this mode (trigger each line) the trigger source parameters (trig type, trig num) it still displays the grabbing (1st picture).

And now answers for your questions:
1) In MAX I have no options for triggering the camera. There is only general settings like acquistion parameters (top, left, width, height, etc.), signal levels (External trigger 0..3 - TTL In/Out). I don't think that there is a problem because as you can see on the 3rd picture the trigger each buffer mode works fine. I can setup the camera in Camera Configuration Tool CCT+. In CCT+ there is option for different modes I spoke about in the first paragraph.

2) and 3) I programmed this problem in LabWindows/CVI before. Now I am trying LabVIEW because there is more support for VIEW. I made an application that is generating the pulse-train singal to RTSI 0  and using the principles of VHA ring example. I am able to see every buffer in the buffer list when the application is stopped. And because of that results I don't think that there is a problem in getting the trigger signal to the camera because trigger buffer list works, trigger each buffer works but I don't know why the triggering each line doesn't. Maybe there is some little thing that should be set for triggering each line in contrast to another triggering modes. But there is only example with encoder for triggering each line and I would need just simple example for triggering each line by external trigger or RTSI.

[Martin V.]

Just a note... the attached files changed the position so keep the numbers please... obr1.jpg is meant to be the first picture...
Have a nice day... Martin V.