Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

tagpossible valuesdescription

x

y

0 ... 65535position of pen onb the touch pad
z

0 ... 1023

32768 .. 65535 (only EM-Pen)

pressure, 0=data frame is not used

>=32768 EM-Pen, hovering above the em-pad

f0 ... 255frame number from Pad
l0 ... 65535line number
t0 ... 65535

Time code

p0-0-0-0-0Process-ID,5 numbers separated with '-'
g0:0:0 0.0.0GMT timestamp of the internal clock of the Pad (Format: (H)H:(M)M:(S)S (d)d.(m)m.(y)y )
d0-0-0-0-0-0

Pad Dimension

SensorSize Min X, Min Y, Max X, Max Y, DPI Horizontal, Vertikal

s0 ... 65535page number of the PDF where the signature is done (inserted from eSO)
n'-' , <NAME>Name of the person which signed. '-' = no person defined (inserted from eSO)
$r'-', <REASON>Reason of the signature. '-' = no reason defined (inserted from eSO)
$c0.0.0.0, <Left>.<Top>.<Right>.<Bottom>Rectangle of signature in PDF-coordinates (inserted from eSO)
$t<day>.<month>.<year> <hour>:<minute>:<seconds>Date/Time of embedding the signature in PDF document. day,month,hour,minute,seconds always 2 chars, year always 4 chars (inserted from eSO)
$l'', <Location>Location, empty string if not defined (inserted from eSO)
b Pad 255 ?
   

 

Note:  There is a known Firmware issue with the line number, which is not correctly resetting the value between 2 signatures. The first signature after device restart starts with Line number 0, but the following signatures starts with the line number of the last signature. Best solution is to ignore this values until first 0 comes.