Installation improper cRIO 9076

Estimados:
tengo mun cRIO 9076, utilizo LabVIEW 2014 y me encontrado con el infortunio del mensaje MODO SEGURO INSTALACION INAPROPIADA.
He realizado todas las sugerencias encontradas en la web:
cambiar el nombre del dispositivo.
volver a instalar el software
en repetidas ocaciones y el resultado sigue siendo el mismo.
No avanzo en el proyecto y es ultimo paso para termianrlo.
Alguine podria ayudarme?
Que me sugueren?
De antemano Muchas gracias por sus valiosas aportaciones
Jose Marticorena

Que tal JMarticorena,
Me gustaría compartir contigo los siguientes links que hacen referencia a las causas del estado "Safe Mode (Improper Installation)" del cRIO y a posibles soluciones.
Why is my CompactRIO (cRIO) System State: Connected - Safe Mode (Improper Installation)?
Improper Installation Message on CompactRIO with NI-RIO 3.1 and MAX 4.5
En el segundo link comenta que una posible solución puede ser actualizar el software que tenemos instalado en la computadora Host por lo cual me gustaría que nos comentaras que versiones de NI-RIO y de MAX posees?
También me gustaría que ingresaramos al Console Out del cRIO para realizar un diagnóstico del controlador cuando se encuentra booteando. Este diagnóstico nos podría dar una idea más clara del posible error. Te comparto el link con el procedimiento para ingresar al Console Out.
How do I enable the Console Out on CompactRIO, Single-Board RIO, CompactFieldPoint Controllers?
Por favor comparte con nosotros un screen shot de la información que aparece en la ventana de la Terminal.
Espero esta información sea de utilidad y quedo al pendiente de tus comentarios.
Saludos!
Antonio S.
Applications Engineer - NI Mexico

Similar Messages

CRIO-9076 USB

Bonjour,
J'aimerais savoir s'il est possible de connecter une clef USB au port dédié sur un cRIO-9076. J'ai essayé plusieur méthode (clef en NTFS et FAT32 de grande et de petite capacité) et impossible de la détecter via Filezilla.
Doit-on installer quelque chose de spécifique dans les logiciels de l'automate auquel je n'aurais pas pensé ?
Merci par avance.
Windows 7 - LabVIEW 2012
Résolu !
Accéder à la solution.

Pardon du double post, en fait un peu de patience et de lecture m'ont permis de trouver la solution.
Une clef USB en FAT32 est bien détectée mais sous "U:\". La réception des données via Fillezilla et à l'aide des VIs FTP sous LabVIEW fonctionne impec'.

I can not find NI cRIO-9076 in Remote System

I can not find NI cRIO-9076 in Remote System. How can i deal with it? The Status LED is on every couple seconds.

It must be activated before Apple's tracking system will recognize it. I just tried your SN and that was the message I got from https://selfsolve.apple.com/wcResults.do.
I suggest editing your post and removing the identifying information in it, as millions of people can read these forums and not all of them are completely honest.

Problem in data acquisition for cRIO-9076 wth c series drive interface module 9516

I am using LabVIEW for my project i.e., the speed control (using PID) of a motor and want to create a vi for the same.
The specifications of the products being used are as follows:
1) Motor: AKM24F (dc motor)
2) CompactRIO: cRIO-9076
3) C Series Servo Drive Interface: NI-9516
I am facing problem regarding the real time interface between the motor and PID block in labVIEW i.e. in the data acquisition part to be specific. Please suggest a way in which I can successfully acquire the analog data(speed) from the motor and vice versa in the vi.

What is the priority of the VI you're running? I'd be concerned that maybe you've starved out the ethernet transmit thread or something.
-Danny

Continuous Data Logging with NI 9236 an cRIO 9076 with FPGA

Hey all,
i'm a beginner in LabVIEW/FPGA. My goal is it to
continuous acquire and log data. I've a 9236, CH0 is
connected to a strain gauge and the cRIO 9076.
I've written a code and I see the incoming data on the FPGA.vi.
On the Host.vi there is no outcoming data out of the FIFO.
There is no error messages or an error during the compilation.
Do I have a timing problem? Where ist the big mistake
Thank you!
Attachments:
1.jpg ‏98 KB
2.jpg ‏71 KB
4.jpg ‏337 KB

In your first image one problem is that you are starting the module on each iteration of the loop. I can't tell how your FIFO is configured, but take a look at the example "Hardware Input and Output->CompactRIO->Module Specific IO->Analog Input->NI 923x Continuous DMA.pvproj. I don't know which LabVIEW version you are using but I found this example in 2012.

New to NI cRIO 9076

Hello everyone!
i am completely new to interfacing NI modules with labview. i interfaced cRIO 9076 through ethernet, installed all the softwares (NI RIO, NI RT etc). it is getting detected in NI MAX. but all it shows is "cRIO is in safe mode( no softwares installed)" and status LED blinks two times indicating trouble with software.
how do i configure the device. what are the things to be done to use cRIO.?
PS:i also have gone through the getting started guide from this link
http://www.ni.com/gettingstarted/setuphardware/compactrio/
Thank you!

i have installed everything from the LabVIEW evaluation CD. i have also checked that all the necessary cRIO softwares are installed.
i use 2013 version of FPGA,NI MAX and RIO
OS is Windows 7
when i check the NI distributed system it says i have attached modules at port 1&4(in screenshot). so i guess there is no problems with the cRIO.
Attachments:
Distributed system.JPG ‏67 KB
national instruments softwares.JPG ‏123 KB

Combine cRIO 9076 and cRIO 9081

I have two FPGA real time controllers: cRIO 9076 and cRIO 9081. Due to not having the latest version of LabVIEW (2011), I am unable to use cRIO 9081. Since cRIO 9076 has only 4 slots for the modules, I am thinking of using cRIO 9081 as a slave just to add more modules on its slots. Will this work? If so, how can I connect cRIO 9081 to cRIO 9076. Any suggestion is appreciated.
Solved!
Go to Solution.

Hello ExcelX,
Unfortunately, there is no meaningful way to interface with the 9081 without having the correct versions of LabVIEW (at least 2011) and NI-RIO (at least 4.0). It does run windows, so you could in theory boot it up in Windows and attach a monitor to it, but you wouldn't be able to run any code on it.
You could download the trial version of LabVIEW 2011 and use it with your 9081 for thirty days. But I recommend just upgrading to LabVIEW 2011 - the 9081 is a powerful (and expensive) CompactRIO.
Colden

CRIO 9076 AI Sampling Problem

Hi,
I have a question about the NI 9223 samping rate in our cRIO 9076 system.
Since we are hoping to samping at a rate up to 500K or 1M, we are now using the user controlled I/O sampling.
Right now, we are sampling at 500K (2us). But I got a tick count of 99 ticks (around 2.5us) for the sampling node only.
Should I be expecting so many ticks for the sampling block? Did I do anything wrong?
Thank you so much!
Solved!
Go to Solution.
Attachments:
problem.JPG ‏399 KB

Hi hang-up,
It looks like you are specifying the loop rate for the entire while loop you are in, and not just that one specific part of code. Because you have your loop timer controlled by an front panel object, it is possible that the code compiled, but if you change the loop time to a low value, the code cannot complete in time. I would suggest that you isolate the acquisition you are trying to do in it's own loop so that it can run at full speed.
Additionally, in order to get the full MS/s acquisition, you are going to need to architect your acquisition. I would encourage you to check out the example code in our Example Finder for the NI 9223 User Controlled II Compositionally for the best way to get these maximum acquisition rates. Additionally, depending on how you are going to be exporting this data from the FPGA, your ART controller may not be able to handle a sustained MS/s throughput.
To explicitly answer your question, I suspect that because you are trying to complete a large loop in a short amount of time, the FPGA cannot complete the task in time, so it defaults to a rate that can be better handled. For the control you are looking for, I would encourage you to move your application over to the architecture found in the example project to get the behavior you are looking for.
Ben N.
Applications Engineering
Certified LabVIEW Developer

CRIO 9076 internal block diagram?

Hi guys--
I'm trying to work up a document on our cRIO 9076 for the lab, and I'd like to include a schematic/block diagram of its overall internal structure...something like what PC motherboard makers give (example below). The internals of the RT controller are pretty easy to guess at, but I'm a little fuzzy on the connections between that and the FPGA, and between the FPGA and the chassis modules. Any pointers on where I should be looking (not in the manual, by the way)?
Thanks a bunch.

David--
Thanks a bunch for your reply. That manual got me pointed in the right direction. I also found this little wiki stub:
http://en.wikipedia.org/wiki/CompactRIO
which specifies the controller-fpga connection as PCI, meaning much of the details are probably obvious with a better understanding of PCI busses. In any case, I've managed to start a diagram of my own that will suit my needs just fine.
Thanks again, and have a great day.

CRIO 9076 disconnecting

I am attempting to use a cRIO-9076 with the NI 9512 and the NI P70530 stepper driver. However, I am having difficulties keeping the 9076 connected to my host PC. I've read the forums on this problem before, but those answers did not help solve my problem. The cRIO will connect when first powered on or reset, and will be visible in MAX, but when I try to view the attached devices in MAX (e.g. NI-9512 module), the cRIO will disconnect.
I also cannot connect to the device in LabVIEW at any point.
I am using LabVIEW Real-Time 11.0.1 on the cRIO, and also Real-TIme 11.0.1 on the host PC (LabVIEW 2011 SP1 f2).
Any suggestions are appreciated.
Thank you,
Enan

Hey Enan,
Thanks for posting on our boards. You posted on the LabVIEW boards which is good, but I think you will probably get more responses if you post on the boards that are for the cRIO and RealTime stuff.
Here is that Board: Real-Time Measurement and Control [cRIO, R Series, FlexRIO, sbRIO, GPIC]
That board is frequented by more people that interact with the cRIO and RT more than just the LabVIEW board.
When you post there, I would also add what your OS is and what bit OS you are using. It might be helpful!
Thanks for posting!
Douglas C.
Applications Engineer
National Instruments

Brushless Motor Commutation using cRIO 9076

I need some help as I trying to find a way to do motor commutation.
I am developing a closed loop control system that consists of an applimotion motor (UTH-100-A-25-A-x-000) and AMC Digital Drive (DPRALTE-020B080) on CompactRIO 9076 FPGA Real Time Controller. The motor does not have hall sensors. Any suggestion on how to do motor commutation using this FPGA device is appreciated.
Thanks

How difficult it will be will depend on how complex those interfaces are.
If the encoder interface is simple, for example a clock and data pin that returns only the position, then writing the code to talk to it will be pretty straight forward.
Some absolute encoders use very complex protocols. I can't tell you exactly how hard it will be because I don't know this encoder.
I would expect that writing the analog position feedback to the drive will be easier but I don't know exactly what the drive is expecting either. You wrote earlier that the drive manufacturer told you specifically that the drive would work with analog position feedback and no hall sensors. I don't see how that would de done from the datasheet. You need to be sure that this is true because otherwise this approach will be impossible.
You should start by tackling just the encoder half of the problem. Hook up the encoder to your DIO module and start trying to query it. I hope you have more information about its interface than what is found in the datasheet- otherwise you would either need to contact the manufacturer or do some experimentation.
Give it a try and if you run into specific obstacles then we can help you with those.
BTW- The easier solution is to throw money at the problem and buy motors, encoders, and drives that are compatible with each other. For example, NI sells motors and cRIO modules that can drive them, including brushless. At that point the software is just opening an example and adding your own position setpoints.

CRIO 9076 Time Sync

If this is true NTP synchronization does a large correction of the date-time on boot. After boot, it adjusts the processor clock to account for drift. The algorithm has an error tolerance but if you exceed that tolerance (i.e. if you are too far out of synch) it will stop trying to adjust the processor clock to synchronize. Calling the Set Date & Time VI typically causes the clock to move beyond the algorithm error tolerance. Is there an error tolerance on the large correction also? I am not able to get my system to sync on boot so if the controller resets, I lose my time. Is there a VI to query the sntp server during initialization and set the time there?
Solved!
Go to Solution.

I must be doing something wrong then.
I have a PC and the crio in a mini switch which is connected to out network switch so they are both running through the same network gateway.
Our Time Server is the same machine as our DHCP server and the DHCP is providing an appropriate IP.
On the Web Based config page of the crio I am getting "Failed to Receive Response from SNTP server" at the 60 second polling interval.
I have installed NI-TimeSync 1.1.2 on the cRIO. Below is my ni-rt.ini
[SYSTEMSETTINGS] Comment=00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 Comment_Format=512 Host_Name=ELO-VTShed Protect_Reboot=FALSE
[TCP_STACK_CONFIG] DNS_Address=USE_DHCP Gateway=USE_DHCP IP_Address=USE_DHCP Subnet_Mask=USE_DHCP
[TIME SYNC] source.sntp.address=192.168.150.44 source.sntp.enable=TRUE source_priority=sntp;rtc; source.sntp.interval=60 source.sntp.port=123 source.sntp.verbose=True source.sntp.log=False
[LVRT] memoryChecking=False LABVIEWRTDir=/c/ni-rt/system CDIntervalTicks=55 WebServer.Enabled=FALSE RTTarget.VIPath=/c/ni-rt/startup RTTarget.IPAccess=+* RTEnetRcvMode=2 RTCPULoadMonitoringEnabled=True RTTarget.ApplicationPath=/c/ni-rt/system/startup.rtexe WebAppServer.Enabled=True StartupDlls=nisysrpc.out;NiRioRpc.out;nidp_target_end.out;taggerrt.out;niserial.out;NiViSrvr.out; PATH=/c/ni-rt/system/;/c/ni-rt/;
[MODULE VERSIONS] criosd.out=6.3 niriompc5125k.out=6.3 nivirio.out=6.3 niriosrv.out=6.3 niriorpc.out=6.3 NiFpga.out=6.3 NiFpgaLv.out=6.3 niriosae.out=6.3 nisysapi.out=6.3 nisysrpc.out=6.3 nirpcs.out=6.3 lvanlys.out=6.3 lvblas.out=6.3 goopsup.out=6.3 rendezvs.out=6.3 semaphor.out=6.3 nbfifo.out=6.3 settime.out=6.3 lvalarms.out=6.3 lvuste.out=6.3 nisvcloc.out=6.3 rtvarsup.out=6.3 lvrt.out=6.3 tsengine.out=6.3 ni_emb.out=6.3 vxfpsup.out=6.3 nirtdm.out=6.3 nipci.out=6.3 libexpat.out=6.3 registry.out=6.3 ftpserve.out=6.3 crio_ce.out=6.3 NiViEnet.out=6.3 NiEnAsrl.out=6.3 NiViRpc.out=6.3 NiViSrvr.out=6.3 niserial.out=6.3 taggerrt.out=6.3 TgrDD.out=6.3 bb_lib.out=6.3 crio_expert.out=6.3 nNIBlueBus_nCrioFixed_nRefnum.out=6.3 lvpidtkt.out=6.3 NiViUsbj.out=6.3 nitaglv.out=6.3 mxssvr.out=6.3 mxsdb.out=6.3 mxsutils.out=6.3 mxsdd.out=6.3 mxsin.out=6.3 mxs.out=6.3 nilvce.out=6.3 lvceconfig_handler.out=6.3 nilvicv_deployhandler.out=6.3 nilvicv_runtime.out=6.3 niScanEngineConfigIntf.out=6.3 nidp_target_end.out=6.3 nidp_host_end.out=6.3 dmRIOBus.out=6.3 NiViSv32.out=6.3 NiViAsrl.out=6.3 visa32.out=6.3 NiViSys.out=6.3 nisysapisvc.out=6.3 niSysNetCfg.out=6.3 niDiscSvc.out=6.3 niDiscExp.out=6.3 ws_runtime.out=6.3 nilwpce.out=6.3 logosrt.out=6.3 nilxtcor.out=6.3 nipspxts.out=6.3 ni_traceengine.out=6.3 nigmp.out=6.3
[SUPPORTED LOCALES] english=L1
[STARTUP] MainExe=/c/ni-rt/system/lvrt.out DisplayStartupLibProgress=TRUE EarlyStartupLibraries=nirtdm.out;nimdnsResponder.out;vxfpsup.out;tsengine.out;nisvcloc.out;RTWebServer.out;niDiscSvc.out;mxssvr.out;
[MDNSRESPONDER] mDNSDisableAnnouncement=0 mDNSDisableDiscovery=0
[DEPENDENCIES] lvrt.out=ni_emb.out;libexpat.out;niCPULib.out;libappweb.out;libappweb.out; crio_ce.out=bb_lib.out;nilvce.out; NiViRpc.out=nirpcs.out; NiViSrvr.out=nirpcs.out; ni_httpClient_nossl.out=nigmp.out; taggerrt.out=logosrt.out;mxssvr.out; bb_lib.out=NiRioSrv.out;libexpat.out;nilvce.out; crio_expert.out=NiRioSrv.out;bb_lib.out; nitaglv.out=logosrt.out; mxs.out=mxsutils.out; mxssvr.out=nirpcs.out;mxsutils.out;mxsdb.out;mxsdd.out;mxsin.out; criosd.out=niriosrv.out; niriompc5125k.out=niriosrv.out; nilvicv_deployhandler.out=nilvicv_runtime.out; nilvicv_runtime.out=logosrt.out;nilvce.out;libexpat.out;nilwpce.out; lvceconfig_handler.out=nilvicv_runtime.out; niScanEngineConfigIntf.out=nidp_host_end.out;nilvicv_runtime.out; nidp_target_end.out=libexpat.out;logosrt.out; nidp_host_end.out=libexpat.out;logosrt.out; dmRIOBus.out=bb_lib.out; visa32.out=NiViSv32.out; NiViSys.out=nisysapi.out;visa32.out; NiFpga.out=niriosrv.out; NiRioSrv.out=libexpat.out;nirpcs.out;lvrt.out; NiRioRpc.out=NiRioSrv.out;nisvcloc.out; NiViRio.out=NiRioSrv.out; niriosae.out=nisysapi.out;niriosrv.out; NiFpgaLv.out=NiFpga.out; nisysapisvc.out=nisysrpc.out;nisysapi.out;nimdnsResponder.out;ws_runtime.out; niSysNetCfg.out=nisysapi.out; nisysrpc.out=nirpcs.out;nisysapi.out; niDiscExp.out=nisysapi.out;nimdnsResponder.out;niDiscSvc.out; niDiscSvc.out=nimdnsResponder.out; ws_runtime.out=nilwpce.out; RTWebServer.out=libappweb.out; libniauthModule.out=nigmp.out; nilwpce.out=logosrt.out; niauth.out=nigmp.out; nipci.out=nirtdm.out;
[NVE] MessageQueueUpperBound=1000000
[NIDP_HANDLER_LOAD_ORDER] nilvicv_deployhandler.out=crio_expert.out; lvceconfig_handler.out=nilvicv_deployhandler.out;
[LOGOSXT] Heartbeat_AbsenceDetectCount=10
Any ideas? Thanx

Firmware update on cRIO pn c module

I am looking to update the firmware in a Comsoft Profinet cRIO c series module. The data length is not outputting the configured data length. The module is in the 4th slot in a cRIO 9076 unit. The module is working but updates the data very slowly. I have attached a picture from the getting started manual showing the parameter and the note about the parameter.

MrSinatra,
I think it is very well possible that the drivers on your cd do not recognize the updated x-fi anymore. the cd is probably useless now.
a screenshot of this firmware update will most likely not be possible because you cannot repeat it! since you cannot downgrade the firmware, the update routine won't run again the next time even if you run the same driver update again.
let them call you a stupid idiot. it doesnt matter. you have seen it, i have seen it, others have seen it. so we know it happens, right?
as to what this cthelper.exe actually is, i have also wondered already. i also have read Soundcard sams comment as well and checked and i also do not see it anymore in vista. it seems to be gone. I have googled a little but it looks like nobody really knows what it does. its probably just not necessary anymore with the new drivers i suppose.
Just check your startup reg and disable it. see if it makes any difference. maybe u don't need it anymore either. maybe its just the old registry entry that didn't get deleted and still calls it at startup? just try. I can still see it being acti've in my Windows XP Sp3 installation (32bit) though. Seems like its just not acti've in vista anymore. just toy around with it a little. you'll notice if it breaks something if you mess it up ;-)
Oh and btw: there is another tool running now, its called Ctxfihlp.exe and it might just be a replacement of the old one...

How to get system time from cRIO?

Hello,
I have an NI cRIO-9076 chassis with an NI-9467 GPS module and an NI-9234 module.
I've downloaded the FPGA Timekeeper application which synchronises the FPGA clock to the 1PPS GPS, this works well. What I want to do is create a trigger that at a pre-defined HH:MMS the system will start to acquire and log data from the Accelerometers connected to the NI-9234 module.
I have added the controls for the entry of the HH:MMS and calculated the time in seconds. I would like to compare the system clock once it is locked to the entered timestamp and then trigger.
As I only have a value that represents seconds in the day I need to calculate the offset from EPOCH to compare against the GPS time reference. I have read that the NI system clock runs from 01/01/1904 instead of the EPOCH 01/01/1970.
The question is how do I get the current system time so that I can compare it against the entered time? I only need seconds in the day = (HH * 3600) + (MM * 60) + (SS)
Thank you,
Kind Regards,
Simon

You should use the Get Date/Time in Seconds VI which will return a timestamp. You can then format this timestamp using the Format Date/Time String to give you exactly the time format that you need. Then you can extract the numbers you need and do your math.
www.movimed.com - Custom Imaging Solutions
Attachments:
Get Seconds in Day.vi ‏9 KB

RT cRIO: Shared Variable Engine Errors

This is an app written in LV2011 running on a cRIO-9076 (Scan mode), with the August release of software installed on it.
I have gown to great lengths to try an optomize my code, I have reached an impasse. The VERY FIRST TIME I run the code on the target (be it via a self-starting EXE or targeting from my Windows development machine I am able to read and write to several shared variables, but then when I access them again (possibly when I am starting a couple timed loops and the processor is very high) I get this:
Error -1950679023 occurred at Shared Variable in targetIdleLoop.vi->ZDAQ_cRIO_Target_Main.vi
Possible reason(s):
LabVIEW: (Hex 0x8BBB0011) The connection to the server was disconnected.
This error or warning occurred while writing the following Shared Variable:\\ZeeAero-RIO1\variables - network - RT (separate)\RTStatus\\10.10.10.10\variables - network - RT (separate)\RTStatus
If I go back to the Dev machine and restart the code, I don't get this error; it only happens after a reboot.
BUT on this second run (or subsequent VI starts), when we get to that same point, a client priogram running on Windows and reading a network variable successfully suddenly gets:
LabVIEW: -1950679035 (Hex 0x8BBB0005) Unable to locate variable in the Shared Variable Engine. Deployment of this variable may have failed.
Which lasts a minute or so, then goes away. The code is made to loop, and when it loops back through this point there are no errors at all.
So, to recap:
1st Run after reeboot, 1st loop :Error on Target (0x8BBB0011), connection to server disconnected
Subsequent Runs, 1st loop: Error on Windows Client (0x8BBB0005) Unable to locate variable in the Shared Variable Engine. Deployment of this variable may have failed.
Subsequent Runs, 2nd+ loop: No error
Here is a link to a screenshot of the installed SW on the Target:
EDIT: I should mention that there are three loops running in parallel on this app; 1 is a Timed-loop (at the moment) set to a period of 10ms with 100 priority, #2 is also a timed loop and is set to 3ms with priority = 50 and the third is a WHILE loop with a 50ms wait. The error occurs during the WHILE init phase, which happens once per run, not repeatedly.
Solved!
Go to Solution.

This is killing me. It's obviously something to do with when the Timed loops start AND when I access the network variables.
See the screenshot below.
Note that I read and write to several network variables in Subroutines to the left of this screenshot at startup. The starting of the timed loops causes the issue with the shared variables. (also note that the periods are set to 100ms and 99ms in my testing after the initial 1st loop.
Now look at the Wait at the bottom set to 10 seconds. In this case, it will work. There is no error at breakpoint 37 if I wait around 10s. If I DON'T wait the 10 seconds, there is an error after the check on the BOOL "stop - Network" variable that NEVER GOES AWAY. If I look at the CPU monitor, there is an initial bump in the cpu when starting the loops, and then it drops to about 15%. But if I don't have that 10s wait, there is ERR 0x8BBB0011 and the CPU spikes to 75% every 5 seconds and it never goes away.
And that's only the 1st loop after reboot. The 10s makes this work, but I still have an issue with it once I start doing individual runs (loops).

Installation improper cRIO 9076

Similar Messages

Maybe you are looking for