11-06-2009 03:12 PM
CoastalMaineBird wrote:I've always used the LabVIEW "Professional" package, as far back as there were such distinctions made.
I have a new client that, unbeknownst to me, bought the "Base" package, and then contracted me to develop some software.
I would like to deliver software that he could open in his base package, but I don't have a good handle on the differences.
He probably doesn't need any of the advanced math tools that are in the "pro" version.
But how do I manage this? Is there a switch I could (temporarily) turn on to warn me that this VI I just placed is not in the base package?
I have other projects that need the pro features, so it would have to be easily switchable.
Do I have to go thru every VI I place and check it for base-ness?
Do I install a separate copy of LabVIEW and make that a BASE copy?
Anybody face this before?
You can go into NI License Manager and deactivate your Professional Development System. Then Activate Base Development System. Then when you restart LabVIEW you will only have access to things available in Base.
08-08-2012 05:13 PM
The Event Structure is available in the Base Package as of LabVIEW 2012.
01-14-2014 06:07 PM
I have a similar issue and I have tried to use the License Manager to deactivate "Professional" and activate "Base". As it turns out, my license (academic site license) can activate "Full" and "Professional" without any problem, but is incompatible with "Base".
Is there any other way to check whether all my VIs and dependencies are compatible with "Base"?
01-15-2014 07:38 AM
You could always download the base version on a 30-day basis for free. AFAIK, this can be done every 30 days, if necessary (a pain in the nether regions to discourage moochers, but might be appropriate for occasional testing).
Cameron
01-15-2014 08:07 AM
01-15-2014 08:17 AM
You can check what functions are available in which package here:
http://www.ni.com/labview/buy/learn/?base
You can also check if a particular function needs a package different than Base by going to LabVIEW help:
01-15-2014 10:05 AM
Thanks, Mateusz.
That still means I have to manually check through hundreds of VIs and dependencies one by one and look whether each individual function is available in the Base package.
I was hoping that there might be a less tedious solution than that. Do you have any suggestion how to achive that, Mateusz?
01-15-2014 10:29 AM
hello bp99,
As far as I know, the Base license should be grandfathered into any Full or Professional license. Your site license may have different terms, however. I would give NI a call and see if a manual activation key can be generated using your serial number.
If you have a volume license agreement, get in touch with whomever manages the VLA as they will have more information on the licenses available and how to activate them via your license management system.
Out of curiosity, though- what is your "similar issue"? There may be a better solution such as building your application into an executable for redistribution.
Regards,
01-15-2014 11:31 AM
@bp99 wrote:
I have a similar issue and I have tried to use the License Manager to deactivate "Professional" and activate "Base". As it turns out, my license (academic site license) can activate "Full" and "Professional" without any problem, but is incompatible with "Base".
Is there any other way to check whether all my VIs and dependencies are compatible with "Base"?
I am still trying to understand why this would be important. If given a choice, nobody would want "base". All academic and student licenses have at least the "full" feature set so there is never any compatibility issue. (With an academic license, " ... any use of the SOFTWARE for commercial or industrial purposes under this Agreement is prohibited", so you cannot e,g, provide programming services to a compay that only has base, while using your academic license.).
01-15-2014 11:49 AM
Altenbach, a colleague is moving to a non-Academic position and he would like to continue using some LabView VIs that I've written for him. So, he needs to buy a licence, but the question is whether a Base licence will be enough. He won't need to do any development himself, just run the VI, but unfortunately I can't build an executable due to a known issue with ImageControl References (http://forums.ni.com/t5/LabVIEW/image-display-reference-control-still-not-working/td-p/435456).