FAQs

FAQs

  • Overview
  • FAQs
  • Support
  • GitHub

›SDK for signature

Introduction

  • Wacom Ink SDK - FAQs

Downloads

  • SDK Downloads
  • Licensing

Request Support

  • Support

STU Tablet

  • STU Installation
  • STU-430V Installation
  • STU-540 Operating Modes
  • STU-540 Serial Installation

STU SDK

  • Installation
  • Programming queries
  • Runtime issues
  • STU SigCaptX

Enterprise Tablet Installation

  • General Installation
  • Driver Installation & Troubleshooting
  • Pen Configuration & Troubleshooting
  • Configuration and customisation

SDK for Ink

  • WILL SDK for ink v2
  • WILL SDK for ink v3

SDK for devices

  • Wacom Ink SDK for devices

SDK for signature

  • Licensing
  • Installation
  • Programming Queries

    • General
    • STU
    • DTU
    • Biometrics
    • Error Messages
  • SigCaptX
  • How to guides

SDK for multi-display

  • Wacom Ink SDK for multi-display

Wacom Applications

  • sign pro PDF - Version 3
  • sign pro PDF - Version 4

    • Contents
    • FAQs
    • User Guides
    • API

    sign pro PDF - Android

    • Contents
    • API
  • Installation Issues
  • Signature Scope
  • plugin for Acrobat Reader

Compatibility tables

  • Overview
  • Compatibility tables

    • Web Browsers
    • SW Compatibility
    • Desktop and mobile
    • Wacom Applications

Licensing

Display the Signature SDK license

To display the license used in your application use the <About> menu:

Click the application icon then select About...

License display

The About dialog displays:

  • Signature Component Version
  • License information

Remove 'Evaluation' watermark on signatures

An 'Evaluation' watermark is displayed in the signature background:

Evaluation License

Solution

To remove the watermark install a Commercial or Enterprise license.

To obtain a license see: Licensing

To install a new license see: How to install a license

To view the license used in an application click the green icon in the Signature Capture window, then <About> to display license information.


No valid signature capture licence found

When running sign pro PDF or a signature application built for use with the Wacom Signature SDK this error can occur in the following situations:

  • No signature pad is connected to the PC
  • A signature pad is connected but Windows does not recognise it (this will probably show as an error in Device Manager)
  • A signature pad is connected but it wasn't manufactured by Wacom
  • You are using a touch-screen PC or laptop which does not have a Wacom digitizer - please contact the manufacturer if there is doubt about this
  • The licence string is invalid, e.g. it has expired or has characters missing or added (please paste it into https://jwt.io to check its validity)
  • The new style long licence string is being used with an old release of the SDK which only supports the old style short string. The long JWT licences are only supported from release 3.19.0 onwards.
  • You are trying to run your application over Remote Desktop or Citrix and the signature pad isn't being forwarded over the network.
    For further information please see Use Citrix for signature capture
  • You are using a virtual machine which isn't forwarding the signature pad data to the virtual operating system
  • Your touch-screen PC or laptop does not have a Wacom digitizer and you are trying to capture a signature from an external Wacom pen device such as a DTU or Intuos
  • You are trying to connect to a Wacom STU pad which is operating serially (e.g. 430-V or STU-540 in serial mode) without first applying the correct configuration settings

Solutions

  1. Install the latest version of the Signature SDK and insert a valid licence string as described at How to install a license.
    A production licence for the Signature SDK (Lite version) can be obtained from the GETTING STARTED.md document on GitHub.
    If you do not wish to upgrade to the latest release of the SDK then it is possible to continue using the old style short licence. Please raise a Support Ticket to obtain one.
  2. Ensure that you are using a signature capture device (digitizer or tablet) manufactured by Wacom
  3. If you are using Remote Desktop ensure that the pad data is being forwarded over the network (see the Remote Desktop FAQ above)
  4. If you are using Citrix make sure that the signature pad is supported - see Signature Devices supported on Citrix
  5. If you are using a VM make sure that the signature pad is being successfully redirected to it - not all VM software does this automatically
  6. If you have a touch-screen laptop, PC or tablet and you are trying to capture a signature from an external Wacom pen device rather than from the touch-screen itself then the Signature SDK or sign pro PDF is likely to fail because it will by default try to capture from the touch-screen.
    It will fail in trying to do so because the touch-screen is not Wacom compatible and therefore a special paid licence is required.
    The solution is to use the wtCintiq registry setting
  7. If you are trying to capture a signature from an STU operating in serial mode make sure you have made the necessary configuration changes first. If applicable please see also Using the 540 with sign pro PDF in serial mode.

My production licence does not work

The production licence which I obtained from the Signature SDK samples on GitHub does not work. I get an error message saying that the licence is invalid or no tablet is found.

Solution

The long-style production licence which is provided on GitHub will not work with releases of the Signature SDK prior to 3.20.4.
There are two solutions:

  1. Upgrade to the latest release of the Signature SDK which is available under "For signature" at https://developer.wacom.com/en-us/developer-dashboard/downloads

  2. If you are unable to upgrade please request an old-style short licence by raising a Support Ticket.


How to install a license

The license is supplied as a text string in a download file, for example:

eyJhbGciOiJSUzUxMiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJMTVMiLCJleHAiOjE1MzAxODEwMDQsImlhdCI6MTUyMjIzMjIwNCwicmlnaHRzIjpbIkNETF9BQ0NFU1MiLCJDRExfTElWRV9TVFJFQU1JTkciLCJDRExfVEhJUkRQQVJUWV9QRU5TIiwiQ0RMX1BIVV8xMTEiLCJTSUdfU0RLX0NPUkUiLCJTSUdDQVBUWF9BQ0NFU1MiXSwiZGV2aWNlcyI6W10sInR5cGUiOiJldmFsIiwibGljX25hbWUiOiJXSUxMX1NpZ25hdHVyZV9FZGl0aW9uIiwid2Fjb21faWQiOiI0NjFjMjZjMDRlMGQ0YjQyODk1MjNiNDcwZDZiNTJhMSIsImxpY191aWQiOiJiMzFkYjFmMS1lODdjLTQzZGUtODQ4MS1kMzJiNmUyYWRlOGUiLCJhcHBzX3dpbmRvd3MiOltdLCJhcHBzX2lvcyI6W10sImFwcHNfYW5kcm9pZCI6W10sIm1hY2hpbmVfaWRzIjpbXX0.r_ntKX8JHbvE5lIjZgInsv-SbxenS60ymxgXYew8o5l4_UPdMAXxFa0xTNzIrTfb1DbJakLxcLUgeW2FeXnd5oaDt8fLrQDEgCt3SScp92YsCPnVnze7j4GHTVElDNgYtQzMBPAgPUGIg4NbinWZt8YthcDMCQbDFxWVhU3-AQMguGClxuZxxJHOzLp71nSczQ9aYsBMK2vaaMhjqVMt83XHc_MLtFiWoMM08n09oAsZqnkySyqgjPgXzR73ZWOrCcnwSKUU2VDraXIrO7z79UV1JvMYYQq7RtBQizjPRJlPz9YsBDrE8fexShNIzdizDNJliR_6YtHfQ1vKIdvtBA

Modify the application code to add the licence is illustrated below:

Signature SDK

HTML/Javascript

As illustrated in TestSDKCapture.html use the following syntax:

 sigCtl.SetProperty("Licence","licence_string");

for example:

sigCtl.SetProperty("Licence","eyJhbGciOiJSUzUxMiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJMTVMiLCJleHAiOjE1NTA1NzgzODYsImlhdCI6MTUxOTA0MjUwNiwicmlnaHRzIjpbIlNJ....tkmp48TZNg"); 

Similarly, if in use the Wizard control must also be licensed:

 wizCtl = new WizCtl(); 
 wizCtl.licence = "licence_string";
Java
 SigCtl sigCtl = new SigCtl(); 
 sigCtl.licence("licence_string");
C#
 SigCtl sigCtl = new SigCtl(); 
 sigCtl.Licence = "licence_string"; 
VB.NET
  Dim sigCtl As New SigCtl 
  sigCtl.Licence = "licence_string"
Delphi
sigCtl := TSigCtl.Create(Self); 
sigCtl.Licence := 'licence_string';

Note that Delphi TString is limited to 255 characters so you need to cut the licence up into consecutive strings, e.g.

license_string := 'first part of the license' + 'another part of the licence' +  '.....' + 'last part of the license.';

SigCaptX

HTML/Javascript

As illustrated in SigCaptX-SessionControl.js use the following code structure:

 sigCtl.PutLicence("licence_string", onSigCtlPutLicence);

If you are also using the WizCtl make sure that the licence string is applied to it in the same way, i.e.

 WizCtl.PutLicence("licence_string", onWizCtlPutLicence);

To make it easier to find the place where the licence string must be inserted in the sample code search for the string "<<license>>" in the appropriate source file.

The SDK samples can be downloaded from the Signature SDK and SigCaptX GitHub repositories.

To view the licence used in an application click the green icon in the Signature Capture window, then <About> to display licence information.


How can I get rid of the "Evaluation" watermark which appears on my pad?

The evaluation watermark image appears if you do not specify a licence key in your application code or if you use a non-Wacom signature pad.

The solution is to insert your licence string at the appropriate place in your application code.

If you are using one of the non-Wacom signature pads which we support such as the ePad-ink this needs a special licence which must be purchased from Wacom and applied within the code.

If no licence is applied, then by default a watermark saying "Evaluation" will appear on the signatures.

A production licence for the standard Signature SDK and SigCaptX is provided in the GETTING STARTED document alongside the sample code at https://github.com/Wacom-Developer/sdk-for-signature-windows

NOTE

The need for a licence key when using Wacom signature devices was removed with release 1.23.3 of the Signature SDK but reintroduced with release 3.13.2.

If you have an older release than 1.23.3 then removing the licence string from your code will not resolve the issue.

From 3.13.2 until 3.20.3 a short-style licence is required and the later, long-style licence (as provided on GitHub and on developer.wacom.com) will not work.

If you are using a release within the above range and do not want to upgrade your SDK please raise a support ticket (see link below) and request a short-style production licence.

If you have any further queries please raise a Support Ticket.


"LQ Wizard not licensed" or "DynCaptNotLicensed" error message

The most likely explanation for this error is that you have not installed the Signature SDK components on the PC where you are trying to capture a signature.

You must install the SDK as well as your signature application.


How do I obtain a licence for the Signature SDK and how much does it cost?

Evaluation licences

You can download evaluation licences from our Developer Relations Web site licensing section

These are normally valid for six months after which you can renew them or request a full licence.

Commercial licences

A production licence for the standard Signature SDK and SigCaptX is provided in the GETTING STARTED document alongside the sample code at https://github.com/Wacom-Developer/sdk-for-signature-windows.

Production licences are normally free unless you want to use the signature ISO format or data encryption functionality which was introduced very recently to the product or you want to use non-Wacom pen input devices (see below).

For details of the ISO and encryption enhancements please see the sections on "Signature Data Encryption" and Signature ISO Format" in the Signature Components API reference document which is provided in the "documentation" folder of the Signature SDK installation file.

The SDK itself can be downloaded at https://developer.wacom.com/en-us/developer-dashboard/downloads under "For signature".

Production licenses must be obtained from your regional Wacom internal sales contact. If you don't know who this is please contact the Wacom Solutions Team at solutions@wacom.eu for assistance.

A full commercial licence is permanent i.e. there is no need to renew or replace it.

It is also valid for every PC on which you install your application once you have included the license string in your code.


How do I capture signatures from non-Wacom devices?

There are three important factors to take into consideration if you want to capture signatures from a non-Wacom input device, such as one of the later Microsoft Surface models, or indeed any Windows-based touch-screen laptop or tablet which doesn't have a Wacom digitizer.

  1. It requires a fee-paid licence for which you will need to contact your regional Wacom Account Manager.
  2. You need to request the licence itself from the Ink Division Enterprise Support team - your Account Manager can arrange this.
  3. You will need to set the value of the CaptureService registry setting to "rts" so that it looks like this:

CaptureService REG_SZ rts

The registry setting itself should be located in HKLM\SOFTWARE\{WOW6432Node\}Florentis\sd.

The WOW6432Node element should be omitted if you are running on a 32-bit PC or using the 64-bit Signature SDK on a 64-bit PC.

The "sd" key will need to be created if it doesn't already exist, as will the CaptureService setting itself.


How can I deploy the Signature SDK and how many licences do I need?

In order to deploy a Signature SDK licence for use with your application in a live environment you must include the licence key in your application code.

You only need one licence key - this will enable signature capture on any PC where your application is installed.

A full licence is permanent - there is no need to renew it and it does not expire.


How to obtain the Static (SSV) or Dynamic (DSV) Signature Verification SDK

To obtain the SSV (Static Signature Verification) or DSV (Dynamic Signature Verification) SDK please send an email to the Wacom Solutions Team at solutions@wacom.eu or contact your regional Wacom Business Development Manager.


← Wacom Ink SDK for devicesInstallation →
  • Display the Signature SDK license
  • Remove 'Evaluation' watermark on signatures
  • No valid signature capture licence found
  • My production licence does not work
  • How to install a license
  • How can I get rid of the "Evaluation" watermark which appears on my pad?
  • "LQ Wizard not licensed" or "DynCaptNotLicensed" error message
  • How do I obtain a licence for the Signature SDK and how much does it cost?
  • How do I capture signatures from non-Wacom devices?
  • How can I deploy the Signature SDK and how many licences do I need?
  • How to obtain the Static (SSV) or Dynamic (DSV) Signature Verification SDK
FAQs
DOCS
IntroductionLicensingWacom Applications
COMMUNITY
TwitterLinkedInGitHub
ABOUT
Terms of UsePrivacyCookies
Wacom Developer Relations
Copyright © 2023 Wacom. All Rights Reserved. All other trademarks are the property of their respective owners and are used with their permission.