COMPRION introduces their new product line for NFC development testing that helps identifying and resolving error causes in NFC communication at an early stage.
On the Embedded World, February 27 – March 1, in Nuremberg, COMPRION – a provider of test solutions – is going to launch their latest product line for NFC testing, the CL Development Line. It can be used for validating the interface design, for preparing the certification, for functional testing, and for verifying interoperability.
NFC problems? Do they still exist?
You could think that a technology like NFC which is not brand-new would meanwhile work smoothly. “But that’s not the case!” says Dr. Michael Jahnich, Development Head for NFC Test Solutions at COMPRION. “We observe recurring problems in the field.“
This has four main reasons: First of all, the market is inundated with new NFC devices and applications. Technologies are melting together. This results in a great number of NFC devices that have not been tested according to universal standards. Secondly, the standards often do not cover everything, because the NFC application demands conformance to its own specifications. Thirdly, closed and in itself functioning NFC systems like, for example, access control or contactless payment are extended by use of the smartphone. This can cause interoperability issues. Finally, when individually tested NFC modules are integrated, for example, into car door handles, terminals, or machines, the used materials may interfere with sensitive NFC fields.
Early testing wins half the battle
“Many of these problems could become real showstoppers and cause expensive recalls. This can be avoided by testing early in the development phase,“ explains Jahnich.
The new CL Development Line has been especially designed for NFC development testing and can be used in the following areas:
What’s the solution like?
The CL Development Line is a modular system consisting of different hardware and software components as well as unique antennas and accessories that can be configured to match the particular test case. “You don’t pay for software and features that you don’t use, but only for those that you actually need. On the other hand, the system can also be extended by adding further components so that you can cover other application areas,“ Jahnich is glad.
There is a way to minimize this risk of fatal accidents caused by sensors, actors, or tags connected to each other via the IoT
You’re using TraceCase to sniff into payment transactions in the field, but you’re faced with incomplete or faulty traces that are not helpful. The...