Engiby's Libraries
Licenses Validity and Registration Procedure
Valid for PG5 1.4 and 2.0
General
The licenses for the
Engiby’s libraries are bound to the PG5 licences (user name and main version).
Usually the library is addressed to the Integrator. The Integrator is
the company which owns a licensed version of PG5 and will install the
additional library on PG5. If the Integrator AND the End User have got a
different PG5 license and install the Engiby product on PG5, each of them must
purchase a product license. With PG5 1.4 and 2.0, a license key for each
library must be entered when the library is installed (not in SPM as for PG5
1.3). Please read also the few restrictions at the end of this page.
Note that the main PG5 version following 1.4 is 2.0.
License Validity
The license keys are valid
for one main version of PG5, e. g.: Versions 1.4.xxx. An update and a new key
will be required for the next main versions, e. g.: Versions 2.0.xxx.
Within a delay of 12 months
from the delivery of a driver or an update (free update excluded), you can ask
for a free update and a key for the next PG5 main version. E.g.
from PG5 1.3 to PG5 1.4 or from PG5 1.4 to PG5 2.0.
In other words, Engiby ensure that a driver can be used at least one year without
being invoiced for a new license key. This is only valid for products with
unlimited licence.
Registration
procedure
In the
following procedure we base on the assumption that you have got a official and
licensed version of PG5 1.4 or 2.0 (V1.4.100 or V2.0.100 or higher) installed
on your computer and you have used the register software feature of PG5 to
install the User.key file you have got with your PG5 (user of Demo package,
$-versions and Beta tester, see below).
Ensure you have the correct
User.key installed on PG5 as follow: Start Saia Project Manager, go to the About box over Help menu and check the displayed User name.
Example:
1. When you order an Engiby license or
an update for a new PG5 version, send the USER.KEY file of the
corresponding PG5 package to Engiby. This allows us to create a license key
that matches with your PG5 license. If you don't have any personal address,
please send the file to info@engiby.ch.
2. The Integrator (or End User) is
registered by Engiby and a License key is sent back.
3. Start the setup of the concerned
library. Select the installation for PG5 1.4 or 2.0. If you don’t need to
install the library, you can uncheck the option ‘Library’.
4. Click Install.
5. When the dialogue box appears,
copy the received Key and click OK.
Now you can build a project
using the corresponding library.
Other Conditions and
Restrictions
You need
at least a version V 1.4.100 or V2.0.100 of PG5. If you have a former version
(Beta or $-version), see below.
License keys will not be
created for package without a correct user name (E.g. package 'For SAIA
Internal use only').
The keys can be used only
on the PC with the correct PG5 license (the one sent to Engiby
!) but you are allowed to use it on other PCs as long as they have the
same PG5 license. It means the PC is used inside the same company.
In emergency cases, Engiby
can provide an emergency Key, valid for any user name and any library, for a
limited period. The emergency key is shorter and can be easily be transmitted
by phone.
On the same PG5 version,
the same key is valid for several version of a library, as long as these
versions are bound to the same license.
Example: M-Bus driver version 2.5.005 use the same
keys as the former version 2.5.001.
Special case: Modbus1 and
Modbus 2
The keys for Modbus 1 (versions 1.7x) are not valid
for the Modbus 2 package (version 2.5.xxx). This package needs another key.
Note also that some
libraries need a runtime license key (one license
Updating from PG5 1.3
to PG5 1.4 and to PG5 2.0
The
user.key files made for PG5 1.3 are not valid for PG5 1.4. Also the passwords
provided by Engiby for PG5 1.3 are not valid for PG5 1.4.
In the same way, user.key files made for PG5 1.4 are not valid for PG5 2.0.
Also the passwords provided by Engiby for PG5 1.4 are not valid for PG5 2.0.
See above the conditions for the delivery of free license key. Note also that
user.key files created for $ or beta versions will not be valid for official
versions and service pack of PG5. Therefore, we recommend to use demo key files
only for $ and beta version of PG5.
Demo license
Demo licenses
of PG5 don’t restrict the use of any library (including Engiby's) but has only
a time limitation (30 to 90 days). At each build you get a warning indicating
the expiration date of the demo license. Take care !
A license key will be required when the personalized user.key file will be
installed.
Beta tester and user
of $-version
Beta tester and
user of $-version must also have a demo license to use Engiby's libraries.
Engiby will not deliver license keys for generic packages like 'FOR SAIA
INTERNAL USE ONLY' or similar. Take care ! A
license key will be required when the personalized license is installed. The
above described procedure must be executed when the official licensed version
will be installed.
|
|
Engiby / 20.02.2010 |
