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
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.
Microcontroller Overview
MCU Card / MCU
Architecture
PIC
MCU Memory (KB)
48
Silicon Vendor
Microchip
Pin count
28
RAM (Bytes)
3328
Used MCU Pins
mikroBUS™ mapper
Take a closer look
Schematic
Step by step
Project assembly
Track your results in real time
Application Output via UART Mode
1. Once the code example is loaded, pressing the "FLASH" button initiates the build process, and programs it on the created setup.
2. After the programming is completed, click on the Tools icon in the upper-right panel, and select the UART Terminal.
3. After opening the UART Terminal tab, first check the baud rate setting in the Options menu (default is 115200). If this parameter is correct, activate the terminal by clicking the "CONNECT" button.
4. Now terminal status changes from Disconnected to Connected in green, and the data is displayed in the Received data field.
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
This example can be found in NECTO Studio. Feel free to download the code, or you can copy the code below.
/*!
* \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