JNLP and Eclipse Birt Runtime Engine

The Birt report engine requires a path to the jar files that are downloaded. Is there a way to get the install location so that path can be used to setBirtHome(path_to_install).
Dennis

Is there a way to get the install location ...Sure, or rather, use an installer to put the Jar's
in a specific place, then store where that specific
place is, in your 'env. variable' or whatever.
(Note that I, as an end user, can change the
location of the class cache any time I like, so
it is not advisable to try and get the 'path' to it
for any reason.)

Similar Messages

How do CVI7.0 runtime engine and TestStand3.0 runtime engine work in a test system?

I developed code modules from CVI 7.0, and test sequence from TestStand 3.0. Now I want to deploy all to a test system. Should I create distribution kits for CVI and TestStand, and install to a target PC? Do each kit include the RTE? How do the runtime engine work in a system?

hp7550,
I saw your post earlier entitled "what is a run-time engine?". It looks like this post is addressing the same issue.
To answer your questions, it is not necessary to create a distribution kit for your CVI code modules. You can simply install the CVI Run-time Engine, which you can find if you go to www.ni.com and click on the Drivers and Updates link on the left-hand side.
Then you will need to deploy your TestStand system using Tools >> Deploy TestStand System in the Sequence Editor. That tool will go out and gather all the CVI code modules your sequence calls - unless you are calling a DLL or something dynamically inside of a code module; in which case, you need to add that dynamically called DLL (or code module) to your TestStand workspace.
To install the TestStand Run-time Engine, make sure the Install TestStand Engine option is checked on the Installer Options tab of the deployment utility. You can customize what gets installed with the engine by clicking on the Engine Options.
For more information on deployment, see Chapter 14 of the TestStand Reference manual (Help >> Search the TestStand Bookshelf...).
To answer your last question a run-time engine simply gives you access to the compiled code that corresponds to the functions you used from the CVI or TestStand libraries during development.
I hope that helps.
Best Regards,
Matt P.
Applications Engineer
National Instruments

Problem creating dataset using db2 stored procedure in Eclipse BIRT

Hi,
I am using DB2 9.7 Express Edition in Eclipse BIRT(version 2.5.1) for generating reports. I have used Type4 driver for jdbc connection.
For that, I have established jdbc connection using db2jcc.jar and db2jcc_license_cu.jar files.
I have successfully created data source, say DB2BIRT having following requisites-
Driver Class - com.ibm.db2.jcc.DB2Driver ( v3.50)
Driver URL - jdbc:db2://localhost:50000/database_name
User name - user_name
Password - Password
I have written some stored procedures and trying to use resultsets from those stored procedures into my report..
The stored procedures having involvement of only single resultset are working absolutely fine for new dataset using above DB2BIRT.
But, I am unable to create new dataset using stored procedures those having involvement of multiple resultsets.
I am getting following error as -
org.eclipse.birt.data.engine.odaconsumer.PreparedStatement$SequentialResultSetHandler getMoreResults
SEVERE: Cannot get more result sets from the statement.
Cannot get the result set.
SQL error #1: [jcc][10120][10943][3.50.152] Invalid operation: statement is closed. ERRORCODE=-4470, SQLSTATE=null
org.eclipse.birt.report.data.oda.jdbc.JDBCException: Cannot get the result set.
SQL error #1: [jcc][10120][10943][3.50.152] Invalid operation: statement is closed. ERRORCODE=-4470, SQLSTATE=null
com.ibm.db2.jcc.b.SqlException: [jcc][10120][10943][3.50.152] Invalid operation: statement is closed. ERRORCODE=-4470, SQLSTATE=null
at org.eclipse.birt.report.data.oda.jdbc.CallStatement.getMoreResults(CallStatement.java:1760)
at org.eclipse.datatools.connectivity.oda.consumer.helper.OdaAdvancedQuery.getMoreResults(OdaAdvancedQuery.java:214)
at org.eclipse.birt.data.engine.odaconsumer.PreparedStatement$SequentialResultSetHandler.getMoreResults(PreparedStatement.java:5183)
at org.eclipse.birt.data.engine.odaconsumer.PreparedStatement.getMoreResults(PreparedStatement.java:792)
at org.eclipse.birt.data.engine.odaconsumer.PreparedStatement.flushResultSets(PreparedStatement.java:1009)
at org.eclipse.birt.data.engine.odaconsumer.PreparedStatement.close(PreparedStatement.java:980)
at org.eclipse.birt.data.engine.executor.DataSource$DataSourceReleaser.run(DataSource.java:374)
at java.lang.Thread.run(Thread.java:619)
Caused by: com.ibm.db2.jcc.b.SqlException: [jcc][10120][10943][3.50.152] Invalid operation: statement is closed. ERRORCODE=-4470, SQLSTATE=null
at com.ibm.db2.jcc.b.wc.a(wc.java:55)
at com.ibm.db2.jcc.b.wc.a(wc.java:102)
at com.ibm.db2.jcc.b.tk.db(tk.java:3118)
at com.ibm.db2.jcc.b.tk.a(tk.java:1063)
at com.ibm.db2.jcc.b.tk.getMoreResults(tk.java:908)
at org.eclipse.birt.report.data.oda.jdbc.CallStatement.getMoreResults(CallStatement.java:1756)
... 7 more
Moreover, I tried to resolve above issue by changing Driver Class from com.ibm.db2.jcc.DB2Driver ( v3.50) to com.ibm.db2.jcc.uw.DB2StoredProcDriver ( v3.50)
So again while *"Test Connection"* for new Data source using this new driver class for stored procedure, there is an error reflection as -
org.eclipse.birt.report.data.oda.jdbc.JDBCException: The selected driver cannot parse the given url.
at org.eclipse.birt.report.data.oda.jdbc.JDBCDriverManager.testConnection(JDBCDriverManager.java:627)
at org.eclipse.birt.report.data.oda.jdbc.ui.util.DriverLoader.testConnection(DriverLoader.java:120)
at org.eclipse.birt.report.data.oda.jdbc.ui.util.DriverLoader.testConnection(DriverLoader.java:133)
at org.eclipse.birt.report.data.oda.jdbc.ui.profile.JDBCSelectionPageHelper.testConnection(JDBCSelectionPageHelper.java:653)
at org.eclipse.birt.report.data.oda.jdbc.ui.profile.JDBCSelectionPageHelper.access$7(JDBCSelectionPageHelper.java:627)
at org.eclipse.birt.report.data.oda.jdbc.ui.profile.JDBCSelectionPageHelper$7.widgetSelected(JDBCSelectionPageHelper.java:549)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:228)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1176)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3493)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3112)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
at org.eclipse.jface.window.Window.open(Window.java:801)
at org.eclipse.birt.report.designer.ui.dialogs.BaseDialog.open(BaseDialog.java:110)
at org.eclipse.birt.report.designer.data.ui.actions.EditDataSourceAction.doAction(EditDataSourceAction.java:68)
at org.eclipse.birt.report.designer.internal.ui.views.actions.AbstractElementAction.run(AbstractElementAction.java:70)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1176)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3493)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3112)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
Can anybody address my this issue for successful implementation of stored procedure(with involvement of multiple resultsets) for creating Data set in Eclipse BIRT ?
I will be really thankful.
Thanks in advance,
Manasi

Well, in my stored procedure I have used 2 to3 cursors(as per my business logic) and all cursors except one are holding result sets. That exceptional cursor is intended for holding as well as returning result set after call to the procedure. And its perfectly running on db2 and returning the desired output. The problem is with Eclipse. The same procedure is not working in Eclipse BIRT.

LV 6.0 runtime engine not found with labview 6.1

I recently upgraded to LabView 6.1.
Now when I try to run an exe built under 6.02, I get an error that the 6.0 (or compatable) runtime engine could not be found.
I have the developers version of labview 6.1 installed, and the labview runtime engine 6.1 installed.
Do I need to install 6.0 runtime too? (in that case do I need 5.1 ruintime instaled too for exe's built a log time ago)?
Shouldnt the 6.1 RTE be able to run older exe's?
I could find no solution searching this web site.
Thanks
Larry Junek, Certified LabVIEW Developer

Did you install 6.1 wheer 6.0 was?
You may have lost the 6.0 RTE you did not realize you where using.
Yes you need the version of RTE that matches the app.
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

LabVIEW Runtime engine on Windows Embedded Standard 7 P 32/64 bit?

Did anyone ever try to install and run LabVIEW Runtime engine (2011 or later) on Windows Embedded Standard 7 P 32/64 bit?
I am trying to figure out if this will work, for example on a Beckhoff CX5120 embedded PC. I will need to have some simple TCP/IP communication in order to exchange information with another PC, but nothing else, i.e. drivers, etc...
I hope someone tried to do this already. I just don't have the right hardware right now to check it out.
Solved!
Go to Solution.

As NI sells touch panels with WES7 installed here: http://sine.ni.com/nips/cds/view/p/lang/en/nid/210551 it's pretty safe to assume they've used the RTE on WES7.
But yes, it's been done.

NI Developer Suite 8.2 / LV Runtime Engine 8.2 vs 7.1.1

I have NI Developer Suite 8.2 and have installed LabVIEW v8.2 from it onto my development computer. I have converted a LabVIEW 6.1 application to 8.2 and am now setting up an installer build for the application.
When setting up installer build properties, I find NI LabVIEW 7.1.1 Runtime Engine, NI LabVIEW Run-Time Engine 8.0.1, and NI LabVIEW Run-Time Engine 8.2 listed as additional installers that can be included in the build.
Wanting to use the latest and greatest for my application, I have selected Run-Time Engine 8.2 for inclusion in the installer.
Upon testing the installer, I find Runtime Engine 7.1.1 installed, not 8.2.
I checked the development computer (Control Panel->Add/Remove Programs->National Instruments Software) and found only Runtime Engine 7.1.1 installed. I then uninstalled LabVIEW 8.2 and reinstalled it, hoping to be able to specify which runtime engine to install, but there is no option in the installation process for runtime engines.
My question is: what happened to runtime engine 8.2? Why can't I get it installed on my development computer? If it doesn't exist, why is it listed in the installer build properties as an installer that can be included? Is it vaporware?

Hi Igk,
On your development machine, the LabVIEW RTE 8.x will not appear in Add/Remove Programs because it is an invisible MSI Installer. The installer is invisible because other applications (LabVIEW Development environment, for example) are dependent on the RTE. Uninstalling the RTE would cause problems for all the other programs with dependencies, so the option to remove it is not there. If you uninstall all the programs that depend on the RTE, the RTE will be uninstalled with the last program. You can see in the attached image that I don't have LV RTE 8.0, or 8.0.1, or 8.2 in Add/Remove Programs, but it is listed in MAX Software.
If you run this LV installer on a clean PC(without the LV development environment), I havn't tested for sure, but because the application installed depends on the RTE, the RTE still probably won't show up in Add/Remove Programs (but your application will). You can verify the RTE's existance by checking the <Program Files\National Instruments\Shared\LabVIEW Run-Time\8.2> directory and verifying the lvrt.dll version is 8.20.x.xxxx. Also, when the application runs, you will know the RTE exists. Also as TonP mentioned, you can use MAX to verify its installation.
As a side note, I would generally avoid running LV built installers on a development machine that already has LV. Installing the RTE (or any other NI installer) from a LV custom installer will change its installation source stored in the registry from the LV CD where it was originally installed from to the installer that you built. Future repairs of the RTE will then look for this custom installer rather than the original source. If that installer disappears or changes, repairs or uninstalls become more difficult. I usually set up a test machine to test my LV built installers.
Cheers,
Spex
National Instruments
To the pessimist, the glass is half empty; to the optimist, the glass is half full; to the engineer, the glass is twice as big as it needs to be...
Attachments:
820RTE-Installed.jpg ‏127 KB

Run labview exe in other way than runtime engine?

Hi guys
This might be stupid question, but can I run labview's *.exe in other way than in the runtime engine? In these days in have done *exe and installer with runtime engine and give it to the end-user. It does not matter how tiny ur code is, user have to install 40 conponents and then restart computer... How annoying. Is there eny other way? Can i use other programming languages some how?
-AA-

If the runtime is only one out of 40 components, it should not make a big difference for you.
I always tell my users to download and install the runtime engine directly from NI. This needs to be done only once per PC and per runtime version, at which point you can distribute a small installer.
There is also an idea to simplify all this. Please support it.
(It is not reasonable to be able to build an executable with embedded runtime, that would make a LabVIEW 2009 executable 100+MB in size. (We had that back in LabVIEW 4.0, where each 20kb VI turned into a 3+MB executable, which was significant in the days of 1GB drives.)
Message Edited by altenbach on 12-16-2009 11:42 AM
LabVIEW Champion . Do more with less code and in less time .

Linux VI with Runtime Engine Only

Hi,
We're trying to start a VI on a Linux system, with only the runtime engine installed. But we're having a few problems...
First, if the runtime engine installed without errors ("rpm --install labview71-rte......i386.rpm" and "rpm --install labview-rte-aal......i386.rpm") how can I know for sure that it's working? I can't find any file that indicates that it is installed...
Is it possible (just like under windows) to start a VI with only the runtime engine? What should I call on the shell to start a VI?
Is it possible to run a windows VI under Linux, with only the runtime engine? I read somewhere on www.ni.com that to run a VI a rte of the LabVIEW version used to build the VI is needed. But is LV7.1 for Linux the same version as LV7.1 for windows? Is the Linux runtime engine capable of running the windows VI?
In short, what we like to do is: Use windows to develop some VI's with serial communication. Copy the VI's to a Linux system. Start the VI's.
Any ideas are greatly appreciated.
Wiebe.

"shoneill" <[email protected]> wrote in message news:[email protected]...
Wiebe,I wrote that the binary code is OS dependent, not independent.  Please re-check my post (and your reference to my post to rule out cheeky editing.... )Regarding running a linux VI on linux without the development
You're right. Let's blame it on the language barier (on my side), and today being fryday. Still I don't see why assembler code can't be the same on two exactly the same i386 processors. The OS stuff should be handled in the runtime engine, and the add's mul's, call's etc. are the same. But I haven't given in much thought, and never tried anything like that. I'm sure their will be some problems.
environment, I wouldn't know since I've never used LV on linux (yet).  I thought the original duscussion was about running a VI from one platform on another without requiring the development environment to re-compile. 
It was about running a VI on Linux with only the rte. And what's needed to make this happen.
Can't you just build a wrapper VI to call the VI from a built application (provide path and hey presto, it can be called dynamincally.....no?)I also agree that a bit more multi-platform support would ultimately help NI, but I can understand
Yes, if we had an application builder for Linux, we could make a wrapper. It would solve the licensing problem. Perhaps someone can make a Linux application wrapper/vi starter for LV8.2 (we'd be happy with any version though)?
About the support.. Somehow someone forget to put all the Linux documentation on ni.com.
the thinking behind it.  Not that I agree, I just understand Further, I believe the run-time is required to prevent each and every LV application being huge.  But sometimes I wish we could distribute without theis run-time Stigma (or better - have the choice).You've raised an interesting point by questioning the existance of the run-time engine......Shane.Message Edited by shoneill on 02-09-2007 04:01 PM
Someone ought to make a virtual machine that can execute LabVIEW's executable code inside a vi, and simulate the runtime engine at the same time : ) It will take some time though...
Regards, Wiebe.

Small runtime engine for newer labview versions?

A few times in the past I have created simple LabVIEW standalone executibles. I did this in 8.6 and used the runtime engine minimal installer instead of the full version. This resulted in an installation package size of 30-35 Meg.
I agin need to create a simple executible but have not seen a minimum runtime installer for any LabVIEW version since 8.6
Are there any minimal runtimes for other versions?
The default 2014 runtime is 264 Meg!!! It is hard to explain to a customer why a simple "Hello World" program requires a 200+ Meg download.
Solved!
Go to Solution.

Jack Dunaway has documented a way of segmenting the run time engine, basically only including the pieces of it you need.
https://connect.wirebirdlabs.com/knowledgebase/articles/172999-segmenting-the-run-time-engine
And here is an idea exchange item on it.
http://forums.ni.com/t5/LabVIEW-Idea-Exchange/Segment-the-LabVIEW-Run-Time-Engine-RTE-to-ONLY-Necess...
Unofficial Forum Rules and Guidelines - Hooovahh - LabVIEW Overlord
If 10 out of 10 experts in any field say something is bad, you should probably take their opinion seriously.

Several question s about runtime Engine, application builder and labview player

I am a little confused by all the options to distribute a program.
Please help bij answering (one of) the following questions:
1. Does an application built with the application builder always need the LV runtime engine? The LV runtime engine is 33 Mb to download!
2. Is there anyway to make a 'normal' executable that runs on a windows machine, without any supporting installed software?
3. What is the advantage of the labview player above the runtime Engine?
All questions refer to the latest software versions of NI software
Thanks in advance,
Regards,
Ferry

ferry1979 wrote:
1. Does an application built with the application builder always need the LV runtime engine? The LV runtime engine is 33 Mb to download!
Yes, the runtime engine contains all the stuff that is common to all LabVIEW applications. This is not any different than e.g. the Visual basic runtime (VBrun...) or dforrt.dll for Fortran.
If you built the application, you can strip it a little bit by including the runtime with the installer and leaving out unneeded modules (see image from the 7.1 builder).
The advantage of a seperate runtime engine is that applications are very small. The runtime needs to be installed only once. On any broadband connection, 33MB is peanuts. I distribute everything without runtine, but tell people to download and install the runtime directly from NI.
(In LabVIEW 4, no runtime was needed, with the disadvantage that even the simplest program was multiple megabytes. Not an efficient solution).
(Maybe in a few years LabVIEW will be so prevalent that the LabVIEW runtime will be part of a standard OS install ;
2. Is there anyway to make a 'normal' executable that runs on a windows machine, without any supporting installed software?
No. See above.
3. What is the advantage of the labview player above the runtime Engine?
The two are quite different. The labview player is more a simple educational tool, because it lets users inspect the diagram. It is not designed for any serious application deployment.
Message Edited by altenbach on 08-21-2005 10:05 AM
LabVIEW Champion . Do more with less code and in less time .
Attachments:
runtime.png ‏24 KB

Labview 8 Application Builder and VISA Runtime Engine

Hi,
I am using Labview 8 Application Builder and everything is working fine except for 1 small thing. My program makes use of some of the VISA functions and when I build the application I'm having to include the VISA Runtime Engine Installer as a separate item on the CD to make the .exe file work.
What I would ideally like is for people who want to use the application to run the installer and that all necessary components (including the VISA Runtime Engine) are also installed in the one installation. At the moment they're having to do 2 installations and I would like to streamline this.
Is this possible?
Ken

Hi,
this How-To explains about making those selections and including the different drivers :
http://zone.ni.com/reference/en-XX/help/371361A-01/lvhowto/add_installers_to_build/
and this tutorial covers the screenshots a little more step by step.
http://zone.ni.com/devzone/conceptd.nsf/webmain/5ADBC06AC32E508A8625706E0062EBD1
Hope that helps
Sacha Emery
National Instruments (UK)
// it takes almost no time to rate an answer

Cannot load Runtime engine verion 7.0, only 8.0 and later versions are supported

Hi,
I am new to using third party labview drivers. I have a labview driver for Chroma 63600 loads that I want to use in TestStand 2012.
However when I load the vi. I get an error 'cannot load Runtime engine verion 7.0, only 8.0 and later versions are supported'
I have Labview Runtime Engine version 7.0 Installed on my Windows 7 machine.
Could anyone please let me know, How I could resolve this issue?
Please see attached driver for Chroma Loads
Solved!
Go to Solution.
Attachments:
chr63600_LabView_V11.zip ‏866 KB

To avoid more confuison,Here is the scenario,
The version that was on the driver attached is from the driver manufacturer.
I do not have any version of labview INSTALLED on my system. I am using the driver in Test Stand 2012 using a labview adapter.
I make sure I match the VI version and the run time engine version on TestStand 2012 to load the VI.
But for this specific driver, I was not successful in loading the VI at all.
As I understood that only 8.0 OR LATER are supported on TS 2012, I have asked to upconvert the driver to work with 8.2.1 Labview runtime engine.
I have now got a.LLB file of the driver mass compiled in Labview 2012 from discussion boards( and also attached here). I have tried the mass compiled LLB file on TS2012 but still have issues loading the VI as it moans about different version of SUB VIs.
However I am still trying to fix this version incomaptibilies. Any help would be much appreciated

Make the installer for my executable run the DAqcarddriver and runtime engine installer automatically

*Hi
I would like to know how to make the installer for my executable run the DAqcarddriver and runtime engine installer automatically
I would like to include run time engine and the drivers of my daqcard(AI16XE50),( and maybe Ni daq or anything else needed?) in order to make my application portable for other computers on OS win98 and winXP .
How can I do that
thank you in advance
Olivier

Olivier,
What version of LabVIEW are you using to build your application? On a remote computer you should only need the drivers you are using and the Run-Time Engine. You can attach installers to LabVIEW 8 installers, but for previous versions you will have to add it by opening the installer configuration page, configuring your installer and then configure the Advanced properties. This will allow you to attach a EXE to the installer which you can run. Also depending on the version of LabVIEW will affect the OS version that you will be able to install the RTE on. LabVIEW 7.0 is the last version that can be installed on Windows 98.
Please let me know if you have any further questions and please include the version of LabVIEW you are using. Thanks!
Andy F.
National Instruments

USB/Serial Drivers and App Builder Installer Questions...are drivers included in the Installer with the LV runtime engine?

Hello all,
I'm wondering if someone can help me out with how drivers and all are treated with applications distributed with App Builder, used to create a stand alone, full install of app and labview engine with Installer.
What has happened is, my application was created using the NI branded USB to RS232...and USB to RS485, and they work great.
On the application when running..you fire it up, it finds the USB to serial device, and I have a dropdown that finds the available COM ports to use (along with setting parity, etc).
I've installed on different computers (without previous labview installs) with the installer. They all worked.
The customer has received the installer....and despite us telling them to use the NI branded USB/Serial interfaces..they are trying to work with a different USB/serial cable.
They say the COM ports aren't even showing up when they run the installed application.
So, I'm not sure where to start. Is this a driver issue? Does the App Builder Installer...install the drivers for the interfaces I was using with it? Is there a way for the person to find and install a driver on their own...or would I have to somehow find out a driver for what they use....then, basically redo the App Builder Installer build...to include that driver with the executable I send back out?
I guess I basically need a better understanding of how drivers for external access/communications are handled when you use App Builder to create a stand alone application complete with the labview runtime engine...and nothing else.
Thank you in advance,
cayenne

The main thing is that LV uses VISA to talk to serial port whether native on the machine or from USB dongles that you plug into the computer. It sounds to me like their dongles aren't working.
Can the customer see the ports in the Windows Device Manager? Can they access them through something like hyperterminal? How does your program find the USB/Serial devices?
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

RunTime Engine and Tdms Files

Hello,
I have built a application with Labview 8.2.0, NI DAQmx 8.3 and NI USI TDMS
Plugin 1.0.
My appli work very good on my developpement computer, but when I install the
appli on computer with RunTime Engine 8.2.0, NI DACmx 8.3 and NI USI TDMS
Plugin 1.0, I have a error. If I use RunTime Engine 8.2.1, NI DACmx 8.5 and NI
USI TDMS Plugin 1.0, I have a error to.
The error is 2500.
How I can use my appli with a run time ????!!
Thanks

Hello,
I suggest you to reinstall everything on the second machine, because what you did seemed to be the right thing to do, you must install the same run-time version as your LV version (what you did at first) and every soft or plugin you VI needs.
I really think it will work... (I hope)
Regards
Richard Keromen
National Instruments France
#adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
>> Découvrez, en vidéo, les innovations technologiques réalisées en éco-conception

JNLP and Eclipse Birt Runtime Engine

Similar Messages

Maybe you are looking for