From 11:00 PM CST Friday, Feb 14th - 6:30 PM CST Saturday, Feb 15th, ni.com will undergo system upgrades that may result in temporary service interruption.

We appreciate your patience as we improve our online experience.

Neosoft Technologies

cancel
Showing results for 
Search instead for 
Did you mean: 

Support Forum: Neosoft DQMH TestStandifier

Solved!
Go to solution

Hi Micheal,

 

Yes enum are not so trivial in TS, we'll see if we find an easy solution.

But I definitely added it into our 'next features' board.

 

For the bug related to the lvlib vs lvclass name, do you have a print screen of that ?

Behind the scene we use the app builder, so anything that would let the app builder produce an error will happen in the TSifgier as well.

And there are numerous corner cases where it could heppen. That is why you can try different settings for the source distribution and ppl builds.

If you have a screen copy of the error (and maybe a module to send me), we can take a look and see if we need to build a patch / add more settings regarding SD/PPL building.

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 21 of 68
(1,740 Views)

When you modify the start module to allow a custom module ID, this allows the system to get in a conflicting situation. If you set "run as singleton" false and set a custom ID of 0, then this is an invalid state. If the intention was to run as a cloneable, then setting zero makes it singleton.

 

I don't know how to resolve this, but it makes for a confusing user experience. Perhaps if setting the "run as singleton" flag as false and then specifying a custom module ID as 0 should generate a runtime error with an explanation.



Michael Aivaliotis
VI Shots LLC
0 Kudos
Message 22 of 68
(1,676 Views)

If I wanted to automate this as part of my build process, how can I run the tool? Can I run some of the low level code, or is there an API? Also, is there a way to change the build output folder location?



Michael Aivaliotis
VI Shots LLC
0 Kudos
Message 23 of 68
(1,665 Views)

@MichaelAivaliotis wrote:

If I wanted to automate this as part of my build process, how can I run the tool? Can I run some of the low level code, or is there an API? Also, is there a way to change the build output folder location?


Hi Michael,

 

For the moment no API ! And no, for the moment it is not possible to change the destination directory.

Lets see what we can do for v2 ! ^^

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 24 of 68
(1,649 Views)

@MichaelAivaliotis wrote:

When you modify the start module to allow a custom module ID, this allows the system to get in a conflicting situation. If you set "run as singleton" false and set a custom ID of 0, then this is an invalid state. If the intention was to run as a cloneable, then setting zero makes it singleton.

 

I don't know how to resolve this, but it makes for a confusing user experience. Perhaps if setting the "run as singleton" flag as false and then specifying a custom module ID as 0 should generate a runtime error with an explanation.


The TSifier doesn't remove your responsabilty when using your DQMH module.

It gives you capability, and like any hero, big super power means big responsablities !

 

You should set your module ID correctly based on the inputs you give to the Start Module VI.

If you run your module as a singleton, use default DQMH numbering or set the module ID to 0 in TS.

If you run  your module as a cloneable, ensure that a module ID deosn't get used twice in TS.

 

When using cloneables in TS my advice is to usually set the moduleID MySocketIndex+1.

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 25 of 68
(1,648 Views)

I ran into an issue, and I was able to reproduce it in a sample project. Find attached the code to reproduce the issue. Basically, if your module calls any dependent class method VI that has a name identical to a DQMH request VI name. Then the source distribution step fails. In the example I have a class with a VI method called "Sample Request.vi". I also have a DQMH request with the same name.

 

Here's the error for the attached project:

 

Error 1357 occurred at Error copying files.
Source: C:\_Projects\SampleProject\Instrument Module\Sample Request.vi
Destination: C:\Users\michael.aivaliotis\AppData\Local\Temp\Instrument Module\Instrument Module\Sample Request.vi

Invoke Node in AB_Source_VI.lvclass:Set_VI_Path.vi->AB_Source_VI.lvclass:Copy_SourceItem.vi->AB_Build.lvclass:Copy_Files.vi->AB_Build.lvclass:Build.vi->AB_API Do Two Step Build.vi:4020001->AB_API Build.vi:4700001->NI_AB_API_Build.lvclass:Build.vi->NI_AB_API_SDIST.lvclass:Build.vi->DQMH_TestStandifier.lvlib:Create Source Dist.vi->DQMH_TestStandifier.lvlib:TestStandify State Machine.vi->DQMH_TestStandifier.lvlib:Main.vi

Possible reason(s):

LabVIEW: (Hex 0x54D) A LabVIEW file from that path already exists in memory, or exists within a project library already in memory.

Method Name: Set Path
<Call Chain>Error 1357 occurred at AB_Source_VI.lvclass:Copy_SourceItem.vi -> AB_Build.lvclass:Copy_Files.vi -> AB_Build.lvclass:Build.vi -> AB_API Do Two Step Build.vi:4020001 -> AB_API Build.vi:4700001 -> NI_AB_API_Build.lvclass:Build.vi -> NI_AB_API_S