LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Netbook suggestions?

Solved!
Go to solution
Do you have an update on this project? Was the netbook you ordered capable enough to handle the job?
0 Kudos
Message 11 of 21
(2,691 Views)

Just got it today and have been firefighting most of today.  I will let you all know when I get things up and running.

 

Cheers, Matt

0 Kudos
Message 12 of 21
(2,686 Views)
Excellent! Good luck!
0 Kudos
Message 13 of 21
(2,668 Views)

I just got a netbook that has windows 7 starter edition.

 

Big bummer! Trying to install LabVIEW runtine 2009 SP1 stops with the error that Windows 7 starter edition is not supported!

 

There seems to be a way to force installation by modifying the setup.ini. However, if I do these modifications, the same error still appears. Is this supposed to work for the 2009 SP1 run-time engine 32bit?

 

Did anyone get this to work? 

 

 

0 Kudos
Message 14 of 21
(2,599 Views)

altenbach wrote: 

There seems to be a way to force installation by modifying the setup.ini. However, if I do these modifications, the same error still appears. Is this supposed to work for the 2009 SP1 run-time engine 32bit?


 

OK, false alarm. Seems I mistyped the ini key 😉
 
(That "..wW.." and "..sS.." is way to hard to spell correctly ;))
0 Kudos
Message 15 of 21
(2,593 Views)

OK, so the KB article from 12-16-2009 says that:

 

"Note: Windows 7 Starter Edition is a supported operating system for National Instruments products. Future installers will install normally on this OS." 

 

However, the LabVIEW 2009 SP1 Run-time was released two months later (2-2010) and apparently still does not count as a "future installer". I think the run-time page should mention this and have a link to the mentioned KB article.

 

0 Kudos
Message 16 of 21
(2,576 Views)
We use the EEE top touchscreens computers. We reload it with XP Pro and we use it for touchscreens for our real-time systems. Works well for us and for not much more than I was paying for just the touchscreens before.
0 Kudos
Message 17 of 21
(2,556 Views)

OK, so it looks like there is some definite interest in this which forces me to respond without everthing that I wanted to show. 

 

Some background first...

 

This netbook is being used as a host interface to interact with two PXI chassis', a Window's 2000 machine and an aircraft data acquisition system (this instrument is being deployed on a P3 for acquisition of measurements characterizing aerosol light absorption/extinction in the atmosphere).  Unfortunately, I (as others) was under the impression until about a month before deployment that each chassis would have it's own individual interface, and therefore we had no network communication nor a platform for the host (hence my initial inquiry here).  So, for the past month I have been struggling to aggregate all of the data acquisition into one simple UI for the two instruments.  If I had my druthers, the systems would have been RT thus junking some of the jitter associated with running the DAQs on Window's machines.  C'est la vie...


The setup...

 

Though I am still working to get all of the communication in line, my initial impression is that the Asus Eee PC 1201N is an excellent platform for the work that I am trying to do.  Most of the heavy lifting is done by the two PXI chassis', leaving only the data storage and display to the host (the Asus netbook).  The network topology looks like this:

Network Topology.png

The two chassis' and the  host are communicating via the the STM library; data is shipped from the two chassis' at a rate of 1 Hz.  On the CRD side (PXI-1) the controller sends back a series of 16 signals representing mean exponential decays acquired at 1 kHz.  These represent the bulk of the data that is shipped - the data itself is decimated before transmission and the signals are each represented by about 80 to 100 integer words.  Including reduced data and housekeeping, the amount of data sent back is quite small - maybe around a couple of Mbs.  Controller 2 (the PAS) sends back considerably more data (about the limit of what is  allowable in terms of bandwidth) representing snapshots of a time domain signal and the resulting frequency domain signals (acquired at a rate of 250 kHz).  All of this data is displayed as it is acquired (1 Hz) with the user being able to send commands asynchronously via the Event Structure.  Data is saved at this same rate (1 Hz) to binary files for both instruments.

 

Now my impression...

 

I am currently running Labview 2009 with SP1 and no real issues regarding installation.  My initial impression is that the dual core ATOM with the stock 2 Gb of memory is more than sufficient for our needs.  There is a lot of  Asus bloatware that is shipped with the computer, but it is easily removed.  In regards to developing with this computer, I would suggest updating to the maximum amount of memory that this computer can be expanded to (4 Gb) - the performance can get kind of jumpy and everything kind of slows down when you call things from the Quick Drop menu - and the screen is quite small (but has awesome resolution so you will be amazed at what can fit on it).

 

That being said, I would definitely recommend this little netbook.  However, as stated before, everthing is not quite complete, so I will provide more info and probably put up some snapshots of what we are actually displaying as well as any hiccups encountered that I have not noted here.

 

Hope all of this helps.

 

Peace, Matt

0 Kudos
Message 18 of 21
(2,537 Views)

Personally I do not see what all the fuss is about here. Netbooks these days are just small PC's. Sure some of the first ones ran Windows CE or whatever they are calling it now. Every netbook I have seen lately comes stock with Windows XP Home Edition or Windows7 Starter Edition. They are all about the same hardware wise 1.2-1.6Gzh Atom CPu 1GB RAM... Etc.

 

I run Labview 2009 on my EeePC-900 (900Mhz celeron) at home and sure it runs slower than the Quad-core desktop I have here at work, but it still runs just fine.

 

 

Message Edited by RTSLVU on 03-29-2010 01:11 PM
========================
=== Engineer Ambiguously ===
========================
0 Kudos
Message 19 of 21
(2,524 Views)

RTSLVU,

 

I think that the fuss is that netbooks are relatively new (in fact there is no firm definition of exactly what is  a netbook) which means that you are bound to hit a few speedbumps (as Christian demonstrated above).  When you are working with tight timelines and budgets, these speedbumps can be potentially big headaches.  As these devices become more widespread and more people begin using them in conjunction with Labview, I think we will all find that what you are saying is true (particularly for newer models).  But until then, it's nice to have the thoughts and opinions of those who have used them before.

 

Cheers, Matt

Message 20 of 21
(2,505 Views)