Raytac announced that the module built by nRF52840 with Rev.2 SoC now has started the mass production shipment.
Raytac Corporation, A Bluetooth Module Maker based on Nordic nRF52840 & nRF52832 & nRF51822 & nRF52810 Solution. Bluetooth Specification Version: BT5 & BT4.2 & BT4.1 & BT4.0
Monday, June 17, 2019
MDBT50Q Series Module Built By nRF52840 Rev.2 (Build Code:DXX) Started Shipment
Nordic Semiconductor has updated nRF52840 SoC version from Rev.1 to Rev.2.
Raytac announced that the module built by nRF52840 with Rev.2 SoC now has started the mass production shipment.
Raytac announced that the module built by nRF52840 with Rev.2 SoC now has started the mass production shipment.
Wednesday, May 22, 2019
Regulations, Certifications and Raytac's Modules - What do we make more convenient for our customers?
Raytac's pre-certified module for your convenience - but how?
So, in this post, we would like to take you on a little journey through most of the important certifications that Raytac has pre-certified their modules with.
The exact topic is actually what you need to know and what that means to you as a Raytac customer.
Obviously, each and every certification has their own rules, so that's how we're going to do this - one by one.
So for the FCC certification, you can as a Raytac customer:
What you will need to do is:
Firstly, for the wireless test, you can refer to Raytac's own certification report so that the lab knows the module itself has passed although it still needs to be tested.
Secondly, the for wire (IO port) test, you will have to do from scratch essentially.
Thus, even though we have applied for KC for our modules, you will still have to test them locally.
Thus, the procedure becomes:
When applying to this certification, you will be in either of these two circumstances:
So, in this post, we would like to take you on a little journey through most of the important certifications that Raytac has pre-certified their modules with.
The exact topic is actually what you need to know and what that means to you as a Raytac customer.
Obviously, each and every certification has their own rules, so that's how we're going to do this - one by one.
- FCC - (U.S.A.)
So for the FCC certification, you can as a Raytac customer:
- Use Raytac's certification ID directly on your finished product's label But you need to:
- Test FCC Part 15B EMC for your finished products
- IC - (Canada)
- Use Raytac's certification ID on your finished product's label (same as FCC) But, just like FCC, you need to:
- Test IC ES003 (EMC)
- This can be combined together with the FCC Part 15B test
- TELEC - (Japan)
What you will need to do is:
- Use Raytac's certification ID on your finished product's label
- KC - (South Korea)
- Test EMC for wireless (KN301489 - same as CE's EN301489)
- Test EMC for wire (IO port) (KN3235)
- If, and only if, your final product is equipped with IO ports, that is.
Firstly, for the wireless test, you can refer to Raytac's own certification report so that the lab knows the module itself has passed although it still needs to be tested.
Secondly, the for wire (IO port) test, you will have to do from scratch essentially.
Thus, even though we have applied for KC for our modules, you will still have to test them locally.
- CE (Radio Equipment Directive 2014/53/EU (RED)) - (EEA, Europe)
- Test on Conducted engineering sample (EN300328)
- You can refer to Raytac's test report, if the test lab accepts it, that is.
To ensure that they do, you can choose to conduct your tests at the same lab as Raytac - SGS.
- You can refer to Raytac's test report, if the test lab accepts it, that is.
- Test on Radiated engineering sample (EN300328)
- Test EMC (EN301489)
- Test Safety (EN60950)
- Subject to change to EN62368 in 2021
- SRRC
- Your end product can either be defined as a "Home Appliances" or an "Office Utilities" product
- Then you can simply refer Raytac's SRRC ID (module policy just like FCC/IC/TELEC)
- Your end product is neither of the above
- You have to apply for your own SRRC ID by testing everything required by the regulation
- NCC
Thus, the procedure becomes:
- Adding functionality of an already existing feature (a.k.a. platform)?
- Then you can simply refer Raytac's NCC ID on your product (module policy just like FCC/IC/TELEC/SRRC)
- New ideas/features?
- Sorry, you have to apply for your own NCC ID by conducting all tests necessary
- RCM
When applying to this certification, you will be in either of these two circumstances:
- CE already done.
- You can refer to your own CE certification and ask your test lab to copy the report to your RCM application.
- CE NOT done.
- You must conduct the test from scratch. But it is a whole lot like CE, meaning:
- Test on Conducted engineering sample
- Test on Radiated engineering sample
- Test EMC
- Test Safety
- Bluetooth Certification
- Apply for Bluetooth SIG's "Adopter Membership" (free)
- You can apply for the membership here
- Purchase your DID
- You can do this directly at Bluetooth SIG's website
- Leverage Raytac's QDID
- To activate your newly purchased DID
- Hardware
- Unless you are still using Raytac's module
- Feature
- Unless you are still using Raytac's module
- Brand Name
- Brand name remains unchanged.
As always - Happy tinkering everybody :)
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 |
Wednesday, May 15, 2019
Raytac Product Change Notice (PCN) Announcement for Nordic nRF52840 Solution
Correspond to Nordic new revision of the IC with key changes (Nordic PCN No.: PCN-111 rev. 1.0)
Raytac would like to announce Product Change Notice (PCN-19051001) for below Module lines which are built based on Nordic nRF52840 Solution
nRF52840 SoC Revision changed from Rev.1 to Rev.2 (Build Code Changed from CXX to DXX)
From MDBT50Q-1M to MDBT50Q-1MV2
From MDBT50Q-P1M to MDBT50Q-P1MV2
From MDBT50Q-U1M to MDBT50Q-U1MV2
Change estimated to become active from 2019/8/1
Raytac would like to announce Product Change Notice (PCN-19051001) for below Module lines which are built based on Nordic nRF52840 Solution
nRF52840 SoC Revision changed from Rev.1 to Rev.2 (Build Code Changed from CXX to DXX)
Change estimated to become active from 2019/8/1
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 |
Tuesday, May 7, 2019
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.
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.
Friday, April 26, 2019
Raytac's UART Service (AT Command Central / Master) - 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.
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".
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:
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:
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 :)
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.
- Device Name
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".
- RSSI
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:
- Slave device's SDK
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:
- 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 |
Monday, April 8, 2019
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.
Wednesday, April 3, 2019
New Distributor Announcement (Turkey & Egypt) - Özdisan Elektronik A.Ş.
Raytac is glad to announce that we has expanded our distributor network to Turkey and Egypt. The distribution agreement with Özdisan Elektronik A.Ş. covers FAE, Engineering, Sales, Marketing and support for Raytac Corporation's full range of module lines, including nRF52840, nRF52811, nR52832 and nRF51 series in territory.
Özdisan Elektronik A.Ş. was founded in 1980 and currently is the leading electronic components distributor in Turkey. The headquarter located in Istanbul and built up 4 sales offices and warehouse in major cities in Turkey cities(Istanbul, Ankara, Izmir, Bursa). Employed RD FAE capability to support the development and evaluation consultant and also Marketing & Sales service.
Not only distribution service, Özdisan Elektronik A.Ş. but also expanded business to PCB & PCB assembly, LED lighting solutions, aluminum coolers aimed to achieve the synergy collaboration all the way from product idea emerging, developing and mass production.
IoT now has become a part of people's life experience and Bluetooth is the key protocol connecting between human and IoT appliance.
Raytac employees Nordic's solution developed series of modules which is a recommended 3rd party module maker listed in Nordic website. All modules from Raytac comes with superior RF efficiency, reliable quality, Bluetooth certification granted, and FCC/IC/CE/Telec/KC/SRRC/NCC pre-certified. Developers who deployed Raytac's module into products may save lots of efforts in RF design expertise and obtain the low cost and time-to-market efficiency.
With Raytac' Bluetooth Low Energy module joined the line card, Özdisan Elektronik A.Ş. expects to advance the service from the Bluetooth world connecting to an unlimited future.
Özdisan Elektronik A.Ş. was founded in 1980 and currently is the leading electronic components distributor in Turkey. The headquarter located in Istanbul and built up 4 sales offices and warehouse in major cities in Turkey cities(Istanbul, Ankara, Izmir, Bursa). Employed RD FAE capability to support the development and evaluation consultant and also Marketing & Sales service.
Not only distribution service, Özdisan Elektronik A.Ş. but also expanded business to PCB & PCB assembly, LED lighting solutions, aluminum coolers aimed to achieve the synergy collaboration all the way from product idea emerging, developing and mass production.
IoT now has become a part of people's life experience and Bluetooth is the key protocol connecting between human and IoT appliance.
Raytac employees Nordic's solution developed series of modules which is a recommended 3rd party module maker listed in Nordic website. All modules from Raytac comes with superior RF efficiency, reliable quality, Bluetooth certification granted, and FCC/IC/CE/Telec/KC/SRRC/NCC pre-certified. Developers who deployed Raytac's module into products may save lots of efforts in RF design expertise and obtain the low cost and time-to-market efficiency.
With Raytac' Bluetooth Low Energy module joined the line card, Özdisan Elektronik A.Ş. expects to advance the service from the Bluetooth world connecting to an unlimited future.
 | Özdisan Elektronik Paz. San. ve Tic. A.Ş. | |
| Name: | Okan Abdi | İbrahim Ekmekçi |
|---|---|---|
| Title: | Genel Müdür Yardımcısı Deputy General Manager | Saha Uygulama Mühendisi Field Application Engineer |
| Email: | oabdi@ozdisan.com | iekmekci@ozdisan.com |
| Tel.: | +90 (61) 420 1882 | Tel: +90 (61) 420 1882 /Ext:230 Mobile: +90 (534) 014 78 76 |
| Web: | www.ozdisan.com | |
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 |
Sunday, March 31, 2019
nRF52840 AT Command USB Dongle MDBT50Q-RX-ATM
To have an easy understanding of Raytac's AT Command USB Dongle, here provides the command table for reader's easy reference.
We encourage readers to visit Raytac's website to obtain the detail information
MDBT50Q-RX-ATM (Click Me)
We encourage readers to visit Raytac's website to obtain the detail information
MDBT50Q-RX-ATM (Click Me)
Thursday, March 28, 2019
Raytac Central Role AT Command USB Dongle MDBT50Q-RX-ATM Released
Raytac welcomes another product to its AT Command family
Part No.:
MDBT50Q-RX-ATM
Raytac developed AT Command (Master / Central ) solution based on Nordic's nRF52840, thus fulfilled the demand of the USB interface and our mission to deliver a full coverage of our AT Command product line.
Raytac’s nRF52840 USB AT Command dongle, MDBT50Q-RX-ATM, is a BT5, FCC/IC/CE/Telec/KC/SRRC/NCC/RCM/WPC pre-certified dongle which eliminates the need for RF design expertise and significantly reduces the time to release your product to market for complex M2M IoT applications.
AT command modules is an easy solution that provides developers a quick breakthrough to Bluetooth connection. Without the need for firmware development, you simply have command settings on the MCU and can start to enjoy the implementation of bridging connectivity between devices through Bluetooth.
After we have completed both Central (Master) & Peripheral (Salve) role AT command module projects, the USB interface has brought up the strongest demand by developers.
Part No.:
MDBT50Q-RX-ATM
Raytac developed AT Command (Master / Central ) solution based on Nordic's nRF52840, thus fulfilled the demand of the USB interface and our mission to deliver a full coverage of our AT Command product line.
Raytac’s nRF52840 USB AT Command dongle, MDBT50Q-RX-ATM, is a BT5, FCC/IC/CE/Telec/KC/SRRC/NCC/RCM/WPC pre-certified dongle which eliminates the need for RF design expertise and significantly reduces the time to release your product to market for complex M2M IoT applications.
AT command modules is an easy solution that provides developers a quick breakthrough to Bluetooth connection. Without the need for firmware development, you simply have command settings on the MCU and can start to enjoy the implementation of bridging connectivity between devices through Bluetooth.
After we have completed both Central (Master) & Peripheral (Salve) role AT command module projects, the USB interface has brought up the strongest demand by developers.
Raytac Corporation 勁達國際電子有限公司
A BT5 & BT 4.2 & BTv4.1 module maker based on Nordic nRF51 & nRF52 solution
(nRF51822 & nRF52832 & nRF52810 & nRF52811 & nRF52840)
(nRF51822 & nRF52832 & nRF52810 & nRF52811 & nRF52840)
| www.raytac.com | email: cs@raytac.com | Tel: +886.2.3234.0208 |
Wednesday, March 27, 2019
Burn your firmware - onto MDBT50Q-RX, that is.
Hi there, folks!
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 ;)
(I am serious! Just look at Plezmo! You see that USB stick? Yep, that's another Raytac for ya)
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 :)
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 ;)
(I am serious! Just look at Plezmo! You see that USB stick? Yep, that's another Raytac for ya)
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)
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 |
Thursday, March 21, 2019
Raytac Product Change Notice (PCN) Announcement for nRF52840 Dongle: MDBT50Q-RX
Dear Customers,
To enable hardware reset function in Raytac's nRF52840 dongle (P/N: MDBT50Q-RX), Raytac's has revised the circuit and issued the PCN accordingly.
Description of the Change:
1. Change circuit design to enable the hardware reset function.
2. Change PCB Imprint
3. Change Label
4. Change Part No.
Here provided the content of the PCN for customer's reference.
Customers those who have been developing firmware based on our previous dongle, please contact us at service@raytac.com to request latest sample for evaluation.
Description of the Change:
1. Change circuit design to enable the hardware reset function.
2. Change PCB Imprint
3. Change Label
4. Change Part No.
Here provided the content of the PCN for customer's reference.
Customers those who have been developing firmware based on our previous dongle, please contact us at service@raytac.com to request latest sample for evaluation.
Raytac Corporation 勁達國際電子有限公司
A BT5 & BT 4.2 & BTv4.1 module maker based on Nordic nRF51 & nRF52 solution
(nRF51822 & nRF51422 & nRF52832 & nRF52810 & nRF52840)
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 |
Wednesday, February 13, 2019
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.
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.
Monday, January 28, 2019
How To Use MDBT50Q Demo Board / MDBT50Q-DB (nRF52840 Solution)
Here provides an easy introduction of How to set up of MDBT50Q-DB!
MDBT50Q-DB, built by Raytac's MDBT50Q-1M deployed nRF52840 SoC with Bluetooth 5 & Thread Combo module Demo Board. Equipped Raytac's MDBT50Q-1M with 1MB Flash Memory and 256KB RAM and Chip Antenna. Certifications include: FCC, IC, CE, Telec, KC, SRRC, RCM, NCC, WPC
Friday, January 25, 2019
MDBT50Q-RX, a nRF52840 USB Dongle, delivers an easy implement for M2M IoT application
Raytac’s BT5 certified nRF52840 USB dongle, MDBT50Q-RX, eliminating the need for RF design expertise, and speeding time to market for complex M2M IoT applications. The Dongle built by Raytac's MDBT50Q-P1M module with FCC/IC/CE/Telec/KC/SRRC/NCC/RCM/WPC certification.
Monday, January 21, 2019
Where To Buy Raytac Bluetooth Module Sample?
To enhance the accessibility to Raytac BLE module sample for evaluation and development, Raytac has put effort to corporate with several channels.
Differ channels may carry various items, we encourage developers firstly visiting Raytac official site. The easy link options listed in each product may help customers to select the friendly channel for approach.
Differ channels may carry various items, we encourage developers firstly visiting Raytac official site. The easy link options listed in each product may help customers to select the friendly channel for approach.
Thursday, January 10, 2019
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.
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
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
Subscribe to:
Posts (Atom)