OEM&ODM
  • Broadcast Interval and Connection Interval
    Broadcast Interval and Connection Interval Mar 24, 2022
    Broadcast Interval and Connection Interval Broadcast interval: the settable range is 20 ms to 1024 ms. The maximum broadcast interval of RF-star modules is 5 s. Because the broadcast interval is the main factor affecting the power consumption. The bigger the broadcast interval, the lower the power consumption. However, if the module enables a bigger broadcast interval, the connection establishment and the scan operation will work slowly. Under the broadcast interval of 5 s, there may be no connection that can be built. RF-star recommends the maximum broadcast interval is 2 s. Connection interval: the settable range is 8 ms to 425 s. The default connection interval between RF-star modules is 20 ms. The connection interval between the BLE module and mobile phone will be different. The default minimum connection interval of the iOS system is 30 ms, and Andriod can reach 20 ms and the below.
    Read More
  • Hardware Flow Control and Software Flow Control
    Hardware Flow Control and Software Flow Control Mar 24, 2022
    Hardware Flow Control and Software Flow Control Hardware flow control: RF-star Nordic Semiconductor-based module list: nRF52832: RF-BM-ND04, RF-BM-ND04I, RF-BM-ND08 nRF52810: RF-BM-ND04C, RF-BM-ND04CI, RF-BM-ND08C nRF52805: RF-BM-ND09, RF-BM-ND09A nRF52811: RF-BM-ND04A, RF-BM-ND08A nRF52833: RF-BM-ND07 nRF52840: RF-BM-ND05, RF-BM-ND05I, RF-BM-ND06 Silicon Labs-based module list EFR32BG22C112: RF-BM-BG22A1 EFR32BG22C224: RF-BM-BG22A3 Software flow control: RF-star series module: RS02A1-A: RSBRS02AA, RSBRS02AI RS02A1-B: RSBRS02ABR, RSBRS02ABRI TI series module: CC2640R2FRSM: RF-BM-4044B1, RF-BM-4044B2, RF-BM-4044B4, RF-BM-4044B5 CC2640R2FRGZ: RF-BM-4077B1 CC2640R2F-Q1: RF-BM-4077B2 CC2640R2LRHB: RF-BM-4055B1L CC2640R2LRGZ: RF-BM-4077B1L In order to make sure the normal receiving and transmitting function of the BLE modules, the hardware flow control must care about the CTS pin, while the software flow control must care about BRTS.
    Read More
  • MTU, Connection Interval and Transparent Transmission Rate
    MTU, Connection Interval and Transparent Transmission Rate Mar 24, 2022
    MTU, Connection Interval and Transparent Transmission Rate MTU is the maximum transmission unit during the BLE data transmission. MTU is set to limit the maximum data length of BLE devices. The MTU of BLE4.0 is 23 bytes and BLE5.0 is 251 bytes.   For BLE4.0, the maximum data package should be (MTU-3) bytes, that is, the data length should be 20 bytes at most. For BLE4.2, the communication rate is increased according to the raise of the MTU. For BLE5.0, MTU will be different from the SDK of different manufacturers. Nordic nRF52 series: 247 bytes; RF-star RS02Ax series: 251 bytes; SiliconLabs EFR32BG22 series: 250 bytes; TI CC26XX series: 251 bytes. Different mobile phone systems have different MTU. Android is 251 bytes, while iOS is 185 bytes. Each BLE packet is (MTU-3) bytes. For RF-star serial port module, the transparent transmission rate is one of the most important factors that the users will take into consideration. So, how can we achieve the biggest transparent transmission rate? The connection status of the BLE serial port module is the periodic operation of sleep events and connection events. The time between two events is the connection interval. The data only can be sent out when the connection event comes. There is no chance to send out the data during the sleep event. The smaller the connection interval, the closer the connection events. Then, more opportunities to send data and more data is sent. At most 6~7 frames of data can be sent during each connection event. So, when more data can be sent in one frame of data, more data can be transmitted during one connection event. One frame of data means the MTU. The bigger MTU, the higher the transparent transmission rate. When we test the limit transparent transmission rate, we usually shorten the connection interval and increase the MTU. What’s more, there are so many other factors that can influence the rate, including baud rate, single sending interval of serial port data.
    Read More
  • The Authentication and Pairing Function of BLE Module
    The Authentication and Pairing Function of BLE Module Mar 24, 2022
    The Authentication and Pairing Function of BLE Module From the view of protocol: Authentication: The authentication is used for checking device identity by UART data, which is only effective for APP. How to use the authentication function? Enable the authentication function and set a password for authentication for the slave device. When the master connects to the slave, the master must send the pre-set password in the authentication channel. After the slave receives the password, it will check whether the password is the same as the pre-set one. If yes, the connection will be kept if no, the connection will be disabled. Pairing: The pairing is supported by the Bluetooth underlying protocol. It will save the paired device in the pairing list. No matter what device for the master part is: a module or a mobile phone, it supports the paring function. For the function: Authentication: The authentication requires the password in the channel for each connection. Pairing: The pairing supports the direct connection without a password after the first pairing is set. Only the MAC address of the pre-pairing device is deleted in the pairing list, there will be a password needed to set the connection again,
    Read More
  • Basic Wiring of Bluetooth Module Pins
    Basic Wiring of Bluetooth Module Pins Mar 16, 2022
    Basic Wiring of Bluetooth Module Pins RF-star series module: RS02A1-A: RSBRS02AA, RSBRS02AI RS02A1-B: RSBRS02ABR, RSBRS02ABRI The pins need to be connected during transparent transmission test and debug: VCC, GND, TX, RX, BRTS, BCTS, EN (Active low for BRTS, BCTS and EN pins). The pins need to be connected during broadcasting: VCC, GND, EN. The pins need to be connected during flashing firmware (by J-Link or offline writer): SWC, SWD, VCC, GND, RES. TI series module: CC2540: RF-BM-S01, RF-BM-S02, RF-BM-S02I CC2541: RF-CC2540A1, RF-BM-S01A, RF-BM-S02A, RF-BMPA-2541B1 CC2640R2FRSM: RF-BM-4044B1, RF-BM-4044B2, RF-BM-4044B4, RF-BM-4044B5 CC2640R2FRGZ: RF-BM-4077B1 CC2640R2F-Q1: RF-BM-4077B2 CC2640R2LRHB: RF-BM-4055B1L CC2640R2LRGZ: RF-BM-4077B1L The pins need to be connected during transparent transmission test and debug: VCC, GND, TX, RX, RES, BRTS, BCTS, EN (Active low for BRTS, BCTS and EN pins). The pins need to be connected during flashing firmware: CC2540/CC2541: TDI, TDO (by CC-Debugger) CC2640: TMS, TCK (by XDS110) Nordic series module, Siliconlabs series module, TI CC26X2 series module: Nordic series modules: nRF52832: RF-BM-ND04, RF-BM-ND04I, RF-BM-ND08 nRF52810: RF-BM-ND04C, RF-BM-ND04CI, RF-BM-ND08C nRF52805: RF-BM-ND09, RF-BM-ND09A nRF52811: RF-BM-ND04A, RF-BM-ND08A nRF52833: RF-BM-ND07 nRF52840: RF-BM-ND05, RF-BM-ND05I, RF-BM-ND06 Silicon Labs series modules EFR32BG22C112: RF-BM-BG22A1 EFR32BG22C224: RF-BM-BG22A3 TI series modules: CC2642R: RF-BM-2642B1 CC2652R: RF-BM-2652B1 The pins need to be connected during transparent transmission test and debug: VCC, GND, TX, RX, RES, RTS, CTS (Active low for RTS and CTS). The pins need to be connected during broadcasting (Beacon): VCC, GND. The pins need to be connected during flashing firmware (by J-Link): SWC, SWD, VCC, GND, RES. Remark: Because each module has different definitions of BRTS, BCTS and CTS, RTS, it is recommended to connect those pins to avoid the problem that may be caused during the transparent transmission. Some of RF-star BLE modules (a few modules do not) have a sleep status indicator pin and a connection status indicator pin. Those pins are used to know the current Bluetooth module status or use an LED to indicate the current Bluetooth status through MCU.
    Read More
  • What the difference between serial module and direct-driven module
    What the difference between serial module and direct-driven module Mar 16, 2022
    What the difference between serial module and direct-driven module The serial module is to forward data. And the direct-driven module can directly control peripheral circuits. The serial module is the bridge between the connected devices and the mobile devices, which enables two-way communication. The direct-driven module can be regarded as the CPU, the customer only needs to do the programming to drive the peripheral circuits. Direct-driven module: RF-star series modules: RS02A1-A: RSBRS02AA, RSBRS02AI RS02A1-B: RSBRS02ABR, RSBRS02ABRI TI series modules: CC2540: RF-BM-S01, RF-BM-S02, RF-BM-S02I CC2541: RF-CC2540A1, RF-BM-S01A, RF-BM-S02A
    Read More
  • Q & A on UART Assistant
    Q & A on UART Assistant Mar 16, 2022
    Q & A on UART Assistant ①Pls choose and click RTS and CTS on the UART Assistant (called DTR as well). For example: ②Almost all of the RF-star BLE modules have the feedback string after power-on. If the module doesn’t have any string printed out after power on, pls try to reset the module or re-power on the module. If the above operations are done and there is no string shown, pls check whether you choose the right UART port, because there may several UART ports working at the same time, ③If the string is messy, pls check whether you choose the right baud rate. ④Dring using AT commands, pls note whether the module needs the CRLF at the end of the AT commands. RF-star series and some of TI series modules do not need CRLF. RF-star series modules: RS02A1-A: RSBRS02AA, RSBRS02AI RS02A1-B: RSBRS02ABR, RSBRS02ABRI TI series modules: CC2640R2FRSM: RF-BM-4044B1, RF-BM-4044B2, RF-BM-4044B4, RF-BM-4044B5 CC2640R2FRGZ: RF-BM-4077B1 CC2640R2F-Q1: RF-BM-4077B2 CC2640R2LRHB: RF-BM-4055B1L CC2640R2LRGZ: RF-BM-4077B1L Nordic series, Silicon Labs series and some of TI series modules need to use “+++” to enter the AT command mode. All the AT commands need to be followed by a CFRL, then the modules can work normally. Under AT command mode, the module only can receive the data, but cannot send the data. If you would like to do the data transparent transmission, pls exit AT command mode at first. Nordic series modules: nRF52832: RF-BM-ND04, RF-BM-ND04I, RF-BM-ND08 nRF52810: RF-BM-ND04C, RF-BM-ND04CI, RF-BM-ND08C nRF52805: RF-BM-ND09, RF-BM-ND09A nRF52811: RF-BM-ND04A, RF-BM-ND08A nRF52833: RF-BM-ND07 nRF52840: RF-BM-ND05, RF-BM-ND05I, RF-BM-ND06 Silicon Labs series modules EFR32BG22C112: RF-BM-BG22A1 EFR32BG22C224: RF-BM-BG22A3 TI series modules: CC2642R: RF-BM-2642B1 CC2652R: RF-BM-2652B1
    Read More
  • OTA Upgrade
    OTA Upgrade Feb 17, 2022
    OTA Upgrade Here is the BLE module list with OTA function. a) RF-star-based modules: RS02A1-A, RS02A1-B RS02A1-A: RSBRS02AA, RSBRS02AI RS02A1-B: RSBRS02ABR, RSBRS02ABRI APP: RF-star OTA. Support batch upgrading. Contact RF-star. b) Silicon Labs-based modules: EFR32BG22 series: EFR32BG22C112: RF-BM-BG22A1 EFR32BG22C224: RF-BM-BG22A3 APP: EFR Connect c) Nordic Semiconductor-based modules: nRF52810, nRF52832, nRF52840, nRF52811, nRF52833 and nRF52805: nRF52832: RF-BM-ND04, RF-BM-ND04I, RF-BM-ND08 nRF52810: RF-BM-ND04C, RF-BM-ND04CI, RF-BM-ND08C nRF52805: RF-BM-ND09, RF-BM-ND09A nRF52811: RF-BM-ND04A, RF-BM-ND08A nRF52833: RF-BM-ND07 nRF52840: RF-BM-ND05, RF-BM-ND05I, RF-BM-ND06 APP: nRF Connect d) TI-based modules: CC2642R, CC2652R CC2642R: RF-BM-2642B1 CC2652R: RF-BM-2652B1 Remark: Due to different SDKs, even the module is the same one, it cannot be upgraded. They can only upgrade iteratively on the original firmware.
    Read More
  • The FAQ of TI ZigBee
    The FAQ of TI ZigBee Oct 29, 2021
    Written by RF-star senior adviser XCODER (a We-Media essayist) 1. Due to the differences among the versions of TI ZigBee protocol stack, how to choose the right protocol stack for product development? TI ZigBee protocol stack Z-Stack is developed from Z-Stack 0.1 to Z-Stack 2.5.1a, and later Z-Stack Home 1.2.1, Z-Stack Lighting 1.0.2, Z-Stack Energy 1.0. 1, Z-Stack Mesh 1.0.0. In the process of upgrading the protocol stack, TI has mainly done two aspects of the protocol stack. 1) Add some new features according to the ZigBee Specification of the ZigBee Alliance. For example, ZigBee 2007 is a tree-shaped routing. In ZigBee Pro, Mesh routing is coming out, and routing algorithms such as MTO and Source Routing are proposed. TI adds corresponding new features to the protocol stack is to fix some related bugs in specs, such as those with ambiguous descriptions. 2) To fix the bug in the TI ZigBee protocol stack itself. The difference of the protocol stack between a version and the previous version can be found in the Release Note. After the version of Z-Stack 2.5.1a, TI protocol stack did not continue to be released directly in the form of Z-Stack 2.6.x, but was released in the form of Application Profile. The reason is that TI wants developers to choose more targeted protocol stack for development according to the actual application. Protocol stack like Z-stack Home 1.2.1 mainly includes the following two parts. 1) The Core Stack, the beginning of this part is the continuation version of Z-Stack 2.5.1a and later, can be found in the Z-Stack Core Release Notes.txt, Version 2.6.2. 2) The application protocol stack is related to the profile, which is mainly related to the actual application. The Home Automation protocol stack is all related to the implementation of the ZigBee Home Automation Profile. Similarly, Z-Stack Lighting 1.0.2 and Z-Stack Energy 1.0.1 are also a Core Stack with an application profile. a.Z-Stack Home 1.2.2a is developed for smart home related products. b.Z-Stack Lighting 1.0.2 is developed for ZLL related products. c.Z-Stack Energy 1.0.1 is developed for smart energy, Meter, In Home Display, and other related products. d.Z-Stack Mesh 1.0.0 is developed for products related to private applications, which only uses standard ZigBee protocol related features, such as Mesh routing, etc. The application layer is defined by the developer. After the ZigBee Alliance released the ZigBee 3.0 protocol, the latest ZigBee protocol stack is Z-Stack 3.0, which currently supports CC2530, CC2538, CC2652R, CC265P. 2.How to do ZigBee testing and certification of products, what needs to be understood and what process needs to be followed? There is an example about the development of standard ZigBee Home Automation related products. To begin with, when developers develop products, they must develop products according to the products described in the ZigBee Home Automation Profile Specification which can be downloaded at www.zigbee.org. After completing ...
    Read More
1 2

A total of 2 pages

Leave A Message

Leave A Message
If you are interested in our products and want to know more details, please leave a message here, we will reply you as soon as we can.

Home

Product

skype

whatsapp