![]()
Licenses Validity and
Registration procedure in PG5 1.2 and 1.3
General
The licenses for the Engiby’s libraries are bound to the PG5 licences. 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.2 and 1.3, the license of each
library must be registered in PG5. Please read also the few restrictions at the
end of this page.
License Validity
The passwords are valid for
one main version of PG5, e. g.: Versions 1.3.xxx. An update or a new password
will be required for the next versions.
Within a delay of 12 months
from the delivery of a driver or an update (free update excluded) for PG5 1.2,
you can ask for a free password for PG5 1.3.
In other words, Engiby ensure that a driver can be used at least one year
without being invoiced for a password update. This is only valid for products
with unlimited licence.
This does not necessarily imply the delivery of a new library for free. You
will need to order a library update to have a new version of a library with new
features.
Registration
procedure
In the
following procedure we base on the assumption that you have got a official and
licensed version of PG5 1.2 or 1.3 (V 1.2.100 or higher) installed on your
computer and you have used the register software feature of PG5 to install the
key file you have got with PG5: User of Demo package, $-versions and Beta
tester, see below.
The registration procedure
is identical for PG5 1.2 and 1.3. When updating from PG5 1.2 to PG5 1.3, please
read the chapter below.
Note also that this procedure is not valid for Engiby’s
Add-On tools. Passwords for Add-On tool must be registered in the Add-On tool
itself.
1.
When you order a
license or an update for PG5 version 1.2 or 1.3, send the USER.KEY file
of the corresponding PG5 package to Engiby. This allows us to create a password
that matches with your PG5 license. Please send the file to Engiby.
2.
The Integrator (or
End User) is registered by Engiby and a Password is sent back.
3.
Start PG5 and use
the menu command Help - Register Software.
4.
In the dialogue box
(example below), select Enter Password, copy the received Password and
click OK.

Now you can build a project
using the registered library.
Other Conditions and
Restrictions
You need at
least a version V 1.2.100 of the PG5 1.2 or $ 1.3.012 for PG5 1.3. If you have
a former version (Beta or $-version), see below.
Password will not be
created for package without a correct user license (E.g. package 'For SAIA
Internal use only').
The password can be used
only once on the same PC, and 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, if you
cannot install your password or you cannot receive a password from Engiby, you
can ask an emergency password by SAIA for a limited period. Please contact the Customer
Care department of your local SAIA representative in this case.
On the same PG5 version,
the same password is valid for several version of a library, as long as these
versions are bound to the same license.
Example : ESPA 444 driver version 2.4.xxx use the same
passwords as the former version 2.3.xxx.
Other example
: Modbus
The passwords for version 1.5x are the same as for the versions 1.6x.
But these passwords are not valid for the Modbus 2 package (version 2.4.xxx). This package need another license.
Note also that some
libraries need a system license (one license per PCD system).
Updating from PG5 1.2
to PG5 1.3
The key
files you have received for PG5 1.2 is not valid for PG5 1.3. Take care to use
the correct one. Also the passwords provided by Engiby for PG5 1.2 are not
valid for PG5 1.3. See above the conditions for the delivery of free password.
Note that key files as well as passwords created for $ or beta versions of PG5
1.3 will not be valid for official versions and service pack of PG5 1.3.
Therefore, we recommend to use demo key files only for $ and beta version of
PG5 1.3.
Updating
from PG5 1.3 to PG5 1.4
Demo package
Demo packages of PG5 does not 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 password
will be required when the personalized license will be installed.
Beta tester and user
of $-version
Beta tester and
user of $-version must also have a demo package to use Engiby's
libraries. Engiby will not deliver passwords for generic packages like 'FOR
SAIA INTERNAL USE ONLY' or similar. Take care !
A password will be required when the personalized license is installed. The
above described procedure must be executed when the official licensed version
will be insalled. User.key
files of Demo, Beta and $-version prior to V 1.2.100 are not anymore compatible
to the versions V 1.2.100 and up.
|
Engiby / 07.01.2008 |