Search the Community

... to provide us with an upgrade to our software which we bought back in 2017. And this is going on for more than a year now. The story is simple - our company bought a license for NI EMBEDDED CONTROL AND MONITORING SOFTWARE SUITE, USB, SPR17, Rev 007, 2017.06.07 and we successfully downloaded the SP1 upgrade later on. The next year we bought a subscription to LabView 2018 but did not renew it for 2019 and went back to using 2017. Meanwhile our downloaded SP1 files gone missing. "No problem" - we thought - "We'll just go to the NI website and download our SP1." https://www.ni.com/en-ca/support/downloads/software-products/download.embedded-control-and-monitoring-software-suite.html#306390 Not that fast! To download previous versions of LabView you need an active subscription. OK... So, how do you get missing pieces for your software you have a license for if you do not have an active subscription? We contacted NI and their representative Newark and asked them for help... Long story short - we are still waiting for a resolution. Meanwhile, I see no other option but to ask the community for help if NI is so ignorant. Maybe some of the members can share their LabView 2017 SP1 installation files? I don't think it will be a copyright violation or something - what can you do with it without the license? In any case, I would greatly appreciate any input and, maybe, perhaps an advise or a comment. https://www.ni.com/en-ca/shop/software/products/embedded-control-and-monitoring-software-suite.html We are looking for: 1. LabView2017SP1-WinEng 2. 2017SP1RealTime-WinEng 3. 2017SP1FPGAModule-WinEng 4. 2017SP1XILINXCompilationTools Best Regards.

Hi, I would like to implement a Run-time license checking mechanism that will enable or disable some parts of my LabVIEW API depending on a license status. After reading numerous discussions here on the forum (We need a new password cracker :( , Low level VI data editor (warning: not for production use!) , I found some more hidden INI keys, Password Security in LabVIEW) I realised few things: - reverse engineering in a LabVIEW-related field seems to be a doable task for some smart people, - password protection on block diagrams does not protect your IP, it is more of a "read-only" or a "private property" sign, - removing block diagrams or compiling it into an executable are the ways to go, and finally, - there are few tools out there, that seem to have a potential to "unflatten" VI data and modify/extract its data even without block diagrams. Back to my task. I decided to remove block diagrams. Inside my protected VI I call an external library that does the actual license checking. So the code only gets this status and returns it back to other VIs. Then the VIs do not perform their main functions, and the user gets an error. Do you think I am safe here? Is it possible to extract sensitive string information out of my VIs (without BD)? Is there a way to change wiring rules/connector pane on my VIs? Should I worry about DLL hijacking? Does NI have some kind of a tutorial for protecting your run-time API? How do you protect your API knowing all that? Do you sleep well? Thanks

Have a look to this brand new toolkit for LabVIEW if you are interested to distribute LabVIEW executable with advanced licensing, automatic update capabilities and a lot more amazing features. BLT for LabVIEW (Building, Licensing and Tracking) http://sine.ni.com/nips/cds/view/p/lang/en/nid/211731 BLT for LabVIEW is a stand-alone program you can use to distribute LabVIEW applications for commercial use in a few clicks. License your own LabVIEW application in a few clicks - no coding required Automatically (and remotely) update your applications when you make changes in your LabVIEW code Automate the build process for your LabVIEW executables Get user activity reports and error logs so you can remotely debug your program Use BLT scripting to remotely execute actions on a deployed computer, e.g., update LabVIEW RT Engine Disable parts of your code with features definitions

(cross-posted to the NI CLA Forum; you'll need to be a CLA to view that link) Do you care about software licensing? As evidenced by this exciting thread from last year, some of us (including me) obviously do . Here's the deal: I'm going to be leading a session at the CLA Summit Americas on Software Licensing. I want to make sure I have the areas of focus dialed in so that everyone gets useful information out of the hour we'll have together. Whether you're a CLA or not, and whether you're coming to the Summit or not, can you please post software licensing questions or concerns that affect you or your business? This will help me capture as broad an understanding of people as possible. Here are some seeds to get you thinking: Do your consulting customers ever ask you about licensing issues with your software? What questions do they ask? Have you ever had a project fail due to licensing issues? What was the core hang-up? If you make (or are considering making) LabVIEW add-ons for the LabVIEW Tools Network, is there anything related to licensing that you're kind of stuck or can't understand? Software licensing is a big topic with lots of tricky details. What do you feel like you just don't understand? Thanks! P.S. If you have some licensing question or story that you'd rather not share publicly for some reason, feel free to PM it to me!