Neosoft Technologies

Showing results for 
Search instead for 
Did you mean: 

Support Forum: Neosoft DQMH TestStandifier

Go to solution

Please use this forum thread for any support question on the:

Neosoft DQMH TestStandifier

It is available on

Vincent Carpentier, Ing./Eng.
Neosoft Technologies
DQMH Trusted Advisor
0 Kudos
Message 1 of 7

I tried to convert a project with multiple DQMH libraries and I got the following error:

Error 1055 occurred at Close Reference in DQMH_TestStandifier_Resources.lvlib:Modify Module ID Generation>DQMH_TestStandifier.lvlib:TestStandify State>

Possible reason(s):

LabVIEW: (Hex 0x41F) Object reference is invalid.

Error Dialog w Copy to Clipboard.lvlib:Simple Error

0 Kudos
Message 2 of 7

Hi Alfredo,

Would you be able to post your DQMH module here ?

If not let me know, and we'll find a way to analyze this.


The error is related to modifying the module ID inner code in request and reply VIs which are part of cloneable modules.


View Cyril Gambini's profile on LinkedIn
0 Kudos
Message 3 of 7

Unfortunately this is not possible.

0 Kudos
Message 4 of 7

Hi Alfredo,


Difficult to help without seeing the original code.

Maybe you can send it me in PM so that it is not public.


Quick question, was your DQMH made with the latest version of DQMH ?


View Cyril Gambini's profile on LinkedIn
0 Kudos
Message 5 of 7

Hello, i will try to contact you privattely. The version of DQMH used for the project was v6.1.0.90 

0 Kudos
Message 6 of 7
Accepted by CyGa

So for the record, with another user (so not @Alfredo_VM ) we faced the same issue.

The problem comes from the fact the original module was made using DQMH v4.

The module was upgraded with the DQMH Validator v5 and v6, but a fix was not correctly applied by the user (validator did not return an error but the status message was saying something went wrong).


This lead to Start Module VI was not containing the feedback node to handle the clone IDs but was still having the 'old' way to generate the clone ID (based on VI Clone name) and was launching the Main VI thanks to the Run VI method instead of the Run Asynchronous node.

So if you face this issue with the TestStandifier, ensure that your module is a fully valid DQMH module as defined per DQMH v6.1



View Cyril Gambini's profile on LinkedIn
0 Kudos
Message 7 of 7