Delve into the realm of high-fidelity audio with our analog active crossover solution, designed to enhance clarity and precision in two-way loudspeakers
A
A
Hardware Overview
How does it work?
Audio Xover Click is based on the MCP6H012, an operational amplifier with rail-to-rail output operation from Microchip. It uses three Butterworth filters (one for each speaker) with possibility of changing cutoff frequency between 120Hz, 90Hz and 70Hz. Butterworth filters are called maximally flat filters because, for a given order, they have the sharpest roll-off possible without inducing peaking in the Bode plot. The two-pole filter with a damping ratio of 0.707 is the second-order Butterworth filter. Audio crossovers are a type of electronic filter circuitry used in a range of audio applications, to split up an audio signal into two or more frequency ranges, so that
the signals can be sent to drivers that are designed for different frequency ranges. Active crossovers are distinguished from passive crossovers in that whereas passive crossovers split up an amplified signal coming from one power amplifier so that it can be sent to two or more drivers (e.g., a woofer and a very low frequency subwoofer, or a woofer and a tweeter), an active crossover splits up audio signal prior to amplification, so that it can be sent to two or more power amplifiers, each of which is connected to a separate driver type. Active crossovers as Audio Xover Click don’t care how powerful your amplifiers are because they process the signal
before it enters the amplifier. Active crossovers are also not very sensitive to temperature variations, so they can be very accurate, all the time. If one of the amplifiers channels in an active crossover system clips, the distortion only affects that single channel. This Click board™ can be operated only with a 5V logic voltage level. The board must perform appropriate logic voltage level conversion before using MCUs with different logic levels. Also, it comes equipped with a library containing functions and an example code that can be used as a reference for further development.
Features overview
Development board
Fusion for TIVA v8 is a development board specially designed for the needs of rapid development of embedded applications. It supports a wide range of microcontrollers, such as different 32-bit ARM® Cortex®-M based MCUs from Texas Instruments, regardless of their number of pins, and a broad set of unique functions, such as the first-ever embedded debugger/programmer over a WiFi network. The development board is well organized and designed so that the end-user has all the necessary elements, such as switches, buttons, indicators, connectors, and others, in one place. Thanks to innovative manufacturing technology, Fusion for TIVA v8 provides a fluid and immersive working experience, allowing access
anywhere and under any circumstances at any time. Each part of the Fusion for TIVA v8 development board contains the components necessary for the most efficient operation of the same board. An advanced integrated CODEGRIP programmer/debugger module offers many valuable programming/debugging options, including support for JTAG, SWD, and SWO Trace (Single Wire Output)), and seamless integration with the Mikroe software environment. Besides, it also includes a clean and regulated power supply module for the development board. It can use a wide range of external power sources, including a battery, an external 12V power supply, and a power source via the USB Type-C (USB-C) connector.
Communication options such as USB-UART, USB HOST/DEVICE, CAN (on the MCU card, if supported), and Ethernet is also included. In addition, it also has the well-established mikroBUS™ standard, a standardized socket for the MCU card (SiBRAIN standard), and two display options for the TFT board line of products and character-based LCD. Fusion for TIVA v8 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
Type
8th Generation
Architecture
ARM Cortex-M4
MCU Memory (KB)
512
Silicon Vendor
Texas Instruments
Pin count
212
RAM (Bytes)
262144
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 Audio Xover Click driver.
Key functions:
audioxover_power_on
- Device power on function.audioxover_shut_down
- Device shut down 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 Audio Xover Click example
*
* # Description
* This example demonstrates the use of the Audio Xover click board.
* The click is an analog active crossover solution for two-way loudspeakers.
* The primary purpose of the crossover circuit in a loudspeaker is to split
* an incoming audio signal into frequency bands that are passed to
* the speaker best suited.
*
* The demo application is composed of two sections :
*
* ## Application Init
* This function initializes the driver and makes an initial log.
*
* ## Application Task
* This function enables and disables the click board every 10 seconds,
* and logs an appropriate message on the USB UART.
*
* @note
* The hardware revision v100 of the click board works only with MCUs that operates
* at 5V operating voltage level.
*
* \author MikroE Team
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "audioxover.h"
// ------------------------------------------------------------------ VARIABLES
static audioxover_t audioxover;
static log_t logger;
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( void )
{
log_cfg_t log_cfg;
audioxover_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.
audioxover_cfg_setup( &cfg );
AUDIOXOVER_MAP_MIKROBUS( cfg, MIKROBUS_1 );
audioxover_init( &audioxover, &cfg );
}
void application_task ( void )
{
log_printf( &logger, " * Switch: ON *\r\n" );
audioxover_power_on ( &audioxover );
Delay_ms( 10000 );
log_printf( &logger, " * Switch: OFF *\r\n" );
audioxover_shut_down ( &audioxover );
Delay_ms( 10000 );
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END