Gigabit ehternet card in real time PXI chassis

I was reading document # DZ52103_US about general real-time
information. This document states that plug in ethernet, serial, and
GPIB cards are not supported for real-time I/O operations. I want to
use a plug in PXI gigabit ethernet card to transfer data from my real
time PXI chassis to a host laptop computer. Can this be done?

Currently, the only PXI ethernet controllers supported in LabVIEW Real-Time are the PXI-8211 and the PXI-8212. These are not Gigabit cards. This information is documented in the following link and will be updated as ethernet device support in LabVIEW Real-Time changes.
If you have any further questions, please post a reply.
Regards,
Kristi H
Applications Engineer
National Instruments

Similar Messages

  • Compatibility of Pattern I/O with a PXI-6533 card with real time application

    Hi,
    I use a PXI-6533 card on a chassis with a PXI-8145 RT controller. I want to acquire 32 bits of data with this card at 1,25 kHz. These data are generated by an external FPGA card together with a clock signal. Referring to the 6533 documentation, a simple way to synchronize the acquisition is to use pattern I/O, entering the clock signal on the REQ pin. I tried the LabVIEW example Cont Pattern Input.vi. It seems to go well, but it does not work when I change this .vi priority to Time-critical or any higher priority than normal. Is there an incompatibility between this type of acquisition and real-time ?

    Hi,
    Sorry for this late answer, I effectively added a �wait until next ms function� in the time-critical loop and it seems to work. In fact, I don�t see exactly how, but it works with 1ms up to 50 ms.
    Nevertheless, the next step is to add the content of this example in a more complex system with a communication loop to transfer the acquired data to the Host PC. I already have such an architecture, with a �time-critical priority� .VI to read the data at 1.25 kHz and a RTFIFO to transfer them to a second �normal priority� .VI loaded on the PXI, that ensures a TCP communication with the HOST PC. This architecture works correctly on another application with an internal clock, BUT doesn�t with this example, even with your solution.
    In
    fact, it seems to work when I put the two .VIs loaded on the PXI in �normal� priority, but with a tremendous jitter (the frequency varies from 1 to 2 kHz) and a scan backlog that gets full very fast. Then, the PXI crashes as soon as I change any priority.
    You�ll find attached these three .VIs and I hope this could help to find a solution.
    Cordially
    PS: Since we started this thread, I�m in relation with NI Support France on that subject. Nevertheless, we haven�t found any solution yet and any new idea is welcome !
    Attachments:
    HOST_Comm.vi ‏532 KB
    RT_Comm.vi ‏265 KB
    TCLoop.vi ‏256 KB

  • Open a txt file in a real time PXI target

    I want to open and read a txt file when targeting to a PXI, running a real time OS. The file is saved in a specific directory of the real time machine. When I run the typical Labview (version 7.1) examples there is alwasys an error message.

    Hi Matt,
    I hope you're doing well.  To be able to open files on the host from the RT target or vice-versa, you most likely will need to FTP the files back and forth between the two.  You need to have the files local on either machine to be able to edit or view them, and FTP is the simplest way to do so.  You can connect to your RT target via any standard FTP utility as discussed in this KnowledgeBase article.  I hope this is helpful.  Let us know if you have any additional questions though.
    Thaison V
    Applications Engineer
    National Instruments

  • Does a capture card improve real time functions?

    I am reading posts regarding capture cards and i figured for DV material, capture card may not be necessary as firewire is there. but does capture cards improve the effeciency of the machine /CPU , does it render faster and play more real time effects?
    thanks
    sameer

    The Aurora is a Standard Definition card and the Decklink is an HD card. I don't have them both installed at the same time...I put in what I need. Right now I am working with HD so I have the decklink card in.
    AJA I/O is a standard definition "solution." I say solution because it isn't a capture card per se, but rather an external box that captures SD signals (SDI, Component, Composite) and inputs them into FCP via a firewire connection to the computer. This allows it to be used on multiple machines easily. The Kona series are High Def cards that need to be installed in the PCI slots of your computer.
    What is my workflow with the DSR-11? Probably the same as you. DV/NTSC Easy Setup, then connect it to the computer via firewire and capture. When I am done, I output back to tape. What else is there to do with this?
    Codecs? DV, 8-bit uncompressed SD, DCPRO 50, DVCPRO HD. Depends on the project I am working on and how it was shot.
    10-bit uncompressed DV? DV by nature is compressed 5:1 when it is recorded to tape. When you capture that via firewire from your DSR-11 deck, you are capturing it at the highest possible quality. It is simply a file transfer. Now, if you were delivering on DV then you don't need a capture card. But if you were, say, needing to deliver a digibeta master, or betasp, then you'd need a capture card to output to that format...uprezzing the DV footage to 8-bit uncompressed (better color space, beter codec for graphics and stils) and output. 10-bit is overkill for DV.
    My workflow depends on the footage I am given and the format I need to master to. My HD workflow differs greatly from my DV workflow, which differs from my SD Uncompressed workflow. To go into detail of each would mean writing an article, and I am too busy editing to do that.
    Shane

  • What is the best way to create shared variable for multiple PXI(Real-Time) to GUI PC?

    What is the best way to create shared variable for multiple Real time (PXI) to GUI PC? I have 16 Nos of PXI system in network and 1 nos of GUI PC. I want to send command to all the PXI system with using single variable from GUI PC(Like Start Data acquisition, Stop data Acquisition) and I also want data from each PXI system to GUI PC display purpose. Can anybody suggest me best performance system configuration. Where to create variable?(Host PC or at  individual PXI system).

    Dear Ravens,
    I want to control real-time application from host(Command from GUI PC to PXI).Host PC should have access to all 16 sets PXI's variable. During communication failure with PXI, Host will stop data display for particular station.
    Ravens Fan wrote:
    Either.  For the best performance, you need to determine what that means.  Is it more important for each PXI machine to have access to the shared variable, or for the host PC to have access to all 16 sets of variables?  If you have slowdown or issue with the network communication, what kinds of problems would it cause for each machine?
    You want to located the shared variable library on whatever machine is more critical.  That is probably each PXI machine, but only you know your application.
    Ravens Fan wrote:
    Either.  For the best performance, you need to determine what that means.  Is it more important for each PXI machine to have access to the shared variable, or for the host PC to have access to all 16 sets of variables?  If you have slowdown or issue with the network communication, what kinds of problems would it cause for each machine?
    You want to located the shared variable library on whatever machine is more critical.  That is probably each PXI machine, but only you know your application.

  • 6U digitizer in 3U pxi chassis

    Hi,
    Is there somekind of adapter where I can use a 6U digitizer card in a 3U PXI chassis ? Or do I have to buy a 6U chassis. I currently have a 8 slot 3U chassis and hate to waste it. 
    Thanks
    Dan

    We have an adapter to fit 3U modules in a 6U chassis, but we don't have an adapter to go the other way. If it's useful for you in the future, though, we offer a combination chassis (the PXI-1056) that has both 3U and 6U slots.

  • Is there support for the AC-1000 target real-time system?

    Hi,
    Is NI supporting the AC-1000 target real-time system? We've used MatrixX, SysBld, Autocode, and Realsim to compile, link, download, and run various control models on the target real-time system for interfacing with hardware. The AC-1000 has 2-3 processors running a pSOS Operating System, multiple I/O boards, and a MIL-STD-1553 bus. It's connected to an NT workstation via a LAN and a serial cable.
    So, any information regarding support and maintenance would be very helpful. Thank you for your time!
    Take care,
    Chris Holmes
    Senior Modelling and Simulation Engineer
    United Defense, L.P.

    Although NI acquired MATRIXx, we did not acquire the RealSim hardware (AC-1000, AC-104, and PCI-Pro). Wind River retains the ownership of the hardware but is not supporting the product line. Wind River has made available the attached parts list for the RealSim hardware so that customers can self-service existing systems.
    NI doesn't plan to develop or support RealSim - and is directing customers who wish to continue to use this software/hardware to 3rd parties. The following NI Alliance members can provide RealSim support.
    iControl: www.icontrol-inc.com
    ADI: www.adi.com
    OPAL-RT: www.opal-rt.com
    NI plans to make it easy for customers to target NI hardware, including real-time PXI, with MATRIXx in the future. For information on P
    XI, please refer to the PXI section of the ni.com site at ni.com/pxi.
    Ash Razdan
    National Instruments
    [email protected]
    Attachments:
    AC-104_Parts_List.xls ‏36 KB
    AC-1000_Parts_List.xls ‏37 KB
    PCI-Pro_Parts_list.xls ‏37 KB

  • "Waiting for real-time target (RT PXI target) to respond" error when the program waits interrupts

    Hi there,
    I have developed an application to detect interrupts generated by a electronic card and act in consequence. The program has been developed in labview but it calls a dll; that was created with labwindows. The dll is programmed to open the visa communication, enable events and install the interrupt handler and when an interrupt is detected, it reads the value of the different registers of the card and returns it to labview to visualize them. 
    The problem is that when the program waits for an interrupt, a prompt appears with the message "Waiting for real-time target (RT PXI target) to respond" and the only option I have is to click on the button to disconnect from the pxi or just wait. If I wait and I generate an interrupt, the prompt disappears and the application visualize the data like it was expected. 
    To wait for the interrupt the following code has been programmed in the function:
                    while (flag == 0)
                                    Sleep (1000);
    When an interrupt occurs, the value of flag changes to 1 and the function continue without any problem. I am not really sure, but probably here is the problem and probably this is not the best way to wait for an interrupt because the sleep function suspends the thread for the configured time, but at least the computing load in the PXI is between 0% and 1%. I was wondering if somebody knows how to wait for an interrupt without "lost" the communication with the PXI and if there is a better way to do it. 
    Any answer will be welcome and thanks for them,
    Jaime
    Solved!
    Go to Solution.

    Hello Naity,
    First of all, in which thread runs the waiting process? Is it scheduled in another thread than the function setting the flag?
    It scheduled in the same thread that I use to configure the communications and configure the card. Anyway, here is the pseudo code of the function interrupt that I programmed under labwindows,.
    char* interrupt(void)
    1. Open visa communications
    2.Install handler interrupt --> status = viInstallHandler (instr, VI_EVENT_PXI_INTR, IntrHandler, VI_NULL);   // the function IntrHandler will be called when an interrupt occurs
    3. Enable event PXI interrupt
    4. Wait
    while (flag == 0)
                  Sleep (1000);
    5. Visualize the data coming from the interrupt (registers and values measured with the card)
    6. Uninstall handler interrupt
    7. Close visa session
    The interrupt handler function IntrHandler is called immediately when an interrupt occurs and the pseudo code is like this
    ViStatus _VI_FUNCH IntrHandler(ViSession instr, ViEventType etype, ViEvent event, ViAddr userhandle)
    1. Disable some functions of the card to avoid damages. 
    2. Read registers and put them in a buffer
    3. Change the value of flag ---> flag = 1;
    In labview, I call the function interrupt with a call library function node (see the capture attached) and the program reads and saves the data from returned from the function.
    Secondly, I am not sure this method is the most elegant. You could for example register an event with the function and, insteand of setting a flag to 1, trigger the event and schedule it in another thread (if the function is thread safe). This could reduce your CPU Load even more and seem a bit cleaner to me.
    I've never used events before in labwindows but I will try to do it in this way. But anyway, I suppose that I should; somehow, wait the event to occurs in labview while the waiting for the event is programmed inside the dll...and probably the same prompt that i am trying to avoid is going to appear again, because I am not returning the "control" to labview (I mean, labview executes the dll and waits for the event to occur. Then the execution of the labview program is stopped in the call library function node executing the dll)
    Third point, which environment of development are you using?
    I am working with LV 2010 sp1 and Labwindows cv 10.0.1 and with the real time module.
    I did also another test, I divided the program in different functions, one to initialize the communication, another to wait until a interrupt has been detected and the other to obtain the data from the interrupt and close communications. With labview I call first with the call library function node the function to initialize, later I call inside a while loop the wait function like this
    int waitAseconds (double seconds, short stop_waiting)
    if(flag==1 || stop_waiting == 1)
    flag = 1; //to detect the stop_waiting button
    printf("flagAA =1 stop waiting = %d time = %d\n", stop_waiting, clock());
    return flag;
    else
    SleepUS(seconds*1000000);
    //a++;
    printf("flag a= %d stop waiting = %d time = %d\n", flag, stop_waiting, clock());
    return flag;
     and when the program detects an interrupt, the function returns to labview the flag and stops the loop. Finally, it reads the values and close communications. 
    In this way, the prompt appears but after running the application for 10 or 20 minutes and also i checked that there is a time gap between the executions in the loop.
    Thanks for your reply and your help,
    Jaime
    Attachments:
    capture.png ‏40 KB

  • Using PXI 6541 in real time applications

    Hi,
    I am using PXI 6541 for data acquisition from an electronic card. Electronic card generates an interrupt signal and PXI acquire data  when it gets interrupt signal. The interrupt signal is generated 1 KHz. But using my windows XP, I cannot acquire data on this high rate. The highest rate that I can acquire data is 50 Hz. If I want to acquire data with 1 K Hz, from electronic card using PXI 6541 and using Windows XP,  What Should I do.

    Are you trying to use the 'interrupt signal' as a sample clock for your acquisition?  If so, you should be able to route the signal to the PFI input and configure it as the sample clock.  
    As mentioned in your other thread (http://forums.ni.com/t5/Digital-I-O/Using-PXI-6541-in-real-time-applications/m-p/2561885), I would also recommend looking through some of the examples to get a starting point for your application.  
    James K.
    National Instruments
    Applications Engineer

  • Using PXI 6541 in real time applicatio​ns

    Hi,
    I want to use PXI 6541 in real time mood, can it be used in real time applications.

    I am using PXI 6541 for data acquisition from an electronic card. Electronic card generates an interrupt signal and PXI acquire data. The interrupt signal is generated 1 KHz. But using my windows XP, I cant acquire data on this rate. The highest rate that I can acquire data is 50 Hz. If I want to acquire data with 1 K Hz, from electronic card using PXI 6541 and using Windows XP,  What Should I do.

  • Are there any examples for using a CAN card via XNET on a real time system?

    I am programming a real time application and I have a PXI 8512 card.  My first order of business is to get 5-byte messages from transducers that are broadcasting at 10 Hz on known message IDs.  There are no CAN/XNET samples in my "realtime" CVI sample folder.  I have found some in the nixnet folder but they are Windows based so I have to hack a lot of stuff out of them.
    Thank you.
    Michael Chadwell
    Department of Engine and Vehicle R&D
    Southwest Research Institute

    In other words, I just need to do something very similar to this with no user interface:
    NOTE: See attachment
    Michael Chadwell
    Department of Engine and Vehicle R&D
    Southwest Research Institute
    Attachments:
    CAN Bus Monitor.jpg ‏83 KB

  • 6608 clock card in PXI Chassis

    I have the 6608 High presision clock card in slot 2 in the PXI (1000b)
    Chassis, I also have an Analogue and a Digital Card in the Chassis.
    How do I get the Clock card to provide a very stable clock for the other
    cards, and how do I prove that these cards are getting this clock
    correctly?
    Any advice welcomed
    Cheers

    There are several ways to use the 6608 clock to drive other cards. One is to use Route Signal.vi to route the output from a counter on the 6608 to a RTSI pin. Then use Route Signal.vi again connect the RTSI pin to the AI Convert signal on an E Series card. You can also route the RTSI pin to the 6533 Ack or Req pin as needed using RTSI Control.vi. Be careful to only drive a RTSI line with one card at a time, although several can receive it at once.
    A second way to tie several cards to the 6608 clock is to use Route Signal to send the 6608 board clock to the RTSI clock and then use Route Signal for the E Series card to send the RTSI Clock to the E Series board clock.

  • Hi am trying to save Data into a write to measurement file vi using a NI PXI 1042Q with a real time mode but it is not working but when i run it with uploading it into the PXI it save in to the file

    Hi am trying to save Data into a write to measurement file vi using a NI PXI 1042Q and DAQ NI PXI-6229 with a real time mode but it is not working but when i run it without uploading it into the PXI it save in to the file please find attached my vi
    Attachments:
    PWMs.vi ‏130 KB

     other problem is that the channel DAQmx only works at real time mode not on stand alone vi using Labview 8.2 and Real time 8.2

  • HELP! I need to be able to remove power from a PXI chassis and replace a card without rebooting the whole system

    I do not have particulars on the controller, but I am sure it's an NI chassis
    and NI regular controller that has a serial cable leading back to the PC.
    I am making this PXI rack into a debug rack for instrument cards,
    so I need to be able to remove power from just the PXI chassis
    and then replace the card with another one
    or the same one and then turn the power back on and restart a
    diagnostic test on the card WITHOUT
    having to reboot the PC.
    Is there a PCIe bridge setup that would allow me to do this?
    Is there software that I need that can accomplish this?

    Yes
    The Chassi is a NI PXI 1045
    and the controller is a NI-PXI-8331
    Let me re-enumerate my requirements:
    Background:
    I have a number of NI cards as well as other manufactured cards in the system.
    One of these cards in the NI system is considered to be a UUT.
    That is, I am using the NI card cage system and other cards in the system to test a CARD
    during a manufacturing test of said UUT CARD.
    The UUT uses a PLX 9030 for it's PCI interfacing.
    This UUT is not designed for hot swap, and I do not bieleve it is plug and play.
    Requirement:
    1. I need to be able to shut off the chassis and remove the UUT when the test finishes, replace the tested UUT
    with a unknown UUT, re-apply power and then test the new UUT WITHOUT having to reboot the PC.
    I have tried several things, such as disabling the PCIe busses in the windows control panel, and then removing power
    replacing the UUT with the next one, re-applying chassis power and then re-enabling the bus and SOMETIMES it works.
    I need a very robust way to do this.
    I also bought a CHROMA PXI-52906-E extender card with bus switches on it, so that I can remove power to the UUT
    without shutting off the chassis. The card is supposedley designed so that when power is re-applied to the UUT, the necessary
    signals to boot the PXI PCI interface is conducted, but I think something else has to be written to the card's PCI registers.
    I am by no means an expert in PCI/PXI, 
    but I seem to have exhausted all of my reserach online in how to meet my requirements.
    Perhaps there is a way for the NI8331 controller to capture PCI configuration data to the card's on system boot,
    and then "replay it" to my UUT after I re-apply power to the UUT?
    Or perhaps PLX makes such a tool?
    Any ideas?

  • How can I boot my PXI controller into real-time without a floppy disk?

    My PXI controller is in a lab which has intense magnetic fields that could corrupt the floppy disk used to boot the PXI controller into the LabVIEW Real-Time (RT) Operating System. How can I boot the PXI controller into real-time directly from the hard drive?

    If you are using LabVIEW 5.1.2 Real-Time (RT), launch Remote System Explorer and select Disks >> Create Format Hard Drive Disk. If you have LabVIEW 6 RT, launch the Measurement and Automation Explorer (MAX) and select Tools >> RT PXI Disk Utilities >> Create Format Hard Drive Disk (LabVIEW RT 6 has not be released yet). Once you have created the disk, boot the PXI controller with the Format Hard Drive Disk, and this will format the PXI's hard drive and install the real-time OS boot loader. Now you can reboot the PXI without a floppy disk and configure the PXI using Remote System Explorer or MAX. Be aware that this will remove all information from the hard drive, including other operating systems.

Maybe you are looking for