Support Forum: Neosoft DQMH TestStandifier

[Thomas44444]

Hi,

I'm getting a similar error than another post, I confirm I'm admin on the computer ...

Error -4500 occurred at : DQMH_TestStandifier.lvlib:Main.vi -> DQMH_TestStandifier.lvlib:TestStandify State Machine.vi -> DQMH_TestStandifier.lvlib:Create Source Dist.vi -> NI_AB_API_SDIST.lvclass:Set Destination Path.vi -> NI_AB_API_Build.lvclass:Set Destination Path.vi -> AB_API Set Destination Path.vi

This error code is not defined. Undefined errors can occur for several reasons. For example, nobody has provided a description for the code, or you have wired a number that is not a valid error code for the error code entry.

In addition, undefined error codes can occur if the error relates to a third-party object, such as the operating system or ActiveX. In the case of a third-party error, it is sometimes possible to obtain a description of the error by searching for the error code (-4500) or its hexadecimal representation (0xFFFFEE6C) on the Web.

Any idea why this could be happening ?

[CyGa]

Hi,

The destination path error is usually related to rights.

If you are setting your destination to C: for example, you must be admin of your PC but moreover in some cases you have to launch the TSifier as admin. Since you might be laucnhing it from LV, it means that LV should be started as administrator (right click LV icon -> Run as Asdministrator).

Otherwise, you could also set the destination in the Public Documents.
TSifier sometimes (due to some build specs options) might use the Temporary Folders, which also require on some systems the admin rigts for the current application execution.

[Thomas44444]

Thank you for your fast answer.

I tried to change the path to public document, to run LV in admin as you described and I tried to testandify another DQMH and got the same issue.
Is there any way to get more detail on this error ?

[python007]

Hi

I have a DQMH Module (9015 n-Point Calibration) in which i use functions from an other PPL (9007 HMC8012.lvlibp). When I try to teststandify the DQMH Module (9015 n-Point Calibration)

with "Library Build Config" -> "Exclude dependetent packed libraries" checked the 9007 HMC8012.lvlibp is anyway added to the output folder.

Does some one know what the problem is?

[CyGa]

---

@Thomas44444 wrote:

Thank you for your fast answer.

I tried to change the path to public document, to run LV in admin as you described and I tried to testandify another DQMH and got the same issue.
Is there any way to get more detail on this error ?

---

This difficult to get more info because it happens inside a library that is protected by NI.

I don't know what happens in there ...

Question out of the blue : all your licences (and especially the builder one) are valid ?

[CyGa]

---

@python007 wrote:

Hi

I have a DQMH Module (9015 n-Point Calibration) in which i use functions from an other PPL (9007 HMC8012.lvlibp). When I try to teststandify the DQMH Module (9015 n-Point Calibration)

with "Library Build Config" -> "Exclude dependetent packed libraries" checked the 9007 HMC8012.lvlibp is anyway added to the output folder.

Does some one know what the problem is?

---

Good question !

You may have a circular dependency that forces LV to add again the lvlibp.

Behind the scene we use the VIs that LV uses when you create a source distrubtion or a PPL. So we do not have much control over it.

If the same thing happens with LV alone, then there is a reason but I don't know which one !

Nevertheless, I'd advise to keep your dependent PPL linked here. The builder is able to change the dependency paths, and therefore it hsould greatly help when TS will load up your top level DQMH lib.

[python007]

---

@CyGa wrote:

---

@python007 wrote:

Hi

I have a DQMH Module (9015 n-Point Calibration) in which i use functions from an other PPL (9007 HMC8012.lvlibp). When I try to teststandify the DQMH Module (9015 n-Point Calibration)

with "Library Build Config" -> "Exclude dependetent packed libraries" checked the 9007 HMC8012.lvlibp is anyway added to the output folder.

Does some one know what the problem is?

---

Good question !

You may have a circular dependency that forces LV to add again the lvlibp.

Behind the scene we use the VIs that LV uses when you create a source distrubtion or a PPL. So we do not have much control over it.

If the same thing happens with LV alone, then there is a reason but I don't know which one !

Nevertheless, I'd advise to keep your dependent PPL linked here. The builder is able to change the dependency paths, and therefore it hsould greatly help when TS will load up your top level DQMH lib.

---

Hi CyGa

Thanks for your fast response.

The strange thing is when I create from this DQMH Module a PPL in LV without the Teststandifier it doesen't add the "9007 HMC8012.lvlibp". Could it be that something in Teststandifier goes wrong?

To make a simple Test I created the fallowung:

- "Test PPL.lvlibp" with the VI "Test.vi"

- Created a DQMH Module "Module 1" and added a Request which runs the "Test.vi" from the PPL

If I run the TestStandifier with "Exclude dependetent packed libraries" the "Test PPL.lvlibp" is added in the output Folder.

Attatched you can find "Test DQMH.zip" with all the files maybe this helps.

Best regards

[python007]

Hi

I get the fallowing Error Message:

Updating Media

Detail Error COde

Spoiler

Error -17306 occurred at Unknown variable or property name 'ConnectorNumber'.
Error accessing item 'ConnectorNumber'. in DQMH_TestStandifier_Resources.lvlib:Verify For Sequence Context terminal.vi->DQMH_TestStandifier_Resources.lvlib:Recursive_Create_And_Map_Parameter.vi:7290004->DQMH_TestStandifier_Resources.lvlib:Recursive_Create_And_Map_Parameter.vi:7290003->DQMH_TestStandifier_Resources.lvlib:Recursive_Create_And_Map_Parameter.vi:7290001->DQMH_TestStandifier_Resources.lvlib:Recursive_Create_And_Map_Parameter.vi:7290002->DQMH_TestStandifier_Resources.lvlib:Add_TS_parameters.vi->DQMH_TestStandifier_Resources.lvlib:Add Steps in Sequences.vi->DQMH_TestStandifier_Resources.lvlib:Create TS Sequence.vi->DQMH_TestStandifier.lvlib:TestStandify State Machine.vi->DQMH_TestStandifier.lvlib:Main.vi

This error code is undefined. Undefined errors might occur for a number of reasons. For example, no one has provided a description for the code, or you might have wired a number that is not an error code to the error code input.

Additionally, undefined error codes might occur because the error relates to a third-party object, such as the operating system or ActiveX. For these third-party errors, you might be able to obtain a description of the error by searching the Web for the error code (-17306) or for its hexadecimal representation (0xFFFFBC66).

Error Dialog w Copy to Clipboard.lvlib:Simple Error Handler.viDQMH_TestStandifier.lvlib:Main.vi

Has anyone a idea what this could be?

Best regards

[CyGa]

Is one of your inputs/output on a connector named ConnectorNumber ?

If not, the only thing I can see is that we change the connector where there is no more place, and we add a connector and remap everything as best as we can.

Is your connector full on one of the requests ?

[python007]

---

@CyGa wrote:

Is one of your inputs/output on a connector named ConnectorNumber ?

If not, the only thing I can see is that we change the connector where there is no more place, and we add a connector and remap everything as best as we can.

Is your connector full on one of the requests ?

---

Hi CyGa and thanks for your response.

I don't have a connector named "ConnectorNumber".

Is your connector full on one of the requests: If you mean with that the connector Pane in LabVIWE then No they are not full.

On one of the requests I have a large Array of Clusters with many sub-clusters and arrays. Could this be the Problem?