Module initialization with input from creator (via Start Module VI)?

[_Mike_]

That's great news!

I completely agree with Darren, that it may not be the most essential, but it may be of a great help when combined with factory LVOOP patern. God job!

Do you have some poll of ideas to throw into DQMH 3.0?

If so, then on top of my wish-list is compatibility with RTsystems. DQMH does a great job there, but each module need to be manually tuned, ad they contain several features that are not RT compatible. The main ofthose being the lack of front panel events, which renders module test vis virtually useless for debugging on target.

I have went one step forward and "mocek-up" an intermediate layer between test vi and module, which was sending commands through tcp/ip. this layer couls be invisible for PC developers, while it woud serve great for RT.

Best regards,

Mike

[FabiolaDelaCueva]

_Mike_ wrote:

Do you have some poll of ideas to throw into DQMH 3.0?

If so, then on top of my wish-list is compatibility with RTsystems.

Mike, I will add your suggestion to our internal wishlist tracking system. If/when we implement it, I will post back here.

_Mike_ wrote:

I have went one step forward and "mocek-up" an intermediate layer between test vi and module, which was sending commands through tcp/ip. this layer couls be invisible for PC developers, while it woud serve great for RT.

If you don't mind sharing, you could post a sample project to this group (on a separate document), others could give you feedback and we would have something to evaluate when adding new features to DQMH.

Also, if you don't mind, please share your experiences with DQMH via a LabVIEW Tools Network tool review: http://sine.ni.com/nips/cds/view/p/lang/en/nid/213286#ratingsAndReviews

Thanks,

Fab

[FabiolaDelaCueva]

---

@_Mike_ wrote:

That's great news!

I completely agree with Darren, that it may not be the most essential, but it may be of a great help when combined with factory LVOOP patern. God job!

...then on top of my wish-list is compatibility with RTsystems. DQMH does a great job there, but each module need to be manually tuned, ad they contain several features that are not RT compatible. The main ofthose being the lack of front panel events, which renders module test vis virtually useless for debugging on target.

I have went one step forward and "mocek-up" an intermediate layer between test vi and module, which was sending commands through tcp/ip. this layer couls be invisible for PC developers, while it woud serve great for RT.

Best regards,

Mike

---

Hi Mike, 

DQMH 4.0 is released now and it contains a new feature to create RT DQMH API Testers for DQMH Cloneable modules.

Let us know what you think.

Regards,

Fab

[nlhnt]

Hello, sorry for replying to an old thread, but it was one of the first search results when I typed the following into Google search:

dqmh modification of start module vi

In DQMH 5.0 the modules are called using Start Asynchronous Call which changes the way you can pass data into a module when it is started by another VI or module.
DQMH utilizes the connector pane now and the comments in Start Module.vi describe how update the accepted init data in detail.