Licensing of projects made with ScriptCommunicator
Scriptable data terminal which supports several interfaces.
Brought to you by:
szieke
Menu
▾
▴
What are the licensing implications/options for creating and distributing projects made with ScriptCommunicator? We're thinking of creating automation tools for some test and measurement instruments that we could provide free of charge with the instruments.
What about executables that include DLL files? Does the source have to be provided as well?
What do you exactly mean with distributing? Only the scripts (and the user has to install ScriptCommunicator) or scripts bundled with ScriptCommunicator?
The ScriptCommunicator executable and the used libraries (Qt, PCAN, OpenSSL and Total Phase Aardvark ) are free of charge. In other words you don't need any license.
The source code is GPL3, which means if you change it you have to publish this changes.
My intention is to make scripts that can be downloaded from our website and which can be run by anyone with ScriptCommunicator installed. I suspect there will be no issue here but wanted to check.
With regard to the executables, I understood that the Qt components required any project made using them to be published as open source (which is presumably what you have done) or pay a massive licence fee. It's not so clear what happens if I use your tools to create a "second generation executable" which incorporates Qt components. I don't intend to change any of your components so I don't think I would need to publish them? We also don't intend to charge for the executables, but I'd like some kind of reassurance that we're not doing anything wrong in creating and publishing our own work using your tools. I hope that made sense! :-)
Yes you are right. You don't need a license if you want to publish scripts.
Can you send me the link to your website please? I'm interrested in seeing for what ScriptCommunicator is used for (maybe I can improve ScriptCommunicator).
Last edit: Stefan Zieker 2019-01-24
The site is www.aimtti.com but there is nothing related to ScriptCommunicator there (yet?). We manufacture electronic test and measurement equipment with Ethernet/LXi, USB, RS232 and GPIB automation interfaces. ScriptCommunicator is a fantastic tool for creating custom test setups and automation interfaces. I've been experimenting with it and have done a little script for measuring battery capacity using an electronic load. We are evaluating some different ways forward with automation and ScriptCommunicator is one of them, with the licensing being one of the questions being raised. Personally, I really like it.
One of the most difficult things about ScriptCommunicator is working out what it is and then explaining it to others! It is, in my experience, something very special and unique. The other thing I find difficult is remembering its name for some reason!
Thx for your response. Nice to see that ScriptCommunicator is used by someone :-).
I started it as a serial terminal because I was not happy with the free serial terminals, which I used at work (I'm a SW developer, mostly microcontroller) and therefore I started ScriptCommunicator for myself. Then I published it and since then it eveloves more and more. Every time I need a functionality for my work I add this to ScriptCommunicator.
And yes sometimes it is even hard for me to descripe what ScriptCommunicator is because there is no other tool, which is similar to it.
Maybe you can explain it as the 'swiss army knife for SW-delopers and testers' :-).
Last edit: Stefan Zieker 2019-01-24
Hi. Glad to see that a measurement equipment manufacturer is interested in ScriptCommunicator.
I used for PCB test during development (parameters input and functionnal check for the product).
With time, the small script/UI slowly improved to a tool for mass production.
One missing feature is power consumption measurement...
The scripts and UI are internally shared using a subversion server from which the different test operators can update their computer.
Nice work Stefan,
Best regards,
Pascal
Hi Pascal,
it's always interesting how ScriptCommunicator is used. Thanks for your message.
Best regards,
Stefan