1.6. Problems, errors, issues

µFR Nano UART on Raspberry Pi 3

How to flash-update µFR Firmware and test the reader

How to flash-update µFR Firmware – µFR reader/writer firmware upgrade & downgrade If your device is a non-wireless µFR reader/writer (Nano, Classic CS, Classic, Advance, XL), all can update its firmware using the flashing software tool available at https://code.d-logic.com/nfc-rfid-reader-sdk/ufr_plus-flasher-oneclick. When you initially run the flashing software on a Windows machine, you may get a pop-up warning as shown below. Make sure you click the Run Anyway button and enable this app. If you haven’t accomplished the step above and are experiencing a problem starting the software tool, you can still enable it in Windows security/Firewall & network protection, as seen below.   Further, use the uFR Plus Flasher and select the most recent firmware version:   Now, find the desired firmware version. Type the firmware ordinal number (the last one recommended) and press Enter. Wait for the software to complete the process. After you hear the reader’s beeper sound, the firmware flashing is completed. Make sure not to interrupt this process until it’s completely done. If it was interrupted for some reason (readers cable unplugged, power went down, etc.), you need to repeat the flashing process until it is successfully accomplished. How to test the reader’s basic functions — Programming...

When is an RF Booster Upgrade recommended?

The RF Booster upgrade is optional for most of the hardware of the Digital Logic product line. Its purpose is to power up the reader's RF field...

µFR Reader Writer on macOS – FTDI drivers and communication permissions tips

µFR Reader Writer on macOS FTDI drivers and communication permissions tips *NOTICE: Applicable only to old macOS versions and legacy µFR devices. Do not use for the µFR Zero series and recent macOS releases! macOS has a bit different structure than Linux so communication with the reader cannot be enabled with a simple script available for Linux users. Enabling the communication between the software and the USB-connected reader varies depending on the macOS version. The OS versions from Mavericks (version 10.9) and above already have the AppleUSBFTDI driver. The interface is matched to the FTDI kext, which in turn creates a BSD serial port for use at the application layer. The application opens the serial port to communicate with the hardware. On the other hand, the USB-connected µFR devices implement user client drivers to communicate directly with the device from the user space (FTDI D2XX Driver). Therefore, the presence of the AppleUSBFTDI kext might affect communication with the software. Software applications may fail to open a connection with the hardware because IOKit already has matched the AppleUSBFTDI driver to the device. The solution in this instance is to unload the AppleUSBFTDI drivers before installing the FTDI D2XX. You may find...

USB-connected µFR Nano Online NFC RFID Reader Writer on the Raspberry Pi

USB-connected µFR Nano Online NFC RFID Reader Writer on the Raspberry Pi To connect and run the µFR Nano Online reader plugged into the Raspberry Pi USB port, follow the instructions below: 1) USB-CONNECTED µFR NANO ONLINE NFC READER INSTALLATION All µFR series devices require FTDI drivers for USB communication. This also applies to the µFR Nano Online NFC reader if it is used as a standard USB device. If you have no FTDI drivers installed on your installed Raspberry Pi, please follow the manual for the FTDI drivers installed on the Linux-based platforms. This article is also available in our Knowledge Base. Important notice: Before you proceed with the µFR Nano Online implementation, make sure you grant the USB PORT access permission to the local user (the script is available in our GitLab projects repository). Once you have the FTDI drivers installed with your USB-connected NFC reader, you will be able to open the port and establish communication with the device by the ReaderOpen function provided by the ufr library. Important notice: The recommended library for the Raspberry Pi is the 64-bit aarch64. However, there are some known problems with aarch64 on a Raspberry Pi 4 with 8 GB...

iOS support for µFR Series hardware

For iOS, we provide the µFR Series hardware library for iOS, the APIs, and other documentation related to hardware, as well as all the necessary technical support for your project development.   As for the development tools and executable software solutions, the current iOS compliant SDK is available at our GitLab repository and the two apps at App Store.  The SDK is compliant with all the µFR Series devices, while one of two available iOS apps is developed for the µFR Nano Online reader exclusively.

Card/tag reading error on NT4H C Console software with device firmware version 5.0.52

The (currently latest) firmware version 5.0.52 may cause some SDK functions error, or the console freezing (issue detected in ufr-examples-c-nt4h software). If you are experiencing such a problem, the solution Is to install another firmware version on your device. If there is on new firmware version available in our firmware update list, we advise the firmware downgrade. The upgrade or downgrade of the firmware to the 5.0.51 version solves this issue. To install the new firmware, you can use the µFR Nano Online web settings (device IP), search for available firmware versions, and select the latest available firmware version, or the 5.0.51 version from the list.     Alternatively, for this purpose, you can also use desktop software https://code.d-logic.com/nfc-rfid-reader-sdk/ufr_online-flasher-oneclick.

Reader opening error on macOS – Code (0x54)

Reader opening error on macOS - Code (0x54)

Running Python SDK/software on macOS

For Python software examples, we suggest you use any Python 3.x.x version. If you don’t have the right Python version installed, use the following command line to install a new version: brew install python Now simply run our source code software example with the command: python3 file_name.py Please have in mind that our Python SDK structure has only one executable .py file (main file) and that one imports all other files as modules. For example, the NDEF Python SDK console uses ndef_example.py as the main file, so the software is executed with the following command: python3 ndef_example.py To make sure which file is the main executable file, you can simply check the source code of the *.py files and look for the one that has a ReaderOpen/ReaderOpenEx function calls.   NOTE: This test was performed with Python 3.7.2 so and included the following SDK:     https://code.d-logic.com/nfc-rfid-reader-sdk/ufr-ndef-examples-python-console     https://code.d-logic.com/nfc-rfid-reader-sdk/ufr-mf-examples-c

How to communicate with µFR device on Windows without FTDI drivers implementation

How to use the µFR device on Windows without the FTDI drivers implementation: You can avoid using FTDI drivers (D2XX) by communicating with the reader via

µFR Device RF settings – reset to default

µFR Series devices installation on Linux distributions

ReaderHWReset function returns a 0x0F error code (UFR PARAMETERS ERROR) – Android Library Issue

Configure Raspbian for Raspberry Pi 3 to use Digital Logic shield with uFReader RS232

How to set the µFR Card Formatter software to configure the access bits and security keys for each sector of a MIFARE 1K card

µFR Card Formatter GUI displays the entire MIFARE Classic 1K structure with simple access to all its sectors and blocks ( 16 sectors of 4 blocks). The first block (block zero) contains the card factory UID, ad it is read-only by default.

Mifare® structure – card programming help

Is SUN Mirroring NT4H tag available with uFR devices?

How to integrate the NFC reader to the web based management system via browser?

µFR NFC Reader library for Android devices

Is the development of NDEF commands (eg reset/clear commands) support NT4H planned?

Use the NDEF methods with the NT4H on µFR Nano reader (eg erase_all_ndef_records) – NDEF_UNSUPPORTED_CARD_TYPE status message

How to use the NDEF methods with the NT4H (e.g. erase_all_ndef_records) on µFR Nano reader if you get an NDEF_UNSUPPORTED_CARD_TYPE status?

Configure Raspbian for Raspberry Pi 3 to use Digital Logic shield with µFR Series RS232 devices

µFR Nano TTL connection

Windows PS/CS driver for µFR Series devices

Is there any µFR Series device that is addressed directly via the USB interface and javax.smartcard?

Which devices belong to the μFR series?

Is there any simple console application example for continuous reading?

Is there any SDK for C # .NET Core 3.1?

How to avoid Virtual COM port and FTDI drivers implementation on Windows OS?

Card reading distance issue

Which firmware to use on a device with a SAM slot?

Which software to use for getting the credit card PAN and all public data?

What is the purpose of RTC and EEPROM upgrade for µFR device?

Embedded RTC Some projects require accurate current time instead of relying on the PC system time or the host time. Accepting the time from these sources bears a potential risk because it can be changed on purpose, causing a potential system vulnerability and security issues. For this reason, the readers’ built-in RTC module ensures accurate timekeeping without any influence from its environment. The time set for the reader can be modified with password authentication only. Embedded EEPROM User EEPROM is part of non-volatile memory for storing small amounts of important data, such as license keys and similar. It is also a password-protected area: a valid password is required for writing data into that area. The data reading is also available with a provided password only. This feature is very convenient for the device integration with the custom made software, or another complex project.

How to integrate Digital Logic hardware into other devices and systems like PLCs and embedded boards

Find out how to integrate Digital Logic NFC RFID hardware into other devices and systems PLCs and embedded boards...

Is NFC RFID reader rebranding possible?

Some of the Digital Logic products are already available with customizable cases/housing, while the OEM versions are not branded as a final product. For more details on how to brand the specific device, please, contact our customer support.  

Can µFR devices be used in OpenWRT projects?

OpenWRT (OPEN Wireless Router) is an open-source project for embedded operating systems based on Linux, primarily used on embedded devices to route network traffic. The application of µFR Series devices in OpenWRT projects has not yet been tested. Since these devices have full support for Linux and Linx based environments (eg Raspberry Pi, BeagleBone, etc), the implementation on OpenWRT should theoretically be easy to achieve. Even though the MIPS libraries were not compiled yet, the ARM and x86 libraries can be used for these projects’ development. Find out more on https://dev.openwrt.org/wiki/platforms. 

Do the Digital Logic readers support P2P (Peer To Peer)?

The P2P (Peer To Peer) function for Digital Logic devices is not yet fully developed. Follow our News Blog to keep up to date with our project processes and new releases.

Does any Digital Logic device support 125Hz tags?

Is the library for ARM architecture (for Linux on the Raspberry Pi) available?

Among others, µFR Series SDK includes the libraries for the ARM processors. Please, check all available support below. µFR Series libraries µFR Series libraries are available for the following platforms: Windows 32 and 64 bit (static and dynamic) Windows ARM Linux 32 and 64 bit (dynamic only) Linux ARM and ARM-HF (dynamic only) Mac OSX 32 and 64 bit (dynamic only) iOS 64 bit (static only). Download libraries GitLab repository https://code.d-logic.com/nfc-rfid-reader-sdk/ufr-lib Implementation Find more details in the µFR Series API reference. For quick insight and functions’ prototypes, check  the/include/ufCoder.h header file. Requirements µFR Series device. Notice These libraries are specific to the listed hardware ONLY.  There is no guarantee that they might be functional with any other hardware.

Can Digital Logic devices read-write Mifare Ultralight ®, Mifare Ultralight® C, Mifare Ultralight® EV1 cards/tags?

Currently, most Digital Logic devices support Mifare Ultralight® cards/tags. Mifare Ultralight® C is supported in compatibility mode (as standard Ultralight®). The support for Mifare Ultralight® EV1 cards/tags is still in development. Please, check the selected hardware features table for the details on all supported cards/tags.

Is it possible to use Digital Logic tools to duplicate the Vigik tag?

Is it possible to use Digital Logic tools to duplicate a Vigik® tag? MIFARE Classic® 1K or MIFARE Ultralight® chips are integrated into Vigik