KCML Support Access

KCML support licences allow a Keyloop associate or dealer support person to gain access to the application code via the workbench where normal customer access has been prohibited. This is done by a KClient support licence tied to the machine executing KClient.

KCML Versions

KCML Version Build introduced Feature
5.02 All builds No license restrictions on workbench access
5.50 All builds No license restrictions on workbench access
6.00 < 15201 Workbench access controlled by Version 1 scheme
>= 15201 and < 16153 Workbench access controlled by Version 2 scheme
>= 16153 Workbench access controlled by Version 2 scheme, with a further change that ADPSUP, ADPCON and ADPDEV roles have the same access as ADPKCC.
6.20 < 15201 Workbench access controlled by Version 1 scheme
>= 15201 Workbench access controlled by Version 2 scheme
6.40 All builds Workbench access controlled by Version 1 scheme
6.6x All builds Workbench access controlled by Version 1 scheme
6.90 < 15201 Workbench access controlled by Version 1 scheme
>= 15201 Workbench access controlled by Version 2 scheme
7.0x All builds Workbench access controlled by Version 2 scheme

Version 1 scheme

This scheme is only available to Keyloop associates. Access is controlled by a users= value in the support section of the KClient licence:

[SUPPORT]
users=14!2150 eaa1 f23d 26cf 

Although the users= value is a number it is not a count, but interepreted as a binary number where each bit represents some part of access.

Bit Access
HEX(01)Reserved
HEX(02)Programmable - code can be viewed, variables inspected, read only mode.
HEX(04)Limited debugging - program flow can be changed, variables modified, read/write mode.
HEX(08)Full Workbench support for writing/modifying programs and debugging.
HEX(10)Reserved for application use.

Version 2 scheme

The version 2 scheme was introduced to provide better control. All version 2 support licences are issued with a time expiry, typically of six months, after which the licence has to be renewed. The KClient support licence uses the machine identifier protection introduced with KCML7. This is a longer, more detailed format than that used in KCML6. It is stored in a new value, MID=, in a new section. Examples of the old CPU= and new MID= are:

[Protection]
CPU=4224 3A94 7A4E 164C!8634 9c68 00fa 286f 
[MachineIdentity]
MID=AABOyaFyF0JDKgnJGWxfuGrouU2AjEtVds/Be0lz3yAAeDAAFaDJVxTKnnD0Wrib+ratrqT9n0/ajWQd8MoHz31XKSYrrd
CY7BetO+FxbtLzib7+NfBYIPydntvTzToWe0yiFWGANitwixinuSHYsTel9Hou3nDQzvrGNC+C7zs1dMLk68jcTQXVR4gVnE6I
KNDVI+rpDQdGgXndOKjlT4AxUWNhKO2j+sa5HtaNvZO46HPItlBY2nOO7fWDCg6ksdOZ0ztTpXrPGZT2369yJ7Ki!665d ff9d c854 723d 

Note that the MID= must be on one line, event thiough many text editors will display it wrapped onto several

Keyloop associate KClient support licence

A typical Keyloop associate KClient support licence will look like this:

[SUPPORT]
users=14!2150 eaa1 f23d 26cf 
role=ADPCON!ff46 ff7f 5baa b091 

The users= section has the same meaning as in the Version 1 scheme, but in addition the role= setting must also be set or no workbench access will be allowed. The role is one of a set list of values:

Role Access
ADPNo workbench access
ADPROBOTNo workbench access
ADPSUPThe associate can break into application code to access the workbench. The associate can single step, continue and tooltip variables, but not modify the program flow. There is no access to the console window or the system shell.
ADPCONThe associate can break into application code to access the workbench. The associate can single step, continue and tooltip variables, but not modify the program flow. There is no access to the console window or the system shell.
ADPDEVThe associate can break into application code to access the workbench. The associate can single step, continue and tooltip variables, but not modify the program flow. There is no access to the console window or the system shell.
ADPKCCFull workbench and shell access is available
TOOLSETFull workbench and shell access is available
ADPTECHThe associate can break into application code to access the workbench. The associate can single step, continue and tooltip variables. There is limited ability to modify program flow, by skipping to another program line. There is no access to the console window or the system shell.
ADPOSLOWShell access is available, but no Workbench access is allowed. Introduced in KCML build 18291 - for older KCML will be ADPSUP
ADPOSHIGHThe associate can break into application code to access the workbench. The associate can single step, continue and tooltip variables, but not modify the program flow. There is no access to the console window or the system shell. Introduced in KCML build 18291 - for older KCML will be ADPSUP.

Dealer KClient support licence

A typical dealer KClient support licence will look like this:

[DEALER]
users=14!6ffd c986 c77b c0bf 
role=DEALERHIGH!91d0 71f1 4803 6316 
Name=12345!719b 416f f978 9a49 

The KCML licence will also contain a Name= value. The values must match or no support access will be available:

[DEALER]
Name=12345!719b 416f f978 9a49 

The users= section has the same meaning as in the Version 1 scheme, but in addition the role= setting must also be set or no workbench access will be allowed. The role is one of a set list of values:

Role Access
DEALERLOWThe user can break into application code to access the workbench. The associate can single step, continue and tooltip variables, but not modify the program flow. There is no access to the console window or the system shell.
DISTLOWThe user can break into application code to access the workbench. The associate can single step, continue and tooltip variables, but not modify the program flow. There is no access to the console window or the system shell. Introduced in KCML build 18291 - for older KCML will be DEALERLOW.
DEALERHIGHFull workbench and shell access is available
DISTHIGHFull workbench and shell access is available. Introduced in KCML build 18291 - for older KCML will be DEALERHIGH.

For distributors (who distribute Autoline and KCML), there are similar roles to those for dealers.

Role Access
DISTLOWThe user can break into application code to access the workbench. The associate can single step, continue and tooltip variables, but not modify the program flow. There is no access to the console window or the system shell. Introduced in KCML build 18291 - for older KCML will be DEALERLOW.
DISTHIGHFull workbench and shell access is available. Introduced in KCML build 18291 - for older KCML will be DEALERHIGH.

Development machines

Development machines are intended for where software is being developed and should not be used in customer situations. Here the KCML licence enables workbench access for everyone and the KClient support licence is not used.

Keyloop Development machines

A typical licence is as follows. The users= contain bits to enable the access required.

[SUPPORT]
users=14!2150 eaa1 f23d 26cf 

Dealer development machines

A typical licence is as follows. The users= contain bits to enable the access required.

[DEALER]
users=14!6ffd c986 c77b c0bf 
Name=12345!719b 416f f978 9a49