Leaderboard

Today I told NI, that I am not willing to join a subcription program, in which NI can increase the pices as they want or to shutdown my software and that LabVIEW 2022 will be my last version. I just can encourage all other guys to do the same and to not accept such a pricing model.

new release in my fork : https://github.com/AntoineChalons/lv-toml/releases/tag/releases%2Fv2.3.2 what's new : I've improved the error reporting when there is a typo in the value, ex : [cluster] some-numerial-value = 10 other-numerial-value-with-a-typo = 10s The error source will quote the line at fault and give you the line index, something like "Parsing error at line 3 : 'other-numerical-value-with-a-typo = 10s'

You don't need that. That is the API that you could create TPLAT with. This is the basic procedure Create a product definition (Using LFEdit or via the Softwarekey web page). Create a licence file for the product (Using LFEdit). Apply the licence to the lvlib (Using TPLAT in advanced mode. This will give you a Licenced version of your code.) Point VIPM to the licence when you build the distribution (If you have the full VIPM, it can also apply it instead of using TPLAT above). This is the full licencing process (excluding the VIPM). You can also buy the licensing server from Softwarekey for installation on your own network, if you want everything in-house rather than using theirs (or NI's)

This is the process for adding licencing to addons. You only need "Protection PLUS 5 SDK" if you want Advanced licencing features or your own SOLO server. The licence file (*.lf) created by TPLAT can only create a licence for "Standard" and you cannot change the SOLO server location (NI's SOLO server). In advanced mode you can choose a pre-created licence file (created with LFEdit from the Protection PLUS 5 SDK) which can have a different SOLO Server URL and more advanced features. What happens if you click on the "New to Solo Server" on the TPLAT dialogue? Is there no link to sign up? (I don't have TPLAT installed for 2022 at present).

Actually, BOTH behaviours with or without "ignore errors inside node" set are different from error-chaining the individual subVIs (which is how I would argue stacked Property Node should behave).

Hello, LAVA. My team at SpaceX is looking for LabVIEW developers. We have two job reqs open, one for entry-level developer and one for senior. Ground Software is the mission control software for all Falcon and Dragon flights. Every screen you see in the image below is running LabVIEW. Our G code takes signals off of the vehicles, correlates it for displays across all our mission control centers and remote viewers at our customer sites and NASA. It's the software used for flight controllers to issue commands to the vehicles. This is the software that flies the most profitable rockets in the world, and we're going to be flying a lot next year and in the years to come. If you'd like to get involved with a massively distributed application with some serious network requirements, please apply. You can help us build a global communications platform, support science research, and be one of the stairsteps to Mars. Entry level: https://boards.greenhouse.io/spacex/jobs/6436532002?gh_jid=6436532002 Senior level: https://boards.greenhouse.io/spacex/jobs/6488107002?gh_jid=6488107002

Hello Youssef, As Shaun and Brian mentioned, BLT is a toolbox allowing you to distribute commercial LabVIEW applications with just a few easy steps. However it is limited to LabVIEW executable running on Windows. So this will not cover your need for licensing LabVIEW source code. If you are looking to sell LabVIEW applications running as executable on Windows computers with advanced licensing scenarios, you should definitely look into BLT for LabVIEW. You can try BLT for free with no time limitation, with all the features, and distribute 1 application on up to 5 computers. After that, there are some fees associated. BLT does not only provide licensing features, but also auto-update capabilities, usage tracking and remote debugging tools. You can get a lot of information regarding BLT for LabVIEW at https://BLTforLabVIEW.com and also by looking at the product documentation at: http://help.studiobods.com/bltforlabview If you have any further questions feel free to send an email to contact@studiobods.com Best regards.

Yes. I think it was the Studio Bods one I was thinking of. Looking at it now it seems to be geared towards executables and not sure if it will suffice for source code.

There was a couple, but I never used any of them. I think BLT is one that meets the needs, and I think Wirebird Labs had one, but that hasn't had any update in forever.

Interesting. This is could be due to their new subscription method. It might be worth finding out whether that is the case as there will be other caveats like you need to maintain a subscription Indeed. I vaguely remember a third party that was offering an alternative solution that was implicitly geared towards LabVIEW and used the TPLAT. But I can't remember who it was or how it worked.

This announcement might be of interest: https://create.vi/ni-and-jki-partnering-on-package-management-in-labview-d243b13ae3a6 "Features in VIPM Pro 2023+ (Paid): NI Third Party Licensing and Activation Toolkit (TPLAT) Integration"