Create reliable switching solutions with CT10-1540-G1 and MK64FN1M0VDC12
Switch it up with REED: Electromagnetic control redefined
Published Sep 13, 2023
Click board™
REED Click
Dev. board
Clicker 2 for Kinetis
Compiler
NECTO Studio
MCU
MK64FN1M0VDC12
With the flexibility of our Reed switch solution, you can design innovative applications that rely on precise electromagnetic control, expanding the possibilities for automation and monitoring
A
A
Hardware Overview
How does it work?
REED Click is based on the CT10-1540-G1, a Coto Classic C10 series molded reed switch from Coto Technology. This hermetically sealed low-current dry reed switch is an SPST type (single pole, single throw), having normally open ruthenium contacts. The sensor is a double-ended type and may be actuated with an electromagnet, a permanent magnet, or a combination of both. The CT10-1540-G1 designation indicates that this sensor has a sensitivity range from 15 to 40AT and a release range from 3 to 39AT. The sensor has resistance to a vibration of 10G and resistance to a shock of
100G, which ensures that the switch will not be activated with anything but the electromagnetic field. The REED Click uses a single CS pin of the mikroBUS™ socket connected to the host MCU to output 1 or 0, depending on whether the switch is closed or open. The sensor has two separate pole contacts inside a glass casing (north and south). When a magnetic field is applied, it snaps them shut, thus activating the switch. Once the magnet is removed, it opens up again. A magnetic field activates the sensor and not the field's distance to the sensor. A stronger but farther field counts
more than a weaker but closer one. In addition, this Click board™ features an L1 LED to present the activated switch visually. 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. Also, this 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
Clicker 2 for Kinetis is a compact starter development board that brings the flexibility of add-on Click boards™ to your favorite microcontroller, making it a perfect starter kit for implementing your ideas. It comes with an onboard 32-bit ARM Cortex-M4F microcontroller, the MK64FN1M0VDC12 from NXP Semiconductors, two mikroBUS™ sockets for Click board™ connectivity, a USB connector, LED indicators, buttons, a JTAG programmer connector, and two 26-pin headers for interfacing with external electronics. Its compact design with clear and easily recognizable silkscreen markings allows you to build gadgets with unique functionalities and
features quickly. Each part of the Clicker 2 for Kinetis development kit contains the components necessary for the most efficient operation of the same board. In addition to the possibility of choosing the Clicker 2 for Kinetis programming method, using a USB HID mikroBootloader or an external mikroProg connector for Kinetis programmer, the Clicker 2 board also includes a clean and regulated power supply module for the development kit. It provides two ways of board-powering; through the USB Micro-B cable, where onboard voltage regulators provide the appropriate voltage levels to each component on the board, or
using a Li-Polymer battery via an onboard battery connector. All communication methods that mikroBUS™ itself supports are on this board, including the well-established mikroBUS™ socket, reset button, and several user-configurable buttons and LED indicators. Clicker 2 for Kinetis is an integral part of the Mikroe ecosystem, allowing you to create a new application in minutes. Natively supported by Mikroe software tools, it covers many aspects of prototyping thanks to a considerable number of different Click boards™ (over a thousand boards), the number of which is growing every day.
Microcontroller Overview
MCU Card / MCU
Architecture
ARM Cortex-M4
MCU Memory (KB)
1024
Silicon Vendor
NXP
Pin count
121
RAM (Bytes)
262144
Used MCU Pins
mikroBUS™ mapper
Take a closer look
Click board™ Schematic
Step by step
Project assembly
Start by selecting your development board and Click board™. Begin with the Clicker 2 for Kinetis as your development board.
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 REED Click driver.
Key functions:
reed_get_status- Get magnetic detected status function
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
* \brief REED Click example
*
* # Description
* This is a example which demonstrates the use of REED Click board.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Configuring clicks and log objects.
*
* ## Application Task
* Detect the magnetic field near the REED Click.
* Results are being sent to the Usart Terminal where you can track their changes.
* All data logs on usb uart when magnetic field is detected.
*
* \author Nemanja Medakovic
*
*/
#include "board.h"
#include "log.h"
#include "reed.h"
static reed_t reed;
static log_t logger;
void application_init ( void )
{
log_cfg_t log_cfg;
reed_cfg_t reed_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.
reed_cfg_setup( &reed_cfg );
REED_MAP_MIKROBUS( reed_cfg, MIKROBUS_1 );
if ( reed_init( &reed, &reed_cfg ) == REED_INIT_ERROR )
{
log_info( &logger, "---- Application Init Error. ----" );
log_info( &logger, "---- Please, run program again... ----" );
for ( ; ; );
}
log_info( &logger, "---- Application Init Done. ----" );
log_info( &logger, "---- Application Running... ----\n" );
}
void application_task ( void )
{
uint8_t reed_state = REED_NO_MAGNETIC_FIELD;
static uint8_t reed_state_old = REED_NO_MAGNETIC_FIELD;
reed_state = reed_get_status( &reed );
if ( ( reed_state == REED_MAGNETIC_FIELD_DETECTED ) && ( reed_state_old == REED_NO_MAGNETIC_FIELD ) )
{
reed_state_old = reed_state;
log_printf( &logger, " ~ UNLOCKED ~\r\n" );
log_printf( &logger, "--------------------\r\n" );
}
else if ( ( reed_state == REED_NO_MAGNETIC_FIELD ) && ( reed_state_old == REED_MAGNETIC_FIELD_DETECTED ) )
{
reed_state_old = reed_state;
log_printf( &logger, " ~ LOCKED ~\r\n" );
log_printf( &logger, "--------------------\r\n" );
}
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END
