Raytac announced nRF52805 module, MDBT42T series, has moved to mass production stage.
Raytac announced nRF52805 module, MDBT42T series, has moved to mass production stage.
Raytac is glad to announce a brand new AT command module line released today.
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.
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.
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:
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.
Raytac’s AT command central role module, deploys Nordic nRF52832 solution.
There are 2 major features which has drawn developers’ dramatic attention.
1. Supports scanning other makers’ AT command peripheral module as long as based on peripheral’s UUID/TX/RX character can be matched.
2. Supports scanning Beacon company ID/UUID (31 bytes Beacon)
AT command module, 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 Peripheral (Salve) role AT command module released, the demand of Central role has been highlighted by developers.
To have a completed solution, Raytac today announced Central role, as known as Master, AT command module released.
MDBT42Q-ATM (Chip Antenna Version)
MDBT42Q-PATM (PCB Antenna Version)
Differ from Peripheral role AT command module built by nRF52810 solution, Central role AT command module deployed Nordic nRF52832 which employees 64K RAM and 512K Flash Memory.
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!
In order to help developers easily implement the AT command module into application, Raytac released AT command module Demo Board for quick development.