Raytac/abietec at COMPUTEX Taipei 2026 - Explore the Future of Nordic Bluetooth, Wi-Fi, and Edge AI Technologies

 

As COMPUTEX 2026 approaches, are you ready to witness the next breakthrough in wireless connectivity technology?

From June 2 to June 5, 2026, Raytac and abietec sincerely invite customers and partners worldwide to visit our exclusive booth at:
POPPOP Taipei (Taipei Bottle Cap Factory), Building F (Click here for Google Maps location)

Join us to explore the future of Bluetooth and Wi-Fi technologies, exchange ideas with our engineering team, and discover how next-generation wireless solutions can accelerate your product development.

Why Raytac/abietec?
We understand that having a powerful Nordic Semiconductor SoC is only the beginning of successful product development.
The real challenges often come afterward — including RF design optimization, antenna tuning, impedance matching, and complex global RF certifications.


At Raytac, we provide more than high-quality wireless modules; we help shorten your development cycle.
Industry-Leading Bluetooth® & WiFi Solutions
Built on Nordic Semiconductor’s advanced SoC platforms, Raytac modules deliver:
- Ultra-low power consumption
- Stable wireless performance

One-Stop Wireless Development Support
We understand the complexity behind RF engineering. Raytac’s solutions help reduce engineering effort in areas such as:
- Antenna design
- RF tuning & impedance matching
- Certification preparation
- Hardware integration

Allowing your engineering team to focus more on developing core product functionality.

A Truly Non-China Supply Chain
Raytac takes pride in maintaining a 100% non-China manufacturing background, offering greater supply chain transparency, flexibility, and competitiveness in international markets: an increasingly important advantage in today’s global environment.

Daily Tech Talks During the Event
Throughout the 4-day exhibition period, we will host daily Tech Talk sessions from 11:00 AM – 11:30 AM, covering:
- Nordic nRF54 and nRF70 series technologies
- Raytac's Low-power Wi-Fi + Bluetooth® solutions
- Real-world application examples from customers
- How Raytac's pre-certified modules help you shorten IoT development and reduce time-to-market

Whether you are looking for a reliable Bluetooth module, evaluating Wi-Fi solutions, or facing engineering challenges during product development, we welcome you to stop by and discuss your project with us — we may have ideas that help solve your challenges.

Reserve a Meeting with Us
Interested in scheduling an on-site discussion or learning more?
Please feel free to contact us directly on: https://www.raytac.com/contact/,
or reach out to our sales representative:
Mr. Welson Kuo
Email: welson@raytac.com

We look forward to seeing you in Nangang, Taipei.

Raytac's nRF7002 module: AN7002Q series Wi-Fi module have obtained Wi-Fi Alliance CID

 [2025.02.19]

Raytac Corporation is proud to announce that our application for Wi-Fi Alliance (WFA) certification on the AN7002Q series(based on Nordic's nRF7002 IC) has been successfully approved. This achievement reinforces our commitment to providing high-quality, reliable, and standard-compliant wireless solutions.
By leveraging this certification, our modules ensure seamless interoperability, enhanced security, and superior performance for a wide range of IoT applications.

Advantages of Using Raytac Modules with WFA Certification:

Reliable and Secure Connectivity – Ensures seamless communication with other Wi-Fi-certified devices while meeting industry-leading security standards for stable and secure data transmission.
Faster Time-to-Market – Pre-certified modules simplify compliance processes, reducing development time.
Global Market Access – Certification helps meet regulatory requirements in multiple regions, expanding business opportunities.
Significant Cost-Saving – Compared to the chip-on-board approach, using Raytac’s Wi-Fi module allows direct access to the Derivative programs(please click here for more descriptions), leveraging Raytac’s CID to minimize certification costs and save time-to-market.

To learn more about Wi-Fi certifications and Wi-Fi + BLE applications, feel free to contact us anytime at service@raytac.com.

---

Edited by Account Manager: Ms. Mandy Chao

Raytac Corporation 勁達國際電子股份有限公司
A Bluetooth, Wi-Fi, and LoRa Module Maker based on
Nordic nRF54; nRF53: nRF52; nRF51; nRF7002
Semtech Specification: SX1262

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

All products are FCC/IC/CE/Telec/KC/RCM/SRRC/NCC/WPC Pre-Certified.
http://www.raytac.com
email: sales@raytac.com

Step-by-Step Guide to Purchasing MAC Addresses from IEEE for Your Devices

The Ultimate Guide to Acquiring MAC Addresses from IEEE 

Secure DFU OTA for nRF52832 solution modules: Creating hex/zip file for implementation – Part 2(Combining/merging built files)

 Following up – Part 1: Bootloader & Application (Click for article link),

We will be focusing on:

Part 2: Combining and merging built files

in this article.

IC: nRF52832
DK: PCA10040 (for nRF52832)
SDK: 16.0.0
Softdevice: s132_nrf52_7.0.1_softdevice.hex
IDE: Keil C
PC: Win 10

---

Part 2: Combining and merging built files

FAQ: How to write MAC address into the OTP memory of Raytac’s AN7002Q Wi-Fi module/AN7002Q-DB-5340 DevKit

Recently we have received the FAQ: how to write MAC address into the OTP memory of AN7002Q-P Wi-Fi module? In this article, we’ll get this question explained to give customers a more smooth experience using the AN7002Q-nRF5340 Demo Board(AN7002Q-DB-5340).

Is there an existing Wi-Fi MAC address in the AN7002Q part on the DevKit?

Currently, the AN7002Q module on Raytac’s AN7002Q-DB-5340 board isn’t loaded with a Wi-Fi MAC address.


When running Wi-Fi Scan code/Station code/Shell code…etc. on NCS v2.6.0 (and later versions), the AN7002Q module must have a programed Wi-Fi MAC address to function properly.

Therefore, it’s necessary to follow the below process:
1. Program the original Wi-Fi radio test code (..\nrf\samples\wifi\radio_test) into the MDBT53 section,
2. Then write the Wi-Fi MAC address in to the AN7002Q section via command.

After this, program the original Wi-Fi Scan code/Station code /Shell code … into the 5340, and it will function properly.

*Raytac will assign 2 MAC addresses(for both 2.4GHz & 5GHz) to every AN7002Q module.

*If customers don't have MAC addresses for DevKit development yet, please reach out to service@raytac.com

=========================================================

Case study 1. SCAN code example

Scenario:
Following error occurred when building the SCAN example code, flash it onto the AN7002Q-DB-5340 board, and run the test.

Solution:

When running Wi-Fi scan code on NCS v.2.6.0 or later version, the OTP memory in the AN7002Q module must have a Wi-Fi MAC address programmed in for the Wi-Fi scan functionality to work properly.

(Note: OTP is a One-Time programmable memory, which means the value can only be written once.
The customer must aware of this before performing the OTP operation.)

1. Program the original Wi-Fi radio test code (..\nrf\samples\wifi\radio_test) into the MDBT53 section,
then manually input and execute the following OTP read command.

wifi_radio_ficr_prog otp_read_params

If you see both MAC0 and MAC1 display a value of 0xFF, as shown in above, it means that you haven’t written the Wi-Fi MAC address into the AN7002Q’s OTP.

2. Manually issue the OTP write command to write the Wi-Fi MAC address into the OTP.

https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/samples/wifi/radio_test/ficr.html

wifi_radio_ficr_prog otp_write_params 0x120 0xDDCCBBAA 0xFFEE

wifi_radio_ficr_prog otp_write_params 0x128 0xDDCCBBAA 0xFFEE

After you complete the above, use the OTP read command in below to check if the Wi-Fi MAC address value was written.
The MAC0 and MAC1 should display the value you’ve input from the OTP write command.

wifi_radio_ficr_prog otp_read_params

3. Program the original Wi-Fi SCAN code back into the MDBT53, the Wi-Fi scan functionality should work properly.

==================================================================

Case study 2. Shell code example

SDK Wi-Fi example test – Running Shell Code on AN7002Q-DB-5340:
Scenario:
An error occurs while running Shell code on AN7002Q-DB-5340.

Solution:
The AN7002Q-DB-5340 is paired with nRF5340 DK for development,
but neither of the 2 boards has an external MX25R64 (Serial NOR Flash) component.
So far, only the nRF7002DK board is equipped with the MX25R64.

Therefore, while running the original Wi-Fi shell code, the program will enable SPI NOR.

When using AN7002Q-DB-5340, you should add CONFIG_SPI_NOR=n in the prj.conf file to disable SPI NOR, to turn off any configurations related to it.

After recompiling and flashing, the shell code function
( e.g., Wi-Fi scan/Wi-Fi connect/net ping ..) should work properly.

6 wireless technologies for wearables

Raytac Corporation

A BT4.1 & BT4.2 module maker based on Nordic nRF51 & nRF52 solution 

(nRF51822 & nRF51422 & nRF52832 & nRF51802)

www.raytac.com

Tel: +886.2.3234.0208

email: service@raytac.com  
 https://raytacblog.wordpress.com/

http://bluetooth.tokyo

Quoted from Nordic Blog

http://blog.nordicsemi.com/getconnected/wireless-technologies-for-wearables?hs_preview=cRandwfB-4125023772

Which one of these wireless technologies is best for your wearable product?

Are you creating a wearable product, but not sure of what wireless technology to choose? The way modern APIs work, developers don’t necessarily need to know the technical details. But having a basic understanding of the underlying technology will help you make apps that are more efficient, more responsive and easier to use.

Which solution is best for your wearable product? This depends on your requirements for bandwidth, power considerations and range. Here’s a brief overview of the 6 most common wireless technologies to consider.

Near Field Communication (NFC)

NFC works best for wearables that require low power consumption. It involves the transfer of tiny amounts of data over a very short range, essentially by touching two devices together. The devices will switch between two different modes: Active and passive. The power consumption for NFC is similar to what we see in Bluetooth Low Energy, although higher when communicating with a passive tag.

If you need your wearable to transfer data over a longer range, you should look for other options.

Bluetooth Low Energy (BLE)

Today, most wearables are running on Bluetooth Low Energy (BLE, formerly called Bluetooth Smart).
This technology is known as an easy to implement, low-cost option that requires very little power from your wearable. Your product can be powered by a coin cell battery for months - even years in some cases. But BLE comes with a compromise: Your data throughput will be limited. As most wearables generally transfer very little data, product owners can usually live with this.

The BLE chip is small, and fits nicely into an esthetically pleasing wearable that is convenient for the user to wear. A line-of-sight range of up to 100 meters is possible.

Using BLE requires your device to be paired with a host, most usually a cellphone with an app activated.

If you plan for your wearable to transfer higher amounts of data frequently,Bluetooth Low Energy may not be the best choice. Limited data transfer capacity makes this technology unsuitable for audio and video streaming, for example.

ANT

The wireless network technology ANT is a good option for sports wearables. A subsidiary of Garmin, ANT is huge in the sports and fitness segment where it is typically used for monitoring of heart rate, cycling power, distance and speed. Many of today’s cycling and fitness brands use ANT for their wearables. In fact, it has almost become a de facto standard in cycling.

The sensors and other nodes will act as either slaves or masters within a wireless network. Each node can transmit, receive or even function as a repeater to increase the range of the network. You can configure the network to spend long periods in low-power sleep mode, consuming extremely little power.

Bluetooth Classic

Initially a standard intended to cover a lot of use cases for wireless communication, Bluetooth Classic (originally named slimply 'Bluetooth', of course) found its niche in audio. Today it is the de facto standard for audio streaming, whether from your smartphone to a headset, speaker or in-car multimedia system.

Compared to BLE, Bluetooth Classic requires much higher bandwith and therefore more power. The network topology is limited and not suitable for large sensor networks.

Wi-Fi

If your wearable needs to transfer a lot of data with as little lag as possible, Wi-Fi is your best option. The technology is best when streaming huge amounts of data, like video, but its main drawback is high power consumption that will require daily battery charging.

By using Wi-Fi, your wearable product can connect directly to the Internet via a Wi-Fi Access point.

Google Glass uses Wi-Fi to transfer graphics at high data rates for a better user experience. But the high power consumption of the display, and the high CPU load, requires the consumer to charge the device frequently. Be aware that such charging requirements will be a very important factor in overall customer satisfaction.

Cellular

In a similar way to how your smartphone operates, using a cellular radio means that your wearable device can talk directly to the cellular network. Although convenient, as there is no need for a bridge device such as a smart phone to access the cloud, today’s cellular technologies are not suitable for small wearable devices. Power consumption is high and the physical dimensions are usually rather large. In the future, we will see new cellular technologies that are more competitive in the wearable space. But we're not there yet.

The best of all worlds?

Some wearables combine different wireless technologies to take advantage of different aspects of each method. The Apple Watch uses Bluetooth Classic, BLE, Wi-Fi, and even NFC for mobile payments. Nordic Semiconductor is currently the only manufacturer delivering chips that support both ANT and Bluetooth Low Energy (BLE), as well as NFC - all in one low power, 'system on chip' solution.

Hopefully, you’re now a little clearer on which wireless technology is best for you. If you’re still struggling, consider your product priorities. Is it size, power consumption, user experience, cost, or something else? Once you're clear on the priorities for your wearable, your wireless communication options become a lot clearer, too.