UniFlow MiCard MultiTech4 Instruction sheet

MiCard MultiTech4
Installation & Configuration Manual

Versioning
Document
Versioning
Version
Date
Author(s)
Reviewer(s)
1.0
27-Nov-2018
Thomas
Lemmer, André
Meß
Thomas Lemmer, André Meß, Holger Bauszus
1.1
28-Jan-2019
Thomas
Lemmer, André
Meß
Thomas Lemmer, André Meß
1.2
Thomas
Lemmer, André
Meß
Thomas Lemmer
2.0
30-Mar-2020
André Meß
Thomas Lemmer
2.1
15-Jul-2021
Thomas
Lemmer
Holger Bauszus
Document Name
MiCard MultiTech4 - Installation & Configuration Manual
Knowledgebase
MOMKB-998 (https://web.nt-ware.net/its/browse/MOMKB-998)
File Name
MiCard MultiTech4 - Installation & Configuration Manual.pdf
Technologies
Concerned
MiCard MultiTech4-P
MiCard MultiTech4-PI
MiCard MultiTech4-P LEGIC
MiCard MultiTech4-P BLE
MiCard MultiTech4-PI BLE
Short Summary
Installation & configuration manual for the NT-ware MiCard MultiTech4 series.
Document
Changes
Version
Topic(s)
Changes
1.0
All
Initial version.
1.1
Supported transponder types (on page 31)
Firmware version (on page 24)
FAQ (on page 34)
Configuration of the App
Added support for "Paradox" and
"ISONAS™".
Added new topic "Firmware version".
Added an FAQ section.
Improved note.
1.2
FAQ (on page 34)
Enabling Tracer Mode (on page 4)
Added another FAQ.
Added note to topic Enabling Tracer
Mode.
2.0
All
Added instructions for MiCard
MultiTech4-P BLE and -PI BLE
2.1
Compliance and disposal notes (on page
32)
Added NCC compliance note (Taiwan).

Disclaimer
NT-ware Systemprogrammierungs-GmbH, all its affiliates, partners and licensors disclaim all warranties,
including, but not limited to, warranties about the accuracy or completeness of statements of this
site's/document's content or the content of any site or external sites for a particular purpose. This
site/document and the materials, information, services, and products at this site/document, including,
without limitation, text, graphics, and links, are provided 'as is' and without warranties of any kind, whether
expressed or implied.
All rights reserved. No parts of this work may be reproduced in any form or by any means - graphic,
electronic, or mechanical, including photocopying, recording, taping, or information storage and retrieval
systems - without the prior written permission of NT-ware Systemprogrammierungs-GmbH (hereinafter
also referred to as NT-ware).
Company and product names mentioned herein are registered or unregistered trademarks of their
respective companies. Mention of third-party products is for information purposes only and constitutes
neither an endorsement nor a recommendation. NT-ware assumes no responsibility with regard to the
performance or use of these products. Also, NT-ware makes no claim to these trademarks. Any use of
trademarks, logo, service marks, trade names, and product names is prohibited without the written
permission of the respective owners.
Adlib, Express and Express Server are either registered trademarks or trademarks of Adlib Publishing
Systems Inc.; Adobe®, Adobe® Reader®, Acrobat®, Distiller®, PostScript® and products of the CREATIVE
SUITE(S) are either registered trademarks or trademarks of Adobe Systems Incorporated in the United
States and/or other countries; Android is a trademark of Google Inc.; Apple®, the Apple® logo, Mac®, Mac
OS®, Macintosh®, iPhone®, iPad® and AirPrint® are trademarks of Apple Inc. registered in the U.S. and other
countries; Box of Box Inc.; Blackboard Transact™ of Blackboard Inc.; CANON, imageRUNNER, imageRUNNER
ADVANCE, MEAP, CPCA, AMS, iW AMS, iW Desktop, iSend, iW SAM are trademarks or registered
trademarks of Canon Inc.; CardSmith® is a trademark of CardSmith LLC; CBORD CS Gold® of the CBORD
Group Inc.; Crystal Reports and other Business Objects products and services mentioned herein as well as
their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business
Objects is an SAP company; Dropbox of Dropbox Inc.; eCopy™, eCopy ShareScan® and eCopy ScanStation™
are marks or trademarks of Nuance Communications, Inc.; Evernote® of Evernote Corporation; FileNet® of
IBM Corporation; Foxit®SDK and Foxit® Reader of Foxit Corporation; Google Docs of Google Inc.; Google
Cloud Print™ web printing service is a trademark of Google Inc.; Helix™ Production Workflow is a trademark
of NT-ware Systemprogrammierungs-GmbH; HP, HEWLETT-PACKARD, PCL and LASERJET are registered
trademarks that belong to HP Inc.; KONICA MINOLTA is a registered trademark of KONICA MINOLTA Inc.;
iOS® of Cisco Technology Inc.; iDRS™ SDK and IRISConnect™ are unregistered trademarks of I.R.I.S. Group
S.A.; JAWS pdf courier™ are trademarks of Global Graphics SA.; Microsoft®, Windows®, Windows Server®,
Internet Explorer®, Internet Information Services, Microsoft® Word, Microsoft® Excel, Microsoft
SharePoint®, Microsoft SharePoint® Online, OneDrive®, One Drive® for Business, SQL Server®, Active
Directory®, Hyper-V® are either registered trademarks or trademarks of Microsoft Corporation in the
United States and/or other countries of Microsoft Corporation; Mopria Print Service of Mopria Alliance Inc.;
Neevia Document Converter Pro™ of Neevia Technology; NetWare®, Novell®, Novell eDirectory™ of Novell
Inc. are registered/unregistered trademarks of Novell Inc. in the United States and other countries;
MobileIron® of Mobile Iron Inc., Océ, Océ PlotWave®, Océ ColorWave® and PRISMA are trademarks or
registered trademarks of Océ-Technologies B.V. Océ is a Canon company, OpenOffice.org™ of Oracle
Corporation; PAS™ is a trademark of Equitrac Corp.; PosterJet is copyrighted and an internationally
registered trademark of Eisfeld Datentechnik GmbH & Co. KG; RedTitan EscapeE of RedTitan Limited;

NETAPHOR®, SiteAudit™ are trademarks of NETAPHOR SOFTWARE Inc.; SAMSUNG is a trademark of
SAMSUNG in the United States or other countries; Therefore™, Therefore™ Online of Therefore; UNIX® is a
registered trademark of The Open Group; uniFLOW®, mdsFLOW®, uniFLOW Serverless Secure Printing®,
Helix Production Workflow®, MIND®, microMIND®, and MiCard® are registered trademarks of NT-ware
Systemprogrammierungs-GmbH; pcProx®, AIR ID® are registered trademarks of RFIdeas Inc.Readers;
CASI-RUSCO® is a registered trademark of ID Card Group; Radio Key® is a registered trademark of Secura
Key; GProx™ II is an unregistered trademark of Guardall; HID® ProxHID is a registered trademark of HID
Global Corporation; Indala® is a registered trademark of Motorola; ioProx™ is an unregistered trademark of
Kantech; VMware vSphere® and VMware vSphere® Motion® are registered trademarks of VMware; Xerox,
Xerox and Design, as well as Fuji Xerox and Design are registered trademarks or trademarks of Xerox
Corporation in Japan and/or other countries.
All other trademarks, trade names, product names, service marks are the property of their respective
owners and are hereby acknowledged.
While every precaution has been taken in the preparation of this document, NT-ware assumes no
responsibility for errors or omissions, or for damages resulting from the use of information contained in this
document or from the use of programs and source code that may accompany it. NT-ware does not assume
any responsibility or liability for any malfunctions or loss of data caused by the combination of at least one
NT-ware product and the used operating system and/or third-party products. In no event shall NT-ware be
liable for any loss of profit or any other commercial damage caused or alleged to have been caused directly
or indirectly by this document.
In addition, this manual provides links to the sites of affiliated or independent companies and certain other
businesses. NT-ware is not responsible for examining or evaluating, and NT-ware does not warrant the
offerings of, any of these businesses or individuals or the content of their websites. NT-ware does not
assume any responsibility or liability for the actions, product, and content of all these and any other third
parties. You should carefully review their privacy statements and other conditions of use.
Thursday, July 15, 2021, Bad Iburg (Germany)
Important Note
Serious problems might occur if you modify the registry of your Windows operating system incorrectly.
These problems might require that you reinstall the operating system. We strongly recommend to always
back up the registry of your Windows operating system before applying changes to it, just in case you do
something wrong. NT-ware does not assume any responsibility or liability for any impact on the
operating system after changing the registry. You understand and accept that you use this information
and modify the registry of your Windows operating system at your own risk.
uniFLOW and corresponding components like Web Submission and Internet Gateway rely heavily on
their SQL databases. We strongly suggest that you refrain from modifying these SQL databases manually
without prior consultation from the NT-ware support team. NT-ware does not assume responsibility or
liability for possible impact on your uniFLOW environment after modifying any of the SQL databases.
Copyright and Contact
NT-ware Systemprogrammierungs-GmbH
Niedersachsenstraße 6
49186 Bad Iburg
Germany

www.nt-ware.com
Tel: +49 - 54 03 - 7243 - 0
Fax: +49 - 54 03 - 78 01 03
Email: [email protected]om
Register of Companies: Amtsgericht Osnabrück
No. of entry in Register of Companies: HRB 110944
Chief Executive Officer: Karsten Huster
Responsible according to § 6 MDStV: Karsten Huster
VAT registration no. according to §27 a Umsatzsteuergesetz: DE 230932141
©1998-2021 NT-ware Systemprogrammierungs-GmbH.
Feedback
Should you come across any relevant errors or have any suggestions, please contact
[e-mail] or use the Send feedback here button of the uniFLOW Online Help.
Technical Support
Your dealer will provide first technical support services. Before you contact the dealer for technical support,
ensure you have read this document.

Legal and Safety Notices
Intended Use of NT-ware Products
NT-ware products may only be used for the applications specified in this manual and the associated
technical documentation. If third-party products and components are used, they must be recommended or
approved by NT-ware. Use NT-ware products only with accessories approved by us. Correct and safe
operation of the products requires proper transport, storage, installation, assembly, commissioning,
operation and maintenance. The permissible ambient conditions must be observed. Notes in the
corresponding documentation must be observed.
Qualified Staff
The device this documentation belongs to may only be operated by staff qualified for the relevant task,
observing the documentation belonging to the respective task, in particular the safety and warning
instructions contained therein. Due to their training and experience, qualified staff is able to recognize risks
and avoid possible dangers when operating this device.
Modifications
Changes and/or modifications of the device not approved by NT-ware will make void the users' authority to
operate the device. Modification of a device also invalidates CE, FCC and other certifications and will void
the warranty.
Defective Devices
Do not use defective devices, cables or accessories. Defective devices must be disconnected from the
power supply immediately. Please note that repairs to electrical devices may only be carried out by
qualified staff.
Cleaning
Clean the device with a slightly dampened cloth that has been wrung out well. Turn off the power, unplug
the device and unplug the USB connector before cleaning. Never use alcohol, benzene, paint thinner,
aerosol sprays or any other highly flammable substance for cleaning. Improper cleaning can lead to
malfunctions.
Liability Exclusion
We have checked the contents of this document for compliance with the hardware and software described.
Nevertheless, deviations cannot be ruled out, so that we do not assume any guarantee for complete
conformity. The information in this publication is regularly checked, necessary corrections are included in
the following editions.

How to use this Document
Text Styles
This style is used for text that is displayed on screen.
This style is used for text the user has to type in.
This style is used for hyperlinks to web pages, internal links to other pages in this manual.
This style is used for code examples: XML code, variables or regular expressions.
Pictograms
Important Note:
Information that is crucial for the correct functioning of the software.
Further Information:
Pointer to additional manuals, installation manuals, white papers or the NT-ware
Knowledgebase.
Region Specific Feature:
Indicator for features that are not available worldwide.
External Link:
Link to an external web page.
Settings:
Detailed explanation of configuration settings or operational procedures.
Compass:
Path to the menu or configuration page in the software.
Screenshots and Diagrams
This manual contains screenshots of the software, diagrams explaining relations and pictures of products.
Even though all visuals are up-to-date at the time of writing, they are subject to change.
Language and Translations
This document has originally been written in English language. Translations of this document are based on
the English original. Some screenshots, diagrams and pictures in this document may not be translated and
appear in English language only.
Send Feedback
Should you come across any relevant errors or have any suggestions please contact
[e-mail] or use the Send feedback here button of the Online Help.

About this Document
This document is delivered as part of the device / the software from NT-ware. Please read this document
before using the device / the software and keep this document or the link to an online version of this
document for future reference. Please make sure that all persons operating the device / the software are
familiar with this document. Please observe all instructions given in this document. Installation,
configuration and maintenance must only be performed by sufficiently qualified personnel. Failure to
comply with this document may void the warranty.
Every effort has been made to ensure that the contents of this manual are accurate. However, NT-ware
reserves the right to make changes without notice.

MiCard MultiTech4 Contents
I
Contents
1Introduction ............................................................................................... 1
2Connection ................................................................................................. 1
3LED and beeper behavior............................................................................ 2
4Compatibility.............................................................................................. 2
5MiCard MultiTech4 - AppBlaster (NT-ware Edition) .................................... 3
5.1 Configuration example..................................................................................................4
5.1.1 Enabling Tracer Mode....................................................................................................................4
5.1.2 Reading out the transponder type.................................................................................................6
5.1.3 Configuration of the app................................................................................................................7
5.1.4 Creation of the app......................................................................................................................11
5.1.5 Uploading the app to the card reader .........................................................................................12
6MiCard MultiTech4 BLE ............................................................................ 14
6.1 Android/iOS App - NT-ware Mobile Badge BLE ............................................................ 15
6.1.1 Download of the app ...................................................................................................................15
6.1.2 Unique Phone ID..........................................................................................................................15
6.1.3 Configuration of the app..............................................................................................................16
6.1.4 Configuration in uniFLOW / uniFLOW Online..............................................................................17
6.2 Configuration example................................................................................................ 17
6.2.1 Example configuration of the app ...............................................................................................17
6.2.2 Creation of the app......................................................................................................................21
6.2.3 Uploading the app to the card reader .........................................................................................22
7Firmware version...................................................................................... 24
7.1 Firmware version string explanation ........................................................................... 26
7.2 Firmware compatibility ............................................................................................... 27
7.3 Apply standard firmware image (factory default) ........................................................ 28
8Specifications ........................................................................................... 29
8.1 Supported transponder types...................................................................................... 31
8.2 Compliance and disposal notes ................................................................................... 32
8.3 EU declaration of conformity....................................................................................... 34
9FAQ .......................................................................................................... 34
10 Index ........................................................................................................ 37

MiCard MultiTech4
1
1Introduction
The MiCard MultiTech4 is a USB card reader that combines proximity and contactless
technologies into one single reader and comes in five different versions:
MiCard MultiTech4-P
MiCard MultiTech4-PI
MiCard MultiTech4-P LEGIC
MiCard MultiTech4-P BLE
MiCard MultiTech4-PI BLE
For simplicity, we call the reader MiCard MultiTech4 in this manual. Technical and
configuration differences are explained accordingly.
MiCard MultiTech4 is able to read various different contactless transponder types. See
topic Supported transponder types (on page 31) for a list of all supported transponder
types.
This reader eliminates the need for manual entry and provides error-free identification
and security throughout the workplace. The MiCard MultiTech4 allows users to use
their contactless building access card / time tracking card for identification in
conjunction with Canon MEAP enabled devices (V3.0.8 onwards), Canon SFP MEAP
devices (V1.0.2 onwards), and microMIND V2 (V2.0.5 onwards). In addition, the
MiCard MultiTech4-P BLE and -PI BLE allows the authentication via the Android/iOS
app called NT-ware Mobile Badge BLE.
The plug and play reader comes with flash memory, allowing the user to quickly
configure the output to meet the needs. With its dual-frequency multi-technology
support and no limitation on the amount of the various supported transponder
technologies, the MiCard MultiTech4 is highly configurable.
The default configuration –as shipped by NT-ware - of MiCard MultiTech4 card readers
is to ensure maximum compatibility. Therefore the majority of supported transponder
types and BLE (if applicable) are enabled by default. NT-ware highly recommends
configuring the card readers to the specific transponder types in use at the customer to
ensure maximum performance of the card reader.
2Connection
Connect the card reader to the USB port of the device.

MiCard MultiTech4
2
3LED and beeper behavior
The MiCard MultiTech4 reader is equipped with two LEDs and a beeper which emits
different beep tones for different statuses.
The default values are shown in the following screenshot. LEDs and beep tones are
configurable via the MiCard MultiTech4 - AppBlaster (NT-ware Edition) (on page 3).
4Compatibility
Canon MEAP devices (V3.0.8 onwards)
Canon SFP MEAP devices (V1.0.2 onwards)
Canon CMFP devices
Note that the MiCard MultiTech4 reader must be configured for Canon CMFP
devices. To make it compatible, the reader requires a certain configuration. Please
refer to MiCard MultiTech4 - AppBlaster (NT-ware Edition) (on page 3).
Canon imageFORMULA ScanFront devices
microMIND V2 (V2.0.5 onwards)
uniFLOW

MiCard MultiTech4
3
uniFLOW Desktop Scan Client (requires uniFLOW 2018 LTS or higher)
uniFLOW Online
Universal Login Manager (ULM)
embedded Universal Login Manager (eULM)
Note that eULM devices utilize the keyboard protocol similar to Canon MEAP and
Canon SFP devices. Therefore, no CMFP/MiCard protocol is required.
5MiCard MultiTech4 - AppBlaster (NT-ware
Edition)
The MiCard MultiTech4 can be configured with the MiCard MultiTech4 - AppBlaster
(NT-ware Edition) configuration utility.
A configuration via uniFLOW Server Configuration > Connections > Agents/Terminals
> MiCard is not possible.
The AppBlaster (NT-ware Edition) configuration utility must be copied to a Windows
computer first.
Software Download
MiCard MultiTech4 - AppBlaster (NT-ware Edition)
(https://web.nt-ware.net/its/browse/MOMKB-998)
When downloaded, unzip, and run the AppBlaster.exe file.
The AppBlaster (NT-ware Edition) is described in the following subchapters, based on
an example configuration.
The following readers are using the Core chipset:
MiCard MultiTech4-P
MiCard MultiTech4-PI
MiCard MultiTech4-P LEGIC
For Canon CMFP devices (not eULM), select Encrypted NT-ware Core CMFP V3.23, App
NT-ware CMFP V1.01 when configuring the app (see Configuration of the app (on page
7)).
For all other Canon devices, select Encrypted NT-ware Core Keyboard V3.23, App
NT-ware Standard V1.00 when configuring the app (see Configuration of the app (on
page 7)).

MiCard MultiTech4
4
5.1 Configuration example
The customer utilizes two different transponder-type cards:
MIFARE Classic
HID Prox
The customer would like to limit the access to the printers to the HID Prox transponder
type only. By default, the card reader would allow all transponder types.
The following chapters explain how to use the AppBlaster (NT-ware Edition) to
configure your specific cards. The topics are based on an example configuration for the
above mentioned MIFARE Classic and HID Prox.
5.1.1 Enabling Tracer Mode
To identify the transponder types utilized by the cards in use at the customer, you
need to set the MiCard MultiTech4 into the so-called "Tracer Mode".
This operating mode allows you to read out the transponder-type information with the
MiCard MultiTech4. The transponder-type information is required to configure the
device according to your needs.
Enabling the MiCard MultiTech4 "Tracer Mode"
1. Connect the MiCard MultiTech4 to your computer via USB.
2. Open the AppBlaster (NT-ware Edition).

MiCard MultiTech4
5
3. Select Program Firmware Image.
4. Click on Select Image and choose the Tracer app
(TWN4N_CKx323_TRC220_Tracer.bix) from the \Firmware\ folder.
Note that the file name may vary depending on the firmware version.

MiCard MultiTech4
6
5. Click Program Image.
6. After the successful application of the app, the MiCard MultiTech4 will be in
"Tracer Mode". You will recognize a red flashing Status LED on the card reader.
The MiCard MultiTech4 cannot be attached to a printer when in "Tracer Mode".
5.1.2 Reading out the transponder type
Once the MiCard MultiTech4 "Tracer Mode" is enabled, you can read out the
transponder type information with the MiCard MultiTech4.
1. Connect the MiCard MultiTech4 to your computer via USB.
2. Open a text editor (e.g., Notepad) on your computer.
3. Swipe your customer card(s) to identify the transponder types utilized.
Note that some cards may have various transponder types. To ensure all
transponder types are read out, leave the card on the reader for a couple of
seconds.

MiCard MultiTech4
7
4. Since the card reader is acting as a keyboard, the result is displayed in the text
editor as shown in the following example screenshot:
If the MiCard MultiTech4 is configured in "Tracer Mode", the keyboard layout of the
Windows operating system must be set to QWERTY/QWERTZ. Otherwise, the read-out
card data is misinterpreted.
5.1.3 Configuration of the app
Now that we know which transponder types to configure, we have to configure the
App of the device utilizing the AppBlaster (NT-ware Edition). The firmware
configuration file is called App in the following chapters.
As can be seen in our example screenshot in topic Reading out the transponder type
(on page 6), the customer has MIFARE Classic and HID Prox cards in use.
The customer would like to limit the usage to HID Prox transponder types. As the card
number is stored in decimal output format in Active Directory, the output needs to be
changed.
The default output format for all transponder types is set to hexadecimal uppercase.

MiCard MultiTech4
8
1. Open the AppBlaster (NT-ware Edition) and select Configurable Project.
2. Since different devices require different communication protocols, we need to
configure the reader with the respective firmware Core module.
Select Application Template.
3. Select the Firmware Core Module:
a. For Canon CMFP devices (not eULM), select Encrypted NT-ware Core CMFP
V3.23, App NT-ware CMFP V1.01.