Overview This reference design of a 3-phase Permanent Magnet Synchronous Motor (PMSM) sensorless vector control drive and a Brushless DC (BLDC) Motor drive without position encoder coupled to the motor shaft uses the NXP® 56F8013 with Processor Expert® software support. PMSM/BLDC motor are excellent choices for many appliances and industrial applications that require low cost and high-performance variable speed operation This design will employ sensorless FOC to control a PMSM and a sensorless algorithm to control BLDC The hardware design supports both motor types with the algorithms fully implemented digitally via software running on the 56F8013 DSC Features General: For PMSM the motor control algorithm employs Field-Oriented Control (FOC). The power stage switches are controlled by means of Space Vector Pulse Width Modulation (SVPWM) The feedback hardware elements are limited to the motor stator phase currents and the bus voltage. No position information devices or stator flux measurement are used; sensorless speed methods are employed The Motor is capable of forward and reverse rotation and has a speed range of 500rpm to 6000rpm The user controls motion profiles, rotation direction, and speed. The RS-232 communication supports further R&D by enabling the easy tuning of control parameters The motor drive system is designed to create minimal acoustic noise Active power factor correction which reduces the negative effects of the load on the power grid in conducted noise and imaginary power Design is low cost General Benefits: Improved End System Performance Energy savings Quieter operation Improved EMI performance System Cost savings Enhanced Reliability Performance: Input voltage: 85 ~265VAC Input frequency: 45 ~65HZ Rating bus voltage: 350V Rating output power: 500W Switch frequency of PFC switch: 100KHZ Switch frequency of inverter: 10KHZ Power factor: >95% Efficiency: >90% Communications: RS232 port for communication with optoisolation Visual Interface: Multi-segment LED indicators Block Diagram Board Design Resources

Overview To improve performance in industrial drives, Field Oriented Control (FOC) is an advanced technique used for Permanent Magnetic Synchronous and other motor types. This reference design jump-starts your ability to leverage the NXP® DSCs' advanced feature sets via complete software, tools and hardware platform. Features Bi-directional rotation Application speed ranges from 0 to 100 percent of nominal speed (no field weakening) Four state machine Fault protection for driver DC-bus overcurrent, SW overcurrent, overvoltage and over speed Current control loop execution time: 17 us @ 100 MHz MCU speed PMSM vector control using the quadrature encoder Block Diagram Design Resources

Overview This application creates a vector control PMSM drive with optional speed closed-loop using a quadrature encoder, and serves as an example of a PMSM vector control system design based on the cost-effective 32-MIPS NXP® digital signal controller MC56F80XX. Dedicated algorithms such as transformations, PI controllers and space vector modulation, are implemented using NXP’s Motor Control Library This cost-effective and highly reliable solution minimizes system cost, as the algorithm implements a single shunt current sensing, reducing 3 current sensors to one The reference manual provides a detailed description of the application, including the design of the hardware and the software Features Designed to fit into consumer and industrial applications Uses 56F8013 or 56F8023 32 MIPS Digital Signal Controller Running on a 3-phase High Voltage Power Stage Vector control of PMSM using theQuadrature Encoder as a position sensor Control technique incorporates: Vector control with speed closed-loop with position encoder Rotation in both direction Start from any motor position with rotor alignment 4-quadrant operation Reconstruction of three-phase motor currents from DC-Bus shunt resistor Wide speed range FreeMASTER Control Interface Fault protection - overcurrent, overvoltage, undervoltage Block Diagram Board Design Resources

Overview This reference design deals with the average current mode control of Power Factor Correction (PFC) on the NXP® MC56F8013 digital signal controller (DSC). The application is written for MC56F8013, but can be easy ported into the other members of the MC56F80xx family according to application requirements Both fast current and slow voltage loops are implemented digitally using the DSC and the PFC power switch is controlled directly by the DSC Using direct PFC, we can achieve much better dynamics of the system so the solution is cost-effective The example of such PFC implementation into 3-phase single shunt ACIM vector control is described in this reference design Features Inner current loop Outer voltage loop Direct PFC algorithm Average current control mode 230VAC Input voltage FreeMASTER control interface Part of the system together with HV AC/BLDC Power Stage dedicated for Motor Control Applications Maximal output power 750W Fault protection: Input over-current fault protection Input under-voltage fault protection Input over-voltage fault protection DC-Bus under-voltage fault protection DC-Bus over-voltage fault protection Block Diagram Board Design Resources

Overview This thermostat reference design is an example of how a thermostat can be built taking advantage of the features of the NXP® MC9S08LL MCU, which has a very flexible LCD module that allows driving an 8x24 LCD and power saving modes while keeping track of the time and the LCD information and a 12-bit analog to digital converter. Features Low-power battery (2 AA) operation Small Glass (2-4 uA) Large Glass (7-9 uA) Support for two LCD displays 8x24 mode for greater flexibility 2x26 mode optimized for lowest power Standard HVAC connectivity Temperature sensors Programmable heat/cool temp Block Diagram Board Design Resources

Overview This reference design exhibits the suitability and advantages of the NXP® 56F80x and 56F83XX Digital Signal Controllers (DSCs) for torque control applications using a 3-phase PMSM motor with an encoder position sensor. It can also be adapted to 56F81XX Digital Signal Controllers PM synchronous motors are popular in a wide application area The PM synchronous motor lacks a commutator and is, therefore, more reliable than the DC motor The PM synchronous motor also has advantages when compared to an AC induction motor Features Targeted 56F80X, 56F83XX, and 56F81XX Digital Signal Controllers Torque producing current component closed loop Vector current control with position feedback Encoder position feedback Overvoltage, undervoltage and overcurrent fault protection FreeMASTER display interface Manual interface Block Diagram Board

Hi: This thread mainly introduces how to sample multi channels ADC with DMA. The slides is in Chinese. For different MCU family, Kinetis & LPC has different ADC & DMA system. There takes KE15 & LPC51U68 for example, introduce how to enable various ADC & DMA trigger solution. 1.KE15:Three sample projects include: 1.1 LPIT HW trigger ADC & DMA transfer, enable interrupt for get ADC value; 1.2 LPIT HW trigger ADC & DMA transfer, DMA will automatically trigger next transfer; 1.3 Software trigger multi-ADC & DMA transfer;  2.LPC51U68: Two sample projects include: 2.1 Software trigger multi-ADC & DMA transfer;  2.2 SCT HW trigger ADC & DMA transfer, DMA will automatically trigger next transfer; Products Product Category NXP Part Number URL MCU KE15 Arm Cortex-M0+|Kinetis KE1xZ 32-bit 5V MCUs with Touch Interface | NXP  MCU LPC51U68 LPC51U68 | NXP  MCUXpresso SDK Software NXP standard SDK Welcome | MCUXpresso SDK Builder    Tools NXP Development Board URL FRDM-KE15Z Freedom Board FRDM-KE15Z Platform|Freedom Development Board | NXP  LPCXpresso51U68 board LPCXpresso51U68 board for LPC51U68 MCU | NXP 

The attached document describes how to optimize LCD display performance on RT10xx platform. The content include RT10xx configuration and Emwin setting with LCD parameters. Products Product Category NXP Part Number URL MCU i.MX RT1060 i.MX RT1060 MCU/Applications Crossover MCU | Arm® Cortex®-M7, 1MB SRAM | NXP  MCU i.MX RT1050 i.MX RT1050 MCU/Applications Crossover MCU| Arm® Cortex-M7, 512KB SRAM | NXP  SDK Software Software Development Kit https://mcuxpresso.nxp.com/en/select    Tools NXP Development Board URL MIMXRT1060-EVK i.MX RT1060 Evaluation Kit | NXP  MIMXRT1050-EVK i.MX RT1050 Evaluation Kit | NXP  Was this helpful to you?

       由于RT系列没有内置 Flash，大多数用户会选择外部 QSPI Flash 作为应用代码和数据的非易失存储设备，同时外部Flash的大容量在满足用户代码存储需求之外也会为用户提供了足够的灵活空间存储应用数据，但是其中涉及到的对数据读擦写以及用户的应用程序均需要在外部 Flash 执行，这为 Flash 的操作带来了麻烦。        对于在XIP（eXecute-In-Place）模式下的应用，对Flash读擦写的操作需要在内部 RAM 里执行，而RT系列由于高主频而引入了内核 Dcache 以及 Flexspi 模块自带的 Pre-fetch 功能，对外部 Flash 的操作会有很多需要注意的地方，这些问题在带有 RTOS 的系统里则更是突显出来，而无论在 XIP 模式下的裸机还是基于 RTOS 方式对 Flash 的操作，SDK 里均没有提供例程可供参考。        本参考方案来自很多客户的实际应用需求，所以编写了基于 FreeRTOS 下的对片外 QSPI Flash 的读擦写操作，客户可以基于此例程移植到自己的应用里面做相关的应用开发，并配套对应的指导文档提醒用户在移植过程中需要注意的几个常见的 tips。 Products Product Category NXP Part Number URL MCU MIMXRT1021 i.MX RT1020 Crossover MCU with Arm® Cortex®-M7 core MCUXpresso SDK Software SDK v2.6.1 Welcome | MCUXpresso SDK Builder    Tools NXP Development Board URL MIMXRT1020-EVK MIMXRT1020-EVK: i.MX RT1020 Evaluation Kit

Overview    This demo uses the i.MX RT600 EVK (MIMXRT685-EVK) with a GUI software to playback MP3 files. An equalizer can be switch on to demonstrate the HiGi-4 audio DSP. Beside the board itself it requires a SD-card with MP3 music tracks and a portable speaker or headphone.    The i.MX RT600 is a crossover MCU family optimized for 32-bit immersive audio playback and voice user interface applications combining a high-performance Cadence® Tensilica® HiFi 4 audio DSP core with a next-generation Cortex-M33 core. The i.MX RT600 family of crossover MCUs is designed to unlock the potential of voice-assisted end nodes with a secure, power-optimized embedded processor. Demoing Guide No software installation required to demo this board. To build this demo, pls. refer to the description at the end of this guide. Insert the SD-Card with mp3 files to on-board SD Card connector, not to the one below the LCD board Connect headphones or external speakers to the 3.5mm jack Line Out (J4) Supply the board through Micro-USB connector (J5) in the upper right edge Three main windows/tabs on the GUI: File playback This screen shows: • Album artwork/NXP logo • Current track information (title, artist, album) • Media controls (prev, play/stop, next) • Volume slider Playlist This screen shows: • Playlist information from mp3 files found in SD card • A track for playback can be selected by touching the line Spectrum visualizer This screen shows: • Seven vertical bars showing the frequency spectrum of the current track being played. • Button for toggling Equalizer On/Off o if on the sound is AM radio style Products i.MX RT600 Evaluation Kit | NXP 

The KW36/35/34 is an ultra-low power, highly integrated single-chip family that enables Bluetooth Low Energy version 5 and Generic FSK (at 250, 500 and 1000 kbps) connectivity for automotive, industrial and medical embedded systems. KW36/35/34 integrates an Arm ®  Cortex ® -M0+ CPU, up to 512 KB Flash and 64 KB SRAM, Bluetooth LE and Generic FSK hardware Link Layers and peripherals optimized to meet the requirements of the target applications. KW36/35/34 supports up to 8 simultaneous Bluetooth LE connections as either a master, a slave or any combination. The KW36 includes an integrated FlexCAN module enabling seamless integration into an automotive or industrial CAN communication network. The FlexCAN module can support CAN’s flexible data-rate (CAN FD) protocol for increased bandwidth and lower latency. The Kinetis KW36A/35A/34A MCUs feature AEC Q100-Grade 2 temperature range qualification while the KW36Z/35Z feature and Industrial qualification. As more and more car OEM are considering to use phone as the car key, which need to localize the driver’s position, most customers prefer to use RSSI based solution as it can be supported by current phone directly, while PDE and AOA is not compatible with current phone. Common RSSI Localization method is acquiring advertising channels, It’s easy, but it is hard to make authentication, can be attacked easily and have low anti-interference ability as it only have 3 channels. So customers are asking for a new method to monitor the data channels with hopping. This demonstration system implement data channel’s RSSI tracing and monitoring of 4 BLE connections at the same time, and designed a GUI to simplify the steps to setup the demo system, and view the result visually.

  JN51xx Flash Programmer可以支持NXP JN516x，JN518x全系列Zigbee SoC的程序烧写。通过多端口USB Hub，支持8路芯片同时烧写，可用于小规模量产烧写。这是一个绿色工具，无需安装即可运行。 JN51xx Flash Programmer只支持FT232 USB to UART串口转换接口芯片，具体信息可以参考JN-RM-2065文档。 使用时先选择芯片系列和需要烧写的Firmware固件，执行”Program Flash”即可。 提供JN51xx UART ISP通信协议源代码。

电容式感应触摸按键可以穿透绝缘材料外壳，准确无误地侦测到手指的有效触摸。并保证了产品的灵敏度、稳定性、可靠性等不会因环境条件的改变或长期使用而发生变化，并具有防水和强抗干扰能力，超强防护，超强适应温度范围 电容式触摸按键控制芯片通常广泛适用于遥控器、灯具调光、各类开关以及车载、小家电和家用电器控制界面等应用中。芯片内部集成高分辨率触摸检测模块和专用信号处理电路，以保证芯片对环境变化具有灵敏的自动识别和跟踪功能。芯片还必须满足用户在复杂应用中对稳定性、灵敏度、功耗、响应速度、防水、带水操作、抗震动、抗电磁干扰等方面的高体验要求。本文将介绍一套基于NXP KE16Z64的轻量级TSI算法。 基于KE1XZ64平台的TSI轻量级算法： KE1XZ64继承了KE family的高可靠抗干扰性，并提供了更小的引脚封装尺寸，让客户硬件设计更加便利。其内部集成了改进版的TSI模块，性能更加稳定可靠，该模块支持自耦和互耦两种方式：自耦模式下最多可支持25个按键，互耦模式最多可支持36个按键，因此能够覆盖当前市场上绝大部分的触摸应用场景。 NXP官方的NT LIB软件虽然功能完善，但由于代码量大且程序架构复杂等原因，部分客户不愿意选用。所以该市场对于轻量级应用代码还是有需求的。 此参考设计展示了TSI轻量级算法的具体实现，按照配置模式分为两个对应的参考例程：自耦模式为12个按键的功能实现，硬件基于KE16 PCB，主要适用于按键所需数目少的应用场景；互耦模式为36个按键的功能实现，硬件基于RT-TSI-KE16，主要适用于按键所需数目多的应用场景。该算法精简可靠，十分易于移植，使客户可以很快地上手。并且可以结合使用NXP的GUI监测软件FreeMaster，方便中后期的灵敏度调试及问题追踪。 此套算法在实验室通过了IEC61000-4-6注入电流可靠性测试。 参考代码及说明文档请详见附件压缩包。

LS104x DPAA Support PCD in Linux Kernel Products Product Category NXP Part Number URL MPU LS1043A https://www.nxp.com/products/processors-and-microcontrollers/arm-processors/layerscape-communication-process/qoriq-layerscape-1043a-and-1023a-multicore-communications-processors:LS1043A MPU LS1046A https://www.nxp.com/products/processors-and-microcontrollers/arm-processors/layerscape-communication-process/qoriq-layerscape-1046a-and-1026a-multicore-communications-processors:LS1046A LSDK Software Layerscape Software Development Kit https://www.nxp.com/design/software/embedded-software/linux-software-and-development-tools/layerscape-software-development-kit:LAYERSCAPE-SDK Tools NXP Development Board URL LS1043ARDB https://www.nxp.com/design/qoriq-developer-resources/layerscape-ls1043a-reference-design-board:LS1043A-RDB LS1046ARDB https://www.nxp.com/design/qoriq-developer-resources/layerscape-ls1046a-reference-design-board:LS1046A-RDB

This is a quick video for demonstration purposes of the i.MX RT1060 Evaluation Kit capability for running an Embedded Wizzard GUI application and a Neural Network Model as an inference engine.

使用NXP集成丰富的模拟外设和数字接口，针对成本敏感，低功耗电池供电应用场景应用的K32 L2B系列，可以实现额温测量的应用。其具有如下特性： 1. 集成多通道16-bit ADC，可用于采集红外温度传感器的信号，以及采集电池电压，目前K32L2B的16位单端模式精度可以达到13.9位，差分模式可以达到14.5位，使用芯片内置的ADC就可以满足要求，实现0.1度温度测量精度要求。 2. 12-bitDAC为外置运放提供偏置电压；可以节省一颗外部的3V转1.2V电平转换芯片或者外围分离器件搭建的降压转换电路（由于运放的偏置电路消耗电流只需要uA级，目前片内的一路DAC可以满足此要求）。另外Vref 该引脚可以内部输出1.2V参考电压，带载能力也可达1mA。 3. sLCD：低功耗段码显示支持24x8或者28x4段，sLCD引脚既可以做Segment，也可以做COM口的功能，即使未配置为sLCD的引脚也可以做其他IO功能控制口。 4. 3路I2C(其中的2路I2C中一路接红外数字传感器或者接近传感器，另外一路接高精度数字温度传感器，可外接NXP PCT2075温度传感器芯片，还有预留的1路I2C用FlexIO实现标准的I2C或者UART或者SPI通信) 。 5. 2路PWM用于驱动LED指示LED或者蜂鸣器报警信号，以及实现语音播放功能。 6. USB FS 2.0从设备接口，不要额外的晶体。 7. 支持最大256K Flash，48 MHz Arm® Cortex®-M0+内核。K32L2B11VLH0A 64K Flash，32K RAM的配置即可满足额温枪的需要。 8. 低功耗特征：运行模式达 54 uA/MHz，在深度睡眠模式下RAM和RTC处于保持状态的功耗为1.96uA；满足采用采用电池供电的手持式红外测温枪，对系统功耗苛刻的要求。 9. 具有小于10us的快速唤醒模式，能及时唤醒主控进入运行模式。 10. 64 LQFP封装, 至少提供5个GPIOs满足用户人机界面设置按键需求。如果是做额温测试模块外接高端i.MX系列带大屏幕彩色显示屏的应用，可以选择32脚封装，例如K32L2B11VFM0A。 11. 额温枪对Flash容量大小的需求，主要是NTC（RT电阻温度换算表）和红外测温（VT电压温度换算表）标定参数存储，语音播报数据的存储，64K Flash是可以满足要求的。 12. K32 L2B系列具有广泛的产品路线图，支持引脚功能完全兼容，扩展的Flash，可以添加诸如蓝牙以及二维码扫码等新型扩展功能需求。 13. 内置ROM bootloader方便用户程序在线升级和温度参数标定，内置高精度的内部时钟，此功能用于工厂固件生产配置，使用NXP提供的Kinetis Flash Tool下载工具软件 GUI，可以直接方便的通过USB刷新固件和校准配置参数，无需额外的仿真下载调试工具。 14. MCUXpresso ConfigTool：易用的软件配置工具以及完整的外设驱动SDK包方便用户快速原型开发。 目前64脚的IO资源已经用足，所以做额温枪，使用集成段码显示的单芯片，64脚封装应该是主流。当然也有48或者32脚的产品，一般都是需要外置sLCD显示驱动芯片。 基于NXP K32L2B MCU的额温枪参考方案(硬件篇)： https://mp.weixin.qq.com/s/k96HO32ek2i_FjADtdsK9g 基于NXP K32L2B MCU的额温枪参考方案(软件篇)： https://mp.weixin.qq.com/s/QVCeW1RS57tAYaDi8mQ7Lw

Hi:    In industrial application, high RS485 Bus requires more real time performance, possible higher throughput. Normally in NXP MCUxpresso SDK, it provides basic sample codes to demonstrate UART, DMA peripherals usage, but not RS485. Though enough driver API could support such applicatio. But for newbie or fast prototype requirement, it's hard to build it in short time. This design show how to use DMA for RS485 application, and how to use UART "Smart" Features to implement high throughput.

Overview During critical processes, an industrial diesel engine management system that includes an electric generator can supply emergency power to all vital and selected loads as desired. Today, most state-of-the-art- hospitals, manufacturing plants, telecommunications organizations, data centers, emergency facilities, large industries, and mining companies require uninterrupted power and have backup diesel engine generators that are reliable. As shown in the block diagram, NXP provides a full range of MCUs, barometric pressure sensors (BAP), and analog/mixed-signal IC drivers for improving diesel vehicle fuel economy, enhancing performance, and meeting emissions requirements in automotive applications. However, the NXP industrial diesel engine management solution is equally applicable in other industrial applications by changing the input sensors and outputs that require control. The NXP Industrial diesel engine management solution incorporates the MPC5777C Power Architecture® MCU that delivers advanced performance, timing systems, security, and functional safety capabilities. This includes a lockstep function that serves as a watchdog function to flag any problems with the MCU, support for advanced timers and ADCs, external memory, fault detection, and handling support, and the highest functional safety standards (ASIL-D) support. Together, this solution provides a reliable and high-performance solution to ensure your customers and their employees are safe. Block Diagram Recommended Products Category Link MCU MPC5777C|Engine Control MCU | NXP  Safety Power Management MC33905 | SBC Gen2 with High-Speed CAN and LIN | NXP  Physical Interface TJA1021 | LIN2.1/SAE J2602 Transceiver | NXP  Output Driver MC33800 | Engine Control Integrated Circuit | NXP  Motor Driver H-Bridge MC33931 | H-Bridge Motor Driver | NXP  MAP Sensor 20 to 105kPa, Absolute, Integrated Pressure Sensor | NXP  BAP Sensor -115 - 115kPa Gauge, Absolute Pressure Sensor | NXP  Injector Driver MC33810 | Automotive Engine Control IC | NXP  Input Signal and Sensor Interface MSDI | NXP 

This guide is intended as a reference for creating a demo application using the SLN-VIZN-IOT kit. In this guide, we will be constructing a demo e-lock application using the SLN-VIZN-IOT kit for secure face recognition using liveness detection/anti-spoofing. If you haven’t already, be sure to check out the Getting Started Guide for the SLN-VIZN-IOT kit here. Build Process Our e-lock design will make use of GPIO_AD_B0_2 and GPIO_AD_B0_03 to drive an H-Bridge circuit which actuates a lock using a 9-volt battery. These pins (and our ground) can be found on the serial header located on the front of the kit as shown below: To build our e-lock, we will be modifying the sln_vizn_iot_userid_oobe application found in the SLN-VIZN-IOT SDK. Instructions for downloading the SDK and importing the userid_oobe application can be found in the ‘Get Software’ and ‘Build and Run’ sections of the Getting Started Guide. The following video shows the modifications necessary to implement the E-Lock demo using the sln_vizn_iot_userid_oobe project To enable these pins as GPIOs, we must modify pin_mux.h and pin_mux.c found under the board folder. For simplicity, we contained these initializations in a function called BOARD_InitDoorLockPins. The code to enable these pins was generated using MCUXpresso’s integrated Config Tools, although this is not necessary. The MCUXpresso Config Tools can be read about in-depth here. Next, we need to make sure that the BOARD_InitDoorLockPins function we just created actually gets called so that the GPIOs will work the way we want them to. To do this, we will add the function call inside of our main function in main.c. After adding the door lock initialization to main, we will modify sln_system_state.cpp found under the source folder to add the code which will toggle the GPIO’s we setup in the previous step. To do this, we will make use of the GPIO_PinWrite function found in “fsl_gpio.h.” Using this function requires us to add the line “#include fsl_gpio.h” at the top of sln_system.cpp like shown below: The GPIO_PinWrite functions here will be used to unlock the door whenever a face is recognized (sysStateDetectedKnownUser) and lock the door whenever no known users are in view of the camera (sysStateDetectedNoUser). With the software modifications complete, we need to compile the code and flash our kit with the updated firmware. This can be done by using the ‘Debug’ option found in the Quickstart Panel as shown below. Make sure that the project is compiled and flashed is the sln_vizn_iot_userid_oobe project by verifying the name of the project shown at the top of the Quickstart Panel. For more detailed instructions about flashing the SLN-VIZN-IOT, check out the Flash and Debug SLN-VIZN-IOT Project section under Build, Run in the Getting Started Guide.  With the software modifications complete and the updated firmware installed, all that’s left to do is to add some wires from the GPIO pins to the door lock and power on the kit. Now our e-lock is ready to go! When a user with an unrecognized face (indicated by a red LED) tries to turn the handle nothing happens.  But when a user with a recognized face (indicated by a green LED) tries to turn the handle, the lock is disengaged allowing the latch to move. Conclusion With just a few lines of code and some external hardware, we were able to create a fully-functioning face-controlled e-lock that works entirely offline just by using the SLN-VIZN-IOT. Not to mention the fact that there was no need for any ML experience whatsoever. Because the SLN-VIZN-IOT was designed with flexibility in mind, all sorts of use cases can be supported with only minimal effort when compared to a face recognition implemented from scratch. By using the production-ready software that comes provided with the kit, it’s now possible to add local (no cloud connectivity necessary) face and emotion recognition capabilities to all sorts of products in record time. We hope this guide was helpful in showing you how to jumpstart your face recognition project with the power of the SLN-VIZN-IOT. 

Overview OM27462NBR is a battery operated easy-to-use smart lock demonstrator kit for hospitality door access applications. The door operates by exchanging and verifying door access tokens via NFC and Bluetooth Low Energy. The design incorporates NXP ®  PN7462 first all-in-one full NFC Controller and the ultra-low-power Bluetooth Low Energy system-on-chip QN9021. The hardware is designed for low-power operation using a CR2 battery and features intelligent sleep and wake-up logic via Bluetooth Low Energy and a touch sensor using NXP capacitive touch sensor IC PCF8883. The Bluetooth ®  word mark and logos are registered trademarks owned by Bluetooth SIG, Inc. and any use of such marks by NXP ®  Semiconductors is under license. OM27462NBR Kit Content OM27462NBR Full Kit Content OM27462NBR Module   Specifications Power Management Battery operated Wireless NFC and Bluetooth Low Energy design and operation Token concept Access token exchange and validation ECDSA token signature verification Smart card, Bluetooth Low Energy, and NFC via HCE token exchange Support MIFARE® DESFire® support Android™ app available in Google Play™ Store Ready to use Documents and Software User manual and Quick Start Guide are attached to this document