PXI-2570 switch capacitance

I am generating a 5V peak, 400 kHz signal from an ARB (NI 5401) and inputting it into an amplfier with a gain of about 2, current draw around 400mA and an input voltage of 13V. I am taking the output of that amplifier and going straight into the PXI-2570 relay switches. From NO-1 and NO-2 I run the cable directly to DUT and get a ~2.5V peak-peak signal in which i should be getting a 10V peak-peak signal. If I take the output of the amplifier and without putting it through the relays I run it directly to the DUT i get the 10V peak-peak.
My Question is why when i generate the 5V peak, 400 kHz signal and run it through the PXI-2570 and attach to the DUT do I see the large decrease in peak to peak voltage? Is there some internal capacitance of the relays that would be causing such a drop? The spec for PXI-2570 seems to be able to handle a 400 kHz signal?

Murphyky,
There’s one more test I’d like you to do with your setup. Connect the signal from your amplifier, through the switch (modeled as 1 Ohm resistors), and then to a large load (not connected to your DUT). If the signal shows up without attenuation, then we can confirm that the switch itself is working correctly.
Switches have a resistance listed in the specifications manual. It is small, but it should still be considered in your design. You’ve basically built a voltage divider with your circuit.
A colleague of mine simulated your DUT in our Multisim circuit design software to see if we could determine the exact source of the signal attenuation in your DUT. What sort of load are the two transformers driving? We found that we could get a wide range of voltages across the DUT just by altering the load attached to the transformers. See the images I’ve attached for reference:
With the transformers driving 2 Megaohm loads:
With one load reduced to 100 Ohms:
Do you know the specifications of the amplifier that you're using? Is it possible that it can't source the power required to drive the DUT.
Let me know how the test with the switch goes. If it passes, there is some other limitation in the circuit that is causing the signal attenuation.
Good luck with everything.
Regards,
Jared R.
Precision DC Product Support Engineer
National Instruments

Similar Messages

How to obtain 16 x 64 configuration using PXI-2532 switch

Hello,
We have a PXI 1042 chasis with PXI-8106 microcontroller and PXI-2532 switch. With this switch and NI TB-2641 we are able to configure the system as 8 x 64 switch. We would like to configure switch as 16 x 64 matrix . After some research I found out that we might need to use two PXI-2532 switches to acheive this. My question is let us suppose we configure two switches as 8 x 32 matrices then how can one switch access the elements on the other switch (In order to make this 16 x 64)? Is this possible ?What are the available alternatives?
Thanks,
kartik

Hi Kartik,
We have a really great developer zone article on combining switches, I think you'll find most the information your looking for in there.
Matrix Switch Expansion Guide
I also found the following screen shot in the NI switches help.
It looks like this would be easiest if you had the TB 2642, which would allow you to do column expansion with two 8x64 setups (to make a 16x64).
Let us know if you have any further questions.
Thanks
Scott M.
Applications Engineer
National Instruments

PXI-2532 switch cannot be read in MAX

Hey Guys, I have a PXI-1036DC Chassis with a PXI-2532 switch. I am sure I
have setup the hardware correctly as the switch passes the self test. However
when I try and create a new virtual device I am not able to pick the PXI-2532
switch. Any idea why this would be the case? I have tried the 'configure NI
switches' button and the switch does even appear here. Also tried adding new
logical names and driver sessions but still have no luck.
If someone could please help me with this problem it would be greatly
appreciated.
Nikini

Hi Nikini,
Please continue this thread here.
Best,
Adam
Academic Product Manager
National Intruments

NI Switch Executive error when attempting to add NI PXI-2566 switch to new virtual device.

I just loaded Switch Executive and am wanted to explore its capabilities. I have a PXI system that I am setting up. Currently I have PXI-2566 cards in slots 8 and 9.
I was following the NI Switch Executive help documentation "Creating a Virtual Device" and attempted to create a virtual device with the 2566 modules and I got this error;
Error xBFFA000A occurred.
Failure loading driver module.
The driver for the DAQmx switch is not loaded.[DeviceXI1Slot9_ivi]
Attachments:
SwitchExecutiveError_01.bmp ‏229 KB
SwitchExecutiveError_MAX.bmp ‏364 KB

I had not loaded the "NI-DAQ 7" software that came with the 2566 switch card. I assumed that since MAX showed that I had version 7.2 of DAQmx that I was already up to date.
I received a new PXI-2532 switch, and when I got a "driver not found" error in Switch Executive when I tried to add the 2532 to a new virtual device, I had second thoughts on running the setup/install from the new discs.
After running the software install, I was able to add the 2566 switches to a virtual device in Switch Executive. However, the 2532 failed.
Error xBFFA4B4A occurred.
DAQmx Error -200181 occurred:
Channel name specified is not valid for the switch device.
Device: PXI1Slot10
Channel Name: r4
Attachments:
SwitchExecutiveError_02.bmp ‏35 KB

Problem Controlling PXI-2503 Switch through the IVI-C Switch API

Hi,
I'm writing an application to control a PXI-2503 switch in 1-wire mode using the IVI-C Switch API in order to route signals to a PXI-4060 DMM.
According to the programming instructions, I should be able to create a path from the "ab0" channel to a channel like "ch10" by calling IviSwtch_Connect( "ab0", "com0" ) to connect "ab0" to "com0" and then calling IviSwtch( "com0", "ch10" ) to connect "com0" to "ch10". However, after the program makes those 2 functon calls, the DMM doesn't get the correct signal.
When I use the NI Switch Soft Front Panel application to connect "ab0" to "com0" and then connect "com0" to "ch10", then the DMM gets the correct signal. Does anyone know what the Soft Front Panel tool does differently?
Thanks in advance to anyone who can help.
VRMan

VRMan,
Make sure that you have configured your 2503 to be in the 1-wire 48x1 topology...
Other relays that need to be closed for ch10 to make it to ab0
are "bc01" and "1-wire". Check out the hardware diagram for
the 2503 which can be found by going to
Start>>Programs>>National
Instruments>>NI-Switch>>Documentation>>NI Switches
Help, then browse to Devices>>2503>>PXI-2503 Hardware
Diagram.
When you use the SFP or program with LabVIEW, you have the option to
initialize a switch with a certain topology. For the 2503 1-wire
48x1 mode, this automatically changes "bc01"," bc02", "bc03", and
"1-wire" to the correct positions. Check to make sure that the
same is done when using the IVI-C driver you are working with.
Let me know if this doesn't solve the problem, or if you have any more questions. Best of luck on your application.
Regards,
Travis W

Controlling PXI-2501 Switches in C#

What is the best - prefered - way to control a PXI-2501/2503 Switch Matrix in C#.
I have only been able to find examples showing SCXI switching units. Is it done in the same way?
Code examples would be nice.
Thanks

I am assuming that the examples you are using are the DAQmx C# examples (Program Files\National Instruments\MeasurementStudio70\DotNET\Examples\DAQmx\Switches).
These examples work for all SCXI and PXI switches that are supported in DAQmx. NI-DAQ 7.1, the currently released version of NI-DAQ driver software, does not support PXI-2501/2503 under DAQmx. These modules will be supported in DAQmx in the next version of the driver.

PXI-2800 Switch Block Register Level Programming

I have a PXI-2800 with 2815A and B wand was wondering if there are RLP specs that I can drive with the Linux NIMHDDK?
I have been successful with the Switch RPL, and was thinking this would be an extension. That does not appear to be the case, this card is a bit different.
Thanks

I'm a few steps down the learning curve from plosio so bear with me here. I'm trying to control a pair of PCI 6259 multifunction cards which live in a mac (G5, OS X 10.4.4) using the NI-VISA package and xcode. I have run the driver wizard, and put the inf file it created where the inf file said it wanted to go, and modified the find-resource example code so that the PCI macros get defined. Still the viFindRsrc function can't find my cards. I know they are there because mac's system profiler can see them. one thing that makes me nervous is that inf file lists WindowsNT for the operating system. Another thing that makes me nervous is that i was under the impression that the wizard was also supposed to make new VISA readable drivers (.kext files if i am not mistaken) for each card, and I don't see any new kernel extensions when I search the hard drive. Thanks in advance for any help.

NI PXI Switch Matrix capacitance

Hi all,
I am doing a feasibility study for using a NI PXI crosspoint switches for Switching (connecting) different capacitance values to the input pins of a Device. The device is sensitive to capacitance value of 0.1pF. So any additional parasitic capacitance (Cp) added to the device by the Switch will seriously affect the functioning of the Device.
Based on the following NI article, it seems that the Switching setup might add up to some uF of Cp to the system.
I am trying to findout more details on using a switch for this purpose.
NI Article: http://www.ni.com/white-paper/8505/en
Snapshot:
If anyone has done similar thing please feel free to add your comments.
Anandelamaran Duraisamy,
Senior Project Engineer,
Soliton Technologies (P) Ltd,
www.solitontech.com

It seems the snapshot is not loading properly, reloading it
Anandelamaran Duraisamy,
Senior Project Engineer,
Soliton Technologies (P) Ltd,
www.solitontech.com

2570 Synchronise with LIN card

I have a LIN 3072 PXI card which is capable of outputting a 5v trigger pulse when a specific LIN frame occurs.
What I would like to do is connect this trigger output back in to my PXI 2570 relay card to close a specific relay for a period of time, the idea being to examine how a DUT responds to multiple interrupts happening simultaneously.
The documentation for the 2570 relay card mentions a trigger input but this only seems to be a trigger on the PXI bus and there is no other trigger pin I can locate on the front connector.
How can I connect this trigger signal to close my relays ?
Thanks,
Mike

Hey Mike,
Firstly, I apologise profusely for not getting back to you sooner. I have been away teaching for the past few days.
You have correctly interpreted my suggestion, although you have raised a very good question! Even though you are using a single relay you will need to implement some kind of scan list – there are 40 relays contained within the 2570 board, and so trigger lines could not be set up for each individual relay.
You should be able to create a workable scan list for a single item. If you are struggling with this, perhaps you could implement a scan list that switches between the relay you wish to open & close and a dummy relay. The dummy relay being one of the 39 unused relays within your module - interacting with this shouldn’t have any impact on your experiment.
Furthermore, there is plenty of information concerning scan list creation on the ni.com website.
Sorry again for the late reply, and thanks for your patience,
Best of luck with your application,
Rich R
Applications Engineer
National Instruments UK & Ireland

PXI-board only returns perfect sine wave

Hi, everyone!
This is a strange one:
Im peforming synchronized sampling from two boards; one is a PCI-6224 in my computer and the other a PXI-6229 located in our PXI-system. Being a rookie when it comes to labview, I was quite proud of myself for managing this all by myself. However, when i looked closer at a 10 sec test-record I noticed something peculiar. Although none of the 32 (differential) channels had inputs during the recording, the PXI-board returned 16 perfect 1 Hz sine waves with exactly the same amplitude as the measurement range. Attaching a signal to the terminal block didn't alter this. The PCI-board returns only weak 50 Hz (power network) noise, as expected. What is going on ??
I'm using a PXI-1031 chassis together with a PXI-8184 controller connected to the PC with a network cable. I trigger the pxi-board by sending the PC-clock through a PFI-port and a physichal wire.
regards, Einar

As I said, I haven't used LabVIEW 8 all that much. It's a bit tricky: you'll have to make a new Project, add the PXI as a new Target, and the add the VI you're trying to run underneath the new target. The last time I was playing with this I also had to open some ports in the Windows XP firewall.
If this is all a bit much for you, you might have a PXI controller that is configured to dual-boot both LabVIEW RT and Windows XP. If you reboot the controller in Windows XP mode, you can then access the PXI-6229 in the same way you currently access the PCI-6224... provided you don't mind copying the VIs over and hooking up a mouse, monitor, and keyboard to the PXI.
Switching from LV RT to Windows XP is most easily done by selecting the appropriate option in the PXI's BIOS. Check your PXI controller's manual for details.

How to measure different signals with PXI-2501

Hello everybody,
i have a an understanding problem.
I have a PXI-2501 switch and i want to measuere signals with the pxi-4071, so far so good.
I did some voltage- measurements and everything worked fine. Then i disconnected the power source and measured the temperature with a PT1000 in four-wire-mode ... also worked fine.
But i want to measure voltage and temperature, in the same VI, so i connected the voltage signal on CH0 and the PT1000 at CH5 (in four wire mode), and now i get problems. The temperature is fluctating. There are a few measurements that seems OK, and then i see some that are far away from the truth.
The VI consists of a state machine, the measurements are done in different states, of course with the correct scan list for each measurement.
Any suggestions? Am I doing something completely wrong?
Thanks
(and excuse for my english )

Hi Roman,
id I understand you right:
The temperature measurement works fine, if the sensor is directly connected to the 4071, but if connected via the 2501 you see the big deviations?
Have you measured the the resistance of the Switch-Matrix yet?
kind regards
Heinz

Pxi 2575 high resistance

I am having problems with the resistance across relays on a PXI-2575 increasing over time (faster than expected). I am using a PXI-2575 in combination with a PXI-4070 for manufacturing test. In some cases I am looking for an expected short circuit. The data sheet states that with no voltage applied (which I have none) I should see < 1 ohm for up to 2.5 million cycles. However, I am seeing upwards of 16 ohms across a particular relay after ~2500 cycles in many cases. I have a total 6 of these setups, and I am finding myself replacing PXI-2575 cards after less than 1 year of service due to these high resistances.
To prove to myself that it is the switch matrix (after measuring the UUT with a Fluke DMM) I used the following setup:
PXI-4070 DMM
PXI-2575 Switch Matrix
LFH200 Cable
24 awg wire
The PXI-4070 is configured for a 2-wire resistance measurement. The PXI-2575 is configured as a 95x1 2-wire mux. The DMM + terminal is connected to pin 46 of Backshell 0 (CH22+) and the - terminal is connected to pin 47 of Backshell 0 (CH22-). A small 24 awg jumper wire is used between pins 23 and 34 of Backshell 3 (COM+ and COM-). On a brand new switch matrix I see ~0.16 ohms using this test. On the most recent one I pulled out of production use, I saw ~16 ohms initially, with it falling to ~5 ohms after leaving it connected for about 5 minutes.
I am up to 4 PXI-2575 cards that suffer from this issue. According to the data sheet I should not be seeing this. Any help would be appreciated.
Thanks
Jonathan Rice

Steven
Thanks for the reply. I have done some more testing as you have asked. I realized I actually have 11 PXI-2575's, recently purchased 2 spares, and 3 more for new test equipment. They are all used in an identical manner.
We have made a total of 3 purchases. The first was for 6 PXI-2575's, the next was for 2 (spares), and the final was 3. With all of the swapping around, I am not sure where these failing ones came from at the moment, other than to say they were not part of the most recent purchase of 3. I am more than happy to provide serial numbers, if you can tell me which of the stickers on the board is the serial number. There are two identical looking stickers, one on each of the boards, that have different serial numbers on them.
Below is the data I have collected. Cards 5 & 6 can be considered "good" cards. Note that their readings did not change from their initial readings. They are from the most recent batch. We have no examples of cards with lots of cycles on them that do not exhibit this behavior. Prior to attempt 1 the cards had been powered off and removed from chassis anywhere from days to months. Between attempts 1 and 2 several switch cycles were performed and power was cycled on the PXI and the PC.
*All readings are in Ohms.
Below is a diagram of the setup I am using to test the switch matrices after they fail in the field.
Installing a new PXI-2575 immediately resolves the issue in the test set, and that test set continues to work for another several months.
Any help would be appreciated.
Thanks
Jonathan Rice

PXI-6255 Channel Configuration

The documentation for the PXI-6255 is VERY unclear (to me) on configuration. I found the attached sample VI and modified it to test my new card. The VI runs to make the relay connections (without the ~), but when I add the "~" to disconect, the attached error results. The error refers to "channels" and I can find NO documentation on how to set up "channels" for this card. The documentation seems to freely switch syntac between channels and com1 for example? What am I missing.
Attachments:
Switch Connect-Mult Channel working.vi ‏26 KB
PXI-2566 error.jpg ‏19 KB

Hi Alyeska,
When you say that you modified the example so as to test your new card, I am unclear as to what you are trying to do. What functionality do you want to test? The example that you attached configures the device, makes all the connections on the scan list, waits for those connections to settle, and then disconnects all the connections listed on the scan list returning to the original position, and waits for that to settle.
Now to address your confusion about “channels” and “com”s. Your PXI-2566 switch module is “Single Pull Double Throw (SPDT).” This can be seen in the attached image from the excellent NI-SWITCH Help that installs on your computer with the drivers. While most switch modules have a large number of input channels that can be connected one at a time to one outgoing common or “com” pin, your module has 16 common outputs, each of which has only two inputs. The two input channels are labeled “NC” for normally closed (connected) and “NO” for normally open.
The cause of your error message could be two things. The message states that it does not understand the “~” symbol, since it looks for a channel name (for example: ch0 or com0 or nc0) following the specified device. In order to disconnect, the “~” has to come before the device name, so your scan list would look like “~/RelayDevice/no0->com0.”
However, even when the “~” is in the correct location, you still may have difficulties. This is because DAQmx’s Scan mode is by default “Break Before Make” which means that the hardware will break one connection before making another. The only time the “~” disconnect needs to be used is when “No Action” mode is engaged and connections are not broken unless explicitly told to do so. This example program first connects the channels on the scan list, so when it begins to run through the list and sees the “~” it will throw an error. If you look at the block diagram, the disconnect function follows the connect, so every connection that was made on the scan list is then disconnected for you and the relays will return to their default NC position.
I am unsure of how you want to test your new card, but there are a number of great example programs included in LabVIEW with the switch driver. These can be found by navigating to the Help Menu>> Find Examples>> expanding the Hardware Input and Output folder>>expanding the Modular Instruments folder>> and then looking in the NI-SWITCH file. When you click on an example VI, a brief description will appear in the Information box to the right of the Example Finder. You might want to look at Controlling an Individual Relay.vi, Making Connections on a Switch.vi, and Software Scanning.vi. The other examples are for using switch modules with Digital Multimeters and Thermocouples.
Also, when you find some documentation unclear, I find the NI-SWITCH Help to be very useful. It can be found by going Start>> Programs>> National Instruments>> NI-SWITCH>> Documentation>> NI Switches Help. Here you can see the pinouts for your specific device and find explanations of syntax, scanning, and triggering.
I hope this explanation helps, Mallori M.
Message Edited by mallorim on 01-16-2008 07:28 PM
Mallori M
National Instruments
Global Customer Education Program Mananger
Calculate the time you will save with NI Training
Attachments:
single pull double throw.PNG ‏4 KB

Switch Soft Front Panel, Active Device misassigned

I have a PXI chassis with, among other modules, two PXI-2350 switches. Using the Switch Soft Front Panel, it seems the names assigned in the Active Device list ( the two 2350's in this case ) are backwards to what I expect. Is there a way to reassociate these names to the physical 2350's ?
Thanks
Solved!
Go to Solution.

Confustus,
That is an interesting issue that I have never seen before, your devices in Soft Front Panel should be linked to the devices as labeled in MAX. I was wondering, when you say "Using MAX, we can select a route that connects the power source to the DMM using "Switch 1" ( for example ), and we can see the voltage reading show up on the 4071 Soft Front Panel as expected", what exactly do you mean? If you were to select your hardware device and click test panels, the NI Switch Soft Front Panel loads. Are you saying that when selecting test panels and loading Switch Soft Front Panel from max works as expected, however opening the application outside of MAX does not work?
Or are you talking about the Test Panels that you open up within NI Switch Executive? The test panels for NI Switch Executive refer to the NI Switch Executive virtual device name, not the DAQmx device name. If you had named the NI Switch Executive Virtual device name in a similar manner, this could be part of the confusing problems that you are seeing. See images below:
NI DAQmx Test Panel Selection Brings this up.
NI Switch Executive test panel brings this up. If these device names are similar, I can see how this could be confusing.
Frank,
National Instruments
Staff Software Project Engineer

Handshaking DMM with multiple Switch devices - DAQmx error

Hi.
I'm trying to create a handshaking loop with DMM (PXI-4071), SWITCH (PXI-2569) and MUX (PXI-2575). All three instruments are in segment 2 of PXI-1045 chassis (slots 8, 9 and 10) and I am using PXI trigger lanes to route triggers.
I followed the NI article 'Multi-module Scanning with National Instruments Switches' - I modified the NI SWITCH example 'niSwitchDMMSwitchHandshaking' to configure the other SWITCH but when I tried to run the example, I got an error:
0xbffa6b9a - No registered lines could be found between the device in the route. (pop-up screenshot is in the attachment). It is the niSwitch_InitiateScan function for the second Switch that returned the error.
Changing PIX trigger lanes has no effect.
I tried both CVI and LabVIEW examples with the same result.
I even tried to use two 2575 MUXes - same result.
Can anybody tell me what am I doing wrong?
Solved!
Go to Solution.
Attachments:
errror1.JPG ‏26 KB

Hi Pavel,
For the purposes of this post, I'll define
the measurement complete signal (sent by the DMM to the switch modules
after each measurement) as 'MC' and place it on TTL0.
For the
purposes of this post, I'll define the scan advanced signal (sent by the
switch module(s) to the DMM once the relays have settled) as 'SA' and place
it on TTL1.
You mentioned you're using NI-Switch, which is NI's IVI
compliant switch API. Since the IVI Foundation regulates the behavior
of IVI compliant software, we must adhere to their rules when
implementing our API. Unfortunately, the IVI switch standard doesn't
provide a method to control arbiting of triggers between multiple switch modules
simultaneously.
Let's
look at what happens when we setup a system with multiple switch
modules handshaking with a single DMM. The DMM is going to take a
measurement and then send MC on TTL0. Meanwhile, each switch is listening to TTL0,
waiting for the MC pulse. When the MC pulse is received, each switch sets
the relays according to its next scan list entry, waits for debounce,
and then sends SA on TTL1. The problem we run into here is that depending on the switch module, number of relays connected simultaneously, jitter, etc, it's possible that one module will send the SA trigger on TTL1 before the other. Since the IVI spec doesn't provide any way to implement a 'master' switch or an arbitor, it's impossible to implement a system such that only the last switch that settles sends a trigger. Therefore, what happens is we get a whole bunch of switch modules sending triggers at slightly different times onto TTL1. If one switch is driving TTL1 high while the others are driving TTL1 lo, it's remotely possible that we could damage the TTL circuitry on the PXI backplane.
To date, NI hasn't seen any failures due to simultaneously driving the TTL lines high and low at the same time with NI switch hardware, but it is theoretically possible that damage could occur. For this reason, NI implemented a change in DAQmx
9.0.0, 9.0.1, and
9.0.2 that prevents a user from setting up handshaking with multiple switch modules while using NI-Switch. What does DAQmx have to do with this, you might ask? A component installed with DAQmx is responsible for verifying the triggers are valid.
Customers with existing NI-Switch multi-module handshaking applications will find that upon upgrading to any of the above three versions of DAQmx, the error you observed will occur. We've evaluated this customer feedback and have decided to revert to the previous functionality in a yet-to-be released version of DAQmx. Please note that NI does not advise driving the same TTL line with multiple sources due to the chance that we'll double-drive the line. Therefore, it goes with out saying that NI does not advise using NI-Switch in multi-module handshaking applications. We do, however, still recommend NI-Switch for Syncrhonous triggering because the switches never send triggers (in synchronous mode, the DMM just waits a predefined amount of time before switching).
Note that if you use the DAQmx Switch API, we're no longer bound to the IVI spec, which means we have an arbitor that ensures only one switch module drives the SA trigger on TTL1. NI highly recommends that customers evaluate using the DAQmx switching API for multi-switch handshaking applications. An example DAQmx handshaking application for the DAQmx Switch API is located in Example Finder»Hardware Input and Output»DAQmx»Switches»Switch Scanning with DMM - Handshaking.vi.
Note that in DAQmx, we'll only have one scan list, regardless of the number of switches we have. Note that the syntax in DAQmx scanning is different than NI-Switch. I'll defer a detailed explanation of the differences to the DAQmx and NI-Switch Help (search for 'scan list'), but in short, we'll need to include the DAQmx Device name prior to each connection. For example, in NI-Switch, if we want to connect CH1 to Com1:
CH1->Com1;
In DAQmx, we'll need to include the Device name:
Dev1\CH1->Com1;
Note that to add additional switch modules in the DAQmx API, we simply
call the Set Topology and Reset VI multiple times:
DAQmx keeps the
session loaded in memory and as I noted above; we define which switch
does the action as part of the scan list entry.
If you'd still like to use NI-Switch, you could roll back to DAQmx 8.9.5 or previous, or if you want to stick with 9.0.x, I highly recommend that we daisy chain the triggers as follows:
DMM Measurement Complete to Advance Trigger on Switch1 via TTL0
Scan Advance from Switch1 to Advance Trigger on Switch2 via TTL1
Scan Advance from Switch2 to Trigger Source on DMM via TTL2
Note that we'll need an additional TTL line for each switch module. Also note that some switch modules allow front panel triggers, which reduces the number of TTL lines we'll need on the backplane, but which requires external wiring between switch modules.
Message Edited by Knights Who Say NI on 06-11-2010 05:25 PM
Message Edited by Knights Who Say NI on 06-11-2010 05:30 PM
Message Edited by Knights Who Say NI on 06-11-2010 05:30 PM
Message Edited by Knights Who Say NI on 06-11-2010 05:31 PM
-John Sullivan
Analog Engineer

PXI-2570 switch capacitance

Similar Messages

Maybe you are looking for