Unlock a world of possibilities with your personalized digital ID!
A
A
Hardware Overview
How does it work?
Unique ID Click is based on the DS2401, a guaranteed unique 64-bit ROM ID chip from Analog Devices. The 64-bit ROM includes a unique 48-bit serial number, an 8-bit CRC, and an 8-bit Family Code (01h). Its internal ROM is accessed via a single data line with a communication speed of up to 16.3Kbps. In perspective, multiple DS2401 devices can reside on a common 1-Wire net, with a built-in multidrop controller that ensures compatibility with other 1-Wire devices. The
DS2401 features presence pulse acknowledgment when the reader first applies a voltage, where the power for reading and writing the device is derived from the data line itself. The Unique ID Click uses a 1-Wire bus interface to communicate to the host MCU through one of the GPIOs (GP0, GP1) of the mikroBUS™ socket, selectable by the onboard GPIO SEL jumper. This protocol defines bus transactions regarding the bus state during specified time slots initiated on the falling edge of
sync pulses from the host bus. All data is read and written the least significant bit first. This Click board™ can operate with either 3.3V or 5V logic voltage levels selected via the PWR SEL jumper. This way, both 3.3V and 5V capable MCUs can use the communication lines properly. However, the Click board™ comes equipped with a library containing easy-to-use functions and an example code that can be used, as a reference, for further development.
Features overview
Development board
PIC18F57Q43 Curiosity Nano evaluation kit is a cutting-edge hardware platform designed to evaluate microcontrollers within the PIC18-Q43 family. Central to its design is the inclusion of the powerful PIC18F57Q43 microcontroller (MCU), offering advanced functionalities and robust performance. Key features of this evaluation kit include a yellow user LED and a responsive
mechanical user switch, providing seamless interaction and testing. The provision for a 32.768kHz crystal footprint ensures precision timing capabilities. With an onboard debugger boasting a green power and status LED, programming and debugging become intuitive and efficient. Further enhancing its utility is the Virtual serial port (CDC) and a debug GPIO channel (DGI
GPIO), offering extensive connectivity options. Powered via USB, this kit boasts an adjustable target voltage feature facilitated by the MIC5353 LDO regulator, ensuring stable operation with an output voltage ranging from 1.8V to 5.1V, with a maximum output current of 500mA, subject to ambient temperature and voltage constraints.
Microcontroller Overview
MCU Card / MCU

Architecture
PIC
MCU Memory (KB)
128
Silicon Vendor
Microchip
Pin count
48
RAM (Bytes)
8196
You complete me!
Accessories
Curiosity Nano Base for Click boards is a versatile hardware extension platform created to streamline the integration between Curiosity Nano kits and extension boards, tailored explicitly for the mikroBUS™-standardized Click boards and Xplained Pro extension boards. This innovative base board (shield) offers seamless connectivity and expansion possibilities, simplifying experimentation and development. Key features include USB power compatibility from the Curiosity Nano kit, alongside an alternative external power input option for enhanced flexibility. The onboard Li-Ion/LiPo charger and management circuit ensure smooth operation for battery-powered applications, simplifying usage and management. Moreover, the base incorporates a fixed 3.3V PSU dedicated to target and mikroBUS™ power rails, alongside a fixed 5.0V boost converter catering to 5V power rails of mikroBUS™ sockets, providing stable power delivery for various connected devices.
Used MCU Pins
mikroBUS™ mapper
Take a closer look
Click board™ Schematic

Step by step
Project assembly
Track your results in real time
Application Output
1. Application Output - In Debug mode, the 'Application Output' window enables real-time data monitoring, offering direct insight into execution results. Ensure proper data display by configuring the environment correctly using the provided tutorial.

2. UART Terminal - Use the UART Terminal to monitor data transmission via a USB to UART converter, allowing direct communication between the Click board™ and your development system. Configure the baud rate and other serial settings according to your project's requirements to ensure proper functionality. For step-by-step setup instructions, refer to the provided tutorial.

3. Plot Output - The Plot feature offers a powerful way to visualize real-time sensor data, enabling trend analysis, debugging, and comparison of multiple data points. To set it up correctly, follow the provided tutorial, which includes a step-by-step example of using the Plot feature to display Click board™ readings. To use the Plot feature in your code, use the function: plot(*insert_graph_name*, variable_name);. This is a general format, and it is up to the user to replace 'insert_graph_name' with the actual graph name and 'variable_name' with the parameter to be displayed.

Software Support
Library Description
This library contains API for Unique ID Click driver.
Key functions:
uniqueid_read_id
- This function reads Family Code and Serial Number of device's ROM memory
Open Source
Code example
The complete application code and a ready-to-use project are available through the NECTO Studio Package Manager for direct installation in the NECTO Studio. The application code can also be found on the MIKROE GitHub account.
/*!
* @file main.c
* @brief UNIQUE ID Click example.
*
* # Description
* This example demonstrates the use of UNIQUE ID click board by reading and
* displaying Family Code and Serial Number on the UART Terminal.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes both logger config object and
* click config object.
*
* ## Application Task
* Demonstrates the usage of uniqueid_read_id function,
* which stores the Family Code and Serial Number of the click in
* family_code and serial_num variables. Both values will be displayed
* on the UART Terminal.
*
* @author Aleksandra Cvjeticanin
*
*/
#include "board.h"
#include "log.h"
#include "uniqueid.h"
static uniqueid_t uniqueid;
static log_t logger;
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
uniqueid_cfg_t uniqueid_cfg; /**< Click config object. */
/**
* 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
uniqueid_cfg_setup( &uniqueid_cfg );
UNIQUEID_MAP_MIKROBUS( uniqueid_cfg, MIKROBUS_1 );
if ( ONE_WIRE_ERROR == uniqueid_init( &uniqueid, &uniqueid_cfg ) )
{
log_error( &logger, " Initialization error." );
for ( ; ; );
}
log_info( &logger, " Application Task " );
}
void application_task ( void )
{
uint8_t family_code;
uint8_t serial_num[ 6 ];
if ( UNIQUEID_OK == uniqueid_read_id( &uniqueid, &family_code, &serial_num[ 0 ] ) )
{
log_printf( &logger, "Family Code = 0x%.2X\r\n", ( uint16_t ) family_code );
log_printf( &logger, "Serial Number = 0x%.2X%.2X%.2X%.2X%.2X%.2X\r\n",
( uint16_t ) serial_num[ 0 ], ( uint16_t ) serial_num[ 1 ],
( uint16_t ) serial_num[ 2 ], ( uint16_t ) serial_num[ 3 ],
( uint16_t ) serial_num[ 4 ], ( uint16_t ) serial_num[ 5 ] );
}
Delay_ms( 1000 );
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END