LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Labview 8.6 build EXE Error 1073

I am using LabVIEW 8.6 and this problem occurs when Iam trying to build EXE file for the project.

 

Visit the Request Support page at ni.com/ask to learn more about resolving this problem. Use the following information as a reference:
Error 1073 occurred at D:\Projects PFA\Codes Dev\Current Project\00. Project\GUI\GUI\starting v0.01.vi
Possible reason(s):
LabVIEW:  This property is writable only when the VI is in edit mode, or this method is available only when the VI is in edit mode.

 

What is the property described here ? It is the property of the control ? Compile with LabVIEW 8.5 with control property show no error. 

Any1 has anyidea or clue about this error message ?  Thanks in advance.

0 Kudos
Message 1 of 17
(4,781 Views)

Hi engwei,

 

Thanks for your post and I hope your well.

 

I have two things you could try:

 

1) 

This error can occur when a block diagram has been removed from a VI that is part of the build process. Make sure that both the main VI and all subVIs have not had their block diagram removed. The block diagram can be removed by making a custom save from File->Save With Options. Block diagrams that are removed cannot be recovered.

For instructions on how to build an application from subVI without block diagrams, see KnowledgeBase 39BCEA2Q

 

2)

Secondly, this error can also been seen when Main VIs and SubVIs contain a broken arrow. Have you checked that their are no errors (broken arrow) in the code?

 

Please let me know how you get on,

 

Kind Regards,
James.

Kind Regards
James Hillman
Applications Engineer 2008 to 2009 National Instruments UK & Ireland
Loughborough University UK - 2006 to 2011
Remember Kudos those who help! 😉
0 Kudos
Message 2 of 17
(4,763 Views)

Hi Hillman,

 

Thanks for your reply. Regarding the 2 issues, 

 

1. There is no subVI without block diagrams. The message said that the (v 0.01 starting.vi) cause the error 1073, and I have check the subvi in the v 0.01 starting.vi and all is okay. Really wonder why I can run it, but I can't compile it to EXE.

FYI, v0.01 starting.vi is one of the vi in the project.

 

2. No broken arrow. I have "mass compile" the project and I found nothing wrong with it. The mass compile show the message below:

 

#### Starting Mass Compile: Fri, Nov 28, 2008 2:37:53 PM
  Directory: "D:\Projects PFA\Codes Dev\Current Project\00. Project\0PFA.lvproj"
#### Finished Mass Compile: Fri, Nov 28, 2008 2:38:07 PM

 

Obviously, all files is propely located. No conflict, no error.

 

 

Please help .. Thanks in advance. 

 

 

 

0 Kudos
Message 3 of 17
(4,748 Views)

Hi Engwei,

 

Thanks for the update.

 

Could you please attach a project (example) that generates this error?

 

Are you by any chance using the Convert Panel To Screen coorindates method?

 

I would also check any property/method(invoke) nodes and make sure they are avaiable at Run Time - because this will use the Run Time Engine. This can be done using the context help - and it should list Run Time Yes/No.

 

Please let me know,

 

Kind Regards,
James.

Kind Regards
James Hillman
Applications Engineer 2008 to 2009 National Instruments UK & Ireland
Loughborough University UK - 2006 to 2011
Remember Kudos those who help! 😉
0 Kudos
Message 4 of 17
(4,739 Views)

Hi Hillman,

 

Thanks for your reply. Here I attached all property involving in the vi. I can't upload the whole project here since some part of it remain IP of the company. 

Not so clear with what you mean by "Convert Panel To Screen coorindates method" .. 

 

In this vis I din use any coordinates function, either get or set the coordinate of any control. 

 

Is there any other possible causes other than the property of the control ? Thanks for your time.

0 Kudos
Message 5 of 17
(4,731 Views)

Hi Engwei,

 

Thanks for the update.

 

The VI built for me.

 

Are you using any type-defs?

 

Also what options are you selecting for your build, could you please provide details?

 

I would also like to confirm that all your VI(s) have block diagrams.

 

Did you write this code in LabVIEW 8.6?

 

Kind Regards,
James.

Kind Regards
James Hillman
Applications Engineer 2008 to 2009 National Instruments UK & Ireland
Loughborough University UK - 2006 to 2011
Remember Kudos those who help! 😉
0 Kudos
Message 6 of 17
(4,726 Views)

Hi Hillman,

 

 

Thanks for your reply. 

I don't think I have used any type-def.

The option, I have selected "EXE". The rests remain default. 

All VIs is built from block diagram. And some is the build in VIs, provided from Functions Palette (Measurement I/O).

And I have used the VIs from http://forums.lavag.org/Type-Sensitive-Popup-file105.html

 

I wrote this code in Labview 8.5. Then last week I start to move the project development to LabVIEW 8.6.

 

Thanks again for your time.

0 Kudos
Message 7 of 17
(4,701 Views)

some addition here ..

 

compile EXE in LabVIEW 8.5 work perfectly, with the vi from

 

Functions Palette (Measurement I/O).

VIs from http://forums.lavag.org/Type-Sensitive-Popup-file105.html

 

 

 

0 Kudos
Message 8 of 17
(4,692 Views)

Hi Engwei,

 

Can you confirm that the VIs have been compiled in LabVIEW 8.6 and that the code works fine in debug mode under LabVIEW 8.6?

 

Are any toolkits your using in Evaluation Mode in LabVIEW 8.6?

 

Does the application builder - if you go to the Additional Exclusions page and uncheck the options specified in the error - does the error stop?

 

Kind Regards,
James.

Kind Regards
James Hillman
Applications Engineer 2008 to 2009 National Instruments UK & Ireland
Loughborough University UK - 2006 to 2011
Remember Kudos those who help! 😉
0 Kudos
Message 9 of 17
(4,680 Views)
Message Edited by engwei on 12-01-2008 08:10 PM
0 Kudos
Message 10 of 17
(4,661 Views)