Experience the future of data capture with our barcode scanner, where precision and speed drive operational excellence
A
A
Hardware Overview
How does it work?
Barcode 2 Click is based on the EM3080-W, a barcode decoder chip that delivers superior performance and solid reliability with low power consumption from Newland Auto-ID Tech. Co., Ltd. This barcode scanner module is designed to quickly scan the barcode or QRcode data and send the information to the host MCU or PC. It features excellent near-field reading, wide-viewing angle, and snappy reading; it also offers stunning performance in decoding poor-quality and damaged barcodes. The advanced technology incorporated in the EM3080-W helps reduce its power consumption and prolong its service life. The EM3080-W scanner module uses a flat cable to connect to the Click board™ via the FPC Connector located on the top side of the PCB. This flat cable carries all the signals between the EM3080-W module and the host MCU, such as the RX, TX, buzzer, USB, LED, reset, and scanning trigger lines. Barcode 2 Click communicates with MCU using the UART interface at 9600 bps as its default communication protocol, but it is also
equipped with a micro USB port; thus, it can work both as a standalone device and a standard Click board. When the Click board™ is placed into the mikroBUS™ socket, it can exchange data via the standard mikroBUS™ RX and TX pins. Additional functionality, Reset and Scan Trigger push-buttons are provided and routed at RST and PWM pins of the mikroBUS™ socket labeled as RST and TRG used to control the device when working as a standalone device. Both lines, alongside the EM3080-W scanner module, are powered with TLV70033DDCT, low IQ LDO, which at its output gives a voltage of 3.3 V, and which at its input can receive a 5V from mikroBUS™ or can be powered from the micro USB connector. This Click board™ also features the CMT-8540S-SMT magnetic buzzer controlled by the EM3080-W for audible signalization and notification. You can create different sound patterns using the Sound library supported in our compilers. Signal frequency determines the sound pitch, and the duty cycle determines the amplitude (sound volume).
Pressing the onboard TRIG button or pulling the PWM pin of the mikroBUS™ to a LOW logic level for at least 10ms will trigger the barcode scan. A short beep sound and the Barcode Detection LED Indicator (GR) blink will indicate a successful barcode decoding. After releasing the TRIG line, the device will send the decoded information to the selected interface. The RST button is used to reset the device. Pressing the RST button or pulling the RST line to a LOW logic level for 100us to 500us will cause a device reset, followed by the greeting message sound. It should be noted that the device should not be reset too frequently; at least 2 seconds delay should exist between the reset cycles. This Click board™ can be operated only with a 5V logic voltage level. The board must perform appropriate logic voltage level conversion before using MCUs with different logic levels. Also, it comes equipped with a library containing functions and an example code that can be used as a reference for further development.
Features overview
Development board
Arduino UNO is a versatile microcontroller board built around the ATmega328P chip. It offers extensive connectivity options for various projects, featuring 14 digital input/output pins, six of which are PWM-capable, along with six analog inputs. Its core components include a 16MHz ceramic resonator, a USB connection, a power jack, an
ICSP header, and a reset button, providing everything necessary to power and program the board. The Uno is ready to go, whether connected to a computer via USB or powered by an AC-to-DC adapter or battery. As the first USB Arduino board, it serves as the benchmark for the Arduino platform, with "Uno" symbolizing its status as the
first in a series. This name choice, meaning "one" in Italian, commemorates the launch of Arduino Software (IDE) 1.0. Initially introduced alongside version 1.0 of the Arduino Software (IDE), the Uno has since become the foundational model for subsequent Arduino releases, embodying the platform's evolution.
Microcontroller Overview
MCU Card / MCU
![default](https://dbp-cdn.mikroe.com/catalog/mcus/resources/ATmega328P.jpeg)
Architecture
AVR
MCU Memory (KB)
32
Silicon Vendor
Microchip
Pin count
28
RAM (Bytes)
2048
You complete me!
Accessories
Click Shield for Arduino UNO has two proprietary mikroBUS™ sockets, allowing all the Click board™ devices to be interfaced with the Arduino UNO board without effort. The Arduino Uno, a microcontroller board based on the ATmega328P, provides an affordable and flexible way for users to try out new concepts and build prototypes with the ATmega328P microcontroller from various combinations of performance, power consumption, and features. The Arduino Uno has 14 digital input/output pins (of which six can be used as PWM outputs), six analog inputs, a 16 MHz ceramic resonator (CSTCE16M0V53-R0), a USB connection, a power jack, an ICSP header, and reset button. Most of the ATmega328P microcontroller pins are brought to the IO pins on the left and right edge of the board, which are then connected to two existing mikroBUS™ sockets. This Click Shield also has several switches that perform functions such as selecting the logic levels of analog signals on mikroBUS™ sockets and selecting logic voltage levels of the mikroBUS™ sockets themselves. Besides, the user is offered the possibility of using any Click board™ with the help of existing bidirectional level-shifting voltage translators, regardless of whether the Click board™ operates at a 3.3V or 5V logic voltage level. Once you connect the Arduino UNO board with our Click Shield for Arduino UNO, you can access hundreds of Click boards™, working with 3.3V or 5V logic voltage levels.
Used MCU Pins
mikroBUS™ mapper
Take a closer look
Schematic
![Barcode 2 Click Schematic schematic](https://dbp-cdn.mikroe.com/catalog/click-boards/resources/1ee790a5-6545-65b4-b2c5-0242ac120009/schematic.webp)
Step by step
Project assembly
Track your results in real time
Application Output
After loading the code example, pressing the "DEBUG" button builds and programs it on the selected setup.
![Application Output Step 1](https://dbp-cdn.mikroe.com/cms/shared-resources/1eed554e-d80f-6694-8cb9-02420a000272/AP-Step1.jpg)
After programming is completed, a header with buttons for various actions available in the IDE appears. By clicking the green "PLAY "button, we start reading the results achieved with Click board™.
![Application Output Step 3](https://dbp-cdn.mikroe.com/cms/shared-resources/1eed5550-3c0f-6800-a19f-02420a000272/AP-Step3.jpg)
Upon completion of programming, the Application Output tab is automatically opened, where the achieved result can be read. In case of an inability to perform the Debug function, check if a proper connection between the MCU used by the setup and the CODEGRIP programmer has been established. A detailed explanation of the CODEGRIP-board connection can be found in the CODEGRIP User Manual. Please find it in the RESOURCES section.
![Application Output Step 4](https://dbp-cdn.mikroe.com/cms/shared-resources/1eed5550-d4d0-6b20-a348-02420a000272/AP-Step4.jpg)
Software Support
Library Description
This library contains API for Barcode 2 Click driver.
Key functions:
barcode2_enable_scaning
- The function enables or disables barcode scaning depending on state parametar valuebarcode2_process
- The general process of collecting data the module sends
Open Source
Code example
This example can be found in NECTO Studio. Feel free to download the code, or you can copy the code below.
/*!
* \file
* \brief Barcode2 Click example
*
* # Description
* This example reads and processes data from Barcode 2 clicks.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes the UART driver used for communication and another UART bus used
* for data logging.
*
* ## Application Task
* This is an example that demonstrates the use of the Barcode 2 Click board.
* First, it enables scanning and waits up to 10 seconds for the barcode to be detected.
* If the barcode or QR Code is detected, it displays its content to the USB UART.
* After that, disables scanning for 3 seconds.
* Results are being sent to the Usart Terminal where you can track their changes.
*
* ## Additional Function
* - barcode2_process ( ) - The general process of collecting data the module sends.
*
* \author MikroE Team
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "barcode2.h"
#include "string.h"
#define PROCESS_COUNTER 100
#define PROCESS_RX_BUFFER_SIZE 600
#define PROCESS_PARSER_BUFFER_SIZE 600
// ------------------------------------------------------------------ VARIABLES
static barcode2_t barcode2;
static log_t logger;
static char current_parser_buf[ PROCESS_PARSER_BUFFER_SIZE ];
// ------------------------------------------------------- ADDITIONAL FUNCTIONS
static void barcode2_process ( void )
{
int32_t rsp_size;
uint16_t rsp_cnt = 0;
char uart_rx_buffer[ PROCESS_RX_BUFFER_SIZE ] = { 0 };
uint16_t check_buf_cnt;
uint8_t process_cnt = PROCESS_COUNTER;
// Clear parser buffer
memset( current_parser_buf, 0, PROCESS_PARSER_BUFFER_SIZE );
while( process_cnt != 0 )
{
rsp_size = barcode2_generic_read( &barcode2, &uart_rx_buffer, PROCESS_RX_BUFFER_SIZE );
if ( rsp_size >0 )
{
// Validation of the received data
for ( check_buf_cnt = 0; check_buf_cnt < rsp_size; check_buf_cnt++ )
{
if ( uart_rx_buffer[ check_buf_cnt ] == 0 )
{
uart_rx_buffer[ check_buf_cnt ] = 13;
}
}
// Storages data in parser buffer
rsp_cnt += rsp_size;
if ( rsp_cnt < PROCESS_PARSER_BUFFER_SIZE )
{
strncat( current_parser_buf, uart_rx_buffer, rsp_size );
}
process_cnt = 3;
// Clear RX buffer
memset( uart_rx_buffer, 0, PROCESS_RX_BUFFER_SIZE );
}
else
{
process_cnt--;
// Process delay
Delay_100ms( );
}
}
if ( rsp_cnt > 0 )
{
if ( rsp_cnt > 80 )
{
log_printf( &logger, " QR Code:\r\n%s", current_parser_buf );
}
else
{
log_printf( &logger, " Barcode: %s", current_parser_buf );
}
log_printf( &logger, "\r\n------------------------\r\n" );
}
}
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( void )
{
log_cfg_t log_cfg;
barcode2_cfg_t cfg;
/**
* Logger initialization.
* Default baud rate: 115200
* Default log level: LOG_LEVEL_DEBUG
* @note If USB_UART_RX and USB_UART_TX
* are defined as HAL_PIN_NC, you will
* need to define them manually for log to work.
* See @b LOG_MAP_USB_UART macro definition for detailed explanation.
*/
LOG_MAP_USB_UART( log_cfg );
log_init( &logger, &log_cfg );
log_info( &logger, "---- Application Init ----" );
// Click initialization.
barcode2_cfg_setup( &cfg );
BARCODE2_MAP_MIKROBUS( cfg, MIKROBUS_1 );
barcode2_init( &barcode2, &cfg );
Delay_ms ( 100 );
}
void application_task ( void )
{
log_printf( &logger, " Scanning enabled \r\n" );
log_printf( &logger, "------------------------\r\n" );
barcode2_enable_scaning( &barcode2, BARCODE2_ENABLE );
barcode2_process( );
barcode2_enable_scaning( &barcode2, BARCODE2_DISABLE );
log_printf( &logger, " Scanning disabled \r\n" );
log_printf( &logger, "------------------------\r\n" );
Delay_ms( 3000 );
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END