Routing the PXI Controller 'SMB trigger port' to a PXIe-6674T timing and synchronization module for 'SMB to SMA' input / output.

[micgraph]

I'm trying to get some verification from NI gurus (…or Emerson) regarding the capabilities of the PXIe-6674T timing and synchronization module while using the following LabView libraries:

* NI Sync Library API

* NI DAQmx Library API

For most of the NI-Sync vi's, the timing and synchronization functions work fine for routing and generating a signal or trigger event. However, I really need to verify/clarify the following specific issues:

1. How do you setup the PXIe-6674T to receive (or send) a trigger source using NI-Sync through the ‘PXIe-6674T SMA terminals’ TO the ‘SMB trigger port (on the Embedded Controller - ex: PXIe-8861/8881)’?

     2. My understanding is that DAQmx API and the NI-Sync edge detection VI's are not supported on the PXIe-6674T. Is this correct?

     3. How do you setup the PXIe-6674T to simply route the SMB trigger port to the SMA terminals?

Any help in verifying what function 'are' OR 'are not' supported by the PXIe-6674T module would be great!

Especially 'routing the SMB trigger port to the SMA terminals'  and  'receiving/detecting an external trigger using the PXIe-6674T'.

Note: My external trigger source is a function generator. 

[santo_13]

Before we get there, why would you want to route the controller's trigger port to 6674T? can you describe in detail your application?

[micgraph]

Santo_13 - Thanks for the quick reply. It is an available port that we have the appropriate cables. The scope of routing the signal to (...or from) that port is simply to acquire or distribute the trigger signal. Also, to fully characterize the  PXIe-6674T module it would be good to know whether or not the routing is possible. To add some detail to the object, we will be generating a PPS signal to two different instruments. There are other ways to reach the objective for sure, but knowing that it cannot be used with this module is better than assuming (...at least while simply using the NI-Sync API).

[santo_13 · Accepted solution]

You can try using the DAQmx Connect Terminals API to route from the SMB connector to 6674T's PXI Trig line or the front end.

https://www.ni.com/docs/en-US/bundle/ni-daqmx-labview-api-ref/page/lvdaqmx/mxconnectterminals.html

Here is an article on using the SMB trigger line,

https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z0000019Uu6SAE&l=en-US

[micgraph]

Thanks again Santo.

Originally, I did use the DAQmx Connect Terminals VI to route the “PXI backplane trigger line" to the "PXIe-8861 SMB trigger connector”.

However, I tried to perform the “PXIe-6674T PFI" pin to "PXI backplane trigger line” using the NI-Sync API “Connect Trigger Terminals” VI. I will use the DAQmx Connect Terminals VI to make both connections, and see if that takes care of it. (...and thanks for the references)

Best regards,

Mike

[Kevin_Price]

FWIW, I only dealt with PXI timing modules for one project about 12 years ago.  I had to route a custom sample clock from one chassis backplane into a slot 2 timing module, route again to the front SMB connector, cable that over to another chassis, route from front SMB to slot 2 timing module and then route again to 2nd chassis backplane.

Whew, that's a mouthful!

Here's what I recall, but bear in mind this was 12 years ago, very likely different chassis, definitely older DAQmx and NI-Sync versions, and maybe a different timing module (though the model # sounds kinda familiar....).

It was necessary, at least back then with the hardware I had, to be careful about the *order* in which routing was done.  One of either DAQmx or NI-Sync was "greedy" such that I had to make sure I used its routing functions *last*.  Otherwise it would lay claim to too many resources and prevent the other driver from acquiring what it needed.

That's about as much as I can recall now.  It easily might not be relevant any more, but just in case...

-Kevin P

-Kevin P