PXI 6133 - P0.4

Has anyone had problems using P0.4 digital input on a PXI-6133 card?
I've tried to use it on a couple of cards and cant get it to work, all other lines on the port work fine.
Any ideas?
I dont think it is anything I am doing. Is this a known problem?
Solved!
Go to Solution.

Hi Scott,
I assisted you in testing the PXI-6133 card and together we found that the cable connecting the card to the SCB-68 was a SH68-68-D1 cable, which is typically used with our digital products where pin 19 (P0.4 on the PXI-6133) is not connected. The correct cable is the SH68-68-EP for the PXI-6133.
The SH68-68-D1 and SH68-68-EP cables look identical, the only visible difference being the part numbers on their label.  184749-xx for the SH68-68-EP and 183432-xx for the SH68-68-D1.
Best regards,
Tony Gibbs
AE NIUK

Similar Messages

  • PXI 6133 harware failure

    We have a PXI-1042Q computer chassis with 4 PXI-6133 data acquisition boards installed. All of the four boards were working. One day in last week, it seems like one of them stopped working. When I turned on the computer and the "Measurement&Automation Explorer"->"Device and Interfaces"->"PXI-6133XI1Slot6"->"Test Panels", it showed "Hardware failures, do you want to continue?". Then I clicked "yes" and entered the test penel. I clicked "start" then it showed error. The error message was: "Error-50152 occured at test panel. Possible reason(s): a hardware failure has occured. The operation could not be completed as specified".
    The other three boards is still working. Ii tried swapping the board in slot 6 (which is not working) with the boards in other slots. The working boards were still working fine but this board still didn't work. 
    Could anyone suggest what could be the reason and what should we do in this situation? We need all the boards to work for taking a complete set of measurements. We purchased the system about 10 years ago. The board which is not working was purchased probably 6 years ago. 
    Any help or suggestions will be appreciated.
    -An

    wohoho,
    Just to confirm, you tried swapping out this card into other slots to try and see if it receives data? Additionally, do you have a spare card that you could use in the mean time that can collect data to confirm the malfunction of the card? Can you try to test the card in a different chassis as well?
    If all these cases come back negative, it seems as though the card is broken and non functional. How this could have happened, there is really no telling. Age, constant usage, power surge, physical damage, and/or the environment are all possible reasons. 
    You can call into National Instruments Support line and create a service request to try and get the hardware repaired. 
    Rob W.

  • Ni pxi 6133 two channel triggering

    I have a ni PXI 6133 mounted on NI pxie-1071 chassis controlled by ni pxie-8735.
    I have 4 analog input channels and i would like to have an 'or' trigger on two of these channels.
    It's possible to set two trigger sources?
    Riccardo

    Hi Riccardo,
    it is not possible t o set two trigger sources for the same channel (setting the second trigger source overwrites the first) so it is not possible even for two different channels.
    You can try to route the trigger path internally (to verify if it's possible select your device from MAX and look at the table in "Device Routes" tab.

  • Analog,digital and pfi triggering of PXI 6133 card

    Hello,
     i am using PXI-6133 card. i observed that there  are three type of triggering options(i.e., analog, digital and PFI) available on each card. i want to know the difference? and also best  one.
    regards
    chandu

    Hi chandu,
                Analog triggering is based on the value of an analog
    signal. For example you can trigger when your analog signal goes above or below
    a specified value. Digital triggering happens on a rising or falling edge of a
    digital signal. For either type of triggering you must have a trigger source
    that is the signal you are triggering on. For digital triggering on your card this
    can be any PFI line. For analog tirggering it can be any analog input channel.
    A detailed explanation of the triggering capabilities of your PXI-6133 can be
    found in the S-Series User Manual. Triggering is discussed in Chapter 13. Also
    a more great summary of triggering in general can be found in the Developer
    Zone article, Tips and Techniques in Data
    Acquisition Triggering - NI-DAQmx. What triggering is better depends on your
    application and which one is more suited to your trigger signal. If you have a
    digital trigger source then digital triggering will work great. If your trigger
    source is an analog signal than you will probably need to use analog triggering.
    Let me know if you have any questions and have a great weekend.
    Thanks,
    Nathan
    National Instruments
    Digital Hardware Engineer

  • PXI-6682 + multiple Serie S & M cards cause timestamp delay

    I'll try to give as much info as possible and hopefuly someone will have an answer to this problem.
    Language: C++
    Introduction:
    1- I have (1) PXI-6682 (Timing card), (6) PXI-6143 (Serie S (8 analog inputs each)), and (2) PXI-6224 (serie M (8 analog inputs each))
    2- Every card is a task (so that's 8 tasks
    3- Every card is in sync (they give data equal...more or less... to one another
    PROBLEM:
    1- Timestamp is off by up to 200 ms (not drifting...simply off by a set number of ms)
    2- Every call to niSync_ReadMultipleTriggerTimeStamp gives me a timestamp off by that much
    I don't have any info on how the tester managed to know it was 200 ms off, my theory is he tested it with some older equipment to validate the new one

    Hello there,
    Kindly help me with DAQmx Time stamp related problem as described below.
    Setup : PXI 6133 Qty 4 (Slot 3, 4, 5, 6)
    PXI 6255 Qty 1 (Slot 2)
    PXI 6255 doing a Continuous Acquisition at 1 mSec Sampling and 1000 samples/iteration.
    PXI 6133 doing a Ref Triggered Acquisition at 1 uSec Sampling interval and Pre and Post Trigger samples of 100000 Samples each.
    Test : PXI 6133 - Reference Trigger Configured on PFI 1 line of First PXI 6133 card.
                             input Signal given to AI 0 OF First PXI 6133 card.
                             All PXI 6133 cards are included in a single task.
    PXI 6255 - Input given to Channel 0 AI
    External Function generator - One Digital Trigger generated of width 50 mSec High Interval.
                                               Another signal generated for input to above cards. (Square wave of 10 mSec Period - 5 periods generated on the rising edge of trigger)
    So It means When I acquire square wave in my waveform, I can consider rising edge of square wave as a rising edge of trigger (as both signals are generated aligned from external function generator)
    I have attached Screenshots and programs I have used for that.
    Problem: As both singal are generated at a same event, Both 6133 and 6255 should acquire that singnal at a same timestamp.
    I have also read related documents about timestamp but I could not succeeded to find any link in this.
    I am getting square wave 100 msec earlier in 6255 then of 6133.
    If I used only single card of 6133 then that inaccuracy of 100 msec is shifted to 25 msec.
    Please help me as soon as possible.
    Attachments:
    Timestamp mismatch between 6133 and 6255.docx ‏377 KB
    Timestamp mismatch in 6133 & 6255.zip ‏70 KB

  • Why does it take so long to clear a task (with DMA transfer) using the PXI bus?

    I am migrating a system which used to use a PCI-6133 (8 channel simultaneous AI) and PCI-6733 (8 channel AO) to one that uses a PXI-6133 and PXI-6733 mounted in a PXI-1033 chassis.
    In general, things seem to work (synchronized AI/AO running near the maximum rate on both devices), with the one exception that clearing an AO task on the PXI-6733 takes forever (on the order of 20-30 seconds).
    Even when I try the sinewave generation for the PXI-6733 in the MAX test panel it takes the same amount of time to stop the task. If I switch to using interrupts as the transfer mechanism, it stops immediately.
    I tried using the interrupt transfer mechanism on my more demanding set of synchronized tasks, but that does not produce the right behavior (even though it does not give any errors).
    Is there any trick (or better diagnostic) to help get my tasks working with DMA under PXI that used to work fine on PCI?
    Thanks in advance!
    Solved!
    Go to Solution.

    Hi Patrick,
    I'm using a PCIe-8361 controller. The computer is a Dell T5500 workstation running Windows 7 x64. I see the problem every single time I try to clear a task running on the PXI-6733, including my example using the Measurement & Automation test panel (from the very first time I try the Sinewave Generation onward). I can try other parameters in the test panel, but I don't need to adjust anything from the defaults (e.g., Rate = 1000) to get the behavior. I will also try installing the PXI chassis in a few other computers we have here just to confirm that it's not computer specific. From your line of questions I can at least gather that there's nothing obvious (like a known bug with the PXI-6733) and that I should expect this configuration to work.
    Thanks for your help and I'll post any other findings I obtain.

  • Single virtual channel with multiple digital ports

    Hi all,
    I have created a program that creates a task to read continuously from 3 digital port lines from the same device (PXI-6133). I am trying to figure out how I can retrieve the data from each port line to put into a waveform graph. Currently, I am using the DAQmx Read instance with "1 Channel N Samples" but I get a waveform with all values at the same time or a waveform graph with all three lines transposed.
    I am using Windows XP and LabVIEW 8.6.
    Appreciate any help!
    Solved!
    Go to Solution.

    Hi Matt,
    Thanks for your reply. Unfortunately thats not quite I am looking for. I am sending the DAQmx task the 3 port lines that I want therefore as I have read it bundles them all into one channel by default. What I want to do is take that one channel and parse out the data of each of the 3 port lines to create 3 new waveforms to work with individually.
    After fumbling around a little bit, I was able to sort of get what I wanted. I've attached a screen shot of that portion of the program. The red circle in the bottom right hand corner is how I want to end up. I only did it for one of the pieces of data just to try it out and the conversion to string is just for me to print out what I'm working with. Unfortunately, when I look at the waveform it seems like maybe some extra 0's are being thrown in because its not the same graph that appears from the beginning (when all 3 pieces of data are transposed on each other). Let me know what you think.
    Thanks,
    julissa
    Attachments:
    LabVIEW-ss1.JPG ‏57 KB

  • Monitor multiple channels for analog trigger with DAQmx drivers

    Hello! I would like to start a data acquisition of multiple analog channels (16) from an analog trigger. I would like trigger to monitor four of the (same) channels, and trigger when any one of them reaches a certain voltage. I found an example that would work with the Traditional DAQ drivers (using occurances), but can't figure out how to do something similar in DAQmx.
    Time is also an issue, as I would like to collect the first 80 milliseconds of data after the trigger (at a rate of 500,000 Hz).
    I'm using LabView 7.0 and collecting data off of two PXI-6133 cards.
    Thanks for your help!

    Hi Denise-
    After some research, I have found that it is not possible to use the functionality of DAQ Occurrences in DAQmx. Ironically, the reason that this functionality is available in Traditional and not DAQmx is due to the exploitation of an inherent limitation of Traditional that was upgraded in DAQmx. The multi-thread capability of DAQmx is a major advantage for most applications, but in this case it prevents the use of occurrences as they existed in Traditional DAQ.
    In short, this means that you can't directly use this functionality in DAQmx. You can however emulate this functionality with minimal software analysis of the incoming signal. I have attached a modified example VI that logs data to a chart only when the analog level of one of the channels being measured has exceeded a user-defined reference value. Basically, the task is running continuously in the background but the data is not actually logged until the signal is above a predetermined "trigger" level.
    Please let me know if the attached example is helpful for your application. You will see the input channels listed in the format "DevX/ai0:y" where X is the device number and y is the highest channel number of interest.
    Regards,
    Tom W
    National Instruments
    Attachments:
    Cont Acq&Graph Voltage-Int Clk Analog SW Trigger.vi ‏83 KB

  • Differences in DAQmx Trigger (VI)

    I am trying to figure out why DAQmx Trigger VI works differently with different hardware.
    Case 1; using PXI-6133 and Reference Analog Edge version of VI
    Case 2; using PXIe-6368 and Reference Digital Edge version of VI
    My users have shown me that using an analog signal on an analog channel for a trigger source in both cases works.  Now, using the same trigger source conditions, I want to use a PXI-6133 and Reference Digital Edge version of VI.  This does not work.  Why?
    My goal is to create a subVI that will use the appropriate DAQmx Trigger VI, given the source trigger hardware.  My application will aquire 2 sets of data simultaneously on different hardware.  One set based on a trigger, one set continueuosly.  Does this seem unreasonable? 

    TrigConfig.png - code from main VI that create parameters for Trigger
    Setup Triggers.vi - subVI that configures Trigger
    Kevins_Triggered Fast DAQ.vi - working VI for PXI-6133 and PXI1045
    Attachments:
    TrigConfig.png ‏177 KB
    Setup Triggers.vi ‏39 KB
    Kevins_Triggered Fast DAQ.vi ‏45 KB

  • Sine wave frequency error

    Hi! I'm pretty new to labview so any help will be appreciated!
    I'm trying to generate a 6-sine wave pulse using the attached generating and detecting vi. It all looks good, however, the frequency which I want the pulse to be generated ain't quite right no matter how I tweek it. For example, I keyed in the rate of generating pulse to be 1MHz in this case, but the detected signal is only 1 kHz (period = 0.001s). There should be no loss in this case. Other frequencies keyed in are also reduce by a thousand times. I think it is due to my Fs=1000 and #s=1000, because if i change my Fs to be 100 and #s=100, the detected frequency will be reduced by 100 times only. But if I reduce it, the resolution of my signal will be poor and I cant reduce it below 50 for a clear signal. Is there any way I can get the signal generated to be that which I typed in? Help!
    Thanks!
    Attachments:
    detect.jpg ‏48 KB
    generate.jpg ‏29 KB
    graph.jpg ‏118 KB

    Hi, I am using PXI-8331 with analog output PXI-6733 and analog input
    PXI-6133. I am generating voltage signals and collecting voltage
    signals as well.
    The problem I have is that when I
    intend to generate a 100kHz, 4 sine wave in a hanning window pulse, the
    received signal tells me that the signal generated was actually only
    100Hz (reduced by 1000 times) for Fs and #s of 1000, and it will be
    1000Hz (reduced by 100 times)  for Fs and #s of 100. What I hope to
    achieve is for the detected signal to show me that the actuated signal
    is indeed that which is keyed in. I am currently using DAQ assistant to
    control the frequency of my windowed sine wave. Is there any other way
    to go around doing it?
    On a side note, yes, I understand
    Nyquist theorem. I tried using 10kHz generating signal and 1MHz
    sampling frequency (100 times difference) for signal detection, but the
    results is exactly the same as that received using 10kHz sampling
    frequency and thus I believe there should be something I am not getting
    quite right about my signal generation since the frequency is always
    reduced by Fs times and I can't change its period.
     I have attached the vi I am using. Thanks a lot for your reply.
    Attachments:
    combining_testing2_6_2_testtest.vi ‏395 KB

  • Multi-task data logging with DAQmx

    I was wonder is it possible to use 'DAQmx Configure Logging' VI and 'DAQmx Start New File' VI for multiple tasks?  I'm doing synchronized high speed DAQ with NI PXI-6133 cards.  Each card (there are 16) must have its own task.  Although the DAQ is continuous, the user (software trigger) determines when data is saved to the disk and for how long.
    In my scenario the test length could be up to an hour with various test events scatter throughout.  The users want to display the data during the entire test length.  However they only want to write the data to disk during an event.  The event could last from 10 sec to 1 min.  That is why the users want to control when data is written to the disk.
    DAQmx Logging seems to work for a single task only, but I need to do multiple tasks.

    I've attempted to implement your suggestion, but I still do not acquire data for all channels for all tasks.  I've enclosed my VI.
    Attachments:
    TDMS Logging with Pause LoggingFSPR.vi ‏55 KB

  • Trigger acquisition and pulse generation

    Hi,
    I would like to generate a pulse on a PXI 6602 and start aquiring data on a PXI 6133 at the same time. 
    The attached VI seems to do the job but it has a race condition at the read vi. I am sure there is a better way to implement. 
    The problem is that the read vi seems to have an implicit wait until done. Labview does not continue but waits until the read vi finishes.
    Is there a way to commit a read task to the DAQs and then start and trigger it? Similar to what I did with the clock on the PXI 6602.
    Thanks!
    Attachments:
    DaqAndTimingTest.PNG ‏44 KB
    DaqAndTimingTest.vi ‏32 KB

    Take a look at this KB article: http://digital.ni.com/public.nsf/allkb/EBD603683446EC13862575B3006A63A2 It discusses how to synchronize your tasks. Not in the examples that there needs to be a start task for each task you create. Also take a look at both the Synchronization Examples in LabVIEW and the Multiple Device Examples. These should illustrate everything you should need to get your system up and running. I would also recommend that you use the Trigger VI's instead of the Property Nodes. 
    Alex D
    Applications Engineer
    National Instruments

  • Help! data manipulation for high speed streaming to disk from multiple boards and multiple channels

    I am using Labview 7.1 and have been trying to capture data from 12 channels simutaneously sampled at 2MS/s each and streaming to disk for up to a minute or more.  The hardware I am using is 2 x PXI 6133 S series boards with a MXI4 link to a Pentium D 2.8 Ghz machine with 2Gb ram.   I have 2 sata drives set up in a raid 0 configuration which should give me hard disk write speed faster or equal to the MXI-4 transfer speed. 
    I have first started off by using the example code "multi device sync - analog input- cont acquisition" which has enabled me to sync the two boards and sample at the required speed. 
    To stream the data to disk, I have first merged the data from each board  together to save it to one file.  I have tried using the storage vi's but I end up with a Daqmx read error (trying to read data that is no longer available).  I have played around with the read data size to the point that I either get a insufficient memory error, or I get the "trying to read data that is no longer available"  error.  I have also tried using the file IO blocks with some success and have found that I have been able to stream to disk only if I configure the daqmx read block to output the data in "raw 1D I16" format and plugging it into the file-write block.  In doing this, I have noticed that using  multiple channels on one daqmx read task, I will get all the channels in one 1D array rather than a 2D array organized by channels.  This makes it messy to read at the end of this, and I also don't want to write another vi to separate the channels, due to the high chance of getting the data mixed or messed up if I happen to change the number of channels on a board
    Is there a cleaner way of streaming this data to disk and keeping the channel data separated from each other?, and/or is there a better way to capture and handle the data I need? 
    I have attached the vi which I have got to consistantly work streaming to disk using the raw 1D I16 format.
    Thanks in advance to anyone who can help.
    Attachments:
    multidevicesync_analoginput_streamtodisk.vi ‏197 KB

    Hi,
    i can suggest following
    Refer to an example VI called as "High speed data logger.VI"  in conjunction with "High Speed data logger reader.vi" in Labview examples. Alhrough the logger might be in Tradiditional Daq format, it can be quite easily converted to Daq Mx format to store data in Binary (I32 format) . I have used this for many of my applications and i have found that the data retrieved does not have any "messups".
    Why not keep a seperate file for each card? This way, you do not have to load your application with extra process. You only have to acquire and save. After saving in Binbary format, you can retrive it offline, convert it to ascii format and merge the data files of various cards to get one consolidated ascii data file.
    hope this helps
    Regards
    Dev

  • Ignition spark noise interference

    Hi, My project involves using sensors to collect data in a shock tube that employs an automotive (>35kV, 175mJ of energy sparks) and capacitive discharge (2kV, 2Joules of energy arcs) ignition system to initiate combustion of fuel+O2. However, the signals collected by the NI DAQ is overwhelmed by noise caused by the ignition sparks/arcs, as high as 5V or perhaps more because the noise signal is saturated and cut off at 5V.
    Background: The DAQ consists of a PXI-1042 chassis with two PXI 6133 cards. The DAQ is connected to a PC located in another room by a 30m fiber optic cable (MXI-4 cards). The sensors are connected to the PXI-6133 cards by means of BNC 2110 panels using the BNC coaxial Analog Input sockets. Pressure transducers (piezo type) output is connected through a signal conditioner to the BNC2110. Other sensors include a load cell and accelerometer (also piezo type, through the signal conditioner) and type K thermocouples connected directly to the BNC2110 panel.
    The igntion sparks are discharged at varying rates from 10 to 50 Hz as desired. The required signals from the sensors also vary at these frequencies. Therefore a Low pass filter is out of the question. The sensors when connected to a digital oscilloscope did not show any noise.
    All cables (sensor wires, coaxial data cables, and the power cables of the ignition) have been shielded and grounded. The BNC2110 sockets are set to "Grounded Source". However, the noise is still very strong at 5V. Even the channels that are unplugged on the BNC2110 show the same noise pattern up to 5V, which correspond exactly with the firing of the sparks/arcs. We tried putting the DAQ within a grounded metallic box and moving it outside the room, but still the noise is not alleviated.
    The only thing that worked is to reduce the current in the ignition by connecting a series resistor thereby reducing the power of the sparks. This way we are able to get good sensor readings. However, the capacitive discharge delivers currents as high as 2000A, again causing a noise deluge. Also higher igntion energy yields better combustion, so we would really like to use higher ignition currents.
    Does anyone have any insights as to what we can do to cut down the noise, if I am doing anything wrong or can you just point me in the right direction?
    Thank you very much
    Philip Panicker
    GTA
    Aerospace Engineering
    University of Texas at Arlington

    Thanks for the reply.
    I have not tried differential mode, for two reasons. One is that most of the transducers' casing is the return/negative/gnd terminal, which when fixed into their sockets inherently grounds the terminal as all metallic fixtures of the hardware as well as the building are grounded. Secondly, the number of channels would then be reduced in half if used differentially.
    But the odd thing is that in the presence of noise, the DAQ output seems to contain no signals at all. For example pressure would be slowly varying, but in the presence of noise, no pressure signals are visible in between the railed noise signals.
    Today when we changed our dc motor for one with higher hp, we noticed even higher noise. All motors and induction machines with commutators are prone to spark noise.
    Thanks and any suggestions would be highly appreciated.
    Philip

  • LABVIEW FOR LINUX

    Hello,
    Presently i am a user of labVIEW 7.1 and 8.2.1 windows version.
    and also working on following hardware.
    SCXI-1001 12 chassis,
    SCXI-1125,SCXI-1124,SCXI-1160,SCXI-1162,PXI-1001,PXI-6251,PXI-6602,USB
    1600,USB 6602,PXI-1044,PXI-6133,PXI-8187,PXI-9257.
    since i am facing the problem of virus and sudden restarting of system,I am planning to switch over to linux version of linux.
    what is ur comment on my deceision?
    which version of linux OS will support all above mentioned products.
    what are the other advantages i can get from LINUX version?.
    Wil i get full programming help as available in windows?
    Can we easily learn the programming by reding the help?

    Hello chandhuu,
    Most of your hardware will be supported except for the USB devices.  The readme file for DAQmx 8.0 for Linux lists which devices are supported and by which Linux OS.
    The LabVIEW 8.5 readme file for Linux would also be helpful, along with this KnowledgeBase article, which lists which Linux OS versions support National Instruments software and drivers.  You will find that programming in LabVIEW for Linux is basically the same as in Windows, so you shouldn't have any trouble switching over if you are familiar with Linux and with LabVIEW.  Personally, I am not too familiar with Linux so I feel much more comfortable with LabVIEW for Windows.  What about just having a dedicated Windows PC that you can take off the network and use with LabVIEW so that you don't have to worry about viruses?
    Regards,
    Clint M
    National Instruments

Maybe you are looking for