Convert from LabView 6.1 to LabView 6.0

Can anyone kindly save this VI's in 6.0 version. I do not have LV 6.1 and these VI's are written in LV 6.1 version.
Thanks,
Kishor
[email protected]
Attachments:
High_Speed_Data_Logger.llb ‏154 KB

It appears to be one of the example programs provided and as far as I know, it's there in 6.0 (it's a lot older than that I believe). From the help menu, select Find Examples and then go to Hardware Input and Output>DAQ>Solutions. High Speed Data Reader and High Speed Data Logger should both be there.

Similar Messages

Identifying and Converting from an older version of LabVIEW

I have an old .vi program that I am trying to access and run now. I don't know what version of LabView it was written in but I do know it came off of a Windows 95 computer.
Any Suggestions?
Will Huntley
Solved!
Go to Solution.

You said "trying to". Does that mean you've been unsuccessful? On what OS are you trying to run it?
When you open an old VI in a newer version of LabVIEW, if the VI isn't too old, then it will open. If you close the VI you'll get a dialog asking you to save it. The "explain changes" will tell you the version of LabVIEW used to write the VI.
If you cannot open the VI because it's too old, and your LabVIEW is too new (e.g., opening a LabVIEW 5.x VI with LV2011), then you can post a request in the Version Conversion board. If the code is really old (e.g., LabVIEW 3.x or earlier), chances are you will not be able to get it upconverted since versions that old require a special toolkit from NI that is not publicly available.
EDIT: Duplicate answer. Was creating my response while Dennis posted his.

Converting from an older version of LabView

I have VIs written in Labview 3.0 that I would like to convert to 6.1. Does anyone know of any software that will do this? Thanks!
Manny

NI give for free a conversion toolkit. Visit ni.com
"JT" a écrit dans le message de news:
[email protected]..
> mstockma wrote in news:506500000008000000EF000100-
> [email protected]:
>
> > I have VIs written in Labview 3.0 that I would like to convert to 6.1.
> > Does anyone know of any software that will do this? Thanks!
> > Manny
> >
>
> Have you tried opening the vi's in lv6.1? I think the conversion is
> automatic.
>
> JT

Convert from LabVIEW 2011 to LabVIEW 9.0

Please convert from LabVIEW 2011 to LabVIEW 9.0
Attachments:
Watlow Vis.zip ‏76 KB

Looks like somebody forgot to attach the zip file. Here you go.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
Attachments:
Watflow.zip ‏57 KB

Converting from LabView 4.0 to 8.5

I have a Pico Technology TC-08 thermocouple datalogger (RS232). It has drivers for Labview 4.0 but I use Labview 8.5, which says it can't convert the drivers. From the help pages I have understood that there is separate software that can convert from Labview 4.0 to 8.5. Can anyone tell me where I can download or otherwise obtain this software?

Hi EKY,
converted to LV7.1 - should be ok now
But: there's a "missing dll"-error. You have to check this in LV8.5.
There is also no guarantee the dll will work with LV8.5 or maybe new operating system (from Win95 to WinXP or Vista?)
Best regards,
GerdW
CLAD, using 2009SP1 + LV2011SP1 + LV2014SP1 on WinXP+Win7+cRIO
Kudos are welcome
Attachments:
TC081_LV71.LLB ‏29 KB

Convert from Labview 5.1 to labview8.6

Hello Everyone,
Can any one please convert this vi from labview 5.1 to labview 8.6 or labview 2009
Thanks in advance
Nadim
[email protected]
Attachments:
4-Channel Power Spectrum with estimate.vi ‏750 KB

Hi,
Here it is in LV 8 but there are some VI's missing (DAQ)
Kees
Attachments:
4-Channel Power Spectrum with estimate.vi ‏402 KB

How to read and display a signal from my PIC Microcontroller onto Labview

Hi,
I am doing a project on a Pulse Oximeter and i am trying to read and display the signal from my PIC Microcontroller on Labview? How do i go about doing it? I am using the PIC16F877 and also making use of the USART?
How do i implement and initialise the USART in PIC16? What are the steps to be taken, please guide me through the process? The link provides information regarding the USART connection, initialisting and stuff? Is it correct to use these codes in my program?Link: http://ww1.microchip.com/downloads/en/AppNotes/00774a.pdf
Also, i am using the RS232 serial interface to connect to the PC? The connector i am using is the DB9 Connector. Which template and VI can i use? Am i supposed to use the NI-DAQmx and VISA? Also, for my USART connection, i am using the MAX232 Driver which is applicable for my application as i am working with +5V. So far, i have been reading and trying out on Labview and the steps i have taken are:
1) Open a New VI and used the Instrument I/O(Read & Display) template?
2) How do i configure the Instrument I/O Assistant Express VI to read the info from my device connected to COM1?
3) I was reading the Labview Manual, 'Getting Started with Labview' and i was following the steps under Page 55, Communicating with an Instrument. Am i on the right track?
4) How do i check and make sure that the port settings of the I/O Assistant and my PIC Micro Match
Please help me out and guide me through the process. I am student at a polytechnic and i am very new to Labview and the software is used as a development tool for the project. I have a deadline to meet and i hope i can get a response as fast as possible. Your help will be kindly and greatly appreciated. I hope to hear from you guys soon.You can e-mail me all your answers at [email protected]
Thank You
Best regards,
Ashwin
Ashwin Kumar Mansukhani
Attachments:
Getting Started with Labview.pdf ‏901 KB

Hi Ashwin,
I am not familiar with the PIC Microcontrollers, but I am assuming you mean that you have the microcontroller sending out serial data that you want to read on another computer with LabVIEW. Please let me know if this is incorrect.
What type of data is coming out of the serial port? Is it ASCII, or binary? The reason I ask this is that the serial communication in LabVIEW is done through a protocol called VISA, which uses ASCII data to send and receive. You can later convert this data into whatever form you need, but this is what it is designed to read and write.
You can check the settings such as baud rate and data bits in a configuration utility called Measurement and Automation Explorer, or MAX. When you open up the MAX interface, you can expand the Devices and Interfaces entry on the left, and then expand the Ports entry to see your serial port. When you highlight this port, select the Port Settings tab at the bottom of the window, and you can see what the current settings are, and change them if you need to. You can also set these parameters in LabVIEW using the VISA Configure Serial Port VI.
You can also test communication in MAX by right clicking on the correct port and choosing Open VISA Session. Then choose the Basic I/O light blue tab, and then go to the Read tab. When you click execute, it should read in what is coming from the serial port. This will allow you to verify that the correct information is coming in before even trying to acquire the data in the LabVIEW environment.
In LabVIEW, the best resource to use the Basic Serial Write and Read example program that ships with LabVIEW. By examining the block diagram of this program, you will be able to see the basic programming flow of serial communication in LabVIEW.
I hope this information was helpful! Please let us know if there's anything else we can help with.
john
Applications Engineer

CIN: Converting a C String to a LabVIEW String

Hi all,
I have been developing CINs in Microsoft Visual C++ 6.0 for LabVIEW as
project needs. However, I am having a problem with converting a C String
to a LabVIEW String in CIN.
I used two ways to try to make the conversion work that were LStrPrintf
and MoveBlock as stated as following:
1. LStrPrintf
#include "extcode.h"
#include "hosttype.h"
#include "windows.h"
struct teststrct{
const char* test;
struct teststrct testinstance;
typedef struct {
LStrHandle test
} TD1;
CIN MgErr CINRun(TD1 *testcluster, LVBoolean *Error) {
char *tempCStr = NULL;
strcpy(tempCStr, testinstance.test); // this would cause LabVIEW crash!
LStrPrintf(testcluster->test, (CStr) "%s", tempCSt
r);
// but if I assigned tempCStr as tempCStr = "test", the string value
"test" could be passed to LabVIEW without any problems.
2. MoveBlock
#include "extcode.h"
#include "hosttype.h"
#include "windows.h"
struct teststrct{
const char* test;
struct teststrct testinstance;
typedef struct {
LStrHandle test
} TD1;
CIN MgErr CINRun(TD1 *testcluster, LVBoolean *Error) {
char *tempCStr = NULL;
int32 len;
tempCStr = (char *)&testinstance.test; //since strcpy didn't work, I
used this way to try to copy the const char* to char*.
len = StrLen(tempCStr);
if (err = NumericArrayResize(uB, 1L, (UHandle*)&testcluster->test,
len))
*Error = LVFALSE;
goto out;
MoveBlock(&tempCStr, LStrBuf(*testcluster->test), len); // the string
was able to passed to LabVIEE, but it was unreadable.
out:
Did I do anything wrong? Any thougths or suggestions would be very
appreciated!

Thank you so much for your response, Greg. However, I still have problem after making
corresponding modification for LStrPrintf approach:
int32 len;
char tempCStr[255] = "";
strcpy(temCStr, testinstance.test);
len = StrLen(tempCStr);
LStrPrintf(testcluster->test, (CStr) "%s", tempCStr);
LStrLen(*testcluster->test) = len;
LabVIEW crashes. Any ideas?
Greg McKaskle wrote:
> The LStrPrintf example works correctly with the "test" string literal because
> tempCStr= "test"; assigns the pointer tempCStr to point to the buffer containing
> "text". Calling strcpy to move any string to tempStr will cause
> problems because it is copying the string to an uninitialized pointer,
> not to a string buffer. There isn't anything wrong with the LStrPrintf
> call, the damage is already done.
>
> In the moveblock case, the code:
> tempCStr = (char *)&testinstance.test; //since strcpy didn't work, I
> used this way to try to copy the const char* to char*.
>
> doesn't copy the buffer, it just changes a pointer, tempCStr to point to
> the testinstance string buffer. This is not completely necessary, but
> does no harm and is very different from a call to strcpy.
>
> I believe the reason that LV cannot see the returned string is that the
> string size hasn't been set.
> Again, I'm not looking at any documentation, but I believe that you may
> want to look at LStrLen(*testcluster->test). I think it will be size of
> the string passed into the CIN, and it should be set to len before returning.
>
> Greg McKaskle
>
> > struct teststrct{
> > ...
> > const char* test;
> > ...
> > };
> >
> > struct teststrct testinstance;
> >
> > typedef struct {
> > ...
> > LStrHandle test
> > ...
> > } TD1;
> >
> > CIN MgErr CINRun(TD1 *testcluster, LVBoolean *Error) {
> >
> > char *tempCStr = NULL;
> >
> > ...
> >
> > strcpy(tempCStr, testinstance.test); // this would cause LabVIEW crash!
> > LStrPrintf(testcluster->test, (CStr) "%s", tempCStr);
> > // but if I assigned tempCStr as tempCStr = "test", the string value
> > "test" could be passed to LabVIEW without any problems.
> >
> > ...
> > }
> >
> > 2. MoveBlock
> >
> > #include "extcode.h"
> > #include "hosttype.h"
> > #include "windows.h"
> >
> > struct teststrct{
> > ...
> > const char* test;
> > ...
> > };
> >
> > struct teststrct testinstance;
> >
> > typedef struct {
> > ...
> > LStrHandle test
> > ...
> > } TD1;
> >
> > CIN MgErr CINRun(TD1 *testcluster, LVBoolean *Error) {
> >
> > char *tempCStr = NULL;
> > int32 len;
> > ...
> >
> > tempCStr = (char *)&testinstance.test; //since strcpy didn't work, I
> > used this way to try to copy the const char* to char*.
> > len = StrLen(tempCStr);
> >
> > if (err = NumericArrayResize(uB, 1L, (UHandle*)&testcluster->test,
> > len))
> > {
> > *Error = LVFALSE;
> > goto out;
> > }
> >
> > MoveBlock(&tempCStr, LStrBuf(*testcluster->test), len); // the string
> > was able to passed to LabVIEE, but it was unreadable.
> > ...
> >
> > out:
> > ...
> >
> > }
> >
> > Did I do anything wrong? Any thougths or suggestions would be very
> > appreciated!

Reading Waveform (.hws) files from Analog Waveform Editor into LabVIEW causes read errors

Hi Gang,
In my application, I want to create files Using the Analog Waveform Editor and then, through LavVIEW, play them out through an D/A.
I've not been able to read the .hws file into LV. I've tried two methods:
Using the Read Waveform VI in the Waveform palette, yields Error -1821.
I looked in the knowledgebase and found the article "Using the Analog Waveform Editor and HWS Files with Multifunction DAQ Devices" That recommended using the HWS VIs that are a part of the FGEN driver. I tried that and get an Error -21515.
The file I want to read is quite small, only 20 samples. Is there some limitation on .hws files or the Waveform Editor I'm not aware of?
I've attached the file if anyone is willing to experiment. I had to change the extension from .hws to .txt to be able to attach it.
All responses will be appreciated.
Thanks,
Roger
Solved!
Go to Solution.
Attachments:
Havesine.TXT ‏108 KB

Interesting. I tried to look at your file with the low level read .hws file vi's and I too got error -21515. So I tried the NI-HWS express load.vi and it looks like it worked. I'm not familiar with the analog waveform editor...does it store using the dynamic data type? Oh I converted the dynamic data to 1d array of waveforms using the convert from dynamic data.vi.
Using LabVIEW 2010SP1 and TestStand 4.5

Upconvert from Labview 5.1 to Labview 2010

Please convert these VIs (in zip) from labview 5.1 to Labview 2010
Solved!
Go to Solution.
Attachments:
c3d_reader_labview_b.zip ‏864 KB

Attached as 8.2, which you can open.
Note: The VIs in the "Files IO" folder have been deprecated. You should replace them with the single Read from Binary File function.
Attachments:
C3D Reader.zip ‏706 KB

How do I convert an earlier numeric array in LabVIEW 5.x or earlier to a Waveform Data Type in LabVIEW 6i?

I am trying to convert old data arrays in LabVIEW 4.x & 5.x to the new Waveform Data Type in LabVIEW 6i. Please Ref. Doc. LabVIEW 6.0 Upgrades Notes page 7-8 as a source.
Has anyone ever tried it?

try to use Buil Waveform VI after loading old data from files ...
LabView Help : "Build Waveform
Builds a waveform or modifies an existing waveform. If you do not wire an input to waveform, Build Waveform creates a new waveform based on the components you enter. If you do wire an input in waveform, the waveform is modified based on the components you specify. This function is expandable."

How can I get Data from the Sound cart in Labview? Does a VI exist?

How can I get Data from the Sound cart in Labview? Does a VI exist?

Yes, there are VIs for acquiring data from Sound cards. And examples too. If you don't have LabVIEW yet, do a search on NI's site for example VIs.
Khalid

How to read data from a router by using labview

I am a beginner labview. How to read data from a router by using labview ?

What kind of data are you trying to read?
Does the router behave like a webserver that you log into? If so, search the forums for threads discussing HTML.

From Labview 9.0 to Labview 8.2.

I need a conversion, if possible, from Labview 9.0 to Labview 8.2.
Thank you for the support
Attachments:
Write Std Out with Redirection.vi ‏24 KB

attached
WARNING: There is a bug in LabVIEW 8.2 where you cannot use the error cluster to chain together the Call Library Function Nodes. You will need to either create wrapper VIs for each CLFN or you will need to use case structures around each call.
Attachments:
Write Std Out with Redirection.vi ‏28 KB

UDP Error when upgrading from Labview 8.6 to Labview 2009

I recently updgraded from Labview 8.6 to Labview 2009. I am writing an application to stream data to disk from UDP. My VIs run just fine in Labview 8.6, but when I try to run them in Labview 2009 my UDP read times out despite being able to monitor UDP traffic and see that the data is being sent and nothing in the file is changed from 8.6 to 2009. Is there a known issue related to this?

How are you moniting the UDP traffic? Have you verified that the port you are trying to use is actually available? When you installed 2009 there may have been an additional service installed that may have used the port you're trying to use. If you're running on Windows you can use the command "netstat -n -o -a" to see all the ports that are currently in use, as well as the process ID that has that port open.

How to send a command from a vc++.exe to LABVIEW.exe in order to control the button on the LABVIEW.exe

Hello, everyone. Using VC++, I have gotten the handle of a *.exe(built by Labview), but I cannot get the button handle. I want to get the button handle and post the message to control the button. How can I do that? When I use the SPY++, the *.exe(built by Labview) have not any child windows which is very different from the *.exe(built by VC++). In SPY++, what is the LVDChild class? How can I send the message to control the button on *.exe(built by Labview)???
That is to send a command from a vc++.exe to LABVIEW.exe in order to control the button on the LABVIEW.exe. How can I get it ?
Thank you!

hummingbird wrote:
Thank you! But I dont kown how to use vi server to raise a value signalling event. Can we put vi server into the vc program? Can you give me some more information or some examples, hehe!
hummingbird
Checkout the LabVIEW ActiveX server interface in the User Manual in Chapter 20, Windows Connectivity and the VI Server Reference in Chapter 17, Programmatically Controlling VIs.
There is a sample for Visual Basic under examples/comm/VBtoLV.frm, which should be quite simple to translate to Visual C as long as you can figure out the basics of ActiveX programming in VC (I have never done anything with ActiveX in VC). For those basics I would recommend some text book or MSDN.
Rolf Kalbermatter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Convert from LabView 6.1 to LabView 6.0

Similar Messages

Maybe you are looking for