Application Builder arbeitet nicht mit Eurotherm 24XX-Treiber

Hi,
ich muß die Software für einen neuen Teststand schreiben.
Der Teststand beinhaltet u.a. mehrere Eurotherm 2216 und ein Keithley 2700-Messinstrument.
Von Labview ist ein Treiber für die Eurotherm 24XX-Serie erhältlich. Dieser funktioniert (zumindest bei den wenigen Funktionen die wir nutzen) auch bei der 2216-Serie. Ich habe zwei VIs geschrieben: Eines das den Com-Port und den Eurotherm initialisiert, und eines das die Messdaten ausliest.
Will ich nun das VI mit Hilfe des Application Builders in eine .exe-Datei umwandeln, erhalte ich die Fehlermeldung:
Die folgenden Dateien enthalten Links zu ungültigen Hilfedateien. Öffnen Sie die Dateien und korrigieren Sie die Links.
C:\Programme\National Instruments\LabVIEW 8.0\instr.lib\ET24XX\_ET24XX.llb\ET24XX Utility Multiple Write To Registers - Floating Point.vi
In der entsprechenden Datei sind allerdings gar keine Hilfedateien angegeben!
Anbei das VI, das die Fehlermeldung auslöst.
Eine entsprechende Fehlermeldung erhalte ich auch bei dem Labview-Treiber für das Keithley-Messinstrument.
Hoffe, irgendwer kann mir weiterhelfen!!
Attachments:
Eurotherm testen ohne Messwerterfassung.vi ‏10 KB

Remove help path from documentation property page of
ET24XX Utility Multiple Write To Registers - Floating Point.vi
Right klick on VI icon / VI Properties ... / Documentation
Manfred
Attachments:
remove help path.jpg ‏46 KB

Similar Messages

Der Application Builder startet nicht mehr. LabView bricht ab.

Es lassen sich keine Projekte mehr öffnen. LabView 8.0 startet und bricht vollständig ab.
Nach Neuinstallation der Installation 8.2.1, liegt der gleiche Fehler vor.
Auch ein neues Projekt läßt sich nicht öffnen.
Der Application Builder ist registriert und aktiviert.

hallo,
probieren Sie sie datei "labview.ini" im labviewverzeichnis (normal "C:\Programme\National Instruments\LabVIEW 8.2\") zu löschen und LabVIEW neu zu starten.
mfg,
robert h
NI germany
Message Edited by RobertH on 11-08-2007 03:49 AM

Application Builder does not work with Eurotherm 24XX-Driver

Hi,
I have to programm the software for a new teststation including some Eurotherm 2216 and a Keithley 2700-instrument in Labview 8.0.
Labview offers drivers for the Keithley 2700 instrument and a driver for the Eurotherm 24XX-series that works well with the Eurotherm 2216.
But if I try to build an application with the application builder, I receive an error message:
The following files include incorrect links to help files. Open the files and correct the links:
C:\Programme\National Instruments\LabVIEW 8.0\instr.lib\ET24XX\_ET24XX.llb\ET24XX Utility Multiple Write To Registers - Floating Point.vi
I checked this file - there are no links to help files included.
I receive a similar error message for the Keithley-Driver.
I attached the file making the problem.
Would be fine, if someone could help me.
Attachments:
Eurotherm testen ohne Messwerterfassung.vi ‏10 KB

Hi,
I had the same error with my application after I transferred it from LV7 to LV8. I used some external files for documentation of the VI's. LV8 does not find these files anymore (old and new location) Open the VI and add the help file again.
Hope this helps.

Problem mit Script-DAC-Treiber

Hallo
ich habe ein Problem mit einem selbsterstellten Script-DAC-Treiber für mein Navilock GPS Empfänger.
von dem Empfänger bekomme ich ständig über eine Serielle Schnittstell die aktuellen Standortdaten gesendet
diese sehen das so aus:
$GPGGA,061834.500,5146.5823,N,00755.9943,E,1,08,0.8,84.9,M,46.4,M,,0000*68
$GPGSA,A,3,20,11,17,14,23,31,19,28,,,,,1.5,0.8,1.3*3C
$GPGSV,3,1,10,01,83,140,23,11,54,152,19,14,20,042,22,17,31,308,41*70
$GPGSV,3,2,10,19,10,169,16,20,64,251,32,23,20,189,30,28,08,260,29*73
$GPGSV,3,3,10,31,13,098,28,32,72,071,08*79
$GPGLL,5146.5823,N,00755.9943,E,061834.500,A,A*5E
$GPRMC,061834.750,A,5146.5823,N,00755.9942,E,0.99,96.96,130314,,,A*5B
$GPVTG,96.96,T,,M,0.99,N,1.8,K,A*34
$GPGGA,061834.500,5146.5823,N,00755.9943,E,1,08,0.8,84.9,M,46.4,M,,0000*68
$GPGSA,A,3,20,11,17,14,23,31,19,28,,,,,1.5,0.8,1.3*3C
$GPGSV,3,1,10,01,83,140,23,11,54,152,19,14,20,042,22,17,31,308,41*70
$GPGSV,3,2,10,19,10,169,16,20,64,251,32,23,20,189,30,28,08,260,29*73
$GPGSV,3,3,10,31,13,098,28,32,72,071,08*79
$GPGLL,5146.5823,N,00755.9943,E,061834.500,A,A*5E
$GPRMC,061834.750,A,5146.5823,N,00755.9942,E,0.99,96.96,130314,,,A*5B
$GPVTG,96.96,T,,M,0.99,N,1.8,K,A*34
Hiervon interessiert mich nur die $GPRMC Zeile bzw einige Werte hierraus.
In meiner Treiberdatei suche ich also nach dem Trennzeichen, lese von rechts 77 Zeichen und Zerhacke den String dann auf die Daten die ich haben möchte.
Solange ich nur diesen Treibereingang im DAC-Schaltplan verwende funktioniert er auch bestens.
Wenn ich jetzt jedoch noch einen weiteren Treibereingang von z.B. meiner Spider mit reinhänge (natürlich mit anderem Takt, da mir die GPS Position jede Sekunde 1 mal reicht...) und evtl noch einen Sinusgenerator reinlege erhalte ich ständig Fehlermeldungen.
Noch dazu scheint dann die Abarbeitung der Anweisungen im DAC-Treiber-Skript nicht sauber zu funktionieren. So erhalte ich beispielsweise die Meldung das "right" nicht zulässig ist, obwohl ich dieses vorher mit einer IF-Anweisung auszuschließen versuche.
Hat da jemand ne Idee?
Attachments:
GPS-Treiber_ver3.VBS ‏18 KB

Hallo nielscho,
Im empfangenen Datenstrom nach "$GPVTG" zu suchen und darauf zu hoffen, dass die Zeile davor die "$GPRMC" Daten enthält würde ich anders gestalten. Du könntest zunächst den Delimitier auf "$GPRMC" setzen und eine Zeile einlesen. Wenn die Zeile länger als 1 Zeichen ist, kannst du davon ausgehen, dass du den String "$GPRMC" auch empfangen hast. Anschließend der Delimiter auf <CR> oder <LF> setzt werden (du muss das im Hex Dump zu dem Logger nachsehen, was als Zeilenendezeichen übertragen wird.), Anschließend kannst du eine Zeile einlesen. Diese enthält dann die Daten zu der gesuchten Zeile. Alles Weitere sollte sich wie in dem Listing gezeigt interpretieren lassen.
Wenn dieser Treiber in Verbindung mit einem anderen Treiber laufen soll, sollte auf jeden Fall die Messung "asynchron zum Messtakt" erfolgen damit die anderen Treiber durch das Script nicht ausgebremst werden.
Bei den Fehlermeldungen, die beim Betrieb des Treibers auftreten vermute ich einmal, dass hier ein anderer String als der " $GPRMC" empfangen wurde und ausgewertet werden soll.
Im Anhang habe Ich ein GPS Beispiel gespeichert, das stabil läuft.
Gruß
Walter
Attachments:
GPS VBS Driver.zip ‏12 KB

Neuer Flash Payer arbeitet nicht

Mein Rechner ( baujahr 2006 ) arbeitet lediglich mit 1,49 Ghz.
Kann das die Ursache sein, dass die neue Flash Player Version 11.1, die 1,6 Ghz verlangt, nicht funktioniert?

OS = Operating System = Betriebssystem; in Ihrem Fall Windows.
Versuchen Sie
http://forums.adobe.com/thread/885448
http://forums.adobe.com/thread/867968
Falls das immer noch nicht klappt brauche ich die Windows Version & Edition (32-bit, 64-bit).
Welche Files sind in
C:\Windows\system32\Macromed\Flash ?
C:\Windows\syswow64\Macromed\Flash ?

Ich bin gerade auf ein französisches Konto aber ich nicht mit meiner deutschen bezahlen

Ich bin gerade auf ein französisches Konto aber ich nicht mit meiner deutschen bezahlen

Hallo,
wie @Sardun bereits schreibt ist GTA V das von allen drei von dir genannten Spielen mit Abstand das Anspruchvollste, so dass es sich bei deinem "Problem" eigentlich nur um eine Angelegenheit handeln kann, die durch Änderung der Einstellungen in den jeweiligen Spieln, oder durch ein Update des VGA Treibers behoben werden kann.
Die Artikelnummer (P/N) oder Machine Type / Model Name wäre ebenfalls interesssant, ob Du die aktuellsten VGA Treiber von der Lenovo Serviceseite installiert hast, und wie die Einstellungen im Energiemanagement sind.
Auf dem Gerät ist Win 8.1 installiert, richtig?

Problem with logging in to apex application builder listener

I have problem with my settings and am posting this in hope that someone else out there had similar problem and solved it!
I am trying to use reverseproxy to access to our db through apex listener.
It's been all set-up and I can login to the application it self either through proxy or no proxy using the listener.
But when I try to login to apex application builder I cannot do it through proxy(with no proxy, it works).
It just refreshes the login page when I click login....
I tried to upgrade the listener to the latest v1.1(using 1.0.2) but it causes my tomcat to crash...
So solution i am looking for is how to make logging in work through proxy..
In the firebug it is showing that below and few other request status as 302 moved temporariry
http://myserver:8080/testsin/apex/wwv_flow.accept
Where as with no proxy it is saying Found.....
Any thoughts??
Thanks
Sin K

Hello Sin K,
so proxy and Tomcat are located on different machines as well? Is the proxy able to commuicate with the Tomcat on the configured internal ports and is the proxy able to lookup the hostname you configured for the Tomcat?
For the connector, the proxyName and proxyPort should be the parameters the client uses to call APEX. So if your clients should call via http://proxyserver:8080/testsin/apex the settings would be
proxyName=proxyserver
proxyPort=8080Reason for this is that applications (e.g. the APEX Listener) generate there URL references with these parameters.
But does your proxy actually serve on port 8080? And is that port accessible by clients? Do clients accept cookies from that server?
In my case, there is only one 302 which redirects to http://host:port/apex/f?p=4500:1000:sessionid which is correct.
If you look into your first post request in firebug, what's in the request header?
-Udo

Report Generation for Excel does not work after using the Application Builder

I have a VI that writes data to an Excel file using the Report Generation Toolkit. I recently compiled the VI into a single Application (EXE) using the Application Builder. My VI runs its tests properly, but no data is written to Excel. What could be the cause? I don't receive any error messages.

Hi
I usually build exe-files, which sometimes also have report functionality.
Open the Application Builder and check the following things:
1. Add the following vis: _Word Dynamic VIs.vi, _Excel Dynamic VIs.vi They should be located in the directory ..\LabVIEW X.X\vi.lib\addons\_office in the llbs _wordsub.llb and _exclsub.llb (report1.jpg)
2. If you use an Installer, go to the Advanced Settings. There you can select some things to include in the Installer. Check if "NI Reports Support" is selected. (report2.jpg)
These are the things I always do, if I need reports and I never had problems up to now. I made two screen-shots of these settings.
Hope this helps.
Thomas
Using LV8.0
Don't be afraid to rate a good answer...
Attachments:
report.zip ‏25 KB

The executible I build with the application builder does not function the same as my VI file.

I am using a USB 6008 device with the newest DAQmx drivers and Labview
8.2 to make analog voltage readings. Within my main VI I first
create a data folder in the same location as the VI using a property
node and then use case statements to call two sub VIs that create a
data file within the data folder and then collects data. When I use the
application builder to create an executible the resulting file does not
operate the same as the origional VI. The program appears to be
reacting to button presses on the GUI, but there is no indication that
the data folder is being created or that any measurements are buing
made. Are there any known issues that may account for this
anomily?
-Mike
Message Edited by TMBurleson on 10-16-2006 03:09 PM

Are you using the VI Path property, using a reference to the current VI?
I could be wrong, but if you're attempting to use a path relative to the current VI, I think that does indeed change in a built application. If your VI used to be C:\somewhere\foo.VI, then after building its path would actually be C:\somewhere\foo.EXE\foo.vi . Thus, if foo.VI used to try to make a folder like C:\somewhere\datafolder, the built application would be trying to make C:\somewhere\foo.EXE\datafolder , which wouldn't work.
This is sort of a shot in the dark, but does this sound like it might be the case?
EDIT: Dennis beat me to it.Message Edited by kehander on 10-16-2006 03:26 PM

Problem with "Application Builder"

Hello!
I have problem when I am using application builder to convert my program to exe files. MY PROGRAM: I use a main program to copy a template VI in to other VI´s, and then I can execute the copied VI´s from main. When I have tried to convert my program to a EXE file, everything works but not executing the copied VI. The following error messages apperies when I try to execute the copied VI. What does this mean???
BR
Kristian K
Attachments:
error.jpg ‏152 KB

Hello!
Information for users on this discussion forum: the problem was due to 'Build Text' function and when that function was removed the program worked fine. The functionality in the 'Build Text' function could easily be replaced by the 'Format Into String' function.
Regards,
Jimmie A.
Applications Engineer, National Instruments
Regards,
Jimmie Adolph
Systems Engineer Manager, National Instruments Northern Region
Bring Me The Horizon - Sempiternal

Problem with Application build in JDeveloper 11.1.5 to WLS 10.3.5

Hi to everyone, I have a problem with a application build in JDeveloper 11.1.5 and deployed to a standalone WLS 10.3.5 ( with the JRF template appliied , to run adf applications )
When I try access to the page : localhost:7001/myApp , it show me :
"Error 403 Fordbbiben ".
but when I put :
localhost:7001/myApp/index.jspx, it show me :
Error 500--Internal Server Error
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
10.5.1 500 Internal Server Error
The server encountered an unexpected condition which prevented it from fulfilling the request.
and the log is :
<May 8, 2012 9:06:22 PM BOT> <Warning> <oracle.adf.view.rich.component.fragment.UIXRegion> <BEA-000000> <
java.lang.IllegalStateException: The expression "#{bindings.genRegion.regionModel}" (that was specified for the RegionModel "value" attribute of the region component with id "genRegion_dlg") evaluated to null.
This is typically due to an error in the configuration of the objects referenced by this expression.
If it helps, the expression "#{bindings.genRegion}" evaluates to "null".
If it helps, the expression "#{bindings}" evaluates to "null". Now using an empty RegionModel instead.
at oracle.adf.view.rich.component.fragment.UIXRegion.getRegionModel(UIXRegion.java:450)
at oracle.adf.view.rich.component.fragment.UIXRegion._beginInterruptibleRegion(UIXRegion.java:682)
at oracle.adf.view.rich.component.fragment.UIXRegion.processRegion(UIXRegion.java:498)
at oracle.adfinternal.view.faces.taglib.region.RegionTag.doStartTag(RegionTag.java:127)
What can I do to fix the problem ??
Thanks

Analyzing the problem, I created a new ADF application with only a web page (index.jspx) , and deploy it to the WLS, and I access to URL of page and it runs !! ( http:localhost:7001/myApp/faces/index.jspx ).
But, when I ADD A TASK FLOW to the application and deploy to the WLS newly , and try to access to the URL application's ( http:localhost:7001/myApp/faces/index.jspx ) . It show me again :
Error 500--Internal Server Error
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
10.5.1 500 Internal Server Error
The server encountered an unexpected condition which prevented it from fulfilling the request.
and the log is :
<May 10, 2012 19:02:57 PM BOT> <Warning> <oracle.adf.view.rich.component.fragment.UIXRegion> <BEA-000000> <
java.lang.IllegalStateException: The expression "#{bindings.genRegion.regionModel}" (that was specified for the RegionModel "value" attribute of the region component with id "genRegion_dlg") evaluated to null.
This is typically due to an error in the configuration of the objects referenced by this expression.
If it helps, the expression "#{bindings.genRegion}" evaluates to "null".
If it helps, the expression "#{bindings}" evaluates to "null". Now using an empty RegionModel instead.
at oracle.adf.view.rich.component.fragment.UIXRegion.getRegionModel(UIXRegion.java:450)
at oracle.adf.view.rich.component.fragment.UIXRegion._beginInterruptibleRegion(UIXRegion.java:682)
at oracle.adf.view.rich.component.fragment.UIXRegion.processRegion(UIXRegion.java:498)
at oracle.adfinternal.view.faces.taglib.region.RegionTag.doStartTag(RegionTag.java:127)
Why it show me that error when I ADD a Task Flow to the Application ???
Can Anyone help me please ?? I m varios days with this problem. Thanks

Application Builder and Closing

Hi
Already, another problem has arisen. I have developed a simple VI with no big thing inside. I am using an event structure for handling button presses. To quit my application, I have one button, labeled Quit (who would've guessed) which quits the application. I simply wired that button to the quit terminal of the event structure (ok, to the quit terminal of the while structure around the event structure).
I have also built this application with the Application Builder into a .exe file. I managed to get that Run/Pause buttons away. by checking the appropriate checkboxes inside AppBuilder. But now, what happens is as follows:
* I quit my application by using the red X of the window - everything closes down fine, the window disappears *perfect*
* I quit my application by using the button - the program stops, but the run button appears.
How can I avoid that behaviour?
Thanks for your advice

There's a function in Application Control which is used to close LV once everything's done executing. Be careful when using it while developing, as it will close all open vi's. Granted you get the option to save them, but it's annoying nonetheless.
See the attached image
Message Edited by Novatron on 07-10-2006 11:17 AM
Attachments:
Quit.jpg ‏4 KB

Build dll error in application builder 8.6.1

Hello,
I get always an error in the LV 8.6 application builder, when I build a dll. There is only one function in it, that has a string and an error input, and nothing else. I attach a screenshot of the VI prototype, and hier is the error description:
Error 1 occurred at Building DLL.
A component needed for Application Builder does not support the required functionality. This might have been caused by installing an older version of LabVIEW after this version was installed. Reinstall the current LabVIEW version to correct this issue.
Possible reason(s):
LabVIEW: An input parameter is invalid. For example if the input is a path, the path might contain a character not allowed by the OS such as ? or @.
=========================
NI-488: Command requires GPIB Controller to be Controller-In-Charge.
After that I reinstalled LV8.6, I tried to reinstall only the 8.6 app builder, but no success.

Hello,
thank you for the reply.
I have solved the problem. I uninstalled the last installed LV version, this was 8.0. Then ran appbuilder again in 8.6, then I have got an instruction to run applibs\lvdllbuilder\lvdb.exe. Since then works.
regards
Mitulatbati

After installing an application that was created using the Application Builder

After installing an application that I created using the Application Builder I get this error if I try to run " ANY " LabVIEW App's that I have built. "Executable Version 7.1.1 doesn't match Resource File 7.1. Check your configuration."
The way that I tried to fix this is to reload LabVIEW 7.1 and DAQmx 8.0. I am using two NI-6528 switch cards.
After I reload LabVIEW and DAQmx I can run my applications but as soon as I install one on this development machine the error begins again.
The executable that I built works fine on the development machine and any other machine that I try it on but it appears that the Run-Time engine 7.1 becomes corrupt after I run setup.exe for the newly created application.
I have built numerous Installers, setup.exe's in the past without this error. Just this latest one caused this problem to start.
I can NOT upgrade to 7.1.1. I am doing work for many different sections of this factory and I can not force them to upgrade. I've asked. Others supply code for the same machines using LabVIEW 7.1.
I am stuck creating executables and manualing moving the correct files to the target machines.
What can be done?

No. The KB article was talking about a machine with 7.1.1 installed. I have LabVIEW 7.1 installed.
The machine that I am having trouble with is my development machine. LabVIEW 7.1, DAQmx 8.0.
If I build the executable all is fine. I can still run old executables including the one I just built.
If I create the installer all is fine. I can still run old executables including the one I just built.
When I install the app on my development machine the corruption occurs. I can " NOT " run old executables including the one I just built. The subject error pops up.
I have not moved any executables to the other machines yet. I don't want to corrupt others.

Passing arrays with Call Library Function does not work after application builder

Calling a DLL with Call Library Function which requires an array of data works correctly in Labview, but after building an exe with application builder, the call no longer works. Dereferecing the pointer in the DLL retuns all 0s and not the actual values.
Solved!
Go to Solution.
Attachments:
TEST.zip ‏28 KB

I did not run your code because it is a little unclear to me what it does.
Two things:
First, is the DLL you are calling the DLL-ified version of PopUpNames.vi? Then the problem is likely that the panel is not being built into the DLL.
When LabView builds an application / dll, it strips the front panel and block diagram from all VIs that it doesn't think need to show a panel at run time. This reduces file size and increases code security. The App Builder's panel inclusion logic can be overridden by Build Specifications -> Source File Settings -> Remove front panel. A better method is to put a property node on a control in a window you want to show marking it "visible"; this is sufficient to tell the App Builder it should keep the panel.
Currently Source File Settings shows "no dependencies" (clearly incorrect---another evil side effect of Express VIs I guess) but if you change the settings as shown below to keep ALL panels, one might hope the App Builder can figure it to keep the panel when it deconstructs the Express VI. (Alternatively convert the Express VI into a regular one.)
A second comment: I am a bit flummoxed at the larger goal here. You are calling LabView DLL from LabView, which doesn't make a lot of sense, so I assume your larger goal is to call LabView from C or vice-versa. In that case be aware that your DLL is x86 (32-bit) but you are passing 64-bit ints as your pointers. In this case it is 32-bit LabView with 32-bit pointers in embedeed in 64-bit containers calling 32-bit LabView with 32-bit pointers in embedeed in 64-bit containers, so it all works, but if your going to call this from C or whatnot you're going to have to follow that same design.
When calling C code the LabView Call Library Function does have a "unsigned pointer-sized integer" data type that always appears to be 64 bits in the dev env but which actually passes a 64 or 32-bit int to the DLL depending on the environment. The "pointer sized int" has to be 64 bits in the "LabView" part of the code because LabView's strong typing requires the data type to be determined at compile time. Casting all pointers to the largest data type in LabView makes it possible to write platform-independent code, but down at the Call Library level you still have to put the right number of bytes on the stack.

Application Builder arbeitet nicht mit Eurotherm 24XX-Treiber

Similar Messages

Maybe you are looking for