NOR-RIO Patch Nov 2013 on the PXI controller

Similar Questions

• Usability is NOR-SCOPE Soft Front Panel for the PXI-5154?

  I am plans to use the PXI-5154 with his NO-SCOPE Soft Front Panel in a product to test instrumentation. Our past experience, our users need an on-board scope that is easy to use which does not load the CPU. In most cases the scope will be used to check a transitional type of pulses. So, the amplitudes and rise times are essential to ensure compliance with ISO standards. The ability to capture, store and recall traces of reports is important, as well as the ability to perform simple and reproducible follow-up measures. We don't expect our users to have to program the scope; "give me the waveform.

  Does anyone have any comments on the usability of the NOR-SCOPE Soft Front Panel? How to compare with other soft scopes?

  Hello!

  The scope Soft Front Panel is very user friendly and able to load/save waveforms, Load/Save settings and make the scalar measures.  I've attached a screenshot of what the front soft worn looks as well as a link to a help document on the high speed digitizer HELP.  Information on the scope Soft Front Panel lies in this document and can be found under the tab content in the configuration tree (NI - Scope Soft Front Panel help).

  Help of digitizer OR high speed

  http://digital.NI.com/manuals.nsf/WebSearch/2123F564C6DE7B27862574DE006915DE

   

• Installtion of Labview RT on the PXI controller

  We have a 8106 controller PXI that runs on the Windows operating system. We want to make it work on real-time OS of NOR. What are the steps I need to do to install this. Vascular when I boot in the BIOS of fron LabView RT, it displays "control transfer to the user program. System not configured, restart... ». I am able to connect it to MAX by the host PC and able to install Veristand 2011. But it does not reflect while the boot controller.

  Converting Windows a RT, there are some very important things that you must do to handle the conversion. big is your hard drive.  Your hard drive needs to be formatted with a FAT32 partition - probably formatted Windows NTFS, RT cannot read or use.  Convert your drive will be a manual step for you; If you follow these steps, you can use a disk RT PC Desktop Utility to perform the Exchange against (these instructions with a PXI-8106 module):

  First of all, must be a FAT32 partition on it and the format.

  1. Acquire a drive Flash USB 256 MB or more.  Plug it into your host computer.
  2. Image/Format the USB Flash drive via MAX
     • Under tools of-> creating USB utility MAX desktop PC
  3. Plug the USB key into 8106
  4. Enter the BIOS of 8106 using the "Delete" key
  5. Go to the menu "LabVIEW RT" and "Priming" the value "" Windows / other OS '. "
  6. Press F10 to save and exit, restart the controller.
  7. Enter the BIOS of 8106 using the "DELETE" key (we had to put the controller for Windows / Other and restart the computer to enable USB be detected/used)
  8. In the 'Boot' menu, make sure that "USB HDD" (probably also has your mfg of the inserted USB) option is #1 in the startup list (using keys + /)
  9. In 'Advanced-> Integrated Peripherals' ensure 'Legacy USB Support' is [ENABLED].
  10. Press F10 to save and exit, restart the controller.
  11. The startup controller using the USB flash drive.
  12. In the USB Flash Drive Options, choose the 6 'Options of Format' option (according to the image of the flash player, can say another thing, but option # is the same).
  13. Choose to format the drive, use the Option #2 in the format "Erase all Partitions on the disk and create a new single Partition" - This clears the disk partition information and creates a single FAT32 partition on the drive.
  14. FAT32 format (DO NOT use the use of a 8106 - BIOS does not include the system of dependency files).
  15. Once completed, restart the controller (to do this, you can use Option 9).

  Now, we must get the controller to think that it is a PXI and not a desktop RT PC controller

  1. Enter the BIOS of 8106 using the "Delete" key
  2. Go into the menu "LabVIEW RT" and "Boot" "LabVIEW RT safe mode" value
  3. Press F10 to save and exit, restart the controller.
  4. In MAX, find the device to remote systems.  Right click on the device and choose "format disk".
  5. Once you format the disk, the controller will think it is a PXI controller.
  6. (You may need to remove the MAX controller and press F5 to detect again for updated images)

  Now we are going to put the controller in RT mode so we can use it.

  1. Enter the BIOS of 8106 using the "Delete" key
  2. Go to the menu 'LabVIEW RT' and 'Start Configuration' value 'LabVIEW RT'
  3. Press F10 to save and exit, restart the controller.

  There you go.  Now you are ready to rule the world in a deterministic way.

  -Danny

• Remote control of the instsrument of the PXI controller

  Can you suggest the best method to control PXI instruments with an external controller?  I have two machines.  A standard desktop system and a PXI chassis with controller and installed instruments.  I can the remote desktop for the PXI chassis.  I expecting MAX to recognize instruments in my desktop computer PXI chassis and use VISA address as if it were local.  If possible give examples for a starting point.

  Thank you!

  The Keysight support team helped me to solve this problem.  They showed me MAX remote system control and walked me through the Setup program.  The link they sent me from the site NEITHER.

  http://digital.NI.com/public.nsf/allkb/F3AB0B5D7DBA367C86257982005BBF2C

  Thanks Keysight!

• NOR-RIO 4.0 is not compatible with 64-bit LabVIEW?

  Hello

  I have a 7841R multifunction RIO card.  I currently install the evaluation version of LabVIEW to test.  I've got 64-bit LabVIEW installed successfully and I had installed NOR-RIO 3.6 (which was on the disc that came with the card).  Trying to install other features (I think C to FPGA interface or something), I discovered that I needed NOR-RIO 4.0.  I uninstalled OR RIO 3.6, downloaded OR RIO 4.0 and now I try to install it.  I get the message a few steps in the process:

  Important note about NOR-RIO of LabVIEW support (64-bit Versions)
  A 64-bit version of LabVIEW has been detected on your system.  This version of the driver NOR-RIO support the 64-bit versions of LabVIEW.  However, this version of NOR-RIO is fully compatible with the 32-bit versions of LabVIEW installed on 64-bit operating systems.

  Is there a NEITHER-RIO 4.0 version that supports the 64-bit versions of LabVIEW?  If so, could you point me to it?

  Or do I have to install the 32-bit version of LabVIEW?

  Thanks for the help!

  See you soon,.

  Tom

  Hey Tom,

  Unfortunately, we do not have a RIO driver that is compatible with our 64-bit LabVIEW Development software.  If you need to use the RIO driver, you must install the 32-bit version of LabVIEW and build your applications in the development system.  Sorry for the confusion at the start during the installation process!

• How to install the version of nor-Sync 3.1 in the remote system (processor integrated PXI chassis) to recognize the PXI-6682 device to work with labview RT?

  How to install the version of nor-Sync 3.1 in the remote system (processor integrated PXI chassis) to recognize the PXI-6682 device to work with labview RT?

  Hung Nguyen

  Hung Nguyen,

  The installation of drivers for all targets in real-time remotely is more or less the same. First install the driver (in your case the NO-Sync) on your PC, then install it on your system remotely through MAX. For step-by-step instructions, see install the software on your NI CompactRIO controller.

  See you soon,.

• Read the latest version of the driver NOR-RIO by program

  Hello.

  Is there a way to read what NOR-RIO's version of on my RIO programmatically? I know I can get this information through MAX, but I want to get this information at run time.

  Terje-

  If you do not want to develop a
  application with replication tools, please see using FTP with
  Windows Explorer.  If you copy off of full HD which only goes
  be bigger than your app about 15 MB... This will include all the
  software.  It is also an easy way to make backups of their
  configuration and software.  I think that will be the best way
  This round.  Let me know how well are you and if you have a
  questions.  I'll make sure that it will be evaluated for a future
  Release.

  Kind regards

  John

• Control of low level of the PXI-2596

  How to control a PXI-2506 Mux 26.5 GHz Dual 6 x 1 chassis PXI-1042 a code 'C' with a minimum of drivers? We want to use our own code, not of LabView, just plain 'C '. Also, we prefer to use our own controller (Linix based) shipped without a slot for a PXI card (if possible). Is there like a simple series or ethernet interface to control the boards housed in the PXI-1042 chassis? The switching speed is very low, it is part of a manufacturing test system, we want to use the PXI-1042 with several 6 x 1 Mux inside for instruments RF switching in of the DUT.

  Hi eirlund,

  In response to your questions:

  Is there a simple series or ethernet interface to control the boards housed in the PXI-1042 chassis?

  • Chassis PXI itself contains only the connections for the PXI bus and some timing and triggering and power for the cards. This white paper explains the PXI architecture in many more details: http://www.ni.com/white-paper/52018/en/
  
  
  • In order to be interfaced with the cards that you need to use a controller Embedded PXI or a remote control which allows you to use another computer in place and place an on-board controller. A remote control can be easier to apply to what you're after however there are some limitations regarding the use under Linux. More information on what the remote controllers can be found here: http://sine.ni.com/nips/cds/view/p/lang/en/nid/10359

  We want to use our own code, not of LabView, just plain 'C '.

  • You should always use the relevant drivers for the hardware you are using, in this case NOR-Switch and NI PXI Platform Services if you are using a remote control.
  
  
  • These drivers work with LabWindows/CVI which adds additional tools to facilitate the programming intended for the material OR in C, this means that it should be possible to use these drivers of C, but there is less evidence for this

  Also, we prefer to use our own controller shipped (Linux-based) without a slot for a PXI card (if possible)

  • If this is possible will depend in part on the question of whether the version of Linux you are using is supported. You can look into this further here: http://www.ni.com/product-documentation/52786/en/
  
  
  • In addition, you will need a PCI slot or a slot ExpressCard to connect to a remote installation program with

  I hope that this information gives you somewhere to start to consider whether what you want to do is doable?

  Best regards

  Joe

• Why is relativeInitalX value not taking into account the triggering delay? using scope OR with the PXI-5124

  Hi all

  play with a digitizer PXI-5124 in a case of PXI1042Q with a PXI8110 controller that runs labview 2012 (latest updates) with the latest version of the driver NIScope.

  I put in place an acquisition of off-delay (by assigning the triggering delay, for example 20us) which works very well (I can tell by the signal I get delay control works correctly), but the data returned in the info wfm cluster (using the 2D version of niScope I16 Fetch) does not have this delay.

  Description of the relativeInitialX within this cluster indicator indicates "is the time in seconds between the trigger and the first sample in the acquired waveform" but its never to return something around 1E-9 independent of trigger delay. Surely the relative initial x should reflect the triggering delay?

  I'm doing something wrong?

  Thanks for your help!

  So, I made a screenshot of the image in the section "Trigger Delay" link I sent you.

  

  Meaning of the symbol:

  T0 = original moment of relaxation

  T1 = time to trigger used in the acquired record (t1 = t0 + TriggerDelay)

  T2 = time of first sample in the record of the acquis.

  RX = relativeInitialX = t1 - t2

  Response to previous reviews

  «I understand what you're saying - so basically, if I want to know the delay of my trigger for the first sample in the record, I just add my delay time value to the relativeInitialX.»

  • Close, the delay of the original trigger (t0), for the first sample in the record (t2), would actually be TriggerDelay-relativeInitialX

  «.. . Nowhere does graphically describe where is the relative value of initialX real. »

  • Right, relativeInitialX is not a timestamp, so it is not a place on the timeline, it is the difference between two timestamps (t1 and t2 above), where the relativeInitialX name.

   

  "The trigger"record"is the straight line in the Middle, so expect relative to - 1/2 initialX record length?

  • Almost correct, because the reference trigger is relativeInitialX to the position of 50%, will be the time in seconds for 1/2 the record length. (i.e. If the registration has been long relativeInitialX, 2s = 1 s).  RelativeInitialX will always be the delta time between the trigger (t1) and the first sample returned in the record (t2).
  
  
  • For example using the picture above: If t0 is 10 sec, Trigger Delay = 3 sec, SampleRate = 1 kHz, = 1000 record size.  This means that t1 = 13 s.  Our record is long of 1s (1000 points to 1 DC between each = 1 s), if t2 = 12.5 sec.  If away from all these moments are absolute time, as the timestamps.  So relativeInitialX = t1 - t2 is 13-12, 5 = 0.5 sec.
  
  
  • As a side note, the reference position should not be 50%, you can configure to between 0-100%.

  Time not yet discussed record attributes

  I don't want to make you more confused, but there is another useful attribute in the waveform info that we've not yet discussed and its AbsoluteInitialX.  Starting from the NOR-SCOPE help file:"absoluteInitialX is the timestamp of the first sample of recoveries in seconds..." "So, using the above image, absoluteInitialX = t2.

  I hope this helps.  If a part is still not clear, let me know.

  -Nathan

• Support of NOR-DNET for LabVIEW 2013

  We currently use OR DNET 1.6.6 with LabVIEW 2011. I installed LabVIEW 2013 now also on my computer and tried to synchronize all of the drivers with my installation of LabVIEW 2011.

  Well, it seems that NEITHER-DNET does not support LabVIEW 2013, at least officially. compatibility of Version of LabVIEW and NOR-DNET indicates that NEITHER-DNET 1.6.6 supports 2011 NOR-DNET 1.6.7 2012 LabVIEW and LabVIEW.

  The list NOR system driver November 2013 set OR DNET 1.6.7 defined pilot. When I try to install it, there is no support for LabVIEW 2013.

  My question is, if there is a plan to include support OR DNET for LabVIEW 2013 or later in the game to pilot?

  I copied the directories vi.lib\DeviceNet and vi.lib\nidnet of LabVIEW 2011-2013 and I can load my programs without any problems. I always did not build an executable and does not run on the test set-up, but projects can be loaded in LabVIEW 2013 without any screws of brocken. should I expect any problems running LabVIEW 2013 with the NOR-DNET to 1.6.6 and 1.6.7 driver?

  Nick

  There should not be problems but it is a former pilot, we will not be updated for the future version of labview.

• Pulse modulated CW with the PXI-5650 and PXI-6653

  Hello

  I'm trying to generate a signal CW of pulse modulated with the PXI-5650 as source RF and the PXI-6653 as the modulation signal. Basically, I'm trying to generate a simple radar waveform. It seems that it would be possible to use the synchronization Module (6653) to transform the RF output on / off on the signal generator (5650), but I do not know how to route the signals from one to another using LabView.

  Has anyone tried this or something like this before? Can anyone please offer some advice?

  Thank you!

  -John

  Hi John,.

  Reading your post, it seems you want to use your calendar and map of synchronization to the RF output power, in other words, on Off Keying. OOK modulation is a feature built into the 5650. For more information, you can navigate through the NI RF Signal generators Help for devices-RF signal generators > NOR -> NOR 5650/5651/5652 overview-> Modes of Modulation and simply click on the Modulation Modes.

  An example of this is found in the example Finder OR by navigating to the help-> find the examples in LabVIEW and then navigate in the Finder to example NOR material input and output-> Modular Instruments-> NI - RFSG-> signals-> RFSG 565 x Digital Modulation.vi.

  Kind regards

  Jason L.

• The PXI-8512 does support the series 2 filter or a similar mechanism to filter the messages?

  Hello

  I need to buy a couple of cards CAN interfaces for my test application and I wonder what you choose

  I already used a PXI-8461 to obtain data of the customer model under test, and due to the fact that sometimes the client bus can be very busy, but most of the messages is not interesting for my system that I use currently series 2 comparator/mask/filter to filter only the interesting messages.

  Without this filter, the PXI-8461 often returns an error due to overloading of the bus. With the filter, everything works perfectly

  Now I need to implement several testbeds with this same feature, and I plan to move to the new PXI-8512 for new.

  My question is: is the most recent PXI-8512 a device series 2 institutions? Support the filter 2 series or any other mechanism to avoid problems on the busy bus?

  Thank you for your support.

  Kind regards

  Davide

  Hi Davide.

  the PXI-8512 isn't a series 2 device. The PXI-8512 is a device of the X-NET family. X-NET is the technology whose use OR in support of CAN, LIN and FlexRay with a driver API. Series 2 devices use the former NI-CAN driver that only supports the CAN. All of the new devices are devices X-NET.

  Take a look to the following document:

  NI-CAN for NOR-XNET application migration
  http://www.NI.com/white-paper/9717/en

  On this page you will find the following statement for the function that you are already using:

  Transceiver filters were traditionally indicated for applications where only a few CAN IDs have been considered on a bus high load. In some cases, material NI-CAN support the bandwidth of the full bus, which leads to a buffer overflow. The hardware architecture OR XNET uses the engine NOR-XNET DMA-driven to eliminate the occurrence of buffer overflows. CAN of NOR-XNET interfaces are able to handle high load bus and transmitting at the maximum rate without coupling to buffer overrun. If your applications use the hardware filters extensively, NOR recommend setting up CAN opposes, or by reading the bus while using Network Interface objects. The best option for these applications is to modify your code to use the API OR-XNET native.

  Best regards, Stephan

• Would it not correct to say that the PCI-6110 can be set to 'redeclenchables' but the PXI-6115 module cannot use this property?

  Would it not correct to say that the PCI-6110 can be set to 'redeclenchables' but the PXI-6115 module cannot use this property?  If Yes, where is it documented the series cards can do trigger?  For example, is it possible to configure the trigger on the PXI-6124?

  Hi Joel_Neptune,

  The PCI-6110 and other materials as the PXI-6115 S series and SMU-6124 do not natively support NOR-DAQmx analog input alarm. However, you can use one of the generalist counters/timers of the Council to generate a reenclenchees pulse train, then use this as the sample clock pulse train. This transportation example shows how:

  LabVIEW\examples\DAQmx\Synchronization\Multi-Function.llb\Multi-Function-Ctr Retrigg Pulse Train generation for the Clock.vi sample

  In addition, the new material of the simultaneous sampling X series are supported trigger analog input without using a separate task of counters/timers.

  Brad

• Programming on Board on the PXI-6132

  Hello

  This is my first post, so please be abstain.

  Asked me to develop a Labview Vi for the acquisition of data. I must acquire and a number of disintegrations exponential (as happens during the discharge of a capacitor through a resistor) averaged for calculating the decay constant. My boss has already bought a chassis PXI-1073 with a PXI-6132 to acquire the data. My question is this: since the sampling rate must use is very high, I want to minimize the amount of data transferred from the PXi system to the computer, with my system (windows 7, LV 2011, nor-DAQmx?), so it is possible to "say" the PXI-6132 to isolate the data belonging to the decomposition of exponantial on average several decays, then send the data to the host?

  Thanks in advance for your help

  Channel counter in the example I did you, is the meter, you use to generate the clock signal. Therefore a finished with 30 pulse pulse train if you want to acquire 30 samples.

  This channel can be configured as redeclenchables and control 'Source', you must select the PFI where the trigger signal is wired. It depends on how you did.

  The clock signal is routed internally, which means that you don't need all cabeling, simply select the right source for your route of entry of the AI (for example. Ctr0InternalOutput if you selected against 0).

  So external signals will only be ounces you want to measure with Amnesty International and the trigger for the clockgeneration (counter) signal.

  In MAX, you can do a right click on the device and see the layout of the pins on your device.

• How can I display an analog input for the PXI-5105 on LabVIEW?

  Hi all

  I am very very new to LabVIEW and I started to tinker with it. I use the version of LabVIEW 2010 SP1 on Windows 7 OS. I also have the chassis NI SMU-1073 with SMU-6361 and PXI-5105 modules and the chassis is connected to my PC via PCI. I became familiar with the devices and trying to see some analog signals to one of the channels on the PXI-5105 module in a graph in LabVIEW.

  I would appreciate your help.

  Hello Henokview!

  I would like to read through these tutorials to understand the steps of programming of the NOR-SCOPE, NOR-DAQmx. After reading these links below, you will be able to understand how to connect the output of a readfunction to a chart or table.

  DAQmx

  http://www.NI.com/white-paper/5434/en

  OR-SCOPE

  http://www.NI.com/white-paper/3382/en

  Best regards

  Jonas