RIO devices

Similar Questions

• Basis of LabVIEW Development with Compact RIO device software

  Hello.  Currently, I have the LabVIEW Base development software package and have been using it with DAQ Compact devices for the acquisition of basic data.  I would now like to start integrating controls in my system, changing to RIO Compact for deterministic real-time features.  My question is that I would be able to build applications for the Compact RIO system using only the basis of LabVIEW Development package without updating immediately?  Maybe some features are not available for me, but could at least get a good start like that?

  A CompactRIO embedded time real operating system (RTOS) called VxWorks you need to target the deployment of LabVIEW code to the device. Classic LabVIEW screws you will have been written so far are built to target general purpose operating systems (GPO) such as windows.

  To create screws that are deployable to STSOp, you will need the real-time Module that is not included in the basis of LabVIEW. As a result, to take advantage of the embedded FPGA, you'll need to install the LabVIEW FPGA Module as well.

  As long as you have the FPGA modules and in real time, it seems to me that you should be able to control these devices with LabVIEW Base. Without these software components you will not be able to create an instance of the device target your LabVIEW project.

• Using global variables in a device custom

  Hello world

  I have problems with the passing of data through my device customized using global variables. I want to allow a user to select a RIO device address when you set up the system definition file. This is recorded in a global variable using the hand Page VI. I would later use this RIO device address in RT driver to deploy a bitfile. I can hard-code, but it is much more convenient to use a global.

  When I try to store the address of the global variable, it updates the value temporarily (I confirmed that the structure of the event recognizes the change of value). When I click the node of the tree to define system linked to the Main Page VI and then click on it again, the hand Page VI runs again. I wrote the code to repopulate the address of device of RIO with the last value stored in the global variable, but it is empty. I've included the VI global variables in my build, so I can't imagine why it can reset this value.

  Any help would be appreciated!

  Thank you

  Mitch

  Have you tried to use the custom device properties to store this value instead of GVs?

  Configuration VI, you can set this property, and if I'm not mistaken, you can read these properties on the RT driver.

• FPGA - try to use the screw of the replication of RIO to replace going to reset the FPGA running

  Running LabVIEW 12.1

  We have an application that uses an FPGA that was compiled in Run to Reset (works on any reset or power on).  Sometimes we need to update the image on the RT and FPGA and I downloaded the NI RIO replication screw.

  The problem I have now is that when I got to download the bitfile on the Flash FPGA on the sbRIO9636, I get the following error:

  Error-61141

  Possible reasons:

  LabVIEW FPGA: The operation could not be performed because the FPGA is busy. Stop all activity on the FPGA before asking this operation. If the target is in the Interface of Scan program mode, put in FPGA Interface programming mode.

  My updater is stand alone EXE.  He isn't able to get a link to the FPGA, because we are not sure what Bitfile currently is on a particular system.  I tried using the open FPGA reference and load a VACUUM on the FPGA bitfile by setting the FPGA to RUN when he sound the FPGA VI of the Open reference - and it works for me to erase the bitfile.  It does not allow me to immediately after run the bitfile VI of replication of RIO download - even if I close and reset the FPGA before trying to download the Bitfile for the RIO Flash.

  I have to first delete the existing bitfile, then load a new?

  Well, I found what I consider as a workaround - but maybe it's required to do things - but it doesn't seem like it should be, since the RIO device Setup.exe is able to flash or clear the bitfile regardless of the State of the FPGA.

  What I've done is to define the FPGA to "do not load automatically on re" then call the RT Config screw system and order a restart of the system.  The RT operating system restarts and then restarts the RIO system and this ensures that the FPGA is not busy.  Then I'm able to erase them or write about a new bitfile for the RIO Flash and set the "Automatic loading on any Reset" Rio de JANEIRO and restart the system again.

  Our current situation, it will work.  Long time restarts do a bit of headache.

• How will impact using LV 8.5 on my use of NOR-RIO 3.1.0

  I just started using the NI Compact Rio device and while I was installing NOR-RIO 3.1.0 he gave me the message that I really need to use at least LV 8.5.1.  At the moment I am unable to use LV 8.5.1 because I work in a regulated environment and I'm stuck at 8.5 at the moment.  What it will really affect me or I'll probably be OK?  Thanks for any idea that you can provide.

  You should be fine with RIO 3.1 and LabVIEW 8.5. Please note that 3.1.1 is available on our Web site at http://joule.ni.com/nidu/cds/view/p/id/1289/lang/en and you will see in the Readme that passed the version of LabVIEW 8.0 are supported.

  To check the minimum software for your hardware, versions of LabVIEW and RIO see this link:

  FTP://FTP.NI.com/pub/DevZone/tut/crio_software_versions.htm

  Let us know if you have any problems. Don't forget to install RIO after all modules and toolkits.

  Kind regards

  Anna K.

• How to install the biomedical toolkit to myRIO 1900 RT target

  Hello

  I try to install biomedical toolkit to myRIO using NI MAX. However, after that I installed on my system and ran the software Assistant in real-time to myRIO, I couldn't find the box tool as shown in the pictures

  

  I tried quitting biomedical screws on the portion of your code RT, but it complicates things even more by creating conflicts between the PC and the copy of LabVIEW RT library. Is there another way, I can understand that?

  

  You should not have to install the toolkit separately to the myRIO, it should be included automatically. However, if you have not done so already you need to reinstall the software recommended defined to ensure that these screws are pushed towards the target. After you do this verification for the biomedical palette on your myRIO.

  In addition, some express screws included in this palette will not work on this target because they use DAQmx, which is not compatible with our RIO devices. You will still be able to run the 'Biosignal Measurements' screw, but you will need to acquire the data using standard RIO methods.

• Restrict the LabVIEW deployment on NOR sbRIO

  Hi all

  I searched a lot to find a solution, but could not find one.

  I have to protect my controller sbRIO OR deploy any application of LV
  For example, if anyone with LV connects to the network of the controller, it should be not able to deploy anything to sbRIO before filling the credentials of the controller.

  Web configuration of the controller, I deleted all permissions to "everyone" group and set password for the user "admin".
  After that, MAX OR requires a password before you save anything to the controller, but LV does not require anything before you proceed with the connection of the programmer and the deployment of a VI on it.

  Could you please help me?

  Thank you in advance.

  Khoren

  What Single-Board RIO device do you use (Linux or VxWorks RTOS based?)

  The following white paper explains how to protect a Single-Board RIO and CompactRIO against unauthorized access.

  Overview of best practices for safety in RIO systems

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

  Looks like you need configure access to the server VI in part 1 to read the Security white paper.

  Kind regards

• NI USBLAN adapter disabled after a while

  Hello

  I use myRIO 1900 with LV2014 on an Acer Iconia tablet with win 8.1, 32 bit OS. I see (in network connections) that, whenever I connect the USB myRIO to the Tablet (via usb 2.0 OTG cable), NI USBLAN adapter installs and later is disabled (grayed) after one or two minutes. Here are my observations.

  1 restart the Tablet allows the card is physically removing and reconnecting the cable, both still for a few minutes only.

  2 tried manually all of RIO device drivers install the 32-bit driver LAN from the DVD, also installed in the tablet.

  3. no problem with my Lenovo PC, which uses 64-bit driver NI USBLAN.

  4. same question with Dell tablets and chroma too.

  5 'diagnose this connection"network connections wonder plug a cable ethernet on the network map, even if the cable is already connected.

  I have disabled firewall completely while doing all this. I had faced similar problems before while you try to view the remote façade on a Tablet and displayed in the forums, but has been unable to find the exact solution. I thought that it was a problem of OS until I saw the greying adapter out on its own after about two minutes. What could be the problem?

  Thank you

  Arya

  
  

• The link on cRIO speed settings do not survive restart

  I'm running a cRIO-9068 with firmware revision 1.0.0f1.  It is part of a static network including setting on autonegotiation link speeds.  However, if I put the cRIO to autonegotiation link speed, the cRIO fails to connect to the switch.  Fail lights and pings on the cRIO and switch activity doesn't show any activity.

  Curiously, the cRIO connects successfully when I set the connection speed to 100 Mbps/Full duplex or slower, and it is an acceptable workaround for me (for as far as the requirements of the project creep beyond 100 Mbps).  My problem is that this link speed setting does not survive a reboot cRIO.  After the reboot, the connection speed is reset to auto-negotiation and the cRIO is disconnected once more.

  I'm doing the link configuration changes via web interface of the cRIO speed.  I am logged in as an administrator and save my changes, and I get confirmation that the speed of the link has been set at 100/FDX.  Despite this, restarts always resets the cRIO to auto-negotiation.

  Another curiosity is the ratio of the switch that the cRIO is connected to 100/HDX.

  I tried to make a file of script in /etc/init.d with the command "ethtool speed 100 duplex full s.  I have updated using update - rc.d, but no joy.  Any script OR bat mine is either not using ethtool, or it is not dans/etc/init.d.  I don't know what else to watch because no where else to look at.

  Change the setting of switching to 100/FDX has solved the problem, but this setting is applied to individual ports.  This would force me to always use the same port for the cRIO, a restriction which I've had rather not commit.

  The problem is obviously the switch, because the cRIO connects to my development computer fine with auto-negotiation framework.  Unfortunately, the switch is a component not negotiable material project.  The fix should be done on the side of things cRIO.

  Any thoughts on why the cRIO doesn't remember it's link speed setting?

  Red evening,

  I found a known bug with this problem reported for LabVIEW 2013. I did a little test with LV 2014 shows that it is work as expected.

  You can try to upgrade to the latest NOR-RIO device driver? I could not find the details of it being fixed, so I don't know if its on the side of the LabVEW or the driver but its worth a shot.

  Car # is 464089 for your records.

  One last thing, you should switch to RIO 14.0.1 because there was a bug with disocvered with some components in the FPGA that fixed us that you need to upgrade.

  http://digital.NI.com/public.nsf/allkb/90AEA2EB87466CE786257D20005A3A44

• Cannot add to the target FPGA project

  I installed labview 2010 with en FPGA in real time

  In MAX under hardware, I see RIO0 under RIO devices.

  I also installed NI - RIO3.0, that I can see in MAX.

  When I try to add my FPGA PCI-7831R target in my project I don't see not all FPGA targets.

  How can I add my PCI-7831R to my project?

  LabVIEW FPGA and real-time 2010 require NEITHER RIO 3.5.1.  NOR-RIO 3.0 won't the good support for LabVIEW to create targets in the project, even if the FPGA will be detected in MAX.  You can install OR-RIO http://joule.ni.com/nidu/cds/view/p/id/2144/lang/en3.5.1.

• How a cRIO can access remote systems VISA resources?

  I have a NI 9871 RS485 module on an ethernet 9148 RIO.

  I have also a laptop and a cRIO 9073.

  I can access each of the 9871 serial ports on the computer but not the 9073.

  When you try to access it from the cRIO, I get error:-1073807192, VISA: (Hex 0xBFFF00A8) is denied access to the resource or to the remote machine. This is due to the lack of sufficient privileges for the current user or the machine.

  How the cRIO can access the serial ports of the module 9871 on the ethernetRIO?

  Or how a remote access cRIO visa resources?

  Or how a cRIO can have sufficient privileges to access remote resources from visa?

  Thank you for your help.

  LabVIEW 2010 & VISA 5.1 on pc

  NOR-RIO 4.0 and 5.1 VISA & NI 9871 SERIES scan engine support on cRIO and eRIO

  Hi Woss,

  It is possible that your RIO Ethernet has some parameters of active access which is to prohibit the connection to serial ports.  You can change these settings in a position and Automation Explorer (MAX) for your device by going to the device under remote systems, expanding the category of software under it and choosing NI-VISA.  There will be a tab in the right pane of MAX called Options of VISA.  In this tab, select Server VISA > security to access these settings.

  From there, you should be able to add the IP address of the RIO device that needs to access the VISA on the RIO Ethernet server.  Once you have changed these settings, just click on register at the top of the window and allow the unit to restart.  Let me know if that helps!

• Unable to access SMU-7962R + OR-5734 in LabVIEW

  Hello

  I have already developed a SMU system that uses FlexRIO. This has worked well. FlexRIO devices appear in MAX OR as follows (note that FlexRIO modules have yellow icons of FPGA, and their adaptation modules are shown):

  

  I'm now trying to build an exact copy of this system. I put together a together identical material, and (far as I can tell) I installed all the same components as the original system (using the NI Developer Suite 2015 DS1 set). However, something is not quite right. Here's what MAX OR shows me in the new system (note that FlexRIO devices now have generic grey icons instead of yellow icons of FPGA, and adaptation modules are not visible).

  

  In addition, the LabVIEW code that I developed for the original system generates a runtime on the new system error "NOR-RIO: (Hex 0xFFFF0928) the name of the supplied resource is not valid in a resource name of RIO or the device was not found." Use MAX to find resources appropriate for the expected device name. " LabVIEW is unable to find RIO devices:

  

  Here is the list of software installed on the new system:

  

  I also installed NI FlexRIO Adapter Module Support 14.1.0 (who does not appear in NI MAX). Can anyone place what Miss me?

  Thanks in advance!

  Hi David,

  2 controllers had exactly the same BIOS (version 1.2.0f0), which was the latest version for the SMU-8135.

  It turns out that, even if I had installed the drivers, Windows had not "registered" (?) the drivers properly for some reason any. There was a lot of articles in "Device Manager"-> "devices OR-RIO":

  • x 15 "NI SMU-7962R", were all OK
  
  
  • x 15 "NOR-RIO FPGA Device", all had yellow exclamation on them.

  I clicked "NOR-RIO FPGA Device" and selected "update driver software...". '-> 'Browse my computer for driver software'-> "Let Me pick from a list of drivers on my computer"-> 'NI - RIO FPGA Device'. After that I did "device of FPGA OR-RIO", all 15 exclamation points disappeared and I could use my FlexRIOs correctly.

• VeriStand not deply two FPGAS

  So, I can't understand why this is happening...

  If I deply the VS project to the RT with enabled FPGA (RIO0 and RIO1) target, it cannot deploy every time.  If I activate RIO0 and RIO1 - it works.  And same sense reverse (enable RIO0 and disable RIO1) so I know that my FPGA code and the *.fpgaconfig file work properly.

  Anyone know why this is happening?  I did some research but did not come with anything.

  Thanks in advance for the help.

  big shot in the dark here...

  Assumes that you have a chassis 18 locations, you use NIVS 2011 SP1 or an earlier version, and the cards are in different segments bus of your chassis (aka, pretty remote)?

  If so you must go to MAX, select the controller-> hardware-> frame-> triggers (the bottom tab)... and route of line 0 onset of the RIO device which is "BOLD" blue in your system definition (which is the specified master device on the chassis page)

  If I get this with no error information at all and a total guess I think I deserve a Bravo. If not too bad

• USB-6289 DAQmx delay early in the program

  Hello! Anyone help me with this problem.
  I have a new data acquisition is USB-6289.
  I'm only looking for I multiply by a decimal factor, after putting this result on AUG.
  for example
  AO0 ai0 * x =
  I want to do in continuous mode and in real time, with minimum delay. When I start the program, I have a time delay which varies.
  How can I measure this delay time?
  Anyone have an example of program to do (a simple multiplication in real time) and check where I have my mistakes.

  Thank you very much.
  Jonathan

  I put my program and a few cards of my oscilloscope (ai0-signal ao0 drop signal)

  Hi Jonathan.

  The code that you downloaded was not in parallel. Flat sequence structure forces the process to the AO HAVE to wait for the update panel. You can use the "Acquisition and recording of data" model to Create... Project for a reference on how to separate the update of the user interface of the real transformation.

  However, you must keep in mind that it is not possible to "simply to acquire a signal, multiply it and transmit" with DAQ hardware. This is because you must proceed as follows to get a signal and send it through the AO:

  1 acquire the signal in the DAQ card.

  2 send the signal to the computer via USB.

  3. ask the OS and LabVIEW process the signal to multiply.

  4. send the signal via USB in data acquisition.

  5. the output signal.

  This means that, while you can probably reduce the delay, you will always have this delay in the order of milliseconds. If you really need a shorter delay, you have a few options:

  (1) I noticed that the signal you're reading seems to be periodic. If it is a periodic signal, you can enable the regeneration in the AO and drastically reduce the delay, like the acquisition of data will just get the waveform periodical and cycle it. However, if the waveform changes, you will have some glitching.

  (2) use a multiplier circuit separated instead of data acquisition.

  (3) use a FPGA or RIO device instead of data acquisition.

  I hope this helps.

• Research of interface software for FlexRIOs using API c do I need LabVIEW once I use the C API generator?

  Current versions of software:

  LabVIEW 2014 SP1

  LabVIEW FPGA 2014

  Xilinx Vivado

  Hi all

  I plan to interface my FlexRIOs to the software programmed in C, then the C API FlexRIO is excellent.

  My question is more economy of memory sake.

  I have a PC with Visual Studio, I want to add the minimum amount of software development.

  If I have a station (a separate Visual Studio PC PC) FPGA development with all LabVIEW software necessary to take the step of the use of the generator of the C API to create the necessary files of C and H, should what software I on the development PC Visual Studio in interface with the files in the generated C API?

  If all goes well, it's just (from the help)

  What you need to get started

  • Drivers for devices OR RIO August 2013 or later

  However... The help of the C API, it gives me the full list of the software including LabVIEW and LabVIEW FPGA... (below)

  What you need to get started

  In addition to a RIO device like a CompactRIO reconfigurable chassis, a Single-Board RIO device or RIO PCI or PXI hardware, you need the following software to use FPGA Interface C API.

  • LabVIEW 2009 SP1 or later (32-bit only)
  • LabVIEW FPGA Module 2009 SP1 or later (32-bit only)
  • Drivers for devices OR RIO August 2013 or later
  • Operating system supported development
    • Windows 8 or 8.1 (32-bit or 64-bit)
    • Windows 7 Professional (32-bit or 64-bit)
    • Windows Vista Business (32-bit or 64-bit version)
    • Windows XP Professional SP2
    • Windows Server 2008 R2 (64-bit version)
    • Windows Server 2003 (64-bit version)
  • Target supported OS
  • Supported C/C++ compiler

  So I have LabVIEW and LabVIEW FPGA on the development PC?

  (If all goes well no....)

  Thank you

  Hey Colonel1013,

  With the C API, you only need LabVIEW to build a bitfile and run the generator of C API tool, but LabVIEW is not required to run. That is, you need all the software listed, but it must not all be on the same machine. You can transfer the file lvbitx and the .c and .h files generated on another machine where you need only NOR-RIO and Visual Studio installed.

  Sebastian