DQMH Consortium Toolkits Discussions

cancel
Showing results for 
Search instead for 
Did you mean: 

Integration of IG Streams & Messaging with DQMH

It's been suggested I look into/create examples of my messaging APIs with DQMH: https://github.com/illuminated-g/lv-msg-simple/issues/5

 

BLOT: Who sees a need for more remote communication options with DQMH modules and integrations of DQMH modules with Web UIs such as G Web and others?

 

I see that there's a Generic Networking Module available for servicing remote requests but of course this is for DQMH <-> DQMH messaging. If you're unfamiliar, my stream-based APIs are a more abstract library with a separate messaging layer. It has stream implementations for files, in-memory, TCP, WebSockets, and if you really wanted to you could even use it over Serial/VISA. In particular, the WebSockets implementation provides an opportunity for cleaner integration with web-based UIs. As the messaging layer uses streams abstractly, it's also possible to mix & match stream implementations to provide capabilities such as having both TCP connected clients and WebSocket connected clients to the same application (Basic example package https://www.vipm.io/package/illuminatedg_lib_ig_websocket_&_tcp_messaging_example/ )

 

Is this something that sounds worth pursuing? Is there anyone that's looked into web UI integrations yet? I'm familiar with the DQMH pattern and module architecture  but less familiar with the tooling and how much effort it would be to integrate with the existing tooling or provide a similar level of tooling to users of DQMH. I'm thinking a good first demo would be exposing a G Web remote UI for the thermal chamber example but let me know what other good example ideas there are as well.

 

I'm happy to implement the integrations though I'll have some questions around architecture design & best practices, e.g. whether or not to implement a top-level connection management module that itself provides a DQMH style API to managing the connections or if it's fine to directly consume the streams/messaging API directly from higher level "app" modules and the integration just wraps up the message handling to transcribe broadcasts/requests.

~ The wizard formerly known as DerrickB ~
Gradatim Ferociter
Message 1 of 5
(1,162 Views)

Hey Derrick, thanks for reaching out. This sounds extremely useful and interesting. I think we should schedule a meeting to talk this through. I will reach out to you directly. 




DSH Pragmatic Software Development Workshops (Fab, Steve, Brian and me)
Release Automation Tools for LabVIEW (CI/CD integration with LabVIEW)
HSE Discord Server (Discuss our free and commercial tools and services)
DQMH® (The Future of Team-Based LabVIEW Development)


0 Kudos
Message 2 of 5
(1,145 Views)

Wow! It's great to see this topic Derrick!, so interesting.

0 Kudos
Message 3 of 5
(1,129 Views)

I think this is worth pursuing.  This is going to be required more and more.

 

We have dabbled in this space a bit too - we have developed DQMH modules that leverage Simple Messaging, as well as other modules that use MQTT, and HTTPS (web services).

 

Sounds like this is related to your recent GLA Summit presentation Derrick - something I have on my watchlist but yet to do!

Christopher Farmer

Certified LabVIEW Architect and LabVIEW Champion
DQMH Trusted Advisor
https://wiredinsoftware.com.au

Message 4 of 5
(1,099 Views)

For anyone interested in joining in on architecture discussions https://github.com/orgs/illuminated-g/discussions/1

~ The wizard formerly known as DerrickB ~
Gradatim Ferociter
0 Kudos
Message 5 of 5
(1,044 Views)