Hi guys, I've been working with a couple of customers recently who are interested in building applications based on DQMH. One of the requirements which has been coming up is the idea of creating a base DQMH module which has a message pump to continuously output messages at a preset rate (different for each instance of the module). What the module is outputting messages to will change, often some hardware protocol which requires continuous messaging even if the data has not changed (I don't want to use the main event timeout as the message pump period would get interrupted by other events being triggered). I have been discussing the idea of creating a cloneable DQMH module which has an additional helper loop to continuously send messages, and then uses a simple hardware abstraction layer to hide the communications protocol behind. I just thought it would be good to get your feedback on this, is this something you've done elsewhere with a similar/different method? If you would like a more fully featured example I could try and find some time to work on it in the next few weeks, but have attached my initial PoC here. Cheers, Pete

Hi Fab, At last I've got around to making some changes to the example code originally posted and building it in to a vip which I've attached. This should install the source and metadata files into the correct place to populate the template enum with a Message Pump template. It sounds like a few people have taken this idea and run with it which is excellent - hopefully the updated code will be useful. Cheers, Pete

DQMH Consortium Toolkits Discussions

Message Pumps in DQMH

Solved!

For me, wiring the output event registration wire to the structure is actually notm readable (like you're saying I think Joerg). It says "I'm changing the way this event structure behaves here"... But that's just me!

Paul

Message 41 of 41

(791 Views)

DQMH Consortium Toolkits Discussions

Message Pumps in DQMH

Re: Message Pumps in DQMH