Development License vs Debug/Deployment License

[FSuh]

I am not well-versed in LabView, and this is my first exposure with LabView since college. I am contracting a company to develop a LabView application for me that includes the vision module. During development, I need to run .vi files to test functionality, but will not be developing any programs myself. 

What is the functionality difference between the development license and the debug/deployment license? Would the debug/deployment license provide enough functionality for just testing the .vi files to give feedback for the base Labview and vision module?

[Kyle97330]

I'm neither a NI employee nor the person who buys or manages licenses at my company, so I could very well be wrong on these points.  However, I think the differences are:

1. How they are assigned:

Debug\Deployment licenses are for one PC each

Pro licenses are for one user each

2. Stuff included:

Debug\Deployment licenses are just for trying out code in the IDE but on the station and nothing more, so no extras

Pro license are for full developer needs, so in addition to the IDE they also include code analysis tools, source control tools, the application builder addon, remote EXE debugging, and probably more that I'm forgetting.

[JÞB · Accepted solution]

A debug deployment license is actually a full featured Development environment.   HOWEVER, the terms of the End User License Agreement restrict it more than a LabVIEW Development License does.  Read them both carefully (Disclaimer, I am not a legal authority nor do I warrant any advice given as binding outside of your company's agreements with NI, AND I represent neither party)

Essentially, a Debug Deployment Key let's you install the software on one machine only for the purpose of testing a system and making small code changes that you would feed back to the development team and suggest altering either the code or the system hardware.  I'll often stick one on system serial number 1 (I'd ALWAYS do that if the boss ALWAYS listened to my advice)  it is a highly effective integration tool.  Unless, of course, you fail to capture system changes and let the rest of the team know about them via a proper ECR / ECO. system. 

<sea story> One of my favorite contract positions actually DID Engineering Change Requests by scribbling a note on paper, balling up and throwing it across the bullpen at the responsible Engineer.</sea story>

[newlabVIEWuser25]

Thank you, this is very helpful. One thing I am having trouble understanding is if I purchase LabVIEW professional (which includes application builder) does this come with a debug/deploy license, and if so, can I use this debug/deploy license on other PCs/test stations beyond my own PC?

For example, if I am using the development license on my PC, but I would like to use debug/deploy on a separate PC connected to a test station, do you know if I need to purchase a separate debug/deploy license for this specific test station?

[rolfk]

A Development license gives you basically the choice to use it as a personal license or a hardware bound license. A personal license lets you install it on up to three computers as long as you are the only person who uses them. Basically they should not run at the same time and since you can not easily break yourself up in multiple persons, that is the limitation factor that guarantees this.

As hardware bound license, you install it on one PC and anyone having (hopefully legal, but that is nothing NI is concerned about but you should of course) access to that computer can use it.