Connect to terminals to cRIO target

I'm new to LabVIEW Real-time and not become familiar with all the tools available in 2009.  I make changes/improvements to an app developed by another engineer under 8.x.  As a result of the upgrade, our application is no longer working properly.  I tried the VI's instrumentation to manipulate the User1 LED as an indicator, but nothing happens.  I'm used to having a mechanism for terminal connection in the target.  For example, in the past, I used WindView with VxWorks for the same reason.  However, I did not have a license for the Wind River developer tools now and don't even know if this version of VxWorks (in LabView) supports WindView.

My question: is there a combination of tools and the configuration of the target to get a terminal connection to the target OS (not only the output of the console on the RIO RS232)?

Hi deepforge,

The console feature on CompactRIO is not unidirectional.   Visitors of most National Instruments are not familiar with the underlying interfaces of VxWorks, but when you use Hyperterminal or another Terminal console series, you can type commands in the Console VxWorks.  For example, if you think that your application does not load, you can use the 'moduleShow' command to display the modules loaded on the operating system and the command "ld" to load your application manually.  It is useful to activate the function "echo" on the terminal that you can 'see' what you send to the console.

The console of feedingstuffs should also indicate a status that your application is trying to load.  Get you an indication that demand starts to load and do not?

Your startup application using the serial port?  Small chance of this being your real problem, but I'll throw it out there.  I've seen startup applications in the past who did not attend work because the Console on the feature is enabled, but demand is tryting to write to the serial port.   Unless errors are handled properly, an error Stops series could be the cause of your application to behave unexpectedly.

Kind regards

Tags: NI Hardware

Similar Questions

  • Unable to connect to a real-time target... ugh I give up!

    This one is really frustrating... I did a lot with Labwindows for a long time, so get in... I just installed LW/CVI 2013 on a new machine in my lab.  hooked to a new PXI chassis, formatted a new disk in and installed all the drivers.  When you try to connect to the target environment labwindows I get the popup in the screenshot.  As you can see, the chassis is on the network, to the good ip, and the drivers are installed on the target... What is the problem!  Thank you.

    Hello

    This is the acutally NOR Configuration system that comes with MAX and interferes during the installation of the CVI real-time on the target.

    Decommissioning of MAX should solve the problem.

    If you don't want to upgrade to CVI real-time Module to 2013 SP1 there is also a work around:

    Edit C:\Program NIUninstaller Instruments\RT Images\CVI\version\cvilvrt.cdf and do one of the following:
    Remove the entry from CVIRealTimePeer.
    Specify the IP address or desired host name.
    Reinstall the LabWindows/CVI runtime for RT component to the target via NI MAX.

    Good day

    Constantin

  • 8.1 non-accessible Windows computer enterprise network error is failed to connect on behalf of the target is incorrect. other computer os is windows 7 Professional

    I want to share the printer in win 8.1 computer but when search this computer from another computer that there is error is connection failure target name is incorrect. I turn off the firewall on this error also but even the computer.

    Hi Shilpatel,

    Thanks for posting your query in Microsoft Community.

    According to the description of the issue, I recommend you post your query in the TechNet Forums. TechNet is watched by other computing professionals who would be more likely to help you.

    TechNet Forum

    http://social.technet.Microsoft.com/forums/Windows/en-us/home?category=w7itpro

    Hope this information is useful.

  • How to day/change the descriptor of connection to a database to target CARS in Cloud control

    I have Cloud control 12 c than Release 3 implemented and followed by many hosts and targets. However when monitoring my RAC (2 knots), it cannot connect to database instances (although it shows them only up to). I get the message "IO error: the network adapter could not establish the connection. I see that the connect descriptior using vip, rather than the host name.

    How can I update the connection descriptor in Cloud control to the correct values?

    Change the following configuration control listed below note

    How to change/update Configuration of the analysis of a target database or the listener in 12 c Cloud Control (Doc ID 1385769.1)

  • Build table - you have connected two terminals of different types

    Hello, I'm getting my vibration sensor data using my USB 9171 cdaq and the NI 9234. I want to display the signal of vibration, to record in a file, to do all kinds of possible statistics and the display of the statistics table on the front in update mode, attached is my VI based on some examples in the finder of the example, it has an error, can someone help me to make it work. Thank you very much in advance for your collaboration. Ihab

    Change the table build to add entries instead of concatenate.

    Lynn

  • Different behavior between cRIO 'Run as Startup' and debugging run

    Hello

    I have an application that does a lot of things, including playing a card NI 9213 Thermocouple, which lies on a connected to a RT cRIO target expansion chassis. The application is run on the target of RT. My problem is related to a behavioral difference between opening a connection to the channels of thermocouple in debug (by clicking on the arrow on the VI run) mode and the opening of the connection through a Build specification (by clicking Run as to start).

    During execution, the VI wrote in a text file on the hard drive of the cRIO. I enclose the text files, one of the debug mode and a Run as startup mode. I have only two thermocouples connected (ch1 and ch15). From the text file, you can see the connection opens without error in debug mode, but get an error in startup mode. I've also attached an extract showing the VI that I used for the test.

    A few notes:

    Nothing to do with the VI is changed between each type of race.

    The Build specification has the attached VI selected as startup VI, everything else is default

    Someone else out there has had a problem similar to this? I feel like the debug mode should act identically to the normal start deployment. Otherwise, what's the point?

    Thank you

    I solved the problem! Or at least worked around it by setting a different bug. This another bug happened to be the same words that were this bug, to run as a startup. I'll summarize for you:

  • Cannot make connection IP cRIO more

    Short version: connection of Ethernet to my cRIO but suddenly become unstable, and I can't connect at all now.

    I'm working on the cRIO code for a client and try to work remotely. We had problems getting the deployed code to run (see http://forums.ni.com/t5/LabVIEW/Real-Time-Application-doesn-t-run-source-code-works-fine/m-p/3106679 for more information on this), but this seems to be a new problem, so I thought I would start a new thread to avoid confusion.

    It was impossible to troubleshoot remote, so I convinced the customer to ship the cRIO for me. Packaging is intact, the unit was well packed, so I'm skeptical that it has been damaged during transport, but something is happening.

    I started working with it using a direct connection cable between my laptop and the cRIO. All was well for about an hour; then things began to happen. The debug console (in the project window > Operate > Application Debug or Shared Library...) ('') was unable to find an executable file that can be debugged even if he had worked a few minutes before. I restarted the RIO through the project window (right click on the target > utilities > restart) and after a bit but I got a message "an error occurred while trying to restart the cRIO target. Power to bike. Tried to deploy the RT again, but he failed because the cRIO has failed.

    I tried all sorts of things over the next hours. MAX sees sometimes and sometimes does not. Even when he sees MAX, it tells me that there are no network adapters. Network properties and "ipconfig" sometimes show the port is connected and sometimes not. Ping Gets a response packet about 25% of the time, but the other 75% say "destination unreachable".

    I tried 4 different cables, crossover and the patch. I connected the laptop to another computer and ping 100 packets without problem, it isn't my port. I checked my IP address and the subnet. I have disabled the firewall. Power of many loading cycle. Starts the RIO in Mode safe. Switch used the 'IP Reset' but MAX can't connect long enough for me to give it an IP address on my subnet. Changed my IP port to a static address on the subnet 169.254.184.X (which is the subnet by default as it IP Reset puts on) but I have the same erratic connection. Forced half-duplex by http://digital.ni.com/public.nsf/websearch/FD24D98FF428F21686256B64007FB6C1). Reset the MAX database by http://digital.ni.com/public.nsf/allkb/2C7480E856987FFF862573AE005AB0D9?OpenDocument.

    Nothing works. If anything it gets worse. My guess is that the cRIO has a hardware fault in the IP port. The other port is disabled, and I can't connect long enough to enable it.

    I point out that I worked directly with the cRIO also uses this same computer during one week in February so all my drivers, etc. should be fine.

    Suggestions?

    There that weird looking messages sent on the port series with the DIP switches game console?

  • How to deploy target (Crio) shared variable configured RT chassis, NOT of LIBRARIES

    I have a PC, connected to a switch RT target (Crio) THROUGH 5 port host.

    I want to be able to run a program on the host computer, that will load and run a RTexe on the target of RT.

    However, I want to be able to load and run different RT exe, which have different chassis configuration variable. Scaling, PWM DIO, ect... may be different from one program to a program for different channels.

    I know how to deploy libraries, but how do I Deploy/undeploy the chassis configured static variable?

    Hi teslaaaa,

    The attached photo, it seems you're looking for your e/s Scan Mode programmatically. We have a white paper section that deals here. The first section of the article discusses discovered by program your I/o modules, which you will get a reference to your modules. Then you will be able to configure the modules with nodes of this reference property.

    Let me know if it helps!

  • Call to a shared library a VI on a target NI Linux RT (cRIO 9068)

    Hi, I wrote a very small shared library (.so) with Eclipse (toolchain 2014), which essentially serves as a wrapper for more complex, but I am having problems with the call go to in LabVIEW RT on a target Linux RT - specifically, the cRIO 9068. First: the library was copied in/usr/lib and ldconfig has been correctly implemented. More important yet, I have also written a C program (using Eclipse as well) that calls the single function currently implemented in the shared library: this works perfectly, both in Eclipse and you connecting directly on the cRIO with a Putty terminal. So I guess the shared library itself is ok and can be called from code/external programs. Now, dating back to LabVIEW (2014 here btw). Here's where things get difficult, I guess. Initially, I had the symptoms listed here--> http://forums.ni.com/t5/LabVIEW/How-to-create-a-c-shared-library-so-for-linux-real-time-for/td-p/302... who prevented me from actually run any code on the target of RT. Then I changed the call library function node: various tutorials suggest to put name_of_library.* in the path text box or the name of library, but unfortunately it doesn't seem to work, so I had to put the name and the extension too. But it still produces the error below ("the name of the function is not found" etc.) So I check the box 'specify path on diagram' and add/usr/lib as a parameter to the node library function call: now the VI can work and is actually transferred to the target of the RT... but the cluster of output error returns error 7, which is a kind of "File not found" error. However, I believe that this error message is misleading: indeed, if I try to debug remotely this library shared under Eclipse, I am actually able to pause it. and when I press the Pause button on the debugger, the goal of RT VI pauses, then continues as soon as I press the Resume button, I'm stuck... I tried searching forums and Google as well, but I have not yet found a solution. Any ideas on what's going on? Moreover, I can add more details if needed.

    Problem solved, it was a bad configuration of the node library function call which prevented the actual library (.so) to be called.

  • cRIO 9082 - cannot connect through NI MAX/LV

    Hi all

    I am writing my bachelor on the dynamic memory and the vibration tests.

    The project I design an experimental platform used to excite some mechanical components.

    We need several sensors (MON, accelerometers, DC motors etc.), we use a cRIO 9082.

    However, when I want to connect to the cRIO I can't OR Max, that is I can't set it up. I can see it only in the browser OR (see photo).

    I am connected directly to the cRIO via a crossover cable and IPv4 is set to automatically assign the IP address.

    Any ideas of how I properly connect to the cRIO 9082.

    I'm new on the job with this kind of electronic products, since I am majoring in mechanical engineering - so please keep the explanations as simple as possible ;-)

    If you want more details, please let me know.

    Thanks in advance.

    JZaulich.

    Hi Alex,

    Thank you very much for your answer.

    I had to disable the Windows Firewall as well as the AVG firewall, that did the trick.

    Apparently Windows does not allow this type of connection.

    After you turn off the firewall, I added the cRIO using the IP address, and it seems to work very well.

    Thanks again.

    Best regards

    Jakob Zaulich

  • Access denied error connecting to the target RT

    Hello

    I use LV2009 on a desktop host and RT 9 on a target PXI.  I can connect to the target through the project with the original target embedded sw Explorer but cannot access the modules of IO MAX due to a driver version (DAQmx) inconsistancy between the host and the target.  When I install the DAQmx 9.3 drivers on the two systems that I can connect and access as the target I/O via MAX modules but cannot connect to the target through the Project Explorer.  I gives me an IP address in the host not to mistake of authorized access list, even if I've added to the list of users under properties of the target. Something in the DAQmx update is complete my ability to connect through the Project Explorer.

    Any help would be appreciated,

    Thank you

    Dave

    Hi DDockery,

    Our objectives of RT keep record of system information in a file named nor - rt.ini

    We do not suggest edit our files nor - rt.ini if you are not similar with them.

    Important lines in the ni - rt.ini follow the lines:
    Server.TCP.Access = "' + * '"
    RTTarget.IPAccess = "' + * '"

    '+' * means that each IP address can access

    If you have any more specific questions or unconfortable editing the .ini file please contact Supportm technique of NOR, create a Service request and an Applications engineer can help out you.

  • VISA connection terminals

    Hi all

    I wanted to take over the existing application on the forum "Fact Serial Port operation," but I could not connect the two terminals of the VISA. the error message is 'you have connected two terminals of different types.

    can someone tell me how adapter a table 1 d of class session to a receiver of type session of class visa.

    Thanks, JB

    on your recommendation, the connection is made and thanks again.

  • published RT cRIO-9030 with network-a project of shared variables cannot communicate with host VI when compiled and deployed as executable startup.

    I have a project including a VI RT running on a cRIO-9030 and a host VI running on a desktop computer.  The two programs communicate via shared variables that are hosted on the cRIO.  As shows, when I run the screw of the project, everything works as expected.  When I compile the RT VI in a start-up executable can deploy for the cRIO, as well as the libraries of shared variables (the record of support in the build specification-oriented), I am unable to connect to the executable running in real time.

    I have 'Disable Autodeploy Variables' checked on the cRIO target, if I no longer get the prompt to stop the currently running application to deploy the variables.  The host VI opens and appears to run, but has no connection with shared variables (data does not update).  Compilation of the host VI as an executable file and it works outside the project result in the same behavior.

    I read some relevant posts / knowledge base articles related to this problem, but still can't seem to find a way around it.  I note a number of articles on the series in double bond of variables, but this is in contradiction with my possible behavior for this system: I finally have a number of cRIO controllers identical all runnning the same executable RT and want to be able to have a single host VI which allows the user to select from a list of available controllers (using the screw system configuration) and extract the host name of the controller selected, that would be later used for programmatic addressing of the variables on the host of part VI.

    In any case, I want to start with the simple fact of being able to get that first controller running without an open connection to the RT VI project.  With the deployed executable start, I checked via programmed behavior of LED application of the RT and FPGA are running on the cRIO.  The problem, I think, has to do with shared variables, but I'm not sure where to go from here.  I want to connect to RT executable running from the VI to the host (in project) to verify that the compiled executable of RT works as expected and then the subsequently compile host VI in an executable that can be run from any desktop on the local subnet.

    Thoughts?

    It seems that the error has now been corrected.  There were three things, I changed: the file startup.aliases in the startup on the target directory (Home: / lvuser/natinst/bin) put in 'localhost' as an alias for the controller.  I changed it to the IP address of the controller.  Then, I got some features of IO files in my application RT relative paths using the path obtained by the 'current path VI' VI.  As this path changes according to the location / delivery system, I had to create a VI that has used the Application property: type with a case properly structure band / build railroads desired regardless of the runtime system data files.  This may have broke my RT request.  Finally, I got a property node in one of my RT SubVIs, who attempted to change an indicator in the Subvi, which is not taken care of in an RT compiled executable.  I can't do this for debugging purposes somewhere along the way, but in any case, I removed it, and after a recompilation and the deployment of the executable of RT, everything seems to work as expected today.  The host VI on the desktop can connect to the application of the RT project, and when it is compiled into an executable file, which also works.

  • Indicator how to Panel on update of the target by target pc rt code?

    Hello

    I use a desktop as a target Rt PC.

    Using the shared variable, I can see the settings in the target.

    Another way to see parameter is to set an indicator in the control panel front of target code.

    I would like to know how this indicator updates?

    Which method is more efficient (that is, it causes less target the CPU usage)? Shares of variable or an indicator in the front panel of the code target?

    Also, I would like to know is there a way to see the front of the target code in the monitor which is connected to the RT PC target?

    Thanks in advance

    This white paperexplained a bit more including the integrated HIM available on newer cRIO controllers based on Linux

  • Support of IP camera OR cRIO

    Hello

    I work with a cRIO 9022. Also, I have a camera (Panasonic C210A) based ethernet. Should be power thanks to its converter. The converter has received 2 slots for LAN and Ethernet cables are such that we're going to the camera and we're going to the cRIO and the camera has power through the converter using a 9V adapter.

    Now, when I create a VI under the target (cRIO) and try to search for the IP camera you want (either not sure if it's IP camera or not), it does not appear in the Vision Assistant under vi. I have the drivers for this webcam is installed on the HOST PC. However, these drivers are not installed on the cRIO, target. I don't know if the drivers can be installed on the target also in some way. (Should the host files be transferred to the target using the FTP Client for installation)?

    The slot of the ethernet on the cRIO got 2 LEDs above and below the ethernet cable. They both turn green when I connect the camera. But I can't find the camera when I use Vision Assistant.

    Can someone help me with this problem?

    Amar Makana.

    Hi Amar,

    Let me begin my comments by saying that you should post this question hereon the discussion Multifunction DAQ board. Our monitors applications group our forums and you should get feedback from a supporter of the acquisition of engineering data. In addition, you will probably get a response from our very large forum community. You probably wouldn't get a community response to your question of 6216 on this thread, as it is classified as machine vision.

    That said, it is difficult to say what might be causing these jumps of waveform without knowledge of the type of signal being monitored. When you post in the thread of data acquisition, you must include a description of the signal being played and more screenshots you mentioned. However, since you mentioned that N-samples worked, but continuous has not, that leads me to think that the size of the read buffer should be increased. When using low level DAQmx screws, you can specify the size of the read buffer, which allocates a certain amount of memory the computer to play the samples in your DAQ hardware. Then, whenever a loop containing playback DAQmx runs, it will take as many samples out of the buffer. In addition, depending on the type of signal and the number of signals during playback, you might see sampling aliasing is not fast enough, or multiplexing by mistake as the 6216 does not support simultaneous sampling. Here are some things to consider, and I encourage you to mention in your post of data acquisition.

    I hope this helps!

Maybe you are looking for