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: http://www.raytac.com

 

Come to visit Raytac at Embedded World #Hall 3 / 3-520

With over 1,000 exhibitors gathering in Nuremberg, Germany on 26 Feb.~29 Feb., 2019 , Embedded World has become one of  the biggest trade fair among the IoT Technologies.

RAYTAC27-20181220_lo

BLE Module Firmware Development Q&A: NFC pins creates “Error 404 – signal not found” (technically)

When you start developing your firmware for your Nordic nRF52832 solution-based Raytac BLE module, you will (like on most other projects) bump into some difficulties.

The other day, we had yet another case where a simple thing caused major difficulties for even some of the brightest people – a customer couldn’t get their GPIO direction bit to work.

Although not too difficult to solve, it’s a common error that most customers end up having on our modules and that is because Pin 0.09 & 0.10 are set to NFC per Nordic’s default settings. In order to be able to use these pins as normal GPIOs, you will have to change those settings.

The two pins I am talking about are the ones linked to the NFC-part to the far left in the circuit example below:


nRF52832 MDBT42V Schematic.png

So, to convert these two pins to normal GPIOs, here’s what you need to do:

In SES, you’ll need to add CONFIG_NFCT_PINS_AS_GPIOS.

Pic 1
Right-click on the project and click “Edit Options”

Pic 2
Select “Common”, click on “Preprocessor” under “Code” and then click “CONFIG_NFCT_PINS_AS_GPIOS”

Check out the link below for a reference example on Nordic’s DevZone.

Reference link: Nordic DevZone – NFC pins into GPIOs

 

Raytac Corporation
A BT4.1 & BT4.2 & BT5 module maker based on Nordic nRF51 & nRF52 solution 
(nRF51822 & nRF51422 & nRF52832 & nR52810 & nRF52840)
www.raytac.com          email: cs@raytac.com          Tel: +886.2.3234.0208

New Distributor Announcement (Russia) – PR Electronics

Raytac is glad to announce that we has expanded our distributor network to CIS Countries (Russia), Ukraine, Latvia, Lithuania. The distribution agreement covers sales, marketing, and support for Raytac Corporation’s full range of Modules lines, including Nordic’s proven nRF51 Series, nRF52 Series, and nRF52840 in the territory.

Raytac Nordic Module Line

PR Electronics is a Distributor of Electronic components and Modules

with offices in Russia and Belarus. The company now has 51 employees and 4 sales offices.

Key market segments: Automation, POS terminals and vending systems, Telecommunications, Security systems, Medical, Navigation.

  • Management: ISO 9001:2015 qualified
  • Stock maintenance: Reliability and flexibility
  • Add-on financial logistics
  • Experienced sales team with technical background
  •  Quick technical support through trained FAEs

With recent solid demand and positive feedback receiving from market, we strongly believe that IoT is the future to enhance people’s life.

With PR Electronics’s join of Raytac’s module distribution network, we truly expect he complementary of network portfolio can bring the opportunity and competitive advantage along with a speedy and convenient accessibility for developers.

 

PR Electronics

Contact: Pavel Lyashenko

Tel: +7 (499) 500-56-40  / Телефон/Факс: +7 (499) 500-56-40

Fax: +7 (495) 937-13-27

Email: lyashenko@premier-electric.com

Website: www.prelectro.com

Address: Andronovskoe Roadway, 26, Moscow 111024 Russia

                  111024 г. Москва, Андроновское шоссе 26

спецификации Bluetooth Core  под версией 5

спецификации Bluetooth Core  под версией 4.2

спецификации Bluetooth Core  под версией 4.1

CD卡-2
Raytac Corporation
A BT4.1 & BT4.2 & BT5 module maker based on Nordic nRF51 & nRF52 solution 
(nRF51822 & nRF51422 & nRF52832 & nR52810 & nRF52840)
www.raytac.com          email: cs@raytac.com          Tel: +886.2.3234.0208

Nordic nRF52832 & nRF52840 Module Solution

After Nordic released nRF52840, the confusion raised what the difference between nRF52832. Raytac provided an easy comparison chart based on module solution hopes to provide a quick understanding in between.

CD卡-2

Raytac Module Now Is Available in Chip 1 Stop

To provide developers a quick access of Raytac BT5 / BT4.2 modules, Raytac announced the corporation with OneChipStop, an Arrow company, have modules and development kit listed.

We encourage customers who is interested in IoT and Bluetooth Low Energy may visit below link for more information.

Raytac is one of the most important 3rd party module maker listed in Nordic’s list located in Taiwan,  also the one of the biggest module supplier all over the world.

With the passion Raytac’s team possessed, the effort is aimed to create the maximum benefits contributes by pre-certified modules.

Bluetooth QDID Granted:

BT4.1:  MDBT40 Series

BT5 & BT4.2: MDBT42Q / MDBT42 / MDBT42V

Regional RF Safety Regulation

FCC (USA)

IC (Canada)

CE (EU)

MIC Telec (Japan)

KC (Korea)

SRRC (China)

NCC (Taiwan)

To easy developers’s work, speed up the project schedule, lower down the total budget by deploy the module built in products just like a plug and play components is always the ultimate mission Raytac would like to dedicate to all developers.

Raytac QR Code-BLE&Laser-Landscape

Raytac Corporation
A BT4.1 & BT4.2 & BT5 module maker based on Nordic nRF51 & nRF52 solution 
(nRF51822 & nRF51422 & nRF52832 & nR52810 & nRF52840)
www.raytac.com          email: cs@raytac.com          Tel: +886.2.3234.0208

Come to visit Raytac at Embedded World #Hall 3 / 3-613

With over 1,000 exhibitors gathering in Nuremberg, Germany, Embedded World has become one of  the biggest trade fair among the IoT Technologies.
Raytac will be in attendance and present our latest module MDBT50Q series which are built based on Nordic nRF52840 solution and Mesh network implements.
We look forward to seeing you there.
Nordic Module Embeded World
Raytac nRF52840 BLE Module
Raytac Corporation
A BT4.1 & BT4.2 & BT5 module maker based on Nordic nRF51 & nRF52 solution 
(nRF51822 & nRF51422 & nRF52832 & nR52810 & nRF52840)
www.raytac.com            Tel: +886.2.3234.0208
email: service@raytac.com

Nordic Mesh Network Development Update

Mesh Network has grabbed the highlight of BLE development.
To keep all Nordic users get the updated information post, Raytac keep closely watching for every step Nordic achieved and summarized current status in below.
Mesh-Message Relay & Flooding.png

Nordic Licensed A Free Development IDE-Embedded Studio

Nordic announced it recently has signed with SEGGER to license all developers allowed to use Embedded Studio to develop Nordic nRF51 & nRF52 application freely without any limitations.

Getting started with SEGGER Embedded Studio and the nRF5 SDK Tutorial Video:

Nordic nRF51822 VS. nRF52832 VS. nRF52810 BLE Solution Specification Comparison Chart

Nordic Semiconductor, a BLE solution leading provider, has released different solutions to fulfill IOT various implements. However, Raytac acknowledged there are still a lots of developers are still confused about the difference among nRF51822, nRF52832, nRF52810.
Raytac would like to contribute the comparison chart in below in order to provide a speedy understanding in between solutions.
nRF51 VS nRF52