Why would I get different sized exe's if I build the same source code and target the same RT target?

[Ben]

Hi all,

This is driving me nuts! I have a VI that uses different amount of memory depending on which machine I use to do the build.

I use the same build file and the same source.

It is targeted at the same cFP2000.

FP version is the same.

LV version is the same.

If I build it from the one machine, there is enough memory available to target the RT platform, show the front panel and do a "show RT engine info".

If I try this from the other machine, the cFP crashes, starts flashing the "status light" and latter on the crash dump file indicate "insuffiecient memory to complete this operation".

The OS on the two machines are both XP. One is a laptop (t
he one that works) the other is a tower.

Are there any LV ini file settings that could be hitting me?

My customer is seeing the same issue, so it not just me.

Any clues?

Ben

[LucaP.]

Hi Ben

This is a really strange behaviour. What I would try is to build the executable being targeted to LabVIEW and to check if both files sizes are the same. It should, to be honest. Then you can move the executable through FTP to the FP-Controller. Please review the KB linked below for more details:
http://digital.ni.com/public.nsf/websearch/B8C2F938DB61960C86256C8C006D7123?OpenDocument

Regards,
Luca

[Ben]

Hi Luca,

The method discussed in the link you provided is the method we will be using when this product finally goes into production.

For the time being, I am still enhancing the application and enhancing an app for a cFP2000 can be rather challenging once it moves beyond the simple demo version.

The application can be loaded into any of the cFP models so I can do my devlopment on one of the bigger units, debug and test using normal tchniques. Unfortunately the app will only run in the cFP2000 if I target the build and run it as an exe. I can live with this because I am the only person who ever want to see the front panel of the exe. The main reason I want to see this FP is to be able to occationally see how my memory is holding up using the "show RT
engine info" ( I plan to include the available memory as another tag in the future).

What brought this to my attention and prompted be to post is that the code works just fine when using my laptop but not my tower. The same issue is affecting when my customer tries to build using my code.

I was rather troubling when I sent out code that worked using the laptop but my coustomer could get it to work.

So...

I would like to figure out what is different and correct it so I can be resonably confident that when my customer builds using my source, he is testing the same image I tested.

Thank for the help! Still wondering,

Ben

[JeanPierre]

Ben,

one ini settings that affects how an application is built is BldApp.RemovePolyVIsandTypedefs. When set to true (default) controls are disconnected from their typedefs and the latter are not saved in the app. It also removes unused subVIs of polymorphic VIs.

Jean-Pierre

[Ben]

Michael A. brought this setting up in the context of LV7.

Is this setting present in LV 6.1?

I will have to check my machines to see if I have this set on my laptop.

Thank you very much!

Ben

[Ben]

It will be a while before I can finish this up.

So far the laptop does NOT have that ini file setting.

I will check my tower when I get back to work.

I will post here if I figure out why this is happening.

Ben

[Ben]

After checking that INI setting is not set in either machine.

Still curious,

Ben