Issue with DQMH Tester Auto-Generation – Request Button Not Created

[ftosoratti]

I am experiencing an issue with DQMH when creating a new Request event in a module.

When I create a new Request event, the following occurs:

• The event is correctly added to the Main VI.

• All required VIs are generated properly.

• The corresponding Event Case is created inside the Tester VI Event Structure.

However, the button that should be automatically generated in the Tester front panel to trigger the Request is not created. Additionally, there is no automatic association between a Boolean control and the Value Change event that should trigger the corresponding case.

This problem occurs both when creating a simple Request and when creating a Request and Wait for Reply event.

The issue appeared suddenly. Up until a certain point, everything was functioning perfectly, but now the Tester does not create the trigger buttons automatically.

To rule out module-specific issues, I performed the following tests:

• Created a completely new project.

• Created a brand-new DQMH module.

• Added a new Request event.

The behavior remains the same: the Event Case is created in the Tester, but the trigger button is not generated.

VI Scripting is enabled, and I have also tested after restarting LabVIEW and clearing the VIObjCache folder. I have additionally uninstalled and reinstalled DQMH via VI Package Manager, but the issue persists.

For reference, I am attaching:

• Photos showing how the Tester appears when I try to create a new case.

• A project containing a module and a case, to demonstrate how everything is being created.

I am using LabVIEW 2023 Q3 and DQMH version 7.1.2.1547.

Could you please advise on what might be causing the Tester front panel control not to be generated automatically?

[Olivier-JOURDAN · Accepted solution]

Hello @ftosoratti

The very first check is whether the option is enabled in the Create New DQMH Event window.

I've already disabled it inadvertently once. So, it's worth checking.

[ftosoratti]

Hello Olivier,

Thanks so much! I’m not sure why, but it was disabled. Usually, when I create a DQMH event, it’s always enabled, and I didn’t notice this time.
Also, it changed in the meantime because I created another event in an already populated module.

Thank you again!