Raytac is glad to announce a brand new AT command module line released today.
Nordic announced their 6th multi-protocol solution of nRF52 series with nRF52820, which supports Bluetooth Low Energy (BLE), Bluetooth mesh, Thread, Zigbee and 2.4GHz proprietary wireless connectivity.
Like other nRF52 siblings, nRF52820 highlights a powerful 64MHz 32bit Arm Cortex-M4 processor, includes 256Kb Flash Memory and 32Kb RAM, features of Bluetooth 5.2, 5.1 and 5 including long range and high-throughput of 2Mbits per second, as well as direction finding, low energy power control and low energy isochronous channels.
A full speed (12Mbits per second) USB 2.0 interface and 1.7~5.5V operation voltage bring a wide range of commercial and industrial wireless applications to nRF52820. To support nRF52820’s development, Nordic released SoftDevice S112, a new memory-optimized central stack. S112 now released as a alpha and will have full SDK (SDK V16.0.0) support coming in Q2 2020.
Here introduce the firmware perspective about how to program your code onto MDBT50Q-RX dongle.
Believed all readers have done the hardware setting and now has well prepared to load the code onto the dongle. (If not yet done the hardware setting, pls find it here)
In this blog, we will introduce the procedure based on below 2 scenarios
So, I thought we’d take this in two simple steps.
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.
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:
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.
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.
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:
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 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 🙂
We encourage readers to visit Raytac’s website to obtain the detail information
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
Raytac today announced (Central / Master) AT command dongle released.
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.
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 email@example.com
Have a good day and we at Raytac wish you smooth and happy tinkering 🙂
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.
MDBT50Q Module Series Mass Production has completed, customers who are interested in nRF52840 solution may contact with firstname.lastname@example.org 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.