10-27-2025 05:31 PM - edited 10-27-2025 08:11 PM
Whenever I create a new Module or Event I get the error below. The modules seem to work as they should, but I figure I should find out why this is happening. I'm on Windows 11, LV 2025 64-bit Q3, the latest DQMH. The modules I've created so far pass the validation test.
Thanks,
David Ferster
Lafayette Instruments
Error 7 occurred at Open VI Reference in Panther Dasboard Scripting Hooks.lvlib:_Refresh Module By Name.vi->PDash - Remove DQMH Event.vi->DQMH Remove Event.lvlib:Remove Event - Call Post Scripting Actions.vi->DQMH Remove Event.lvlib:Remove Event.vi->DQMH Remove Do Something.lvlib:Remove Do Something.vi->DQMH New Module.lvlib:Script New Module.vi->DQMH New Module.lvlib:Add New DQMH Module.vi
Possible reason(s):
LabVIEW: (Hex 0x7) File not found. The file might be in a different location or deleted. Use the command prompt or the file explorer to verify that the path is correct.
=========================
Nonexistent GPIB interface.
VI Path: C:\Program Files\National Instruments\LabVIEW 2025\vi.lib\PantherLAB\Panther Dashboard\Panther Dashboard\Refresh Module By Name.vi
11-04-2025 04:36 PM
Thanks for bringing this to our attention but this seems to be Panther Dashboard error, not a DQMH error. I will let Enrique from PantherLabs know
11-05-2025 12:31 PM - edited 11-05-2025 12:32 PM
Hi David, Panther Dashboard works the following way:
What I can imagine is happening here is that you moved/deleted some of the files under [LabVIEW Data]\DQMH Scripting Plugins\, so please could you please uninstall/install Panther Dashboard and see if the problem is gone?
If the problem persists, please create an issue here: https://github.com/PantherLAB/PantherDashboard/issues
Enrique.
11-05-2025 12:44 PM
Dear Enrique,
I'm sure I never moved any files related to DQMH. I never installed Panther Dashboard, and am not using it. The error appears when I am creating events or modules directly from the DQMH items in the Tools menu.
David
11-05-2025 02:23 PM
Well, your post title made me think you were talking about Panther Dashboard. I can't think a way that you ended up running Panther Dashboard code without installing it, that is a separate tool from DQMH.
11-05-2025 02:30 PM
I wonder if files were copied from the [LabVIEW Data] folder from one machine onto another machine. Or maybe both machines share a OneDrive location for the [LabVIEW Data] folder? Maybe Machine A had Panther Dashboard installed, but Machine B does not. Machine A's [LabVIEW Data] folder could have been copied over to (or being accessed by) Machine B, and the folder includes the Panther Dashboard post-scripting plugin VIs. Machine B runs DQMH scripting tools... but if Panther Dashboard isn't installed on Machine B, then those scripting VIs in the [LabVIEW Data] folder are going to have missing dependencies, resulting in the DQMH scripting errors.
That's my best guess as to what's going on here.
11-05-2025 03:48 PM - edited 11-05-2025 04:00 PM
Hi David,
You were at the DQMH Day, and I did include Panther Dashboard in the vipc file we used for the training.
Would you please open your VIPM and filter only to show what is installed? Let's verify which version of DQMH you have installed and confirm that Panther Dashboard is not installed.
Thanks,
Fab
11-05-2025 05:02 PM
Panther Dashboard was not installed according to VIPM. I think at the class I used a different VM. In any case, I have now installed it and the errors no longer appear.
Thanks for your help.
David
11-17-2025 10:21 AM
If this issue reoccurs, the upcoming Panther Dashboard release will enhance error handling for Scripting Plugins. If the tool isn’t installed but the scripting plugins are listed under LabVIEW Data, an error will prompt you to install Panther Dashboard or reinstall it.
Once the tool is installed, the scripting plugins are moved to LabVIEW data, thanks to VIPM’s post-install custom actions. When the tool is uninstalled, another post-uninstall custom action will handle the deletion of Panther Dashboard Plugins.
This tool utilizes separate VIs; the majority of them are located under vi.lib, but the scripting plugins need to be under LabVIEW Data. This setup isn’t standard. However, it’s necessary because that’s how the framework is designed.
Putting this comment here in case someone else falls into the same issue.
Enrique.