LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Metric.FPSizes of the same vi are different on different PCs

Pen_Pen_0-1754836677786.png

the Metric.FPsize property gives diffrent values when run on different PCs, although it is for exact same VI (2 PCs are different interms of CPU,GPU,memeory, etc.). And in my case it only happens in executables, if I run the hashgenerating code in development environment, they give same result. The value for Codesize stays the same on different PCs.

I then tried different vis to generate hashcode, the difference is not the same too, if the vi is really simple for instance 1 control and 1 indicator, then there is no difference, if the vi is more complicated, the difference is also greater.

 

I suspect it has something to do witth how the Metric.FPSize is calculated, but I could not find any useful infomation. Can someone give me advice?

 

back ground:

we use LV20.0.1f1 32bit.

We use above code to generate hashcode of a test vi, this hashcode is saved in database after test vi release.

Then before running the test vi, the hashcode is again calculated and compared with the one in the database.

it can be that the hashcode is generated on one PC for the database and gets calculated and checked on another pc, and a mismatch is reported. 

 

0 Kudos
Message 1 of 3
(152 Views)

Hi Pen,

 

I don't know about the VI metrics changing from one PC to another, but I wouldn't use it for generating a VI hashcode.

 

Try this private property instead:

VI Signature.png

 

To access private (brown) properties/methods/classes, add this key to your LabVIEW.ini and restart LabVIEW:

SuperSecretPrivateSpecialStuff=True

 

Regards,

Raphaël.

0 Kudos
Message 2 of 3
(126 Views)

Than you raphschru for your advice, I will check this method out and align with my team members. 

 

I am still very curious though about how this FPSize is calculated.

0 Kudos
Message 3 of 3
(107 Views)