one LabVIEW license, one developer and some systems

[Vasilich2004]

Hi,

In ideal way I develop program on office computer and build a application. Then I launch the application on real another system/computer.

In real life I can not debug everything on my office computer (sometimes there is not spare card, sometimes it is impossible without real system). So I need to use LabVIEW on another system/computer too.

By first expensive way company can buy one license per one computer. Of course, it is not good way. Also rule is "one license per one developer" not per one computer!

In another way, I don't understand clearly how I can work.

As I understood license rule I can hold LabVIEW on one computer in the same time (Is it correct?) So I install and activate LabVIEW and NI drivers, debug something and then deinstall/deactivate LabVIEW. But each installation takes a lot of time 😞 Also I have some systems in private network and I think each activation takes my time 😞

Can anyone expain how I can work without headache?

Thanks ...

[altenbach]

What is your LabVIEW version? These things typically change slightly with every release.

See e.g. http://forums.ni.com/ni/board/message?board.id=170&message.id=118316 

Message Edited by altenbach on 03-26-2007 03:40 PM

[Vasilich2004]

Thank you.

I have Prof. LabVIEW 8.2

Link is useful. It looks much better. I can hold LabVIEW on 3 computers + home computer.

When I move to another computer I can de-install LabVIEW from one of 3 computers.

Can you explain me what is Debug license?

[altenbach]

Try this link:

https://www.ni.com/en/shop/software-portfolio/understanding-ni-software-policies.html

One reason for a debug license would be if you need to install your application in a client environment, but you need to be able to edit code in order to debug and make everything work with the local hardware, something you could not do on your own development system.

[Vasilich2004]

Thank you for link.

[Chris_Cilino]

I don't know if this would be helpful, but also consider a debuggable executable. For information refer to the Knowledgebase titled How Can I Debug My LabVIEW Executable? [link removed; article no longer available]

Chris C