Open vi reference problems in labview 7 after building an application

I have a vi with an Open VI Reference vi in it.
This works fine. But when I build an application of it and run the vi it gives problems.
I get an Open VI Reference error. Why?

If you have strict typedefs for the dynamic loaded VIs you need to include the line "BldApp.RemovePolyVIsandTypedefs=False" into your LV ini file. See this discussion.
Waldemar
Waldemar
Using 7.1.1, 8.5.1, 8.6.1, 2009 on XP and RT
Don't forget to give Kudos to good answers and/or questions

Similar Messages

Open VI reference, problem on RT target

I'm having problems opening references to VI's on my RT target (cRIO 9074 with NI-RIO 3.1.0, VI server enabled). I'm using Labview 8.6.1
What I'm doing is opening the reference using an absolute path ("c:\ni-rt\temp\test12.vi") to the VI I want to run (path is the only input that is wired). "Open VI reference" throws error 1124 (VI not loadable).
The VI that should be loaded only contains a while loop toggling a boolean indicator, no subVI's.
If I remove the VI from the specified path I get error 7 (File not
found) when I run the code, so the path doesn't seem to be wrong.
I've tried running the"open vi reference" function on my host computer and on the target (both as an .exe and directly deployed) but the result is the same.
No error is thrown if I build an .exe and include test12.vi in the build, but I assume that in that case the VI has already been loaded when "open vi reference" is called. This is not a solution for me.
If I move both VI's to my host computer everything works.
Does anyone have any ideas about what could be wrong? I've searched to forum but found no solution.

Hi Sterlind,
Have you tried building a source distribution, the VI might depend on some VI:s from VI.lib or such.
This KB seems to suite your error description,
http://digital.ni.com/public.nsf/allkb/10F1D411ACBAD3D9862572FF0064C801?OpenDocument
Regards,
Klas Andersson
National Instruments
AE, Sweden

Open vi reference conversion from Labview 6 to Labview 2014

Is there a way that someone can help me convert this VI written in Labview 6.1 so that I can work en EXE in Labview 2014.
I succed to open this vi from 6.1 to 2014 but it does not run. The open vi reference those not work in exe program. Someone know how I can replace that function...
Thanks!
Solved!
Go to Solution.
Attachments:
to convert 2104.zip ‏17 KB

Error 7 is File Not Found. So your dynamically called VI is not in your executable.
In the build spec for the executable in your project, there is a section for "Source Files". On of the options for the VIs is "Always Include".
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

Open VI Reference to a LabVIEW executable.

Hello,
I haven't done this for a while and it's not working like expected. I'm trying to "Open VI Reference" from executable A.exe to B.exe. I'm trying to get a control value from B.exe in A.exe. Can someone send me an example?
Right now I'm at this stage: I have A.exe running as a LabVIEW executable. I'm trying to "Open VI Reference" to A.exe from LabVIEW development without success. Not sure what I'm doing wrong.
Don't hesitate to ask more info if you need some.
LabVIEW 2012, Windows 8.1.
Thanks,
Michel
Solved!
Go to Solution.

Bob_Schor wrote:
Once you have an Executable, does it matter that the underlying Development system is LabVIEW, rather than (say) Visual Studio, or Matlab? I suppose you could write an application that "knows" to, for example, listen to a TCP/IP port and interpret/execute commands, but that doesn't sound like the question being asked.
BS
LabVIEW-built executables still run as VI's in the RTE, though. Their identities have not been abstracted away into one single object or anything, and they still have name-based VI server access.
You can configure a build specification to include almost nothing, and require the VI files to be present in expected locations (i.e build specification's data or support directories). By default, all items in an executable application build specification are set to be put in the same location as their caller, which results in most things going into the .exe file, internally referenced in a directory-esque form like crossrulz mentioned, "MyExecutable.exe\MySubVI.vi".

Crash opening logic express 7.1.1 after install pro application support 4.0

I was working a long time ago with logic express in my g4 and g3... after install pro application support 4.0 in may logic works in my imac G4 but crash when is opening in my ibook G3
somebody can help me? thanks
here is the error report:
Date/Time: 2007-07-25 01:41:38.613 +0200
OS Version: 10.4.10 (Build 8R218)
Report Version: 4
Command: Logic Express
Path: /Applications/Logic Express.app/Contents/MacOS/Logic Express
Parent: WindowServer [71]
Version: 7.0.1 (7.0.1(840))
Build Version: 8
Project Name: LogicExpress701_DiskData
Source Version: 840000
PID: 258
Thread: 0
Exception: EXCBADINSTRUCTION (0x0002)
Code[0]: 0x00000002
Code[1]: 0x963761c8
Thread 0 Crashed:
0 com.apple.prokit 0x963761c8 DrawNinePartElementAtIndexWithOperation + 0
1 com.apple.prokit 0x963d5884 -[NSProTextFieldCell drawWithFrame:inView:] + 216
2 com.apple.AppKit 0x937e6d88 -[NSControl drawRect:] + 324
3 com.apple.AppKit 0x937c2858 -[NSView _drawRect:clip:] + 2128
4 com.apple.AppKit 0x937c1e18 -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] + 404
5 com.apple.AppKit 0x937c4b60 _recursiveDisplayInRect2 + 84
6 com.apple.CoreFoundation 0x907ed3ec CFArrayApplyFunction + 416
7 com.apple.AppKit 0x937c1f2c -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] + 680
8 com.apple.AppKit 0x937c4b60 _recursiveDisplayInRect2 + 84
9 com.apple.CoreFoundation 0x907ed3ec CFArrayApplyFunction + 416
10 com.apple.AppKit 0x937c1f2c -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] + 680
11 com.apple.AppKit 0x937c13e0 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 196
12 com.apple.AppKit 0x937e2044 -[NSThemeFrame _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 192
13 com.apple.prokit 0x963acb50 -[NSProWindowFrame _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 92
14 com.apple.AppKit 0x937bb054 -[NSView _displayRectIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:] + 384
15 com.apple.AppKit 0x937b0348 -[NSView displayIfNeeded] + 248
16 com.apple.AppKit 0x937b01b8 -[NSWindow displayIfNeeded] + 180
17 com.apple.AppKit 0x937bb6a8 -[NSWindow _reallyDoOrderWindow:relativeTo:findKey:forCounter:force:isModal:] + 1140
18 com.apple.prokit 0x963888cc -[NSProPanel(_ProSplash) _reallyDoOrderWindow:relativeTo:findKey:forCounter:force:isModal:] + 184
19 com.apple.AppKit 0x938c03f8 -[NSApplication _orderFrontModalWindow:relativeToWindow:] + 512
20 com.apple.AppKit 0x938bffdc -[NSApplication _commonBeginModalSessionForWindow:relativeToWindow:modalDelegate:didEndSelector :contextInfo:] + 544
21 com.apple.AppKit 0x9391e27c -[NSApplication runModalForWindow:] + 124
22 com.apple.logic.express 0x0030236c 0x1000 + 3150700
23 com.apple.logic.express 0x00303710 0x1000 + 3155728
24 com.apple.logic.express 0x003084d8 0x1000 + 3175640
25 com.apple.logic.express 0x0030b810 0x1000 + 3188752
26 com.apple.logic.express 0x0009d174 0x1000 + 639348
27 com.apple.logic.express 0x001e077c 0x1000 + 1963900
28 com.apple.AE 0x914fe960 aeDispatchAppleEvent(AEDesc const*, AEDesc*, unsigned long, unsigned char*) + 208
29 com.apple.AE 0x914fe7fc dispatchEventAndSendReply(AEDesc const*, AEDesc*) + 44
30 com.apple.AE 0x914fe654 aeProcessAppleEvent + 284
31 com.apple.HIToolbox 0x9329a2e0 AEProcessAppleEvent + 60
32 com.apple.HIToolbox 0x932ddf88 ProcessHighLevelEvent + 140
33 com.apple.HIToolbox 0x932ddee0 StandardApplicationEventHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 328
34 com.apple.HIToolbox 0x93296934 DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 692
35 com.apple.HIToolbox 0x9329608c SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 372
36 com.apple.HIToolbox 0x93295f08 SendEventToEventTargetWithOptions + 40
37 com.apple.HIToolbox 0x9329d2cc ToolboxEventDispatcherHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 704
38 com.apple.HIToolbox 0x93296b84 DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1284
39 com.apple.HIToolbox 0x9329608c SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 372
40 com.apple.HIToolbox 0x9329ce90 SendEventToEventTarget + 40
41 com.apple.HIToolbox 0x932ddc04 ToolboxEventDispatcher + 92
42 com.apple.HIToolbox 0x932ddb90 HLTBEventDispatcher + 16
43 com.apple.HIToolbox 0x932dc148 RunApplicationEventLoop + 148
44 com.apple.logic.express 0x001e6584 0x1000 + 1987972
45 com.apple.logic.express 0x0009d40c 0x1000 + 640012
46 com.apple.logic.express 0x0000543c 0x1000 + 17468
47 com.apple.logic.express 0x0000526c 0x1000 + 17004
Thread 1:
0 libSystem.B.dylib 0x9000b348 machmsgtrap + 8
1 libSystem.B.dylib 0x9000b29c mach_msg + 60
2 com.unsanity.ape 0xc000a954 _apeinternal + 37044 (icplusplus.c:27)
3 com.unsanity.ape 0xc0001330 _apeagent + 64 (icplusplus.c:27)
4 libSystem.B.dylib 0x9002bd08 pthreadbody + 96
Thread 0 crashed with PPC Thread State 64:
srr0: 0x00000000963761c8 srr1: 0x000000000008f930 vrsave: 0x0000000000000000
cr: 0x24442244 xer: 0x000000000000001c lr: 0x0000000096377538 ctr: 0x00000000963e3960
r0: 0x0000000000000000 r1: 0x00000000bfffd840 r2: 0x0000000000000000 r3: 0x0000000000000000
r4: 0x0000000000000000 r5: 0x0000000042e40000 r6: 0x0000000041700000 r7: 0x0000000000000000
r8: 0x0000000000172700 r9: 0x0000000000000000 r10: 0x0000000000000002 r11: 0x00000000000000fc
r12: 0x00000000963e3960 r13: 0x0000000000000002 r14: 0x00000000bfffe340 r15: 0x00000000a3296698
r16: 0x0000000000c620c0 r17: 0x00000000bffff6f0 r18: 0x0000000000000000 r19: 0x0000000000000000
r20: 0x0000000000000000 r21: 0x00000000a37b1c84 r22: 0x00000000bfffdf50 r23: 0x0000000000000000
r24: 0x0000000000000000 r25: 0x0000000000000000 r26: 0x0000000000000000 r27: 0x0000000000000001
r28: 0x00000000a07c2244 r29: 0x0000000000c5c070 r30: 0x0000000000c407f0 r31: 0x00000000963774dc
Binary Images Description:
0x1000 - 0x677fff com.apple.logic.express 7.0.1 (7.0.1(840)) /Applications/Logic Express.app/Contents/MacOS/Logic Express
0xd15000 - 0xd34fff com.apple.prokit.TigerPanels 4.0 (672.5) /System/Library/PrivateFrameworks/ProKit.framework/Versions/A/Resources/TigerPa nels.bundle/Contents/MacOS/TigerPanels
0x8fe00000 - 0x8fe52fff dyld 46.12 /usr/lib/dyld
0x90000000 - 0x901bcfff libSystem.B.dylib /usr/lib/libSystem.B.dylib
0x90214000 - 0x90219fff libmathCommon.A.dylib /usr/lib/system/libmathCommon.A.dylib
0x9021b000 - 0x90268fff com.apple.CoreText 1.0.3 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreText.framework/Versions/A/CoreText
0x90293000 - 0x90344fff ATS /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ATS.framework/Versions/A/ATS
0x90373000 - 0x9072efff com.apple.CoreGraphics 1.258.75 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/CoreGraphics
0x907bb000 - 0x90894fff com.apple.CoreFoundation 6.4.7 (368.28) /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x908dd000 - 0x908ddfff com.apple.CoreServices 10.4 (???) /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
0x908df000 - 0x909e1fff libicucore.A.dylib /usr/lib/libicucore.A.dylib
0x90a3b000 - 0x90abffff libobjc.A.dylib /usr/lib/libobjc.A.dylib
0x90ae9000 - 0x90b5bfff com.apple.framework.IOKit 1.4 (???) /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
0x90b71000 - 0x90b83fff libauto.dylib /usr/lib/libauto.dylib
0x90b8a000 - 0x90e61fff com.apple.CoreServices.CarbonCore 681.15 /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonC ore.framework/Versions/A/CarbonCore
0x90ec7000 - 0x90f47fff com.apple.CoreServices.OSServices 4.1 /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServi ces.framework/Versions/A/OSServices
0x90f91000 - 0x90fd2fff com.apple.CFNetwork 4.0 (129.20) /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CFNetwo rk.framework/Versions/A/CFNetwork
0x90fe7000 - 0x90ffffff com.apple.WebServices 1.1.2 (1.1.0) /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/WebServ icesCore.framework/Versions/A/WebServicesCore
0x9100f000 - 0x91090fff com.apple.SearchKit 1.0.5 /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchK it.framework/Versions/A/SearchKit
0x910d6000 - 0x910fffff com.apple.Metadata 10.4.4 (121.36) /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadat a.framework/Versions/A/Metadata
0x91110000 - 0x9111efff libz.1.dylib /usr/lib/libz.1.dylib
0x91121000 - 0x912dcfff com.apple.security 4.6 (29770) /System/Library/Frameworks/Security.framework/Versions/A/Security
0x913db000 - 0x913e4fff com.apple.DiskArbitration 2.1 /System/Library/PrivateFrameworks/DiskArbitration.framework/Versions/A/DiskArbi tration
0x913eb000 - 0x913f3fff libbsm.dylib /usr/lib/libbsm.dylib
0x913f7000 - 0x9141ffff com.apple.SystemConfiguration 1.8.3 /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfi guration
0x91432000 - 0x9143dfff libgcc_s.1.dylib /usr/lib/libgcc_s.1.dylib
0x91442000 - 0x914bdfff com.apple.audio.CoreAudio 3.0.4 /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio
0x914fa000 - 0x914fafff com.apple.ApplicationServices 10.4 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Application Services
0x914fc000 - 0x91534fff com.apple.AE 1.5 (297) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ AE.framework/Versions/A/AE
0x9154f000 - 0x91621fff com.apple.ColorSync 4.4.9 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ColorSync.framework/Versions/A/ColorSync
0x91674000 - 0x91705fff com.apple.print.framework.PrintCore 4.6 (177.13) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ PrintCore.framework/Versions/A/PrintCore
0x9174c000 - 0x91803fff com.apple.QD 3.10.24 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ QD.framework/Versions/A/QD
0x91840000 - 0x9189efff com.apple.HIServices 1.5.3 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ HIServices.framework/Versions/A/HIServices
0x918cd000 - 0x918eefff com.apple.LangAnalysis 1.6.1 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ LangAnalysis.framework/Versions/A/LangAnalysis
0x91902000 - 0x91927fff com.apple.FindByContent 1.5 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ FindByContent.framework/Versions/A/FindByContent
0x9193a000 - 0x9197cfff com.apple.LaunchServices 182 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ LaunchServices.framework/Versions/A/LaunchServices
0x91998000 - 0x919acfff com.apple.speech.synthesis.framework 3.3 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ SpeechSynthesis.framework/Versions/A/SpeechSynthesis
0x919ba000 - 0x91a00fff com.apple.ImageIO.framework 1.5.5 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/ImageIO
0x91a17000 - 0x91adefff libcrypto.0.9.7.dylib /usr/lib/libcrypto.0.9.7.dylib
0x91b2c000 - 0x91b41fff libcups.2.dylib /usr/lib/libcups.2.dylib
0x91b46000 - 0x91b64fff libJPEG.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libJPEG.dylib
0x91b6a000 - 0x91c21fff libJP2.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libJP2.dylib
0x91c70000 - 0x91c74fff libGIF.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libGIF.dylib
0x91c76000 - 0x91cdefff libRaw.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libRaw.dylib
0x91ce3000 - 0x91d20fff libTIFF.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libTIFF.dylib
0x91d27000 - 0x91d40fff libPng.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libPng.dylib
0x91d45000 - 0x91d48fff libRadiance.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libRadiance.dylib
0x91d4a000 - 0x91e28fff libxml2.2.dylib /usr/lib/libxml2.2.dylib
0x91e48000 - 0x91e48fff com.apple.Accelerate 1.2.2 (Accelerate 1.2.2) /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate
0x91e4a000 - 0x91f2ffff com.apple.vImage 2.4 /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.fr amework/Versions/A/vImage
0x91f37000 - 0x91f56fff com.apple.Accelerate.vecLib 3.2.2 (vecLib 3.2.2) /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/vecLib
0x91fc2000 - 0x92030fff libvMisc.dylib /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libvMisc.dylib
0x9203b000 - 0x920d0fff libvDSP.dylib /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libvDSP.dylib
0x920ea000 - 0x92672fff libBLAS.dylib /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libBLAS.dylib
0x926a5000 - 0x929d0fff libLAPACK.dylib /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libLAPACK.dylib
0x92a00000 - 0x92aeefff libiconv.2.dylib /usr/lib/libiconv.2.dylib
0x92af1000 - 0x92b79fff com.apple.DesktopServices 1.3.6 /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/Desk topServicesPriv
0x92bba000 - 0x92de5fff com.apple.Foundation 6.4.8 (567.29) /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
0x92f12000 - 0x92f30fff libGL.dylib /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib
0x92f3b000 - 0x92f95fff libGLU.dylib /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib
0x92fb3000 - 0x92fb3fff com.apple.Carbon 10.4 (???) /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon
0x92fb5000 - 0x92fc9fff com.apple.ImageCapture 3.0 /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/ImageCapture. framework/Versions/A/ImageCapture
0x92fe1000 - 0x92ff1fff com.apple.speech.recognition.framework 3.4 /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecogni tion.framework/Versions/A/SpeechRecognition
0x92ffd000 - 0x93012fff com.apple.securityhi 2.0 (203) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SecurityHI.fr amework/Versions/A/SecurityHI
0x93024000 - 0x930abfff com.apple.ink.framework 101.2 (69) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework /Versions/A/Ink
0x930bf000 - 0x930cafff com.apple.help 1.0.3 (32) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Help.framewor k/Versions/A/Help
0x930d4000 - 0x93101fff com.apple.openscripting 1.2.5 (???) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/OpenScripting .framework/Versions/A/OpenScripting
0x9311b000 - 0x9312afff com.apple.print.framework.Print 5.2 (192.4) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Print.framewo rk/Versions/A/Print
0x93136000 - 0x9319cfff com.apple.htmlrendering 1.1.2 /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HTMLRendering .framework/Versions/A/HTMLRendering
0x931cd000 - 0x9321cfff com.apple.NavigationServices 3.4.4 (3.4.3) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/NavigationSer vices.framework/Versions/A/NavigationServices
0x9324a000 - 0x93267fff com.apple.audio.SoundManager 3.9 /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CarbonSound.f ramework/Versions/A/CarbonSound
0x93279000 - 0x93286fff com.apple.CommonPanels 1.2.2 (73) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CommonPanels. framework/Versions/A/CommonPanels
0x9328f000 - 0x9359dfff com.apple.HIToolbox 1.4.9 (???) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.fra mework/Versions/A/HIToolbox
0x936ed000 - 0x936f9fff com.apple.opengl 1.4.7 /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL
0x936fe000 - 0x9371efff com.apple.DirectoryService.Framework 3.3 /System/Library/Frameworks/DirectoryService.framework/Versions/A/DirectoryServi ce
0x93772000 - 0x93772fff com.apple.Cocoa 6.4 (???) /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa
0x93774000 - 0x93da7fff com.apple.AppKit 6.4.7 (824.41) /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
0x94134000 - 0x941a6fff com.apple.CoreData 91 (92.1) /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData
0x941df000 - 0x942a3fff com.apple.audio.toolbox.AudioToolbox 1.4.5 /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox
0x942f5000 - 0x942f5fff com.apple.audio.units.AudioUnit 1.4 /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit
0x942f7000 - 0x944b7fff com.apple.QuartzCore 1.4.12 /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore
0x94501000 - 0x9453efff libsqlite3.0.dylib /usr/lib/libsqlite3.0.dylib
0x94546000 - 0x94596fff libGLImage.dylib /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dyl ib
0x9459f000 - 0x945b3fff com.apple.CoreVideo 1.4 /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo
0x945f8000 - 0x9463dfff com.apple.bom 8.5 (86.3) /System/Library/PrivateFrameworks/Bom.framework/Versions/A/Bom
0x9475c000 - 0x9476bfff libCGATS.A.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/Resources/libCGATS.A.dylib
0x94773000 - 0x94780fff libCSync.A.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/Resources/libCSync.A.dylib
0x947c6000 - 0x947dffff libRIP.A.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/Resources/libRIP.A.dylib
0x947e6000 - 0x94ab5fff com.apple.QuickTime 7.1.3 /System/Library/Frameworks/QuickTime.framework/Versions/A/QuickTime
0x94b78000 - 0x94be9fff libstdc++.6.dylib /usr/lib/libstdc++.6.dylib
0x94c5c000 - 0x94c7cfff libmx.A.dylib /usr/lib/libmx.A.dylib
0x94d84000 - 0x94eb4fff com.apple.AddressBook.framework 4.0.5 (487) /System/Library/Frameworks/AddressBook.framework/Versions/A/AddressBook
0x94f46000 - 0x94f55fff com.apple.DSObjCWrappers.Framework 1.1 /System/Library/PrivateFrameworks/DSObjCWrappers.framework/Versions/A/DSObjCWra ppers
0x94f5d000 - 0x94f8afff com.apple.LDAPFramework 1.4.1 (69.0.1) /System/Library/Frameworks/LDAP.framework/Versions/A/LDAP
0x94f91000 - 0x94fa1fff libsasl2.2.dylib /usr/lib/libsasl2.2.dylib
0x94fa5000 - 0x94fd4fff libssl.0.9.7.dylib /usr/lib/libssl.0.9.7.dylib
0x94fe4000 - 0x95001fff libresolv.9.dylib /usr/lib/libresolv.9.dylib
0x953f3000 - 0x953f3fff com.apple.DiscRecording 3.1.3 (???) /System/Library/Frameworks/DiscRecording.framework/Versions/A/DiscRecording
0x953f5000 - 0x95478fff com.apple.DiscRecordingEngine 3.1.3 /System/Library/Frameworks/DiscRecording.framework/Versions/A/Frameworks/DiscRe cordingEngine.framework/Versions/A/DiscRecordingEngine
0x954a5000 - 0x954ebfff com.apple.DiscRecordingContent 3.1.3 /System/Library/Frameworks/DiscRecording.framework/Versions/A/Frameworks/DiscRe cordingContent.framework/Versions/A/DiscRecordingContent
0x95fbd000 - 0x95fbffff com.apple.ExceptionHandling 1.2 (???) /System/Library/Frameworks/ExceptionHandling.framework/Versions/A/ExceptionHand ling
0x9636c000 - 0x964f7fff com.apple.prokit 4.0 (672.5) /System/Library/PrivateFrameworks/ProKit.framework/Versions/A/ProKit
0x96c93000 - 0x96cd2fff com.apple.audio.midi.CoreMIDI 1.5 (41) /System/Library/Frameworks/CoreMIDI.framework/Versions/A/CoreMIDI
0x970ba000 - 0x970d9fff com.apple.vecLib 3.2.2 (vecLib 3.2.2) /System/Library/Frameworks/vecLib.framework/Versions/A/vecLib
0xc0000000 - 0xc000efff com.unsanity.ape 1.4.2 /Library/Frameworks/ApplicationEnhancer.framework/Versions/A/ApplicationEnhance r
0xefcf9000 - 0xefd1afff com.apple.LogicLoopBrowser 1.0 /Applications/Logic Express.app/Contents/Frameworks/LogicLoopBrowser.framework/Versions/A/LogicLoop Browser
0xefd37000 - 0xefd4afff com.apple.DfSearchEngineWrapper 1.1.0 /Applications/Logic Express.app/Contents/Frameworks/DfSearchEngineWrapper.framework/Versions/A/DfSe archEngineWrapper
0xefdd8000 - 0xefe35fff com.apple.LoopCore 1.0.1 (1.1.0df) /Applications/Logic Express.app/Contents/Frameworks/LoopCore.framework/Versions/A/LoopCore
0xefe81000 - 0xeff54fff com.apple.AECore 1.0.1 (1.1.0df) /Applications/Logic Express.app/Contents/Frameworks/AECore.framework/Versions/A/AECore
Model: PowerBook4,3, BootROM 4.6.4f1, 1 processors, PowerPC 750 (2.3), 900 MHz, 640 MB
Graphics: ATI Mobility Radeon 7500, ATY,RageM7, AGP, 32 MB
Memory Module: DIMM0/BUILT-IN, 128 MB, built-in, built-in
Memory Module: DIMM1/J12, 512 MB, SDRAM, PC133U-333
Modem: MicroDash, Euro, V.92, 1.0F, APPLE VERSION 2.6.6
Network Service: Ethernet incorporada, Ethernet, en0
Parallel ATA Device: TOSHIBA MK4021GAS, 37.26 GB
Parallel ATA Device: SONY CD-RW/DVD-ROM CRX820E

Nothing like keeping an up to date back up.
You could try an Archive and Install. That is the least harmful way,. and you will lose little. Then, run Software Update, unchecking what may be trouble. Once you get to a good point, make your backup current, and continue that, Daily. Carbon Copy Cloner can do it for free, and without your interaction.

Problems installing Xcode for building iPhone applications

Just got a mac mini today for building iphone applications. I'm new to macs.
Downloaded the iPhone SDK. Installed it. But I saw there are a lot of
packages. Do I need to install them all? I've installed the iPhone ones.
When I launch Xcode I get the 'Welcome to Xcode 3.1', which just looks like
a lot of tutorials. How do I run the Xcode application to build iPhone apps?
Cheers,
John.

you just install XCode and it will install ALL packages, the packages that you see are to be installed one by one for expert users or users that want to have a the newest packages.
Remember: Install the iPhone SDK 2.2
you just go to menu and click File > New Project > iPhone and choose the type of project for the iPhone that you want to use, WebApp, UIApp, etc ...
because you are new to the MAC world and probably never used Objective-C in your live, it is good to start somewhere first, buy a good book of the subject, start with the language (Objective-C) them learn about the framework (Cocoa Touch) and then read all about XCode.
In the meanwhile you can check several websites to start knowing what you going to be able to do one day, here are some examples:
- Writing your first iPhone application (payed movies, first for free)
- iPhone Developer Central
- Apps Amuck
- iPhone SDK Articles
remember that you will need to apply to the iPhone Developer Program in order to submit your SDK Apps to the Apple AppStore.
Updated: You can find several movies on YouTube on how to start building apps to the iPhone, but the most seams to do a bad job cause they are screen casting the entire desktop rather the area that we need, so text will be unreadable on such dimensions.

Problem with form after registering in applications

Hi all,i have developed a new form using template.fmb which i got from AU_TOP.I developed the new form from form builder 10g and registered in applications.Now,when i see my form in applications..there are somethings missing like,
1)Every form in Oracle has a oracle logo on the top left corner of the form.My form has something different logo.
2)When one form is opened,even we can open other forms or navigate to another responsibility.But,when my form is open nothing else works.
Can someone kindly address my problems and give a solution.
Any help is appreciated,
Thanks in advance!!

Hi Sandy;
Please see below note and recheck your step
How to Register a Custom Form in Oracle Applications [ID 133995.1]
Regard
Helios

I using iPod touch (4th Gen) one year plus, from iOS 5 upgrade to iOS 6.1.3 sometime facing the late problem. But after all the application update support iOS 7, now my iPod touch become like snail. too late and application always force close. pls help...

Who can help me ? Any solution...... pls help
I'm very like the iPod Touch, small and easier to carry.

See:
iOS: Troubleshooting applications purchased from the App Store
Contact the developer/go to their support site if only one app.
Restore from backup. See:
iOS: How to back up
Restore to factory settings/new iPod

Open vi reference in exe works in one pc but the same does not in another PC

I have a problem. The exe acts weird.
After building the application to include 3 vis by are opened by vi reference methods, I am able to open it and run. These three vis are included as dynamic vis.Then I copy the same program and ran it in another PC.It produces erros that says about Open Vi referernce. I tried and copy it in to another third PC and it works.There are no llbs involved. What could be the problems?
I am using labview 7.1
Clement

I mean, if the VI cannot be started via VI server the error cluster contain the error code that explain the reason of not starting. Explanation could give a clue like path incorrect or bad VI, etc.
Can you verify that all VI are started?
Message Edited by andre.buurman@carya on 10-20-2008 01:08 PM
Regards,
André
Using whatever version of LV the customer requires. (LV5.1-LV2012) (www.carya.nl)

Does "Open Vi Reference" work differently in 8.5 if a string input is wired to vi path?

SO I was reading the upgrade notes to labview 8.5 and I noticed a change in the "Open VI Reference" function. In 8.2 you can simply wire a string of the vi name to the vi path input of the function, and labview will open a reference to the vi already in memory. But in 8.5 the relative paths have to be the same.
So say I have a vi in memory called window.vi. Its real path is C:\test\window.vi. And let's say its already in memory and its reentrant so I can call it by vi server. I used to be able to just pass a sting containing "window.vi" to the vi path input of "Open VI Reference." I like to do that because I already know the vi is in memory, and it is a big pain to get all the relative paths right between developement and deployed executable. This way I don't have to worry about getting dozens of relative paths right for a bunch of support vi's when I build an installer. Does this mean if I upgrade to labview 8.5 I'll have to change this every single place I did it and then rebuild every installer to include support vi's with relative paths to the exe that are the same as their relative paths to the main vi in the development environment?
-Devin
I got 99 problems but 8.6 ain't one.

Well thank god for that. It is too bad the upgrade notes give no mention of how this impacts the executable environment, since it certainly seems like the executable the biggest and most likely part of the impact. I bet you'll still have a ton of people with relative paths that are wrong in the installed executable but right in development environment. Previously they would have worked even though the relative paths were wrong, but now you'll see errors. By the way, what will happen if they have a relative path in the development environment but in the installed executable they compiled all their vi's into a single exe. Will it error? Do they have to rebuild with those vi's included as support files?
tst,
Check out the notes. I don't know if there is enough there to understand or misunderstand, but I get nervous when they say stuff like this.
Open VI Reference Function
In LabVIEW 8.0.x and 8.2.x, if the name of the VI from the vi path input
matches the name of a VI in memory on that target, LabVIEW returns a
reference to the VI in memory and LabVIEW does not load the VI specified
in the vi path input. In LabVIEW 8.5, if the name of the VI from the vi path
input matches the name of a VI in memory on that target but the paths
differ, the Open VI Reference function returns an error.
Message Edited by billings11 on 09-05-2007 01:01 PM
-Devin
I got 99 problems but 8.6 ain't one.

Slow update of shared variables on RT (cRIO) after building exe

Hi,
I've been struggling with this for the past few days. I am having a problem with slow updating of shared variables on my RT project....but only after building the application into exe's.
The application consists of an RT target (cRIO 9073) sampling inputs at a rate of 1sec. I have a host PC running the front panel that updates with the new acquired values from the cRIO. These values are communicated via shared variables.
Once the cRIO samples the inputs, it writes the values to the shared variables, and then flags the data as 'ready to be read' using a boolean shared variable flag. The hostPC polls this boolean shared variable and updates the indicators on the front panel accordingly.
Now, this worked fine during development, but as soon as I built the RT exe and host exe's, it stopped working properly and the shared variables ended up being updated very slowly, roughly 2-3sec update time.
To give you some more background:
I am running the Labview 2010 v10.0.
I am deploying the shared variable library on the RT device (as the system must work even without the hostPC). I have checked that its deploying using Distributed System Manager, as well as deploying it into the support directory on the cRIO and not the exe itself.
I have also disabled all firewalls and my antivirus, plus made sure that the IP's and subnets are correct and its DNS Server address is set to 0.0.0.0.
There are 25 shared variables all in all, but over half of those are config values only used once or twice at startup. Some are arrays, plus I dont have any buffering and none of them are configured as RT FIFO's either.
The available memory on the cRIO is about 15MB minimum.
What strikes me is that it works fine before building exe's and its not like the cRIO code is processor intensive, its idleing 95% of the time.

Thats exactly what I'm saying, it takes 2-3seconds to update the values.
I have tried taking out the polling on the PC side, and registered an event on the changing of that shared variable and that doesn't do anything to change the slow update time. Even if I stop the PC, and just monitor the shared variables in DSM it updates slowly.
I also tried utilising the "flush shared variables" vi to try to force the update....that does nothing.
I wire all the error nodes religously. Still no luck.
Its very strange, I'm not too sure whats happening here. These things should be able to update in 10ms.

Print VI front panel to file does not work after building executable.

I am using a property and invoke node to print the front panel of my VI to an HTML file. It works fine in the development mode. After Building the application, this subvi will no longer
print the front panel. Is there some special files that included in the build??

You can use the Report Generation VIs to generate the HTML report. Specifically, you could use Append Front Panel Image to Report.vi and Save Report to File.vi to save the image of the panel to an HTML report.
Check out the examples in examples\reports to get a better idea how to use these VIs if you've never used them before.
Good luck,
-D
Darren Nattinger, CLA
LabVIEW Artisan and Nugget Penman

MS office report function does not work after building the appication

I use the MS office report function with a custom excel template my application.
It works properly in de developstate, but after building the application it does not work .
I use office 2000 and Windows XP

jmq wrote:
I use the MS office report function with a custom excel template my application.
It works properly in de developstate, but after building the application it does not work .
What error message if any did you get? It could be a couple things:
1. Did you include the Report Toolkit's dynamic vis in the app's build process?
Ref: Error 7 when Running an .EXE Using VIs from Report Generation Toolkit for MS Office
2. How are you giving the path to you custom template, as a relative or an absolute path? The path will be different for the .exe. You have to strip twice.
Ref: Why Can't My Executable Load My Included File When I Use Relative Path Encoding?
=====================================================
Fading out. " ... J. Arthur Rank on gong."

Open VI reference and paths problem

Hi,
in my project I need to have a VI running independently from the calling VI so I use VI Server and "Open VI reference" to run the VI. However this is not without problems. The VI that I run is not in the same folder, as the caller VI and also not on a fixed location on disk, so I use relative paths (something like "..\subfolder\myVi.vi"). This works in the project and .exe but not e.g. in a .llb file where there seems to be no folder structure anymore.
Actually I'd prefer if this would not use paths on disk at all but if I could somehow create a reference to another VI in my project and it would even work if the VI's location on disk changed (and is updated in the project). I think it is quite confusing that I have to care about physical location of the VI here when I use the project browser for everything else. Is there a way to accomplish this? Or is there even a better way to start a VI that keeps running even after the caller stopped?
Thanks,
Tobias

As far as I've seen, every VI has the path ../Application.exe/currentvi.vi when you are running in a build. Therefore, to open another VI you have to strip the current vi's path once, and add the other vi.
I have written a VI that determines whether or not I'm running from a build, it is attached. It returns true if you're in a build, and also the current vi's path stripped once giving you ../Application.exe.
The way I use the VI is pictured below. I send the stripped path Is Executable returns and the relative path (minus the vi name) into a Select icon which is wired to the boolean Is Executable returns. Then I add the other VI name to the path.
Message Edited by elset191 on 04-21-2009 10:43 AM
Tim Elsey
LabVIEW 2010, 2012
Certified LabVIEW Architect
Attachments:
Is executable.vi ‏8 KB
untitled.JPG ‏7 KB

LabVIEW 8.6.1 Project causes slow Open VI Reference

I have an odd problem with "Open VI Reference.vi".
Case 1.
Open LabVIEW project containing "Main.vi"
Open "Main.vi"
Run "Main.vi"
Execution of "Open VI Reference.vi" take about 2,000ms
Case 2.
Open "Main.vi" - No LabVIEW project open
Run "Main.vi"
Execution of "Open VI Reference.vi" take about 100ms
I converted the project to 8.5 and the problem goes away. I don't have any machines with 8.6.0 to test if this is an issue with 8.6.1 only.
Has anybody else seen something like this?
Solved!
Go to Solution.

Good catch on the type def. It turns out that this is also key to the problem. I cleaned up my example VIs, removed the Type Defs and OpenG VIs. When I ran the cleaned up VIs the problem went away. So, I added a simple type def back to my called VI and the problem was back.
You misunderstand the reason for including gmath into the project. This has nothing to do with the time to load the project from disk. The problem is slow execution of "Open VI Reference.vi" when opening VIs that contain TypeDefs that are in large projects. By including gmath I was able to create a large project without attaching extra VIs.
Open Reference Test - No Project: 11 ms
Open Reference Test - small Project: 105 ms
Open Reference Test - large Project: 753 ms
Code in Zip file is LV2009
Message Edited by Gleichman on 08-21-2009 06:36 PM
Attachments:
Open Ref Test - II.zip ‏62 KB

Open vi reference problems in labview 7 after building an application

Similar Messages

Maybe you are looking for