Select Page

Lumos (Pre-order)


Even though the financing via Kickstarter fell through, the interest in DQMH Lumos is higher than ever. From our wonderful backers here to personal discussions at conferences and workshops, it is clear that there is a need for this tool. So we will continue the work and aim to release DQMH Lumos before EOY!

All licences purchased via our webshop before October 26 will include all the perks we promised in our Kickstarter campaign: A discount AND a free upgrade to v2.0, bragging rights for supporting the DQMH Consortium and a Lumos sticker. If you feel really lucky, ask for the autographed photo of Joerg 😉

If you are interested in a Site License (10 or more seats), please contact us directly.




Monitor your DQMH modules’ communication (requests and broadcasts) live and in real-time.

Doesn’t that sound like a dream come true? Yes, it does – at least for LabVIEW programmers who choose the DQMH® Framework as their weapon of choice.

All the flexibility that the DQMH Framework brings with its modules – which you can start and stop dynamically, and which can receive request messages from any place in your application and send broadcasts out into the wild – comes at a cost: The more dynamic your application, the harder to follow the flow of information and data.

Just imagine taking over a software project from a coworker, and then having to track down a race condition in between a bunch of modules – impossible!

Lumos to the Rescue!

The Lumos toolkit allows you to monitor the communication inside your application – live and in real time! 

With a little bit of VI Scripting magic, the tool taps into your code and adds hooks so it can listen in on the events being sent between your modules. The viewer then displays the logged messages in a sequence-style diagram.

But see for yourselves:

The Lumos viewer shows the full trace like this (click on picture for large version):

Full Trace


A beautiful SVG export is available directly from the viewer window:

SVG export of full trace


The trace can be configured to only display messages of certain types (…):

Trace view with messages filtered by type
Trace view with messages filtered by type


An exported SVG will only show those messages not filtered out, which can be very helpful and give more clarity in certain situations:


Messages can also be filtered by time:

Trace view with messages filtered by time
Trace view with messages filtered by time


Again, the SVG export will reflect the filtered scenario:


For programmatic access to the Lumos tracing engine, the tool comes with an API that is easily accessible via the palettes:

Application Programming Interface (API) palette
Application Programming Interface (API) palette


Being able to place a divider “manually” – i.e. by placing the Generate Divider on the block diagram – showcases how flexible the Lumos trace engine is. The potential for extensions to this tool is infinite!

Generate Divider
Generate Divider


Divider as seen in the live trace
Divider as seen in the live trace

Additional information

Product Documentation