Introducing LabVIEW 2009

[tst]

---

Nickerbocker wrote:

Are we going to have to buy a module for the event structure next?

---

In a sense, you already do. If you get the base version of LabVIEW, which is cheaper, you can't edit event structures. I'm guessing that the logic behind that is that the base version is targeted for people who want do simple logging or analysis apps which will not need a complex UI.

[kmcdevitt]

---

Jeffrey P wrote: 

I'm one of the LabVIEW Product Managers, and am specifically responsible for the new MathScript RT Module.  We invested significant engineering resources into the development of the MathScript technology.  The 2009 release of the MathScript RT Module delivers huge functionality differentiation to the marketplace by allowing users to deploy their custom .m files to all real-time hardware platforms. Previously, this has been a significant challenge for developers working with the .m file format, as deployment to embedded hardware required mutliple steps, code rewrites, and additional compiler/debuggers for the specific hardware platforms.

---

Thank you Jeffrey,  I am looking forward to utilizing this new capability for RT.  Yes it has taken quite a while.  I am glad it has finally arrived.

---

Jeffrey P wrote: 

Productizing the MathScript technology provided several benefits:

• Separating the MathScript technology from the LabVIEW core platform raises the visibility of MathScript, and the new functionality being delivered with the 2009 release
• Productizing MathScript allows us to recoup a small portion of our investment, allowing us to focus on new opportunities for the technology
• With MathScript as part of LabVIEW, we really had no idea who was using MathScript, or how.  Productizing MathScript gives us an immediate list of users that we can engage for feedback, feature discussions, and roadmap prioritizations.

---

In summary productizing it allows you to charge for something that we have already paid for.

---

Jeffrey P wrote: 

We realized that many of our existing customers would be put off by this decision, so we implemented a "grandfather" clause of sorts.  Any existing LabVIEW user current on their SSP contract (including single-seat, Developer Suite, or VLA) can "purchase" the new LabVIEW MathScript RT Module for $0.  This purchase will include one year of service, and at the conclusion of that year, you will only be expected to pay the renewal price to stay current with the Module.  As a Developer Suite customer, that renewal price is even lower than with a single-seat contact.  You can contact your local Sales Engineer or call into NI, as the systems are in place to handle this order.

---

Yes  Jeffrey, we are put off.  All of us on current SSP should be AUTOMATICALLY grandfathered.  This should be done without any action on our part or our local sales person.  Just do it.  Sorry Ravens Fan and Coq Rogue for screaming, you'll just have to get over it. 

---

Jeffrey P wrote:

I would also like to emphasize that this is not a trend that is forming with the LabVIEW product.  We are not going to be productizing and removing other features of the LabVIEW Core environment.  This was a one-off decision made with special circumstances.   

---

At worst this is a lie.  At best this is an untruth.  It is not a one-off decision.  It has become a pattern.  You did it with Trace Execution Toolkit.  You're doing it now with Math Script.  And you'll be doing it in the future with other toolkits and modules.  Why not just be honest and upfront about it.

Kevin. 

Message Edited by kmcdevitt on 08-11-2009 11:45 AM

[Ray.R]

---

Ben wrote:

Yes. When this was presented to the LabVIEW Champions, it was mentioned that one of those image file formats (png or jpg ?) had some extra functionality built-in that allows NI to include the source code inside the image. So they will still work with browser and can be dragged into a VI BD.

---

I don't recall that...  Maybe I wasn't paying enough attention.  

First I thoughtyou were kidding, butsince it's not April 1.. then you mustbe serious.. 

It has to be a special image to contain the code.  It cannot be from a regular image..

I'm just reading these posts and may have posted this prematurely.. 

 >>>  reading on <<<

[Jeffrey_P]

Mark,

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".

The MathScript RT Module delivers the MathScript compiler, and the two interfaces for accessing that compiler (the Node and the Window).

Could you describe what you are doing with LabVIEW and MathScript? I'd love to hear about your application.

Regards,

[Coq_Rouge]

I have often used copy and paste from Labview to paint. If I copy some code from the block diagram, I can paste the selection into paint as picture. The code is of course lost. So I guess this is not a big deal in the windows OS at least.  

[hecmar.arreola]

@tst - Right.  I paid extra for the extra features of the Professional version of LabVIEW over the Base Version of LabVIEW.  I completely agree with you on that sentiment.  One of those features was the Event Structure, and another one of those features was the MathScript support.  MathScript support has been taken away from the set of extra features that I already pay extra for.  So what is to keep National Instruments from taking the Event Structure and making it a Module that I have to pay extra for next?  Their promise? I'm really not happy about this change.  People who do not do RT do not bennefit by these MathScript changes and I do not understand why National Instruments now wants us to pay extra as part of our Subscription Service.  This will definitly have an effect on my companies decision to renew our subscription service this year.  When I started working here in 2005, they were still using LabVIEW 5.  I'm afraid that these changes are going to push my company back towards an upgrade LabVIEW once every 5 years plan.

[Jeffrey_P]

Nicker,

Thank you for the feedback on LabVIEW 2009.  It's great to hear that the features delivered in the product meet the expectation(s) of our end users.  Ultimately, that is the goal.  I hear your feedback regarding MathScript, and we will evaluate the potential in your suggestion(s).  Regarding your concerns over an Event Structure Module, I wanted to reiterate that this is not a trend starting in the LabVIEW Product. There will not be an OOP Toolbox or Event Structure Module coming out.  This was a decision that we weighed heavily internally, and I assure you, was not made lightly.

Respectfully,

[hecmar.arreola]

@Jeffrey P - Thanks for taking the time to read our complaints and concerns.  Ultimatly, I do want to convey that I am pleased with the 2009 release.

[kmcdevitt]

---

Jeffrey P wrote: 

Thank you for the feedback on LabVIEW 2009.  It's great to hear that the features delivered in the product meet the expectation(s) of our end users.  Ultimately, that is the goal.  I hear your feedback regarding MathScript, and we will evaluate the potential in your suggestion(s).  Regarding your concerns over an Event Structure Module, I wanted to reiterate that this is not a trend starting in the LabVIEW Product. There will not be an OOP Toolbox or Event Structure Module coming out.  This was a decision that we weighed heavily internally, and I assure you, was not made lightly.

---

Jeffrey,

Every Productization is a broken promise, including this one.  It is inherently unfair.  The only fair thing is to honor the commitment made in the SSP.  Moving forward, it is fair to charge separately for new purchases.  It is then upon us to work within our own budjets and make our own decision wheather it is in our best interest to renew our SSP next year, and/or make additional purchases.  Or freeze our software at the end of our current SSP.

Kevin 

[Jeffrey_P]

Kmcdevitt,

We definitely considered an automatic grandfathering clause.  The problem here is that then everybody would recieve the updated software, and we would be back to not knowing who is actually using MathScript.  With this approach, we have a clear definition of which LabVIEW users are using MathScript, and gives us the outlet to work with you for new features, what features (or lack of features) are roadbumps for you, and how we can ultimately make the experience better. Automatically grandfathering everyone would only delay this conversation until a year from now.