Base and Full Evaluation Package

[Tepig]

We can try LabVIEW as Evaluation.
But the package we can use is only Professional Development System.

Why is there no Base or Full package ?

If ni makes these package, we can try LabVIEW more easily.
And more engineer can use it!

Thanks,

Tepig

[RavensFan]

I don't know how having the lesser packages as evaluation let you to "try LabVIEW more easily and more engineer[s] can use it".

It makes sense to me that the PDS system is the evaluation.  It is intended to demonstrate the capabilities of LabVIEW so that you can determine whether it meets your needs.  If you evaluated a lesser version, you might decide it didn't meet your needs and you wouldn't consider buying it!

[Darren]

The evaluation version of LabVIEW is intended to demonstrate the full capabilities of the software, and as such, makes sense to remain based on the Professional Development System.

[Tepig]

Because when they hope to buy Base Development System, there is no evaluation SW.

They can use Pro but can not test as Base.

There is a lot of difference between Pro and Base.

I think we should use Base as evaluation.

How do you think?

[Intaris]

I think two different interests are competing here:

1) NI only offers the professional evaluation so a lot of users try out LV thinking that they can use the base version and find out much of the features they found cool are only in the full or pro versions and end up giving out more money.  This is in NIs interest.

2) A user knows he / she can only buy the base version and has a real hard time doing a proper evaluation because the evaluation has way more functionality than the version of the software they would like to buy.  The availability of a base or full evaluation package woule be of benefit to the user.

A middle road I would propose is having to choose an evaluation license when installing the evaluation so that you can mimic the limitations between the different versioons of software.  By saying that an evaluation should "demonstrate the full capabilities of the software" is OK if everyone wants to buy the pro version and it was clear looking at the code which parts are available in which version but at the moment this is clearly not the case.

[fabric]

How hard can this be anyway? It's the same code...

[RavensFan]

I think if the person who is evaluating should look at the functions they are using then determine which version it is in.  The help file tells you whether the functions are in the base version or not, and there is a chart to tell you what is a part of each level of the package.

First you figure out what you need to do.  Then you figure out which level of the tool you need to do it.

[Tepig]

Sorry I am late. My customer already has LabVIEW Professional. He plans to buy new LabVIEW. But He thinks LabVIEW Base is enough. There is a lot of function difference between Base and Pro (fitting func, etc...). He has already created a lot of VIs. But there is no way to check that His VI whether can use on Base package. I know that NI hope to use Pro, but they want to use Base. I believe we should have multi-evaluation package for our customer.