DQMH-CML in RT: is there an example project available?

[maurizio.bollini]

Hi to everyone,

I'd like to open my eyes on future RT applications using DQMH: is there an example CML project available ready to use?

Cheers,

Maurizio.

[FabiolaDelaCueva]

Hi Maurizio,

I don't know of an example readily available.

You should be able to use culpable DQMH modules in RT with no change. There is a menu option to create an RT API Tester because although user events do work on RT, there is no UI on RT and no user interface events work.

Alternatively, you can take a look at what Joerg did with the Hampel DQMH Networking module. 

Regards,

Fab

[maurizio.bollini]

Thanks Fab,

I'll go through in details on a RT example my own and through the great Joerg's networking module.

See you at GDevCon #2 workshop and conference.

Regards,

Maurizio.

[Shuggy1]

Sorry I know this is an old post....

I am struggling doing the same thing.

Will the CML example modules port straight over to the RT.  The reason I ask is they are Singleton modules. There is a fair bit documented that cloneable modules should be used on rt, but then has this changed on later DQMH updates. Even the current documentation contradicts it's self, suggesting you can use singletons on RT but use the API tester with it.

https://documentation.dqmh.org/dqmh/7.0/DQMHinLabVIEWRealTime.html

I am using DQMH 7.0.

[joerg.hampel]

Hello Shuggy1,

thanks for giving DQMH a try!

You can read up on the history of DQMH on RT in our Dokuwiki. In a nutshell, a bug in LabVIEW prevented DQMH 4.x and earlier from working correctly on RT. With DQMH 5, Delacor changed the way the modules are launched, so from then onwards both Singleton and Cloneable modules are supported on Real-Time targets.

I'm sorry that the documentation seems ambiguous to you. What we mean to say is that for DQMH 5 and later:

1. You can execute Singleton and Cloneable modules on RT systems, both with or without Embedded UI enabled.
2. LabVIEW Real-Time does not support Front Panel Controls events if no embedded UI is enabled, so regular API Tester "Value Change" events would not work. DQMH includes a tool for creating Real-Time-capable API Testers.

Could you maybe help with finding a better wording? How would you think this should be phrased?

As for the CML project, I will leave it to others to talk to the extent of portability. At the very least, the API Testers are not designed for use on RT without Embedded UI, so you need to create the RT API Testers first. The application itself is designed to run on Windows, and you operate it through its UI, right? That will not work on RT if no Embedded UI is enabled.

Hope that helps!

[Shuggy1]

I'm sorry I got no notification of your response. 

Thank you for your response the wiki page was great and does explain it. 

DQMH is great I am a convert and have just finished my first app using it, (I'm sure I still have a lot to learn.) thank you for all the online help everyone!

The section of the documentation that confused me was in the 'DQMH API Tester for RT',  where it still states ...

"

* DQMH Module API Tester for RT only works for Cloneable DQMH modules.

Singleton DQMH Modules do not work in LabVIEW Real-Time running in Linux operating systems. There is a bug in how VI Server works in Real-Time for Linux resulting in the Ctrl Value Set invoke node used inside the Start Module.vi to not working. We decided to only support DQMH cloneable modules in LabVIEW Real-Time.

"

https://documentation.dqmh.org/dqmh/7.0/DQMHAPITesterforRT.html 

I think this is out dated and left over from before v4.x. I think it can be removed? 

With regards to the CML after trying It does port across as you expected. I was after a headless application with UI to check it was operational and this was easily achievable.

Regards