DQMH clonable module plugin

[Eztainu]

Hello everyone,
I’m relatively new to DQMH, so my question might be obvious. So far, I’ve only done simple things with it. But this time I’ve got a bit ambitious:

I’m trying to create an application that programmes a series of cards. I have different card models, and each one is programmed using a different sequence. The number of models is expected to keep growing in the future, and we’d like to avoid having to recompile the application every time.
That’s why I’ve thought of creating a plugin-based application. The application will detect the card model and dynamically load the corresponding plugin. So far, so good – there are various tutorials that explain this.
The problem is:
1- The programming process is complex, to such an extent that the option we’ve considered is to use a DQMH module as a plugin. This would automatically generate the tester for us, and we could have a state machine within it…
2- We want to programme cards in parallel, so it would be useful if this DQMH module were cloneable.
From the techniques I’ve found for creating plugins, I don’t think they’re compatible with a clonable module. The ‘Multiple Instances’ folder cannot be inserted into a class.
Do you know if it’s possible to do something like this?

I’ve found information to solve point 1 and point 2, but not to solve both at the same time.

[Ludwig72]

There are always different solutions and the implementation depends on your requirements and level of experience.

This is how I would implement such a case:

• Create a cloneable module CARD and caller CARDBOARD which registers the module IDs and manages the clones
• Create a parent class card_parent which includes the data and methods for your card and add it to your CARD module MHL data
• Create a request configure for the CARD module
• Inside configure you can pass and assign the specific child class to your object either static or with help of a factory pattern
• Create DQMH requests for each method of your class to call it somewhere in your code

Ready is your CARDGAME

To be serious: I think you mean measurement cards like PXI. Both DQMH cloneables and classes are working if you use the same methods for all your clones or children. If you use different PXI cards which have different functions and methods you have to develop DQMH modules for each of them and a main application to orchestrate the different modules. The big advantage is that you can develop and test them independently (you have a tester for each DQMH module) and put it all together later.