Delacor Toolkits Discussions

cancel
Showing results for 
Search instead for 
Did you mean: 

Error when trying to create new module from custom Template

Highlighted

It would be nice if we could get more information when the DQMH fails to locate a file, ie what file is missing or not found.

 

Edit:  The module passed validation, with no errors or warnings (non-critical errors).

 

Currently, if you try to add a Custom DQMH module, and there is an incorrect file, you only get "Error 7 occurred at Invoke Node in DQMH New Module.lvlib:Script New Module.vi->DQMH New Module.lvlib:Add New DQMH Module.vi.   LabVIEW:  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. 
Method Name: Library:Open"

A nice addition would be "Error 7 occurred at Invoke Node in DQMH New Module.lvlib:Script New Module.vi->DQMH New Module.lvlib:Add New DQMH Module.vi.  LabVIEW:  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. 
Method Name: Library:Open
Attempted to open file: C:\<folder>\filename.vi"

Kenny

0 Kudos
Message 1 of 7
(2,515 Views)
Highlighted

I have the same issue.

LV 2016 32-bit

DQMH 3.1

 

Thanks,

Sergiy

 

0 Kudos
Message 2 of 7
(2,479 Views)
Highlighted

Were you guys able to get your DQMH module from template to work?

 

If not, please try the code that ships with DQMH 3.1 and place it in the locations indicated in the documentation: http://delacor.com/documentation/dqmh-html/AddingaNewDQMHModulefromaCustomT.html

 

Things to check if the creation of DQMH modules from template is not working for you:

* in XML Meta data file, make sure the name of the module and the tester match

* in XML Meta data file, make sure the paths match the file structure of your files

* Make sure you did copy the API Tester as well as the DQMH module.

 

Regarding:


@Kenny_K wrote:


A nice addition would be "Error 7 occurred at Invoke Node in DQMH New Module.lvlib:Script New Module.vi->DQMH New Module.lvlib:Add New DQMH Module.vi.  LabVIEW:  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. 
Method Name: Library:Open
Attempted to open file: C:\<folder>\filename.vi"


I will file a feature request to have more descriptive errors for this part.

 

Thanks,

Fab

I'm Organizing the GLA Summit!


For an opportunity to learn from experienced developers / entrepeneurs (Steve, Joerg, and Brian amongst them):
Check out DSH Pragmatic Software Development Workshop!

DQMH Lead Architect * DQMH Trusted Advisor * Certified LabVIEW Architect * Certified LabVIEW Embedded Developer * Certified Professional Instructor * LabVIEW Champion * Code Janitor

Have you been nice to future you?
0 Kudos
Message 3 of 7
(2,470 Views)
Highlighted

As a feature request for the templates related to this, can the paths in the XML be absolute rather than relative to "<LabVIEW Data>\DQMH Module Templates\Source"?

 

Thanks

0 Kudos
Message 4 of 7
(2,281 Views)
Highlighted

@Evan wrote:

As a feature request for the templates related to this, can the paths in the XML be absolute rather than relative to "<LabVIEW Data>\DQMH Module Templates\Source"?

 

Thanks


We will add it to the feature requests list.

Thanks for giving us feedback.

Fab

I'm Organizing the GLA Summit!


For an opportunity to learn from experienced developers / entrepeneurs (Steve, Joerg, and Brian amongst them):
Check out DSH Pragmatic Software Development Workshop!

DQMH Lead Architect * DQMH Trusted Advisor * Certified LabVIEW Architect * Certified LabVIEW Embedded Developer * Certified Professional Instructor * LabVIEW Champion * Code Janitor

Have you been nice to future you?
0 Kudos
Message 5 of 7
(2,268 Views)
Highlighted

Hi,

 

I also experienced this issue, but noted that the help documentation is slightly wrong.  When I changed my paths as per below, it worked.

 

Please see my slight correction (highlighted in red) for page http://delacor.com/documentation/dqmh-html/DQMHDocumentation.html?Introduction:

 

  1. Create a new DQMH Module and customize it to fit your needs. Save your DQMH Module. This document refers to this new DQMH module as <MyNewModule>. Replace <MyNewModule> with the new DQMH Module name. Make sure that the DQMH module was created using Tools>Delacor>DQMH>Add New DQMH Module… and if you need to rename the DQMH Module, use Tools>Delacor>DQMH>Rename DQMH Module…
  2. Save the DQMH Custom Template in <LabVIEW Data>\DQMH Module Templates\Source\Delacor\<MyNewModule> folder.
  3. Save the Test <MyNewModule> API.vi in <LabVIEW Data>\DQMH Module Templates\Source\Delacor\<MyNewModule> folder.
  4. Create the DQMH Module Template MetaData XML file and save it as <LabVIEW Data>\DQMH Module Templates\MetaData\<MyNewModule>.xml

Either this, or change the Location Path in XML file to not have the Delacor folder, ie:

<LocationPath>Delacor/<MyNewModule> </LocationPath>

 

Regards

Christopher Farmer

Certified LabVIEW Architect
DQMH Trusted Advisor
http://wiredinsoftware.com.au
Message 6 of 7
(2,113 Views)
Highlighted

@Ozfarmboy wrote:

Please see my slight correction (highlighted in red) for page http://delacor.com/documentation/dqmh-html/DQMHDocumentation.html?Introduction

 


...

Chris, 

 

Thanks for bringing this to our attention, we have updated the online documentation at:

http://delacor.com/documentation/dqmh-html/AddingaNewDQMHModulefromaCustomT

 

To include the Delacor folder in the paths and updated the Change history at:

http://delacor.com/documentation/dqmh-html/ChangeHistory

 

The documentation that ships with DQMH is installed in:

<LabVIEW>\help\Delacor\_Delacor QMH\DQMHDocumentation.chm

We will update this change in the shipping documentation in the next release.

 

BTW, the documentation that ships with DQMH is accessed automatically via the Help>>Delacor menu when the computer is not connected to the internet.

 

Regards,

Fab

I'm Organizing the GLA Summit!


For an opportunity to learn from experienced developers / entrepeneurs (Steve, Joerg, and Brian amongst them):
Check out DSH Pragmatic Software Development Workshop!

DQMH Lead Architect * DQMH Trusted Advisor * Certified LabVIEW Architect * Certified LabVIEW Embedded Developer * Certified Professional Instructor * LabVIEW Champion * Code Janitor

Have you been nice to future you?
0 Kudos
Message 7 of 7
(2,106 Views)