PXI trigger line names.

What are terminal names for PXI-Trig lines in traditional NI-DAQ?
There are only ND_PXI_STAR and ND_PXI_STAR_3... constants.

Hi Shibaev,
Thanks for posting on the NI forums.
I have taken a look into this one. From what is documented in the Traditional NI-DAQ manual, and the DAQ help file, the trigger lines for PXI devices are referred to as RTSI lines. For PCI devices there is an optional connector for a RTSI cable to provide shared triggers in a desktop PC. With PXI these lines are built into the PXI chassis. Although PXI and PCI are different form factors for DAQ devices, the (Traditional) NI-DAQ driver refers to either RTSI lines or PXI lines as simply 'RTSI'.
To route your clocks/triggers accross these lines you should use the string "RTSI X", where X is the line number you wish to use (X = {0,1,...,6,7}). Take a look at the attached .jpg for a list of possible signal route connections (this was extracted from the NI-DAQ help file).
I hope this helps!
Rob
Field Sales Engineer | National Instruments | UK & Ireland
Attachments:
TriggerLineOptions.JPG ‏98 KB

Similar Messages

PXIe-1065 Trigger lines

Hi all
I'm trying to acquire data on 7 PXIe-6358 boards. All these boards are put in a PXIe-1065 chassis which is connecte to a RMC 8354 throught a MXI 8360. In order to synchronize all boards togethet i use a PXI 6682H board which will generate a clock and a start trigger on two PXI trigger lines.
I made some test on a PXIe 1075 chassis and everything seems to work fine. I moved then on a PXIe-1065 chassis and now i'm having some problem when i try to acquire data on the 7 boards. When i have more than 5 boards, it seems at least one board doesn' receive either the clock or the start trigger.
Then trigger are configured in MAX to go through all 3 bus. When i configure only 5 boards (wherever in the slot) i works fine. But when i declare more than 5 boards i have the problem again.... It seems you cannot connect more than 5 boards to the trigger lines.
Does someone have an idea...

Ok, i found the problem, it has nothing to do with the PXIe 1065 chassis.
In my application i use the PXI 6682H to generate the start trigger and a clock. The acquisition tasks are waiting for the trigger to start the acquisition. In my case when i switched the chassis, the PXI 6682H becomes a master (in the old configuration it was parameter as a slave). When it is configured as a slave i check that the board is synchronized with the master (this can takes a little time). When i am the master i doesn't wait (cause i am already synchronized). Therefore, in that case the start Trigger is generated before all instances of the PXIe-6358 are started, and they wait indefinitively the trigger ....
I modify the code in order to wait a certain amount of time (even if the PXI6682 is configured as the matser) , and now its works properly ...

Generate PXI Trigger Signals with PXI-6115

Hello,
I have a question.
I have a PXI-6115 and some other card in my mainframe.
These other cards nee 10 Mhz pulses on line PXI-Star1 and 2.5 MHz on PXI_trg7.
So I thought to apply (somewhere on my PXI 6115 card) 10 MHz, divide the 10 MHz with a counter to 4 and route all this things to the backplane.
But I don't understand how to do this.
There are no good examples.
And as far as I know the PXI-6115 isn't yet supported by DAQ-MX.
Can anybody give me some good advises or tips, white paper or so to make me solve my problem ???
Thanks Ruediger

I don't have time to write any example snippets right now, but I'll try to provide you the general idea and hopefully you can take it from there.
First, it's not clear whether you want to generate the 10 MHz from the 6115 and send it to other devices in the system or accept the 10 MHz externally and route it to the rest of the system. If you're bringing in the signal externally, I would simply using the DAQmx Connect Terminals VI to route the signal from a PFI line on the front connector of the board to one of the PXI trigger bus lines in the backplane. Check out the routing table in MAX to see what routes are possible. To perform this route, the driver will have to route through Counter 0 so you won't be able to use Counter 0 for anything else.
If you want to generate 10 MHz from the 6115, I would create a continuous pulse train task on Counter 0 using the CO Pulse Ticks version of the Create Channel VI with a value of 2 for both the high ticks and low ticks input. However, to achieve 10 MHz clock on a PXI trigger line, you'll have to perform a couple of modifications that typically aren't done with counter tasks. First, you'll need to use the DAQmx Export Signal Property Node to route the Counter Output Event to the desired PXI trigger line. You can find this property by navigating the following menu hierarchy Events->Counter Output Event->Output Terminal. By default, the driver routes this event to the Ctr0Output pin on the front connector of the board. Using this property will override this behavior and route the output of the counter to a PXI trigger line instead. Second, you will need to change the output behavior of the Counter Output Event from toggle to pulse. This can be through the Events->Counter Output Event->Output Behavior property. Normally, when generating pulse trains, the high ticks and low ticks parameters from the Create Channel VI determine the frequency and duty cycle of the pulse train. When the high ticks count expires, the output of the counter toggles. The low ticks value is then loaded into the counter, and the counter output toggles again when the low ticks value expires. This process repeats to produce a pulse train of the desired frequency and duty cycle. Since the counter uses a 20 MHz timebase and has a minimum low ticks and high ticks value of 2, you can only produce at maximum a 5 MHz pulse train using the toggle behavior. However, by changing the output behavior from toggle to pulse, the counter output will issue a short pulse each time the high ticks and low ticks counts expire yielding a 10 MHz clock signal.
Now that you have the 10 MHz signal taken care of, you need to generate a 2.5 MHz signal from it. My guess is that since you have a 6115, you already have plans for the AI engine so I'll describe a route that uses AO instead. First, create an AO task to perform continous waveform generation. Use the DAQmx Channel Property Node and set the Use Only Onboard Memory property to true. Setting this to true will cause the driver to download the waveform once upon starting the task and replay the waveform from the onboard FIFO. Since you're only using this task to generate a clock, you don't really care about the data and this will prevent unneccessary traffic across the PCI bus. Next, use the DAQmx Timing Property Node to set the Sample Clock->Timebase->Source to the PXI Trigger line that you're generating the 10 MHz clock on, and set the Sample Clock->Timebase Divisor to 4 (10 MHz / 4 should give you a 2.5 MHz sample clock). Last, use the DAQmx Export Signal Property Node to set the Clocks->Sample Clock->Output Terminal to the PXI Trigger Line you want to generate the 2.5 MHz signal on.
It requires some creative programming, but you should now have a 10 MHz and 2.5 MHz signal routed onto two different PXI Trigger lines. I know this solution is a bit involved so if you have any further questions be sure to post back.

Route PXI SMB connector to Chassis Trigger line

Hi,
I want to use this toolkit to route my PXI SMB connector to a chassis trigger line.
I ask this question to the originator of this tool with no response:
Quote/
I used your library to route my SMB connector on PXI controller to the trigger 1 line of the back plane of the chassis. But I have a question, when I route the signal to the trigger line I always have a 3.5vdc that output from my SMB connector of the PXI controller. I use the PXI SMB Trigger Router - Map Trigger.vi with input to "Input for Direction, Trigger 1 for Trigger, and False for Inverted Polarity". What I need to do the get 0vdc at the SMB connector and not getting a short circuit with my external device that generate a Trig.
/Quote
Anyone have experience with this tool that can help me to resolve my problem?
Anyone have a different approach to route the PXI SMB trigger to a chassis trigger line?
Thank you
Dany
Dany Allard

Hi Frank,
I use PXIe-8106,8108,8130 Controller, with PXIe-1062,1065,1075,1000B Chassis and 5663,5660,5673,5672 RF Module.
Yes I have taken a look at this with no more success.
In my application I have some limitation on the number of module most of the time the chassis is full.
Can't add additional module.
Have you tested this example on your side?
Thank you
Dany
Dany Allard

Error message: no registered trigger lines

Hi,
I was using the example within labview 7.1 under "Hardware input and output ------Daqmx ------Synchronization------Multi-function---multi-funtion-synch AI-AO.vi". I was using pci-6032e card (device 2) for input and pci-6713 card (device 1) for output.
Then this error message jumped out when I was trying to run the labview vi.
Possible reason(s):
No registered trigger lines could be found between the devices in the route.
If you have a PXI chassis, identify the chassis correctly in MAX, and make sure it has been configured properly. If you are using PCI devices, make sure they are connected with a RTSI cable and that the RTSI cable is registered in MAX. Otherwise, make sure there is an available trigger line on the trigger bus shared between the devices.
Source Device: Dev2
Destination Device: Dev1
Task Name: _unnamedTask<9>
I am using RTSI cables connecting the two devices. But I don't know how to check if this RTSI cable is registered in MAX or not. If not, how could I register it?
Thanks,
Zexi,
http://mypage.iu.edu/~zzhuang

Thank you for your information.
I just had trouble finding that item RTSI cable in the MAX. Later in the help, I found that I needed to use "creat new" to creat that item. Thanks very much.
http://mypage.iu.edu/~zzhuang

Trigger line requested could not be reserved because it is already in use.

Hi , I am trying to export markers on PFI0 and PXI_Trig0 on NI5450 (in the script mode)
using the following code
There are no errors when I configure using the following code.
commWrapper.ExportSignal(PXICommonGenWrapper.niFgenConstants.MarkerEvent, "Marker1", "PFI0")
commWrapper.ExportSignal(PXICommonGenWrapper.niFgenConstants.Marker, "Marker0", "PXI_Trig0")
When I run the script, I get the following error
Trigger line requested could not be reserved because it is already in use.
Property: Marker Event Output Terminal
Destination Device: PXI1Slot2
Status Code: -89126
Would appreciate any solution that enables to me configure the two triggers/markers. I use these markers to trigger another PXI card (NI5644R on PXI_Trig0) and an external piece of equipment (using PFI0 output).
Thank you.
Solved!
Go to Solution.

Hi Surya,
Thanks for posting this on the community page. What this error is telling you is that it can't route a trigger to your requested destination because something else has already reserved that trigger line. One pottential typo is that your second ExportSignal command specifies niFgenConstants.Marker and not .MarkerEvent. This is a simple error to resolve but there are many possible sources. Is it possible for you to share the full code with me? Or,maybe you could host a join.me session and I can look at your full setup.
Sean Ferguson
Application Engineering Specialist | RF and Reconfigurable Test

Trigger Line Reserved

I'm trying to route a signal from a PXI-6251 PFI line to the Gate of a counter (PCI-6602) for pulse width and period measurements. When I add in the connect terminals VI, I get error code -89126: Trigger line requested could not be reserved because it is already in use. The documentation for the PXI-6602 says I can route directly from the RTSI bus to the gate of a counter. I'm not sure why this conflict is happening.
Attached is a VI showing my setup and jpg of the error I'm seeing. No error shows up until it hits the DAQmx Read VI.
Attachments:
Trigger Reserved.vi ‏35 KB
Trigger Reserved.JPG ‏54 KB

SirMutt,
The recommended way of making your connection would be to allow the driver to automatically configure the route for you. You can accomplish this by making the following changes to your code.
Also, I tested your original code with a PCI-6221 and a PCI-6602 and got it working after making the following change.
You were previously trying to connect the RTSI0 Line from the 6251 to the CTR Gate on the 6602, when in fact you should be connecting the RTSI0 Line from the 6602 to the CTR Gate on the 6602.
Either way is an acceptable, but the first the recommended method. Have a great weekend.
Ryan N
Message Edited by Ryan N. on 02-15-2008 03:19 PM
Ryan N
National Instruments
Application Engineer
ni.com/support
Attachments:
2008-02-15_150237.png ‏11 KB
2008-02-15_151534.png ‏2 KB

Drive trigger line by multiple devices (or connect many trigger lines)

Hey all,
Here's what i've been trying to do recently and am starting to get frustrated. So basically I want multiple devices to drive the same trigger line. Thought this mighyt be a problem for my application. Let me rephrase with a question that would give me the optimal solution. I have an PXI-6653 card on my PXI-1045 and what i want to do is say:
Send triggers generated on 2 lines (say PXI_Trig0 and PXI_Trig1) to a 3rd line (say PXI_Trig2). effectively I want the line PXI_Trig2 to get triggered whenever either of the first 2 get triggered. (If you want to think of this in a binary logic way, I want something like "Trig2 = Trig0 OR Trig1" , so I will get a rising edge on 2 whenever 0 or 1 have a rising edge)..
If it try to send (connect) both Trig0(source) and Trig1(source) to Trig2(destination) using NISYNC vi's, it wont work because it will say that Trig2 is already in use after connecting to one of the others (0 or 1).
Note that I dont want Trig0 or Trig1 to change, i.e i dont want to send trig0 to trig1 and then send trig1 to trig2
PS: when i say "send trig1 to trig2" i mean connect trig1 as the source and trig2 as the destination in the NISYNC connect trigger terminal VIs.
What can be done about this? Smart workarounds? or some way of overriding the fact that i cant connect multiple lines to the same destination line??

Hey mimomar,
Could you give us a little more background as to why you are trying to share the connection between these trigger lines? Most likely you will have to implement some sort of external connection to achieve this, but if I had more details as to the hardware that you are trying to synchronize with this setup then we should be able to give you the best solution. Let me know!
Regards,
Lars

How to change the network name and line name on iPad 4?

Could anybody help me how to fix this problem?
Previously I used qb (a mobile network in Cambodia) for my iPad 4 (iOS 7.0.4 non-jailbreak) the network name is qb.
The problem is that after I changed to use SMART (another mobile network in Cambodia) for this iPad the network name is still in QB and the Line name changed to SMART.
I don't know how to fix it now.
I have tried many methods as in restore through iTunes, reset network setting, reset all setting... but I still could not get the solutions.
I do hope to get it fix through all your experience.
Regards,
Panharith

Hi Anikesh
using SU01..u can change the password but can't see the old password..
Hope this helps, reward with points if it does...;-)
Regards,
Tejas

Firewire-B cable with built-in trigger lines?

Hi all,
We are building multiple vision systems. Each system has a camera with Firewire-b cable and also a Trigger Cable (with 3 conductors).
For our application, we need as few cables as possible. Our users are very concerned about having too many cables.
Does anyone know if I can purchase a firewire-B cable that has trigger lines. Some kind of two-in-one cable?
Our best option right now is to use spiral wrap.
- John

The signal is being generated by an NI DAQ card:
Pin 1: +5V
Pin 2: DGND
Pin 3: A digital pulse train that fires the camera shutter. From 0.25 Hz to up to 60 Hz.
Not really sure about jitter or latency. I'd rather not have much of either. But don't have specific requirements.
How can I put the signal "in band" with the FireWire cable? Are there unused pins I could utitilize? Not sure if it'd be worth the effort, but I am curious.
Thanks! This machine vision board is very helpful!

Trigger lines across busses

I have not been able to get more than one line to route dynamically. Here is the setup code:
    viUnmapTrigger(instr, VI_TRIG_TTL6, VI_TRIG_TTL6);
    viUnmapTrigger(instr, VI_TRIG_TTL5, VI_TRIG_TTL5);
    checkErr(viSetAttribute(instr, VI_ATTR_PXI_SRC_TRIG_BUS, 2));
    checkErr(viSetAttribute(instr, VI_ATTR_PXI_DEST_TRIG_BUS, 1));
    checkErr(viMapTrigger(instr, VI_TRIG_TTL5, VI_TRIG_TTL5, VI_NULL));
    checkErr(viMapTrigger(instr, VI_TRIG_TTL6, VI_TRIG_TTL6, VI_NULL));
    checkErr(viSetAttribute(instr, VI_ATTR_PXI_SRC_TRIG_BUS, 2));
    checkErr(viSetAttribute(instr, VI_ATTR_PXI_DEST_TRIG_BUS, 3));
    checkErr(viMapTrigger(instr, VI_TRIG_TTL5, VI_TRIG_TTL5, VI_NULL));
    checkErr(viMapTrigger(instr, VI_TRIG_TTL6, VI_TRIG_TTL6, VI_NULL));
When both TTL5 and TTL6 are setup using viMapTrigger() I get the following error when calling niTClk_ConfigureForHomogeneousTriggers() for the second group. I am able to map one of the TTL lines across busses but not both. Any ideas?
Error fffc2f4f: NI-TClk committed a session, and the instrument driver reported
an error.
Session index (starts at zero): 0
Error reported by the instrument driver:
DAQmx Error -89126 occurred:
Trigger line requested could not be reserved because it is already in use.
Property: Marker Event Output Terminal
Destination Device: Scan1
Status Code: -89126
Status Code: -250033

Hi tonys10,
Why are you both manually mapping trigger lines using viMapTrigger AND automatically configuring the crosspoint switches using niTClk_ConfigureForHomogeneousTriggers? When you use viMapTrigger you are reserving the trigger lines. This may be why you receive the error. I am assuming niTClk_ConfigureForHomogeneousTriggers is all you want to do.
If you desire to manually map the trigger lines, please follow the instructions in the attached pdf. These instructions are also documented in the NI-TClk Synchronization Help.
Please let me know if you have further questions or if this does not resolve your issue!
Chad AE
Applications Engineer

On the login screen on my mac says a property name, the laptop changed hands and I'd like to change the property line name to my own, how do I do that?

On the login screen on my mac says a property name, the laptop changed hands and I'd like to change the property line name to my own, how do I do that?

Open Accounts preferences. Create a new user account with the name and username of your choosing as well as your own password. Be sure to give the new account Admin status. Log out of the old account and log into your new account. Now, delete the old account.

Using PXI Star line for Sample CLK with 6551.

Using PXI Star line for Sample CLK with 6551.
Im trying to clock 5 6551s in a PXI-1006 chassis and a5404 in slot 2. I have configured the 6551s to use the start line as the sample clock but I still get the error
Possible reason(s):
Driver Status: (Hex 0xBFFA49B5) DAQmx Error -200586 occurred:
Hardware clocking error occurred.
If you are using an external sample clock, make sure it is connected and within specifications. If you are generating your sample clock internally, please contact National Instruments Technical Support.
Device: PXI2Slot17
Status Code: -200586
Any ideas why?
Thanks,
Brian

Nevermind...problem solved. I was exporting the wrong signal to the star line.
Brian
Message Edited by BrianPack on 11-28-2005 12:07 PM

4472 external trigger source name

Dear All,
I have a PCI-4472B which I want to program in order to acquire a signal from channel 0 whenever it recives a TTL signal throw the External Trigger input.
I'm using a modified example but I don't know which is the name of the external trigger source. I always recive this kind of error (for example if I connect a string containing "EXT_TRIG"):
code: "-200265"
"DAQmx Start Task.vi:1<append>
Property: Start.AnlgEdge.Src
Corresponding Value: EXT_TRIG
Task Name: _unnamedTask<DB>"
The program I'm using is of this form:
First of all, does this error mean that I didn't input the right external trigger source name?
If so, which is the right name of the external trigger source for NI4472B?
Thank you for help

Hi tooooommi,
would you mind expanding the error message? I cannot see the entire message and there should be more information about the error that we can use to solve it.
Also, have you tried connecting another Physical Channel control (like the one that you connect to the AI Voltage function) to the Start Analog Edge function? That may allow you to browse to find the right source for your analog trigger.
Let me know, so I can try to help you further. Best,
Corrado Degl'Incerti Tocci
Application Engineer

Where is RTSI trigger lines in 6711 card

Hi there,
I have a PCI-6711 card. The manual said it supports the RTSI trigger line to connect the external clock as the timing source. I try to find the pin associate with the RTSI in the layout for PCI 6711 but I didn't see any. I only see PFI8/GPCTR0_SOURCE. Is it the same thing? I am pretty confusing how to use external clock to replace the internal software-based clock. Thanks.
Solved!
Go to Solution.

TheRealMichaelJordan wrote:
Hi dragondriver,
Refer to this KnowledgeBase article for information on the RTSI trigger lines on PCI cards. The RTSI bus will allow allow synchronization between DAQ devices on the computer.
Regards,
Jordan G.
Thanks you. I didn't realize that there are some pin on the top of the card. But then cause my doubts. I have a 6711 card. Many posts said that it only support softwared based clock, I cannot use the external or hardware clock to drive the digital output. Ok, so my question is, can I connect the external clock to the RTSI pin so as a hardware clock and use it to drive the analog ouput and counter output? The manual said I can use the external clock connected to the PFI or RTSI, so are they the same. It is so confusing since I don't see any example to do that on 6711 card and I don't know which PFI pin I should go to ?

PXI trigger line names.

Similar Messages

Maybe you are looking for