SCXI-1314T

I have a number of test stands which use a SCXI-1520 with SCXI-1314T terminal block to measure various bridge-type sensors. I'm only using this terminal block for the convienence of the RJ-50 connectors, not for the TEDS functionality. I'm having a bit of trouble getting this setup to work with a third-party LabView RT application which supports the SCXI-1520, but which has not been tested with the SCXI-1314T terminal block.
Figure 3 in the SCXI-1314T manual shows the excitation, bridge output, remote sense, and shunt cal. signals being passed straight through the SCXI-1314T module from the RJ-50 connectors to the SCXI-1520 front panel connector. Is this always the case? The application vendor has suggested that the SCXI-1314T may not always pass-through these signals, or may need to be specially configured to do so.
Thanks,
Mark Moss

Hello Mark,
When you configure your SCXI-1520 in Measurement & Automation Explorer (MAX) you can also assign an accessory such as the SCXI-1314T to the module. Since you can also assign an SCXI-1314 as an accessory to the SCXI-1520, you should be aware that the signals in the 1314 and 1314T are different. But, to answer your specific question, yes, the SCXI-1314T always passes the excitation, bridge output, remote sense, shunt calibration, and TEDS data signals from the RJ-50 connectors to the SCXI-1520 front panel connector. Of course, if you do not wire a signal to the RJ-50 modular plug, the signal will not be fed through to the 1520. If you are having problems, one thing that I would suggest is making sure that the accessory to the SCXI-1520 is actually a 1314T, and not a 1314 in MAX.
Best wishes,
Wallace F.
National Instruments
Applications Engineer

Similar Messages

Verify SCXI chassis: Configuration specifies a SCXI -1600 module but nothing was detected

Hello NI Engineer,
I am using SCXI 1001 chassis with SCXI 1600 control module, SCXI 1520 signal conditioning module and SCXI 1314 connector block to acquire data from strain gage. Once I right clicked SCXI 1001 under device and Interfaces in MAX>> test>>I found a pop up window as “Verify SCXI chassis: Configuration specifies a SCXI -1600 module but nothing was detected”.
This is what I did. I connected wires from strain gage to SCXI 1314 connector block which is then connected to SCXI 1520, placed in chassis. I connected SCXI 1600 controller module to computer using a USB 2.0 cable. As soon as I switched on chassis, I found a pop up at task bar as “SCXI 1600 is detected”. I opened MAX and right clicked NI SCXI -1001 under devices and interfaces>> Properties>>selected the accessory under module tab and got “Configuration complete” message at top of pop up window, But once I right clicked NI SCXI 1001 >> test >> I found an error as mentioned above. Also once I right clicked NI SCXI 1520, under NI SCXI 1001>> Configure TEDS>> I was not able to click scan for HW TEDS option (i.e. It’s not shown up). How to overcome these two errors? Please help me. I also attached screen shots with this. I am using windows XP.
Thanks
Dhaya.
Attachments:
Error pic 1.JPG ‏115 KB
Error pic.JPG ‏97 KB

Hi Dhaya,
You seems in the correct direction to configure the SCXI hardware. There is nothing to test on the SCXI-1001 chassis instead you can test on the individual channels inside the SCXI. SCXI 1600 will auto detect the modules inside the SCXI Chassis and display it in MAX. The next step that you may need to do is to configure the Accessories (Connector Block) that is attached to the SCXI-1520 mentioned.
Once you configure the connector block, you should be able to test SCXI-1520 channel.
In regards to TEDS, Are you using SCXI-1314T connector block (http://sine.ni.com/nips/cds/view/p/lang/en/nid/13735) which is for TEDS sensors?
I hope that this helps
- Meadow -
LabVIEW 7.0 - 2011, Vision, RT, FPGA
TestStand 3.0 - 4.5

Does DAQmx handle TEDS calibration templates?

I've had no luck finding any info on this in what little NI documentation exists on TEDS and thought I'd try asking before running experiments to figure it out. If I have a TEDS sensor and include a calibration template (ID 40, 41, or 42) will DAQmx properly apply the calibration from the TEDS?

Tom, Thanks for the reply.
But I think that your statement that DAQmx handles TEDS directly is misleading. Consider the following:
Since I'm working with SCXI-1520 and SCXI-1314T hardware my discussion be slanted towards strain gages. I've configured 4 different TEDS EEPROMS with the strain gage template (ID=35), with unique values for physical min/max, electrical min/max, nominal excitation, and bridge resistance. I have a simple VI that consists of a DAQmx Create Task followed by a DAQmx Configure TEDS followed by a DAQmx Create AI Channel TEDS(sub) (I extracted this from the DAQmx Create Channel (TEDS-AI-Strain-Strain Gage) to eliminate the effects of the property node in the parent VI) followed by a channel property node (to observe the min/max, bridge resistance, etc.) followed by a DAQmx Clear Task. When I run this VI on one of my channels, it is clear that the physical min/max and excitation levels from the TEDS are not propagated to the channels properties by DAQmx (based on the property node in DAQmx Create Channel (TEDS-AI-Strain-Strain Gage) this is what I would expect), but the bridge resistance is (i.e. the value from the TEDS is displayed).
Another situation arises when dealing with the Gage Type and Type of Bridge entries from the template. The Type of Bridge is straight forward, either quarter, half, or full. But the Gage Type values available in TEDS provide many more possibilities than the types provided in DAQmx (Full Bridge I, II, III, etc.). If I set up a TEDS template for rosette, I get readings from the VI, but don't know if it's really using the information from the template.
So when I'm using the DAQmx Create Channel (TEDS-AI-Strain-Strain Gage) in my code, do I assume that the only parameters I need to pull out of TEDS myself are those necessary for the inputs on this function and it will extract any other fields it needs itself? How can I tell which fields from the template are being used by DAQmx? Do I need to explicitly pull out all the fields that apply and use property nodes to get these values into DAQmx?
I think most of this all boils down to a lack of detailed documentation. I could run lots of experiments, but can't afford to invest the time. So it looks like I'll have to pull all the fields from TEDS myself and use DAQmx function inputs and property nodes to try and make sure each channels is configured correctly. But if I have to do that, what's the point of having the TEDS variations in the DAQmx Create Channel function?

Has anyone used a touch screen monitor with scxi.I am having video lock ups while using LV and MAX

I have a PCI-MIO-16XE-50 daq card (dev1) connected to a scxi-1000 chassis address 0 ID 1, with a scxi-1102,1163,1163,1162 slots 1,2,3,4 respectively.Cable is connected to daq card to 1102 card .Micro touch screen is used on com2. Have tried other serial ports 1,5. Touch screen works fine with windows until LabView and max is installed .Video lockups,Max failures occur.MAX seems to confict with touch screen.

Max is the NI interface for all the drivers. It may be a specific driver that is causing problems, perhaps NI-VISA. I would try installing things one piece at a time. Might want to start by uninstalling everything so that you start with a clean system. First install LabVIEW with no drivers at all. See if the Micro touch screen still works. Then try installing NI-DAQ. Install each of the drivers you need one at a time. If you don't need something, leave it out.

Communication problem with SCXI 1000 Chasis

I have followed all instructions on this site...
I have a SCXI1000 chasis, in this I have a 1520 strain guage board connected (via connection kit) to a pci-mio-16e1 DAQ card... I can not auto detect the board and when I manually add the board (in MAX) and then verify I get "Card ** missing in slot *whatever slot I am using* "
any suggestions??
The problem might be that the SCXI chassis I am using is second hand.... I am worried it is not poweing the card... even though the "on" light is on... Which are the pins that supply power to the card and what levels should they be at (I can simply verify if it works with a multimeter then)
Thanks in advance,
Scott

Scott;
It's sort of hard to verify if the problem is on the chssis or not by probing some lines. Even if you get the power lines working correctly, the SCXI bus might be damage and you will have that same behavior regardless the power lines state.
The best way to troubleshoot that is by either trying another SCXI module that you know for a fact that is working, or to try that module of yours on a SCXI chassis you that is working.
Hope this helps.
Filipe A.
Applications Engineer
National Instruments

SCXI-1321 Bad Chips and Function Calls

8-4-04
This message is intended for the PSE of the SCXI-1321 and that person�s manager. Please route it accordingly. I would appreciate a phone response to 8**-2**-2*** so that I might share some specific experiences.
To the managers of the SCXI product line,
I have used the SCXI-1121 with the SCXI 1321 for some time now, approximately 6 years. Our company generally uses them for full bridge pressure transducers and similar applications. I have some suggestions that would make them more saleable. I also believe that you will never know how many customers you have already lost on this product line, for the reasons given below.
1. For many years the shunt resistor on the 1321 has been vastly unusable. What SHOULD be possible is to command the shunt resistor through a Labview command, and then read the virtual channel to see the shunted value. That IS the purpose of the feature. What happens is that once you set the shunt command, then read the virtual channel, the very act of reading the channel UN-shunts the resistor. What you read is some value part way between, because the chip relay from Clare actually ramps open and closed, unlike a mechanical relay. If your timing loop to read the value is consistent, you will consistently read a BAD value. Several VI�s tried to command the shunt, then quickly read the virtual channel, then loop and do it again, and thought they had solved the problem. Further investigation showed that all that was really happening is that the readings appeared to be stable because of the fast loop time, but were actually mid-release of the shunt for all readings.
2. NI eventually starting saying �don�t use virtual channels with the shunt�. In fact, there is a channel string that starts with the word �shunt� that was recommended. The only problem with this is that the data that comes back is not scaled! Keep in mind that NI has been pushing �virtual channels� on users for many years as the way to do business, and so entire test stands are developed around them and MAX. Because we depend on MAX to do the scaling, how are we supposed to be able to read the data scaled? Does NI expect customers to duplicate the efforts of MAX for every virtual channel and scale it separately? Do I have to keep duplicate tracking of scaling information so that my virtual channels will work in the main code, but again elsewhere so that my calibration routine can read the data? This is messy, and for most customers, untenable.
3. I was told, literally, year after year and release after release, that the problem would be fixed in future versions of NI-DAQ. Each release proved that the problem was not resolved. I am sure that many customers were not repeat customers as they found the problems associated with using a simple shunt on the board. I myself needed this hardware due to the 1121/1321 parallel operation capability.
4. After years of trying to fight with the issues above, and what seemed like random problems with the shunting of channels, a second hardware related issue has finally been identified. See SRQ#600753 with Michelle Yagle. The Clare solid state relays installed on the 14 different 1321�s I bought ALL had the same defect. Imagine what this means for troubleshooting! You swap boards to try to troubleshoot, but they are all defective and so you falsely rule out the board, the problem didn�t resolve with a different board. The lot# 0027T12627 of chips covers a wide range of 1321 serial numbers (see my SRQ for details). That means this impacts a lot of potential customers. The part is rated by the manufacturer to 80C, 176F. This particular lot stops functioning as low as 96F! A great deal of testing with heat guns, shop air, and a thermocouple showed that all the chips in this lot fail somewhere between 96 and 110F, well below manufacturers specs or NI�s specs on the board. I also tested lot 98, from a board two years older, as well as new chips from lot 03, which both worked perfectly all the way up to 212F (100C).
Conclusions:
I believe that the people that have tried to use your 1321 have generally had a miserable time of it, unless they already do their own scaling (like some of the Alliance members do.) This is because the shunt feature is not compatible with virtual channels, because NI did not offer a reasonable fix for this problem over a four+ year period, and does NOT advertise this limitation when people are making hardware selections. Further, I believe there are many people that have boards with the same bad lot of chips on them that don�t know it. They may have elected to hardwire their own resistors after fighting with random problems (temperature related). They might have elected to hardwire their own resistors to get around the NI-DAQ limitation. They might not even use the shunt resistor. But one thing is certain: NI needs to clean up this board�s operation, make sure that customers of the serial numbers in my SRQ named above are notified of the bad chips, and fully test that the use of the relays is transparent to LV virtual channels in the future. People will not trust NI products with this type of problems, and will not buy the product again if all the features don�t work!
I have helped NI resolve similar issues with the SCXI-1126 years ago, which had a number of scaling issues in NI-DAQ (the board read great when you used 1k, 2k, 4k, 8k, etc. even ranges, but if you set a virtual channel to 0-2200, the readings were off.) I plotted the problem, documented it with my sales rep, and worked at length with tech support. The boards also had a lot of bad buffer amplifier chips that allowed cross talk between channels, causing a lot of other spurious problems. Those experiences were horribly frustrating, but I now buy the product with confidence. It took a lot of push on my part to convince NI there was a real underlying problem. This 1321 board is similar.
I want NI products to be the best they can be, as I have dedicated my career around them. Please take this feedback to heart, and contact me at 8**-2**-2*** to talk about these issues. Additionally, I am speaking at NI week this year and will be available for discussion. Contact me at the same number.
Sincerely,
Tim Jones
Test Equipment Design Engineer
Space Shuttle Program
Space, Land and Sea Enterprise, Hamilton Sundstrand

Tim
Thank you for your feedback for the SCXI-1321 terminal block.
I wanted to see if it would be possible for you to move your application to NI DAQmx, the new driver for DAQ and SCXI as of NI-DAQ 7.0. I have tested the shunt calibration using a SCXI-1121 and SCXI-1321 and it works as it should. There are two ways to do the shunt calibration with DAQmx.
The first is to use the Calibration feature in the DAQ Assistant. When creating a DAQmx Task in either MAX or LabVIEW, you can select the �Device� tab and click on the Calibration button. It will then ask you if you either want to do a null or shunt calibration, or both. It will then do the calibrations selected and save the values to the task.
The other option to measure the shunted value is to use the AI.B
ridge.ShuntCal.Enable property node in LabVIEW. By setting this property to True, the driver will enable the shunt for the current measurements. If you are taking a strain measurement, the value will be converted to strain.
We are currently looking into the issues you are seeing with the Clare relays to see if other users could be affected.
Brian Lewis
Signal Conditioning PSE
National Instruments

How can I acquire data in a PCI DAQ board using a SCXI rack?

Hello.
I have an acquisition system that consists in:
· 3 PCI DAQ boards:
- PCI-MIO-16-E-1
- PCI-6052-E
- PCI-6034-E
· 3 cables to connect PCI boards and SCXI modules
· 1 SCXI chassis:
- SCXI-1001
· SCXI modules + terminal blocks:
- 4x SCXI_1121 + SCXI_1320 (for voltage analog inputs)
- 1x SCXI_1520 + SCXI_1314 (for strain gauges)
- 1x SCXI_1530 (for accelerometers)
I have been trying to acquire different signals (specially voltage signals that are easier to reproduce) but I haven't been able to do it. I can't read anything from MAX or LabView. I have tested the PCI boards with a SCB68 terminal block (without any SCXI component) and they work properly. Problems appear when I use the SCXI chassis and the SCXI modules. I don't know if there is a problem with the hardware or it is a wrong configuration.
I guess channels in the SCXI modules correspond to analog input channels in the PCI board they are connected to, but I don't know if I have to read data from analog input channels of the PCI boards or from SCXI channels that appear in MAX (I have tried both posibilities, but they don't seem to work).
I don't know if I have to use Differential, RSE or NRSE configuration. I have tried all of them. Sometimes I only read noise, sometimes signal is fixed in a limit value (maximum or minimum, it depends), sometimes it's fixed in a value near zero,... I have changed connections and configuration options so many times I can't exactly say when one thing or another happens.
I have tested only one PCI board with only a SCXI module in order to avoid interaction and confusion. Nothing.
I think I have tried changing almost every option in MAX, but it doesn't work.
I'm sure I'm missing something and solution is quite simple, but I can't find it.
Can anybody explain to me how to connect and configure my system to read any signal? I only need a few steps or highlights. Maybe some clues about what the problem can be.
Thanks!

I have several comments and suggestions:
A) Have you "added a device" in MAX and actually added the SCXI chassis? This step is necessary to get the chassis to work. Click on "add a device" and choose the 1001 chassis . Do this for one DAQ card and one module only initially. The Set Up wizard should walk you through the configuration. If you are unable to add a chassis within MAX, I suspect the chassis is not working correctly.
B) Once configured, you can examine the SCXI channels in MAX as follows:
1) Open the DAQ card in MAX and Open the Test Panels
2) For the SCXI channel to view, use the following convention OB0!sc(n)!md(m)!ch where the letter (n) corresponds to the chassis number in MAX (usually = 1), the letter (m) corresponds to the module number (slot) where the module is located in the chassis, and (ch) represents the channel(or channels) you wish to view. So presuming chassis ID=1, and a module in slot 1, and you wish to view channel 3, you would type the following in the channel field for the DAQ card channel to view:
OB0!sc1!md1!3 (note OB0!sc1!md1!3:6 will display channels 3 through 6)
All of the SCXI channels for a given DAQ card are multiplexed through channel 0 of the DAQ card, Channels 1 and up are not used, hence the initial three characters in the SCXI call refer to "On-Board Channel 0 (OB0)"
C) For the subsequent set up, it will be necessary to first add the additional modules to the chassis (when powered off). Then open MAX and update the chassis. (If you get an error then simply delete the chassis reference in MAX and add a new chassis). You will then be required to set the interface mode of each module as either parallel or multiplexed. In parallel mode, you associate a distinct module with a distinct DAQ card in the host PC. For those DAQ cards that will address multiple modules, you must first configure the modules to be in adjacent slots in the chassis and then assign the first module to the cabled DAQ card - then all of the modules assigned to that DAQ card should be configured in "multiplexed" mode.
D) Once the chassis has been properly configured, you can click on each module and set the gains, filters, and terminal block types.
I hope that this helps to get you started.

How can I read channels from different SCXI modules simultaneusly?

Hello.
I have a system that consists in:
- Three E-series DAQ boards (PCI-6034, PCI-6052 & PCI-MIO-16E)
- One SCXI chassis (SCXI 1001)
- 4 SCXI modules for voltage measurement connected to PCI MIO 16E
- One SCXI module for strain gauges connected to PCI 6034
- One SCXI module for accelerometers connected to PCI 6052
I have to develop a software application that reads all the channels at the same time or at least in the same program cycle. I have tried to create only one DAQmx task containing all the channels, although they belong to different DAQ boards (and SCXI modules, of course), but it seems to be impossible to use channels from different devices in the same task.
So I have created three different DAQmx tasks, one for each device and its channels. I have used one "DAQmx Start Task" VI for each task at the beggining of the loop in order to use them independently, reading their channels inside the loop in every program cycle.
When I have run the program I have get the following error:
"ERROR -200619 ocurred at DAQmx Start Task.vi
Chassis cannot be used for more than one scanning operation at the same time.
Do only one scanning operation or combine multiple scanning operations into a single operation."
What is the problem? How can I combine these multiple scanning operations? What can I do to read all channels at the same time?
Thanks.

Hello pablomendana,
it's ok that you got an error when trying to use more than one device on the same task. According to the setup you have, I agree that 3 tasks should be put in place.
The key question I have is... Have you configured manually at MAX the SG and accel. modules to be in Parallel mode?
I would not expect the error you get if they are in parallel mode (in which you could even read directly from the DAQ board, using DAQ device channels instead of SCXI channels).
Unfortunately, I haven't been able to setup a system similar to yours, but I would like to know more details on what you've tried so far.
Also, I recommend you that if still need help on setting up the system, use NI's SSP program to get support from your local NI Application Engineering organization, as this will be faster than the forum.
Regards,
Jorge M.

How can I set the gain on a SCXI-1102 module without having my computer lock-up for 3 seconds?

Forgive my insolence, but did it never occur to anyone that spinning in a hard loop while polling a status register to set a gain for 3 seconds isn�t a great idea?
I have a number of SCXI-1102 modules to set the gains on, and it takes several seconds for each. Reading the documentation on the subject indicates that the SCXI_Set_Gain call polls a status register waiting for the gain to settle before returning � and it doesn�t even yield while doing so.
Are there any other ways I can set the gain? Is there a way that doesn't poll the register that returns in a reasonable amount of time?
AFAICT, there's no good reason to only allow one module to be s
etting its gain at a time. An asynchronous call it really needed - one that makes it the API programmer's responsibility to check the status of the register, or one that spawns a thread and sleeps between polls, and signals an event or invokes a callback or some-such-thing. Or you could even just sleep for three seconds after setting all the gains, this way the delay would be 3 seconds total � not 3 seconds for each gain set.

This NI-DAQ function call directly accesses the nidaq32.dll. While the nidaq32.dll is multithread safe, it is not a multithreaded DLL. This is also described in the KnowledgeBase entry 1V9DSHDM: "Can NI-DAQ Handle Different Operations at the Same Time? Is It a Multi-threaded DLL?"
You are correct that the SCXI_Set_Gain function is not asynchronous. Thus, you do have to wait till that function returns before calling the next one. LabVIEW has found a way around this. So, you can actually use the LabVIEW functions to set the gain on these modules without having to wait as you do with SCXI_Set_Gain.
Regards,
Geneva L.
Applications Engineer
National Instruments
http://www.ni.com/ask

How can I use LabVIEW 6 on a SCXI-FRQ8 module?

Hi, here is a description of our problem. We hope that you will be able to help us.
We bought from NI, a few years ago, some SCXI-FRQ8 modules. (Those modules were made by a company called Developpement Ingenierie in France) The problem is, we can not update to the version 6 of labview since we do not have the drivers to install Labview 6. The drivers we have are for Labview 5.x and 4.x.
Furthermore, we can not update those drivers by ourselves, since we do not have acces to the diagram of these VI drivers. We tried to contact that company, but no one answers. So maybe the company does not even exists anymore.
We would like to be able to install Labview 6 on these modules and if we can
make it work, we will probably buy some new SCXI-FRQ8 modules(if we can still buy them).
Thank you

The driver for the SCXI-FRQ8 provided by DI originally did not include the block diagrams. So if you try to use them in a newer version of LabVIEW, you will receive error messages because LabVIEW needs the source code to recompile the code into the newer LabVIEW format.
National Instruments can provide you with the code you need to use this module with LabVIEW 6. Request this code at http://www.ni.com/ask.
Raecine Meza
Applications Engineer
National Instruments

How do I use the counter and digital signals of the 6071E while it is connected to SCXI modules?

I am contemplating using a PCI 6071E with SCXI. We have the boards (6071E), we would need the cable (I suppose SH1006868) and the SCXI system. I would like to know how would you access the counter and digital line capabilities of the board. I will be using a SCXI-1314 with a SCXI-1520 Module for strain measurements but will need to use the counter and digital lines of the board as well. Can this be done? If so, how and/or what else do I need?

I think this KnowledgeBase will answer the question for you.
Accessing DAQ Board Counter Pins with an SCXI System
Otis
Training and Certification
Product Support Engineer
National Instruments

How to Optimize SCXI 1600 for speed with Thermocouples

I'm working on a data acquisition system for my engineering firm and I'm trying to find a way to use our new thermocouple system as fast as possible.
The requirements for the DAQ process are:
Read 32 voltage channels from a PCI-6071E card
Read 32 thermocouple channels from a SCXI-1600 with an 1102C accessory
Complete the entire operation in under 5ms (this is so other parts of the program can respond to the incoming data quickly and trigger safety protocols if necessary)
Using LabVIEW 7.1 and MAX 4.4, I've got the voltage channels working to my satisfaction (with traditional DAQ VIs) and the rep rates I measure when I run the program are around 1ms (I do this by putting the DAQ code in a loop and reading the millisecond timer every time through that loop, then calculating the average time between loop executions). I have been trying to get similar performance from the thermocouple channels using DAQ Assistant and DAQmx. Some of the problems I've encountered are:
Very slow rep rates with 1-sample and N-sample acquisition modes (300-500ms)
Good rep rates when I switch to continuous mode, but then I get buffer overflow error -200279.
When I attempted to correct that error by setting the DAQmx buffer to overwrite unread data and only read the most recent sample, the calculated sample rate went to 20ms. It was around 8ms when I left the error unhandled and continued acquisition.
At this point I'm out of ideas and am just looking for something to try and optimize the DAQ process for speed, as much as is possible.
Thank you for any help.

I guess I would be interested in checking out your code to see if there is anything I can recommend on changing. However, I do have a few general Ideas of how to improve your performance. These recommendations are purely based on what you could be doing to slow down the speed of the program because I am not sure how exactly you have everything set up.
-Are you setting up the task and closing the task each time that you read from your daq card?  the way to get around this is to only have the DAQmx read vi in the while loop so you do not have time alloted for opening and closing the task each time.
-Try using a Producer/Consumer architecture. This architecture uses queues and splits the aquisition with the post processing.  Here is a link to how to set up this architecture and some information on when to use it.
Application Design Patterns: Producer/Consumer
http://zone.ni.com/devzone/cda/tut/p/id/3023
Message Edited by Jordan F on 02-06-2009 04:35 PM
Regards,
Jordan F
National Instruments

How do I add a SCXI-1160 to my system?

This falls into the 'had some extra parts, let's use them' category.
My current configuration is PCI-6221 into a SCXI-1001 Chassis with a 1349 Cable Adapter. The only modules I have in this chassis right now are a 1102/b/c with a 1303 terminal block and a 1180 feedthrough with a 1302 terminal block.
I've come across a spare SCXI-1160 module with 1342 breakout connector. I'd like to use this for some switching tasks rather than the analog outputs of my 6221 (need more channels than the card has, which is two). This module came to me with no documentation or cabling so I'm unsure how to connect it to my current system.
If someone could point me in the right direction for the correct cable to purchase I'd appreciate it, and input on the connection setup as well. Much thanks
Ralph
Still confused after 8 years.

Hi Ralph,
You shouldn't need any extra cabling to be able to control or interface
with your SCXI-1160 relay module. The 1160 can be controlled from
the PCI-6221 M-Series card (via the 1349 adapter), and the 1324
terminal block provides the interface for the relays. Check out this tutorial for more information on connecting signals to the 1160.
Try installing the 1160, adding it to your SCXI chassis in MAX, and try
switching with the Switch Soft Front Panel. Let me know how this
goes.
Have a great day!
Travis W

Can I use SCXI 1000 (110v US model) in 220V 50Hz country?

Somebody is selling SCXI 1000 with couple modules to me at a very good
price. However, it is a US model(110V) while in my region we use 220V
50Hz. Can I use a fransformer to convert 220V to 110V and use
with this chassis? Are there any know issues? This will be used for
hobby projects. Not a mission critical task
Thank you.
Message Edited by System on 08-20-2005 01:35 AM

just4fun,
Let me start my response by saying that most likely there should not be
any problems with using a transformer. If I were you, I would
purchase a voltage adaptor that also changes the frequency of the power
supply from 50 Hz to 60 Hz. Neglecting to change the frequency
could cause problems in some devices that have power supplies not
intended for 60Hz VDC power (this could lead to a noisy DC power line).
With that said, the newer SCXI chassis can handle the different
voltage levels without a voltage adaptor, but you are supposed to
change the fuse inside the power supply to a lower amp fuse if you
switch from 110 to 220. You should be able to determine what
types of power you can connect to the scxi-1000 (110V/60Hz or
220V/50Hz) by reading the labels on the back of the SCXI chassis.
If the labels on the back of the SCXI chassis make no sense, feel free
to reply with the info from the labels in an email and I can help you
decipher them.
I hope this helps,
Lorne Hengst
Application Engineer
National Instruments

How can I use LabVIEW to ground floating SCXI-1520 channels (in order not to lose scanning capabilities from the multiplexer)?

Currently I am reading quarter bridge strain with several SCXI-1520s. When in MAX I noticed my values were no longer reading after a certain gage and as I attempted to troubleshoot, found out that the multiplexer in this module will not scan past any open channel (or if it does, channel results are not consistent) for a very logical reason. If I lose a gage, I usually lose any data from any subsequent gages which we really cannot afford.
Are there any suggestions programming in LabVIEW (right now i'm using NI-DAQmx with an analog task set up)so that each time my loop executes, the program will check for any open channels and either not collect that data or change the order of acquisition (i.e. place the open channels last on the scan list?
I'm open to anything that might be of help

Yes, by "open channel" i mean that there is no signal returning from the gage because it has broken off the structure or the signal to the terminal block has been disconnected somehow.
When I lose data, I'm referring to the data that is acquired on following channels. The behavior appears to be fairly random (which was a troubleshooting nightmare ) but usually if a channel is open, then that and those behind it in the scan order do not return any data. It returns a number like 10.357E-6 and I do not pick up any noise or fluctuations. As far as I understand, the multiplexer stops scanning at this point (open channel) because it has nothing to ground to and subsequently "hangs" - not (or randomly) scanning the following channels. I have gone through the bridge configuration and as of yet, have not figured out how to fix this using any hard-wiring techniques. I emailed NI, and was sent a library file to "ground the channels" but it actually resets the Analog input Task I have defined each loop.
I am new to NI-DAQmx so I do not know if this will alter any configurations I already have in MAX for NI-DAQmx. Will it override? I am concerned it will slow my loop time, and also I cannot see the code for this sub.vi so am a little skiddish about using it if i do not know if it can be tailored to my app.
What do you think? Am I on the right path?

SCXI-1314T

Similar Messages

Maybe you are looking for