MiCard MultiTech4

Installation & Configuration Manual

Versioning
Document Version Date Author(s) Reviewer(s)
Versioning
Thomas
1.0 27-Nov-2018 Lemmer, André Thomas Lemmer, André Meß, Holger Bauszus
Meß
Thomas
1.1 28-Jan-2019 Lemmer, André Thomas Lemmer, André Meß
Meß
Thomas
1.2 Lemmer, André Thomas Lemmer
Meß
2.0 30-Mar-2020 André Meß Thomas Lemmer
Thomas
2.1 15-Jul-2021 Holger Bauszus
Lemmer

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  MiCard MultiTech4-P

Concerned
 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 Version Topic(s) Changes

Changes
1.0 All Initial version.
Added support for "Paradox" and
Supported transponder types (on page 31)
"ISONAS™".
Firmware version (on page 24)
1.1 Added new topic "Firmware version".
FAQ (on page 34) Added an FAQ section.
Configuration of the App Improved note.
Added another FAQ.
FAQ (on page 34)
1.2 Added note to topic Enabling Tracer
Enabling Tracer Mode (on page 4)
Mode.
Added instructions for MiCard
2.0 All
MultiTech4-P BLE and -PI BLE
Compliance and disposal notes (on page
2.1 Added NCC compliance note (Taiwan).
32)
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: info@nt-ware.com
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
documentation@nt-ware.com 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
documentation@nt-ware.com 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

Contents
1 Introduction ............................................................................................... 1

2 Connection ................................................................................................. 1

3 LED and beeper behavior ............................................................................ 2

4 Compatibility .............................................................................................. 2

5 MiCard 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

6 MiCard 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

7 Firmware version...................................................................................... 24
7.1 Firmware version string explanation ........................................................................... 26
7.2 Firmware compatibility ............................................................................................... 27
7.3 Apply standard firmware image (factory default) ........................................................ 28

8 Specifications ........................................................................................... 29
8.1 Supported transponder types ...................................................................................... 31
8.2 Compliance and disposal notes ................................................................................... 32
8.3 EU declaration of conformity ....................................................................................... 34

9 FAQ .......................................................................................................... 34

10 Index ........................................................................................................ 37

I
MiCard MultiTech4

1 Introduction
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.

2 Connection
Connect the card reader to the USB port of the device.

1
MiCard MultiTech4

3 LED 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).

4 Compatibility
 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
2
MiCard MultiTech4

 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.

5 MiCard 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)).

3
MiCard MultiTech4

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).

4
MiCard MultiTech4

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.

5
MiCard MultiTech4

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.

6
MiCard MultiTech4

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.

7
MiCard MultiTech4

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.

8
MiCard MultiTech4

b. For all other Canon devices, select Encrypted NT-ware Core Keyboard V3.23,
App NT-ware Standard V1.00.

4. Select the Frequency and Type (LF (125kHz / 134.2kHz) and HID Prox for this
example).
For a list of all supported transponder types and their supported frequencies, see
Supported transponder types (on page 31).

9
MiCard MultiTech4

5. Click on Add to add the transponder type to the Active Transponder Types list.

6. Repeat the previous step to add further transponder types, if required.

7. Expand the Transponder Types for further configurations, depending on the
requirements.

10
MiCard MultiTech4

8. Select Output Format and Decimal (for this example).

The MiCard MultiTech4 readers can be configured to support multiple different card
technologies at the same time, regardless of technology and frequency range. There is
no limit on the amount of different configured transponder types.

5.1.4 Creation of the app

In this step the .bix and .abp file are created.
The .abp file is the project configuration file for the AppBlaster (NT-ware Edition),
which stores the configuration of the card reader.
The .bix file is the image file that must be uploaded to the card reader to activate the
configuration on the card reader.
1. Select Version Information.
2. Type a unique identifier as App Character (max. 4 characters).

11
MiCard MultiTech4

3. Enter an App Description.

4. Click Save.
The resulting .abp file is the AppBlaster (NT-ware Edition) project file, which can
be utilized to do further modifications on the App (e.g., to add additional
transponder types).
5. Click Create Image.
The resulting .bix file is the App (firmware file), which needs to be uploaded to the
MiCard MultiTech4.

Firmware and App cannot be read back from a reader. This allows storing secret keys
and other cryptographic functionality as part of an App. Furthermore, the possibility to
clone a device is avoided, and the intellectual property is protected.

5.1.5 Uploading the app to the card reader

1. Attach the card reader to your computer (USB).

12
MiCard MultiTech4

2. Select Program Firmware Image.

3. Select the .bix file for this project.

13
MiCard MultiTech4

4. Click Program Image.

5. This completes the configuration of the MiCard MultiTech4 reader.

6 MiCard MultiTech4 BLE

The MiCard MultiTech4-P BLE & MiCard MultiTech4-PI BLE can work in the frequencies
of 125 kHz, 134.2 kHz, 13.56 MHz, and the BLE frequency range. To use the BLE
functionality, you need to use an Android/iOS smartphone and the NT-ware Mobile
Badge BLE app.
The following readers are using the Nano chipset:
 MiCard MultiTech4-P BLE
 MiCard MultiTech4-PI BLE
For Canon CMFP devices (not eULM), select Encrypted NT-ware Nano CMFP V3.23,
App NT-ware CMFP V1.01 when configuring the app (see Example configuration of the
app (on page 17)).

14
MiCard MultiTech4

For all other Canon devices, select Encrypted NT-ware Nano Keyboard V3.23, App
NT-ware Standard V1.00 when configuring the app (see Example configuration of the
app (on page 17)).

6.1 Android/iOS App - NT-ware Mobile Badge BLE

6.1.1 Download of the app

The NT-ware Mobile Badge BLE app is available free of charge and can be downloaded
via Google Play for Android devices and the Apple App Store for Apple iOS devices. It is
mandatory to utilize the BLE functionality of the MiCard MultiTech4 BLE card readers.
 Apple App Store - NT-ware Mobile Badge BLE
(https://apps.apple.com/app/nt-ware-mobile-badge-ble-2-0/id1491354650)
 Google Play - NT-ware Mobile Badge BLE
(https://play.google.com/store/apps/details?id=com.ntware.mobilebadge.ble20)

6.1.2 Unique Phone ID

The NT-ware Mobile Badge BLE app utilizes the following unique Phone IDs from the
smartphone:
 Apple iOS: Vendor ID
 Android: Android Device ID
Both Phone IDs are stable and unique per smartphone and can neither be changed nor
assigned manually.

15
MiCard MultiTech4

The Phone ID utilized is displayed in the Settings screen of the app:

Please be aware that a factory reset of the smartphone can result in a new Phone ID.

6.1.3 Configuration of the app

In general default settings are recommended, so no user interaction is required. It is
possible to individually configure the connection distance on the Settings screen of the
app. Please note that only the Short-Range setting applies since only this range is
relevant in uniFLOW / uniFLOW Online environments.

16
MiCard MultiTech4

The Background mode is currently in Beta phase on the Android app.

In case you encounter problems with the Background mode, please disable this
setting. The setting is disabled by default.

6.1.4 Configuration in uniFLOW / uniFLOW Online

The Phone ID will be stored as a Card Identity in uniFLOW / uniFLOW Online. The card
learning functionality (Card Registration Code / Username/Password) needs to be
activated accordingly. No further configuration within uniFLOW / uniFLOW Online
required.

6.2 Configuration example

The customer would like to use the HID Prox cards. Additionally, the customer would
like to use smartphone authentication.
The following transponder types must be enabled:
 BLE 2.0
 HID Prox
The following chapters explain how to use the AppBlaster (NT-ware Edition) to
configure the card reader(s). The topics are based on an example configuration for the
above-mentioned transponder types.

6.2.1 Example 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.
The customer would like to limit the usage to HID Prox and BLE 2.0 transponder types.
The default output format for all transponder types is set to hexadecimal uppercase.

17
MiCard MultiTech4

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 Nano module.
Select Application Template.
3. Select the firmware Nano module:
a. For Canon CMFP devices (not eULM), select Encrypted NT-ware Nano CMFP
V3.23, App NT-ware CMFP V1.01.

18
MiCard MultiTech4

b. For all other Canon devices, select Encrypted NT-ware Nano Keyboard V3.23,
App NT-ware Standard V1.00.

4. Select the Frequency and Type (LF (125kHz / 134.2kHz) and HID Prox for this
example) and select BLE (Bluetooth® Low Energy) for BLE 2.0.
For a list of all supported transponder types and their supported frequencies, see
Supported transponder types (on page 31).

19
MiCard MultiTech4

5. Click on Add to add the transponder type to the Active Transponder Types list.

6. Expand the Transponder Types for further configurations, depending on the

requirements.

20
MiCard MultiTech4

7. Select Output Format for further configuration if necessary.

The MiCard MultiTech4 readers can be configured to support multiple different card
technologies at the same time, regardless of technology and frequency range. There is
no limit on the amount of different configured transponder types.

6.2.2 Creation of the app

In this step the .bix and .abp file are created.
The .abp file is the project configuration file for the AppBlaster (NT-ware Edition)
which stores the configuration of the card reader.
The .bix file is the image file which must be uploaded to the card reader to activate the
configuration on the card reader.
1. Select Version Information.
2. Type a unique identifier as App Character (max. 4 characters).

21
MiCard MultiTech4

3. Enter an App Description.

4. Click Save.
The resulting .abp file is the AppBlaster (NT-ware Edition) project file which, can
be utilized to do further modifications on the App (e.g., to add additional
transponder types).
5. Click Create Image.
The resulting .bix file is the App (firmware file), which needs to be uploaded to the
MiCard MultiTech4.

Firmware and App cannot be read back from a reader. This allows storing secret keys
and other cryptographic functionality as part of an App. Furthermore, the possibility to
clone a device is avoided, and the intellectual property is protected.

6.2.3 Uploading the app to the card reader

1. Attach the card reader to your computer (USB).

22
MiCard MultiTech4

2. Select Program Firmware Image.

3. Select the .bix file for this project.

23
MiCard MultiTech4

4. Click Program Image.

5. This completes the configuration of the MiCard MultiTech4 reader.

7 Firmware version
To identify the firmware image configured on the MiCard MultiTech4, the AppBlaster
(NT-ware Edition) can be utilized.
1. Connect the MiCard MultiTech4 to your computer via USB.
2. Open the AppBlaster (NT-ware Edition).

24
MiCard MultiTech4

3. Select Program Firmware Image.

4. Click on Read Version.

25
MiCard MultiTech4

5. The firmware image configured will be displayed in the Messages box.

If the MiCard MultiTech4 firmware image has been provided by NT-ware, the firmware
image can be identified by the next-to-last section, e.g. "G0031.00".

7.1 Firmware version string explanation

The firmware version string can be utilized to clearly identify the firmware image
applied to a MiCard MultiTech4 card reader.

Example

The string consists of fixed and variable values which are explained in the following.
Possible values for the "variable values" are listed under each bullet point.

26
MiCard MultiTech4

Fixed values
TWN4 Product Family Name
B1.08 Version of Boot Loader
N Encrypted NT-ware Boot Loader

Variable values
N Underlying Hardware Technology
 C: Core, Core Module, Desktop Readers (-P, -PI, -P LEGIC)
 N: Nano, Nano Module, MiCard MultiTech4 (-P BLE, -PI BLE)
K Type of USB Communication
 K: USB Keyboard
 M: MiCard Protocol (CMFP only)
F HF Frontend
 A: High Frequency (LEGIC 42 or LEGIC 45)
 B: Low Frequency & High Frequency (LEGIC 42 or LEGIC 45)
 E: High Frequency only
 F: Low Frequency & High Frequency (standard)
 L: Low Frequency only
 X: No Frequency (signaling an error condition)
3.23 Firmware Version (Base / AppBlaster (NT-ware Edition) Version)
NTW Name of configured Firmware App (2-4 characters)
1.0.1 Version of configured Firmware App
P Additional Features of Card Reader
 P: Extended Set of Supported Transponder Types
 PI: Extended Support of -P Option
 PB: Extended Set of Supported Transponder Types and BLE Support
 PIB: Extended Support of -P Option and BLE Support

7.2 Firmware compatibility

MiCard MultiTech4 readers with a firmware older than V3.23
With release of the AppBlaster (NT-ware Edition) 3.23 the AppBlaster (NT-ware
Edition) equally requires the base firmware version of the MiCard MultiTech4 card
reader to be 3.23 (or higher) and Encrypted NT-ware Boot Loader. This is because it
contains some security-related updates that were required with the new version of the
AppBlaster (NT-ware Edition).
Upgrading a MiCard MultTech4 from the previously released firmware versions (e.g.,
3.12/3.20) to version 3.23 is not possible.
27
MiCard MultiTech4

You will receive the following error message in the AppBlaster (NT-ware Edition) when
trying to update the firmware:
The provided firmware image is not compatible with the connected TWN4. Please
double check, if the firmware image was create for the connected device.
If you have any questions regarding this or if you face problems due to this change at
existing customers please open a ticket in the MOMPS area of the ITS and the NT-ware
Project Team will help you.

7.3 Apply standard firmware image (factory default)

In case you have to reset the reader to the standard firmware image (factory default),
please proceed as described in topic Uploading the app to the card reader (on page
12).
For MiCard MultiTech4-P -PI -P LEGIC proceed as follows:
1. Navigate to ..\AppBlaster_-_NT-ware_Edition_3.23\Firmware\MiCard MultiTech4
-P -PI -P LEGIC\
2. Use the firmware file TWN4N_CKx323_STDN100_CoreN_NT-ware_Standard.bix to
set the reader back to its factory default.

For MiCard MultiTech4-P BLE / -PI BLE proceed as follows:

1. Navigate to ..\AppBlaster_-_NT-ware_Edition_3.23\Firmware\MiCard MultiTech4
-P -PI BLE\
2. Use the firmware file TWN4N_NKx323_STDN101_NanoN_NT-ware_Standard.bix
to set the reader back to its factory default.

28
MiCard MultiTech4

8 Specifications
Model:  MiCard MultiTech4-P
 MiCard MultiTech4-PI
 MiCard MultiTech4-P LEGIC
 MiCard MultiTech4-P BLE
 MiCard MultiTech4-PI BLE

Power supply:  4.3 V - 5.5 V via USB

Current consumption:  RF field on: 120-140 mA typically / Sleep: 500 μA typ. /

Cyclic Operation: TBD

USB connector:  USB Type A, pre-wired 45 cm (17.7 ") USB cable

Indicators:  Tri-state LED, dual-tone beeper

Frequency:  125 kHz/134.2 kHz (LF) / 13.56 MHz (HF)

 2.4 GHz (Bluetooth® Low Energy; BLE models only)
Antenna:  Integrated

Housing:  Material: ABS UL94-V0, color: white

Read/write distance:  Up to 100 mm / 4 inches, depending on environment

and transponder

Transmission speed:  Host: USB full speed (12 Mbit/s), Air: up to 848 kbit/s

Operating modes (USB):  USB keyboard emulation – MiCard Protocol (CMFP)

MTBF  500,000 hours

Dimensions:  Desktop Reader: 88 mm x 56 mm x 18 mm / 3.5 inch x

2.2 inch x 0.7 inch

Weight:  Approx. 20 g (without housing)

Temperature range:  Desktop, Operating: -25 °C up to +70 °C (-13 °F up to

+158 °F)
 Desktop, Storage: -45 °C up to +75 °C (-49 °F up to
+167 °F)

Relative humidity  5% to 95% non-condensing

Included items:  MiCard MultiTech4

 Pre-wired USB cable
 Quick start guide

29
MiCard MultiTech4

Manufacturer:  ELATEC GmbH

Zeppelinstr. 1
82178 Puchheim
Germany

Certification name:  For MiCard MultiTech4-P and MiCard MultiTech4-PI:

TWN4 MIFARE NFC
 For MiCard MultiTech4-P LEGIC:
TWN4 LEGIC NFC
 For MiCard MultiTech4-P/-PI BLE: TWN4 MultiTech 2
Certifications:  The MiCard MultiTech4 card readers are certified
according to CE, FCC/IC, and RCM regulations. For a
detailed overview of country approvals, see
MOMKB-939
(https://web.nt-ware.net/its/browse/MOMKB-93
9).

30
MiCard MultiTech4

8.1 Supported transponder types

MiCard MultiTech4-P: 13.56 MHz:
Calypso, CEPAS CAN, CTS CSN, CTS Special Sectors,
EM4x33, EM4x35, eTag CSN, Futitsu (MB89R118C,
MB89R119C, MB89R112), HID iCLASS® CSN, ICODE®
DNA CSN, ICODE® SLI CSN, ICODE® SLI Memory,
Infineon my-d™ CSN, ISO 14443A CSN, ISO 14443B
CSN, ISO 15693 CSN, I-tag CSN, Izly, LEGIC Advant CSN
(ISO 15693, 14443A), MIFARE® Classic (Standard, EV1)
Blocks, MIFARE® Classic (Standard, EV1) CSN,
MIFARE® DESFire® (Standard, EV1, EV2) CSN,
MIFARE® DESFire® (Standard, EV1, EV2) Memory,
MIFARE® Plus CSN, MIFARE® Plus Memory incl. SL 0-3,
MIFARE® Pro X, MIFARE® Smart MX (CSN), MIFARE®
Ultralight® (Standard, EV1, C) CSN, MIFARE®
Ultralight® (Standard, EV1, C) Memory, Moneo, NFC
Host Card Emulation, NFC Peer to Peer (P2P), NFC
Type 1 CSN, NFC Type 2 CSN, NFC Type 3 CSN, NFC
Type 4 CSN, NTAG 2XX, Oyster CSN, PayPass CSN, Pico
Pass CSN, SLE44R35, SLE66Rxx (my-d move), Sony
FeliCa CSN, Sony FeliCa Special Blocks, SRF55Vxx
(my-d vicinity), SRI4K, SRIX4K CSN, SRI4K, SRIX4K
Memory, SRI512, SRT512 CSN, SRI512, SRT512
Memory, ST (ST, ST LRI1k, ST LRI2k, ST LRIS2k, ST
LRIS64k, ST M24LR64-R, ST M24LR04E-R, ST
M24LR16E-R), Texas Instruments Tag-It CSN, Texas
Instruments Tag-It Memory, Topaz
125 kHz, 134.2 kHz:
AWID, Bosch ReadykeyPRO® UID, Cardax UID,
CASI-RUSCO®, Cotag, Deister UID, EM 400x, EM 4050,
EM 410x (4100, 4102, 4105), EM 4150, EM 4200, EM
4305, EM 4450, EM 4550, Farpointe Data Pyramid,
Farpointe Data Pyramid UID, GProx™ II UID, HID®
Prox, Hitag 1, Hitag 2, Hitag S, Honeywell Nexwatch,
ICT, ID TECK Alternate (128 bits), ID TECK UID (64
bits), Indala® 26 bit / 40134 (Motorola), Indala® ASP
UID, Indala® ASP+ UID, Indala® ECR, ioProx, ISONAS™,
ISO FDX-B/4105, Kantech ioProx™, Keri KC-10x UID,
Keri KC-26x, Keri NXT UID, NEDAP Prox, PAC, Paradox,
Rosslare, T5557, T5567, TIRIS/HDX, UltraProx,
UNIQUE, ZOODIAC
MiCard MultiTech4-PI: All MiCard MultiTech4-P transponder types and the

31
MiCard MultiTech4

following:
13.56 MHz:
HID iCLASS® Elite (including Seos®), HID iCLASS® ID
technology (including Seos®), HID iCLASS® SE
technology
MiCard MultiTech4-P LEGIC: All MiCard MultiTech4-P transponder types and the
following:
13.56 MHz:
LEGIC Advant Special Sectors, LEGIC Prime CSN, LEGIC
Prime Special Sectors
MiCard MultiTech4-P BLE All MiCard MultiTech4-P transponder types and
Bluetooth® Low Energy
MiCard MultiTech4-PI BLE All MiCard MultiTech4-PI transponder types and
Bluetooth® Low Energy

Default Settings
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. This can be configured using the
MiCard MultiTech4 - AppBlaster (NT-ware Edition) (on page 3).

8.2 Compliance and disposal notes

FCC Compliance Notes (for USA)
This equipment has been tested and found to comply with the limits for a Class B
digital device, pursuant to part 15 of the FCC Rules. These limits are designed to
provide reasonable protection against harmful interference in a residential installation.
This equipment generates, uses and can radiate radio frequency energy and, if not
installed and used in accordance with the instructions, may cause harmful interference
to radio communications. However, there is no guarantee that interference will not
occur in a particular installation. If this equipment does cause harmful interference to
radio or television reception, which can be determined by turning the equipment off
and on, the user is encouraged to try to correct the interference by one or more of the
following measures:
 Reorient or relocate the receiving antenna.
 Increase the separation between the equipment and receiver.

32
MiCard MultiTech4

 Connect the equipment to an outlet on a circuit different from that to which the
receiver is connected.
 Consult the dealer or an experienced radio/TV technician for help.

IC Compliance Notes (for Canada)

This Class B digital apparatus complies with Canadian ICES-003.
Cet appareil numérique de la classe B est conforme à la norme NMB-003 du Canada.
For models with integrated RFID functionality:
This device complies with Industry Canada licence-exempt RSS standard(s). Operation
is subject to the following two conditions: (1) this device may not cause interference,
and (2) this device must accept any interference, including interference that may cause
undesired operation of the device.
Le présent appareil est conforme aux CNR d'Industrie Canada applicables aux appareils
radio exempts de licence. L'exploitation est autorisée aux deux conditions suivantes :
(1) l'appareil ne doit pas produire de brouillage, et (2) l'utilisateur de l'appareil doit
accepter tout brouillage radioélectrique subi, même si le brouillage est susceptible
d'en compromettre le fonctionnement.

NCC Compliance Notes (for Taiwan)

取得審驗證明之低功率射頻器材，非經核准，公司、商號或使 用者均不得擅自
變更頻率、加大功率或變更原設計之特性及功能。低功率射 頻器材之使用不得
影響飛航安全及干擾合法通信；經發現有干擾現象時，應 立即停用，並改善至
無干擾時方得繼續使用。前述合法通信，指依電信管理 法規定作業之無線電通
信。低功率射頻器材須忍受合法通信或工業、科學及 醫療用電波輻射性電機設
備之干擾。

User Information on Disposal of Waste Electrical & Electronic Equipment

(WEEE)
The WEEE symbol on the product and/or accompanying documents means that used
electrical and electronic equipment should not be mixed with general household
waste. For proper treatment, recovery, and recycling, please take this product to
designated collection points, in accordance with your national legislation and the
Directive 2012/19/EU.

33
MiCard MultiTech4

The following symbol is only valid in the European Union (EU).

The correct disposal of this product will help save valuable resources and prevent any
potential negative effects on human health and the environment, which could
otherwise arise from inappropriate waste handling.
Please contact your local authority for further details of your nearest designated
collection point.

For disposal in countries outside of the European Union

If you wish to discard this product, please contact your local authorities or dealer and
ask for the correct method of disposal.

Country of Origin / US Export Administration Regulations (EAR)

The country of origin for the MiCard MultiTech4 card readers is Germany. Its
components of US-origin make up less than 25% of the total product value.

8.3 EU declaration of conformity

NT-ware hereby declares that the radio equipment type MiCard MultiTech4 complies
with the Directive 2014/53/EU.
The full text of the EU Declaration of Conformity can be found under the following
URL: http://link.nt-ware.net/id160 (https://link.nt-ware.net/id160)

9 FAQ
Question Answer Question ID

Can firmware or app (configuration) Both firmware and app (configuration) cannot be read back MMT001
be retrieved from a MiCard from a reader. This allows storing secret keys and other
MultiTech4 card reader? cryptographic functions as part of an app.
Can a MiCard MultiTech4 card No, this is not possible. The card reader configuration can be MMT002
reader be cloned? stored by utilizing the AppBlaster (NT-ware Edition). Please also
see "MMT001".
Will the MiCard MultiTech4 card They are an addition to the current hardware offer. The MiCard MMT003
reader release replace other card V2 HiTag and MiCard V2 HID are replaced by the new MiCard

34
MiCard MultiTech4

Question Answer Question ID

readers offered by NT-ware? MultiTech4.

Can MiCard MultiTech4 card readers Yes, MiCard MultiTech4 card readers can be utilized with all MMT004
be utilized with uniFLOW / uniFLOW software solutions offered by NT-ware.
Online / uniFLOW Online Express /
Universal Login Manager?
Can MiCard MultiTech4 card readers Yes, MiCard MultiTech4 card readers can be utilized with the MMT005
be utilized with the uniFLOW uniFLOW Release Station on a project basis. This is currently
Release Station? not available on the NT-ware price list.
MiCard MultiTech4 card readers are Yes, NT-ware offers a USB Extention Cable (140 cm), which is MMT006
available with 45cm USB cables. Is it available on the NT-ware price list.
possible to attach a longer USB
cable?
MiCard MultiTech4 card readers are Yes, this is currently by design. NT-ware is already working on MMT007
displayed as "MiCard PLUS" within an improved mechanism to identify the attached card readers
the "List View" of the uniFLOW user correctly.
interface. Is this by design?
The AppBlaster (NT-ware Edition) The AppBlaster (NT-ware Edition) will try to load available MMT008
displays an error message when firmware templates on startup. If this is is not possible, e.g.,
searching for available templates. due to insufficient access rights of the logged-in user, please
How can this be resolved? right click on "AppBlaster.exe" and select "Run as
Error message: Administrator" to resolve the problem.
No templates found.
The MiCard MultiTech4 can be Due to security reasons, this setting is disabled within the MMT009
configured to accept Configuration default NT-ware firmware image. "Accept Configuration Cards"
Cards by utilizing the AppBlaster can be enabled in self-created firmware images, though. The
(NT-ware Edition). Why is this firmware image stored on the Configuration Card can be
setting not enabled by default? configured to not allow any further configurations through a
Configuration Card. This can be useful in case a customer starts
with Configuration A but wants to switch to configuration B at
a later stage without allowing the usage of Configuration Cards
in general.
Can multiple MiCard MultiTech4 This is currently not possible, but a feature request has been MMT010
card readers be configured at the raised with ELATEC to get this functionality included in an
same time utilizing the AppBlaster upcoming version of the AppBlaster (NT-ware Edition).
(NT-ware Edition)?
Are the Canon (eULM) device series Yes, the devices accept the card reader configured in USB MMT011
supported? keyboard mode.
Are there any plans to introduce a Yes, it is planned to provide a possibility to configure MiCard MMT012
uniFLOW functionality to distribute MultiTech4 card readers remotely.
firmware images (card reader
configurations) to MiCard
MultiTech4 card readers similar to
the MiCard PLUS configuration file
upload?
When configured in "Tracer Mode" If the MiCard MultiTech4 is configured in "Tracer Mode", the MMT013
the output in Notepad looks keyboard layout of the Windows operating system must be set
unreadable. Can this be changed? to QWERTY/QWERTZ. Otherwise, the read-out card data is
misinterpreted.

35
MiCard MultiTech4

Question Answer Question ID

The customer would like to remove Yes, go to Transponder Types > Output Format and set MMT014
leading zeros (e.g., 0001234 should Minimum to 1 digit in the Length of Output section.
be 1234). Can this be configured in
the AppBlaster (NT-ware Edition)?
Is the NT-ware Mobile Badge BLE No, this is currently not available. MMT015
app also available for
smartwatches?
Is Orange PackID as a smartphone Yes, this is available on a project basis. Please create a MOMPS MMT016
identification solution supported by ticket, and the NT-ware Project Team will help you.
the MiCard MultiTech4 BLE card
readers?
Can the MiCard MultiTech4 BLE card No, this is currently not possible. MMT017
readers be utilized with HID Mobile
Access?
Is the "Tracer Mode" also available Yes, the Tracer app is available in the Firmware folder of the MMT018
for MiCard MultiTech4 BLE card AppBlaster (NT-ware Edition) package.
readers?
MiCard MultiTech4 BLE card readers Yes. All MiCard MultiTech4 card readers can be utilized with MMT019
and NT-ware Mobile Badge BLE app any uniFLOW / uniFLOW Online version.
have been launched with uniFLOW
2020 LTS. Can we use them with
previous uniFLOW versions as well?

For any questions regarding MiCard MultiTech4 card readers or transponder type
support and configuration, open a MOMPS ticket, and the NT-ware Project Team will
help you.

36
MiCard MultiTech4 Index

Index
A H
Android/iOS App - NT-ware Mobile Badge BLE ..15 How to use this Document ...................................9
Apply standard firmware image (factory default)
............................................................................28 I
Introduction ..........................................................1
C
Compatibility ........................................................ 2 L
Compliance and disposal notes ...................... 3, 32 LED and beeper behavior .....................................2

Configuration example ................................... 4, 17 Legal and Safety Notices .......................................8

Configuration in uniFLOW / uniFLOW Online.....17

M
Configuration of the app ............................ 3, 7, 16
MiCard MultiTech4 - AppBlaster (NT-ware
Connection ........................................................... 1 Edition)........................................................ 2, 3, 32
Creation of the app....................................... 11, 21 MiCard MultiTech4 BLE ..................................... 14

D R
Disclaimer ............................................................. 5 Reading out the transponder type ...................6, 7
Download of the app ..........................................15
S
E Specifications ..................................................... 29
Enabling Tracer Mode ...................................... 3, 4 Supported transponder types........... 3, 1, 9, 19, 31
EU declaration of conformity .............................34
U
Example configuration of the app .......... 14, 15, 17
Unique Phone ID ................................................ 15

F Uploading the app to the card reader ....12, 22, 28

FAQ ................................................................. 3, 34
V
Firmware compatibility ......................................27
Versioning .............................................................3
Firmware version ............................................ 3, 24
Firmware version string explanation ..................26

37
© NT-ware 2009-2021