Raytac’s UART Service (AT Command) – How do you get started?

Easy! At least when you know what to doMany 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 you want or need.
For example, if you have a device set to have the name “I_love_Bluetooth” 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.

  1. 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:

  1. 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 😀
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:

  1. 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

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

MDBT50Q-RX-ATM-1.jpg

Raytac AT command is built based on Nordic UART service, aka NUS, which is similar to SPP (Serial Port Profile) applied in Classic Bluetooth (BT2 and BT3)

To service the Bluetooth bridging works, AT command modules or dongle comes with both Central/Master & Peripheral/ Slave role available.

Latest released MDBT50Q-RX-ATM is a USB dongle designated to connect to PC or Machine acted as the Central / Mater role supporting below commands.

List of supported commands

  • Setting of scanned device name
  • Setting of scanned base UUID/service UUID/TX character/RX character
  • Setting of scanned RSSI threshold
  • Selective data rate of 1M bps, 2M bps or 125K bps on-air
  • Set TX output power in 6 levels.
  • Set scanning time
  • Enable/disable scanning
  • Set LED pattern indicating scanning or connecting status
  • Auto UART baud rates
  • Use external 32.768KHz oscillator
  • Recover-to-default setting with software method
  • System reset of software
  • Set serial number and retrieve
  • Retrieve MAC Address
  • Support maximum MTU 247bytes / data payload up to maximum 244 bytes

MDBT50Q-RX-ATM-2 Command Table.jpg

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

A BT5 & BT 4.2 & BTv4.1 module maker based on Nordic nRF51 & nRF52 solution

(nRF51822 & nRF52832 & nRF52810 & nRF52811 & nRF52840)

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

 

Raytac Central Role AT Command USB Dongle MDBT50Q-RX-ATM Released

Raytac today announced (Central / Master) AT command dongle released.

Part No.:

MDBT50Q-RX-ATM

Raytac AT Command Module Family

nRF52840 is Nordic’s latest and advanced solution, which brings a new interface “USB” from other lines, has drawn the attention among developers. 


Raytac developed AT Command  (Master / Central ) solution based on nRF52840 solution, fulfilled the demand of USB interface, missioned to deliver a full coverage of 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 is  eliminating the need for RF design expertise, and speeding time to market for complex M2M IoT applications. 


AT command module is an easy solution provides developers a quick breakthrough to Bluetooth connection. Without firmware effort needed, simply have commands setting on MCU and the start to enjoy the implement of bridging connectivity between devices through Bluetooth.

After Raytac’s 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 & nRF51422 & nRF52832 & nRF52810 & & nRF52811 &nRF52840)
www.raytac.com email: cs@raytac.com Tel: +886.2.3234.0208

 

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:
Burning pins on MDBT50Q-RXFurther down in the specification sheet, in section 9, you will find pictures illustrating where exactly on the PCB you can find these pins:
Pin locations

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:

MDBT50Q-RX and J-Link connection

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:

J-Link Cable Connection

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

 

How To Use MDBT50Q Demo Board (MDBT50Q-DB)

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 
mdbt50q demo board package 拷貝

Raytac Released nRF52840 USB Dongle “MDBT50Q-RX”

Raytac released nRF52840 USB Dongle which deployed MDBT50Q-P1M module offers a Bluetooth 5 specification granted, FCC/IC/Telec(MIC)/KC/SRRC/NCC/WPC pre-certified, and CE/RCM compliant solution.

Raytac nRF52840 Dongle MDBT50Q-RX
Abstract molecule structure on dark blue color background. Vector illustration of Communication – network for futuristic technology concept

Raytac BT5 MDBT50Q Series Module (Nordic nRF52840 Solution) Mass Production

MDBT50Q Module Series Mass Production has completed, customers who are interested in nRF52840 solution may contact with service@raytac.com for further information.

Raytac’s MDBT50Q module deploy Nordic nRF52840 is a Bluetooth 5 (BLE), Zigbee and Thread (802.15.4) modular solution and is an advanced multi-protocol SoM with an ARM® Cortex™-M4F CPU and featured built-in USB and 5.5V compatible DC/DC supply.


The compact size 10.5 x 15.5 x 2.0 (2.2)mm incorporates 48 GPIO,  integrated various antenna types option (Chip Antenna, PCB antenna, u.FL connector) provides developers flexibility to meet most IoT Application Demanding, Connectivity Range Requirement, BOM Cost Saving, Designs Simplifying, and Time-TO-Market Efficiency.

nRF52840 MDBT50Q Family 拷貝

Bluetooth 5-ready Nordic nRF52840 multi-protocol SoC released!

 

Raytac Corporation

Bluetooth module maker based on Nordic nRF51 & nRF52 solution 
(Nordic nRF51822 & nRF5142 & nRF52832 & nRF52840)
Bluetooth Specification Version: BT4.0 & BT4.1 & BT4.2
Tel: +886.2.3234.0208
email: service@raytac.com
http://raytaccorp.blogspot.tw/2016/12/bluetooth-5-ready-nordic-nrf52840-multi.html

Quoted from Nordic Press released!
https://www.nordicsemi.com/eng/News/News-releases/Product-Related-News/Bluetooth-5-ready-SoC-from-Nordic-redefines-scope-for-smart-home-IoT-and-wearables-by-delivering-4x-range-2x-bandwidth-and-best-in-class-security

Nordic Semiconductor has today released the new nRF52840 multi-protocol SoC with on-chip support for the upcoming Bluetooth 5 specification. In addition to Bluetooth 5 the nRF52840 also introduces on-chip support for the 802.15.4 standard. With Bluetooth 5’s new high throughput and long range modes and 802.15.4, it offers unparalleled development opportunities for connected devices for IoT. These opportunities include advanced single-chip wearables, wearables with payment options and connected home devices.
 
Bluetooth 5 will undergo ratification by the Bluetooth SIG beginning December 6th2016. Upon completion, we will provide Bluetooth 5-ready SoftDevices to support nRF52840 and the nRF52832 (high-throughput mode only).