![]() With the LabVIEW Electrical Power Suite, you combine the fixed standardized algorithms from the power industry with the custom capability of a full programming language and modular hardware. Measurement of under-deviation and over-deviation parameters Mains signaling voltage on the supply voltage The following analysis functions are included with the Full edition of this suite: The NI LabVIEW Electrical Power Suite helps you develop a custom single- or three-phase power monitoring, metering, or quality analysis application. The Opinions Expressed Here are not only my own, but seem logical and sensible to me, and consistent with what I believe is the Spirit of the Community Edition License.Download a seven-day evaluation from the Resources tab.ĭevelop an Open, Custom Power Quality Measurement System ), but if you want to "teach yourself LVOOP" or "learn FPGA" by taking Tutorials or writing "learning code" at home in the evening, you can bring this enhanced knowledge back to work and be a more effective LabVIEW Developer. You can't "bring your work home" with you to use Community Edition (but if the Company gives you a laptop with their licensed "Professional" Edition installed, there's no reason you can't use that system at home, but check on Overtime Rules. I do not believe the intent of Community Edition was to forbid us from "playing around" with algorithms and such that arise in the course of "doing one's job". Just be sure to keep the two code bases strictly separated - if, as you seem to indicate, you intend to stop working on the Project at home, it would probably be prudent to delete the code produced with Community Edition and do all of your future development at work. Having just worked out some of the algorithms and data structures you'll need to use from your earlier work at home, this should be fairly quick to do. Leave your personal PC at home, go to your Work Environment, use your Work PC with your Company-licensed version of LabVIEW installed on it, and start coding all over again. I must turn down the assignment including giving advise to my colleaguesĪs I understand it, you cannot use LabVIEW Community Edition (meaning the software system, installed on your personal PC, used by you to develop LabVIEW routines for your own personal use, non-commercial, non-academic) to develop code for commercial or academic use.I must refuse producing code for this project.I must refuse participating in producing code I have completed in the Community Edition.Reusing code partially by manually replicating similar functionality:.Reusing code partially by manually replicating identical algorithms:.Reusing code partially by copying/pasting between block diagrams:.I'm allowed to migrate VIs/Libraries/Classes from the Professional Development System to the Community Edition (reasonable proof available, like timestamped version control).I'm allowed to migrate VIs/Libraries/Classes from the Community Edition to the Professional one.I see several potential solutions (all assuming consent given by the employer): ![]() I'm now wondering what the intended degree of separation between private and commercial projects is. Not only have I solved a lot of the problems I'm about to encounter at work already, I've also been using a lot of the best practices and patterns I've become familiar with through my job for my own project. ![]() My own project is not completed at this point and I do not intend to continue working on it. A day later it becomes apparent I'm about to be assigned to the very project that inspired my own. I've been inspired by a work related project just recently, so I've started a similar one at home using the LabView Community Edition and have been making a lot of progress due to somewhat laxer review processes.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |