cRIO 9802 error 65000

Similar Questions

• Error 65550: CRio 9802

  Hello world

  I was running an example 'NI 9802 RT access' writing to a 9802 9074, but I got the following error:

  Error 65550 occurred at cRio - 91XX_MountSdDrive.vi

  Possible reasons:

  CompactRIO: A problem was found in the file system. Remove the SD card and run the CHKDSK command.

  Running CHKDSK returns no problem. No idea what is causing this error?

  Thank you very much.

  Derrick

  It is a known problem for the driver NOR-RIO 3.0.1 you can fix by upgrading NI RIO 3.1

  Please repost if that does not fix it.

  -Hunter

• Unable to create a file with "nidll_vxworks" in Matlab for use with the LabVIEW SIT 2010 and a cRio 9073, error sh.exe

  I am trying to compile an OUTPUT for my Simulink model file by using "nidll_vxworks" and execute it using the Simulation Interface Toolkit for a cRIO 9073. I am able to compile the DLL file by using "nidll" and managed to run the simulation using my PC as a host.

  I have already downloaded the files "gccdist" and "vxworks61gccdist" and copied in "c:" when I build the model in Sumulink I get the following error at the end of the process (at the same time windows tells me that "sh.exe" has stopped working). If it's important, I'm on Windows 7 64-bit, but using Matlab 2009 b 32bits and LabView 2010 32-bit. ANY HELP WILL BE APPRECIATED. "QofV" is the name of my Simulink model and I changed to parts of "XXX" in the path of the file.

  6.1 CCG is only supported on Windows XP.  It is almost indicated in the readme_sit_vxworks.txt found in C:\SimulationInterfaceToolkit\xxxx\VxWorks (where xxxx is the version of the DIS).  It is said:

  * Known issues
  
  ---------------------------
  
  -WindRiver GNU Toolchain 6.3 and 6.1 do not work on Windows Vista.

  To be more explicit, it should be "Vista and later.

  Carl L

  National Instruments

• CRIO build error

  I downloaded the files for example Structural Health Monitoring and them custom for my equipment (cRIO-9074 with 2xNI9234 and 1xNI9213). The program has been implemented until I cleaned my files and folders in the project. Now when I try to compile the main VI (Deployment.vi [RT]) to a startup in real time application, I get the following error.

  Don't know what to do because:

  1 - .vi runs when I just click "Run" rather than build.

  2. all files are still there I would say.

  3 - error message is not very clear

  Any help?

  Visit ni.com/ask support request page to learn more about the resolution of this problem. Use the following as a reference:

  Error 6a held at AB_Source_VI.lvclass:Close_Reference.vi-> AB_Build.lvclass:Copy_Files.vi-> AB_Application.lvclass:Copy_Files.vi-> AB_RTEXE.lvclass:Copy_Files.vi-> AB_Build.lvclass:Build.vi-> AB_Application.lvclass:Build.vi-> AB_RTEXE.lvclass:Build.vi-> AB_Engine_Build.vi-> AB_Build_Invoke.vi-> AB_Build_Invoke.vi.ProxyCaller

  Possible reasons:

  LabVIEW: File generic i/o error.
  =========================
  NOR-488: IO operation abandoned

  Stephen is correct, it is a problem of length of path of files. It is imposed by Windows, not of LabVIEW, and I saw it happen when the components in a project are organized very closely in many subfolders. Windows imposes a restriction of 255 characters path length. Have fewer subfolders or reduce the length of the name of the object so that it does not exceed. Look in the tab "Files" of your project, so you can have an idea of 'complex' how the structure of your file, just put something on your desktop come a long way!

• Error 15 with COLD LAKE in nisyscfg.lvlib:Set the System Image

  Recently updated the code that worked for imaging cRIOs in LV and LV 2012 2011 should be replaced by the new and improved nisyscfg.lvlib screw: define a System Image, get a System Image, etc,...

  I get the following error message when my installed executable tries to imagine a cRIO: ' 15 error occurred at the library function node call in nisyscfg.lvlib: Set the system (folder) .vi:1-> nisyscfg.lvlib Image: System to define Image (file) .vi:1-> GetSetSystemImage.vi'. Displays the possible reason: ' LabVIEW: resource not found. "

  What products/installation packages are required for the system of screw configuration? I'm including NISysCfg_Runtime and NISysAPI_Framework.

  Thanks for your time.

  Problem solved! Correct installation packages are: NISysAPI_Framework, NISysCfg_Runtime, mDNS_Responder, NI_Curl, NI_SSL_Support, NI_TraceEngine, NI_RPC and the mxRmCfg.dll.

• VI to convert input signals NI 9402 in a RPM value, based on the frequency of the pulses

  Hello

  I'm looking for a VI convert an input signal NI 9402 in a RPM value, based on the frequency of the pulses. Is there such a thing that exists in the library of national instruments?

  I run LAbview 2014 integrated control and monitoring on on a cRIO 9802 high performance integrated system with NEITHER 9402, 4 channels, 50 LV, LV TTL Module input/output digital, ultra high speed digital i/o for the cRIO module.

  Any help would be greatly appreciated.

  The easiest way is to use the FPGA to get the time between the edges of your pulse increase (shift registers to maintain the current situation and the time will be necessary).  This will give you the period.  If it's a single pulse per turn, then the number of laps is just 60/T, where T is the time in seconds.

• FTP 9802 by cRIO-9074

  Hi all

  Using the example of LV I can apparently go up and write on a SC map in a module 9802 without problem. A sample file is written to the location u:\Example.txt

  Unfortunately, I can't FTP to this player using the address ftp://xxx.xxx.xxx.xxx/u :/ (I can ftp to the controller, a cRIO-9074, without problem). When trying to connect to the SD card, the internet Explorer simply indicates that the page cannot be displayed.

  Various previous discussions talk about adding a property node (where should pass exactly?) that allows to resolve a conflict. Supposedly this problem has been resolved the recent versions of RIO.

  Another discussion suggests that RIO 3.0.0 worked while RIO 3.1.0 failed in a manner similar to what I see - he seems to not have been a resolution.

  I'm running RIO 3.1.0 with Support of EtherCAT Scan Engine since October 2008.

  Ideas?

  Thank you!

  a slight correction... I "cd" to the "sup" drive letter and the crio ftp server responds "Directory changed to" / u: / '. '.   Sorry for the mistake.

  quarterlbr wrote:

  Hi-

  just stumbled on this thread - I hope that someone is always watching...

  I have a similar problem, (9074 w/9802) that I can't ftp access to the card.  I can mount it and writing, but I do not see in ftp.

  I mount it and it assign a drive letter.

  through screw normal rt file, writing to the card.

  Let the mounted card until the program ends, then it should retain the drive letter - correct?

  When I ftp to the card (via ftp console), I "cd" to the drive letter "x:" and the crio ftp server responds "Directory changed to" / u: / '. '.  look suspicious to me, but in any case, I try to "dir" content and I get an 'error of e/s 451.

  I checked the content of the map is there in removing the card and reading the contents via a card reader.

  no idea what I am doing wrong?

  I have installed 3.1.1 rio.

  Thank you.

• error when trying ot read more large block memory on cRIO 9067 LVRT 2014

  I get error "-2147220623" when you run the following code on a cRIO 9067. It works on the cRIO 9074

  

  
  

• Version with ControlLogix - link cRIO (implicit messaging), "(Code 16 #0315) problem" connection request error: invalid segment type ""

  I have developed and delivered a system in Germany several years ago.  He worked then.  But the cRIO was damaged and replaced by a newer model, and does not now.  I suspect (and Support technical OR agree) it's a problem of software version, which could be solved with the NOT-MAX Software Installer.  But I do not have access to the system myself, and correspondence is slow and tedious.

  The original system was a cRIO-9073, developed with LabView 2009.  He used the implicit Messaging.  The ID of Instance, sizes, IP addresses, etc everything has worked very well.

  The current system is a cRIO-9074, with LabView DURATION 14.0 (I guess that LV 2014), Scan Engine 4.3, NI - Industrial Communications for Ethernet/IP 14.0.0, etc.  Programs FPGA and processor are responsible and seem to work in the cRIO.  The "EthernetIP Set Assembly Instance Data.vi' will return no error.  But the PLC just pointing out "(Code 16 #0315)" connection request error: invalid segment type "."  We looked at intellectual property (the mistake was different), sizes and body #s.

  The PLC doesn't have to all be modified.

  Anyone know if there is no problem of compatibility with LV-2014 and Ethernet/IP 14.0.0?  Or if there are all the other required packages?

  I am including the NOT-Max reports.

  Hi ZX81

  To help you 2009 application to work with the new cRIO, you must deploy it to the device. You must in order to deploy the cRIO, make sure it has the same versions of software that you used with the old cRIO.

  You can format the cRIO NI MAX and deploy the application of LV, 2009. However, if you do not have access to the cRIO or your client does not have the necessary software, you can deploy the application in another cRIO with software (cRIO same model and same modules as your client) and create a picture of it and send it to your customer so that it can deploy the cRIO even without the software on his computer. The following document explains how to do this.

  Utility of RAD

  WenR

• Error Code HDL with CRio RFP generation after update for LabView 2012

  Hello everyone,

  I use a CRio DP Comsoft master/slave module for my communication with a PLC system. The application worked perfectly under LabView 2011. After the update to LabView2012, I got an error message that the HDL Code generation failed. After that I've updated also the Software NI Profibus CRio in Version 1.3, but this n ' t´t solve the problem. The next step was to use the example of project code "CS_cRIO-PB_DP-MasterExample" which was delivered with the new NI CRio Profibus software. Even with this code example, the problem still exists. For detailed information on the configuration and the error message please refer to the screenshot. Any help or idea would be appreciated.

  Jürgen

  Hi Jürgen,

  I looked inside and could reproduce this error. Somehow the compiler with LV 2012 has problems with the coded 8.5.1 Subvi LV. Please use the attached VI and copy it to the following location. (\\Program Files\National Instruments\LabVIEW 2012\vi.lib\addons\Comsoft.lib\cRIO PB)

  Before do you it please close your LabVIEW.

  Then try to compile again.

  Let me know if it still does not. We are currently working on a new installer that will correct this problem.

  DirkW

• Error 200220 CRIO 9081 and data acquisition modules

  Hello

  I try to use a CRIO 9081 with NI9206 modules. Max recognize the chassis, but not the module.

  When I try to add an acquisition of data associated with the NI9206 in Veristand, 200220 error message seems.

  I have the solution, finally he was required to add a custom device to search for new engines and detect modules. Then, it is possible to interact with modules.

  Thank you very much for your help!

• cRIO 9068 + Scan Engine Support error - even if it is installed on the cRIO, after the deployment of error says his lack

  All,

  I have a cRIO-9068 I try to use the scan mode for. I have intalled all the latest drivers and software as explained. However, when I put my chassis to scan mode, then select deployment all, I get this error on my chassis and all my modules:

  "The current module settings require a NI Scan Engine support on the controller. You can use Measurement & Automation Explorer (MAX) to install a software package recommended NOR-Rio with NI Scan Engine support on the controller. If you installed LabVIEW FPGA, you can use this module with LabVIEW FPGA by adding an element of FPGA target under the chassis and drag and drop the module on the FPGA target element. »

  Everyone knows this or know why labVIEW does not recognize that the software is installed on my cRIO or is it not installed correctly?

  AGJ,

  Thanks for the image. I saw a green arrown beside all my pictures of chip and it seemed that meant that the software wasn't really being installed. I formatted my cRIO and did a custom install. My problem was that I had the two labview 2013 and 2014 installed and the cRIO put conflicting versions of software. After doing a custom installation and choose only the versions of 2014, my picture now looks like yours!

• cRIO ethercat application error

  I have a cRIO-9074 connected to and AKD via EtherCAT drive, running in standard mode.

  Simple straight line move using a VI express softmotion.

  It works fine except when I force the engine to stall, a strange thing.

  When I take the engine yet it will suddenly reverse direction rotates at a speed faster than the requested speed rear forward.

  The faults of the ADK out but it takes 100 to 400 ms to turn off the power.

  The AKD displays F 503 and Labview indicates an error code 6A 3130.  This resulted in "phase failure AKD.

  Relavent part of this error is: "the excessive power single-phase connection load".

  Of course I am inducing power over load so expect this fault, but the reverse rotation before the AKD Cup feeding is strange.

  I tried to reproduce this using the Kollmorgen Workbench software, but so far it only happens when Labview is controlling via EtherCAT.

  Hello Brians,

  Taking the engine beyond normal limits of operation may cause unexpected behavior. It is never recommended to intentionally block the engine. In this case, it seems that LabVIEW is trying to remove the constraints inherent in the system in the case of a stall by reversing the motor. The reason why you do not see this behavior in the Workbench is because it does not contain the control algorithms that are present in LabVIEW. In addition, I am curious about how to determine the time the motor runs in reverse; 100-400 ms seems very specific. If the pitch of the engine is possible in your code, I need to program under a security to handle this situation and perform all measures requires your application in the case of a stall.

  N

• cRIO-9074 2147138533 error on active state transition analysis engine

  I have a cRIO 9074 configured as master EtherCAT.  The code for the RIO FPGA is followed by other data on the State and he is able to shut down all power to the rest of the system (including the EtherCAT slaves) for safety.  If I power cycle the cRIO (whose power to EtherCAT slaves Travel) I get the following error when it goes into active mode on the scan engine:

  Error 2147138533 has occurred to the property node (arg 1) in the updated scan engine Mode.vi-> RT Startup.vi system

  Possible reasons:

  The telegram is to expire.

  Check that the master device is connected to the EtherCAT network. Ensure that each slave in the EtherCAT network device is turned on and properly connected.

  Is it possible to start the engine even with the slaves turned off?  I just need to change my program to dynamically discover the slaves to stop the scan engine of faults on scan engine transitions?  I don't want to feed my slaves EtherCAT back on until I can read data that are currently being monitored by the scanning engine on the RIO even... is this possible somehow?

  Hello

  EtherCAT is tightly coupled with the analytical engine.  There is no way to set the active scan engine, while an EtherCAT Slave is disconnected.

  I recommend watching the following Article of knowledge-based programmatically discover and access EtherCAT.

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

  Kind regards

• TDM screw streaming doesn't work is not on the cRIO - error 53?

  Hello

  I am fairly new to the programming of the aim of RT, and I am running into a problem.  I use a cRIO-9074 to acquire data and I try to log on by using screw TDM streaming.  Unfortunately, I get this error:

  Error 53 occurred at TDMS Open in Test_TDMS.vi

  Possible reasons:

  LabVIEW: Manager call not supported.

  The VI is attached, and writes to a file normal works very well.

  Thank you very much!

  TDMS cRIO/VxWorks support has been added in LabVIEW 8.6. Older versions of LabVIEW will give you this error when you run on one operating system other than Windows or PharLap.

  You can also write on cRIO TDMS files using the VI based TDMS API for LabVIEW 7.1 or newer.

  Hope that helps,
  Herbert