LibConvert2

Manual

Author: RA
Date: 31.03.2015
Version: 1.04
This manual applies to LibConvert2 starting from version [Link].
See chapter Manual history for comments about new LibConvert2 features and updates to this manual.

© P.V. Supa Oy Ltd

1
Table of Contents
Overview .................................................................................................................................................. 7
Manual history ...................................................................................................................................... 7
Version 1.01 ...................................................................................................................................... 7
Version 1.02 ...................................................................................................................................... 7
Version 1.03 ...................................................................................................................................... 7
Version 1.04 ...................................................................................................................................... 7
Requirements ....................................................................................................................................... 8
Installation................................................................................................................................................ 8
Settings file........................................................................................................................................... 8
Local database ..................................................................................................................................... 8
SQL Express ..................................................................................................................................... 8
Access .............................................................................................................................................. 9
Common application data folder ........................................................................................................... 9
Common files folder ........................................................................................................................... 10
Rfid reader initialization file ................................................................................................................. 10
Section READER ............................................................................................................................ 11
Section DATAMODEL ..................................................................................................................... 11
Section SECONDARYDATAMODEL ............................................................................................... 12
Section SECURITY ......................................................................................................................... 12
Section DANISH ............................................................................................................................. 12
Section FINNISH ............................................................................................................................ 13
Section TV2 .................................................................................................................................... 13
Section ISO 28560-2....................................................................................................................... 13
Section ITG ..................................................................................................................................... 14
Section DUTCH .............................................................................................................................. 14
Section MISC .................................................................................................................................. 14
Nedap exceptions ........................................................................................................................... 14
Setup ..................................................................................................................................................... 15
General .............................................................................................................................................. 15
Conversion Session ........................................................................................................................ 15
ToolTips .......................................................................................................................................... 15

© P.V. Supa Oy Ltd

2
 Full Screen ..................................................................................................................................... 15
Language........................................................................................................................................ 16
RFID................................................................................................................................................... 16
Reader ............................................................................................................................................ 16
Initialization ..................................................................................................................................... 16
Tags ................................................................................................................................................ 17
Tag Data ............................................................................................................................................. 18
Data Model ..................................................................................................................................... 18
Functions ........................................................................................................................................ 18
Multipart Items .................................................................................................................................... 19
Tag sharing ..................................................................................................................................... 19
Connections ....................................................................................................................................... 19
Local History Database ................................................................................................................... 19
History Database Server ................................................................................................................. 20
ItemId service ................................................................................................................................. 20
Weeding ......................................................................................................................................... 20
Barcode .............................................................................................................................................. 21
Filter ............................................................................................................................................... 21
Misc.................................................................................................................................................... 21
Convert to file.................................................................................................................................. 21
User interface ........................................................................................................................................ 22
Start-up page ..................................................................................................................................... 22
Start Session .................................................................................................................................. 23
Setup .............................................................................................................................................. 24
Exit ................................................................................................................................................. 24
Help ................................................................................................................................................ 24
Session page ..................................................................................................................................... 25
Item ID and Tags read fields ........................................................................................................... 25
Get item id ...................................................................................................................................... 26
Parts count selection....................................................................................................................... 27
Usage type selection....................................................................................................................... 28
Media type selection ....................................................................................................................... 28
Instruction text ................................................................................................................................ 29
Conversion history .......................................................................................................................... 32
Tags ................................................................................................................................................ 33

© P.V. Supa Oy Ltd

3
 Buttons ........................................................................................................................................... 35
Weeding ............................................................................................................................................. 35
Warning only ................................................................................................................................... 36
Warning with popup message ......................................................................................................... 36
Warning with question popup .......................................................................................................... 36
Shortcut Keys ..................................................................................................................................... 37
Start-up screen ............................................................................................................................... 37
Session screen ............................................................................................................................... 38
Data model conversion .......................................................................................................................... 39
Standard mode ................................................................................................................................... 39
Danish to ISO 28560-2 ................................................................................................................... 40
ISO 28560-2 to Danish ................................................................................................................... 40
TV2 to ISO 28560-2 ........................................................................................................................ 41
Background mode .............................................................................................................................. 41
Danish to ISO 28560-2 ................................................................................................................... 41
ISO 28560-2 to Danish ................................................................................................................... 42
TV2 to ISO 28560-2 ........................................................................................................................ 42
Supported data models .......................................................................................................................... 42
Danish ................................................................................................................................................ 43
Mandatory fields ............................................................................................................................. 43
Optional fields ................................................................................................................................. 44
Dutch.................................................................................................................................................. 45
Mandatory fields ............................................................................................................................. 45
Optional fields ................................................................................................................................. 46
French ................................................................................................................................................ 47
Encoded fields ................................................................................................................................ 47
ISO 28560-2 ....................................................................................................................................... 49
Mandatory element ......................................................................................................................... 50
Optional elements ........................................................................................................................... 50
ITG ..................................................................................................................................................... 51
Encoded fields ................................................................................................................................ 51
QUEENS ............................................................................................................................................ 52
Item id ............................................................................................................................................. 52
TV2 .................................................................................................................................................... 53
Mandatory fields ............................................................................................................................. 53

© P.V. Supa Oy Ltd

4
 Optional fields ................................................................................................................................. 53
Finnish ............................................................................................................................................... 54
Log ........................................................................................................................................................ 54
ANNEX A: Setup screens....................................................................................................................... 55
General .............................................................................................................................................. 55
RFID................................................................................................................................................... 55
Tag Data ............................................................................................................................................. 56
Multipart Items .................................................................................................................................... 56
Connections ....................................................................................................................................... 57
Barcode .............................................................................................................................................. 57
Misc.................................................................................................................................................... 58
ANNEX B: Programming tags ................................................................................................................ 59
Example 1: Single item from barcode ................................................................................................. 59
Example 1: Step 1 – Start session .................................................................................................. 59
Example 1: Step 2 – Session started .............................................................................................. 60
Example 1: Step 3 – Item on antenna ............................................................................................. 61
Example 1: Step 4 – Converting...................................................................................................... 62
Example 1: Step 5 – Item converted ............................................................................................... 63
Example 2: Set from barcode ............................................................................................................. 64
Example 2: Steps 1 and 2 ............................................................................................................... 64
Example 2: Step 3 – Items on antenna ........................................................................................... 64
Example 2: Step 4 – Enter item id ................................................................................................... 65
Example 2: Step 5 – Converting...................................................................................................... 66
Example 2: Step 6 – Items converted.............................................................................................. 67
Example 3: Single item with new item number ................................................................................... 68
Example 3: Steps 1 and 2 ............................................................................................................... 68
Example 3: Steps 3 – Enter item id ................................................................................................. 68
Example 3: Step 4 – Converting...................................................................................................... 69
Example 3: Step 5 – Item converted ............................................................................................... 70
Example 4: Single item from barcode, error during conversion ........................................................... 71
Example 4: Steps 1 to 4 .................................................................................................................. 71
Example 4: Step 5 – Error ............................................................................................................... 71
Example 4: Step 6 – Item converted ............................................................................................... 72
ANNEX C: Windows Device Manager .................................................................................................... 72
ANNEX D: Reader initialization file example .......................................................................................... 72

© P.V. Supa Oy Ltd

5
ANNEX E: Tag file format file ................................................................................................................. 75

© P.V. Supa Oy Ltd

6
Overview
LibConvert2 is used to program existing barcode information into rfid tags or to program rfid tags with
new item numbers along with other data model dependent information.
LIbConvert2 supports commonly used data models and reader manufacturers.

Manual history

Version 1.01
Added explanation of new features provided by LibConvert2 version [Link].
 Data model conversion from data models Danish and TV2 into data model ISO 28560-2
 New rfid reader initialization file parameters MinItemIdLength and MaxItemIdLength into
section ISO 28560-2
 New parameter Show data model name into setup page Tags.
 New parameters Convert automatically to main data model and Use standard mode with
automatic data model conversion added to setup page Tag Data

Version 1.02
Added explanation of new features provided by LibConvert2 version [Link].
 Data model conversion from data model ISO 28560-2 into data model Danish
 Barcode length and starts with filtering

Version 1.03
Added explanation of new features provided by LibConvert2 version [Link].
 Parameter Check that the serial port is free (session startup) into setup page RFID
 Setup page Misc with new functionality Convert to file
 New rfid reader Initialization mode at session startup
 Write also alternate item id on tag when Danish data model is used

Version 1.04
Added explanation of new features provided by LibConvert2 version [Link].
 Option to read block security status from rfid tags

© P.V. Supa Oy Ltd

7
Requirements
 Windows operating system XP or later
 .NET Framework 4 Client Profile or .NET Framework 4

Installation
Installation requires administrator rights.
To install LibConvert2 unpack LibConvert2_x.[Link] and run [Link].
Installation sequence:
 Accept license agreement
 Choose how to handle conversion history. See chapter local database for more information.
 Select installation path, default path is recommended
During installation PV LibConvert2 log is created, required security permissions for authenticated users
are given to PV-Supa folder in common application data folder and settings file with default values is
created.

Settings file
Settings file is called “[Link]” and it is located in folder “\PV-Supa\LibConvert2” under common
application data folder.
Settings file is in xml format and it is permanent so updating or uninstalling LibConvert2 does not
remove the file or erase settings.
Backing up all settings, beside rfid reader settings, can be done by copying the “[Link]” file into
desired location.

Local database
LIbConvert2 can be set to store conversion history into database. Two database types can be selected
during installation or later changed from setup.
See chapter Local History Database for instructions how to change the storage plan after installation.

SQL Express
In case SQL Express is selected to store local conversion history it must be installed and started before
running LibConvert2.

© P.V. Supa Oy Ltd

8
Content of the database can be viewed for example with Microsoft SQL Server Management Studio.
Conversion history is stored into table CNV_CONVERSION in database SUPA.
With Windows 7 and UAC enabled it might be necessary to add quest user sufficient privileges into SUPA
database for storing of history to work.

Access
Access database does not require any additional software to be installed. To store the conversion history
[Link] access database file is used and it is located in common application data folder.
Access file can be opened for analyzing with Microsoft Access. LibConvert2 conversion history is stored
into table CNV_CONVERSION.

Common application data folder

LibConvert2 stores settings and language texts into LibConvert2 folder that is located under PV-Supa
common application data folder.
Access database file if required is stored into PV-Supa common application data folder.
Default locations of PV-Supa common application data folder in English windows.
 Windows XP – C:\Documents and Settings\All Users\Application Data\PV-Supa\
 Windows 7 - C:\ProgramData\PV-Supa\

By default common application data

folder is a hidden folder, but It can
be accessed for example by entering
command line
“%allusersprofile%\PV-Supa” into
“Run”.

Figure 1: Open common application data folder from Run

© P.V. Supa Oy Ltd

9
Common application data folder can
also be accessed by entering
“%allusersprofile%\PV-Supa” into
Windows Explorer navigation field.

Figure 2: Open common application data folder from Windows Explorer

Common files folder

LibConvert2 installs commonly used files that are shared by all P.V. Supa applications into PV-Supa folder
that is located under common files folder. These files include files required by licensing, MasterController
connection and rfid reader connection.
All files in PV-Supa common files folder are shared legacy files, except license file which is permanent,
which means as long as there is even one P.V. Supa application installed that requires these files the files
are not removed on uninstall. However in case LibConvert2 is the only installed P.V. Supa application all
files are removed on uninstall, except the license file, and therefore it is recommended to back up the
rfid reader initialization file after the installation and configuration is done.
Default location of PV-Supa common files folder in English windows.
 32 bit windows, C:\Program Files\Common Files\ PV-Supa\
 64 bit windows, C:\Program Files (x86)\Common Files\PV-Supa\

Rfid reader initialization file

Rfid reader Initialization files are located in common files folder and named by manufacturer type with
suffix “[Link]”, for example [Link].
Purpose of this manual is not to explain every initialization file parameter in detail, instead a brief
explanation of most commonly used parameters that affect rfid tag programming are explained.
Data models that support writing but are not mentioned in this chapter do not have any parameters that
would require configuration section in reader initialization files.
In the comment line of many parameters a definition for default value can be found, this means that if
the parameter is removed, does not exist or is commented out (a semicolon in front) from the
initialization file, which value is used in this case.
A good example of this is parameter DefaultByteOrder in section MISC. Setting this parameter incorrectly
can cause improperly programmed tags so the value is by default commented out and default byte order
is always used. See chapter Section MISC.

© P.V. Supa Oy Ltd

10
[MISC]
; Set default byte order, 0 no, 1 yes, default yes
; DefaultByteOrder = 0

Backing up the reader settings can be done by copying the reader initialization file into desired location.
See chapter ANNEX D: Reader initialization file example for an example of [Link] file.

Section READER
Section reader contains parameters that affect the communication between client application, such as
LibConvert2 and the rfid reader.
In most of the cases only two parameters serial port and polling interval require changes.
ComPort
Rfid reader communication port must always be set after reader is connected to computer and in case of
USB readers the necessary drivers are installed.
Serial port is the only rfid reader setting that can be configured from the setup screen of LibConvert2 on
page RFID reader.
Installed serial ports are shown in setup dialog and can also be found from windows device manager.
See chapter ANNEX C: Windows Device Manager for an example.
With Feig USB readers the Comport parameter can be left to default value “COM1” as Feig USB readers
do not use virtual serial port for communication.
[READER]
; Port
ComPort = COM1

PollingInterval
Polling interval parameter affects how often the rfid reader creates an inventory of the rfid tags present
on the antenna. Polling interval affects how quickly tags are detected and how quickly removal of tags is
detected. Setting too low value for polling interval can exhaust the reader and cause slowness.
In case polling interval is too high and user removes tags quickly after tags are programmed the tags
count field on LibConvert2 might not be updated. If this happens often the polling interval value should
be lowered to 200 (milliseconds) except with Nedap readers, see chapter Nedap exceptions.
By default the polling interval is set to 500, except in Nedap initialization file.
[READER]
; Polling interval (in milliseconds)
PollingInterval = 500

Section DATAMODEL
In section DATAMODEL the data model that is used to program rfid tags must be set. List of data models
that support tag programming can be found in chapter Supported data models.

© P.V. Supa Oy Ltd

11
By default the data model type is set to “Danish”.
[DATAMODEL]
; Main Data model. First to analyze when tag is read and used when writing tags
; Danish, Finnish, Nec, Queens, TechLogic, TV2, 3M, TRC, ITG, ITG2, ISO-28560-2, Dutch, French or Raw
Type = "Danish"

Section SECONDARYDATAMODEL

Section SECURITY
In section SECURITY the method that is used to write security must be set.
After tag is programmed LibCovnert2 always either activates or deactivates the security depending on
setup and uses method configured in this section of the reader initialization file.
Available security modes are:
0. AFI only
1. EAS only
2. Both AFI and EAS
3. Use AFI deactivate EAS
In case security method is set to 0, 2 or 3 AFI activate and deactivate values must be set according to
used data model specification.
By default the security mode is set to AFI only and AFI values set to Danish values of 7 (Activate) and 194
(Deactivate).
[SECURITY]
; Security mode, 0 for afi only, 1 EAS only, 2 both, 3 use AFI deactivate EAS
SecurityMode = 0
; Activate afi value
AfiAct = 7
; Deactivate afi value
AfiDeact = 194

Section DANISH
WriteBytes
Write bytes value needs to be set according to barcode and library id length. In case the value is too
short an error message is shown during conversion.
By default the value is set 40 bytes which is enough to hold all the mandatory field and media type
extension field.
See chapter Danish for more detailed information.
[DANISH]
; WriteBytes

© P.V. Supa Oy Ltd

12
WriteBytes = 40

ReadBytes
In case LibConvert2 is set to read the tag information from detected tags and the tag information
appears incorrectly or there are error messages the read bytes value should be increased with increment
of 4, for example from 40 to 48, to a value that is sufficient to read all data from the tags.
By default the value is set to 40 bytes.
[DANISH]
; ReadBytes
; 16, item ID, usage type and set information returned, item ID max 13 chars
; 20, item ID max 16 chars
; 32, library ID and country code returned, library ID max 9 chars
; 36, library ID max 11 chars
; 40, media format returned
; 56-112, item IDs and/or library IDs longer than 16/11 chars
ReadBytes = 40

Section FINNISH
See chapter Section DANISH.

Section TV2
No modifications required.

Section ISO 28560-2

ReadBytes
In case LibConvert2 is set to read the tag information from detected tags and the tag information
appears incorrectly or there are read error messages the read bytes value should be increased with
increment of 4, for example from 48 to 52, to a value that is sufficient to read all data from the tags.
[ISO-28560-2]
; ReadBytes
ReadBytes = 48

MinItemIdLength and MaxItemIdLength

When rfid reader is configured to read more than one data model in section SECONDARYDATAMODEL
and main data model is set to ISO 28560-2 in section DATAMODEL it might be necessary to limit the
accepted item id lengths.
The reason for limiting the item id length when reading (decoding) is that depending of secondary data
model the data at the beginning of the tag can confirm to the bit packing rules of ISO 15962.
For example the most common Danish data model start bytes “110101” encode according to the rules as
item id 1.
By default MinItemIdLength is set to 5 and MaxItemIdLength is set to 25.

© P.V. Supa Oy Ltd

13
Section ITG
In section ITG the single item set size can be set to either 0 or 1.
By default single item set size is set to 1.
[ITG]
; Single item set size, 0 or 1. Default 1.
SingleItemSetSize = 1

Section DUTCH
Contact P.V. Supa support on how to correctly set Dutch data model parameters as this always requires
agreement with library on how the information, for example object identifier field, should be encoded
into rfid tags.

Section MISC
In some cases the existing rfid tags in library have been programmed with a reader that by default writes
data to rfid in opposite byte order. In this case the byte order needs to be reversed so that programmed
tags are compatible with old applications and rfid tags.
It is always recommended to consult P.V. Supa support before modifying this parameter to make sure
the existing rfid tags are really programmed with opposite byte order.
[MISC]
; Set default byte order, 0 no, 1 yes, default yes
; DefaultByteOrder = 0

Nedap exceptions
ComTimeout
Due to hardware limitations of Nedap readers the serial port read total timeout constant is by default
lowered to lowest possible working value of 200 milliseconds.
With LibConvert2 this can however in rare cases cause timeout errors because tag writing is more time
consuming process than reading of tags. To solve this issue the value should be slightly increased to for
example 300 milliseconds.
To change the read total timeout constant the third comma separated value in ComTimeout must be set.
[READER]
; Timeout params
ComTimeout = ",,300,,"

PollingInterval
With Nedap readers the detection of rfid tags is implemented differently and therefore the polling
interval value needs to be set according to worst case which means it must be set according to how large
sets LibConvert2 should be able to program. Roughly 50 milliseconds increase in polling interval means
detection of 2-3 more tags, but this is also affected by other things such interference, material (DVD, Blu-

© P.V. Supa Oy Ltd

14
ray), reader model etc.
Good default value for Nedap readers for polling interval is 100, which in good conditions allows
programming sets of size four to five rfid tags. In case only single items are programmed the value can be
lowered to 50 milliseconds for faster handling (detection) of rfid tags.
By default the polling interval value with Nedap readers is set to 100.
[READER]
; Polling interval (in milliseconds)
PollingInterval = 100

Setup
Setup can be accessed from the initial screen by clicking setup button. Default password for setup screen
is “admin”. The password can be changed by manually modifying settings file and changing the value of
<SetupPassword>admin</SetupPassword>.

General
General page contains settings that affect the user interface of LibConvert2.

Conversion Session
LibConvert2 can be set to return to start screen after an idle timeout period has elapsed. Idle timeout
period means a period of inactivity when no functions are chosen or rfid tags added or removed from
antenna.
By default idle timeout period is enabled with timeout period of five minutes.

ToolTips
Tooltips can be shown when mouse is hovering over
controls.
By default tooltips are enabled.

Figure 3: Tooltip

Full Screen
LibConvert2 can be set to start in full screen mode which is practical for dedicated conversion stations.
By default full screen is disabled.

© P.V. Supa Oy Ltd

15
Language
User interface language selection.
Installation package currently includes following languages: English, Finnish, German, Czech and Slovak.
New languages can be added or existing ones modified with P.V. Supa Language Editor. Language file
“[Link]” is located in common application data folder. When new language is added it is
automatically added to the language selection control at LibConvert2 start.
In case a new language is added or translation mistakes are fixed please send the language file to P.V.
Supa support so that it can be included in future installation packages.
By default user interface language is set to English.

RFID
Rfid page contains settings related to rfid reader connection.

Reader
RFID reader
This setting is used to select the rfid reader manufacturer type. Currently supported reader types are
Nedap, Scemtec, Feig and Tagsys. Selection of rfid reader affects which rfid reader initialization file is
used for rfid reader initialization.
Serial port
Serial port or virtual serial port in case USB readers is used.
This is the only setting that is not written into settings file, instead it is written into rfid reader
initialization file and it requires that in Windows 7 LibConvert2 was started as an administrator,
otherwise the setting won’t be saved.
Note! Feig USB readers are not affected by this setting, so it can be left into default value.

Initialization
Rfid reader can be initialized when LibConvert2 starts (Application startup) or when a conversion session
starts (share reader status and release).
Initialize reader
When application start-up mode is selected rfid reader is initialized only once when LibConvert2 starts,
which means reader is not available to any other application until LibConvert2 is closed. This mode
should be used in case there are no other applications, such as PV GoodStuff, that require rfid reader.
The advantage of this mode is that session start up time is shorter.
In case session start-up mode is selected rfid reader is initialized every time a conversion session starts
and uninitialized when conversion session ends. This leaves the reader free to use for other applications

© P.V. Supa Oy Ltd

16
such as PV GoodStuff when LibConvert2 is not in session.
Session start-up mode also enables sharing of reader status with PV GoodStuff. When conversion session
is started a signal is given to PV GoodStuff to release rfid reader and similarly when conversion session
ends PV GoodStuff is signaled that rfid reader is now free to use.
Disadvantage of application start-up mode is that session start-up times are longer compared to
application start-up mode.
When session startup release mode is selected LibConvert2 releases the rfid reader when it is not the
active application. If there is an active conversion session the session is ended and rfid reader is released
when LibConvert2 becomes inactive. This mode can be used to share the rfid reader with other
applications that do not support sharing reader.
By default application start-up mode is selected.
Check that the serial port is free (session startup)
By default when either of the session startup modes is enabled LibConvert2 when session is started
checks when the serial port is free to open. This sometimes freezes LibConvert2 after session start when
using a combination of Windows 7 and rfid reader that utilizes Microsoft [Link] driver.
By disabling the check instead of checking if serial port is free a predefined timer is used to wait before
LibConvert2 tries to open the serial port.

Tags
Read data from tags
LibConvert2 can be set to read the data from the tags, which makes it easy to distinguish between
already programmed and empty tags, and also to verify that tags were written correctly.
When reading of tag information is enabled tags view is visible on session screen. Following information,
if available by configured data model, is shown for each detected tag.
 Item id
 Media type
 Usage type
 Set information
Show data model name
When show data model name is enabled the data model name of the detected tags is shown in the tags
view.
Note when enabled data model name column will replace optional media type column.
By default show data model name is enabled.

© P.V. Supa Oy Ltd

17
Read block security status
When read block security is enabled the security status of the rfid tag blocks is read to determine if the
tag is locked or not. In case any locked tags are detected programming is not allowed. Locked tags are
marked with lock icon in the tags view.
When block security read is enabled and there is an error while reading the security status tag
programming is not allowed.
By default read block security status is disabled.

Tag Data
Tag data page contains settings related to data that is encoded (programmed) into rfid tags.

Data Model
Available fields and values vary according to selected data model.
See chapter supported data models for detailed information.

Functions
Select type of usage during session
This selection is enabled if data model supports programming of usage type.
Instead of setting type of usage permanently to for example “Item for circulation” the most common
type of usages can also be selected during conversion session.
In case select type of usage during session is enabled the value that is set in setup screen is ignored.
By default selection of usage type during session is disabled.
Deactivate circulation items
By default LibCovenrt2 always activates the alarms on programmed rfid tags, in case the security should
instead be deactivated on all programmed rfid tags deactivate circulation items must be enabled.
Write media type on tag
This selection is enabled if data model supports programming of media type.
In case write media type on tag is enabled media type selection with data model specific media types is
added to session screen.
By default writing of media type is enabled if a data model supports programming of media type.
Convert automatically to main data model
LibConvert2 can be set to convert tags detected with secondary data models into the main data model.
See chapter Rfid reader initialization file for instructions how to configure the data models.
Currently supported conversions

© P.V. Supa Oy Ltd

18
  Danish to ISO 28560-2
 TV2 to ISO 28560-2
By default convert automatically to main data model is disabled.
Use standard mode with automatic data model conversion
This setting is enabled when Convert automatically to main data model is enabled.
Converting from secondary data models to main data model has to operating modes, Standard mode
and Background mode. When this setting is enabled standard mode is used otherwise the background
mode is used.
By default convert to main one by one is enabled.
Write also alternate item id on tag
When enabled an alternate item id number can be
programmed into Danish data model extension block.
In the user interface there will be two id number fields
available.

Figure 4: Alternate item identification number

Multipart Items
Multipart items page contains settings that affect programming of sets.

Tag sharing
LibConvert2 can be configured to program a separate tag for each item of a set or to program set with
only one tag which specifies the amount of items that belong to a set.
By default tag sharing is set to each part has own tag.

Connections
Connections page allows the configuration of additional functionalities that require connection to server,
database or file.

Local History Database

Three options are available how storing of conversion history should be handled.

© P.V. Supa Oy Ltd

19
  None, do not store conversion history
 Access, store history into Microsoft Access Database
 SqlExpress, store history into Microsoft SQL Express database
See chapter Local database for more information.

History Database Server

Besides storing conversion history to local database LibConvert2 can be configured to store data to a
central database location.
To enable centralized storing of conversion history a server name must entered, MSMQ (Microsoft
Message Queuing) enabled and on the database server a separate P.V. Supa windows service called Item
Listener has to be installed and running. MSMQ allows conversion data to be stored and uploaded into
database without requiring a constant connection to the server.
Situations where Item Listener server is located on Windows 2008 server, Windows 7 or on a later
version of Windows operating system and there are LibConvert2 installations running on windows XP
message queue security policies must be set to accept anonymous messages on the server side.
By default centralized storing of conversion history is disabled.

ItemId service
Item id service is provided by MasterController to centrally generate unique item ids. For setting up a
centralized item id service see MasterController manual.
When retrieving of item ids from server is enabled new button get item id is available on the session
screen. Pressing this button retrieves new item id from the server and writes it to the rfid tag.
Enabling item id service requires restart of LibConvert2.
By default retrieving of item ids from server is disabled.

Weeding
Weeding can be used to filter out material that is not to be converted. Weeding file must be a text file
with one item number per row.
A warning popup, beside standard warning message, can be shown. Two types of popups are available,
information popup and question popup with option to write the tag although it was on the weeding list.
By default weeding is disabled and popup is not shown, set to “None”.
See chapter Weeding for more information.

© P.V. Supa Oy Ltd

20
Barcode
Barcode page contains settings that affect the handling of read barcode.

Filter
Received barcodes can be filtered to avoid accidentally converting wrong information into rfid tags, such
as ISBN codes.
Minimum length
Minimum length of the barcode can be set between 0 and 20 characters. In case barcode length does
not match or exceed the minimum length value the barcode is not accepted.
By default value is set to 0, which means all read barcodes are accepted.
Starts with
Starts with allows filtering of barcodes to ones that starts with specified character or characters. Multiple
values can be entered with comma as separator.
Note that all characters, including spaces, between commas are considered as starts with values.
By default starts with field is empty.

Misc
Miscellaneous page contains settings for various functions.

Convert to file
Convert to file allows writing to file the encoded data. The format and content of the written data can be
changed in xml file [Link] that is automatically generated into Common application data
folder when Write encoded data to file is enabled. ANNEX E: Tag file format file contains an example of
the default configuration file.
Write encoded data to file
Enable or disable writing to file.
By default writing to file is disabled.
Tag file name
Tag file name is the name of the output file.
By default file name is empty.
Tag file path
Tag file path is the directory where the output file should be created.
By default file path is empty.

© P.V. Supa Oy Ltd

21
Tag write mode
Tag write mode specifies whether to write only to file or should the tag also be programmed.
By default tag write mode is set to file only.
Tag file mode
Tag file mode specifies whether the file should always be created as new (overwritten) or if the latest tag
information should be appended into the file.
By default tag file mode is set to overwrite.

User interface
LibConvert2 user interface consist of two pages, start-up page and session page.
At first start if rfid reader has not been previously configured rfid initialization failure popup might be
shown, see figure five for example.

Start-up page
Start-up page contains access to setup, conversion session and manual.

© P.V. Supa Oy Ltd

22
 Figure 5: Start-up screen

Start Session
Start session button when enabled starts new conversion session.
Start session button is disabled when rfid Initialization mode is set to application start-up mode and rfid
reader connection fails.
When rfid Initialization mode is set to staff mode Start Session button is always enabled and a popup is
shown in case connection to rfid reader fails.

© P.V. Supa Oy Ltd

23
 Figure 6: Rfid initialization error

Setup
Setup button opens first the password dialog and when correct password is entered setup dialog is
opened.

Exit
Exit button closes LibConvert2.

Help
Help button opens this manual.

© P.V. Supa Oy Ltd

24
Session page
Session screen is divided into two sides. On the left side are the controls to provide information that is to
be encoded into programmed rfid tags. On the right side are instruction texts and result lists. Content of
the screen is dependent on selected data model and setup.

Figure 7: Session screen

Item ID and Tags read fields

Item id field is active and accepts input from keyboard or from barcode scanner when parts count
selection and tags read values match.
Tags read field shows the current amount of tags on the antenna that rfid reader is able to detect.
After tags are programmed item id field stays disabled and shows the recently programmed item
number until all programmed tags are removed from antenna.

© P.V. Supa Oy Ltd

25
When there are no tags on antenna or
tags read count does not match parts
count selection item id field is disabled.

Figure 8: Item id field disabled

When tags read count and parts count

selection match item id field is active
and accepts input from barcode scanner
or keyboard.

Figure 9: Item id field enabled

After tag or tags have been programmed

item id field stays disabled and shows
the last programmed item number until
all programmed tags are removed from
antenna.
In case Item ID field and tags count stay
disabled even after programmed rfid Figure 10: Item id field after tags are programmed
tags are removed from antenna return
the items to antenna wait a second and
remove the items again. If this happens
often PollingInterval on the rfid reader
initialization file should be lowered.

Get item id
Get item id button is visible when ItemId service connection is enabled. When Get item id button is
pressed next item id is fetched from item id service and programmed into tag or tags.

© P.V. Supa Oy Ltd

26
When there are no tags on antenna or tags read
count does not match parts count selection get
item id button is disabled.

Figure 11: Get item id button disabled

When tags read count and parts count selection

match get item id button is enabled.

Figure 12: Get item id button enabled

Parts count selection

In case data model supports programming of set information parts count selection is visible. By default
parts count is set to 1. In case a set of items is to be programmed parts count selection must be changed
to match the value of tags to be programmed.

Default parts count value is one.

Figure 13: Default parts count

© P.V. Supa Oy Ltd

27
When a set is to be programmed parts count
value must be set to match the tags read count
in order to enable item id field and
programming of tags.

Figure 14: Parts count set to four

Usage type selection

Usage type selection is visible if data model supports writing of usage type and selection of usage type
during session is enabled from setup.
Example screens are taken when data model is set to Danish.

Tag or tags are to be programmed as standard

items for circulation.

Figure 15: Usage type Item for circulation

Tag is to be programmed as patron card.

Figure 16: Usage type Patron card

See chapter Select type of usage during session on how to enable or disable usage type selection during
conversion session.

Media type selection

Media type selection is visible if data model supports writing of media type and write media type on tag
is enabled from setup.

© P.V. Supa Oy Ltd

28
Tags are to be programmed with media
type Book.

Figure 17: Media type book selected

See chapter Write media type on tag on how to enable or disable media type selection.

Instruction text
Instruction text area is used to present information to the user of what to do next and present error
messages in case something goes wrong.
Common instructions

Please locate item on the reader instruction is

shown when parts count selection is set to 1 and
no rfid tag is detected on antenna.
User is expected to place item with single rfid
tag on antenna. Figure 18: Instruction - Please locate item on the reader

Please locate items on the reader instruction is

shown when parts count selection is set to
higher value than one, a set is to be
programmed, and detected rfid tag count is
smaller than parts count selection.
Figure 19: Instruction - Please locate items on the reader
User is expected to place all items with rfid tags
that are to be programmed with same item
number on the antenna.

Please enter item ID instruction is shown when

tag read count and parts count selection match.
User is expected to provide an item number
from keyboard, barcode scanner or item id
service that is to be programmed into rfid tag or Figure 20: Instruction - Please enter item ID
tags.

© P.V. Supa Oy Ltd

29
Too many items instruction is shown when too
many rfid tags are detected compared to parts
count selection.
User is expected to remove extra rfid tags from
antenna or to set parts count selection to match Figure 21: Instruction - Too many items
tags read count in case a set is to be
programmed.

Item or items converted please remove them

instructions are shown after rfid tag or tags are
successfully programmed.
User is expected to remove the programmed rfid
tags from antenna. Figure 22: Instruction - Item converted, please remove it

Figure 23: Instruction - 2 items converted

Failed to check lock status message is shown

when read block security status is enabled and
an error occurs while reading the status.
User is expected to remove the rfid tag from the
antenna and then put it back again until the Figure 24: Message - Failed to check lock status
security status is read properly and
programming is enabled or locked tags message
is shown.

Locked item message is shown when read block

security status is enabled and a locked rfid tag is
detected. When locked tags are detected
programming is disabled.
Figure 25: Message - Locked item
User is expected to remove the locked rfid tag
from the antenna as it cannot be programmed.

© P.V. Supa Oy Ltd

30
Common errors

Too long item ID error message is shown when

entered item number is too long according to
data model restrictions or rfid reader
initialization file settings.
Usually this error is shown with Danish data
model when barcode longer than 16 characters
is tried to be programmed. In this case the rfid
reader initialization file needs to be modified to
Figure 26: Rfid error - Too long item ID
enable programming of item number into
extension field area.

Too short country code or too short library id

errors are shown when data model information
is not correctly setup.
Data model information must be correctly set
according to data model specification at setup
page Tag Data.

Figure 27: Rfid error - Too short country code

Figure 28: Rfid error - Too short library ID

No tag found error message is shown when rfid

reader could not find rfid tag for writing.
User should make sure all tags that are to be
programmed are placed on top of the antenna
and then retry programming.

© P.V. Supa Oy Ltd

31
 Figure 29: Rfid error - No tag found

Collision, CRC error, write failure and similar

RFID error messages are shown when rfid reader
could not properly program rfid tag.
User should make sure all tags that are to be
programmed are placed on the antenna and
then retry programming.
Moving or lifting items, especially discs, on the
antenna can solve these errors. Figure 30: Rfid error - Weak collision
In case the errors appear constantly it should be
checked that there are no metal objects,
keyboard, mouse, barcode reader etc. on top of
the antenna or in close vicinity of the antenna.
In case none of the above helps P.V. Supa
support is to be contacted for help.

Communication write error indicates that the

connection to the reader has faulted.
User should check that reader is properly
connected and powered on and in case the
reader is connected via USB the reader is listed Figure 31: Rfid error - Communication write error
without errors at windows device manager.
Restarting the rfid reader, power off then on,
and LibConvert2 is recommended.
See chapter ANNEX C: Windows Device
Manager.

Conversion history
Conversion history shows list of the last programmed tags.

© P.V. Supa Oy Ltd

32
 Figure 32: Conversion history

Tags
Tags list shows the content of tags that are currently on the reading area. Tags list visibility can be
changed from setup.

© P.V. Supa Oy Ltd

33
 Figure 33: Tags view with column Media Type

Figure 34: Tags view with column Data Model

Figure 35: Tags view with tag locked column

© P.V. Supa Oy Ltd

34
Buttons

By default session screen contains only stop

session button.
When stop session is pressed LibConvert2
returns to start-up page. Figure 36: Stop session button

When there is an error during programming

retry and cancel buttons are available.
Retry button tries to program the failed rfid tags
again. Figure 37: Error situation buttons

Cancel button cancels the current tag

programming and LibConvert2 returns to
conversion session page.

Weeding
Weeding can be used to filter out material during conversion that is not to be programmed.
There are three types of warning configurations that can be set at setup page Connections.

Weeding list must be a text file with one item

number per row.

Figure 38: Weeding list

© P.V. Supa Oy Ltd

35
Weeding can be enabled and configured from
setup page Connections.

Figure 39: Weeding setup

Warning only
Only a warning is shown when weeding popup type is set to none.

When an item number that is found from

weeding list is tried to be programmed the
operation is cancelled and a conversion
cancelled message is shown at the instruction
text area until rfid tag or tags are removed from
the antenna.
Figure 40: Weeding - Warning

Warning with popup message

Warning with popup is shown when weeding popup type is set to information.

When an item number that is found from weeding list

is tried to be programmed the operation is cancelled
and a popup message is shown.
After the popup is closed a warning message is shown,
like in figure 30, at the instruction text area until rfid
tag or tags are removed from the antenna.

Figure 41: Weeding - Information popup

Warning with question popup

Warning with question is shown when weeding popup type is set to question.

© P.V. Supa Oy Ltd

36
When an item number that is found from weeding list is tried to be programmed a question popup
message is shown.

If the default reply No is chosen the operation is

cancelled and a warning message is shown, like in figure
30, at the instruction text area until rfid tag or tags are
removed from the antenna.

Figure 42: Weeding - Popup reply no

In case reply yes is chosen the rfid tag or tags are

programmed normally.
Item or items converted message is shown at the
instruction text area, like in figures 21 and 22, until rfid
tag or tags are removed from the antenna and
programmed item number is added to conversion
history list.

Figure 43: Weeding - Popup reply yes

Shortcut Keys
Most of the functions can also be chosen from keyboard with shortcut keys. The keys are predefined and
cannot be changed.
Following chapters describe shortcut keys that are available on different screens.

Start-up screen
 F1 - Open manual
 F2 - Start conversion session
 Esc - Exit LibConvert2

© P.V. Supa Oy Ltd

37
Session screen
Common shortcut keys
 F1 - Open manual
 F3 – Stop conversion session
Parts count shortcut keys
In case parts count selection is visible following shortcut keys can be used for parts count selection.
 Ctrl + 1 – Select parts count 1
 Ctrl + 2 – Select parts count 2
 Ctrl + 3 – Select parts count 3
 Ctrl + 4 – Select parts count 4
 Ctrl + 5 – Select parts count 5
 Ctrl + 6 – Select parts count 6
 Ctrl + 7 – Select parts count 7
 Ctrl + 8 – Select parts count 8
 Ctrl + 9 – Select parts count 9
 Ctrl + Shift + 0, Select parts count 10
 Ctrl + Shift + 1, Select parts count 11
 Ctrl + Shift + 2, Select parts count 12
 Ctrl + Shift + 3, Select parts count 13
 Ctrl + Shift + 4, Select parts count 14
 Ctrl + Shift + 5, Select parts count 15
 Ctrl + Shift + 6, Select parts count 16
Usage type
In case usage type selection is visible following shortcut keys can be used for usage type selection.
 Ctrl + I – Item for circulation
 Ctrl + N – Item not for circulation
 Ctrl + P – Patron card
Media type shortcut keys
In case media type selection is visible following shortcut keys can be used for media type selection.
Some of the media types and therefore shortcut keys might not be available according to selected data

© P.V. Supa Oy Ltd

38
model.
 Ctrl + B – Book
 Ctrl + D – CD/DVD
 Ctrl + M – Magnetic Tape
 Ctrl + O – Other
 Ctrl + H – Careful handling
 Ctrl + S – Small item
 Ctrl + U - Undefined

Data model conversion

When Convert automatically to main data model from setup is enabled tags detected with secondary
data models are automatically converted to the main data model.
Depending of the source data models, destination data model and conversion mode some information
might be lost during the conversion.
When converting to data model ISO 28560-2 the MinItemIdLength and MaxItemIdLength parameters in
the rfid initialization file might require modification, although in most of the cases the default values
should be sufficient.
Rfid tags converted from secondary data models are marked with a message, such as “Danish –> ISO
28560-2” in the Conversion history.
Currently data model conversion supports following scenarios
 Danish to ISO 28560-2
 TV2 to ISO 28560-2
 ISO 28560-2 to Danish

Standard mode
Converting tags detected with secondary data models in mode standard is quite similar to converting
tags from barcode. When an rfid tag with secondary data model is detected the conversion starts
automatically and depending of the source data model the user interface selections such as set size and
usage type are done automatically. During the conversion process the standard instruction texts are
shown and for example sets are not converted until all rfid tags belonging to the set are on the reading
area.
When standard mode is used setting select type of usage during session might be ignored depending of
source and target data models.

© P.V. Supa Oy Ltd

39
Mode standard is the default and recommended mode.

Danish to ISO 28560-2

Converting from Danish to ISO 28560-2 in the standard mode does not require any user action besides
placing and removing the rfid tags on the rfid antenna.
Set size and usage type selections are done automatically and for other required fields such as country
code and library id the settings from setup page Tag Data are used like when converting rfid tags from
barcodes.
Here is the list of fields that are encoded when converting from Danish to ISO 28560-2 data model.
Item id Supported. Read from the source rfid tag.
Set size Supported. Automatically set according to source rfid tag.
Set index Supported. Automatically set according to source rfid tag.
Usage type Supported. Automatically set according to source rfid tag.
Library id Supported. Value from settings is used.
Library id type Supported. Value from settings is used.
Media type Not supported
When converting from Danish to ISO 28560-2 media type information is lost, because LibConvert2
does not currently support any of the ISO 28560-2 media type encodings.

ISO 28560-2 to Danish

When converting from data model ISO 28560-2 to Danish in standard mode the required user actions
depend on the data that is encoded into the source rfid tags and on the Danish data model settings that
are set in setup page Tag Data.
Set size selection is done automatically.
For encoding of mandatory fields country code, library id and library id type the settings from setup page
Tag Data are used like when converting rfid tags from barcodes. Possible values, such as ISIL, from the
source ISO 28560-2 rfid tags are not used.
In case usage type, mandatory field in Danish data model, is encoded into the source ISO 28560-2 rfid
tags the values are used, otherwise usage type is encoded according to settings made in setup page Tag
Data.
Media type field is optional in Danish data model and it is encoded according to settings made in setup
page Tag Data.
Here is the list of fields with source that are encoded when converting from ISO 28560-2 to Danish data
model.

© P.V. Supa Oy Ltd

40
Item id Read from the source rfid tag.
Set size Automatically set according to source rfid tag.
Set index Automatically set according to source rfid tag.
Usage type Automatically set according to source rfid tag if present, otherwise set according to
settings.
Country code Value from settings is used.
Library id Value from settings is used.
Library id type Value from settings is used.
Media type Encoded according to user selection if encoding of media type is enabled.

TV2 to ISO 28560-2

Information about conversion from TV2 to ISO 28560-2 will be included in next version of the manual.

Background mode
In background mode rfid tags detected with secondary data models are automatically encoded into the
main data model in the background. There are no checks to see if sets are complete and no instructions
to remove the converted tags so multiple rfid tags (stack) can be converted at once.
Which fields are encoded and from where the values are retrieved in different scenarios is explained in
the following chapters.

Danish to ISO 28560-2

Here is the list of fields that are encoded when converting from Danish to ISO 28560-2 data model in
background mode.
Item id Supported. Taken from the source rfid tag.
Set size Supported. Taken from the source rfid tag.
Set index Supported. Taken from the source rfid tag.
Usage type Supported. Taken from the source rfid tag.
Library id Supported. Taken from the source rfid tag.
Library id type Supported. Taken from the source rfid tag.
Media type Not supported
When converting from Danish to ISO 28560-2 media type information is lost, because LibConvert2

© P.V. Supa Oy Ltd

41
does not currently support any of the ISO 28560-2 media type encodings.

ISO 28560-2 to Danish

Here is the list of fields that are encoded when converting from ISO 28560-2 to Danish data model in
background mode.
Item id Taken from the source rfid tag.
Set size Taken from the source rfid tag.
Set index Taken from the source rfid tag.
Usage type Automatically set according to source rfid tag if present, otherwise set according to
settings.
Country code Value from settings is used.
Library id Value from settings is used.
Library id type Value from settings is used.
Media type Encoded according to user selection if encoding of media type is enabled.
When converting from ISO 28560-2 to Danish data model only item id, set information and usage type,
if present, are directly copied into encoded Danish data model rfid tags. All other values are encoded
according to settings and/or by user selections.

TV2 to ISO 28560-2

Information about conversion from TV2 to ISO 28560-2 will be included in next version of the manual.

Supported data models

This chapter contains all the data models that are currently supported for encoding (programming) of
rfid tags by LibConvert2, beside data models mentioned in this chapter P.V. Supa applications support
reading of various other data models.
For each data model all supported mandatory and optional fields are listed that can be or are encoded
along with an item number.
Mandatory fields are always encoded along with item id, whereas encoding of optional fields depends
on setup, user actions and implementation.

© P.V. Supa Oy Ltd

42
Danish

Figure 44: Danish data model setup page

Detailed explanation of Danish data model standard can be found in Danish data model standard.

Mandatory fields
Primary Item ID
Primary item identification number is read from barcode, typed from keyboard or provided by item id
service. By default the item id can be 16 characters long. In case longer barcodes are to be converted
reader initialization file must be modified to write more bytes to tag so that primary item identifier fits
to the alternate item id field.
Country Code
Two character country code, for example “FI” or “DK”. Country code is set at the setup page and same
country code is encoded into all programmed rfid tags.
Owner library id
Owner library identification field is used to configure the library identification information. Maximum

© P.V. Supa Oy Ltd

43
length of the field is affected by amount of memory on tag, rfid reader settings and library id type.
When library id type is set to “International standardized” field can be 11 characters long, otherwise field
can be 10 characters long. In case short memory tags are used, 32 bytes of available memory, maximum
field length is 9 characters.
In case the library identification information exceeds the maximum length it is written into the extended
owner library field. This requires that rfid reader initialization file is modified to write more bytes to tag.
Owner library id is set at the setup page and same owner library id is encoded into all programmed rfid
tags.
Library id type
Type of library identification field can be set to International (ISIL), National or not standardized. Library
id type that is selected at the setup page is encoded into all programmed rfid tags.
Type of usage
Type of usage can be set to acquisition, item for circulation, item not for circulation, discarded item or
patron card. Type of usage that is selected at the setup page is encoded into all programmed rfid tags.
To select most common type of usages during conversion session see chapter functions. In case type of
usage is selected during conversion session the value at setup page is ignored.
Set information
Set information is always written with two values set index and set size according to parts count
selection during conversion session.

Optional fields
LibConvert2 supports writing of following optional (extension) fields.
 Media format
 Alternate item id, in case item id is longer than 16 characters
 Extended owner library, in case library identification does not fit into the mandatory part
Media format
In case media format is chosen to be written at the setup page one of the following media formats can
be selected during conversion session: book, CD/DVD, Magnetic tape, Other, careful handling, small item
or undefined.

© P.V. Supa Oy Ltd

44
Dutch
LibConvert2 supports writing of Dutch data model according to standard version number 4 with one
exception regarding library identifier.
Programming rfid tags according to Dutch data model always requires customer specific setup and P.V.
Supa support must be contacted to properly setup LibConvert2 according to library requirements.

Figure 45: Dutch data model setup page

Mandatory fields
Data model identifier
Data model identifier is always set to 01.

© P.V. Supa Oy Ltd

45
Type identification
Type identification field is programmed according to type identification selection, either in setup page or
during conversion session. Two values are available object and library user.
Object identifier
Object identifier is a unique number and the programming needs to be agreed with the customer. Object
identifier field is always 14 digits long. LibConvert2 uses a script to generate object identifier field.
Item identifier
Item identifier in Dutch data model stands for set information and it is programmed according to parts
count selection during conversion session.
Library identifier
Library identifier field is programmed according to Dutch data model specification. Library identifier is
combined from country code, library identifier and library id type fields that are set at the setup page.
Same library identifier is encoded into all programmed rfid tags.
Version 4 of Dutch data model standard contains only two library id types, but LibConvert2 library id
selection includes additional library id types that are presented in version 5 of the standard.

Optional fields
Barcode
The existing barcode is programmed into this field. Maximum length for the barcode is 14 digits.
Although the field is optional currently LibConvert2 always programs barcode field.

© P.V. Supa Oy Ltd

46
French
LibConvert2 supports encoding of rfid tags according to French data model version 1.
Detailed explanation of French data model standard can be found in French data model documentation
version 1.

Figure 46: French data model setup page

LibConvert2 always encodes fields mentioned below into programmed rfid tags.

Encoded fields
Version name
Version name is always set to FR01
Usage
Usage is encoded according to type of usage selection, either at the setup page or during conversion

© P.V. Supa Oy Ltd

47
session. Two usage types can be chosen, product tag or patron card.

Library code
Maximum length is 10 digits and the content is set at setup page.

Item number
Item number (set index) is encoded according to parts count selection.
Total items
Total items (set size) is encoded according to parts count selection.
Document number
Document number is read from barcode or provided by item id service. Document number can be 16
ASCII characters long.

© P.V. Supa Oy Ltd

48
ISO 28560-2
LibConvert2 supports bit compacted encoding of ISO 28560 data elements mentioned in this chapter.
Data elements are encoded (bit compacted) according to following standards.
 ISO 28560-1, Data elements and general guidelines for implementation
 ISO 28560-2, Encoding of RFID data elements based on rules from ISI/IEC 15962
 ISO 15962, Information technology - Radio frequency identification (RFD) for item management
– Data protocol: data encoding rules and logical memory functions

Figure 47: ISO 28560-2 data model setup page

© P.V. Supa Oy Ltd

49
Mandatory element
Primary item identifier
The only mandatory data element in ISO-28560-2 data model is primary item identifier. Primary item
identifier is always the first element that is encoded into programmed tags.
Primary item identifier number is read from barcode, typed from keyboard or provided by item id
service.

Optional elements
Elements mentioned in this chapter are optional by ISO 28560-2 standard, but always encoded by
LibConvert2, beside type of usage, into programmed rfid tags.
NISO recommends encoding all of these elements.
Content parameter
Content parameter contains information about which optional elements are encoded into the rfid tag. As
recommended by ISO 28560-2 standard this element is encoded as the second element on the tag.
Content parameter is always encoded into rfid tags by LibConvert2.
Owner institution
Owner institution is encoded according to library id type selection; two types are available ISIL and
alternative. The content for owner institution is combined from setup field’s country code and owner
library id. Same owner institution is used for all encoded rfid tags.
Owner institution is always encoded into rfid tags by LibConvert2.
Set information
Set information is encoded according to parts count selection.
Set information is always encoded into rfid tags by LibConvert2.
Type of usage
Type of usage can be set to acquisition, item for circulation, item not for circulation, discarded item or
patron card.
Type of usage that is selected at the setup page is encoded into all programmed rfid tags.
To select most common type of usages during conversion session see chapter functions. In case type of
usage is selected during conversion session the value at setup page is ignored.
Type of usage is encoded into rfid tags in case setting write usage type on tag is enabled.

© P.V. Supa Oy Ltd

50
ITG

Figure 48: ITG data model setup page

Encoded fields
Item ID
Item id field is read from barcode, typed from keyboard or provided by item id service during conversion
session. Maximum length for item id field is 16 characters.
Country
Two character country code that is set at the setup page and same country code is encoded into all
programmed rfid tags.
Library code
Library code field’s maximum length is 9 characters and it is set at the setup page. Same library code is
encoded into all programmed rfid tags.

© P.V. Supa Oy Ltd

51
Object Qualifier
Object qualifier is set at the setup page. Five object qualifier types can be chosen: undefined, normal
circulation, non-circulating, locking case or withdrawn from circulation. Same object qualifier is encoded
into all programmed rfid tags.
Object type
Object type is encoded according to user selection during conversion session. Following object types are
available: undefined, book, audio tape, video tape, CD audio, DVD video, CD computer, DVD computer,
special and other.

QUEENS

Figure 49: Queens data model setup page

Item id
Data model contains only item id with a hard coded prefix table no other information is encoded into
tags.

© P.V. Supa Oy Ltd

52
TV2
Rfid tags encoded with TV2 data model always contain mandatory and optional fields mentioned in this
chapter.

Figure 50: TV2 data model setup page

Mandatory fields
Barcode
Barcode field is read from barcode, typed from keyboard or provided by item id service during
conversion session. Maximum length for barcode field is 16 characters.
End of data
Last bytes of the encoded rfid tags are always set to 7C 00 in hexadecimal.

Optional fields
Following fields are optional by TV2 data model documentation, but LibConvert2 always encodes these
fields.

© P.V. Supa Oy Ltd

53
Country code
Two character country code that is set at the setup page and same country code is encoded into all
programmed rfid tags.

Library number
Library number field’s maximum length is 16 characters and it is set at the setup page. Same library
number is encoded into all programmed rfid tags.
Part number
Part number is encoded according to parts count selection.
Number of parts
Number of parts is encoded according to parts count selection.

Finnish
Finnish data model is almost the same as Danish, only exceptions being that mandatory data blocks are
locked and therefore maximum barcode length is limited to 16 characters.

Log
LibConvert2 writes log to Windows event log. The logs can be read with Windows event viewer or with
Supa Event Viewer. Log name is PV LibConvert2 and it can be found under application logs.
Different ways to access Windows event viewer
 Open Run and type [Link]
 Right mouse click My Computer->Manage->Event Viewer
 Open Control Panel->Administrative Tools->Event Viewer

© P.V. Supa Oy Ltd

54
ANNEX A: Setup screens

General

RFID

© P.V. Supa Oy Ltd

55
Tag Data

Multipart Items

© P.V. Supa Oy Ltd

56
Connections

Barcode

© P.V. Supa Oy Ltd

57
Misc

© P.V. Supa Oy Ltd

58
ANNEX B: Programming tags

Example 1: Single item from barcode

This is an example where a book with barcode is converted. The barcode from the book is read and
programmed into a single rfid tag. Usage type is left to the default one which is item for circulation.

Example 1: Step 1 – Start session

Session is started by pressing Start Session button or by pressing shortcut key F2.

© P.V. Supa Oy Ltd

59
Example 1: Step 2 – Session started
Conversion session is started and instruction message to place item on the reader is shown.

© P.V. Supa Oy Ltd

60
Example 1: Step 3 – Item on antenna
Item with single rfid tag is placed on antenna. Instruction message is changed to please enter item id.
Tags view shows that the detected tag is empty.
Barcode is read with barcode reader and programming of tag starts immediately if barcode reader is
configured to add carriage return after the barcode, otherwise Enter key needs to be pressed.

© P.V. Supa Oy Ltd

61
Example 1: Step 4 – Converting
Item is being programmed with item number that was read from barcode and please wait message is
shown.
In normal conditions when programming single items this step is usually almost invisible since
programming a single rfid tag takes only about a couple of hundred milliseconds.

© P.V. Supa Oy Ltd

62
Example 1: Step 5 – Item converted
After item is successfully converted instruction message to remove the programmed item is shown and
until the item is removed left side controls are disabled to avoid accidentally programming same tag
again.

© P.V. Supa Oy Ltd

63
Example 2: Set from barcode
In this example a set of three CD’s is converted from barcode. All three CD’s have an rfid tag and are
programmed with same item number.

Example 2: Steps 1 and 2

See chapter Example 1: Single item from barcode.

Example 2: Step 3 – Items on antenna

The set of CD’s is placed on antenna. Instruction message changes to too many items and media type
selection is not yet made.
Usage type is left into the default value of item for circulation and on the tags view it can be seen that all
three detected tags are empty.

© P.V. Supa Oy Ltd

64
Example 2: Step 4 – Enter item id
Parts count selection is set to match the tags read count and media type selection is set to CD/DVD.
Item ID field is enabled and instruction message changed to please enter item id.
Barcode is read with barcode reader and programming of tags starts immediately if barcode reader is
configured to add carriage return after the barcode, otherwise Enter key needs to be pressed.

© P.V. Supa Oy Ltd

65
Example 2: Step 5 – Converting
The three tags are being programmed with the item number from barcode and please wait message is
shown.

© P.V. Supa Oy Ltd

66
Example 2: Step 6 – Items converted
After items, the three rfid tags, are successfully converted instruction message to remove the
programmed items is shown and until the items are removed left side controls are disabled to avoid
accidentally programming same tags again.

© P.V. Supa Oy Ltd

67
Example 3: Single item with new item number
In this example a book with one rfid tag is programmed with new item number instead of converting the
item number from an existing barcode.
LibConvert2 has been configured to retrieve the item numbers from ItemId service and therefore get
item id button is available on the session screen.

Example 3: Steps 1 and 2

See chapter Example 1: Single item from barcode.

Example 3: Steps 3 – Enter item id

Instead of reading item number from an existing barcode button get item id is pressed and new item
number is retrieved from MasterController server.

© P.V. Supa Oy Ltd

68
Example 3: Step 4 – Converting
New item number is retrieved from server and programming starts immediately.

© P.V. Supa Oy Ltd

69
Example 3: Step 5 – Item converted
After item with the retrieved item number is successfully converted instruction message to remove the
programmed item is shown and until the item is removed left side controls are disabled to avoid
accidentally programming same tag again.

© P.V. Supa Oy Ltd

70
Example 4: Single item from barcode, error during conversion
This example is same as example one with one exception that at first try there is an rfid error during the
programming of rfid tag.

Example 4: Steps 1 to 4
See chapter Example 1: Single item from barcode.

Example 4: Step 5 – Error

During the tag programming there is an error where rfid reader can’t find the rfid tag that is to be
programmed. The tag is positioned better on the antenna and retry button is pressed.
In case the tag programming keeps failing cancel button can be pressed and programming of another
item tried. The programming could fail for example due to a faulty rfid tag.

© P.V. Supa Oy Ltd

71
Example 4: Step 6 – Item converted
After retry tag programming is successful.
See chapter Example 1: Step 5 – Item converted.

ANNEX C: Windows Device Manager

ANNEX D: Reader initialization file example

[READER]
; Port
ComPort = COM1
; Com params (baud rate, parity, databits, stopbits)
ComParams = "115200,,,"
; Timeout params
ComTimeout = ",,,,"
; Power 1, 2, 3, or 4
; SIR-2710: 0.25W, 0.50W, 0.75W, 1.5W respectively
Power = 4
; ResetPort, 0 = no, 1 = yes, default 0
; With virtual serial port, reader connected to USB, always use 0
ResetPort = 0
; Polling interval (in milliseconds)
PollingInterval = 500
; Reader identification, used to identify reader when more than one reader is used
ReaderID = 1
; Use advanced read command, 0 = no, 1 = yes, default 0
UseAdvancedRead = 1
; Use advanced write commands for AFI and DSFID, default 0
UseAdvancedCommands = 1

© P.V. Supa Oy Ltd

72
; Begin intialization with ESC/RxFlush, 0 = no, 1 = yes, default 1
SendEsc = 1

[DATAMODEL]
; Main Data model. First to analyze when tag is read and used when writing tags
; Danish, Finnish, Nec, Queens, TechLogic, TV2, 3M, TRC, ITG, ITG2, ISO-28560-2, Dutch, French or Raw
Type = "Danish"

[SECONDARYDATAMODEL]
; Secondary Data models. If analyze of main data model fails, tag data is passed to secondary datamodels
; Danish, Finnish, Nec, Queens, TechLogic, TV2, 3M, TRC, ITG, ITG2, ISO-28560-2, Dutch, French or Raw
Type = ""

[DANISH]
; ReadBytes
; 16, item ID, usage type and set information returned, item ID max 13 chars
; 20, item ID max 16 chars
; 32, library ID and country code returned, library ID max 9 chars
; 36, library ID max 11 chars
; 40, media format returned
; 56-112, item IDs and/or library IDs longer than 16/11 chars
ReadBytes = 40
; Check CRC, 0 no, 1 yes (ReadBytes must be >= 32)
CheckCRC = 1
; WriteBytes
WriteBytes = 40

[FINNISH]
; Check CRC, 0 no, 1 yes
CheckCRC = 1

[TV2]
ReadBytes = 32
WriteBytes = 32

[3M]
; MapVersion 3(numeric), 4(alphanumeric), default 4
MapVersion = 4

[ISO-28560-2]
; ReadBytes
ReadBytes = 48

[ITG]
; Single item set size, 0 or 1. Default 1.
SingleItemSetSize = 1

[DUTCH]
; Id mode. Which field/fields should be used to obtain item id.
; 0 = Both, 1 = Barcode, 2 = Object Identifier, default 0
IdMode = 0;
; Object identifier to mark that barcode field should be used. Nedap 10000000000006. Requires IdMode 0. Default = "".
UseBarcode = ""
; Library id mode.
; 0 = Nedap mode, 1 = ASCII/BCD, default 0
LibIdMode = 1

[RAW]
; Returns raw data instead of encoded
; ReadBytes
ReadBytes = 48

[TAG]
; Tag manufacturer
Manufacturer = "Philips"
; Tag type

© P.V. Supa Oy Ltd

73
Type = "ISO 15693 (ICode SLI)"
; Empty tag masks
Empty1 = "0000000000000000????????00000000"

[READ]
; Number of times inventory is executed (1...10), default 1
InventoryCount = 1;
; Delay between inventories, milliseconds (0...1000), default 0
InventoryDelay = 20
; Number of read data retries in case failure (0...10), default 0
ReadDataRetryCount = 1
; Delay between read retries, milliseconds (0...1000), default 0
ReadDataDelay = 20

[SECURITY]
; Security mode, 0 for afi only, 1 EAS only, 2 both, 3 use AFI deactivate EAS
SecurityMode = 0
; Activate afi value
AfiAct = 7
; Deactivate afi value
AfiDeact = 194
; Number of retries in case of write security failure (1...20)
WriteRetryCount = 5

[MISC]
; Set default byte order, 0 no, 1 yes, default yes
; DefaultByteOrder = 0

© P.V. Supa Oy Ltd

74
ANNEX E: Tag file format file
Default tag file format file produces following output as specified in line
<Format>{0},{1},{2},{3},{4},{5},{6}</Format>.

1101014974656D313233340000000000000000F9EB464931323334353637380000000C01005901416C7
435363738000000000000,Item1234,Alt5678,12345678,FI,Book,Item for circulation
<?xml version="1.0" encoding="utf-8"?>
<TagFileFormat xmlns:xsi="[Link]
xmlns:xsd="[Link]
<Format>{0},{1},{2},{3},{4},{5},{6}</Format>
<Description>{0} RawData, {1} ItemId, {2} OptionalData, {3} LibraryId, {4} Country code, {5}
Media format, {6} Usage</Description>
<MediaTypes>
<MediaTypeMapping>
<MappedName>Undefined</MappedName>
<MediaIdentifier>MediaUndefined</MediaIdentifier>
</MediaTypeMapping>
<MediaTypeMapping>
<MappedName>Book</MappedName>
<MediaIdentifier>Book</MediaIdentifier>
</MediaTypeMapping>
<MediaTypeMapping>
<MappedName>CD or DVD</MappedName>
<MediaIdentifier>CD_DVD</MediaIdentifier>
</MediaTypeMapping>
<MediaTypeMapping>
<MappedName>Magnetic tape</MappedName>
<MediaIdentifier>MagneticTape</MediaIdentifier>
</MediaTypeMapping>
<MediaTypeMapping>
<MappedName>Other</MappedName>
<MediaIdentifier>Other</MediaIdentifier>
</MediaTypeMapping>
<MediaTypeMapping>
<MappedName>Other careful handling is required</MappedName>
<MediaIdentifier>OtherCarefulHandling</MediaIdentifier>
</MediaTypeMapping>
<MediaTypeMapping>
<MappedName>Very small item</MappedName>
<MediaIdentifier>SmallItem</MediaIdentifier>
</MediaTypeMapping>
<MediaTypeMapping>
<MappedName>Format7</MappedName>
<MediaIdentifier>Format7</MediaIdentifier>
</MediaTypeMapping>
<MediaTypeMapping>
<MappedName>Format8</MappedName>
<MediaIdentifier>Format8</MediaIdentifier>
</MediaTypeMapping>
<MediaTypeMapping>
<MappedName>Format9</MappedName>
<MediaIdentifier>Format9</MediaIdentifier>
</MediaTypeMapping>
<MediaTypeMapping>
<MappedName>Format10</MappedName>
<MediaIdentifier>Format10</MediaIdentifier>
</MediaTypeMapping>
<MediaTypeMapping>
<MappedName>Format11</MappedName>
<MediaIdentifier>Format11</MediaIdentifier>
</MediaTypeMapping>
<MediaTypeMapping>
<MappedName>Format12</MappedName>
<MediaIdentifier>Format12</MediaIdentifier>

© P.V. Supa Oy Ltd

75
© P.V. Supa Oy Ltd

76