Introducing LabVIEW 2009

[Coq_Rouge]

I have not used mathscript. But I can see why some people are irritated. And it is always a dumb idea to start to charge users for functions they have used for some time. It is like buying a new car. And then show up to get the key to your new car, you find out that in a strange way the backseat and driving lights has become extras. I know mathscript is popular in academic circles. So I guess some will come up with a free solution...

[Ray.R]

---

Intaris wrote:

---

I still have a PC with MS Office 2000 installed.  IMHO the best version they brought out.

---

Ditto..

My main PC has Office 2000, and  luv it.

I gave my wife my Office 2003.  It's okay, although I do like Outlook 2003.

I TOTALLY hate 2007.  Totally sucks.  Really hate it.  Did I mention that I hate msuff office 2007?  I hate it.. 

Never went to VISTA and never will.

All the above to say that the latest versions are not necessarily the greatest versions.

[Coq_Rouge]

I would gladly have paid some money to get rid of all Express VIs. But I guess that is not an option yet in Labview. But perhaps NI should start to charge extra for that scamped work of programming.

[hecmar.arreola]

@ Jeffery -

Let me respond to your inquiry on what I use MathScript for.  LabVIEW G-Code is not suited well for step-by-step calculations as well as iterative calculations.  Lots of time I’m faced with other engineers providing a MathCAD or Matlab worksheet that contains a sequence of calculations that I have to have work in my software that I develop using LabVIEW.  MathScript makes it easy to put these equations into LabVIEW and properly document the calculation line-by-line.  In fact, it was one of the major selling points for my company to go with the Professional Development System version of LabVIEW over the other versions.  Further, the subscription based model was chosen so that we have access to new features as they are released from National Instruments.  Instead of receiving new features, National Instruments is taking away features that we thought was part of our deal.  This is really underhanded.  I’ve spoken to my boss about these changes, and unless NI rectifies the situation I doubt we will continue the subscription based service and go with whatever version we last land with and live with it.

[Magma]

Jeffery:

I'm using LabVIEW and NI hardware to stream multichannel 24-bit DSA readings of a weak (mV to uV) ultralow-frequency repetitive signal superimposed on a much higher (1-10 V) time-varying background. After streaming a ~250 MB TDMS file, I convert it to a MATLAB-readable binary form, close LabVIEW, and use MATLAB to remove the background, apply a statistically robust trimmed mean stacking algorithm, and then work with the extracted signal waveform.

I'm pretty sure I could execute everything in LabVIEW, but time constraints were a factor and I was able to do the development work faster and easier in MATLAB. So if I can import my MATLAB routines to LabVIEW with minimal rewriting, great.

[hecmar.arreola]

-------

Unfortunately, the MathScript compiler doesn't treat functions and scripts differently in the "Real-Time" context verse the "Desktop" context.  We don't have a clean way of separating the functionality of the two contexts, providing different "products" or "experiences".

-------

Did the original creaters of the MathScript compiler leave National Instruments and the current programming staff are incapable or working on it?  Saying "we can't do it because the software we wrote doesn't allow us to" does not make any sense and sounds like a poor excuse.  Surely there is a way to impliment something that is fair to the users who have no interest in RT or MathScript in RT.

[Neil.Pate]

New favourite feature of LV2009.

Ctrl-Space (to open quick drop)

Ctrl-SHIFT-t

violla! The control/indicator labels on the BD are automatically aligned to the left/right.

See more about these here

Thanks Darren!!!!

[Jason_P]

Just to put my 2 cents in on the Mathscript changes.  I work with scientists who are familiar with Matlab but not LabVIEW.  They generate Matlab code as part of their work.  I've been taking their code and dropping it into LV MathScript nodes to shorten our initial development time.  When time permits, I change the Mathscript to native LV code for speed. 

LabVIEW's license costs have been easily justified at my company through the reduction in SW development time.  I've deeply appreciated not just the quality of NI products, but their support as well.  Having said that - I don't use real-time, and have no plans to use it in the future.  The decision to move the Mathscript functionality to a toolkit will eventually increase my SSP cost for no extra benefit.  It's hard to feel good about that... 

Thanks,

Jason

[tst]

I can see at least one good reason for forcing people to explicitly request this (assuming you accept the decision to separate it in the first place) - people don't read documentation. No matter how loudly you would shout it and where, some (quite possibly even most) people just wouldn't notice (Or ignore. Or forget about) this change until their MS stopped working. By doing this now, NI doesn't have to deal with those people finding out in a year.

[Coq_Rouge]

Ok so I am going to test drive Labview 2009. Then I try to install it it suggest the folder "C:\Program Files\National Instruments\LabVIEW 8.6\" as the directory for National Instrument software. Should this not be the "C:\Program Files\National Instruments" directory? I will not in any way mess up my 8.6 installation, since I am not sure I will jump on the 2009 train yet