Update to LabVIEW 8.5

Hallo,
ich versuche gerade mein LabVIEW-Programm, das auf der Version 6.0 programmiert wurde auf die neuere Version 8.5 zu übertragen. Ich bekommen beim öffnen des VI mit der Version 8.5 folgende Meldungen:
1. Die Dateidialog-Funktion unterstützt den Eingang für den Datenprotokolltyp nicht mehr.
2. LabVIEW änderte eine Konstante, die mit einer Case-Struktur verbunden war, in ein verborgenes Element, um die Kompatibilität mit LabVIEW 7.1 und älteren Versionen zu erhalten.
Der Rechner auf dem LabVIEW läuft ist an eine Anlage angeschlossen. LabVIEW läuft auf der neuen Version und die Daten werden auf dem Frontpanel angezeigt, jedoch werden keine Daten geschrieben, ich erhalte ein leeres Excel-Sheet.
Liegt dies an einer der beiden Meldungen oben, oder hat dies eine andere Ursache?
Ich hoffe jemand kann mir weiterhelfen!
Danke

Hallo Gerd,
vielen Dank für deine Antwort!
Zu deiner Frage, wie die Daten gespeichert werden, bin ich mich nicht ganz sicher. Ich kann dir nur sagen, dass sie als .log-Dateien ausgegeben werden.
Ich vermute den Fehler in einem SubVI, welches sich Schreiben.vi nennt. Beim Übertragen auf die neuere LabVIEW-Version heisst es, dass das VI "Zeichen in Date schreiben" nicht mehr unterstützt wird. Dafür soll die Funktion "In Textdatei schreiben" verwendet werden. In "OPC.vi" ist das VI "Zeichen in Datei schreiben" auch zu finden. Ich habe es überall ausgetauscht, habe jedoch immernoch keinen Erfolg!
Ich habe "OPC.vi" und "Schreiben.vi" angehängt!
Ich hoffe du kannst mir weiterhelfen
Viele Grüße,
Tristan
Attachments:
OPC.vi ‏303 KB
Schreiben.vi ‏77 KB

Similar Messages

Modification of Global channels In NIMax while Labview Program running, not updating in Labview

Hello,
Okay, here is my issue. I have a program that reads data from a device using global channels in MAX.
Step 1: I open MAX with the systemExecute.vi with the parameters to wait till program finishes.
Step 2: I Modify a channel in Max, for example change the assigned daqMX Scale, or Min Max values.
Step 3: Save channel in Max.
Step 4: Exit MAX with the file exit.
Step 5: The Labview program continues, and I re-read the available global channels and global scales in the Labview vi but the properties have not changed to match what I change in MAX.
If I stop the VI then start it again and read the global channels then the properties get updated. How can I get the channel properties to update in Labview after changes are made in Max without stopping the labview vi and starting it again?

Many properties of the channel can only be modified when the task is not running. Have you tried stopping the task in LV before modifying the parameters, and then re-starting the task?
Dan

Update of Labview

Hello,
I do not know if I am posting correctly but I will try.
I have been using Labview for one year and the most difficulties that I had, it was always with installation and update of Labview. I have few wishes about better work with this from my point of view.
1) As Labview have many modules etc. And serials for each separately module or one for all. I think it would be more easy and interesting that I put DVD/CD then I put my serial and installation program shows me what I can install or for what kind of modules my license is valid. As I was beginner I did not know what is for what and what I can install for my license.
2) Why there is not proper update of Labview? Something which shows me that new software is release or something? And then installation automatic..I am still trying to install SP1 for Labview 2009 but there is still any problem:/ I wanted to install new drivers for my cRIO system but it shows that something still is missing and I do not know how I can find the rest...A NI UPDATE SERVICE never found anything.
3) Removing of the software is not nice neither. Many things are connecting to each other and some I do not know why..For example I have cRIO drivers 3.3.0 and I installed drivers 3.5.1 but as system showed me that I cannot use it because something is missing and I decided to deinstall. Fortunately the new drivers were linked with the old one and I had to deinstall all...and after again install the old one.
It is few things which really annoying me with Labview but I think it should be much easier...
Regards,
Nemesis
Solved!
Go to Solution.

Thank you for answer. Yes, as I know I have all. Please look at the picture. It seems to be ok. As I said in my first post. I wish had a tool that tell me what I have to install in order my Labview works correctly. Like that I have to think and ask people what I suppose to install or what I need still. For me if I install new drivers let say cRIO 3.4 and if I do not have something it should tell me that you need this and this...and eventually download rest...
Regarding before posts. My update service worked correctly but never found anything. As my service was running of date I though that it have should be after one year something new but I did not receive any news or something that I could upgrade. I just received a DVD with new drivers I think November 2009 but it was by post and nothing new.
I like Labview very much it is really great software for automatics/mechanics/electronics and not only. Just I personally think that some things should be easier.
Attachments:
pic.jpg ‏150 KB

Watch the NI-Week 2009 Presentation: Updating the LabVIEW Error Handling Core

The resources for the "Updating the LabVIEW Error Handling Core" NI-Week 2009 Presentation are now online.
See them here: http://lavag.org/topic/10741-updating-the-labview-error-handling-core/
Copyright © 2004-2015 Christopher G. Relf. Some Rights Reserved. This posting is licensed under a Creative Commons Attribution 2.5 License.

I have always gone the latter route when I needed it. I usually use an action engine to keep track of the error messages. Said action engine can be used to combine and suppress errors, as well. I have posted an example below (LabVIEw 7.1). In this case, the error propagation is occurring in a task handler which is processing multiple command/data pairs. The command is set at the beginning of the task and the error handler is sprinkled liberally throughout the task code. In this particular case, the desired behavior is to continue execution on error, but log the errors.
I prefer this type of method because it gives me complete control over the error propagation. It has the down side of requiring more code and effort, but I think it is worth it. I like functionality to be explicit on my block diagrams. It makes long-term maintenance much easier.
This account is no longer active. Contact ShadesOfGray for current posts and information.
Attachments:
ErrorPropagation.llb ‏65 KB

What's the quickest way to update a LabVIEW executable on a FieldPoint module?

I'm developing a complicated LabVIEW 7.0 standalone executable that runs on a FieldPoint FP-2010 module. I believe I'm going through too many steps whenever I change this software; could somebody tell me a faster way to change the code?
Here's the insanely tedious way I'm doing it now:
1. First, it seems I have to �clear� the existing VI from the FieldPoint module by setting its �Disable VI� jumper to ON, then rebooting the FieldPoint module, waiting for it to boot, then setting its �Disable VI� jumper back to OFF, then rebooting the FieldPoint module, and waiting for it to reboot again. If I don�t do this tedious step, the new LabVIEW .exe won�t load later on.
2. In LabVIEW, change t
he execution target to the FieldPoint module ("Operate >> Switch Execution Target >> RT Target ...").
3. Make the RT application launch at boot up (�Tools >> RT Target � Options >> RT Target: Miscellaneous >> Launch Application at Boot-up�).
4. �Tools >> Build Application or Shared Library (DLL) >> Applications Settings >> Set Target to Launch at Boot-up >> Build�
5. Reboot the FieldPoint module yet a third time to get the new .exe code running.
6. Finally, my code will be running on the FieldPoint module.

The startup.exe file is locate in the \NI-RT\STARTUP directory. 'cd NI-RT' then 'cd STARTUP' should get you to the right place after making the connection with ftp. I don't recognize PH_EXEC.EXE. Logging in as anonymous is fine. I don't recall seeing documentation on the file structure and locations on the module but I'm sure there is some. I just wandered around w/ftp.
The program to update the node should be below. Enter the IP address, the green light will confirm the node is found.
The version function scans the existing startup.exe for a string beginning and ending with " RU Version " and prints everything in between as the version.
The autostart function will copy the existing ni-rt.ini file to your computer, mod
ify the autostart as requested, then put the file back. Leaves the copy on the PC, which can be handy.
Send file will request a file of the format startup*.dat which will be renamed startup.exe and ftp'd to the module. Lets you keep version numbers in the filename on the PC side. Your directory structure probably won't match mine so you'll have to browse for your file.
Reboot module reboots the module.
Hope this is useful, let me know if anything doesn't make sense. Thanks.
Matt
Attachments:
RNconfig.exe ‏855 KB

Acrobat Reader 11.0.07 update causes LabVIEW application to crash

Hi All,
I wrote an application that uses the Adobe ActiveX element to display a PDF.
This code used to work fine, but when I updated my acrobat reader from 11.0.06 to 11.0.07 it causes the application to start very briefly displaying the icon in the taskbar but then close (without an error or warning notification).
When downgrading to 10.0.06 the problem was solved.
Perhaps this can be of help for others who are experiencing problems with LabVIEW / Acrobat Reader.
Chris

This is a known problem that everybody is yelling about and the solution is to not upgrade to 11.0.07. You don't have to all the way back to V10. 11.0.06 works fine. Just remember to configure Acrobat to not automatically update itself.
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

Graph does not update in labview

I am writing a vi and am having trouble with a graph. I am collecting some data every 5 seconds within a while loop. If I send my data outside the loop to an xy graph and turn on auto-indexing, I can get the graph I desire. However, the graph doesn't update. In fact, it waits until I abort the vi by pressing the stop button before it ever draws anything on the graph. I am new to Labview, so perhaps I am missing something simple. Any help would be appreciated. I would like my graph to update with every measurement I take (every 5 seconds). Thanks!

> missing something simple. Any help would be appreciated. I would
> like my graph to update with every measurement I take (every 5
> seconds). Thanks!
The problem isn't specific to graphs. Data leaves a loop when the loop
completes, therefore your program states that you want to wait until the
loop completes, then send that data to the graph.
What you want is to place your graph terminal inside the loop. If you
just send an individual point to a graph, that doesn't make a very
interesting plot, so what you really want is to place the graph terminal
inside the loop and plot all the data accumulated thus far. To do this,
add a shift register to the loop and use an array builder to accumulate
the data, plotting it as you go. You probably also want
to popup up on
the left shift register and create a constant to start the loop out empty.
Greg McKaskle

Matlab workspace not getting updated while labview mex file is running

Hi,
Let me start from the overview of the system for better understanding.
The system is to acquire data from a DAQ6070e using labview 7.1 . this data is then to be used in matlab for processing. All this needs to happen in real time hence the data is to be acquired from labview and outputted into matlab in real time.
in order to do this we generated the labview and the matlab codes seperately. After days of hard work we managed to import the labview vi into matlab using a math interface toolkit, but now have run into another interesting problem.
the workspace in matlab is not getting updated during the time the labview vi is running inside matlab. it only updates after the vi has run . for example if i need to monitor the system for 300 seconds then ideally the labview vi should output the samples for each acquisition and output it to matlab, what actually is happening is that the labview keeps running for 300 seconds without outputting any data during those 300 seconds and only outputs the last set of acquisition values at the end of the 300 seconds. Which beats the purpose of the whole program.
Kindly help
Regards
Manuj

Thanks Mate,
What you said about "MEX file will not be able to "store" data between runs" ,i realised in the morning. as a result i dont think your suggestion of for loop will also be effective as labview mex file will not acquire data during matalb code execution and vice versa.
Hence i have decided to do it the other way...we will now try to run the matlab code in labview.
this leads to other problem
As this is a real time operation i need to find out a way of storing the data into computer memory and then reading from it(when i say memory i do not mean writing it to a file and readin from it as that is slow) becasue i think the buffer i am specifying in my AI config is not big enough.
I was thinking maybe i should use a RT FIFO queue but then i have not been able to find out the difference between buffer memory and fifo memory. ie is buffer memory supposed to be the ram memory or is it the hard disk memory?
I am posting the vi here for easy understanding
All help is very much appreciated
Attachments:
RT-loop2ver21.vi ‏231 KB

Parallel port updating with labview

I have a project to do that I will need to control using the parallel port. The problem is that I will need to use more than one pin at a time. An example is, when I press button 1, data pin1 and data pin3 will send a signal, and when I press button 2, data pin2 and data pin4 will send s signal and data pin1 and 3 will stop.
I tried doing that but stopped at the programming stage.
I have attached the file I've just did, and I would be most grateful if you kindly pointed me on how to configure this problem.
note: am using win2000 and the parallel port is working fine and i've tried controlling things with it, to make the question more obvious, how could i control the 8 pins and update them as i like. i've read some articles
and answers but didn't understand well since am new to labview
Best regards,
Attachments:
semifinaltest.vi ‏39 KB

Hi,
find your vi with working parallel port (values should change). You have made a mistake - do not toggle byte/word, the paraport does not support 16bit. In addition I have attached a radio-button selection-vi; this should give an idea, how to select one of xx buttons; maybe the event structure could do the same job for your case. Unfortunately I don't have the time to deliver a complete solution for you....
Hope this helps already. If you have further questions about paraport - mail simply to my .web-address
You will find it by double-clicking on wha@atmel
regards
wha
Attachments:
semifinaltest.llb ‏46 KB
Simulating_Radio_Buttons.llb ‏47 KB

Problems with SCXI-1000 after update from Labview 5.1 to LabView 6

I'm using a SCXI-1000 board to readout temperatures from some Pt-100 sensors. The analog signal going into the SCXI-1000 is correct. The reading by LabView program is not. The SCXI-1000 is connected to the PC via a PCI-1200 bus. I've used this setup for some time with LabView 5.1. Here it worked nicely. Recently I upgraded to LabView 6. Now the readout is not giving the proper values. When I reinstalled Labview 5.1 it was all OK again. When using LabView6 do I need to calibrate of configure the SCXI-1000 for my temperature readout? Are there any known problems with upgrading from LabView5 to Labview6? How can I see which analog values are being read by the SCXI-1000 and to which values they are converte
d? Hopefully you can help me.

Upgrading from different versions of LabVIEW shouldn't be a problem; I would suspect different versions of NI-DAQ first. Make sure you use the Measurement and Automation Explorer (MAX) to configure your card.
To see if it's a driver update issue, when you use the LabVIEW 6 installation CD, choose custom install and don't upgrade your drivers. You may have to browse into your LabVIEW 5 directory and use copies of the VIs from there.

NI Update of LabVIEW -- Trojan detected?

Hi
Having recently upgraded to LabVIEW 10, I installed the new NI Update software (after another Forum message gave that as the solution to a hanging NI Updater dialog). I ran the Updater, which came up with a few critical updates. I told it to go ahead.
While loading the following file (ten minutes ago):
http://ftp.ni.com/support/softlib/labview/labview_development_system/2010/2010%20f2/Windows/32-bit/L...
my Kaspersky (AV 6) virus software has just claimed that the file contains "HEUR:Trojan.Win32.Generic", and has halted the download, waiting on my decision to junk the file or proceed.
I'm assuming that this is a false positive....... but can someone confirm that this is the case?
Many thanks,
Peter Reid
University of Edinburgh

99.99% of the time these are false positives. NI checks their software for viruses before making them available.
If it helps, there was an apparent update of virus signatures by multiple vendors. My Symantec Antivirus started claiming that some software on my PC suddenly had Trojans. They don't.

Should I 'update' my LabVIEW version?

Hi folks,
I have a LabVIEW 8.5.1 version and I work largely with PXI-1033 and its related FPGA, should I update my current version for better performance, user-friendly nature and ofcourse functionalities?
If so, is there a significant cost associated with this upgrade?
Solved!
Go to Solution.

RedAG wrote:
Thanks for the reply, where would I download this and would there be any cost associated with this?
Do a search from the NI home site for "LabVIEW 2012 download". There should be a link at the top. The eval is free. You might have to talk to your NI Rep to get the trial extended. If you kept up the SSP, then upgrading is free. Otherwise, talk to your NI rep to get a quote.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

Conflict of visa32.dll, since update to Labview 8.0 conflict with TEK software

We are Tektronix customers and with Labview
7.1/MAX everything was working ok with their software to communicate
with the oscilloscope from the PC. However, since upgrading to Labview
8.0 on system startup (XP) we get a message:
>
>"Tekvis.3
>
>The iInstalled visa32.dll is not a Tektronix
version of VISA. Either disable this program by removing it from the
startup directory of re-install TEKVISA."
>
>Obviously we would like to carry on using
Labview 8.0 and MAX, but also the Textronix software to grab
oscilloscope measurements without having to swap between these two file
versions. I re-installed Tektronix software but then MAX stopped working
from the NI suite, hence no devices could be seen. I presume that NI
will not be re-writing their new visa32.dll file to be backwards
compatible, will Tektronix be releasing a newer version of the software
that can use the new visa32.dll file? Or perhaps a visa32.dll file
compatible with MAX etc?
I have contacted Tektronix but I got this: "Unfortunately I only have LV 7.1 and, like you, it seems to work fine
for me. A collegue of mine tried this out with abview 8 and didn't seem
to have any problems. Have you contacted NI regarding why TekVisa works
with Labview 7.1 but not version 8?
>Hope you can help,
>
>Best regards,
>
>
>Daniel Hill

Hi DaniBCN
What versions of software are you using? LabVIEW 8 but what about NI-VISA? . You can download the lastest versions from ww.ni.com/downloads.
What scope are you using? What bus (GPIB, ENET, USB)? Here is a great resource to comunicate with tek scopes
http://digital.ni.com/public.nsf/websearch/202E14463D2D819F86256C39005D7828?OpenDocument
I know NI has a great relationship with tektronics (tek has a LV version inside the open scopes, NI has develop a specific version of SignalExpress for Tek scopes)
Hope it helps.
Javier Gutiérrez
NI Aplication Engineering

LabVIEW 8.0.1 Update for Linux

Hello,
I just downloaded the update for LabVIEW for Linux an tried to install like it is described.
The following output occurs:
Installing...
/bin/sh: /soft/natinst/lv801-update/bin/INSTALL.norpm: No such file or directory
/bin/sh: /soft/natinst/lv801-update/bin/INSTALL.norpm: No such file or directory
/bin/sh: /soft/natinst/lv801-update/bin/INSTALL.norpm: No such file or directory
/bin/sh: /soft/natinst/lv801-update/bin/INSTALL.norpm: No such file or directory
Would you like to install NI Example Finder (LabVIEW 8.0.1)? [Ynq]
/bin/sh: /soft/natinst/lv801-update/bin/INSTALL.norpm: No such file or directory
/bin/sh: /soft/natinst/lv801-update/bin/INSTALL.norpm: No such file or directory
LabVIEW package installation complete.
Launching LabVIEW Mass Compile utility.
When I start LabVIEW after the obviously successfull Mass Compile I still see LabVIEW Version 8 (in contrast to Windows where I get 8.0.1).
Is it possible that the file bin/INSTALL.norpm is missing in the tar archive or that something else is broken? I am running Debian GNU/Linux Sarge.
Thanks in advance,
Armin Herzer

hello armin herzer,
did you download the LabVIEW 8.0.1 update and the "lv801-linux-norpm.tar.gz"?
if not, you can get it here lv801-linux-norpm.tar.gz.
regards,
robert h
NI germany

Where i can find the update 5.1.2 for my LabVIEW RT 5.1

I have LabVIEW RT 5.1, and i need to update it to 5.1.2.

Please send an e-mail message to NI Engineers by visiting http://www.ni.com/ask, and select E-mail NI under Communication Method. Select LabVIEW Real-Time as the software platform. In your e-mail message, request the update from LabVIEW RT 5.1 to 5.1.2.
Regards,
Chad H.
Applications Engineering
National Instruments
http://www.ni.com/ask

Update to LabVIEW 8.5

Similar Messages

Maybe you are looking for