Web Service Remote Control in 2023

[Stephan.Bormann]

Hi there Community !

I am using LabVIEW 2022 Q3. I am new to Web Hosting.

I want to remote control a VI via Web Host Service in 2023. But the "embedded" Viewing Mode is not available anymore.

THE VI is based on a Queued Message Handler and should allow students to remotely control a test bench and measure data.

The official documentary updated on july 2022 does show it, available here: https://knowledge.ni.com/KnowledgeArticleDetails?id=kA03q000000YHeGCAW&l=de-DE

but another article says, it disappeared too. I couldn't find any information on this on NI Sites.

What options other than "converting to NXG G Web" do i have within LabVIEW? I am unexperienced with Java.

Thank you all in advance.

[MilanR · Accepted solution]

---

What options other than "converting to NXG G Web" do i have within LabVIEW? I am unexperienced with Java.

---

The How to Build a Web UI for Your LabVIEW-Based Test System presentation covers step-by-step approaches for incrementally adding G Web Development Software support to an existing LabVIEW application. It does require creating a new web-based interface using G Web Development Software and making changes to the LabVIEW application to communicate with the G Web application.

For most scenarios you should not need JavaScript knowledge to use G Web Development Software, that's only needed if you want to extend the functionality of a G Web application with new plugins and features beyond what is included.

[IlluminatedG · Accepted solution]

https://github.com/illuminated-g/lv-sl-gweb-demo

Following on from Milan's comment, here's an example that demonstrates using SystemLink messaging APIs (SystemLink server not required) to communicate in both directions. NI's video only shows sending a single numeric from the LabVIEW app -> Web app using tags but is otherwise a good overview if you're unfamiliar with G Web.

This demo is a very small example showing adding the ability to publish values to be accessible to web apps as well as accept commands from web apps to interact with the local app. Both the local and web apps have similar UIs (Web app needs to be created from scratch, there's no migration from LabVIEW to G Web) and the web app is basically a "thin-client" for the LabVIEW timer app. With the QMH template there is practically no changes needed for the existing app logic and most of the messaging is added on as an additional loop that uses the QMH to drive the existing functionality.

[IlluminatedG]

And since the request was "other than G Web with LabVIEW"... nothing else from NI.

You can either use G Web for a more familiar development experience which works well in this use-case, or just build a completely separate web application with your web frameworks of choice (or none) and update the LabVIEW application to include Web Services and/or WebSocket capabilities to be able to access/control from the separate web app.

[Stephan.Bormann]

Thanks a lot for your time & knowledge !

I think i will try G Web then 🙂

Does anyone know why they changed it ? It seemed so easy to implement and now it feels far more complicated.

[IlluminatedG]

It relied on a software package that was deprecated by Microsoft and isn't supported in modern web browsers.