中级
30 分钟

使用 AK1595 和 PIC32MZ2048EFH100 实现广播辉煌

低能耗蓝牙发射器

BLE TX Click with Flip&Click PIC32MZ

已发布 6月 24, 2024

点击板

BLE TX Click

开发板

Flip&Click PIC32MZ

编译器

NECTO Studio

微控制器单元

PIC32MZ2048EFH100

我们的尖端BLE发射器使您能够以无与伦比的效率广播信号,实现设备之间的无缝通信和数据交换,适用于各种无线应用。

A

A

硬件概览

它是如何工作的?

BLE TX Click基于AKM Semiconductor的低功耗蓝牙5.2发射器AK1595。AK1595集成了专有的算法软件,可以实现蓝牙低功耗发射器(BLE TX)功能,无需特定的开发环境和编程,适用于传统蓝牙SoC所需的。BLE功能可以通过简单地将要传输的数据设置到内置寄存器中来实现,非常适合在现有微处理器上添加BLE功能的应用。AK1595具有高速响应性,在从待机状态启动广告传输后的3毫秒内开始响应。这一事实允许通过控制BLE广告传输(间歇传输)处于整个待机状态,从而将传输之间的功耗保持在待机状态的低功耗水平(典型值为15nA)。此外,它支持1Mbps GFSK +/-调制,其中调制时钟是从32MHz板载时钟发生器生成的。BLE TX Click提供了使用UART和I2C接口的可能性。

AK1595通过三个GPIO引脚配置其所选的接口,这些引脚标记为U/I,S1和S0,并连接到mikroBUS™插座上的CS、AN和PWM引脚。除了mikroBUS™插座上的I/O引脚根据设置的逻辑电平激活特定的串行通信之外,此Click board™还具有两个用于选择硬件接口本身的跳线。可以通过将标记为COMM SEL的SMD跳线设置到适当的位置来进行选择。注意,所有跳线的位置必须在同一侧,否则Click board™可能会失去响应。当选择UART接口时,当S1引脚检测到低于1μs的低逻辑状态时,UART控制器块将被初始化。此外,通过在S0引脚上设置特定的逻辑电平,用户可以设置UART通信的波特率(将S0设置为低逻辑状态以获得9600bps,或将S0设置为高逻辑状态以获得115200bps)。AK1595

的I2C接口支持标准模式,时钟频率高达100kHz,以及快速模式,时钟频率高达400kHz。此外,此Click board™具有一个Reset引脚,路由到mikroBUS™插座上的RST引脚,该引脚将寄存器保持在其默认状态,直到RST引脚被设置为逻辑低电平状态。BLE TX Click具有一个迷你同轴N.FL系列天线连接器,结合IPEX-SMA电缆,允许连接适当的天线,例如WIFI Rubber Antenna 2.4GHz右角SMA或WIFI Rubber Antenna,以改善范围和接收信号强度。此Click board™只能使用3.3V逻辑电压级别运行。在使用具有不同逻辑电平的MCU之前,必须对电路板执行适当的逻辑电压级别转换。此外,它配备了一个包含功能和示例代码的库,可用作进一步开发的参考。

BLE TX Click top side image
BLE TX Click bottom side image

功能概述

开发板

Flip&Click PIC32MZ 是一款紧凑型开发板,设计为一套完整的解决方案,它将 Click 板™的灵活性带给您喜爱的微控制器,使其成为实现您想法的完美入门套件。它配备了一款板载 32 位 PIC32MZ 微控制器,Microchip 的 PIC32MZ2048EFH100,四个 mikroBUS™ 插槽用于 Click 板™连接,两个 USB 连接器,LED 指示灯,按钮,调试器/程序员连接器,以及两个与 Arduino-UNO 引脚兼容的头部。得益于创

新的制造技术,它允许您快速构建具有独特功能和特性的小工具。Flip&Click PIC32MZ 开发套件的每个部分都包含了使同一板块运行最高效的必要组件。此外,还可以选择 Flip&Click PIC32MZ 的编程方式,使用 chipKIT 引导程序(Arduino 风格的开发环境)或我们的 USB HID 引导程序,使用 mikroC、mikroBasic 和 mikroPascal for PIC32。该套件包括一个通过 USB 类型-C(USB-C)连接器的干净且调

节过的电源供应模块。所有 mikroBUS™ 本身支持的 通信方法都在这块板上,包括已经建立良好的 mikroBUS™ 插槽、用户可配置的按钮和 LED 指示灯。Flip&Click PIC32MZ 开发套件允许您在几分钟内创建新的应用程序。它由 Mikroe 软件工具原生支持,得益于大量不同的 Click 板™(超过一千块板),其数量每天都在增长,它涵盖了原型制作的许多方面。

Flip&Click PIC32MZ double image

微控制器概述 

MCU卡片 / MCU

default

建筑

PIC32

MCU 内存 (KB)

2048

硅供应商

Microchip

引脚数

100

RAM (字节)

524288

你完善了我!

配件

WiFi 2.4GHz/5.4GHz Active FPC天线(W3918B0100)是一款来自Pulse Electronics的主动式平板天线,非常适用于WiFi 6E、蓝牙、ZigBee、ISM频段无线电、物联网、机器对机器通信等应用。该平板天线具有2.4-2.5GHz和4.9-5.925GHz的双频能力,中心频率为2.4GHz和5.4GHz, typ 3dBi的增益和全向辐射特性。尺寸为35.2x8.5x0.15mm,天线体积小巧高效,额定阻抗为50Ω,设计用于与您现有的设置无缝配合。天线采用的FPC材料确保了耐用性和可靠性,额定功率为2W,可以信赖其稳定性能。U.FL连接器类型和10mm的电缆长度使其易于集成到您的系统中,凭借其出色的性能,WiFi 2.4GHz/5.4GHz Active FPC天线是满足您无线通信和网络需求的完美选择。

BLE TX Click accessories image

使用的MCU引脚

mikroBUS™映射器

UART Initialization
RB11
AN
Reset
RE2
RST
Serial Communication Activation
RA0
CS
NC
NC
SCK
NC
NC
MISO
NC
NC
MOSI
Power Supply
3.3V
3.3V
Ground
GND
GND
UART Baud Rate Selection
RC14
PWM
NC
NC
INT
UART TX
RE3
TX
UART RX
RG9
RX
I2C Clock
RA2
SCL
I2C Data
RA3
SDA
NC
NC
5V
Ground
GND
GND
1

“仔细看看!”

Click board™ 原理图

BLE TX Click Schematic schematic

一步一步来

项目组装

Flip&Click PIC32MZ front image hardware assembly

从选择您的开发板和Click板™开始。以Flip&Click PIC32MZ作为您的开发板开始。

Flip&Click PIC32MZ front image hardware assembly
GNSS2 Click front image hardware assembly
Prog-cut hardware assembly
GNSS2 Click complete accessories setup image hardware assembly
Flip&Click PIC32MZ MB1 Access - upright/background hardware assembly
Necto image step 2 hardware assembly
Necto image step 3 hardware assembly
Necto image step 4 hardware assembly
Necto image step 5 hardware assembly
Necto image step 6 hardware assembly
Flip&Click PIC32MZ MCU step hardware assembly
Necto No Display image step 8 hardware assembly
Necto image step 9 hardware assembly
Necto image step 10 hardware assembly
Debug Image Necto Step hardware assembly

实时跟踪您的结果

应用程序输出

1. 应用程序输出 - 在调试模式下,“应用程序输出”窗口支持实时数据监控,直接提供执行结果的可视化。请按照提供的教程正确配置环境,以确保数据正确显示。

2. UART 终端 - 使用UART Terminal通过USB to UART converter监视数据传输,实现Click board™与开发系统之间的直接通信。请根据项目需求配置波特率和其他串行设置,以确保正常运行。有关分步设置说明,请参考提供的教程

3. Plot 输出 - Plot功能提供了一种强大的方式来可视化实时传感器数据,使趋势分析、调试和多个数据点的对比变得更加直观。要正确设置,请按照提供的教程,其中包含使用Plot功能显示Click board™读数的分步示例。在代码中使用Plot功能时,请使用以下函数:plot(insert_graph_name, variable_name);。这是一个通用格式,用户需要将“insert_graph_name”替换为实际图表名称,并将“variable_name”替换为要显示的参数。

软件支持

库描述

该库包含 BLE TX Click 驱动程序的 API。

关键功能:

  • bletx_start_advertising - BLE TX启动广告功能

  • bletx_set_configuration - BLE TX配置设置功能

  • bletx_create_eddystone_uri - BLE TX创建Eddystone™ URI数据包功能

开源

代码示例

完整的应用程序代码和一个现成的项目可以通过NECTO Studio包管理器直接安装到NECTO Studio 应用程序代码也可以在MIKROE的GitHub账户中找到。

/*!
 * @file main.c
 * @brief BleTx Click example
 *
 * # Description
 * This library contains API for the BLE TX Click driver.
 * This example processes data from BLE TX Click, BLE TX Click 
 * Bluetooth® Low Energy compliant advertising transmission 
 * can be achieved by simply configuring the transmission power, 
 * data, and transmission - start trigger.
 *
 * The demo application is composed of two sections :
 *
 * ## Application Init
 * Initialization of I2C module and log UART.
 * Initializes driver and set performs the default configuration.
 * Configure Bluetooth Low Energy Beacons to transmit so-called advertising frames.
 * Configuration of the Eddystone URI, UID, or TLM 
 * Bluetooth Low Energy Beacons profile task depends on uncommented code.
 * Eddystone ( URI ) : broadcasts a URL of at most 15 characters 
 * that redirects to a website that is secured using SSL.
 * Eddystone ( UID ) : broadcasts an identifying code 
 * that allows apps to retrieve information from app servers. 
 * Eddystone ( TLM ) : broadcasts information about the beacon,
 * include battery level, sensor data, or other relevant information 
 * to beacon administrators.
 *
 * ## Application Task
 * This is an example that shows the use of a BLE TX Click board™.
 * In this example, the application turns the selected advertising frames
 * ON and OFF for a period of 10 seconds.
 *
 * @note
 * For scanning BLE TX Click board™ BLE Scanner is a recommended Android application 
 * and you can find it at the link:
 * https://play.google.com/store/apps/details?id=com.macdom.ble.blescanner
 * 
 * @author Nenad Filipovic
 *
 */

#include "board.h"
#include "log.h"
#include "bletx.h"

static bletx_t bletx;
static log_t logger;

#define URI
// #define UID
// #define TLM

bletx_adv_cfg_t adv_cfg;
bletx_eddystone_data_t adv_data;

void application_init ( void ) 
{
    log_cfg_t log_cfg;      /**< Logger config object. */
    bletx_cfg_t bletx_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 " );

    // Click initialization.
    bletx_cfg_setup( &bletx_cfg );
    BLETX_MAP_MIKROBUS( bletx_cfg, MIKROBUS_1 );
    if ( I2C_MASTER_ERROR == bletx_init( &bletx, &bletx_cfg ) ) 
    {
        log_error( &logger, " Communication init." );
        for ( ; ; );
    }

    bletx_default_cfg ( &bletx );
    Delay_ms ( 1000 );
    
    adv_cfg.adv_ch_1_frequency = ADVCH1_37_Ch_2402_MHz;
    adv_cfg.adv_ch_2_frequency = ADVCH2_38_Ch_2426_MHz;
    adv_cfg.adv_ch_3_frequency = ADVCH3_39_Ch_2480_MHz;
    adv_cfg.tx_output_power = TX_POWER_0_dBm;
    adv_cfg.txdata_loop = 0;
    adv_cfg.txdata_cw = 0;
    adv_cfg.eventnum = 0;
    adv_cfg.advdelay_enb = BLETX_ADV_DELAY_ENABLE;
    adv_cfg.avdintvl_interval_ms = 0;
    adv_cfg.crc_enb = BLETX_CRC_ENABLE;
    adv_cfg.white_enb = BLETX_WHITE_ENABLE;
    adv_cfg.pdu_len = 39;
    
    adv_cfg.uuid[ 0 ] = 0x11;
    adv_cfg.uuid[ 1 ] = 0x22;
    adv_cfg.uuid[ 2 ] = 0x33;
    adv_cfg.uuid[ 3 ] = 0x44;
    adv_cfg.uuid[ 4 ] = 0x55;
    adv_cfg.uuid[ 5 ] = 0x66;
    
    if ( BLETX_OK != bletx_set_configuration( &bletx, adv_cfg ) ) 
    {
        log_error( &logger, " Set configuration." );
        for ( ; ; );
    }
    Delay_ms ( 100 );
    
#ifdef URI
    adv_data.length_of_service_list = 3;
    adv_data.param_service_list = 3;
    adv_data.eddystone_id = BLETX_EDDYSTONE_SERVICE_UUID;
    adv_data.length_of_service_data = 13;
    adv_data.service_data = BLETX_EDDYSTONE_SERVICE_DATA_TYPE_VALUE;
    adv_data.frame_type_url = BLETX_EDDYSTONE_FRAME_TYPE_URL;
    adv_data.power = BLETX_TX_POWER_LVL_MODE_LOWEST;
    adv_data.spec_data = BLETX_EDDYSTONE_SPEC_DATA_HTTPS_WWW;
    adv_data.advdata_url[ 0 ] = 'm';
    adv_data.advdata_url[ 1 ] = 'i';
    adv_data.advdata_url[ 2 ] = 'k';
    adv_data.advdata_url[ 3 ] = 'r';
    adv_data.advdata_url[ 4 ] = 'o';
    adv_data.advdata_url[ 5 ] = 'e';
    adv_data.domain = BLETX_CHARACTER_CODES_DOT_COM;
    
    bletx_create_eddystone_uri ( &bletx, adv_data );
#endif

#ifdef UID
    adv_data.length_of_service_list = 3;
    adv_data.param_service_list = 3;
    adv_data.eddystone_id = BLETX_EDDYSTONE_SERVICE_UUID;
    adv_data.length_of_service_data = 23;
    adv_data.service_data = BLETX_EDDYSTONE_SERVICE_DATA_TYPE_VALUE;
    adv_data.frame_type_url = BLETX_EDDYSTONE_FRAME_TYPE_UID;
    adv_data.power = BLETX_TX_POWER_LVL_MODE_LOW;          
    
    adv_data.name_space_id[ 0 ] = 0x01;
    adv_data.name_space_id[ 1 ] = 0x02;
    adv_data.name_space_id[ 2 ] = 0x03;
    adv_data.name_space_id[ 3 ] = 0x04;
    adv_data.name_space_id[ 4 ] = 0x05;
    adv_data.name_space_id[ 5 ] = 0x06;
    adv_data.name_space_id[ 6 ] = 0x07;
    adv_data.name_space_id[ 7 ] = 0x08;
    adv_data.name_space_id[ 8 ] = 0x09;
    adv_data.name_space_id[ 9 ] = 0x0A;
    
    adv_data.instance_id[ 0 ] = 0x01;
    adv_data.instance_id[ 1 ] = 0x23;
    adv_data.instance_id[ 2 ] = 0x45;
    adv_data.instance_id[ 3 ] = 0x67;
    adv_data.instance_id[ 4 ] = 0x89;
    adv_data.instance_id[ 5 ] = 0xAB;
    
    bletx_create_eddystone_uid ( &bletx, adv_data );
#endif

#ifdef TLM
    adv_data.length_of_service_list = 3;
    adv_data.param_service_list = 3;
    adv_data.eddystone_id = BLETX_EDDYSTONE_SERVICE_UUID;
    adv_data.length_of_service_data = 23;
    adv_data.service_data = BLETX_EDDYSTONE_SERVICE_DATA_TYPE_VALUE;
    adv_data.frame_type_url = BLETX_EDDYSTONE_FRAME_TYPE_TLM;
    adv_data.tlm_version = 0;          // TLM version
    adv_data.spec_data = BLETX_EDDYSTONE_SPEC_DATA_TLM;
    
    adv_data.battery_voltage = 3600;
    adv_data.beacon_temperature = 20.21;
    adv_data.pdu_count = 11223344;
    
    bletx_create_eddystone_tlm ( &bletx, adv_data );
#endif
    
    log_info( &logger, " Application Task " );
    Delay_ms ( 100 );
}

void application_task ( void ) 
{  
    log_printf( &logger, ">>>\tStart Advertising \r\n" );
    bletx_start_advertising( &bletx );
    // 10 seconds delay
    Delay_ms ( 1000 );
    Delay_ms ( 1000 );
    Delay_ms ( 1000 );
    Delay_ms ( 1000 );
    Delay_ms ( 1000 );
    Delay_ms ( 1000 );
    Delay_ms ( 1000 );
    Delay_ms ( 1000 );
    Delay_ms ( 1000 );
    Delay_ms ( 1000 );
    
    log_printf( &logger, ">>>\tStop Advertising \r\n" );
    bletx_stop_advertising( &bletx );
    // 10 seconds delay
    Delay_ms ( 1000 );
    Delay_ms ( 1000 );
    Delay_ms ( 1000 );
    Delay_ms ( 1000 );
    Delay_ms ( 1000 );
    Delay_ms ( 1000 );
    Delay_ms ( 1000 );
    Delay_ms ( 1000 );
    Delay_ms ( 1000 );
    Delay_ms ( 1000 );
}

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

额外支持

资源

喜欢这个项目吗?

'购买此套件' 按钮会直接带您进入购物车,您可以在购物车中轻松添加或移除产品。