FAQs

FAQs

  • Overview
  • FAQs
  • Support
  • GitHub

›STU Tablet

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

STU-540 Operating Modes

Introduction

The STU-540 includes a number of alternative operating modes:

  • Normal
  • Signature Capture
  • Key Pad
  • PIN Pad
  • Slide Show

In the alternative operating modes the STU firmware processes the user interface, such as indicating a pushed button. This is achieved by preloading the tablet with images ready for immediate display.

This is particularly important when using the relatively slow serial interface since there is no need to transfer images between user interface operations. In addition the images are stored in non-volatile memory and can be managed independently.

Note that the STU-541 also supports the alternative operating modes.
The difference is that the STU-541 uses encrypted communication and does not support serial communications. Because of encryption the STU-540 test utilities are not compatible with the STU-541

Normal mode

The normal mode is unchanged from the older STU models.

Signature Capture mode

In the Signature Capture mode a capture screen is displayed as shown in the first image below. Up to three capture screens can be defined with the options - see second image.

Signature Capture

Signature Capture config

Signature Capture config

For further details see: STU-540 Signature Capture Mode

Key Pad mode

Use the Key Pad mode to make a selection by clicking a graphic. The Key Pad selection screen can be configured in a number of ways, for example:

Key Pad

Key Pad

Key Pad

For further details see: STU-540 Key Pad Mode

PIN Pad Mode

Use the PIN Pad mode to input a number. The PIN code entry screen can be configured in a number of ways as shown below. The 3 PIN pad types are illustrated followed by the 5 key layouts.

PIN Pad

PIN Pad layout

For further details see: STU-540 PIN Pad Mode

Slide show

Upload images to the tablet and select the auto display function. Store up to 10 images for a round robin display, with a programmable interval between each screen update.

For further details see: STU-540 Slide Show Mode

ROM

The images used by the different operating modes are stored in on-board flash memory (ROM) for immediate retrieval.

For further details see: STU-540 ROM Store


STU 540 Test Utilities

Downloads

FileDescription
STU-540-Test-Utilities.zipTest utilities
STU 540 Test Utilities src.zipC++ source code

The STU-540 can be used in standard USB HID mode or changed to operate as a serial Virtual Com Port (VCP) device (serial over USB connection).
The serial mode can be used when a remote connection is required and a full USB transfer is not possible. The serial interface is significantly slower than HID and the transfer of images takes a significant time.
This means that normal operation is impractical because there is a long delay between display updates while image data is uploaded.
To overcome this the STU-540 has a number of enhanced modes whereby images are preloaded on the device in non-volatile memory and displayed at runtime - this removes the need to upload images during operation.
The test utilities demonstrate these functions in HID and Serial modes.

To configure the STU-540 for USB or Serial operation see:
STU Serial Connection
Unzip the test utilities from STU-540-Test-Utilities.zip to a folder:

UtilityDescription
DemoButtons.exeDemonstrates signature mode
DemoKeyPad.exeDemonstrates key pad mode
DemoPinPad.exeDemonstrates pin pad mode
DemoSlideShow.exeDemonstrates slide show
DeleteRomImages.exeDeletes preloaded images

NOTE: To avoid the delays experienced uploading images, run the tests using the USB HID connection before attempting to use the serial mode.**

DemoButtons

Signature Mode

Capture Signatue Mode

The ‘Use Signature Mode’ option is used to switch between the conventional and on-board signature capture methods. The on-board Signature Mode is intended for use with slow serial connections.
Click [ Signature ] - this will start signature capture using the STU-540 signature capture mode (over HID):

Capture Signatue Mode

The first time DemoButtons runs, the images it needs for signature capture mode will be uploaded to the tablet. Since they are stored in ROM they will not be uploaded again.
It is advisable to use HID mode to upload the images. To exit, press a button on the STU display (not Windows).

Signature Capture over Serial

Run DemoButtons.exe and select the following:

  • Select ‘Use serial connection’
  • Select Port to match the Virtual Port used in query.exe
  • Set Baud rate to 128000
  • Select ‘Use Signature Mode’
  • Click [ Signature ] to start signature capture

Capture Signatue Mode

Capture Signatue Mode

Because the images were uploaded in the HID test they are immediately available and there is no delay in signing or clearing the screen etc.
To emphasise the effectiveness of the signature capture mode, deselect ‘Use Signature Mode’. This method uses the conventional image upload method and takes a considerable time to start because the full screen image is uploaded at runtime:

Capture Signatue Mode

Capture Signatue Mode

DemoKeyPad

The demo uses the Key Pad mode to make a graphic user selection. The first time the program runs it uploads the images it needs.

KeyPad Mode

KeyPad Mode

DemoPinPad

The demo uses the PIN Pad mode to enter a PIN code. The first time the program runs it uploads the images it needs.

PinPad Mode

PinPad Mode

DemoSlideShow

The demo uses the slide show mode to display a number of images. The first time the program runs it uploads the images it needs. The images display continuously on the tablet until stopped.

SlideShow Mode

DeleteRomImages

The utility deletes all images stored on the STU tablet.

Delete Rom

Use query.exe from STU Serial Connection to view the hash values of images stored in ROM. The values indicate the storage status of an image, for example:

RomImageHash[Signature,1,normal]          = 6686b765cb00bcdefd40a0f53c58d46a  
RomImageHash[Signature,1,pushed]          = 1b4bf1afd08396de7fd8715749bd9274   
RomImageHash[Signature,2,normal]          = not stored   
RomImageHash[Signature,2,pushed]          = not stored  

Signature Capture Mode Reference

In Signature Capture mode a predefined screen is displayed, ready for the user to sign, for example:

Signature Mode

In addition to pen colour and thickness, the WILL option (Wacom Ink Layer) can be enabled so that a smooth pen trace is displayed with variable thickness dependent on pen pressure.

Image Design

Define up to three signature capture designs. Each design defines the images used for normal and button pushed displays in the following format:

Signature Mode

Below is an example of a normal image followed by a corresponding keys pushed image:

Signature Mode

Signature Mode

Signature Area

After entering Signature Capture mode, the signature screen from the normal image is shown. The signature area size is 800 dots * 431 dots.
Additional information such as name and reason, can be shown by writing to the signature area after setting the Signature Capture mode.

Operation Area

Button images are included in the normal image. Pushed button images are included in the button pushed image. When a button is pushed, the corresponding button image is displayed. The size and location of each button:

Button NoSize (w * h)Location (x,y)
1265 * 480, 431
2265 * 48266, 431
3265 * 48532, 431

Signature Image settings

Each signature screen requires the settings:

ItemPattern 1
Image design numberImage design number 1..3
Signature screen (Normal)Image data includes normal buttons, initial message and background image
Signature screen (button pushed)Image data includes pushed buttons and background image
Keys Enabled settingThe bitmask (1..3) allows individual keys/buttons to be enabled (1) or disabled (0) as follows:
   Bit 0: key1 - Cancel.   Bit 1: key2 - Clear.   Bit 2: key3 - OK

Signature Capture Operation

Before entering Signature Capture mode the images and settings must be stored. The following options must be set when entering Signature Capture mode:

ItemDescription
Signature Screen SelectSelect Signature screen design from pattern 1..3
MessageBox id after EnterMessageBox screen to show after Enter was pressed
MessageBox id after CancelMessageBox screen to show after Cancel was pressed

Signature Capture Return

UI Event Data reports the selected key number:

ItemDescription
Key value0: Cancel    1: Enter    2: Clear

 

In addition to sending the report:

ButtonDescription
OKClear screen and return to Normal mode
ClearClear screen and redisplay the initial signature capture box screen
CancelClear screen and return to Normal mode

Signature Capture logic

Signature Mode

API Reference

FunctionDescription
initializeSignatureSignature Capture settings
writeRomImageTablet write ROM functions
setOperationModeSelect Signature Capture mode

Code illustration

Upload Image

See STU-540 ROM Store

Requires image descriptor:

romStartImageData = initializeSignature(m_encodingMode, pushed, SIG_IMAGE_NUM, array<bool, 3>{ true, true, true}) );
Start Signature mode
// 0=Cancel; 1=Enter; 2=Clear
OperationMode_Signature sigOpMode{ SIG_IMAGE_NUM,{ 2, 0, 1 }, 0, 0 };
OperationMode opMode = initializeSignature(sigOpMode);
m_tablet.setOperationMode(opMode);
Receive Pen Data
Decode Pen Data from ReportHandler
onReport(PenData & v)
{
  save(penData);
  PostMessage(m_hwnd, WM_USER, 0, 0);
}
...

// Dialog callback

case WM_USER:
    processPenData();
...
Receive the UI Event
Decode the UI Event data from ReportHandler
onReport(EventDataSignature & eventDataSignature)
{
  switch (eventDataSignature.keyValue)
  {
  case 0:
    processCancel();

  case 1:
    processOK();

  case 2:
    processClear();
  }
}
...

Key Pad Mode Reference

In the Key Pad mode a graphic key pad is displayed for user selection, for example:

KeyPad Mode

The general implementation is as follows:

  • Upload Key Pad images
  • Start the Key Pad mode
  • Receive a return code

The images used in the process need only be uploaded once for multiple use. A hash mechanism is provided to determine whether or not the images have already been stored on the STU tablet.
If required the message area can be changed while the tablet is in Key Pad mode.

Key Pad Type

Select the Key Pad type from one of the following:

KeyPad Mode

Image Design

Define up to three Key Pad designs. Each design contains the images used for the Key Pad selection formatted for the type. An example of a KeyPad type 1 normal image is shown below followed by the corresponding keys pushed image.

KeyPad Mode

KeyPad Mode

Key Pad Type 1 Image Design

KeyPad Mode

ItemSize (w * h)Location (x,y)
Message Area800 * 640,0

 

Button NoSize (w * h)Location (x,y)
1240 * 11930, 73
2240 * 119280, 73
3240 * 119530, 73
4240 * 11930, 202
5240 * 119280, 202
6240 * 119530, 202
7240 * 11930, 331
8240 * 119280, 331
9240 * 119530, 331

 

Key Pad Type 2 Image Design

KeyPad Mode

ItemSize (w * h)Location (x,y)
Message Area800 * 2200,0

 

Button NoSize (w * h)Location (x,y)
1240 * 10330, 234
2240 * 103280, 234
3240 * 103530, 234
4240 * 10330, 347
5240 * 103280, 347
6240 * 103530, 347

Key Pad Type 3 Image Design

KeyPad Mode

ItemSize (w * h)Location (x,y)
Message Area514 * 480286,0

 

Button NoSize (w * h)Location (x,y)
1240 * 9630, 30
2240 * 96280, 128
3240 * 96530, 246
4240 * 9630, 354

Key Pad Settings

Up to three Key Pad image designs can be stored. For each design supply:

ItemDescription
Image design numberImage design number 1..3
Normal Key Pad screenImage data includes normal buttons, initial message and background image
Button pushed Key Pad screenImage data includes pushed buttons and background image
KEY Pad typeType 1..3
KEYs Enabled settingThe bitmask (1..9) allows individual keys/buttons to be enabled (1) or disabled (0):
   Bit 0: key1    Bit 1: key2    Bit 2: key3 etc.
Key Pad Mode Settings

Before entering Key Pad mode, the images and settings must be stored. The following options must be set when entering Key Pad mode:

ItemDescription
Key Pad Screen SelectSelect Key Pad screen design from pattern 1..3
Select Message idMessage Box screen to show after an image has been selected
Key Pad Mode Return

UI Event Data reports the selected key number:

ItemDescription
Key Pad Screen SelectKey Pad screen design from pattern 1..3
Selected Key NumberKey number 1..9 dependent on Key Pad type

Key Pad Operation logic

KeyPad Mode

API Reference

FunctionDescription
initializeKeyPadKey Pad settings
writeRomImageTablet write ROM functions
setOperationModeSelect Key Pad mode

Code illustration

Upload Image

See STU-540 ROM Store

Requires image descriptor with buttons enabled mask:

array<bool, 9> KeyPad::m_btnEnabled = { 1, 1, 1, 1, 1, 1, 1, 1, 1 };
romStartImageData = initializeKeyPad(encodingMode, pushed, m_layoutNum, m_layoutNum, m_btnEnabled);
Start Key Pad mode
OperationMode_KeyPad KeyPadMode{ m_layoutNum, 0 };

OperationMode opMode = initializeKeyPad(KeyPadMode);
tablet.setOperationMode(opMode);
Receive the UI Event
Decode the UI Event data from ReportHandler
onReport(EventDataKeyPad & e)
  {
    PostMessage(m_hWnd, WM_KEYPAD_RESULT, MAKEWORD(e.keyNumber, e.screenSelected), 0);
  }
...

// Dialog callback

case WM_KEYPAD_RESULT:
  {
    keyNumber = LOBYTE(wParam);
    screenSelected = HIBYTE(wParam);
  }
...

PIN Pad Mode Reference

In the PIN Pad mode a numeric keypad is displayed for user input, for example:

PINPad Mode

PIN Pad Type

Select the PIN pad type from one of the following:

PINPad Mode

Key Layout

Select the key layout from one of the following:

PINPad Mode

Image Design

Define up to three PIN Pad designs. Each design defines the images used for normal and button pushed displays in the following layout:

PINPad Mode

Below is an example of a normal image followed by a corresponding keys pushed image:

PINPad Mode

PINPad Mode

Message Area:

After entering PIN pad mode, the initial message area from the normal image is shown. When an error occur, the message area from the keys pushed image is shown. The message area size is 800 x 55 dots.

PIN display area:

The characters displayed when pressing a (0~9, *, # and .) are included in the normal image. The display area size is 665 x 74 dots.
The PIN code display image size is 49 x 66 dots. The location of this area is (68, 55) from the top left corner.
The size and location of each PIN code:

PIN codeSize (w * h)Location (x,y)
049 * 6672, 59
149 * 66121, 59
249 * 66170, 59
349 * 66219, 59
449 * 66268, 59
549 * 66317, 59
649 * 66366, 59
749 * 66415, 59
849 * 66464, 59
949 * 66513, 59
*49 * 66562, 59
#49 * 66611, 59
.49 * 66660, 59
PIN pad area:

Button images are included in the normal image. Pushed button images are included in the button pushed image. When a button is pushed, the corresponding button image is displayed.
The size and location of each button:

ButtonsSize (w * h)Location (x,y)
0174 * 66217, 384
1174 * 6630, 147
2174 * 66217, 147
3174 * 66404, 147
4174 * 6630, 226
5174 * 66217, 226
6174 * 66404, 226
7174 * 6630, 305
8174 * 66217, 305
9174 * 66404, 305
'*' or '.'174 * 6630, 384
# or 00174 * 66404, 284
Clear174 * 89596, 147
Cancel174 * 89596, 254
Enter174 * 89596, 361

PIN Pad Image Settings

Each image design requires the settings:

ItemDescription
Image design numberImage design number 1..3
PIN pad normal imageImage data includes normal buttons, initial message, PIN code display fonts and background image
PIN pad buttons pushed imageImage data includes pushed buttons, error message and background image
PIN pad typeKeypad type 1..3
Key layoutRound Robin or specific key layout 0..5

PIN Operation settings

Before entering PIN pad mode, the images and settings must be stored. The following options must be set when entering PIN pad mode.

ItemDescription
PIN Pad ImageSelect the PIN pad image design from pattern 1..3
PIN BypassSet PIN Bypass=1 to disable the minimum digits check
Minimum digitsIf the PIN input is below Minimum the error message is shown and Min Digit Error is reported
Maximum digitsIf the PIN input exceeds Maximum the error message is shown and Max Digit Error is reported. The maximum number of digits is 12
Number Hidden ModeIf this mode is enabled, PIN input codes are shown for 500msec and hidden by *. If the next PIN is input within 500msec, the previous value is hidden by * after input.
Enter Message idMessageBox screen to show after Enter
Cancel Message idMessageBox screen to show after Cancel

PIN Pad Mode Return

UI Event Data reports the list of selected keys as follows:

ItemValue
Key Input0x00: Cancel (PIN values = 0xF)   0x01: Enter    0x02: Min Digit Error (PIN values = 0xF)    0x03: Max Digit Error (PIN values = 0xF)
List of PIN codes in the order selected (1..13)0 to 9    0x0A = *    0x0B = #    0x0C = .

In addition to sending the report:

ButtonFunction
0 to 9Store pushed button number
* . # 00Store pushed character 00: Store 00 and show 2 digits 00
ClearClear input PIN code and clear PIN display area e.g. If Clear button is pushed after 1, 2, 3 are input, all 1, 2, 3 are cleared.
EnterCondition 1: Input PIN code digits are within (Max, Min) digit setting: Output PIN code and exit from PIN pad mode to Normal mode. Condition 2: Input PIN code digits are below (Min) digit setting: Show error message for 2 seconds and exit from PIN pad mode to Normal mode with Min Digit Error report
CancelIssue Cancel Report and exit from PIN pad mode to Normal mode.

PIN Operation logic

PINPad Mode

API Reference

FunctionDescription
initializePinPadPIN Pad settings
writeRomImageTablet write ROM functions
setOperationModeSelect PIN Pad mode

Code illustration

Upload Image

See STU-540 ROM Store

Requires image descriptor:

romStartImageData = initializePinPad(encodingMode, pushed, PINPAD_IMAGE_NUM, PINPAD_TYPE, PINPAD_LAYOUT);
Start PIN Pad mode
OperationMode_PinPad pinPadMode{ PINPAD_IMAGE_NUM,
  0,
  m_minDigits,
  m_maxDigits,
  m_hideNumbers ? 1u : 0u,
  PINPAD_LAYOUT,
  0,
  0 };
OperationMode opMode = initializePinPad(pinPadMode);
m_tablet.setOperationMode(opMode);
Receive the UI Event
Decode the UI Event data from ReportHandler
onReport(EventDataPinPad & e)
  {
    switch (e.keyInput)
    {
      case InputEnter:
        m_pinPad = savePin(e);
      case InputCancel:
      case InputMinDigit:
      case InputMaxDigit:
    PostMessage(m_hWnd, WM_PINPAD_EVENT, e.keyInput, 0);
    }
  }
...

// Dialog callback

case WM_PINPAD_EVENT:
  switch (wParam)
  {
  case InputEnter:
    {
    pin = getSavedPin();
    }
... 

Slide Show Reference

In the slide show mode, stored images are shown automatically for a set interval and order. The slide show will continue until a new mode is selected.

Image Design

Define up to 10 images with the format:

ItemDescription
Image numberImage number 1...10
Image formatBitmap (24bit color, 16bit color, Monochrome)
Image resolution800 x 480 dots

Slide Show Mode Settings

Before entering the Slide Show mode, the images must be stored. The following options must be set when entering Slide Show mode:

ItemsDescription
Working modeRound robin mode: Selected images are shown for the set interval and order.   Single mode: Selected image is shown (only one image is shown)
Number of slidesDefines the number of images for round robin display
First slide numberDefines the image to start the slide show
IntervalSlide show interval: Min. 2000msec   Max. 120000msec

Slide show logic

Slide Show

API Reference

FunctionDescription
initializeSlideShowSlideShow settings
writeRomImageTablet write ROM functions
setOperationModeSelect Slide Show mode

Code illustration

Upload Images

Upload up to 10 images, see STU-540 ROM Store

Requires image descriptor:

romStartImageData = initializeSlideShow(encodingMode, false, bitmapNumber);
Start slide show mode
OperationMode_SlideShow slideShow;

slideShow.workingMode = 0;
slideShow.numberOfSlides = 3;
slideShow.slideNumber[0] = 1;
slideShow.slideNumber[1] = 2;
slideShow.slideNumber[2] = 3;
slideShow.interval = 2000;

tablet.setOperationMode( initializeSlideShow(slideShow) );


ROM Store Reference

Description

ROM storage is allocated as follows:

Image TypeDescription
PIN padPIN pad mode image not-pushed (1 to 3)
PIN pad pushedPIN pad mode image pushed (1 to 3)
SlideSlide show image (1 to 10)
Key padKey pad mode image not-pushed (1 to 3)
Key pad pushedKey pad mode image pushed (1 to 3)
SignatureSignature mode image not-pushed (1 to 3)
Signature pushedSignature mode image pushed (1 to 3)
MessageMessageBox Image (1 to 6)

Validate a stored ROM Image

Compute hash for required image

Compute the MD5 hash of the required image, for example by using an encryption library function.

Get hash for stored image

Retrieve the hash in two steps:
 
1. Request operation:

ItemMessage
Operation ModeMode 1...5
Image designImage design number
Image pushed0/1: non-pushed/pushed image (0 for MessageBox images)
Result0: Succeeded (image was stored)    1: No image stored

 

2. Get operation:

ItemMessage
Operation ModeMode 1...5
Image designImage design number
Image pushed0/1: non-pushed/pushed image design (0 for MessageBox images)
Hash128 bit hash

Upload image

Upload an image if no image is stored or the calculated and retrieved hash values do not match.
Image data is sent in three steps:

  • Start ROM Image Data
  • Write Image Data
  • End Image Data

The Tablet interface simplifies the process with a single writeRomImage function.

Start ROM Data:
ItemMessage
Encoding mode0x04: 24bit Color RAW data format 0x14 24bit Color RAW data format (Bulk)
Operation ModeMode 1..5:    1: PIN Pad mode   2: Slide show mode    3: Key Pad mode   4: Signature mode    5: MessageBox
Image designImage design number
Image pushed0/1: non-pushed/pushed image design (0 for MessageBox images)
Image DescriptorDefined for each image type
Write Image data:
ItemMessage
Data Block SizeNumber of bytes
Image DataImage data
End Image Data:
ItemMessage
Commit Flag0/1: Commit/Abandon

Start ROM Image Descriptors

PIN Pad

ItemDescription
Image design numberImage design number 1..3
PIN pad normal imageImage data includes normal buttons, initial message, PIN code display fonts and background image
PIN pad buttons pushed imageImage data includes pushed buttons, error message and background image
PIN pad typeKeypad type 1..3
Key layoutRound Robin or specific key layout 0..5

Slide Show

ItemDescription
Image formatBitmap (24bit color, 16bit color, Monochrome)
Image resolution800 x 480 dots

Key Pad

ItemDescription
Image design numberImage design number 1..3
Normal Key Pad screenImage data includes normal buttons, initial message and background image
Button pushed Key Pad screenImage data includes pushed buttons and background image
KEY Pad typeType 1..3
KEYs Enabled settingThe bitmask (1..9) allows individual keys/buttons to be enabled (1) or disabled (0):   Bit 0: key1   Bit 1: key2   Bit 2: key3 etc.

Signature Capture

ItemDescription
Image design numberImage design number 1..3
Signature screen (Normal)Image data includes normal buttons, initial message and background image
Signature screen (button pushed)Image data includes pushed buttons and background image
KEYs Enabled settingThe bitmask (1..3) allows individual keys/buttons to be enabled (1) or disabled (0):    Bit 0: key1 - Cancel   Bit 1: key2 - Clear   Bit 2: key3 - OK

Message Box

ItemMessage
Message Box numberMessage ID 1..10
Message screenMessage screen image data

API Reference

FunctionDescription
getRomImageHashTablet get hash function
writeRomImageTablet write ROM functions

Code illustration

Upload Image

The code illustrates uploading a SlideShow image

uploadImage(...)
{
writeImage = true;

// get the hash of the image stored in ROM (if it exists) 
tablet.setRomImageHash(operationModeType, imageType, imageNumber);
romImgHash = tablet.getRomImageHash();

if (romImgHash.result == 0)
  {
    // there is already an image on the tablet - check it is the right one
    // compute hash of the required image
    imgHash = getImageHash(bitmapData.data(), bitmapData.size());           
    if (imgHash == romImgHash.hash)
    {
      // image matches, no need to write it again
      writeImage = false;
    }
  }

if (writeImage)
  {
  romStartImageData = initializeSlideShow(encodingMode, imageType, imageNumber);    
  tablet.writeRomImage(romStartImageData, bitmapData.data(), bitmapData.size());
  }
}

← STU-430V InstallationSTU-540 Serial Installation →
  • Introduction
    • Normal mode
    • Signature Capture mode
    • Key Pad mode
    • PIN Pad Mode
    • Slide show
    • ROM
  • STU 540 Test Utilities
    • Downloads
    • DemoButtons
    • DemoKeyPad
    • DemoPinPad
    • DemoSlideShow
    • DeleteRomImages
  • Signature Capture Mode Reference
    • Image Design
    • Signature Capture logic
    • API Reference
  • Key Pad Mode Reference
    • Image Design
    • Key Pad Operation logic
    • API Reference
  • PIN Pad Mode Reference
    • Image Design
    • PIN Operation logic
    • API Reference
  • Slide Show Reference
    • Image Design
    • Slide show logic
    • API Reference
  • ROM Store Reference
    • Description
    • Validate a stored ROM Image
    • Upload image
    • API Reference
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.