NI PXI-7813R frequency

Hi,
Can i use PXI-7813R module to genarate and measure ferquency arround 15MHz. What is the maximum frequency i can generate and measure using NI PXI-7813R module.
Thanks in Advance.
Krishna

I'm gonna (sorta) disagree... I don't think you should call it quits yet. That said, your current programming approach won't get you there. For higher performance, you're going to have to use Single Cycle Timed loops. You won't be able to use the Wait for Rising Edge node anymore, but a simple Feedback Node + Greater Than will accomplish the same thing. You'll also have to ditch the waits and Tick Counts. You can implement your own counters via shift registers and an increment function. for the waits, you'll just have to "do nothing" for X cycles. A State Machine architecture should let you do that pretty easily.
It'll take time to implement for sure, but I'd argue that it's feasible to get 15MHz performance out of this target from the programming side. The only thing that I'm worried about for your app is the DIO isn't made to go that fast. I believe most of our R-Series boards have the DIO rated to a max of 10MHz due to HW limitations. For anything faster, you'd need a FlexRIO + HSDIO FAM. Otherwise you're risking signal integrity. If you really need to switch at 15MHz, you need a board with IO rates designed for that. If you just need the logic to perform faster (ie. not switching every 15MHz, just being able to respond that fast) then I think you'll be fine.
EDIT: Forgot about this doc: http://digital.ni.com/public.nsf/allkb/59798CF4FF6F7F12862574B4005BE70C
Check out the sample waveforms, and see if a specific rate is good enough for your app.
Cheers!
TJ G

Similar Messages

  • PXI 7813R Register Level Programmer Manual available

    Is the Register Level Programmer Manual available for the PXI 7813R module?  Does a code example exist using Microsoft Visual C++ 6.0?
    Thanks!!!

    The RLP manual for the 7813R is identical to that of the 7831R, which you can get on the MHDDK page (go to the download link).  The only difference is that you will need to use a different PCI device ID to identify the device, the PXI-7813R device ID is 0x7193.  There are MSVC++ examples at the download link as well.
    -Alan A.

  • PXI-4461 frequency sweep.

    Hi,
    I'm writing a sweep function for PXI-4461 to measure frequency response. I fixed the number of samples of sine wave as 100 and the sampling frequency is varied by ten times the output frequency. The Input and Output channels clock rates are changed on the fly according to the output frequency. However, I found that the PXI-4461 is needed to stop the task before changing the clock rate, am I right? Therefore, the output signal from 4461 become on and off repeatedly due to the task start/stop. I want the signal generated continuously, any suggestions?
    Bill

    If you are using LabVIEW, you could try the swept sine in the Sound and Vibration Toolkit. It uses a constant sample rate and update rate and changes the generated frequency on the fly. There are no glitches in the output.
    Doug
    NI Sound and Vibration

  • How to use 9871 RS485 card in scan mode in PXI-7813R (Reconfigurable IO)

    I would like to use 9871 in scan mode in RT code rather than writing FPGA code.
    Plese find the attached snapshot of RT project.
    Attachments:
    9871_InFPGA mode.png ‏13 KB

    Hello craige,
    There isn't any reason the module won't show up properly in MAX. This is probably just a software configuration error. Do you have Scan Engine support installed on the system? Did you specifically install the NI 987x serial support on the RIO? This can be done from the add/remove software window.
    Cheers!
    TJ G

  • How to communicate with a 9401 module using 9151 expansion and 7813r PXI card

    Hi,
    I have just started working with my 7813 R-series card.  I was able to create a simple VI in which I could send and receive digital signals.  Now I would like to do something similar using my 9151 expansion chassis and 9401 C-series module.  If possible I would like to do all of this using windows (no RT for now).  Right now I am right-clicking on "my computer" in the project tree and adding new devices to find the 7813.  From there I have a rough idea of how to build a simple VI using the NI example.  However, I do not know where to look for the expansion chassis or the C-series module.  If any one could give me some advice or point to an example, that would be great.  I have seen the examples in Example Finder for the 9401, but they seem to be using a compactDAQ system as opposed to the PXI setup. 
    Thanks for the help!
    Solved!
    Go to Solution.

    Hello ACE_Lab,
    The steps you should take in order to configure your setup in the LabVIEW project window is as follows:
    Step 1...
    Step 2...This step should auto-populate with the existing PXI-7813R if it is connected. If you want to setup the target without the card connected, the you can just add a new target as follows.
    Step 3...This is the point at which you will be adding the NI-9151 expansion chassis:
    Step 4...
    Step 5...
    Step 6...If you have the module connected to the chassis, you should be able to see the module in the list:
    Step 7...If the module is not connected, you can just select "New Target or Device" from the menu in step 6 and add a new target as follows:
    An example from the Example Finder called "Digital Line Input.vi" should be a good place to start. Below is a screenshot of roughly where you need to start:
    Regards.
    Jeff L.
    Applications Engineer | National Instruments

  • Problems synchronizing FPGA to PXI clock

    I have recently received several of the new larger FPGAs, the PXI-7813R and the PXI-7833R. It appears that we are unable to reliably synchronize them to the 10 MHz PXI back-plane clock. We have only seen this problem with the newer FPGA boards and did not observe it with either the PXI-7811R and PXI-7813R in the same PXI-chassis. Has anybody else had this problem with the new boards? Synchronization is critical because we are feeding the FPGAs signals from a 40 MS/s ADC and if the ADC clock and FPGA clocks are not the same frequency we see glitches/missed ADC samples. Typically we use the 10 MHz output from the back of the signal generator (that provides the 40 MHz ADC trigger signal) to provide a 10 MHz input with the PXI chassis.

    First I should say that the problem is now resolved. It was fixed after we cycled the power on the PXI system after attempting to download the "synchronize" option several times. The first time we cycled the power it did not fix the problem despite leaving the power off for >20 seconds, so the solution hardly seems reliable.
    As for the evidence for lack of synchronization, initially we suspected a lack of synchronization as we observed "glitches" on the output of a digital phase-locked loop. The second clue was that the DPLL was actually locking to a slightly different frequency than it should have by about 5 ppm. All other FPGAs in the same PXI chassis were locking to the correct frequency.
    We then wrote custom vi's that would cause one FPGA to generate a 40 MHz boolean on-off output on the digital front panel output. This was then looped to the FPGA under test (using the approporiate SCSI cable), which would read out the boolean at 40 MHz and register a missed count every time the boolean value did not change (exclusive-or between the current digital input and the previous input). Any given pair of FPGAs would give us zero unsynched counts, except when the suspect, unsynchronized one was used. The unsynched FPGA missed several thousand counts in a matter of seconds.
    Notably, we had this problem with 2 different FPGAs in 2 different PXI chassis. In one case it was the 7833 that was the problem and the 7813 worked fine. In the other system a (different) 7813 was the problem and the 7833 synched fine. We have two more FPGAs waiting to be installed and I will post back here if I see any more issues. We also have three 7811s and three 7831 none of which had synch problems.
    Once the synchronization problem was fixed it has not reappeared again which is good news for us.
    Thanks,
    Daniel

  • PXI not showing up properly in MAX

    Hey everyone,
    I'm new to setting up remote systems in MAX and I'm having some difficulty.  I'm using all LabVIEW 2011 versions of software with FPGA and RT modules.  I'll start by listing the hardware I am using:
    PXI-1042 Chassis
    PXI-8110 Embeeded Controller
    PXI-8231 Ethernet
    PXI-6704 Analog Output
    PXI-6602 Timing I/O
    PXI-7813R Reconfigurable I/O
    Of this list I am using the 8231 to connect to the chassis and I am primarily interested in using and getting working the RIO more so than the other cards right now.  Here is what I have done so far and what has happened.
    When I first plugged it in nothing showed up in MAX and so I did some searching and found that if I change the BIOS options and set them to LabVIEW RT and set the 'Reset IP Address' to 'Yes' that I could see the NI-PXI8110 in the remote systems directory.  Under this is says that it is connected but there is no software installed.  If you click on the software directory, a list of software appears so I'm not sure why it says nothing is installed but there is software listed.
    Now even though there are all these cards in the PXI, nothing shows up under Devices and Interfaces.  I tried to 'Create New...' by right clicking on it and then clicking on PXI Chassis, but I get an error that the the host only supports PXI Platform Services 2.0.0 or greather and that the target has earlier version.  So I made sure that I had the latest PXI Platform Services (3.0.3) and I then I tried to follow the instructions by updating the VISA software it should update the PXI Platform Services on the target.  Now it won't let me do this without updating a bunch of other software on the target such as LabVIEW RT - current it has 10 and it needs 11.  This wouldn't be a big deal but then another error comes up where I need a newer version of Hypervisor (target currently has 1.1).  I downloaded Hypervior 2.0 and tried to install on my host and then subsequently add to target.  I am running Windows 7 64-bit and there seams to be a support issue because it doesn't show up and the installer says it can't install certain parts due to incompatibility issues.  Then I thought I'd try to install it directly to the embedded controller on the target by hooking up a monitor/keyboard/mouse.  Even though the keyboard works in the BIOS, when at the Windows login screen I have no USB keyboard or mouse support therefore, I cannot login.
    So there are a bunch of problems it seems that are plaguing me getting this system set up and running.  I'm not sure where else to look and hopeully someone more knowledgable can give me some guidance.  Thanks in advance for the help.

    Hypervisor systems are a relatively new thing for NI as well, it allows you to run Windows and RT on the same system concurrently (one core goes to Windows, other cores assigned to RT).  One interesting tidbit is that Windows and RT use different disk partitions, and the other tidbit is that when you're in "Hypervisor Mode" versus "RT Mode" you will have some collisions with software on the target.  
    It's unclear as to what you're trying to do with the system, are you trying to run Windows on the PXI controller and program/use the FPGA from the Windows environment, or are you wanting to use the PXI controller as an RT system and use the FPGA on the RT system in a "headless system" environment?
    If you're going to use the system in RT mode, by setting the BIOS option to "LabVIEW RT" in the boot options, you must install LabVIEW RT.  In the previous Hypervisor mode, Hypervisor RT + all the components were probably installed, but in this LabVIEW RT mode you need "Normal LabVIEW RT" + all the components.  The system telling you there's no software installed is because none of the drivers are being loaded because you elected to boot "Normal RT" and the "Hypervisor RT" OS is on the system (instead of the "Normal RT OS").  
    There is an easy and safe thing to do here.  Instead of booting "LabVIEW RT", boot "LabVIEW RT Safe Mode" and then go to MAX and right-click the device in MAX and say "Format Disk".  This will safely format the RT partition, bringing it to a clean slate, and you can then install software and LabVIEW Real-Time to the controller.  Then you can put it back into "LabVIEW RT" mode and use the controller like a regular RT controller.  When your colleagues want to use it as hypervisor, they can put it back into "Windows/Other" mode and then reinstall Hypervisor onto the controller.  
    -Danny

  • Programmatically selecting one NI-9505 module from a PXI R-series expansion slots

    How can I
    change the SoftMotion example entitled “position control closed loop- NI
    9505.lvproj”  in order to use it as a
    configurable sub-vi to drive serveral motors?
    in a PXI-RT
    box I’m using a PXI-7813R card, its ports are connected to several R-series expansion
    chassis’s  each of them driving three
    9505 Modules, i.e. 12 motors in total
    The problem
    is I didn’t find a way to programmatically define which 9505 Module the sub-vi
    should use, i.e which motor to drive.  Is there a way to archive this?
    thank you.
    A. Villa
    Airbus Deutschland
    Bremen, Germany

    Hello Mr. Villa,
    as the current and position control portion of your code needs to get implemented on the FPGA. That means, that the code needs to be mapped to the gates of the FPGA, which doesn't allow dynamical assignment of resources at runtime. So in your case you will have to implement the code for one axis and create multiple instances of it with modified I/O nodes for each axis. In contrast to the design rules of standard LabVIEW vis, you should work with a quite flat vi hierarchy with LabVIEW FPGA in order to save FPGA space.
    Kind regards,
    Jochen Klier
    National Instruments

  • PCI 7813R 5V Terminal current rating

    What's the maximum current load for the 5V terminal on the connector 0 of the the PCI 7813R board? What's the fuse ampere rating of the board?
    Solved!
    Go to Solution.

    Thanks for finding the fuse specs, AKD2M!
    Jjapuy, the +5V port on Connector 0 (pin 1/35) on the PXI-7813R can output a max of 0.5 Amps. The output is limited to 0.5 amps per connector.
    http://sine.ni.com/ds/app/doc/p/id/ds-98/lang/en
    See the power requirements section.
    Please clarify if I have misinterpreted your question!
    Best,
    Joey S.
    Software Product Manager
    National Instruments

  • What needed for 7813R pwm i2c SPI

    Hello,
    we want to use the PXI-7813R 3M Gate Digital RIO (160 DIO) card to generate PWM signals, test I2C communication and use it for SPI testing/communication.
    Perhaps also some conventional I/O testing...
    They've told us that on the site www.ni.com/ipnet we can find IP to do this.
    My question: do we need additional software tooling to use/program this FPGA? Or is just downloading some libraries via VIPM and "using" some vi's sufficient ?
    thanks.

    You will need to have LabVIEW, LabVIEW FPGA and the Xilinx tools which will be installed with the FPGA module.
    You can find IP where you mentioned for SPI and I2C the generation of PWM you can find in LabVIEW Example Finder under Help in the toolbar. The general I/O testing will need more info to describe where to find info how to do it.
    Best Regards
    Jonas Mäki
    Applications Engineering
    National Instruments

  • How to use a counter to build a Logic Analyzer?

    Hi guys, i have heard that we can use a counter as a Logic Analyzer based on an incoming signal and its clock frequency. Anyone know how this works?
    I am trying to read a set of signals, which I have no knowledge of  except that there would a Clock, reset and a data line; and I want to develop a Logic Analyzer to 'know' these signals.
    Thanks, Anoop
    Solved!
    Go to Solution.

    Lynn,
    I have a PXI-7813R, which along with its FPGA is sufficient I believe for this purpose.
    How many digital signals do you need to examine simultaneously?
    Well, I am not sure, but based on the signals generated by similar devices, I would guess between 4 and 6. I expect there to be a Clk, Rst, Data and some other signals.
    What is the maximum frequency?
    I have no idea or how to even come up with a guess on this one.
    What is the maximum and minimum number of samples per signal that you need to capture?
    Again, not a clue. Would it not depend on the Clk frequency?
    Are any of the signals ever in a high impedance (tri-state) mode?  
    Again, don't know, sorry.
    Is the minimum pulse width for non-clock signals the clock period, half the clock period, or something else?
    Sorry again.
    How would you go about in this situation?

  • FPGA: compilation error: size of concat operation is different than size of the target

    Today I got an error, for which I couldn't find a solution.
    I use the PXI-7813R FPGA, with Xilinx tools 10.1
    At compilation, the error I get is:
    Compilation failed due to a Xilinx error.
    Details:
    ERROR:HDLParsers:804 - "C:/NIFPGA/jobs/TESY1S8_X4PR8hn/NiFpgaAG_000000ce_CaseStructureFrame_0000.vhd" Line 301. Size of concat operation is different than size of the target.
    ERROR:HDLParsers:804 - "C:/NIFPGA/jobs/TESY1S8_X4PR8hn/NiFpgaAG_000000ce_CaseStructureFrame_0000.vhd" Line 372. Size of concat operation is different than size of the target.
    --> 
    Total memory usage is 185944 kilobytes
    Number of errors   :    2 (   0 filtered)
    Number of warnings :    0 (   0 filtered)
    Number of infos    :    0 (   0 filtered)
    Process "Synthesis" failed
    Start Time: 18:25:26
    End Time: 18:28:54
    Total Time: 00:03:27
    What can cause a concat size difference?

    This is by the way the configuration:
    Project: FPGAWrapperMG100125AOD.lvproj
    Target: FPGA Target (RIO0, PXI-7813R)
    Build Specification: fpga_integrator_AOD_random_access
    Top level VI: fpga_integrator_AOD_random_access.vi
    Compiling on LabVIEW FPGA Compile Cloud Service
    Compilation Tool: Xilinx 10.1
    Start Time: 05.07.2011 19:06:12
    Run when loaded to Fpga: FALSE
    Xilinx Options
    Design Strategy: Custom
    Synthesis Optimization Goal: Area
    Synthesis Optimization Effort: Normal
    Map Overall Effort Level: Default Xilinx setting
    Place and Route Overall Effort Level: High
    JobId: FNW72uPWorking Directory: C:\NIFPGA\compilation\FPGAWrapperMG100_FPGATarget_fpgaintegratorAO_9D5B4237
    The Xilinx log is attached.
    Attachments:
    XilinxLog.txt ‏80 KB

  • Fpga unexpected error reported from new vi wizard

    When i use the new vi wizard , select a new fpga project -> R-series on RT pxi -> create new system
    I get a pop up saying unexpected error. I have tried a repair to no avail. I have LV2010 and am looking to use a PXI-7813R
    many thanks in advance
    Please remember to accept any solutions and give kudos, Thanks
    LV 8.6.1, LV2010,LV2011SP1, FPGA, Win7

    Hi joedowdle,
    Sorry to hear that you're having issues creating an FPGA project.
    To prevent this error occurring, it seems that one option that has previously been successful, was to uninstall and reinstall LabVIEW and the additional modules. I do appreciate that this would be rather time consuming, so I would like to try some additional troubleshooting steps with yourself first.
    Have you been able to successfully create a standard LabVIEW project without it crashing? If so, could you please try to manually add your R-series card to it please? 
    On a similar note, are you able to successfully run an R-series example project? You can find one of these through LabVIEW >> Help >> Find Examples. And in the example finder go to Hardware Input and Output >> R Series >> Basic I/O, then select an example.
    There are some additional steps that I'd recommend having a look at, in the R-Series user manual which I think is really useful for both explaining where your hardware should appear in the Measurement and Automation Explorer software (MAX) and how to use an example.
    As you mentioned your versions of LabVIEW, FPGA and Real-Time, what version of NI-RIO do you have installed? If this is incompatible with LabVIEW 2011 and the FPGA module, this could potentially be the root of the crash. For LabVIEW 2011, you will need to have version 4.0 installed.
    Best wishes,
    Tori
    Student

  • I need estimated MTBF for a list of products

    Our system customer has requested estimated MTBF.  I therefore need estimated MTBF for the following PXI products: PXI-6509, PXI-6542, PXI-7813R, PXI-8431/8, PXI-8432/4, PXI-7953R.
    It is understood these are estimates only and will be accompanied by disclaimers.  A full 217 calculation is not expected or desired.  I have obtained estimates from other system component suppliers.  How do I obtain these estimates from NI?
    Solved!
    Go to Solution.

    I did some more research on how our MTBF figures are calculated. Generally, including this card, our MTBFs are calculated based on design, not field fail rates. The method used to determine this particular card's MTBF was Bellcore Issue Level II. 
    Dominik E.
    Applications Engineer
    National Instruments

  • Cannot read data in FPGA

    Hi guys, I have a code that I developed for reading in digital data through digital lines in a PXI-7813R. But unfortnately, in the Host vi, I cannot acquire any data, even though I have fed in an external signal to the digital line in the PXI through a connector.
    I have a data graph to display this signal, but nothing can be seen when I run the problem! Anyone know what the problem is?
    I have attached the project.
    ANy help would be great.
    Thanks, Anoop
    Solved!
    Go to Solution.
    Attachments:
    Digital Input FPGA.lvproj ‏100 KB
    FPGA.vi ‏79 KB
    Host.vi ‏81 KB

    Hi, thanks for the reply.
    I have a couple of questions though. I dont understand what you mean in the first line. I have set the READ in the FPGA VI to be true so that when it is pressed, data can be read from the HOST VI.
    Now, getting on to the issues you highlighted.
    1. I have included a polling delay and the error issue is now sloved. But, when you mean "Also make sure you wire your error in to the while loop stop condition....", I have did this using the polling. Is this OK?
    2. You mention "In your vi, you are writing...." do you mean in the FPGA? If so, I have set the "read?" flag on the case structure, to use it as a switch for teh true conditon. is this not correct?
    I have attached the modified Project along with this. Feel free to edit it if you feel the urge too
    Attachments:
    Digital Input FPGA.lvproj ‏91 KB
    Host.vi ‏99 KB
    FPGA.vi ‏199 KB

Maybe you are looking for