Jump to content


Photo
- - - - -

Linux vs Windows


  • Please log in to reply
6 replies to this topic

#1 Doon

Doon

    More Active

  • Members
  • PipPip
  • 43 posts

Posted 02 February 2007 - 03:42 PM

Adding my two cents:

It would also be good to note that some of the add-ons available for LabVIEW are listed as "Windows, Not in Base Package" (e.g., MathScript). You may want to check for add-on availablity as part of your decision.

-H

#2 mermeladeK

mermeladeK

    Active

  • Members
  • Pip
  • 14 posts

Posted 02 February 2007 - 02:14 PM

Hi!!

I am working in the Institute of Space Studies of Catalonia and we're gonna get a license. Because we mainly have computers with Linux we might get a Linux license. However I am wondering if the 2 versions (Win and Lin) are totally equal or they have any differences?

This questions is mainly toward Linux programmers who might have found any problems that Windows programmers haven't found.

Thank you very much!! :)

#3 Tomi Maila

Tomi Maila

    The 500 club

  • JKI
  • 845 posts
  • Location:San Francisco
  • Version:LabVIEW 2011
  • Since:2004

Posted 02 February 2007 - 02:19 PM

The Windows version can call .NET and ActiveX classes. If you are an academic institution, purchase a Academic department license. It costs $5000 and you get professional version of almost all NI software. LabVIEW Mac/PC/Linux are all included.

EDIT: The Academic department license allows anybody in your department to use the licenses for non-commercial projects.

Tomi

EXPRESSIONflow

blog: expressionflow.com

twitter: @expressionflow


#4 LAVA 1.0 Content

LAVA 1.0 Content

    <customize this text>

  • Members
  • PipPipPipPipPipPip
  • 2,827 posts
  • Version:LabVIEW 8.6
  • Since:2009

Posted 02 February 2007 - 03:09 PM

Well, the kind of application you need to develop will define the best version to choose.

IMAQ and DAQ drivers for Linux are often a problem... You should be able to find documentation on NI website about what is/isn't support on Linux version.
I'm absolutely not a fan of windows, but if you have to choose between Linus/MacOS/Windows to develop LabVIEW application, I would recomand to choose Windows it if you want to be sure to avoid drivers nightmare.

Of course as pointed Tomi, if you can afford, a departement license would avoid to have to choose.

#5 mermeladeK

mermeladeK

    Active

  • Members
  • Pip
  • 14 posts

Posted 02 February 2007 - 04:56 PM

Thank you for the valuable information.

I am using the drivers I could found in the Driver Network in National Instruments (http://www.ni.com/devzone/idnet/). The drivers here are not specified to be for Win or Lin. This means they are for both?

Right now the ones being used are the drivers for the Tektronix DPO4000 osciloscopes (http://sine.ni.com/a...0440003BA7CCD71) but I don't know if they are only for Windows. I guess they could be used in Linux as well if they are poster in ni.com. No?

#6 LAVA 1.0 Content

LAVA 1.0 Content

    <customize this text>

  • Members
  • PipPipPipPipPipPip
  • 2,827 posts
  • Version:LabVIEW 8.6
  • Since:2009

Posted 02 February 2007 - 06:15 PM

the drivers for the Tektronix DPO4000 osciloscopes (http://sine.ni.com/a...0440003BA7CCD71) but I don't know if they are only for Windows. I guess they could be used in Linux as well if they are poster in ni.com. No?

This driver is listed as an IVI driver. IVI drivers require some lower level OS specific software. There MAY be IVI drivers for Linux, but you should look for plug-and-play drivers for your instruments.

These are basically VIs that can be loaded on any platform. You can also customize the driver; IVI interfaces are typically DLLs and you can't "see inside". Given a choice, plug-and-play drivers are the way to go :thumbup:

your tkdpo4k has a plug-and-play driver located here

#7 mermeladeK

mermeladeK

    Active

  • Members
  • Pip
  • 14 posts

Posted 03 February 2007 - 12:26 AM

Great info. Ok, so now I know I can use Linux for what I need. The bosses don't seem to interested in getting an academic license right now.

This driver is listed as an IVI driver. IVI drivers require some lower level OS specific software. There MAY be IVI drivers for Linux, but you should look for plug-and-play drivers for your instruments.

These are basically VIs that can be loaded on any platform. You can also customize the driver; IVI interfaces are typically DLLs and you can't "see inside". Given a choice, plug-and-play drivers are the way to go :thumbup:

your tkdpo4k has a plug-and-play driver located here