30 min

Achieve real-time monitoring and control in automotive and industrial settings with ATA663211 and PIC18F26K20

The future of low-speed data communication with LIN transceivers

ATA663211 Click with EasyPIC v7

Published Nov 01, 2023

Click board™

ATA663211 Click

Development board

EasyPIC v7


NECTO Studio



Our LIN transceiver empowers vehicles and industrial systems to efficiently exchange critical data at low speeds, ensuring seamless communication



Hardware Overview

How does it work?

ATA663211 Click is based on the ATA663211, a LIN transceiver from Microchip. It features several protection functionalities, such as over-temperature, short-circuit protection vs. GND and battery, advanced EMC and ESD, and more. The integrated 3.3V onboard LDO voltage regulator is the MCP1804, an LDO regulator with shutdown from Microchip. The combination of a voltage regulator and a bus transceiver makes it possible to develop simple but powerful slave nodes in LIN bus systems. This way, ATA663211 Click can be used as a standalone LIN transceiver without being connected to a mikroBUS™ socket. An onboard LDO (low-dropout regulator) lets it supply power through the VS line screw terminal. This regulated voltage is also available on the +3.3V rail of the mikroBUS™ socket to power up the 3.3V attached host MCU. There are several operating modes for the ATA663211 Click. In Normal mode, the LIN interface is transmitting and receiving. In Sleep mode, the transmission path is disabled, and the LIN transceiver is in low-power mode. The Failsafe mode is automatically switched at system power-up or after a wake-up event. The LIN transceiver

is switched off in this mode, and the inhibit output pin is switched on. For the typical application as a Master node, the ATA663211 requires the LBUS line of the chip to be connected to the VBB of the LIN BUS, achievable via a populated L-PULL jumper. This jumper can be removed in other scenarios, such as the LIN Slave node. The ATA663211 communicates with the MCU using the UART RX and TX signals. Besides communication, these pins also serve to signal the failsafe condition. The undervoltage on the LIN connector can cause the failsafe condition: less than 3.9V will cause the undervoltage condition, signaled by the LOW logic state on the RX pin and the HIGH logic state on the TX pin. A LIN wake-up event from either silent or sleep mode is signaled by the LOW logic state on both the RX and TX pins. This event is received via the LIN bus and is used to switch the ATA663211 click to an active state. On the other hand, Low on TX and HIGH on RX will signal the local wake-up. RX and TX signals are also routed to the header on the edge of the Click board™ so they can be used independently of the mikroBUS™ socket. The inhibit output pin of the LIN transceiver is used

to control the Shutdown input of the MCP1804 LDO; thus, the supply pin of the LIN transceiver itself, as the LDO, supplies the LIN transceiver supply pin with LIN operating voltage. The voltages on this line can be monitored over the INH pin of the mikroBUS™ socket via the resistor divider. To enable the LIN transceiver, there is an EN SEL jumper set to the HI position by default, thus enabling the transceiver. Setting it to the LOW position allows you to control the enable function over the EN pin of the mikroBUS™ socket. In addition, this same pin is routed to the second pair of headers to enable the LIN transceiver externally. The other pin on this header is WKin, a high-voltage input for waking up the device. This Click board™ can be operated only with a 3.3V logic voltage level. The board must perform appropriate logic voltage level conversion before using MCUs with different logic levels. However, the Click board™ comes equipped with a library containing functions and an example code that can be used as a reference for further development.

ATA663211 Click hardware overview image

Features overview

Development board

EasyPIC v7 is the seventh generation of PIC development boards specially designed to develop embedded applications rapidly. It supports a wide range of 8-bit PIC microcontrollers from Microchip and has a broad set of unique functions, such as a powerful onboard mikroProg programmer and In-Circuit debugger over USB-B. The development board is well organized and designed so that the end-user has all the necessary elements in one place, such as switches, buttons, indicators, connectors, and others. With four different connectors for each port, EasyPIC v7 allows you to connect accessory boards, sensors, and custom electronics more efficiently than ever. Each part of

the EasyPIC v7 development board contains the components necessary for the most efficient operation of the same board. An integrated mikroProg, a fast USB 2.0 programmer with mikroICD hardware In-Circuit Debugger, offers many valuable programming/debugging options and seamless integration with the Mikroe software environment. Besides it also includes a clean and regulated power supply block for the development board. It can use various external power sources, including an external 12V power supply, 7-23V AC or 9-32V DC via DC connector/screw terminals, and a power source via the USB Type-B (USB-B) connector. Communication options such as

USB-UART and RS-232 are also included, alongside the well-established mikroBUS™ standard, three display options (7-segment, graphical, and character-based LCD), and several different DIP sockets. These sockets cover a wide range of 8-bit PIC MCUs, from PIC10F, PIC12F, PIC16F, PIC16Enh, PIC18F, PIC18FJ, and PIC18FK families. EasyPIC v7 is an integral part of the Mikroe ecosystem for rapid development. Natively supported by Mikroe software tools, it covers many aspects of prototyping and development thanks to a considerable number of different Click boards™ (over a thousand boards), the number of which is growing every day.

EasyPIC v7 horizontal image

Microcontroller Overview

MCU Card / MCU




MCU Memory (KB)


Silicon Vendor


Pin count


RAM (Bytes)


Used MCU Pins

mikroBUS™ mapper

Voltage Regulator Control
Device Mode Control
Power Supply

Take a closer look


ATA663211 Click Schematic schematic

Step by step

Project assembly

EasyPIC v7 front image hardware assembly

Start by selecting your development board and Click board™. Begin with the EasyPIC v7 as your development board.

EasyPIC v7 front image hardware assembly
LTE IoT 5 Click front image hardware assembly
MCU DIP 28 hardware assembly
LTE IoT 5 Click complete accessories setup image hardware assembly
EasyPIC v7 Access MB 2 - upright/background hardware assembly
Necto image step 2 hardware assembly
Necto image step 3 hardware assembly
Necto image step 4 hardware assembly
NECTO Compiler Selection Step Image hardware assembly
NECTO Output Selection Step Image hardware assembly
Necto image step 6 hardware assembly
Necto DIP image step 7 hardware assembly
EasyPIC PRO v7a Display Selection Necto Step hardware assembly
Necto image step 9 hardware assembly
Necto image step 10 hardware assembly
Necto PreFlash Image hardware assembly

Track your results in real time

Application Output

After pressing the "FLASH" button on the left-side panel, it is necessary to open the UART terminal to display the achieved results. By clicking on the Tools icon in the right-hand panel, multiple different functions are displayed, among which is the UART Terminal. Click on the offered "UART Terminal" icon.

UART Application Output Step 1

Once the UART terminal is opened, the window takes on a new form. At the top of the tab are two buttons, one for adjusting the parameters of the UART terminal and the other for connecting the UART terminal. The tab's lower part is reserved for displaying the achieved results. Before connecting, the terminal has a Disconnected status, indicating that the terminal is not yet active. Before connecting, it is necessary to check the set parameters of the UART terminal. Click on the "OPTIONS" button.

UART Application Output Step 2

In the newly opened UART Terminal Options field, we check if the terminal settings are correct, such as the set port and the Baud rate of UART communication. If the data is not displayed properly, it is possible that the Baud rate value is not set correctly and needs to be adjusted to 115200. If all the parameters are set correctly, click on "CONFIGURE".

UART Application Output Step 3

The next step is to click on the "CONNECT" button, after which the terminal status changes from Disconnected to Connected in green, and the data is displayed in the Received data field.

UART Application Output Step 4

Software Support

Library Description

This library contains API for ATA663211 Click driver.

Key functions:

  • ata663211_generic_write - Generic write function

  • ata663211_generic_read - Generic read function.

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 Ata663211 Click example
 * # Description
 * This application is for handling low-speed data communication in vehicles and in industrial.
 * The demo application is composed of two sections :
 * ## Application Init 
 * Initalizes device and makes an initial log.
 * ## Application Task  
 * Checks if new data byte have received in rx buffer (ready for reading), and if ready than reads one byte from rx buffer.
 * \author MikroE Team
// ------------------------------------------------------------------- INCLUDES

#include "board.h"
#include "log.h"
#include "ata663211.h"

// ------------------------------------------------------------------ VARIABLES


static ata663211_t ata663211;
static log_t logger;

static char demo_message[ 9 ] = { 'M', 'i', 'k', 'r', 'o', 'E', 13, 10, 0 };

// ------------------------------------------------------ APPLICATION FUNCTIONS

void application_init ( void )
    log_cfg_t log_cfg;
    ata663211_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.

    ata663211_cfg_setup( &cfg );
    ATA663211_MAP_MIKROBUS( cfg, MIKROBUS_1 );
    ata663211_init( &ata663211, &cfg );

void application_task ( void )
    char tmp;
    //  Task implementation.

       // RECEIVER - UART polling

       tmp =  ata663211_generic_single_read( &ata663211 );
       log_printf( &logger, " %c ", tmp );

       // TRANSMITER - TX each 2 sec
       ata663211_generic_multi_write( &ata663211, demo_message, 9 );
       Delay_ms( 2000 );


void main ( void )
    application_init( );

    for ( ; ; )
        application_task( );

// ------------------------------------------------------------------------ END

Additional Support