Provide precise and dependable relay control activated by magnetic fields. It empowers you to optimize applications in security systems and industrial automation with ease.
A
A
Hardware Overview
How does it work?
Hall Switch Click is based on the AH1389, an ultra-sensitive dual output unipolar Hall Effect switch, from Diodes Incorporated. This IC utilizes Hall effect - a phenomenon in which the current flow, or rather - the path of the conductor electrons is affected by the magnetic field. Due to the fact that the path of the electrons is curved, a buildup of positive charges is formed on the opposite side of this path, and the voltage is generated. If a voltmeter is connected to the path perpendicular to the current path and the magnetic field, a voltage will be detected. The AH1389 has the ability to detect both the north and south poles of the magnetic field. The magnetic field from the south pole magnet will pull the output 2 to a LOW (active) state, while the magnetic field from the north pole magnet will pull the output 1 to a LOW
(active) state. The IC features several sections for the signal conditioning. It also provides the hysteresis for the output activation, to avoid erratic triggering. The magnetic field strength which activates outputs is about ±25 G, while the field strength under ±20 G will deactivate outputs, giving a hysteresis of typical 5 G. The positive and negative sign is used with respect to the magnet poles (north pole has a negative sign prefix). The outputs of the AH1389 IC are routed to the operational amplifiers, which work as the inverting comparators. When the output of the AH1389 IC is activated - pulled to a LOW voltage level, the output from the comparator will be set to 5V. This will cause biasing of the BJT, allowing current flow through the relay coil, and thus forming a magnetic field necessary for closing the relay
contacts. A Schottky diode across the relay coil prevents the reverse kickback voltage, which forms due to the inert nature of the coils. Activation of the relay coils is indicated by the red and blue LEDs, respectively. Two outputs of the AH1389 IC are also routed to the mikroBUS pins: north pole output (1) is routed to the CS pin and the south pole output (2) is routed to the INT pin of the mikroBUS™ so that the status of the IC can be monitored by the MCU. Two varistors are used to prevent voltage peaks when the load is connected or disconnected on the relay output contacts. The output contacts are further routed to the screw terminals, which allow up to 10A. However the relays allow up to 5A for 250V AC/30V DC, so the connected load should not exceed these power ratings.
Features overview
Development board
Flip&Click PIC32MZ is a compact development board designed as a complete solution 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 PIC32MZ microcontroller, the PIC32MZ2048EFH100 from Microchip, four mikroBUS™ sockets for Click board™ connectivity, two USB connectors, LED indicators, buttons, debugger/programmer connectors, and two headers compatible with Arduino-UNO pinout. Thanks to innovative manufacturing technology,
it allows you to build gadgets with unique functionalities and features quickly. Each part of the Flip&Click PIC32MZ development kit contains the components necessary for the most efficient operation of the same board. In addition, there is the possibility of choosing the Flip&Click PIC32MZ programming method, using the chipKIT bootloader (Arduino-style development environment) or our USB HID bootloader using mikroC, mikroBasic, and mikroPascal for PIC32. This kit includes a clean and regulated power supply block through the USB Type-C (USB-C) connector. All communication
methods that mikroBUS™ itself supports are on this board, including the well-established mikroBUS™ socket, user-configurable buttons, and LED indicators. Flip&Click PIC32MZ development kit allows 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
PIC32
MCU Memory (KB)
2048
Silicon Vendor
Microchip
Pin count
100
RAM (Bytes)
524288
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 Hall Switch Click driver.
Key functions:
hallswitch_set_npole
- Function for turn on and turn off N Pole
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 Hall Switch Click example
*
* # Description
* The application sets sensor magnetic pole
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes Driver init and turn OFF S-pole and N-pole
*
* ## Application Task
* Turns S and N on and off every 500 ms
*
* \author MikroE Team
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "hallswitch.h"
// ------------------------------------------------------------------ VARIABLES
static hallswitch_t hallswitch;
static log_t logger;
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( void )
{
log_cfg_t log_cfg;
hallswitch_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.
hallswitch_cfg_setup( &cfg );
HALLSWITCH_MAP_MIKROBUS( cfg, MIKROBUS_1 );
hallswitch_init( &hallswitch, &cfg );
hallswitch_set_npole( &hallswitch, HALLSWITCH_POLE_NO_ACTIVE );
hallswitch_set_spole( &hallswitch, HALLSWITCH_POLE_NO_ACTIVE );
}
void application_task()
{
hallswitch_set_npole( &hallswitch, HALLSWITCH_POLE_ACTIVE );
Delay_ms ( 500 );
hallswitch_set_spole( &hallswitch, HALLSWITCH_POLE_ACTIVE );
Delay_ms ( 500 );
hallswitch_set_npole( &hallswitch, HALLSWITCH_POLE_NO_ACTIVE );
Delay_ms ( 500 );
hallswitch_set_spole( &hallswitch, HALLSWITCH_POLE_NO_ACTIVE );
Delay_ms ( 500 );
}
int main ( void )
{
/* Do not remove this line or clock might not be set correctly. */
#ifdef PREINIT_SUPPORTED
preinit();
#endif
application_init( );
for ( ; ; )
{
application_task( );
}
return 0;
}
// ------------------------------------------------------------------------ END
/*!
* \file
* \brief Hall Switch Click example
*
* # Description
* The application sets sensor magnetic pole
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes Driver init and turn OFF S-pole and N-pole
*
* ## Application Task
* Turns S and N on and off every 500 ms
*
* \author MikroE Team
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "hallswitch.h"
// ------------------------------------------------------------------ VARIABLES
static hallswitch_t hallswitch;
static log_t logger;
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( void )
{
log_cfg_t log_cfg;
hallswitch_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.
hallswitch_cfg_setup( &cfg );
HALLSWITCH_MAP_MIKROBUS( cfg, MIKROBUS_1 );
hallswitch_init( &hallswitch, &cfg );
hallswitch_set_npole( &hallswitch, HALLSWITCH_POLE_NO_ACTIVE );
hallswitch_set_spole( &hallswitch, HALLSWITCH_POLE_NO_ACTIVE );
}
void application_task()
{
hallswitch_set_npole( &hallswitch, HALLSWITCH_POLE_ACTIVE );
Delay_ms ( 500 );
hallswitch_set_spole( &hallswitch, HALLSWITCH_POLE_ACTIVE );
Delay_ms ( 500 );
hallswitch_set_npole( &hallswitch, HALLSWITCH_POLE_NO_ACTIVE );
Delay_ms ( 500 );
hallswitch_set_spole( &hallswitch, HALLSWITCH_POLE_NO_ACTIVE );
Delay_ms ( 500 );
}
int main ( void )
{
/* Do not remove this line or clock might not be set correctly. */
#ifdef PREINIT_SUPPORTED
preinit();
#endif
application_init( );
for ( ; ; )
{
application_task( );
}
return 0;
}
// ------------------------------------------------------------------------ END