LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Most recommendable Labview version with Windows XP


@mrociogg wrote:

Hi,

 

Is there a portable version of Labview? If it is not, what is the most recommedable Labview version to install using Windows XP and 1,5 Gb RAM memory? I would like to connect a device (using RS232 port) in order to use a vi file I found for working with this device.

 


Can you attach the "VI File" you found?  One of the things you need to know is what version of LabVIEW the VI uses, as you'll want a compatible version of LabVIEW in order to test out this routine, modify it, and "make it portable".

 

The easiest way that I can think to get your code running on an old Windows XP machine with minimal memory and no access to the Internet is to use another PC with LabVIEW and Web Access to do two things -- build an Executable and download a suitable LabVIEW Run Time Engine that you can install on your Target PC.  You can also, in principle, build an "installer" which sort of wraps these two processes into one, but I've always done the EXE + RTE method, myself.  Note that there are licensing issues involved, but I presume that you have the suitable LabVIEW licenses ...

 

Bob Schor

 

P.S. -- you will probably want to think about a fairly "old" version of LabVIEW.  LabVIEW 7.0, I happen to know, worked fairly well with Windows XP, though I'd probably shoot for 8.6 or 2009 ...

0 Kudos
Message 11 of 29
(2,522 Views)

@Bob_Schor wrote:

@mrociogg wrote:

Hi,

 

Is there a portable version of Labview? If it is not, what is the most recommedable Labview version to install using Windows XP and 1,5 Gb RAM memory? I would like to connect a device (using RS232 port) in order to use a vi file I found for working with this device.

 


Can you attach the "VI File" you found?  One of the things you need to know is what version of LabVIEW the VI uses, as you'll want a compatible version of LabVIEW in order to test out this routine, modify it, and "make it portable".

 

The easiest way that I can think to get your code running on an old Windows XP machine with minimal memory and no access to the Internet is to use another PC with LabVIEW and Web Access to do two things -- build an Executable and download a suitable LabVIEW Run Time Engine that you can install on your Target PC.  You can also, in principle, build an "installer" which sort of wraps these two processes into one, but I've always done the EXE + RTE method, myself.  Note that there are licensing issues involved, but I presume that you have the suitable LabVIEW licenses ...

 

Bob Schor

 

P.S. -- you will probably want to think about a fairly "old" version of LabVIEW.  LabVIEW 7.0, I happen to know, worked fairly well with Windows XP, though I'd probably shoot for 8.6 or 2009 ...


Using LV 7.1 works marvelously on a WinXP machine, but it doesn't have the application builder or projects, so building an executable is a bit of a chore.

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
0 Kudos
Message 12 of 29
(2,502 Views)

To be clear LabVIEW 7.1 might not have application builter, but making an EXE is actually easier in some cases.  Just go to Tools >> Make EXE from VI (I don't remember the exact menu name) then click build, it's that easy for simple EXEs.

 

And then there's the fact that LabVIEW 7.1 doesn't need to activate online, and you can get a fully working IDE with EXE creating functionality with the license key A11A11111.

 

Oh and you can make an EXE run without having to install the runtime engine, just make a folders and put in the right DLLs.  LabVIEW 7.1 was a pretty good version, but there certainly are lots of features missing from modern versions.  Going back that far would be quite difficult, just in finding support, and compatibile drivers/hardware.

0 Kudos
Message 13 of 29
(2,490 Views)

@Hooovahh wrote:

To be clear LabVIEW 7.1 might not have application builter, but making an EXE is actually easier in some cases.  Just go to Tools >> Make EXE from VI (I don't remember the exact menu name) then click build, it's that easy for simple EXEs.

 

And then there's the fact that LabVIEW 7.1 doesn't need to activate online, and you can get a fully working IDE with EXE creating functionality with the license key A11A11111.

 

Oh and you can make an EXE run without having to install the runtime engine, just make a folders and put in the right DLLs.  LabVIEW 7.1 was a pretty good version, but there certainly are lots of features missing from modern versions.  Going back that far would be quite difficult, just in finding support, and compatibile drivers/hardware.


I'm looking at LV 7.1 running on XP right now, and you're right.  It's not as hard as I thought.  It could be that I cut my teeth on LV 7.1 so it was just difficult at the time, and that's what I rememembered.  Actually, most of the same things apply then as it does now.  For instance, we still have to add dynamically loaded VIs manually - we just do it differently now.

 

One of the reasons why I had recommended LV 7.1 was, as you had also mentioned, was because you didn't need to activate it online.

 

About finding support, it's true - but then you would have trouble finding support for XP, itself, these days.

 

I would argue for 7.1 because it is probably one of the most stable versions until you get to maybe 2011...

 

I would argue AGAINST LV 7.1 if you ever wanted to update this code to a leter version.  The jump to DAQmx comes to mind...

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
0 Kudos
Message 14 of 29
(2,479 Views)

Actually any version will work. How well or many hoops you may have to jump through will very. But as many here were saying unless you actually need the development system on this old computer, making an EXE is the way to go.

 

I have a computer in our lab that is a P3 512MB RAM WinXP and I build exe's in LV 2015 that run on it just fine. The only "hoop" I have to jump through his turn off SSE optimisation when building the EXE as a P3 does not support it.

 

If you have to use this computer as a development system, I suggest you try the LabVIEW Home edition, as that is based on LV2014. https://www.labviewmakerhub.com/doku.php?id=get_labview

========================
=== Engineer Ambiguously ===
========================
0 Kudos
Message 15 of 29
(2,469 Views)

@billko wrote:

 

I would argue AGAINST LV 7.1 if you ever wanted to update this code to a leter version.  The jump to DAQmx comes to mind...


LabVIEW 7.1 had DAQmx.  It was the first version I used as well.

0 Kudos
Message 16 of 29
(2,466 Views)

According to the chart, DAQmx was not compatible with labVIEW until LV 8.5.

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
0 Kudos
Message 17 of 29
(2,450 Views)

@RTSLVU wrote:

Actually any version will work. How well or many hoops you may have to jump through will very. But as many here were saying unless you actually need the development system on this old computer, making an EXE is the way to go.

 

I have a computer in our lab that is a P3 512MB RAM WinXP and I build exe's in LV 2015 that run on it just fine. The only "hoop" I have to jump through his turn off SSE optimisation when building the EXE as a P3 does not support it.

 

If you have to use this computer as a development system, I suggest you try the LabVIEW Home edition, as that is based on LV2014. https://www.labviewmakerhub.com/doku.php?id=get_labview


Are you sure this is a good idea?  LabVIEW Home edition specifically states the license is for personal use only.

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
0 Kudos
Message 18 of 29
(2,448 Views)

@billko wrote:

@RTSLVU wrote:

Actually any version will work. How well or many hoops you may have to jump through will very. But as many here were saying unless you actually need the development system on this old computer, making an EXE is the way to go.

 

I have a computer in our lab that is a P3 512MB RAM WinXP and I build exe's in LV 2015 that run on it just fine. The only "hoop" I have to jump through his turn off SSE optimisation when building the EXE as a P3 does not support it.

 

If you have to use this computer as a development system, I suggest you try the LabVIEW Home edition, as that is based on LV2014. https://www.labviewmakerhub.com/doku.php?id=get_labview


Are you sure this is a good idea?  LabVIEW Home edition specifically states the license is for personal use only.


Yeah, good point, but it is worth a try to see if the computer will even be usable as development station.  LabVEW 2016 changed things and just installing LabVIEW 2016 to your development system makes it impossible (even for older previously install LabVIEW versions) to deploy to OS’s older than Windows 7 SP1 09086257FC40063DD50?OpenDocument

 

See also http://forums.ni.com/t5/LabVIEW/LabVIEW-2014-installer-points-to-wrong-minimum-OS/td-p/3321712

========================
=== Engineer Ambiguously ===
========================
0 Kudos
Message 19 of 29
(2,442 Views)

@billko wrote:

According to the chart, DAQmx was not compatible with labVIEW until LV 8.5.


That chart only goes back as far as DAQmx 9.1.5.  Trust me, there were plenty of DAQmx releases before that.  Prime example: DAQmx 9.0.  I specifically remember that release because that is when the TDMS streaming was introduced and saved me months of development.

 

Trust me, I remember from experience that there is a version of DAQmx that will work with LabVIEW 7.1.  I could not tell you what version though.


GCentral
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
"Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5
0 Kudos
Message 20 of 29
(2,430 Views)