STANDA MOTOR AND BUILDING AN EXECUTABLE APPLICATION

Hello,
I have some problem to build a executable file from the main labview program.
For other applications and devices i don't have any problems (i build
executable files and use them on other computer without any problems).
But with this stepper motor, the main program and the examples given by the
comapany in Labview works and the executable files don't (By not working i have
no particula error message but no remote control at all).
Has someone met this problem?
I think that there is something wrong during compilation (links are missing or
something like that?)
I would appreciate help on this point
Thanks a lot
Regards
Julien

the config file i rename it in *.txt in order to be able to send on the site
Julien
Attachments:
config_julien_V1.txt ‏1 KB

Similar Messages

  • How do I build an executable w/o installing the runtime engine in the OS?

    Hello everyone
    I have developped an application with LabView 8.01 and build an executable for a customer, this works great, if I have administrator rights. But my customer don't have full administrator rights and they are not able to install the software (Runtime Engine). In LabView 6.0.1, to solve this problem we added the lvrt.dll and some support files directly to the application builder as support files and it worked without to install the runtime engine in the operating system.
    How can this be done in LabView 8.0.1 and which files are needed?
    I am thankfull for any advice.

    hi,
    you always need admin rights to install software.
    I think it's not possible in labVIEW 8.01 to install the runtime without admin rights.
    The costumer only has to  the runtime one time, so he should try to contact his system administrator.
    I've found no workaround for it.
    Best regards.
    Christoph Strasser
    AE/NIG

  • Getting error 'generation failed' when tried to build the CAF application

    Hi All,
    I have created the webdynpro application for the human activity.I have created CAF Application for automated activity.But when I tried to generate and build the CAF application,I am getting an error 'generation failed-com.sap.engine.services.webservices.jaxrpc.exceptions.ProxyGeneratorException: Problem with WSDL file parsing. See nested message.-Problem with WSDL file parsing. See nested message.-unknown protocol: c'
    I am not able to get what does this error mean.Kindly suggest me some solution.
    Regards,
    Pranjali Silimkar

    > In note 1375494, I already installed vcredist_x64.exe (Microsoft Visual C++ 2008 Service Pack 1 Redistributable Package (KB973552)). But even that, the error remained!
    This is the wrong patch - you need the patch for the Runtime 2005, not for 2008.
    Those kernels were build with Visual Studio 2005 and hence you need that runtime.
    Markus

  • LabVIEW 8.5 and building executable (using fxs from Advanced Signal Processing Toolkit)

    Hello out there to NI and Gavin:
    For for building an executable using LabVIEW 8.5 and functions from the
    Advanced Signal Processing toolkit, do we still need to manually copy the
    special set of DLLs related to the toolkit use to the target installation, or are these now included
    within a build file for automatic installation to the target
    installation?
    Thanks,
    Don

    Hi Don,
    I imagine that any improvements made to steps required to build an executable using toolkit-specific vi's would be inherent of the toolkit itself. Meaning, I imagine the inconvenience you experienced would be eliminated with the next release of the Advanced Signal Processing Toolkit.
    Cheers,
    Emilie K. | Applications Engineer

  • Importing "Run and Build Application"

    I've been trying to duplicate my Oracle workspace applications on my local machine. It worked fine for one of my apps, but the second one failed. I exported the file several times in DOS format with Unicode UTF-8, Build Status Override "Run and Build Application", and other fields blank. I imported successfully on my machine, and got to the "Application Install" screen. But the routine then failed with the message:
    ORA-20001: GET_BLOCK Error. ORA-20001: Execution of the statement was unsuccessful. ORA-06550: line 6, column 7: PLS-00103: Encountered the symbol "¿¿¿¿¿¿¿¿4¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿" when expecting one of the following: ( - + case mod new null avg count current max min prior sql stddev sum variance execute forall merge time timestamp interval date 1.4.4.00.33
    When I tried to importing the same file back to the Oracle workspace (to create a backup copy so I could further develop without risk) it also failed at the same point with this message:
    ORA-20001: GET_BLOCK Error. ORA-20001: Execution of the statement was unsuccessful. ORA-06550: line 6, column 7: PLS-00103: Encountered the symbol "䑚⁃敌癡㩥匠汥捥⁴湡攠灭潬敹⁥湡⁤汣捩䈢梠when expecting one of the following: ( - + case mod new null avg count current max min prior sql stddev sum variance execute forall merge time timestamp interval date 1.4.4.00.33
    Any ideas?
    Thanks.
    Bill

    Sergio
    Here is the output from the NLS query:
    PARAMETER VALUE
    NLS_LANGUAGE AMERICAN
    NLS_TERRITORY AMERICA
    NLS_CURRENCY $
    NLS_ISO_CURRENCY AMERICA
    NLS_NUMERIC_CHARACTERS .,
    NLS_CHARACTERSET WE8MSWIN1252
    NLS_CALENDAR GREGORIAN
    NLS_DATE_FORMAT DD-MON-RR
    NLS_DATE_LANGUAGE AMERICAN
    NLS_SORT BINARY
    NLS_TIME_FORMAT HH.MI.SSXFF AM
    NLS_TIMESTAMP_FORMAT DD-MON-RR HH.MI.SSXFF AM
    NLS_TIME_TZ_FORMAT HH.MI.SSXFF AM TZR
    NLS_TIMESTAMP_TZ_FORMAT DD-MON-RR HH.MI.SSXFF AM TZR
    NLS_DUAL_CURRENCY $
    NLS_COMP BINARY
    NLS_LENGTH_SEMANTICS BYTE
    NLS_NCHAR_CONV_EXCP FALSE
    NLS_NCHAR_CHARACTERSET AL16UTF16
    NLS_RDBMS_VERSION 9.2.0.4.0
    Here is the output from the procedure in the other thread:
    nls_language = {AMERICAN}
    nls_territory = {AMERICA}
    nls_characterset = {WE8MSWIN1252}
    add this line to your DAD config:
    PlsqlNLSLanguage AMERICAN_AMERICA.WE8MSWIN1252
    How (or where) do I add this line to my DAD?
    Bill

  • Apex :run and build application

    HI ,
    While exporting apex application from test to prod i gave build status override as run and build application instead of run application only.and then i imported
    i this case according to my knowledge user can run as well as can make changes ....
    is it possible to revert it to run only ....
    if yes how ...
    thanks in advance....

    Yes, from the main screen after logging into workspace, look for "*Manage Services*" link. Under Manage Services, find Manage Application Build Status. There, you can convert application between Run and Build Application to Run Application only and vice versa.
    Ittichai

  • How do I build an air application from swf?

    I have a simple SWF that I have built in FlashPro 5.5
    published for AIR 2.6 player
    It has multi-touch functionality designed for a kiosk installation on MacMini with a magic trackpad
    when I publish/test (F12) it from SDK, the trackpad functions perfectly
    BUT
    when I launch SWF in a stand alone player (or build a executable projector), the mutitouch functionality disappears
    WHAT AM I DOING SO VERY WRONG?

    Steph44 wrote:
    I have inadvertantly deleted the icon to open Adobe Dreamweaver
    Where? From the Dock or the Applicaitons folder?
    The Dock icons are "aliases" or "shortcuts" to the original files  or programs, in this case in your Applications folder.
    Just drag the Adobe Dreamweaver icon out of the Applications folder and position it on the Dock in the old location, it will make another "alias" and the original returns to the Application folder.
    If it's gone from your Applicaiotns folder, look in your Trash can and put it back in the Applicaitons folder
    If not there then open the DMG by double clicking on it and double clicking on the installer file to reinstall it.
    You'll have to update the program and likely enter your serial again.

  • Error while building an executable from vi

    Hello,
    I am trying to make a .exe file from the VI which includes Vision Aquisition Software also and while building it I get a error message--
    Error 1502 occurred at AB_Source_VI.lvclass:Close_Reference.vi -> AB_Build.lvclass: Save.vi -> AB_Build.lvclass:Copy_Files.vi -> AB_Application.lvclass:Copy_Files.vi -> AB_EXE.lvclass:Copy_Files.vi -> AB_Build.lvclass:Build.vi -> AB_Application.lvclass:Build.vi -> AB_EXE.lvclass:Build.vi -> AB_Build.lvclass:Build_from_Wizard.vi -> AB_UI_Frmwk_Build.lvclass:Build.vi -> AB_UI_FRAMEWORK.vi -> AB_Create_Build_Application.vi -> EBUIP_Global_OnCommand.vi -> EBUIP_Global_OnCommand.vi.ProxyCaller
    Possible reason(s):
    LabVIEW: Cannot save a bad VI without its block diagram.
    Can anyone tell me how to solve this problem ?
    Thanks in advance.

    I had done that and did not work.  I did not get rid of the old build defination, but started a brand new one via Tools>Build Application (EXE) from VI...  I got the same error 1502.  Inspecting the offending VI did not yield any obvious problem with the block diagram. 
    Upon searching for error 1502, I found this Know Issue link:
    http://www.ni.com/white-paper/11869/en.  Issue ID 255617 stated:
    Error 1502 can occur if dependencies are placed in non executing case structures
    In previous versions of LabVIEW you could place VIs in a case structure with a constant wired the the case selector. This would load the VIs at runtime. If you have this pattern and attempt to build an executable you could receive error 1502
    Workaround: Don't use unreachable code
    So the issue is I have an case structure with hard coded boolean, so the other case is unreachable.

  • Bus Error: 10 while packaging a Flash Builder 4.6 application containing a native extension (ANE)

    I get this error:
    ld: warning: -ios_version_min not specificed, assuming 4.0
    ld: warning: -dead_strip with lazy loaded static (library) archives has resulted in a duplicate symbol.  You can change your source code to rename symbols to avoid the collision.  This will be an error in a future linker.
    /var/folders/y4/svqv7kzn469_ljcrvw1b99500000gn/T/cmd8085539752601990184.tmp: line 2: 25159 Bus error: 10           "/Applications/Adobe Flash Builder 4.6/sdks/4.6.0/lib/aot/bin/ld64/i686-apple-darwin10-ld64" -ObjC -dead_strip -Z -arch armv7 -syslibroot "/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iP honeOS6.0.sdk" -L/usr/lib -F"/System/Library/Frameworks/" -L"/Applications/Adobe Flash Builder 4.6/sdks/4.6.0/lib/aot/lib" -o "../aot8213014594451590298.tmp" -L"/var/folders/y4/svqv7kzn469_ljcrvw1b99500000gn/T/07f32573-0d2b-42c6-b431-916954d76791" -exported_symbol _main -exported_symbol _ExtInitializer -exported_symbol _ExtFinalizer "extensionglue.o" -lstdc++ -lRuntimeInterpreter.arm-air -lgcc_s.1 -lstdc++.6 -lcrt1.o -lSystem.B -lz -lobjc -framework CoreFoundation -framework UIKit -framework MobileCoreServices -framework CoreGraphics -framework Foundation -framework SystemConfiguration -framework AudioToolbox -framework CFNetwork -framework QuartzCore -framework OpenGLES -framework CoreLocation -framework CoreMedia -framework CoreVideo -framework AVFoundation -framework Security -lcom.pgi.native.extensions.softphone
    Compilation failed while executing : ld64
    The ane was created using this command:
    "/Applications/Adobe Flash Builder 4.6/sdks/4.6.0/bin/adt" -package -target ane SPExtension.ane extension.xml -swc SPTest.swc -platform iPhone-ARM -C ios . -platformoptions platform.xml
    The ANE file seemed to load in my project ok, and build ok.  But when I hit run to package for my ios device, I get the above error.

    Here's the fix in case anyone else runs into this problem.  When Flash Builder is building the deployment during launch, it converts the mapped path to a mangled local path for the ane to find the descriptor to a relative path, which can't be found and throws the null pointer.  Making the Output Folder path actually local to the computer, as opposed to the default that FB creates, resolves the error, and still allows blazeds access from the device.

  • Error when building an executable in BridgeVIEW

    Hi,
    Every time I try to build an executable in BridgeVIEW I get an error that I have to close all VIs before building an EXE, but I only  have the top level VI open. I tried shutting down the PC and restarting but nothing works. I have seen this in LabVIEW, but LV closes them for you.
    Any ideas?
    Thanks.

    Lupita wrote:
    HI,
    You are probably right. So here is what Ive tried:
    1) Restarting my PC. Opening a blank new VI and trying to build an application by adding my "main.vi" as a top level VI. This way I make sure there are NO VIs opened.
    The list that appears on the Build Application menu contains ALL VIs called by my main.vi.
    Thanks again.
    I can't really say that I remember a behaviour like this but considering that the latest BridgeVIEW version corresponds to LabVIEW 4.1 (which was never released) or so, I would say that this is so long ago that my memory might be flaky here.
    And the application builder back then was also not the same as it is now. I'm afraid unless you are going to use a more recent version of LabVIEW together with the DSC Toolkit (which is basically what BridgeVIEW evolved into) there is little cahnge that anybody can help you with this here.
    Rolf Kalbermatter
    Rolf Kalbermatter
    CIT Engineering Netherlands
    a division of Test & Measurement Solutions

  • Error 8 occurred when building an executable due to file permission error?

    I received this error on executable builds from two different .vis.  Other .vis in the project build without incident and the message below doesn't seem to indicate the file that is causing the problem, unless it is the SPT-errors.txt file listed at the end of the error message.
    Visit the Request Support page at ni.com/ask to learn more about resolving this problem. Use the following information as a reference:
    Error 8 occurred at Copy in AB_Engine_Copy_Error_Files.vi->AB_Application.lvclass:Copy_Error_Files.vi->AB_Application.lvclass:Copy_Files.vi->AB_Build.lvclass:Build.vi->AB_EXE.lvclass:Build.vi->AB_Engine_Build.vi->AB_Build_Invoke.vi->AB_Build_Invoke.vi.ProxyCaller
    Possible reason(s):
    LabVIEW:  File permission error. You do not have the correct permissions for the file.
    =========================
    NI-488:  DMA hardware error detected.
    C:\Program Files\National Instruments\LabVIEW 8.5\project\errors\Japanese\SPT-errors.txt

    Hi DanielAllis,
    Like mentioned earlier, there is most likely an application on the internet that you can find and use where you can see what processes are calling specific files or folders to see if that specific file is being used by anything else.  It doesn't sound like this is the root of your problem, but it couldn't hurt to check.  Also, I have seen a similar problem to this with someone who was using the software Subversion and Tortoise with their application.  I am not familiar with this software in particular, but I have attached a link below that goes through the steps that this other person took to try and fix the same error when having this software on their computer.  Let me know if any of this helps!
    http://forums.ni.com/ni/board/message?board.id=170&message.id=172537&query.id=115461#M172537
    Regards
    Noah R
    Applications Engineering
    National Instruments

  • Building an Executable - Not Enough Memory to complete this operation

    I am trying to build an executable from my project, it is quite a large program.  During the build, within the 'initializing build' phase, I get the error message 'not enough memory to complete this operation'.  I have a decent PC running XP and 4GB ram. LabVIEW is using about 1.2GB of ram when the problem occurs.
    This is an application that I've been working on for some time and I have experienced similiar problems before.  To get round it I have added the /3GB switch to the boot.ini file.  However that is no longer working, it complains of a problem loading a dll which seems to have only started happening since moving to LV2012.
    Does anybody have any experience with solving this problem please? It is a bit of a showstopper for me at the moment.
    Thank you,
    Martin

    Hi Martin,
    Adding the 3GB switch is a solution which should still work on your system. 
    I'm a little confused, is the system still complaining about not having enough memory? Or is it just the dll problem?
    And is the error message occuring during the build, or when trying to run the .exe?
    The dll in question is associated with DAQmx. 
    If it is a runtime problem rather than a build problem, it may be that you haven't included the DAQmx driver on the target machine, in which case the answer lies in this document: http://www.ni.com/white-paper/5406/en
    If I've misunderstood, please clarify the exact issue which is currently occuring, and we can continue to troubleshoot.
    Ian S
    Applications Engineer CLD
    National Instruments UK&Ireland

  • Building an executable

    Ive been trying to build an executable to run on a different computer, but I must be doing something wrong.  I have read the NI tips on this subject and I also have the Labview for Everyone book that I have been trying to solve my problem with but I just can't seem to figure it out.
    My program works on my computer, but on the computer I am installing it on (which also has the same version of labview installed) it runs but it doesn't do anything, it just hangs up.  It does not give me any error messages and the program does not break, it just keeps running but doesn't do anything.
    I have attached some screenshots to show how I am building the application in the project explorer.
    One thing I notice is that my application has a bunch of sub.vis, but none of them appear in the project explorer.  I was under the impression that it adds all sub.vis automatically, but maybe I am missing something.
    Also I am confused as to the difference between "Startup VIs" and "Always Included" shown in the image called "Application Builder."

    Adding a VI to a project does not automatically add all subVIs. It doesn't have to. You can add the subVIs yourself if you wish, but it's strictly not necessary. I typically like to see everything in the project file, but some folks don't. Startup VIs refers to the top-level VIs in the application. Normally you'd have just one, but you can have more than one. Always included refers to VIs that you load dynamically. Since they are not directly linked to a VI, in order to make sure they get included with the application you need to put them in that list. This is all explained in the LabVIEW manual. Did you read it?
    As for your issue, your code screenshot implies that you are talking to an instrument. Have you installed the required drivers on the target machine? If your subVIs are using VISA then you should install NI-VISA and NI-488.2. If you're using the plain GPIB functions, then you only need NI-488.2.
    Aside: your use of local variables like that is usually a red flag. Not in the sense that local variables are bad, but it's impossible to say from just the screenshot if you have some sort of race condition. Also, it's not clear what your intention is with error handling. If an error occurs on the first iteration of the loop, that will not prevent subsequent iterations from running, since the string of VIs are controlled from a tunnel, which means each iteration only ever sees the tunnel value at the start of the loop.

  • Why might a VI break when building an executable on one machine versus another?

    I have a large test application that is designed to work on several machines. In the process of testing I go to each machine and open the project on the machine I am testing. When I am satisfied the project is behaving as expected  I build the executable and test that it is working as expected. This is where my problem occurs.
    More Background: This software was originally meant to run one test at a time and was upgraded to run multiple tests at the same time(sharing resources and the like). To accomplish this, another VI was written that opened instances of the original VI (clone). I don't know if this is common, however this has been in use for a while and is known to work even after the migration to the network(probably not the problem).
    My issue is that I can build the software on one machine and it will work on another machine, yet when I try to build the same exact project from the other machine it will no longer open the instance of the original VI. I probed the error wire and it indicates that the VI must be broken. So I open the VI and it has no errors.
    I have no idea how to diagnose this any further. Anyone have any ideas?
    -Nate
    Solved!
    Go to Solution.

    Try mass compiling the entire project hierarchy prior to making a build. Also, if you are dynamically launching VI's, you must put them in the "Always Include" section of a Build Spec.
    Do either of these things help?
    a.lia-user-name-link[href="/t5/user/viewprofilepage/user-id/88938"] {color: black;} a.lia-user-name-link[href="/t5/user/viewprofilepage/user-id/88938"]:after {content: '';} .jrd-sig {height: 80px; overflow: visible;} .jrd-sig-deploy {float:left; opacity:0.2;} .jrd-sig-img {float:right; opacity:0.2;} .jrd-sig-img:hover {opacity:0.8;} .jrd-sig-deploy:hover {opacity:0.8;}

  • Some problems while building tuxedo executables (OS/390 - Open MVS)

    Hi,
    I have a both strange and serious (at least it seems serious to me) problem
    with building tuxedo executables.
    I'd like to link the object files with a library I created (say libmylib.a),
    and the only place I know about to pass some info to the tux builders is the
    env var CFLAGS. In my case the CFLAGS looks as follows: "-L
    /u/myhome/myproject/lib -lmylib", but the linker protests, saying that the
    symbols from object files placed in my library can't be resolved ;(.
    On the other hand if I just take the object files out from the library and
    try to link the executable placing all of them explicitly in the command
    line everything goes smoothly.
    HEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEELP...
    Regards
    Chris
    PS. I use Tuxedo release 6.5

    Hello,
    Welcome to MSDN forum.
    I am afraid that the issue is out of support range of VS General Question forum which mainly discusses
    the usage of Visual Studio IDE such as WPF & SL designer, Visual Studio Guidance Automation Toolkit, Developer Documentation and Help System
    and Visual Studio Editor.
    Because your issue is about ASP.NET web application development, I suggest that you can consult your issue on ASP.NET forum:
    http://forums.asp.net/
     for better solution and support.
    Best regards,
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

Maybe you are looking for