03 Requests

These events are not part of the DQMH default features and have to be implemented manually in every HSE DQMH module.

Triggers the auto-configuration of the module.

• Lets the module configure itself
• The connector pane has to be generic (i.e. only error in / error out) so that this VI can be called dynamically
• The default behaviour of the 'configure' MHL case is to read the module's configuration data from the configuration directory (see Project Structure and hse-configuration for details).

Prepares the module for displaying its front panel.

• meant to be called when the front panel needs specific updating (usually before being shown):

  • 

• used in conjunction with our Windows Application Template when the “Request UI Display” case needs the module to execute code in preparation to showing the front panel (eg reset controls, show a password dialog, etc). The framework calls “Request UI Display”, which in turn calls “Prepare”, which then tidies the FP and executes the original display request:

  • 
  • 

Requests a module to display its UI as specified in the parameter Scenario. The module can either ignore or accept the request.

If the requested scenario is “stand-alone”, the module simply shows its front panel as a new floating window. If the requested scenario is “managed”, the FP is inserted into a subpanel of PROJECT_Layout-VI.vi (no new window pops up).

For the “managed” scenario, the module will send a System Message broadcast with the Ready for Display message, which will be processed by the UI Manager module. To easily create the correct broadcast, the VI hse-dqmh.lvlib:DQMH System Message - Ready for Display.vi is proposed to be used.

More details can be found at the HSE Windows Application Template project.

• Main VI Reference: VI reference to the VI that wants to be displayed. Usually the “Main.vi”.
• Title: The title (e.g. module name) that should be displayed in the app header.
• Target SP Name: Name of the subpanel in which the front panel should be inserted. Default is “SP_Content”, the default subpanel from the HSE-App-Template.

Note: The connector pattern shown above is also necessary for DQMH 5.0, which introduces new connector patterns for Request and Wait for Reply events.