LabVIEW Real-Time Idea Exchange

About LabVIEW Real-Time Idea Exchange

Have a LabVIEW Real-Time Idea?

  1. Does your idea apply to LabVIEW in general? Get the best feedback by posting it on the original LabVIEW Idea Exchange.
  2. Browse by label or search in the LabVIEW Real-Time Idea Exchange to see if your idea has previously been submitted. If your idea exists be sure to vote for the idea by giving it kudos to indicate your approval!
  3. If your idea has not been submitted click New Idea to submit a product idea to the LabVIEW Real-Time Idea Exchange. Be sure to submit a separate post for each idea.
  4. Watch as the community gives your idea kudos and adds their input.
  5. As NI R&D considers the idea, they will change the idea status.
  6. Give kudos to other ideas that you would like to see in a future version of LabVIEW Real-Time!
Top Kudoed Authors
User Kudos Count
1
Showing results for 
Search instead for 
Did you mean: 

Add console to Linux based cRIO

Hi !

With the linux-based cRIOs the console ("Write To Monitor" ; as intended before working with VxWorks/PharLaps OS) disappeared.

It's only possible to have strings pushed to the RS ports or in a (not managed) file.

 

As many cRIOs are connected to the network, it would be nice to have the "Write To Monitor" console access through Ethernet port.

The idea would be also to keep the global functionnalities of this console : see the strings in the cRIO webpage (of course), but also keep strings in a managed file (max number of logs in a file, ...) to have a 'buffered' access to strings sent to the console...

 

In brief, bring us back the 'Console' !! :smileyhappy:

5 Comments
Member MSTB
Member
Yes that would be great ! I feel the same frustration about the "disappearance" of that service... :'(
Member ScotSalmon
Member

We've gotten this request a couple of times now, it makes a lot of sense. Can you clarify whether you specifically want the "WIF console" which would make it like VxWorks cRIO's where your options are serial or the web interface? Another option we could look into would be ways to get console messages on an ssh connection. Assuming "all of the above" is not an option (maybe it is, but if you had to pick) would console messages on ssh be better, worse, or equivalent to the WIF console? Are there specific console messages you care more about? It might be easier, for example, to redirect only the RT Debug String "Write to monitor" output, versus showing all console output such as boot messages. Some in-between options exist, for example, redirecting all LV output ("Welcome to LV", LV error messages, etc.).

 

Active Participant zyl7
Active Participant

Hi ScotSalmon,

 

I don't care if the console can be seen in a web browser or through a specific client with ssh connection. I just want to see strings that I push with 'Output Debug String (write to moniotr)'.

The best would be to only see 'Output Debug String' strings in a web browser (ease of use, everybody as a browser installed on its computer), and be able to see more messages (such as boot messages, etc...) using a specific client (like Putty for example or any other client).

About security, I guess that it is not necessary to apply SSH encryption to 'Output Debug String', because these are strings I intentionnaly want to output from my cRIO. Or give the option to choose between SSH and 'clear' communication from 'Output Debug String' VI could be a good idea... But this security option is not something I strongly need.

 

Just to let you know, I made a very simple webpage to create my own webconsole. I push strings through WebSocket (masked data, securized communication through WSS:\\ ) from my cRIO to any computer asking for a connection.

The webpage is 3Ko big and WebSocket allows pushing strings quite fast and very efficently (efficient on cRIO and on computers). So if I made it, I think that a team of professionnal can do it even better and deliver a very useful tool to end-users. Smiley Wink

Member Deborah_B
Member
Status changed to: In Development
 
Active Participant JoshuaP
Active Participant

I really like your usage of WebSockets.  It is a great technology that enables asynchronous communication with very little overhead on the target.