smartgate manager v11.0.0.

14
Installation Guide for BiblioChip-based Core Services

(Draft, for internal Bibliotheca use only)

www.bibliotheca.com
Copyrights & Trademarks
Copyright 2013 Bibliotheca, all rights reserved. Bibliotheca provides this document to customers and
prospective customers only. The content of this document is strictly confidential and may not to be
reproduced in any form or transferred by any means, in whole or in part, to any third party without the
explicit and prior written consent of Bibliotheca.

Liber8, smartadmin, smartgate manager,

smartstock manager, smartstation manager,
smartdispenser manager, and smartreturn manager are trademarks of Bibliotheca. All external
references to these products must be indicated with the Trademark symbol and credited to Bibliotheca.

3M Standard Interchange Protocol is the copyright of the 3M Corporation 1997, 1998, 2005.
Windows is a registered trademark of the Microsoft Corporation in the United States and other countries.

Terms & Conventions

Text boxes containing an orange circle and white i contain important information
pertaining to the use or configuration of the product. These may also contain tips or
recommendations from Bibliotheca or Bibliotheca customers.

Text boxes containing a red triangle and exclamation point contain either information
critical to the successful use or configuration of the product, or a warning. It is important to
read and consider the information presented in the hazard text boxes carefully.

Text boxes containing a blue square and question mark contain a definition or explanation
of a specific term or concept that may not be immediately apparent or common
knowledge to all users. The information in these text boxes should assist the readers
understanding of this documents content.

Clickable/Writeable Fields Bold Text denotes a button, tab, text field, or menu that a user can select or
otherwise interact with.
Location/Reference Italic text denotes the location of a file or folder on a computer, or a specific section
within the document or reference to a separate document

www.bibliotheca.com
smartgate manager v11.0.0.11 Installation Guide, page 3 of 23

Table of Contents

1 Introduction ............................................................................................................................................................... 4

2 System Requirements ............................................................................................................................................... 5

3 Network Setup ........................................................................................................................................................... 6

4 Pedestal Setup .......................................................................................................................................................... 7

4.1 Temporary connection to gates to load settings and set IP and other values for network. .............. 7
4.2 Default configuration of Feig gates .............................................................................................................. 7
4.3 Default configuration of Tagsys gates .......................................................................................................... 8
4.4 Testing the IP connectivity at the Staff Station PC ..................................................................................... 8

5 Installing smartgate manager .............................................................................................................................. 9

6 Configuring smartgate manager ....................................................................................................................... 10

6.1 Configuring the data models: BiblioChip.Integration\BiblioChip.ini:.................................................... 10
6.2 Configuring the read points: RFIDCore\BiblioChip RFID Core Configuration.xml ............................. 11
<IntegrationControllerConfiguration>.................................................................................................... 11
<ReaderSetupsValue> .............................................................................................................................. 12
<ServicesSetup> ......................................................................................................................................... 13
6.3 Configuring the core: CoreServices\Core Services Configuration.xml ................................................ 13
Core services library .................................................................................................................................. 13
Duplicate filtering ....................................................................................................................................... 13
Advanced topic: reversed people counters (Feig gates only) ........................................................ 14
6.4 smartgate manager.ini through the administrative screen .................................................................... 15
The Pedestals tab: configuring gate groups ......................................................................................... 15
The People Counter tab: configuring aisles .......................................................................................... 16
6.5 smartgate manager.ini by hand ................................................................................................................. 17
Configuring people counters for local reporting ................................................................................. 17
Configuring the application for smartadmin ........................................................................................ 18

7 Configuring the smartadmin client for smartgate manager ....................................................................... 19

8 Running smartgate manager ............................................................................................................................. 21

9 Data Model Key ...................................................................................................................................................... 22

10 Contact Bibliotheca Support ............................................................................................................................ 23

www.bibliotheca.com
smartgate manager v11.0.0.11 Installation Guide, page 4 of 23

1. Introduction
smartgate manager can be configured to use the BiblioChip core or the Intellident core. This document
discusses only configuring the BiblioChip core.
This guide is a draft, and does not cover every detail of every step.
We assume that all pedestal hardware, including people counters and controller boards, has been
installed and correctly configured for each gate and the librarys local security settings. This guide is to get
smartgate manager up and running; specifically:
Reading item barcodes off of tags with security ON as they pass through the gate
Communicating the barcodes to the ILS/LMS and displaying title and status information at the
smartgate manager console (and on smartadmin, when available)
Displaying patron count information on the smartgate manager console (and on smartadmin,
when available.)

We distinguish between a pedestal and a gate. A pedestal is a single antenna, with or without a reader
attached. A master pedestal is a pedestal with a reader, for example, a Feig A pedestal. A gate is a
collection of pedestals that cover a single entrance to the library. A Feig gate usually has a single IP
address, unless it has more than one master (A) pedestal. A Tagsys gate has distinct IP addresses for each
pedestal, as each pedestal is its own master.

www.bibliotheca.com
smartgate manager v11.0.0.11 Installation Guide, page 5 of 23

2. System Requirements
smartgate manager runs on a library-supplied computer, often a staff station. The library IT staff should
supply the following to the installation tech:
A computer running Windows 7 or Windows XP, meeting at least the minimum requirements for the
operating system. (Both 32-bit and 64-bit architectures are supported.)

An account with local administrative permissions. (If installing the smartadmin v2+ client, will
require regedit permissions as well.)

The installation tech should have available the following software prerequisites:

Microsoft .NET frameworks 3.5 and 4.0 (may be supplied by the operating system.)
The appropriate Microsoft SQL Server Compact Runtime Environment for the architecture of the
system.
For Tagsys gates, the Tagsys Library Pedestal Configuration Tool.
For Feig gates, the latest version of OBID ISOStart.

The Microsoft SQL Server installers are available here. The Feig and Tagsys utilities should be available in the
Support folder.

www.bibliotheca.com
smartgate manager v11.0.0.11 Installation Guide, page 6 of 23

3. Network Setup
The network administrator must assign a range of static IPs and should make a list for you showing which IP
is going into each pedestal position.
The network administrator should make reasonable efforts to ensure that the pedestals are reachable
across the firewall typically port 10001 for Feig and ports 4001 (and 4002 for auto-discovery) are open for
TCP and UDP traffic if needed.
Typically with Feig security gates there is one master pedestal (the A pedestal) with an IP address per
group of antennas. For Tagsys security gates, each pedestal has its own IP address and is its own group.

www.bibliotheca.com
smartgate manager v11.0.0.11 Installation Guide, page 7 of 23

4. Pedestal Setup

The details of setting up the number of pedestals, counters, or other peripherals per Feig
master using OBID-ISOStart is not covered in this document

4.1 Temporary connection to gates to load settings and set IP and other
values for network.
Before installing smartgate manager, please install the latest version of the Tagsys Library Pedestal
Configuration Tool or the Feig OBID ISOStart application. Then attempt to reach each pedestal via a
local USB connection, or by forcing your PC or Laptop have an Ethernet adaptor that is on the same IP as
the default IP of the pedestal temporarily. Often this step is done using a laptop computer of the install
tech.

4.2 Default configuration of Feig gates

We strongly recommend that for each Feig gate, you load the appropriate xml settings file
provided with smartgate manager or another default template file approved for use with
smartgate manager before configuring the IP address, AFI values and other settings.
If a default template for your gate architecture has not been provided, please contact
Bibliotheca Support.

There are many non-default settings needed for making Feig pedestals work with AFI, and smartgate
manager data gathering. It is important to load these settings BEFORE setting your gate IPs or other values
(such as number of pedestals, peripherals, etc.) If you try to load these settings AFTER you set other values
you will lose your other settings (such as the gate IP address). If you try to set the values manually to make
the pedestals work with smartgate manager you may run into difficulties and those procedures are not
documented here.

The default configuration file will save you some steps if loaded first. But even after loading it you must set
the correct AFI value(s), IP addresses, and other values related to the number of pedestals and peripherals.
Some of these settings are complicated, even using the OBID tool, and are outside of the scope of this
document. The seasoned install techs have knowledge of these settings. The settings presented in this
document are primarily those required for smartgate manager operation, over and above basic gate
alarming functionality.

www.bibliotheca.com
smartgate manager v11.0.0.11 Installation Guide, page 8 of 23

4.3 Default configuration of Tagsys gates

Use the most recent version of the Tagsys Library Configuration Tool to discover (or connect to) the
pedestal in question.

1. Read UID: checked

2. Read Memory: checked
3. Lowest Blocks First: checked
4. First Block: must be 0 (zero)
5. Nb Blocks: must be at least 8
6. Set other values for Tag
Types, AFI values, etc. Most
of these settings are very
obvious in the Tagsys
configuration windows.

4.4 Testing the IP connectivity at the Staff Station PC

Once the pedestals are installed and the IP addresses have been assigned, and before trying to connect
with smartgate manager, you should confirm that the master pedestals are all reachable through the
firewall. The best way to test this is to use the Feig or Tagsys configuration tool and use the IP of each master
pedestal to see if it can be reached

If you used your own laptop for setting the IP and other initial values on the pedestals, please install the
appropriate gate configuration software(OBID-ISOStart or Tagsys Library Pedestal Configuration Tool) on
the computer that will be used to run smartgate manager.

Once the pedestals are all reachable from the staff station PC, you can use that station to make remaining
changes to the pedestal configuration.

www.bibliotheca.com
smartgate manager v11.0.0.11 Installation Guide, page 9 of 23

5. Installing smartgate manager

smartgate manager v11.0.0.14 has an installer available, which will install the application in
C:\ProgramFiles (x86)\Bibliotheca\smartgate manager (for a 64-bit machine) or
C:\ProgramFiles\Bibliotheca\smartgate manager (for a 32-bit machine). After running the installer,
1. Allow all users (or at least the user with local administrator privileges under which smartgate manager
will be running) to have full control of the smartgate manager folder. The application executable
Bibliotheca smartgate manager.exe should be set to run as administrator.
2. We suggest running the executable vcredist_x86.exe included in the application folder.
3. Use the provided sample configuration files for appropriate gate hardware as the starting point for your
configurations. They have been given expanded names for clarity; please rename them to
BiblioChip.ini, BiblioChip RFID Core Configuration.xml, and smartgate manager.ini before deploying
them.

www.bibliotheca.com
smartgate manager v11.0.0.11 Installation Guide, page 10 of 23

6. Configuring smartgate manager

smartgate manager is concerned only with the barcode of an item detected by the gates. It does not
extract any other data from the tag; nor does it change the tags security setting in any way.
The application architecture of smartgate manager is on 4 levels .There is a configuration file at each level.

We will work from the bottom (BiblioChip.Integration) up.

6.1 Configuring the data models: BiblioChip.Integration\BiblioChip.ini:

BiblioChip.ini defines the data models used to decode a tag and provide the item barcode, and the AFI
values used to discriminate among the data models. Relevant options are provided below.
[Reader] - There is one gate-dependent setting in this block, SystemInformationAvailable. All other settings
are overridden by higher-level configuration files.
For Feig gates, SystemInformationAvailable should be set to 1.
SystemInformationAvailable = 1
For Tagsys gates, its value should be 0.
SystemInformationAvailable = 0
If you have Tagsys gates, forgetting to modify this setting will leave your gates unable to decode tags (for
any data model other than DM60.)
The default value is 1.
[FeigReader] The option TCPTimeout is used to specify the timeout for communication with Feig Ethernet
readers. The default value is 10000 (milliseconds); in the provided BiblioChip.ini file for smartgate
manager, it is configured for 20000 milliseconds.
TCPTimeout = 20000

[Common] - This is where to define the enabled data models, using the Bibliotheca RFID naming scheme
(Data Model key in Section 9) and separating each data model with a pipe | symbol. Among the more
common data models in our libraries: DM45 is Intellident 5; DM60 is Danish; DM170 is ISO 28560 -2; DM135 is
ITG 16; DM136 is ITG 15.
EnabledDataModels = 45|60|170|135|136
Note that the number of enabled data models directly affects the reliability of decoding tags. Best
practice is to enable only the data models used in the customer library and its circulation partners.

[Logger] - Unless you are trying to diagnose low-level tag reading errors in BiblioChip itself, leave the
loglevel at 1. A log level of 4 will generate hundreds of lines of output for a single tag read. You have
been warned.
loglevel=1
In addition, you can set the maximum file size (in MB) that BiblioChip.log can grow to before being
renamed to BiblioChip.log.001, and the maximum number of overflow log files that are created before
the last is overwritten. So to permit a maximum of nine 10MB logs,
MaxFileSize=10
MaxLogFiles=9

www.bibliotheca.com
smartgate manager v11.0.0.11 Installation Guide, page 11 of 23

Leaving these values unset, or 0, will allow a single BiblioChip.log file to grow without bound.

[DM#] - For each enabled data model, provide any AFI values that can be expected on a tag, separating
each value with a space. (So if the library is in a consortium where AFI values differ from member library to
member library, even with the same data model, enter all the valid AFI on and off values.) BiblioChip uses
the AFI value to help determine (with other factors) what data model the tag uses, so that it can extract
the data. Note that the AFI settings determine how to read the tag, not how to write it. For example,
consider an ITG 16 library (DM135) in which both 07 and 9E are valid ON values, and C2 and 9D are
OFF.
[DM135]
AFICI = 07 9E
AFICO = C2 9D

If the library wishes to recognize tags that use only EAS security (likely candidates are older ITG customers or
French libraries), add 00 to both the AFI check-in and check-out values.
[DM136]
AFICO = 9E 00
AFICO = 9D 00

Generally, libraries using EAS only are likely to have Tagsys gates. Feig pedestals, when configured for EAS
only, will detect every tag, whether security is ON or not. This is a limitation of the Feig pedestals.

6.2 Configuring the read points: RFIDCore\BiblioChip RFID Core

Configuration.xml
At the RFIDCore level, the reader configuration is defined in the file BiblioChip RFID Core Configuration.xml.
Unlike other applications, smartgate manager supports the concurrent use of multiple readers, also
called read points, corresponding to the master pedestal in each gate group.

Each instance of smartgate manager can only support a single gate architecture (e.g.,
Tagsys or Feig.) In the rare case that a library has gates from both manufacturers, they will
need separate instances of smartgate manager, each with its own SIP connection.

6.2.1 <IntegrationControllerConfiguration>
These are the recommended settings for the gates, regardless of architecture. Note that both ReadAFI
and ReadEAS are set to false. smartgate manager only attempts to decode tags whose security is ON,
based on detection by the security pedestal.
<ReadInterval>2000</ReadInterval>
<AisleCountsInterval>5000</AisleCountsInterval>
<MaximumReadDuration>3000</MaximumReadDuration>
<MaximumUpdateDuration>5000</MaximumUpdateDuration>
<ReadAFI>false</ReadAFI>
<ReadEAS>false</ReadEAS>

www.bibliotheca.com
smartgate manager v11.0.0.11 Installation Guide, page 12 of 23

6.2.2 <ReaderSetupsValue>
The readers are configured in the <ReaderSetupsValue> block. Each reader is defined in its own
<ReaderSetup>. Each Id must be unique. By default, the application uses ReadPoint1, ReadPoint2, etc. for
each master pedestal. The following is an example of a 2-master-pedestal Feig deployment.

<ReaderSetup>
<RegistrationName />
<Id>ReadPoint1</Id>
<ConfigurationValue>
<BiblioChipReaderType>FeigGate</BiblioChipReaderType>
<Name>Front Gate</Name>
<Interface>TCP</Interface>
<Address>192.168.51.18</Address>
<Port>10001</Port>
<Baudrate>38400</Baudrate>
</ConfigurationValue>
</ReaderSetup>

<ReaderSetup>
<RegistrationName />
<Id>ReadPoint2</Id>
<ConfigurationValue>
<BiblioChipReaderType>FeigGate</BiblioChipReaderType>
<Name>Back Gate</Name>
<Interface>TCP</Interface>
<Address>192.168.51.20</Address>
<Port>10001</Port>
<Baudrate>38400</Baudrate>
</ConfigurationValue>
</ReaderSetup>
Below is a single Tagsys (master) pedestal configuration.
<ReaderSetup>
<RegistrationName />
<Id>ReadPoint1</Id>
<ConfigurationValue>
<BiblioChipReaderType>TagsysLSP3</BiblioChipReaderType>
<Name>Front Gate</Name>
<Interface>TCP</Interface>
<Address>192.168.51.19</Address>
<Port>4001</Port>
<Baudrate>115200</Baudrate>
</ConfigurationValue>
</ReaderSetup>

The <name> tag is a friendly name, but is not promoted to the top level of the application. The <Id> tag
value is used by Core Services to define the reader across the application.

www.bibliotheca.com
smartgate manager v11.0.0.11 Installation Guide, page 13 of 23

6.2.3 <ServicesSetup>
In the <ServicesSetup> block, the read points are configured for each service. smartgate manager uses
two of the core services: RFIDItemService, to detect individual items and return the barcode; and
RFIDAisleCountsService, which reads the people counter values from the gates. Every read point defined in
the <ReaderSetupsValue> block must be declared for each service in which it is used. (This is not an issue in
other Core Services applications because they only use a single reader defined by default as Reader1.)
For the 2-read-point example above, the corresponding block is below:
<ServicesSetup>
<ServiceSetup>
<RegistrationName>bibliochipRFIDItemService</RegistrationName>
<ServiceId>RFIDItemService</ServiceId>
<Configuration>
<Readers>
<string>ReadPoint1</string>
<string>ReadPoint2</string>
</Readers>
</Configuration>
</ServiceSetup>
<ServiceSetup>

<RegistrationName>bibliochipRFIDAisleCountsService</RegistrationName>
<ServiceId>RFIDAisleCountsService</ServiceId>
<Configuration>
<Readers>
<string>ReadPoint1</string>
<string>ReadPoint2</string>
</Readers>
</Configuration>
</ServiceSetup>
</ServicesSetup>
For a single read point, delete/comment out the reference to ReadPoint2.

6.3 Configuring the core: CoreServices\Core Services Configuration.xml

This file is used to define which set of core services the application will use, in our case, BiblioChip; to set the
duration within which duplicate item detections are filtered; to define which people counter direction is IN
and which is OUT.

6.3.1 Core services library

To use the BiblioChip core services, set <CoreSetup><FactoryId> tag to be bibliochip.
<FactoryId>bibliochip</FactoryId>
Because smartgate manager does not write item security, we can ignore the <SecurityCategoriesValue>
block entirely.

6.3.2 Duplicate filtering

Within ExpiryInterval of first detecting an item, core services will filter out duplicate detections. By default,
the ExpiryInterval is 7 seconds.
<RegistrationName>AccumulatingStaging</RegistrationName>
<Configuration xsi:type="StagingExpiryConfig">
<ExpiryInterval>7000</ExpiryInterval>
<ExpiryResetOnDetection>false</ExpiryResetOnDetection>
</Configuration>

www.bibliotheca.com
smartgate manager v11.0.0.11 Installation Guide, page 14 of 23

6.3.3 Advanced topic: reversed people counters (Feig gates only)

There was a period during which Feig gates were installed with people counter directions reversed, so that
rather than the count being returned as an (IN, OUT) pair, it was returned as (OUT, IN). To account for this
oddity without installing the gates backwards, we permit the orientation of the people counter to be
configured from the library level (all read points) down to a per-aisle basis. This applies to both BiblioChip
and ISEM (Intellident) core services.
The setting in question, <AisleCountsMappingValue> is under the <ServiceSetup> block for the
(RFID)AisleCountsService. It can contain many <SerializableAisleCountsMapping> children, each
potentially corresponding to a single aisle.
By default, the application is configured for all defined aisle in normal (non-reversed) order, using the
pattern * as the key.
<SerializableAisleCountsMapping>
<Key>*</Key> <!-- match all read points, all aisles -->
<Value>
<InCount>0</InCount> <!-- IN is first direction -->
<OutCount>1</OutCount> <!-- OUT is second direction -->
</Value>
</SerializableAisleCountsMapping>

To set the direction of an individual aisle, we need to identify the specific people counter. The format is
<ReaderId>,[<board number>].[<detector number>], where <ReaderId> is the read point name
(ReadPoint1, ReadPoint2, etc.); <board number> is a value between 1 and 3, as defined by OBID as
the bus for the given controller board; and <detector number> is a value between 1and 2, for the sensors
position on the board. So given the key ReadPoint1[2][1], smartgate manager will match all detectors on
the read point (gate/pedestal) with the hardware Readpoint1; [2]_ will match the controller board on
bus 2; _[1] will match the first sensor on that board.
<SerializableAisleCountsMapping>
<Key>ReadPoint1[2][1]</Key> <!-- match only ReadPoint1, board 2,
sensor 1 -->
<Value>
<InCount>1</InCount> <!-- IN is second direction -->
<OutCount>0</OutCount> <!-- OUT is first direction -->
</Value>
</SerializableAisleCountsMapping>
The application will attempt to match against <SerializableAisleCountsMappingValue> settings in order. If
the all read points pattern appears before any specific configuration in the file, its settings will be applied
and all other patterns will be ignored.

www.bibliotheca.com
smartgate manager v11.0.0.11 Installation Guide, page 15 of 23

6.4 smartgate manager.ini through the administrative screen

The main configuration file for the application, smartgate manager.ini resides in the application root folder
(usually C:\Program Files (x86)\Bibliotheca\smartgate manager). In this file, we set user preferences,
SIP/NCIP communication with the ILS/LMS (not covered in this guide), smartadmin communication, and the
mapping between the UI/local reporting and core services.
The easiest way to begin setting up the application is to run the graphical configuration tool through the
administrative screens. Further configuration must be done by hand.
We will concentrate on the Pedestals and People Counter tabs in this document.

6.4.1 The Pedestals tab: configuring gate groups

For Pedestal Type select 3-All. Then enter the number of pedestal groups. This corresponds exactly to the
number of distinct read points you defined in BiblioChip RFID Core Configuration.xml. For Tagsys gates,
each pedestal is its own group; for Feig gates, each master (A) pedestal constitutes a group.
To configure each group, select the group number in the Edit Group box using the arrows. For each group,
select a descriptive Name (such as FrontEntrance or BackDoor.)
The Control ID is the name of the read point of this gate group, and must correspond to one of the read
points defined in BiblioChip RFID Core Configuration.xml.
The Station ID is only used for legacy ITG Centralized Statistics and Reporting and should otherwise be
ignored. When used a unique number should be supplied per group.
Note that the other settings are disabled, and cannot be modified.

www.bibliotheca.com
smartgate manager v11.0.0.11 Installation Guide, page 16 of 23

6.4.2 The People Counter tab: configuring aisles

The People Counter tab configures the people counter configuration for each aisle. The syntax is:
[ControllerBoardNumberOnMaster][PeopleCounterNumberOnBoard]
Use Edit Group to select the current gate group by number.
For Tagsys pedestals (each of which is its own master), there is only one controller board and people
counter sensor per pedestal. The Aisle ID will always be [1][1].
For each Feig read point, we can configure a people counter per aisle. A master pedestal may have up
to 3 controller boards associated with it, and up to 2 people counters per controller board (for a maximum
of 6 aisles per master pedestal.)
In our example gate (FrontEntrance), we have 3 aisles, configured with 2 controller boards and 3 sensors.
The first controller board is on bus 1, and has 2 sensors. So its Aisle IDs for aisles 1 and 2 are defined by [1][1]
and [1][2] respectively.
Below, we show the 3rd aisle of FrontEntrance. Its people counter sensor is on controller board 2, in position
1, so its Aisle ID is [2][1].

The smartadmin ID is used to uniquely identify the gate on the smartadmin server, so that the server display
and alerts are (somewhat) descriptive. The format for smartadmin ID is:
gate group name.Counter#
where # is the aisle number in the gate group.
After making the appropriate changes for each of your read points, save the settings and exit the
application.

www.bibliotheca.com
smartgate manager v11.0.0.11 Installation Guide, page 17 of 23

6.5 smartgate manager.ini by hand

Now edit the file smartgate manager.ini by hand. You should see most of the settings you made in the
admin screens you may wish to review the settings. The relevant section is in the [Pedestals] block, at the
bottom of the file.

6.5.1 Configuring people counters for local reporting

The IP address and port for each master pedestal is defined in BiblioChip RFID Core Configuration.xml. In
smartgate manager.ini, a pedestal corresponds to an aisle/people counter, rather than a read point. The
setting NumPedsInGroupN corresponds to the number of aisles in group N, rather than the number of
master pedestals in the group
For local reporting (not smartadmin), you need to define a unique IP address/port for each pedestal
(aisle). For Tagsys gates, this is not an issue, as each aisle is a master pedestal, and has its own people
counter and IP address. For Feig gates, it is more complicated, since aisles cant share an IP address. Our
suggested solution is to just append a letter onto the end of the common IP address for the gate
group/read point, so that its easy to distinguish the people counters belonging to that group.
For our single read point, 3-aisle example in the previous section,
NumOfGroups=1
GroupName1=FrontEntrance
GroupStationID1=1
NumPedsInGroup1=3
GroupID1=ReadPoint1
Group1Ped1IP=192.168.51.20A
Group1Ped1Port=10001
AisleID1,1=[1][1]
SmartAdminID1,1=Gates.FrontEntrance.Counter1
Group1Ped2IP=192.168.51.20B
Group1Ped2Port=10001
AisleID1,2=[1][2]
SmartAdminID1,2=Gates.FrontEntrance.Counter2
Group1Ped3IP=192.168.51.20C
Group1Ped3Port=10001
AisleID1,3=[2][1]
SmartAdminID1,3=Gates.FrontEntrance.Counter3
Note that not all Tagsys gates will have people counters. (Often, the last pedestal spanning an entrance
will not have a gap between it and the wall, so no people counter is needed.) If the gate does not have a
people counter, simply leave the AisleID and SmartAdminID settings out of its gate group definition, e.g.
GroupName1=Town Hall Left
GroupStationID1=1
NumPedsInGroup1=1
GroupID1=ReadPoint1
Group1Ped1IP=192.168.51.23
Group1Ped1Port=4001

www.bibliotheca.com
smartgate manager v11.0.0.11 Installation Guide, page 18 of 23

6.5.2 Configuring the application for smartadmin

To enable reporting of item detections and people count data to smartadmin, the two settings in the
[smartAdmin] block should be set to true.
[smartAdmin]
ReportPeopleCounts=True
ReportItemAlerts=True
If you configure the aisles through the Administrative screen, you do not need to worry about setting the
SmartAdminID for each people counter. If you configure the aisles by hand, the format of the righthand
side of the SmartAdminID for each people counter should follow the groupname.CounterN convention,
where N is the aisle number within the gate group called groupname. The lefthand SmartAdminID
numbering scheme is group number, aisle number, and matches the AisleID numbering scheme. For
example, consider a gate made up of two Tagsys pedestals (two gate groups).
NumOfGroups=2
GroupName1=BackGateLeft
GroupStationID1=1
NumPedsInGroup1=1
GroupID1=ReadPoint1
Group1Ped1IP=192.168.51.19
Group1Ped1Port=4001
AisleID1,1=[1][1]
SmartAdminID1,1=BackGateLeft.Counter1
GroupName2=BackGateRight
GroupStationID2=2
NumPedsInGroup2=1
GroupID2=ReadPoint2
Group2Ped1IP=192.168.51.21
Group2Ped1Port=4001
AisleID2,1=[1][1]
SmartAdminID2,1=BackGateRight.Counter1

www.bibliotheca.com
smartgate manager v11.0.0.11 Installation Guide, page 19 of 23

7. Configuring the smartadmin client for smartgate manager

smartadmin is still in beta for smartgate manager. Please have the project manager contact Software
Development to determine whether your site is eligible to participate and to obtain the appropriate
smartadmin client and documentation. It is not available on Sharepoint.
smartgate manager requires the smartadmin 2.0 client and server. The available client at the time of
writing is version 2.0.0.6.
Install the smartadmin 2.0 client according to its installation guide. You should have previously installed
the SQLServer Compact Runtime Environment when setting up smartgate manager. Make sure that
your servicemodel.bindings.config and servicemodel.client.config are set up for the appropriate server
and server type.

1. smartadmin uses a registry key to find the applications files for remote administration. If this is the first
installation of smartgate manager on this computer, or the first time attempting to use smartadmin, the
key may not be present. The installer for smartgate manager does not automatically create the
registry key for the application. Check the registry (in both Wow6432Node and SOFTWARE) before
creating the key.

If on a 64-bit computer, to the HKEY_LOCAL_MACHINEWow6432NodeBibliotheca key, add a key

called smartgate manager if it does not already exist.

If on a 32-bit computer, add the key to HKEY_LOCAL_MACHINESOFTWARE Bibliotheca key.

To a new key, add a string value InstallPath, with its data being the fully qualified path to the
executable. For example,

2. Edit smartadmin.client.config.
a. Generate a GUID for the identifier. Each 2.0 client has to have its own unique identifier. (There
are a number of on-line sites to generate GUIDs, for example here.)
b. The deviceType for smartgate manager is 2000.
c. The part number for a generic people counter is 15; the part number for the item detector is
31.

www.bibliotheca.com
smartgate manager v11.0.0.11 Installation Guide, page 20 of 23

d. Since we can have multiple people counters and item detectors per smartgate manager,
weve added an instanceId field to the parts list. Starting at 0, increment the instanceId for
each part of the same type you add to the parts list.
In the configuration file below, we have 2 gate groups, each with an item detector (part 31).
The first gate group has a single people counter (part 15), the second has 3 people counters.
Note that there are no descriptions available for the parts. Each part name is taken from the
smartAdminID (for people counters) or the gate group name (for item detection) in smartgate
manager.ini.
<smartadmin.client remoteServerAvailable="true" ignoreSSL="false">
<identification identifier="aeaaa146-9d22-463e-b975-b55c4ec259e7"
customer="Bibliotheca"
location="Norcross"
device="NorcrossGates"
deviceType="2000" />
<deviceParts totalParts="6">
<parts>
<add name="Part1" serverId="31" instanceId="0" />
<add name="Part2" serverId="15" instanceId="0" />
<add name="Part3" serverId="31" instanceId="1" />
<add name="Part4" serverId="15" instanceId="1" />
<add name="Part5" serverId="15" instanceId="2" />
<add name="Part6" serverId="15" instanceId="3" />
</parts>
</deviceParts>
<proxy serverName="" port="" domain="" user="" password="" />
<timers>
<add name="workTimer" period="120" />
<add name="statisticsTimer" period="120" />
</timers>
<installer packageSource="https://www.mysmartadmin.com/software/"
updatesLocation="c:\program files\bibliotheca\updates" />
</smartadmin.client>

e. Delete or comment out the legacy <gateCounters> block.

Version 11.0.0.14 of smartgate manager is stubbed for smartadmin client v2.1 (currently in beta) support,
and requires no modifications to the application when the smartadmin client is upgraded

www.bibliotheca.com
smartgate manager v11.0.0.11 Installation Guide, page 21 of 23

8. Running smartgate manager

If smartgate manager is running and connected to gates when the staff station
computer sleeps, hibernates, or its network adapter otherwise loses power, Windows will cut
the network connection to the gates. On awakening the computer, smartgate manager
may not be able to reestablish the connection.
First, try disconnecting and reconnecting the reader through the Do Pedestal Data Gather
button. If that fails, try restarting smartgate manager. If it still cannot connect, it may be
necessary to power-cycle each master pedestal to permit any network connection,
because its internal state is still connected.
To avoid this condition, disconnect smartgate manager from its gates via the Do
Pedestal Data Gather button, disable automatic sleep/hibernate, or set the staff station
computer to not power down its network adapter for power-savings.

www.bibliotheca.com
smartgate manager v11.0.0.11 Installation Guide, page 22 of 23

9. Data Model Key

Below is a cross-reference list of data models used by Bibliotheca, Intellident, and ITG. Use the Bibliotheca
Data Model numbers when specifying data models.
Description Bibliotheca Intellident ITG Notes
Bibliotheca DM1 1
Bibliotheca DM2 2
Bibliotheca DM3 3
Bibliotheca DM10 10
Bibliotheca DM11 11 16 Used before Danish in the UK
Bibliotheca DM12 12
Bibliotheca DM20 20
Bibliotheca DM21 21
Bibliotheca DM32 32
Axiell 40 8 SATO printer cannot encode
Intellident 1 41 1
Intellident 2 42 2
Intellident 3 43 3
Intellident 4 44 4
Intellident 5 45 5 Used at Axiell UK Customer
Danish 60 12 Also Used by D-Tech and Tlepen
Bibliotheca DM61 61 Mirror image of DM60
Bibliotheca DM62 62 Same as DM61 but without CRC
Netherlands NBD 70
Italy 101
Lucatron 128
3M Version 3 133 9 Numeric Item ID
3M Version 4 134 9 Alphanumeric Item ID
ITG 16 135 16
ITG 15 136 15 Based on Tagsys standard
Idrabib 137 7 French Standard
Plescon 138 14
Belgian 139 11
Swiss 140 13
Japan 150 Not compatible for use with any other data
model
ISO 28560-3 160
IOS 28560-2 170 10
VTLS 200 Tagsys C230 transponder specific
UID Uses UID as Item ID
2CQR 255 15
Dutch 6 Parameter driven

www.bibliotheca.com
smartgate manager v11.0.0.11 Installation Guide, page 23 of 23

10. Contact Bibliotheca Support

Contact Bibliotheca Support 24/7 using the following details.

+61 (3) 9811 4750

support-au@bibliotheca.com

877.207.3127 (toll free)

support-ca@bibliotheca.com
+45 7027 1008
support-dk@bibliotheca.com
+31 (0)229-505538
support-nl@bibliotheca.com
+33 (0)1 56 24 11 76
support-fr@bibliotheca.com
+39 800 011 060
support-it@bibliotheca.com
+49 7121 9264 115
support-de@bibliotheca.com
+41 41 726 9950
support-ch@bibliotheca.com
+44 (0)161 498 1150
support-uk@bibliotheca.com
877.207.3127 (toll free)
support-us@bibliotheca.com

Please be ready with your librarys customer number, case number, any applicable error messages or
conditions, and the product version or serial number.

www.bibliotheca.com