Guidelines and tips pertaining to the HSE Application Template.

• Keep framework and project responsibilities separate

• By default, the Application Template starts only a single, project-specific Application Controller.lvlib module via the framework mechanism (config.ini and startup.vi)

  • having this one dynamically loaded module avoids static dependencies between framework and project-specific code

• The project-specific Application Controller (which typically has an HSE State Machine) is responsible for starting and coordinating all remaining modules

  • this allows for simple static dependencies to anything the project requires
  • it makes deterministic ordering possible
  • → adhere to the guidelines for parent/child module relations
  • → learn more about Starting DQMH Child Modules

• Starting multiple modules directly from the framework is still supported, but should only be used where appropriate:

  • UI Framework modules
  • Modules that are displayed in UI-Manager/Layout VI at startup
  • Very small applications

The Application Controller explicitly coordinates starting and synching of all remaining modules using an HSE State Machine. When starting multiple modules, use

• separate states in the SM
• synchronous
• for modules that depend on each other (ie A needs to run before B)

• same state in the SM
• asynchronous
• for independent modules (ie A and B don't care about each other)

• combination of sequential and parallel
• combine modules in groups
• start modules in groups in parallel
• start different groups sequentially (eg first all models, then all viewers)

• Keep dependencies explicit and one-directional

  • Application Controller – coordinates application state
  • Models – implement business logic and device communication
  • Viewers – present application state

Model modules should not depend on Viewer modules