09-21-2021 05:16 AM
Hi,
I have been google searching this morning to try and find any information on the License terms for using DQMH, I know it is freely provided and supported, but I assume there is some form of GNU License or equivalent somewhere ?
cheers
Danny
Solved! Go to Solution.
09-21-2021 05:20 AM
Go to VIPM, select DQMH from the list, and then select License Agreement:
09-21-2021 05:37 AM
Yep obvious, why did I forget that 🤔, thank you
09-21-2021 05:42 AM
Yep! Although the vipm.io page says License "Not Specified":
DQMH Toolkit for LabVIEW - Download - VIPM by JKI
That should probably have the license info in there @Joerg!
09-21-2021 07:06 AM
@ChrisFarmerWIS wrote:
Yep! Although the vipm.io page says License "Not Specified":
That should probably have the license info in there @Joerg
Thanks for pointing that out!
Seeing as DQMH's license is not one of the generic open-source licenses (like BSD etc.), that field probably won't have much use - but it still should not say "not specified".
I can't edit the value directly via the web interface, so I'll have to check with the VIPM team.
DSH Pragmatic Software Development Workshops (Fab, Steve, Brian and me)
Release Automation Tools for LabVIEW (CI/CD integration with LabVIEW)
HSE Discord Server (Discuss our free and commercial tools and services)
DQMH® (Developer Experience that makes you smile )
10-25-2021 09:32 AM
I'll second that it would be nice to have the license text available somewhere without having to start the package installation process. Even if it's just a small link in the footer of the dqmh.org website
10-25-2021 05:27 PM
I've added the license agreement to the wiki while we're working on a more permanent solution for both vipm.io and DQMH.org.
DSH Pragmatic Software Development Workshops (Fab, Steve, Brian and me)
Release Automation Tools for LabVIEW (CI/CD integration with LabVIEW)
HSE Discord Server (Discuss our free and commercial tools and services)
DQMH® (Developer Experience that makes you smile )
10-26-2021 04:36 AM
The license is now linked to both on vipm.io and DQMH.org (in the "Install" section).
DSH Pragmatic Software Development Workshops (Fab, Steve, Brian and me)
Release Automation Tools for LabVIEW (CI/CD integration with LabVIEW)
HSE Discord Server (Discuss our free and commercial tools and services)
DQMH® (Developer Experience that makes you smile )
01-13-2025 01:44 AM - edited 01-13-2025 01:45 AM
Hello everyone,
I have a very basic question: I am developing an application to perform automated testing using teststand. The main VI (i.e. the only application the operator will actually run) is not implemented using DQMH, but I would like to implement several modules as DQMH (DAQ-Module, single test control, ...).
Is it enough to mention the use of DQMH in the documentation/about window of the main application (which is not dqmh-based)? (many submodules are headless, so there won't be any interface for the user to see an "about" section)
Thank you in advance,
Juan
01-14-2025 04:55 PM
Hi Juan,
We have provided the following VIs on the function palette:
If you place the About DQMH VI on your block diagram and run it, you will see that it displays the text that the other three VIs provide: DQMH Version, DQMH Legal information, and the DQMH End User License Agreement URL.
You can use the About DQMH VI as is, or save it and make your own version with other information relevant to your application and use it as the About VI for your application. Or if you already have an About VI, call in that VI the DQMH Legal Info and DQMH EULA URL and you will be complying with the license.
You don't need an about section per DQMH module in your project, just an acknowledgment that your application is using DQMH.
Thanks for your interest in DQMH and your trust in us.
Happy wiring,
Fab