Capable of concurrently tracking four GNSS constellations delivering highly reliable location data
A
A
Hardware Overview
How does it work?
GNSS MAX Click is based on the MAX-M10S (MAX-M10S-00B-01), a high-performance GNSS module from u-blox. The MAX-M10S features the u-blox M10 standard precision GNSS platform and provides exceptional sensitivity and acquisition times for all L1 GNSS signals. It also supports concurrent reception of up to four GNSS (GPS, GLONASS, Galileo, and BeiDou), maximizing position availability, particularly under challenging conditions such as deep urban canyons. The MAX-M10S offers high sensitivity and minimal acquisition times while maintaining low system power. The MAX-M10S module integrates an LNA and a SAW filter in the RF path for maximum sensitivity. Also, it detects jamming and spoofing attempts and reports them to the host so that the system can react to such events. Advanced filtering algorithms mitigate the impact of RF interference and jamming, thus enabling the product to operate as intended.
The u-blox Super-S technology offers great RF sensitivity that improves the dynamic position accuracy by up to 25% with small antennas or in a non-line-of-sight scenario. This Click board™ comes with a configurable host interface that allows communication with MCU using the selected interface. The MAX-M10S can communicate with MCU using the UART interface with commonly used UART RX and TX pins as its default communication protocol operating at 9600bps to transmit and exchange data with the host MCU or using the I2C interface. The I2C interface is compatible with the Fast-Mode allowing a maximum bit rate of 400kbit/s. In addition to these features, it also uses several mikroBUS™ pins. An active-low reset signal routed on the RST pin of the mikroBUS™ socket activates a hardware reset of the system, while the EXT pin routed to the PWM pin on the mikroBUS™ socket represents an external interrupt used for the module
Wake-Up function. It also uses a PPS signal routed on the INT pin of the mikroBUS™ socket alongside a blue LED indicator marked as STATUS used for time pulse signal information and indication. GNSS MAX Click possesses the SMA antenna connector on which an appropriate antenna connects that Mikroe has in its offer for improved range and received signal strength. Also, in the case of the primary supply failure, the module can use a backup supply voltage from a connected battery if you need the Click board™ to be a standalone device. This Click board™ can only be operated from a 3.3V logic voltage level. Therefore, the board must perform appropriate logic voltage 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.

Features overview
Development board
Nucleo-64 with STM32F103RB MCU offers a cost-effective and adaptable platform for developers to explore new ideas and prototype their designs. This board harnesses the versatility of the STM32 microcontroller, enabling users to select the optimal balance of performance and power consumption for their projects. It accommodates the STM32 microcontroller in the LQFP64 package and includes essential components such as a user LED, which doubles as an ARDUINO® signal, alongside user and reset push-buttons, and a 32.768kHz crystal oscillator for precise timing operations. Designed with expansion and flexibility in mind, the Nucleo-64 board features an ARDUINO® Uno V3 expansion connector and ST morpho extension pin
headers, granting complete access to the STM32's I/Os for comprehensive project integration. Power supply options are adaptable, supporting ST-LINK USB VBUS or external power sources, ensuring adaptability in various development environments. The board also has an on-board ST-LINK debugger/programmer with USB re-enumeration capability, simplifying the programming and debugging process. Moreover, the board is designed to simplify advanced development with its external SMPS for efficient Vcore logic supply, support for USB Device full speed or USB SNK/UFP full speed, and built-in cryptographic features, enhancing both the power efficiency and security of projects. Additional connectivity is
provided through dedicated connectors for external SMPS experimentation, a USB connector for the ST-LINK, and a MIPI® debug connector, expanding the possibilities for hardware interfacing and experimentation. Developers will find extensive support through comprehensive free software libraries and examples, courtesy of the STM32Cube MCU Package. This, combined with compatibility with a wide array of Integrated Development Environments (IDEs), including IAR Embedded Workbench®, MDK-ARM, and STM32CubeIDE, ensures a smooth and efficient development experience, allowing users to fully leverage the capabilities of the Nucleo-64 board in their projects.
Microcontroller Overview
MCU Card / MCU

Architecture
ARM Cortex-M3
MCU Memory (KB)
128
Silicon Vendor
STMicroelectronics
Pin count
64
RAM (Bytes)
20480
You complete me!
Accessories
Click Shield for Nucleo-64 comes equipped with two proprietary mikroBUS™ sockets, allowing all the Click board™ devices to be interfaced with the STM32 Nucleo-64 board with no effort. This way, Mikroe allows its users to add any functionality from our ever-growing range of Click boards™, such as WiFi, GSM, GPS, Bluetooth, ZigBee, environmental sensors, LEDs, speech recognition, motor control, movement sensors, and many more. More than 1537 Click boards™, which can be stacked and integrated, are at your disposal. The STM32 Nucleo-64 boards are based on the microcontrollers in 64-pin packages, a 32-bit MCU with an ARM Cortex M4 processor operating at 84MHz, 512Kb Flash, and 96KB SRAM, divided into two regions where the top section represents the ST-Link/V2 debugger and programmer while the bottom section of the board is an actual development board. These boards are controlled and powered conveniently through a USB connection to program and efficiently debug the Nucleo-64 board out of the box, with an additional USB cable connected to the USB mini port on the board. Most of the STM32 microcontroller pins are brought to the IO pins on the left and right edge of the board, which are then connected to two existing mikroBUS™ sockets. This Click Shield also has several switches that perform functions such as selecting the logic levels of analog signals on mikroBUS™ sockets and selecting logic voltage levels of the mikroBUS™ sockets themselves. Besides, the user is offered the possibility of using any Click board™ with the help of existing bidirectional level-shifting voltage translators, regardless of whether the Click board™ operates at a 3.3V or 5V logic voltage level. Once you connect the STM32 Nucleo-64 board with our Click Shield for Nucleo-64, you can access hundreds of Click boards™, working with 3.3V or 5V logic voltage levels.
GNSS Active External Antenna is a unique multi-band type of antenna coming from u-blox that is the perfect selection for high precision GNSS applications, which require highly accurate location abilities such as RTK. The ANN-MB-00 is a multi-band (L1, L2/E5b/B2I) active GNSS antenna with a 5m cable and SMA connector. The antenna supports GPS, GLONASS, Galileo, and BeiDou and includes a high-performance multi-band RHCP dual-feed patch antenna element, a built-in high-gain LNA with SAW pre-filtering, and a 5 m antenna cable with SMA connector, and is waterproof.
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 GNSSMAX Click driver.
Key functions:
gnssmax_generic_read
- GNSS MAX data reading function.gnssmax_reset
- GNSS MAX reset function.gnssmax_get_pps
- GNSS MAX reads timestamp pin state.
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 main.c
* @brief GNSSMAX Click Example.
*
* # Description
* This example showcases device abillity to read data outputed
* from device and show it's coordinates and altitude when connected.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes host communication modules, additioaln GPIO's used
* for control of device and resets device.
*
* ## Application Task
* Reads data from device and wait's untill device is connected.
* While not connected it will log '.'. When conneceted and received
* data for latitude, longitude, and altitude it will log that data
* parsed from "GNGGA" command.
*
* ## Additional Function
* - static void gnssmax_clear_app_buf ( void )
* - static err_t gnssmax_process ( void )
* - static err_t gnssmax_cmd_parser ( char *cmd )
* - static err_t gnssmax_element_parser ( char *cmd, uint8_t element, char *element_data )
*
* @note
* For the device to connect it can take it from 1 to 10 minutes.
* Time to connect is depending on weather.
*
* @author Luka Filipovic
*
*/
#include "board.h"
#include "log.h"
#include "gnssmax.h"
#define PROCESS_BUFFER_SIZE 700
#define DATA_BUFFER_SIZE 30
#define RSP_GNGGA "GNGGA"
#define RSP_START '$'
#define RSP_SEPARATOR ','
#define RSP_GNGGA_LATITUDE_ELEMENT 2
#define RSP_GNGGA_LONGITUDE_ELEMENT 4
#define RSP_GNGGA_ALTITUDE_ELEMENT 9
static gnssmax_t gnssmax;
static log_t logger;
static char app_buf[ PROCESS_BUFFER_SIZE ] = { 0 };
static int32_t app_buf_len = 0;
static int32_t app_buf_cnt = 0;
static char latitude_data[ DATA_BUFFER_SIZE ] = { 0 };
static char longitude_data[ DATA_BUFFER_SIZE ] = { 0 };
static char altitude_data[ DATA_BUFFER_SIZE ] = { 0 };
err_t last_error_flag;
/**
* @brief GNSSMAX clearing application buffer.
* @details This function clears memory of application buffer and reset it's length and counter.
*/
static void gnssmax_clear_app_buf ( void );
/**
* @brief GNSSMAX data reading function.
* @details This function reads data from device and concats data to application buffer.
*
* @return @li @c GNSSMAX_OK - Read some data.
* @li @c GNSSMAX_ERROR - Nothing is read.
* @li @c GNSSMAX_ERROR_NO_DATA - Application buffer overflow.
*
* See #err_t definition for detailed explanation.
*/
static err_t gnssmax_process ( void );
/**
* @brief GNSSMAX command data parser.
* @details This function searches @b app_buf for @b cmd and logs data of that command.
*
* @param[in] cmd : Command to parese.
*
* @return @li @c GNSSMAX_OK - Parsed data succes.
* @li @c GNSSMAX_ERROR - No @b cmd in application buffer.
*
* See #err_t definition for detailed explanation.
*/
static err_t gnssmax_cmd_parser ( char *cmd );
/**
* @brief GNSSMAX element of command data parser.
* @details This function searches @b app_buf for @b cmd and it's
* @b element and copies data to @b element_data buffer.
*
* @return @li @c GNSSMAX_OK - Read some data.
* @li @c GNSSMAX_ERROR - No @b cmd in application buffer.
* @li @c GNSSMAX_ERROR_NO_DATA - No data for @b element in @b cmd.
* @li @c GNSSMAX_ERROR_OVERFLOW - Data buffer overflow.
*
* See #err_t definition for detailed explanation.
*/
static err_t gnssmax_element_parser ( char *cmd, uint8_t element, char *element_data );
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
gnssmax_cfg_t gnssmax_cfg; /**< Click config object. */
/**
* 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 " );
Delay_ms( 500 );
// Click initialization.
gnssmax_cfg_setup( &gnssmax_cfg );
GNSSMAX_MAP_MIKROBUS( gnssmax_cfg, MIKROBUS_1 );
err_t init_flag = gnssmax_init( &gnssmax, &gnssmax_cfg );
if ( init_flag == UART_ERROR )
{
log_error( &logger, " Application Init Error. " );
log_info( &logger, " Please, run program again... " );
for ( ; ; );
}
gnssmax_default_cfg( &gnssmax );
last_error_flag = GNSSMAX_OK;
log_info( &logger, " Application Task " );
Delay_ms( 500 );
}
void application_task ( void )
{
gnssmax_process();
err_t error_flag = gnssmax_element_parser( RSP_GNGGA, RSP_GNGGA_LATITUDE_ELEMENT,
latitude_data );
error_flag |= gnssmax_element_parser( RSP_GNGGA, RSP_GNGGA_LONGITUDE_ELEMENT,
longitude_data );
error_flag |= gnssmax_element_parser( RSP_GNGGA, RSP_GNGGA_ALTITUDE_ELEMENT,
altitude_data );
if ( error_flag == GNSSMAX_OK )
{
if ( last_error_flag != GNSSMAX_OK )
{
log_printf( &logger, "\r\n" );
}
log_printf( &logger, ">Latitude:\r\n - deg: %.2s \r\n - min: %s\r\n",
latitude_data, &latitude_data[ 2 ] );
log_printf( &logger, ">Longitude:\r\n - deg: %.3s \r\n - min: %s\r\n",
longitude_data, &longitude_data[ 3 ] );
log_printf( &logger, ">Altitude:\r\n - %sm\r\n",
altitude_data );
log_printf( &logger, "----------------------------------------\r\n" );
}
else if ( error_flag < GNSSMAX_ERROR )
{
if ( last_error_flag == GNSSMAX_OK )
{
log_printf( &logger, "Waiting for data " );
}
log_printf( &logger, "." );
}
if ( error_flag != GNSSMAX_ERROR )
{
last_error_flag = error_flag;
gnssmax_clear_app_buf( );
}
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
static void gnssmax_clear_app_buf ( void )
{
memset( app_buf, 0, app_buf_len );
app_buf_len = 0;
app_buf_cnt = 0;
}
static err_t gnssmax_process ( void )
{
int32_t rx_size;
char rx_buff[ PROCESS_BUFFER_SIZE ] = { 0 };
rx_size = gnssmax_generic_read( &gnssmax, rx_buff, PROCESS_BUFFER_SIZE );
if ( rx_size > 0 )
{
int32_t buf_cnt = 0;
if ( ( app_buf_len + rx_size ) > PROCESS_BUFFER_SIZE )
{
gnssmax_clear_app_buf( );
return GNSSMAX_ERROR_NO_DATA;
}
else
{
buf_cnt = app_buf_len;
app_buf_len += rx_size;
}
for ( int32_t rx_cnt = 0; rx_cnt < rx_size; rx_cnt++ )
{
if ( rx_buff[ rx_cnt ] != 0 )
{
app_buf[ ( buf_cnt + rx_cnt ) ] = rx_buff[ rx_cnt ];
}
else
{
app_buf_len--;
buf_cnt--;
}
}
return GNSSMAX_OK;
}
return GNSSMAX_ERROR;
}
static err_t gnssmax_cmd_parser ( char *cmd )
{
err_t ret_flag = GNSSMAX_OK;
if ( strstr( app_buf, cmd ) != GNSSMAX_OK )
{
char * __generic_ptr gngga_ptr;
gngga_ptr = strstr( app_buf, cmd );
while ( strchr( gngga_ptr, RSP_START ) == GNSSMAX_OK )
{
gnssmax_process();
}
for ( ; ; )
{
log_printf( &logger, "%c", *gngga_ptr );
gngga_ptr++;
if ( ( *gngga_ptr == RSP_START ) )
{
break;
}
}
}
else
{
ret_flag = GNSSMAX_ERROR;
}
return ret_flag;
}
static err_t gnssmax_element_parser ( char *cmd, uint8_t element, char *element_data )
{
err_t ret_flag = 0;
if ( strstr( app_buf, cmd ) != 0 )
{
uint8_t element_cnt = 0;
char data_buf[ DATA_BUFFER_SIZE ] = { 0 };
uint8_t data_cnt = 0;
char * __generic_ptr gngga_ptr;
gngga_ptr = strstr( app_buf, cmd );
while ( strchr( gngga_ptr, RSP_START ) == GNSSMAX_OK )
{
gnssmax_process();
}
for ( ; ; )
{
if ( ( *gngga_ptr == RSP_START ) )
{
ret_flag = GNSSMAX_ERROR_NO_DATA;
break;
}
if ( *gngga_ptr == RSP_SEPARATOR )
{
if (element_cnt == element)
{
if ( data_cnt == 0 )
{
ret_flag = GNSSMAX_ERROR_NO_DATA;
}
strcpy( element_data, data_buf );
break;
}
element_cnt++;
}
if ( ( element == element_cnt ) && ( *gngga_ptr != RSP_SEPARATOR ) )
{
data_buf[ data_cnt ] = *gngga_ptr;
data_cnt++;
if ( data_cnt >= DATA_BUFFER_SIZE )
{
ret_flag = GNSSMAX_ERROR_OVERFLOW;
break;
}
}
gngga_ptr++;
}
}
else
{
ret_flag = GNSSMAX_ERROR;
}
return ret_flag;
}
// ------------------------------------------------------------------------ END
Additional Support
Resources
Category:GPS/GNSS