Showing posts with label FCC. Show all posts
Showing posts with label FCC. Show all posts

Thursday, July 2, 2026

Introducing Raytac's nRF54L15 AT Command Module Series – Pre-loaded firmware with Lower Power Consumption

 [CA, USA/Taipei, Taiwan]


Raytac Group, a worldwide leader in wireless modules, wireless solutions, and a Nordic-recommended third-party module manufacturer, is pleased to announce the official release of the AN54LQ-AT and AN54LV-AT series, our newest Bluetooth® Low Energy AT Command modules built upon Nordic Semiconductor's nRF54L15 ultra-low-power wireless SoC.

Designed for engineers who want to integrate BLE quickly and easily, the AT Command series comes with pre-loaded peripheral (slave) role firmware, enabling straightforward UART communication with a host MCU through simple AT Commands.
Built on Nordic's next-generation nRF54L15 SoC, the series delivers exceptional power efficiency, reducing power consumption by approximately 50% compared to previous-generation nRF52-based AT Command modules.


The nRF54L15 AT Command family is available in five variants to satisfy different RF and mechanical requirements.

AN54LQ Series
- Ceramic chip antenna: AN54LQ-AT (Click here for full product details)
- PCB trace antenna: AN54LQ-PAT (Click here for full product details)
- u.FL connector for external antenna: AN54LQ-UAT (Click here for full product details)

AN54LV Series
- Ceramic chip antenna: AN54LV-AT (Click here for full product details)
- PCB trace antenna: AN54LV-PAT (Click here for full product details)

AT Command Development Kit
- AN54LQ Series: AN54LQ-AT-UART-S (Click here for full product details)
- AN54LV Series AN54LV-AT-UART-S (Click here for full product details)


The standard AN54LQ family measures only 9.5 × 13.7 × 1.8 mm, while the AN54LV family further reduces the footprint to just 6.4 × 8.4 × 1.5 mm, making it an excellent choice for wearable devices, portable products, industrial sensors, medical devices, and other space-constrained applications.

Engineers can integrate Bluetooth communication(peripheral role) into an existing MCU platform without implementing the Bluetooth LE protocol or maintaining a Bluetooth LE firmware stack.

Acting as a seamless bridge between the host MCU and Bluetooth devices, the AT Command module enables easy wireless communication without any complexity of firmware development.



Technical Overview

Category
Specification
Series
AN54LQ and AN54LV
Antenna Options
Chip antenna, PCB antenna, u.FL (external antenna)
Bluetooth® Certification
Bluetooth® 6.0 certified
RF Certifications
FCC, IC, UKCA, CE, TELEC (MIC), KC, SRRC, NCC, RCM, WPC
Processor
128 MHz Arm® Cortex®-M33 processor + 128 MHz RISC-V coprocessor
Security
Enhanced security aligned with EU Cyber Resilience Act (CRA) requirements
Interfaces
UART(Bluetooth Connectivity via UART AT Commands)
Key Features
- Rich AT Command(Peripheral/Slave Role) set, No firmware development needed
- Up to 50% Lower Power Consumption vs. nRF52-based AT Command Modules
- Selectable 1 Mbps / 2 Mbps PHY Data Rate
- Custom UUID Configuration (Hex Format)
- Built-in Power Saving & GPIO Wake-Up Functions
- Advertising/Connection Control
- RSSI, Battery Monitoring & Device Management


List of supported commands

  • Setting of device name
  • Choose data rate of 1Mbps or 2Mbps on-air
  • Set TX output power in 6 levels.
  • Set advertising time
  • Set connection interval under Mode 2
  • Enable/disable advertising
  • 8 sets of UART baud rates
  • Enable/disable UART flow control
  • Enable/disable interface of UART hardware
  • Power-down mode for power saving and GPIO wake-up
  • Recover-to-default setting with hardware and software method
  • System reset of hardware and software
  • Set serial number and retrieve
  • Set or retrieve MAC Address
  • Retrieve ADC value for battery detection, delivering the information through battery service.
  • Enable/disable connection command mode
  • Setting of advertising interval
  • Retrieve RSSI value of the connected


The modules are already in Mass Production.

Please subscribe to Raytac’s Blogger: https://raytaccorp.blogspot.com/ for more upcoming information.

Welcome to send an inquiry to any of the below links:
Raytac Corporation contact form: https://www.raytac.com/contact/
Raytac Corporation mailbox: sales@raytac.com

abietec Inc. contact form: https://www.abietec.com/contact
abietec Inc. mailbox: service@abietec.com

to discuss how Raytac/abietec can support your project.

Let's keep in touch!



Raytac Corporation 勁達國際電子股份有限公司 / Raytac Corporation (USA) / abietec Inc.
A Bluetooth, Wi-Fi, and LoRa Module Maker/ODM & OEM Manufacturer based on
Nordic nRF54; nRF53: nRF52; nRF51; nRF7002
Infineon: CYW55912
NXP: RW610, RW612
Semtech: SX1262

Bluetooth Specification: BT6 ; BT5.4 ; BT5.3 ; BT5.2.
Wi-Fi Specification: Wi-Fi 6
LoRa Specification: LoRaWAN
Zephyr Project Silver Member

All products are FCC/IC/CE/Telec/KC/RCM/SRRC/NCC/WPC/RoHS/Reach Certified.

Tel: +886-2-3234-0208(TW)/+1-626-328-3827(USA)

Wednesday, June 17, 2026

User Manual of Raytac AN54LV-DB-15 (Nordic nRF54L15 Module DevKit) Development & Programming Environment

Want to get started quickly with Raytac's AN54LV-15 module? We provide a simple tutorial to guide you step-by-step through setting up the development and programming environment for the nRF54L15 module Development Board (AN54LV-DB-15) and nRF54L15-DK.


Table of Contents
1. Hardware Environment Setup
2. Software Development Kit Resources and Environment Setup
3. Software/Firmware Application Development
4. Flashing / Programming

Related products:
nRF54L15 SoC Spec  << access link
Nordic nRF54L15 DK  << access link
Raytac AN54LV-DB-15 (Development Kit used in this article) << access link
Zephyr documentation of AN54LV-DB-15 << access link
Raytac AN54LV-DB-U15 (Development Kit with u.FL Connector for external antenna) << access link
Raytac AN54LV-DB-K15 (Development Kit with antenna pin) << access link

User manual of Raytac AN54LQ-DB-15 << access linkNordic nRF54L15-DK


1. Hardware Environment Setup
The required equipments are as follows:

  • 1 x Nordic nRF54L15-DK: PCA10156(1.0.0)
  • 1 x AN54LV-DB-15 (Raytac nRF54L15 module Development Board)
  • 1 x IDC Ribbon Cable
  • 2 x USB Type-C Connection Cables

* Reminder: The "Nordic nRF54L15-DK" and "Raytac AN54LV-DB-15 Development Board" must be used together to proceed with application development and flashing firmware into the Raytac AN54LV-DB-15 development board.

Setup Steps:
Step 1: Connect the J-Link on the Nordic DK with the AN54LV-DB-15 using the IDC ribbon cable.



Make sure to match the red side of the IDC ribbon cable with "1" printed on the AN54LV-DB-15's J-Link socket.


Step 2: Use the Type-C USB cables to supply power to both the nRF54L15-DK and the AN54LV-DB-15.


The outcome should be same as the picture above.

Step 3: AN54LV-DB-15 Schematic(Click on the schematic to zoom in):



2. Software Development Kit Resources and Environment Setup
Software Tool kits & Download Links:
Download nRF Connect for Desktop: Download nRF Connect For Desktop (Please Click Me)
Download nRF Command Line Tools: Download nRF Command Line Tools (Please Click Me)
Download Visual Studio Code(VS Code): Download nRF Command Line Tools (Please Click Me)

Setup Steps:
Step 1: Download the latest version of nRF Connect for Desktop. Choose the Windows 64-bit - version 5.3.1 installer (nrfconnect-setup-5.3.1-x64.exe). Once finished, you will see " nRF Connect for Desktop" on your PC.

Step 2: Download the latest version of nRF Command Line Tools. Choose the Windows X86 64 - version 10.24.2 installer (nrf-command-line-tools-10.24.2-x64.exe)

* Reminder: During the installation of the above two programs, a window may pop up prompting that SEGGER J-LINK needs to be installed or updated concurrently.

If you’re initiating Segger Embedded Studio (SES) application, please check the guideline here(Click me)\


Step 3: Download the latest version of Visual Studio Code (VS Code). Choose Windows VSCodeUserSetup-x64 version 1.122 (VSCodeUserSetup-x64-1.122.1.exe). Once complete, you will see "Visual Studio Code" on your PC.

Step 4: After installation is complete, you can verify the installed packages in your PC's Control Panel under "Programs and Features":



3. Software/Firmware Application Development
You can develop application programs within the VS Code IDE development environment.
Below steps are how to install and select your target SDK version (nRF Connect SDK v3.3.0 in this article):

Step 1: Launch "VS Code"-> Select "nRF Connect" icon/extension on the side menu.


Click "Manage SDKs" and then select "Install SDK".


Step 2: Select "nRF Connect SDK".


Step 3: You will see several available versions of nRF Connect SDK vx.x.x. It is highly recommended to choose and install NCS v3.3.0 or later. In this guide, we select nRF Connect SDK(NCS) v3.3.0.


Step 4: Before starting the download for (NCS)v3.3.0, confirm your preferred target installation pathway.
By default, it is configured to c:\ncs\v3.3.0. Press 'Enter' to confirm.


Step 5: Once the nRF Connect SDK v3.3.0 environment setup finishes successfully, open the Bluetooth sample folder and select the "peripheral_uart" application template, then click "Open".


Step 6: In the "nRF Connect" layout, go to "Applications" --> "Add build configuration".


Under "Board target", look up and select "nrf54l15dk/nrf54l15/cpuapp" --> "Generate and Build".


* Note: You can also choose the board name “raytac_an54lv_db_15/nrf54l15/cpuapp” for subsequent building and development.


After completing the configuration, you will see "Build complete".


Step 7: Compilation completed. Once completed, a binary file named "zephyr.hex" will be generated in your "build" directory.


Step 8: Under the "ACTIONS" interface, you can switch between Build, Debug, and Flash functionalities dynamically.

Build


Debug


Flash


Step 9: CRITICAL BEFORE FLASHING/DEBUGGING: You have to change the VDD voltage configuration on the nRF54L15-DK board to 3.3V.

To do this: Launch "nRF Connect for Desktop" -> choose "Board Configurator" -> click "Open"


Change the VDD target selection value to "3.3V" -> click "Write config".



4. Flashing / Programming
The nRF Connect SDK (NCS) natively supports direct programming.
You can utilize the "Programmer" application tool to flash the compiled zephyr.hex binary file onto the target chip.
The exact procedure is detailed below:

Step 1: Open "nRF Connect for Desktop" -> select "Programmer" and click "Open".


Click "Select Device" and choose "nRF54L15DK".


Click "Add file".


Step 2: Select your compiled target ".hex" file.


Click "Erase & write" to initiate the programming/flashing process.


While flashing, a progress diagonal pattern will display on the right-hand panel.


When the LOG shows a "completed" status text, it means that the programming/flashing is successfully done.


Step 3: After the flash operation completes, you can download the "nRF Connect for Mobile" app to scan and verify that the Raytac AN54LV-DB-15 development board is advertising normally.

"nRF Connect for Mobile" app download link: https://www.nordicsemi.com/Products/Development-tools/nRF-Connect-for-mobile


Useful References
nRF Connect SDK Documentation: https://developer.nordicsemi.com/nRF_Connect_SDK/doc/3.3.0/nrf/index.html

Nordic DevZone(technical support forum): Nordic Devzone for technical issue discussion



Edited by Account Manager: Christine Huang
Technical Guidance by R&D Manager: MW Lee

Raytac Corporation 勁達國際電子股份有限公司 / Raytac Corporation (USA) / abietec Inc.
A Bluetooth, Wi-Fi, and LoRa Module Maker/ODM & OEM Manufacturer based on
Nordic nRF54; nRF53: nRF52; nRF51; nRF7002
Infineon: CYW55912
NXP: RW610, RW612
Semtech: SX1262

Bluetooth Specification: BT6 ; BT5.4 ; BT5.3 ; BT5.2.
Wi-Fi Specification: Wi-Fi 6
LoRa Specification: LoRaWAN
Zephyr Project Silver Member

All products are FCC/IC/CE/Telec/KC/RCM/SRRC/NCC/WPC/RoHS/Reach Pre-Certified.

http://www.raytac.com
https://www.raytac.com/contact/
https://www.abietec.com/
email: sales@raytac.com
Tel: +886-2-3234-0208(TW)/+1-626-328-3827(USA)

Friday, April 24, 2026

Product Change Notice (PCN-26041701) on Raytac MDBT40 module's Chip Antenna Replacement

  New Taipei, Taiwan / Los Angeles, USA, 04/23/2026


Raytac announces a Product Change Notice (PCN-26041701) for below modules, change effective on the Date Codes stated within.

Device Affected:
1. MDBT40-256RV3: 618 and after
2. MDBT40-256V3: 618 and after

The supplier(of the original chip antenna) notified Raytac in March 2026 that the original chip antenna has reached its end-of-life (EOL) status, thus the introduction of an alternative(new) chip antenna from the same supplier to ensure long term supply continuity.

There are no changes on Form, Fit, Function, and Quality of Reliability.  Only change in Chip Antenna Appearance.

Upon receiving this notice, our R&D team promptly conducted comprehensive validation. The results confirm that there is no impact on RF performance, EMC compliance, or related certifications. 

In conclusion, all existing certifications and technical documentations remain valid.




The change is already effective as the existing inventory of the original chip antenna has been depleted. All production batches are already using the new chip antenna.

We kindly invite our customers, distributors, and partners to update your records accordingly.
For any questions or support, and further document requests regarding this update, feel free to reach out to Raytac Sales Team via: sales@raytac.com.



Wednesday, March 25, 2026

Raytac / abietec Announce New AN54LM Series Modules based on Nordic nRF54LM20A SoC







[CA, USA/Taipei, Taiwan]

Raytac Group, a worldwide leader in wireless modules, wireless solutions, and a Nordic-recommended third-party module manufacturer, announces the upcoming release of the AN54LM series modules, built on Nordic’s nRF54LM20A/nRF54LM20B SoC.

The series comes in a compact form factor of 9.9 x 13.3 x 2.0 mm (0.39 × 0.52 × 0.08 inches) and offers 3 antenna variants:

– Ceramic chip antenna: AN54LM-20. See full product details
– PCB trace antenna: AN54LM-P20. See full product details
– u.FL connector for external antenna: AN54LM-U20. See full product details

The Max output power is +8 dBm and data rates up to 4 Mbps for low-latency applications.

Monday, November 24, 2025

Raytac Corporation – U.S. Headquarters Relocation Notice

 New U.S. Headquarter Address:

17800 Castleton Street, Suite 238, City of Industry, CA 91748, USA
Phone: 626.328.3827
Our new location strengthens our operational capabilities in the United States, enabling faster logistics, enhanced customer support, and expanded service coverage. We look forward to continuing to serve our partners and customers from our new facility.

Friday, August 15, 2025

Raytac Corporation (USA) Launches Inland DDP Shipping & Local Support in California

 


[08/14/2025, California, USA]
To better support our customers in the United States, Raytac Corporation(USA) now offers inland domestic shipping and a local support team based in California.

By bringing our services closer to U.S. clients, we can provide faster assistance for ongoing projects, significantly shorten lead times, and maintain the high quality and global compliance standards Raytac is known for.

For more information, please do not hesitate to contact us through: https://www.raytac.com/contact/

Wednesday, July 17, 2024

Transition tips for program from MDBT50Q-RX (USB-A) to MDBT50Q-CX (USB-C)  with current NRF52840 project

 Intro:

This is a guidance provided for those who are going to transit (or replicate) their project from Raytac MDBT50Q-RX (USB-A Dongle) to MDBT50Q-CX(USB-C Dongle).  In addition to the hardware spec change (Compact Size , LED, Button, Pin definition change) , the key firmware configuration should be made with changes to fit new USB-C Dongle MDBT50Q-CX.

 


RX-1                    CX-1

MDBT50Q-RX                             MDBT50Q-CX

  

Table of Contents:

1. Comparison chart: MDBT50Q-RX(USB-A) & MDBT50Q-CX(USB-C)

2. Firmware configuration

3. Create a merged hex file (2 in 1 or 4 in 1)

4. Firmware flashing process

 


1. Comparison chart: MDBT50Q-RX & MDBT50Q-CX

Comparison chart


2. Firmware configuration : MDBT50Q-RX → MDBT50Q-CX

Edit your current MDBT50Q-RX firmware with configuration change to align the PIN change to accommodate the hardware change.

Option 1. Using nRF5 SDK:

Make the definition set up of LED, BUTTON pin in the highlighted 4 sections.

Firmware configuration-nRF5

 


Option 2. Using NCS V2.6.X:

Use the board name: nrf52840dongle_nrf52840 and add the overlay file:

nrf52840dongle_nrf52840.overlay to the program (Devicetree Overlays),

then configure the below code definition into the overlay file:

/ {
   leds {
             compatible = "gpio-leds";
             led0_green: led_0 {
                      gpios = <&gpio0 6 GPIO_ACTIVE_LOW>;
                      label = "Green LED 0";
             };
             led1_red: led_1 {
                     gpios = <&gpio0 8 GPIO_ACTIVE_LOW>;
                     label = "Red LED 1";
             };
};

  buttons {
  compatible = "gpio-keys";
  button0: button_0 {
                  gpios = <&gpio1 6(GPIO_PULL_UP | GPIO_ACTIVE_LOW)>;
                  label = "Push button switch 0";
                                   };
};
};

Firmware configuration-NCS

 


3. Create a merged hex file (2-in-1 or 4-in-1 hex file)


3A. Bootloader public key product

nrfutil keys generate public_key.pem → for zipping new firmware

nrfutil keys display --key pk --format code public_key.pem --out_file public_key.c

→ include public key to compile bootloader hex file

3A-1

3A-2

 


3B. Examples Demo

nRF5 SDK: nRF5_SDK_17.1.0_ddde560\examples\ble_peripheral\ble_app_uart\pca10056\s140

NCS V2.6.X: ncs\v2.6.0\nrf\samples\bluetooth\peripheral_uart

 


3C. How to generate bootloader setting file (if you need bootloader):

nrfutil.exe settings generate --family NRF52840 --application nrf52840_xxaa.hex --application-version 255 --bootloader-version 2 --bl-settings-version 1 bootloader_settings.hex

 


3D. Merge and create a 2-in-1 or 4-in-1 hex file

a). Merge 2-in-1 (no Bootloader file required):

mergehex.exe -m s140_nrf52_7.2.0_softdevice.hex nrf52840_xxaa.hex -o merge.hex

3D-a

 


b). Merge 4-in-1 (with Bootloader file & Bootloader settings file required):

mergehex.exe -m bootloader.hex bootloader_settings.hex  s140_nrf52_7.2.0_softdevice.hex nrf52840_xxaa.hex -o merge.hex

3D-b

 


4. Firmware flashing process

MDBT50Q-RX(USB-A):Manual wiring is required to have the firmware uploaded.

Please refer to the article: Firmware Coding & DFU onto MDBT50Q-RX

MDBT50Q-CX(USB-C):Built-in open bootloader included for simple DFU process..

Please refer to the article: User Manual of MDBT50Q-CX (nRF52840/nRF52833-based USB-C Dongle)

 





Edited by Sales Manager:
 Ms. Jocelyn Tsai
Technical guidance provided by Firmware Deputy Manager: Mr. Stanley Huang