Jump to content

Search the Community

Showing results for tags 'browser'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Software & Hardware Discussions
    • LabVIEW Community Edition
    • LabVIEW General
    • LabVIEW (By Category)
    • Hardware
  • Resources
    • LabVIEW Getting Started
    • GCentral
    • Code Repository (Certified)
    • LAVA Code on LabVIEW Tools Network
    • Code In-Development
    • OpenG
  • Community
    • LAVA Lounge
    • LabVIEW Feedback for NI
    • LabVIEW Ecosystem
  • LAVA Site Related
    • Site Feedback & Support
    • Wiki Help


  • *Uncertified*
  • LabVIEW Tools Network Certified
    • VI Scripting
    • JKI Right-Click Framework Plugins
    • Quick Drop Plugins
    • XNodes
  • General
  • User Interface
    • X-Controls
    • Custom Probes
  • Database & File IO
  • Machine Vision & Imaging
  • Remote Control, Monitoring and the Internet
  • Hardware

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start



Personal Website

Company Website

Twitter Name

LinkedIn Profile

Facebook Page



Found 2 results

  1. Hello LAVA. Here's an idea for those interested in browser-based monitoring of cRIO-9068 performance. A few years ago I developed the collectdViewer system as a demonstration to the "DevOps" community of the benefits of using WebSockets for server monitoring. Operation of the system is quite simple conceptually: The system uses a collectd daemon (http://collectd.org) to monitor the performance parameters (eg CPU, memory, network activity) of a Linux platform. This performance data is then sent via a message broker and a WebSocket connection to a browser for display. The WebSocket connection to the browser enables a display update rate of 2x per second and as a result, it's possible to observe short transient phenomenon in the behavior of a server. For example, attached is a screenshot of collectdViewer monitoring the performance of an EC2 instance during various system load tests in a 60 second period. The high update rate also make it possible to observe phenomenon such as the network activity associated with serving a single web page or the CPU usage of the login process. Since the cRIO-9068 uses NI's Real-Time Linux operating system, it seems that it should be possible to use collectdViewer for browser-based monitoring of this platform as well. If you'd like to try the system yourself for this application, more information and a downloadable demo are available at: http://collectdviewer.com. Let me know if you need help with setting up the demo system to monitor the performance of your cRIO-9068. A few of other notes: 1) The downloadable demo of the system at the above link uses a message broker hosted on my cloud server. If there's interest in using this system for autonomously monitoring your cRIO-9068, I can create completely standalone systems for a modest fee. These systems would include a Virtual Machine that hosts an HTTP server and message broker and can run on a PC, Mac or Linux platform within your LAN. 2) The video at the following link shows the use of collectdviewer for monitoring and studying the transfer of data from the (recently defunct) Nirvanix Internet File System to an EC2 Server: http://collectdviewer.com/applications.html#monitoring_cloud_storage_data_transfer. 3) It would be feasible to incorporate the display of values of LabVIEW variables in the collectdViewer plots. One way to do this would be to use the STOMP library that I developed for the LabSocket system to send LabVIEW data to the message broker of the collectdViewer system. This idea is somewhat half-baked at this stage, but I thought I'd put it out there in case anyone had an interest in it. Any thoughts or comments are welcome. PS - Apologies for not including live hyperlinks in this post. It appears that the forum editor software is blocking these links for some reason. -John jbergmans // at bergmans // dot com
  2. Here is a simple .net (C#) application designed as a special web server. It controls any application running on the server via a remotely connected mobile or desktop HTML5 compliant browser. Prerequisites for testing this "Proof of concept application" 1) Install the .Net runtime. I normally use version 4.0 2) Create a directory and unzip all the files. The steps you need to follow to run the application are: a) Start the application you wish to control - say a Labview VI screen b) Run the web server executable in the attachment. c) You should now see a screen as shown below. d) Select a suitable port that clients can use to "talk to" the web server. By default it's 4444. e) Select your VI application from the list of windows shown. In case your application does not show up in the list press the button "Refresh window list". f) Press start to start the web server. You should get a message saying "waiting for a connection " g) The screen shows the url that you need to type into the browser h) If things go as planned the window you want to remote control now shows up in your browser i) If you have a touch sceen then you can simulate a mouse click in the usual way-touch the screen. j) If you need to add text to a control on the VI or any other application you have a text box above the window in the browser screen where you can type out the relevant text using the mobile's keypad or desktop keyboard. You should then tap or mouse click the area on the screen where this text is to be inserted. Note: This application is not a "commercial grade" application - you may get minor errors. You are free to decompile, reverse engineer and use it for whatever purpose you choose. Source code is not included. Colin Rebello [ colinrebello@hotmail.com ] Zip of executable.zip
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.