Neosoft Technologies

cancel
Showing results for 
Search instead for 
Did you mean: 

Support Forum: Neosoft DQMH TestStandifier

Solved!
Go to solution

Hi Michael,

 

When we have to do this, we use the TSifier 'bottom to top'.

 

1. We first compile the bottom layers.

2. Get the PPL and replace the dependant lib by the PPL in your project

3. Continue this way until all submodules actually call the PPLs.

 

Doing so building the top module will link all other submodules as PPLs.

 

It is not that easy to do it automatically, because it means we would have to recursively launch and modify all the DQMH modules called.

Since the PPL keep the realtive path of their external dependancies, hierarchy has to be preserved.

Some may want a completely new hierarchy for a top module, some others may want to point on already built PPLs.
We chose to let that freedom by manually pointing on the dependancies you need.

CLA, CTA, LV Champion
View Cyril Gambini's profile on LinkedIn
This post is made under CC BY 4.0 DEED licensing
0 Kudos
Message 31 of 38
(415 Views)

Hello,

 

I am trying to use TestStandifier on a simple project but I get an error -4500 when testandifying any module :

 


L'erreur -4500 s'est produite à : 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

Ce code d'erreur n'est pas défini. Des erreurs non définies risquent de se produire pour plusieurs raisons. Par exemple, personne n'a fourni de description pour le code, ou vous avez câblé un numéro qui n'est pas un code d'erreur valide pour l'entrée de code d'erreur.

De plus, des codes d'erreurs non définis peuvent survenir si l'erreur concerne un objet de tiers, comme le système d'exploitation ou ActiveX. Dans le cas d'une erreur de tiers, il est parfois possible d'obtenir une description de l'erreur en recherchant le code d'erreur (-4500) ou sa représentation hexadécimale (0xFFFFEE6C) sur le Web.

It seems failing creating the source distribution.

 

I am using LabVIEW 2020 32bit Version.

 

Please find attached the source code and screenshots.

 

Thanks for your help.

0 Kudos
Message 32 of 38
(406 Views)

Hi Jean,

 

The error points to the destination path where the TSifier builds the source distribution.

 


@Jean.L wrote:


L'erreur -4500 s'est produite à : 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


TSifier uses the OS temporary folder to do so. Do you have rights on your PC to target the OS Temp folder ?

Then it builds a folder with the name of the module to TSify. I don't see any special char in your modules name but maybe it may ring a bell.

 

Your example files contain 4 modules.

Which module is producing the error ?

 

As soon as I have time, I'll test it with your files.

CLA, CTA, LV Champion
View Cyril Gambini's profile on LinkedIn
This post is made under CC BY 4.0 DEED licensing
0 Kudos
Message 33 of 38
(398 Views)

Hi Cyril,

 

Thank for your quick reply.

 

Every modules were producing the error.

Indeed I don't have the administrative rights on the computer so I can't access the OS temporary folder. It' probably the problem.

Is there a way to parameter the location of this temporary folder ?

If not I'll have to ask permanents rights to IT department of my client.

 

Regards,

 

 

 

 

0 Kudos
Message 34 of 38
(394 Views)

Hi Jean,

 

Thanks to VIShot who is sponsoring us, we are accelerating the development of the TSifier.

One of the item sponsored by VIShot is to target a specific folder instead of the temp folder.

The milestone containing this feature has a due date for this Friday ! So I hope that you could get an updated version by the beginning of next week !

 

Any features that you would need can be sponsored to accelerate their development.

CLA, CTA, LV Champion
View Cyril Gambini's profile on LinkedIn
This post is made under CC BY 4.0 DEED licensing
0 Kudos
Message 35 of 38
(391 Views)

Hi Cyril,

 

Great, thank you very much !

 

Regards,

0 Kudos
Message 36 of 38
(383 Views)

Hello,

 

I have an issue with the TestStandifier exclusions settings : it seems that they are reset when selecting  "Create a subfolder":

- Click "Library Build Config", change some options and click "Save"

- Select/unselect "Create a subfolder with the module name"

- Click "Library Build Config" again : the settings previously selected are gone !

 

Regards,

 

Micael

Cordialement,


Micaël DA SILVA
0 Kudos
Message 37 of 38
(68 Views)

Hi Micael_,

 

Thanks for letting us know.

We released a new version today (1.5.3.29) on VIPM.

Can you check if it addresses your pain points ?

CLA, CTA, LV Champion
View Cyril Gambini's profile on LinkedIn
This post is made under CC BY 4.0 DEED licensing
0 Kudos
Message 38 of 38
(23 Views)