The “Must Know” about WPC-ETA certificate before entering Raytac Bluetooth module into India

 Intro:

You will get a brief understanding of WPC-ETA certificate (India) and how it relates to Raytac low energy Bluetooth module and how it helps you entering Raytac Bluetooth module into India by passing through importing and Customs clearance procedure way efficiently.

There are some types of ETA certificate categorized by the spec of your wireless transmission product (Bluetooth/Wifi/RFID and by device using frequency spectrum).

Hereafter we’re talking about the WPC-ETA compliance regulation to specifically on “Raytac’s low energy Bluetooth module.”

 

Outline of the article:

1. What is WPC Certificate/Equipment Type Approval (ETA) in India?
2. Raytac Bluetooth module applied to WPC-ETA Regulation Category
3. What is essential to get the ETA-SD license (ETA Approval)?
4. How the ETA-SD license works during importing process

A. What is WPC Certificate/Equipment Type Approval (ETA) in India?

The WPC (Wireless Planning & Coordination) is the broadcasting authority and is part of the Ministry of Communications and Information Technology in India.

Products with radio and/or wireless functionality imported or manufactured or marketed in India are required to have an Equipment Type Approval certificate (ETA certificate) from the Wireless Planning and Coordination (WPC India) Wing of the Ministry of Communications of the government of India. This includes product with Bluetooth, wireless local area network access technology (Wi-Fi), small digital radios (Zigbee), and radio frequency identification (RFID) and else more. The WPC-ETA certificate is required for anyone who wants to do wireless device business in India.

B. Raytac Bluetooth module applied to WPC-ETA Regulation Category

--ETA Through Self Declaration (ETA-SD License)

To specifically recognize what is the compliance regulation of equipment applies to Raytac Bluetooth module, we can be assured with our Bluetooth module spec located within “De-licensed Frequency Band list” , 2400-2483.5MHz / Limit with 10mW EIRP / Use of low power and very low power short range radio frequency device for Non-Specific Short range device, from the following chart which was released from WPC authority.

Once we confirm Raytac Bluetooth module spec is operated in De-License Frequency Band with low transmission power, at the mean time making sure the device is exempt from import license as per Import Policy of DGFT (Directorate General Of Foreign Trade), Ministry OM ETA-WPC-Policy-2018-19 dated 26^th February 2019, free from EXIM Policy of DGFT, Raytac is granted to apply for “ETA Through Self-declaration” application procedure which was enabled by SARAL SANCHAR Portal of DoT on 12^th April, 2019.

Here's Raytac’s ETA through self-declaration (ETA-SD license) of module MDBT50 certified by WPC authority. (Please refer to the following image)

C. What is essential to get the ETA-SD license (ETA Approval)?

After getting idea of what ETA-SD license means to Raytac low energy Bluetooth module business, we need to get ready of the following points for applying the ETA Approval (ETA-SD License)

• Applicant must be India manufacturing or authorized Indian representative
• Making sure product exempt from import license
• Making sure product working in the de-licensed frequency band
• Wireless RF test report conducted by accredited laboratory
• Details of Accreditation laboratory & Accreditation certificate issuing authority
• Authorization letter

 

D. How the ETA-SD license works during importing process

1. Once ETA through self-declaration is generated for a model, subsequently it may be utilized by other person(s) for import/usage purpose in India. It is not necessary the importing agent/manufacturer is same party to the applicant of the license.
2. Question: How to import products falling under the category of ETA through Self-Declaration?      Answer: Such category of product(s) may be imported by submitting an undertaking to the customs along with ETA-SD License without additional payment.
3. The ETA-SD license remains valid and NO renewal is needed until the technical parameter/design of the device is modified or altered.
4. Generally speaking , India doesn’t follow Modular policy nor Non-Modular policy. It determines how you proceed WPC-ETA certificate by product type (Semi-finished & End-product) and product technical spec (Frequency spectrum & Max output power).  For instance: When the product is manufactured in India and its RF module(s) having ETA certificate is/are fitted inside it without any modification/alteration; then NO separate ETA is required for such finished product during import process. However, if finished product(s) are manufactured outside India, then ETA is required for each product before its import.
5. For the product which does not fall under De-Licensed frequency band and exempt from import license, WPC/ETA Certificate shall be obtained by routine proceeding to the concerned RLO ETA certificate. Both ETA (RLO) certificate and Import license shall be submitted to Customs during importing process whereas ETA-SD license Raytac module certified is exempt from import license that is way easier to proceed.

Edited by Account Manager: Jocelyn Tsai

Raytac Corporation 勁達國際電子有限公司
A Bluetooth & WiFi module maker based on Nordic nRF53, nRF52, nRF70 solution 
www.raytac.com email: service@raytac.com Tel: +886.2.3234.0208                             

Bluetooth Solution:  nRF5340, nRF52840, nRF52833, nRF52832, nRF52820, nRF52811, nRF52810, nRF52805, nRF51822                                                                                  WiFi Solution: nRF7002  

Nordic nRF52 Module by Raytac (Advanced Line Series)

Bluetooth has become the basic feature for applications nowadays. 

To fulfill the challenge of coming various Bluetooth function demands, Nordic Semiconductor provides a rage of nRF52 solutions from basic to advanced for customer's selection. Raytac extent this advantage and offer modules with different antenna and form factors based on individual nRF52 solution.

This article, Raytac listed the advanced line modules: MDBT50Q, MDBT50, and MDBT42Q series which deployed Nordic Semiconductor's nRF52840, nRF52833, nRF52832 solutions.

Customers are encouraged may click below link to find more module information from Raytac's website!

nRF52840 Modules: GPIO: 48  Flash: 1MB / RAM: 256K

nRF52833 Modules: GPIO: 48/18  Flash: 512K  / RAM: 128K 

nRF52832 Modules: GPIO: 32/20  Flash: 512K  / RAM: 64K 

Raytac Corporation 勁達國際電子有限公司

A BT5.2 & BT5.1 & BT5 module maker based on Nordic nRF52 & nRF51 solution 
(nRF5340 & nRF52840 & nRF52833 & nRF52832 & nRF52820 & nRF52811 & nRF52810 & nRF52805 & nRF51822)

www.raytac.com

email: cs@raytac.com

Tel: +886.2.3234.0208

Raytac Product Change Notice (PCN) Announcement for AT Command Series Module

Raytac would like to announce Product Change Notice (PCN-20051101) for AT Command modules which built by nRF52832 SoC Build Code EXX (Version 2) includes part no.: MDBT42Q-ATM / MDBT42Q-PATM / MDBT42V-AT / MDBT42V-PAT series.

The major description of this PCN is refer to the update of marking on the shielding case. Apart from the appearance change herein,  there is no further function, quality or safety regulation is affected. 

In case there is anything unclear for this PCN , please do not be hesitated to contact Account Manger for further assistance.



Raytac Corporation 勁達國際電子有限公司
A BT5.2 & BT5.1 & BT5 module maker based on Nordic nRF52 & nRF51 solution 
(nRF5340 & nRF52840 & nRF52833 & nRF52832 & nRF52820 & nRF52811 & nRF52810 & nRF52805 & nRF51822)

www.raytac.com

email: cs@raytac.com

Tel: +886.2.3234.0208

nRF52840 v.2 - What's new?

From IC Revision 1 to 2

While there are quite a few changes available for review in the nRF52840 documentation, there is update that is particularly important for many users out there, including a large amount of our own customers. The update I am talking about is about the power supply.

First things first - if you're interested in reading the whole documentation for Nordic Semiconductor's nRF52840, then look no further than their Infocenter.

Raytac's UART Service (AT Command Central / Master) -MDBT50Q-RX-ATM How do you get started?

Easy! At least when you know what to do

Many of our customers just want a device that provides Bluetooth technology to their product or solution that they've developed. However, utilizing the full capacity of the Bluetooth protocol is not always easy and sometimes not even necessary. For these customers, choosing Raytac's modules/dongles loaded with AT Command, such as MDBT50Q-RX-ATM, is the best choice.
But even a product such as MDBT50Q-RX-ATM that is supposed to make it easy for customers to wirelessly transfer data from one device to the next can be difficult to use - especially when you don't know HOW.

So, I thought we'd take this in two simple steps.

1. Device Name

To be really sure that you can connect to the device thus making you able to pair with it, you will have to make sure that the device name setting in the AT Command list is set to the name that the other (slave) device is set to.
For example, if your slave device set to have the name "ILoveBluetooth" and you haven't changed the settings in the AT Command, you will not be able to pair your MDBT50Q-RX-ATM with this device.
As you can see in the picture below, the default setting for this device's name is "Raytac AT-UART".



When editing this name, you get a smaller window like this popping up:



Make sure that the name set on your device that you wish to connect with the dongle AND this name in the AT-Command device's list are the same. You will in this case need to change this to "ILoveBluetooth".

2. RSSI

This is a trickier part - especially when you don't know what it is.
RSSI stands for Received Signal Strength Indicator and, just like the name implies, is a value of strength of which the incoming signal has to be in order to even be considered by the scanning device.
In other words, the lower the value is set to, the weaker signals the scanning device will show.
The standard value of Raytac's AT-Command modules/dongle is -51 and the setting screen looks like this:

3. Slave device's SDK

What many new customers seem to believe is that if you use our AT-Command modules/dongles, you won't need to do anything - they will just magically communicate with each other somehow.
I hate to break it to you, but no... that's not how it works. You will have to at least make sure that the two devices "speak the same language". As for our AT-Command modules/dongles, or in this case MDBT50Q-RX-ATM, it is through a "language" (a.k.a. protocol) called UART.
First of all, "UART" is not "U-ART" although it's kind of pronounced that way, but it's an abbreviation that stands for Universal Asynchronous Receiver/Transmitter. You can read about it here.
I will spare you all the details about the UART protocol itself, but one thing that we will need to make sure of is that you have it installed onto your slave device.

Hopefully, you've downloaded Nordic's latest SDK and you have it ready on your computer. You can download them directly HERE.
Note: This file is quite big (~130MB), so DO NOT click on the last link if you don't want to download this on your current device.

Inside this file, you will find a lot of stuff. However, for this particular case, we only really need to care about the "examples" folder.

In this folder, we will have (surprise surprise!) even more folders :D
As per usual, we don't have to check them all out. In this case, we specifically only want to check the "ble_peripheral" and the "peripheral" folders.

Go into the former folder and you'll find see the following folders in which you will want to enter the "ble_app_uart" folder.:

In this folder, you will see five more folders and two files, but we only want to check out one of them depending on which chip type you're using in your slave device. Let's say you're using a nRF52832 chip (or module such as MDBT42Q-P512KV2), then you'd want to enter the first folder called pca10040. Check the picture below to see which folder you'd want to enter:

Assuming you entered the folder that I mentioned above, you will then want to enter the "s132" folder.

Once you're in here, I am pretty sure you developers out there know what to pick :)

In the beginning of this section, however, I also mentioned another folder called "peripheral" which we will guide you through now - even if it's very similar to what we just did.

As you can see, there are a TON of folders in here, but we will cherry-pick our folders here too.
Let's say that you'd like to be able to make your slave device to read and transmit information from a sensor. Supposedly, most sensors use either the I2C or the SPI interface. In each respective folder, you will find the same folder layout as in the previous picture - folders representing what chip/module you have.
The main point of showing you this is simply because from these two folders, you can snatch the small amount of code that you need to edit the main code of your UART main-code so that you can both read and send the data from the sensor you might have.

Hopefully, you've now started to realize how these things come together and we can finally start to connect these devices. This takes us to the next step:

4. ATSCANNEW

Once that's done, you will need to use your AT-Command module/dongle (here MDBT50Q-RX-ATM) to scan for the slave device that you want to pair. To do this, you first have to make sure your slave device is broadcasting, then execute a command called ATSCANNEW.
Once you've done so, your MDBT50Q-RX-ATM's blue LED will hopefully go from fast blinking to a slower blinking. This means that your two devices, master and slave, have now paired successfully. Wohoo! :)

We hope that this makes our AT-Command modules/dongles even easier to use!
Raytac wishes you all happy tinkering :)

Raytac Corporation 勁達國際電子有限公司 A BT 5.1 & BT 5 & BT 4.2 module maker based on Nordic nRF51 & nRF52 solution (nRF52840 & nRF52832 & nRF52811 & nRF52810 & nRF51822)

www.raytac.com

email: cs@raytac.com

Tel: +886.2.3234.0208

LINE’s IoT platform "LINE Things"

LINE introduced an IoT platform called "LINE Things" which allows Bluetooth Low Energy  (BLE) devices integrated to LINE's ecosystem through LINE Things and operate by LINE's own developed LINE Front-end Framework (LIFF) application.

Burn your firmware - onto MDBT50Q-RX, that is.

Hi there, folks!

Here introduce the hardware setting perspective to burn your firmware onto MDBT50Q-RX Dongle.

(if you are looking for firmware coding setting, please visit "Firmware Coding & DFU onto MDBT50Q-RX")

So you have hopefully downloaded your IDE, you have written your code which you then plan to copy it over onto your MDBT50Q-RX and make it execute your master plan to take over the world!
Seriously, don't underestimate the Nordic nRF52840 based MDBT50Q-RX. USB sticks with Bluetooth can do wonders ;)
So, first of all, in order to be able to burn your code onto the USB Dongle, you will have to know the nerdy parts which includes which pins you will have to connect to. In our very well documented specification sheet for MDBT50Q-RX on section 8 which is called "Reference Circuit", you will find parts down to the left that has "3.3V/SWDIO/SWCLK/GND" marks on it:

Further down in the specification sheet, in section 9, you will find pictures illustrating where exactly on the PCB you can find these pins:


Now we know what to look for and where they are, so now we have only got to tell you how to use them.

Some people might not know this, but for developing these things, you need to get something called J-Link to connect your MDBT50Q-RX to your desktop. However, since this J-Link, when buying the official one from SEGGER, is very expensive, we strongly recommend you to just buy the nRF52840-DK from Nordic Semiconductor as it can be used as a J-Link through their software development kit (SDK) called nRFgo Studio and is MUCH CHEAPER than the official J-Link from SEGGER is.
Sidenote: There are a couple of other reasons why you should just get your hands on a nRF52840-DK from Nordic Semiconductor instead of getting a SEGGER J-Link, but that's not the topic of this post ;)

When this is done, this is finally how you connect your MDBT50Q-RX to your J-Link to make it all work:



Here you will have to pay attention to the fact that you have to connect J-Link pins 3, 5 & 9 to GND. Otherwise, you won't be able to burn anything onto your dear MDBT50Q-RX.
The physical connection should look like this:



Pay attention to the direction of the cable, because that will also matter. The direction we mean in this case is which way the slim strip of red is facing.

As we have just revised our MDBT50Q-RX, our customers who have been developing firmware for our USB dongle should take a look at our previous blog post in which we explain about the changes made or contact us directly at service@raytac.com

Have a good day and we at Raytac wish you smooth and happy tinkering :)

Raytac Corporation 勁達國際電子有限公司
A BT5 & BT 4.2 & BTv4.1 module maker based on Nordic nRF51 & nRF52 solution
(nRF51822 & nRF51422 & nRF52832 & nRF52810 & nRF52840)

www.raytac.com

email: cs@raytac.com

Tel: +886.2.3234.0208

Raytac Corporation at IT Week Hall 3 & 4 / 11-22

With over 600 exhibitors gathering in Tokyo, Japan from April 10-12, IT Week has become one of  the biggest exhibitions within the IoT Technology sector.
Raytac is pleased to be attending this year's IT Week and present our full range of module family based on Nordic nRF51822, nRF52832 and nRF52840.

Meanwhile, the latest product, MDBT50Q-RX, a multi protocol nRF52840 dongle will make its second public appearance which powers up the most advanced IoT and Mesh network implementations.

Bluetooth - Current and soon-to-perish versions

Bluetooth has been around for quite some time, but that doesn't mean that no one is a beginner when it comes to developing Bluetooth-based products. In fact, due to their recent updates, Bluetooth is becoming increasingly popular as demand for power efficient gadgets and wireless technology is increasing. Smart watches is just one of the many examples out there.

For each and every single one of these devices, you'll first have to register your new product with Bluetooth-functions built in on Bluetooth SIG's website. You will eventually register (and pay for) your product based on what version of the Bluetooth protocol that you're using in the product and do so by purchasing a so called Declaration ID (DID).

Yes, a little exaggeration in the title, but that's essentially what it comes down to. Bluetooth SIG is doing some major updates and changes to the Bluetooth protocol which includes getting rid of the more outdated versions.

There are quite a few versions of the Bluetooth protocol out there, but nowadays you will basically be advised to choose from 2 versions:
v.4.2 or v.5.0
These two versions would be, as I mentioned in the title, the two current versions of Bluetooth.

Although it might seem very simple at first, there are a few things that you need to understand the content of the announcements to fully grasp what these updates and changes mean. That, my friends, is today's topic of this post.

Archived specifications

Deprecated and Withdrawn Specifications

When a specification reaches the end of its useful life, the Bluetooth® SIG may choose either to deprecate the specification, ending maintenance and restricting its use, or to withdraw the specification from use.

Bluetooth SIG - https://www.bluetooth.com/specifications/archived-specifications

What has changed recently is nothing new, but it's big. What I mean is that similar changes have been done in the past, but since the market is more dependent on the technology now than before, it matters far more for people when the Bluetooth SIG do the same changes nowadays. Those changes are as follows:

On 01/28/2019, the following policy changes will be enacted: 

- Creating new designs that implement deprecated or withdrawn specifications will not be permitted 

- New products cannot be added to designs that implement withdrawn specifications 

- You cannot pay a $25,000 fee to qualify a new design that implements a deprecated specification 

- Purchased but unused $25,000 Declaration IDs will no longer be valid and the cost of any unused $25,000 Declaration IDs will be credited to your account 

 Bluetooth SIG - bluetooth.com

This piece of information tells us that the process of withdrawing specifications comes down to two different steps, namely deprecation and withdrawal.
While deprecation literally means "to stop use", it is in this case the first step in the process of making a certain Bluetooth specification obsolete.
Then there's a time gap between a certain specification gets deprecated until it's withdrawn. During this gap, as mentioned above, no new designs can be paid for and/or registered and unused DID's will be invalid. This is only to prevent new devices with deprecated Bluetooth specifications from being produced. To stop the "bloodline" of those specifications if you will. During this gap, however, you are still able to add new products that implement the same fundamental design (e.g. version updates) as you wish.

After this gap is over, when the specification in question is actually withdrawn, you will not be able to add any new products to any existing designs.

Got it? No? It's alright. In fact, there's a lot of information and it's hard to put into context right away. Just to make things clear, let's make an example:
Company R is currently developing a new device called RIC which implements Bluetooth 4.0 specifications. For now, everything's alright and Company R can go right ahead with their developments.
When the Bluetooth core specification 4.0 becomes deprecated in Jan 28th, Company R can no longer come up with new product designs such as RIC-2 since that would count as a new design, but Company R can update their original device RIC as long as they don't change the physical design.
Then, when the Bluetooth core specification 4.0 is finally withdrawn, Company R cannot update their product RIC anymore AND they cannot register new designs under Bluetooth core specification 4.0.

If you're a developer who is very familiar with Bluetooth already, this information might already be, as certain people refer it as, "peanuts". If you're new to the Bluetooth world, however, this is a lot to take in and you might want to read up more about it. We hope this explanation made things clearer for you though :)

You can find more info at:
Bluetooth SIG - https://www.bluetooth.com/specifications/archived-specifications


Don't forget that Raytac Corporation's modules are all pre-certified with FCC, TELEC, IC, CE, RCM, KC and SRRC. The best part is that more is yet to come!
Take a look at our modules on our website: www.raytac.com

Raytac Corporation 勁達國際電子有限公司

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

(nRF51822 & nRF51422 & nRF52832 & nRF52810 & nRF52840)

www.raytac.com          email: cs@raytac.com          Tel: +886.2.3234.0208

Raytac nRF52840 BT5 Module MDBT50Q Series WPC (India) Certification Granted

Raytac would like to announce MDBT50Q series Bluetooth Module which deployed Nordic nRF52840 solution have WPC (India) certificate granted.

We believed it will help Indian customers breakthrough to Bluetooth world with Raytac WPC certified nRF52840 modules. 

Raytac nRF52840 BLE Module Series

Raytac Corporation 勁達國際電子有限公司

A BT4.1 & BT 4.2 & BT 5.0 module maker based on Nordic nRF51 & nRF52 solution 

(nRF51822 & nRF51422 & nRF52832 & nRF52810 & nRF52840)

www.raytac.com          email: cs@raytac.com          Tel: +886.2.3234.0208

Wordpress
Raytac Laser

Bluetooth SIG Announces Deprecation and Withdraw of Legacy Bluetooth Core Spec Version

Bluetooth SIG announced the deprecation and withdrawal of older versions of the Bluetooth Core Specification.

Bluetooth SIG has policy in place to introduce the deprecation and withdraw process for older testing specification, listing procedure and core specification.

For core specification placed into withdrawn status, it will not be allowed to use the withdrawn version anymore. Any product wishes to qualify the Bluetooth Design under this deprecated version must pay additional deprecation fee.

Please refer to the revised plan and schedule summarized as below,
1.     Withdrawal of the following on January 28, 2019:

Bluetooth Specification Version 2.0 + EDR

2.     Deprecation of the following on January 28, 2019 and withdrawal on July 1, 2020:

Bluetooth Specification Version 2.1 + EDR

Bluetooth Core Specification Addendum 1

Bluetooth Specification Version 3.0 + HS

Bluetooth Specification Version 4.0

Bluetooth Core Specification Addendum 2

Bluetooth Core Specification Addendum 3 revision 2

Bluetooth Core Specification Addendum 4

Bluetooth Specification Version 4.1

Nordic's information about Bluetooth Core Specification's Impact!

What impact does the deprecation and withdrawalof Bluetooth Core Specification V4.0 & V4.1 have on your current and futureproducts? (Quoted from Nordic Blog)

Raytac Corporation 勁達國際電子有限公司

A BT4.1 & BT 4.2 & BT 5.0 module maker based on Nordic nRF51 & nRF52 solution 

(nRF51822 & nRF51422 & nRF52832 & nRF52810 & nRF52840)

www.raytac.com          email: cs@raytac.com          Tel: +886.2.3234.0208

Wordpress
Raytac Laser

Nordic nRF52832 & nRF52840 藍牙模組模塊方案

自從Nordic發佈了nRF52840方案, 很多客戶就對和nRF52832兩者間的選擇非常困擾. 勁達國際電子(Raytac Corporation)以所生產的模組模塊提供一個簡單的方案比較表, 希望能提供客戶能快速了解兩者的差異！

Visit Raytac in Global Sources 2018 Fall Exhibition, Hong Kong

With over 3,800 exhibitors gathering in Hong Kong, Global Sources has become one of  the largest specialized sourcing trade fair around electronics.

We are excited to announce that Raytac will be in attendance over there to present our latest products: 

1. Nordic nRF52840 Solution Module: MDBT50Q Series

2. Nordic nRF52810 Solution AT Command Module

3. Nordic nRF52832 Solution AT Command Module

4. Osram Laser Solution: Ultra Low Power Direct Green Laser Module

5. Bluetooth Application

To know more about Raytac, why not come over to have a chat!

Looking forward to seeing you in Hong Kong!

Raytac Corporation

A member of SIG and Thread Group

A BT 4.0 & BT 4.2 & BT 5.0 module maker based on Nordic nRF51 & nRF52 solution 

(nRF51822 & nRF52832 & nRF52810 & nRF52840)

www.raytac.com            Tel: +886.2.3234.0208

email: service@raytac.com

Wordpress

Raytac nRF52840 Module MDBT50Q FCC ID Granted

Raytac's EE policy (Easy Employee) core is to provide the pre-certified modules.
Benefits from this policy, products built by Raytac's module may save or reduce the procedure in certification application process which successfully improved Time To Market efficiency and Cost Effective for all customers.

Raytac's latest module, MDBT50Q series module employed Nordic nRF52840 solution has developed 3 lines with different antenna type.
MDBT50Q-1M: Chip Antenna
MDBT50Q-P1M: PCB Antenna
MDBT50Q-U1M: u.FL connector with external Antenna.

We are glad to announce that MDBT50Q series modules have FCC Part 15 C Regulation Certificated granted with FCC ID: SH6MDBT50Q.

FCC Category: Portable Device
Product Name: Bluetooth Low Energy & IEEE802.15.4 Combo Module
Certified Protocol : BT5 & IEEE 802.15.4
                       

                  

Certification Detail

Certification Item

MDBT50Q-1M (Chip Antenna Version)

MDBT50Q-P1M (PCB Antenna Version)

MDBT50Q-U1M (External Antenna Version, Listed in below)

Raytac Corporation 勁達國際電子有限公司

A BT4.1 & BT 4.2 & BT 5.0 module maker based on Nordic nRF51 & nRF52 solution 

(nRF51822 & nRF51422 & nRF52832 & nRF52810 & nRF52840)

www.raytac.com          email: cs@raytac.com          Tel: +886.2.3234.0208

Wordpress
Raytac Laser

Raytac Product Change Notice (PCN) Announcement for Nordic nRF52810 Solution

Dear Customers,

Raytac would like to announce Product Change Notice (PCN) for Module line: MDBT42Q-192K & MDBT42Q-P192K, which are built based on Nordic nRF52810 Solution.

PCN No.: PCN-17112201

Description of Change:

MDBT42Q-192K and MDBT42Q-P192K Modules of Nordic nRF52810 solution change PCB color from Blue to Green and remove the black dotting on metal shielding case.

Nordic nRF52810 Raytac Module MDBT42Q-P192K & MDBT42Q-192K Spec Sheet Updated

Raytac updated nRF52810 module spec sheet to version B.

We are suggesting all developers refer to the updated Spec Sheet accordingly

Module Part No.: 

MDBT42Q-P192K

Module Part No.: 

MDBT42Q-192K

MDBT42Q&MDBT42Q-P Spec Sheet (nRF52810) download link:

http://www.raytac.com/download/MDBT42/(nRF52810)%20MDBT42Q-192K%20&%20MDBT42Q-P192K-Version%20B.pdf

Raytac Corporation

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

(nRF51822 & nRF51422 & nRF52832 & nRF52810 & nRF52840)

www.raytac.com            Tel: +886.2.3234.0208

email: service@raytac.com

Wordpress