Coming to bluetooth in audio applications, we have versions from 3.0 to 5.4. In the practical audio application we have to keep 2-3 things in mind. Like we need what is the max power it is consuming, what is the SNR of the received signal and what is the ideal power conditions. Some other parameters like wireless range, noise in signal, DAC resolution and number of bits also play an important role here. Today in the article we will plot them all and see the difference in performance of a 3.0 and 5.0 bluetooth in real time.

THUMB.png

I have available a lot of them in stock, ranging from 3.0 to 5.0 but here specifically using these two. I have covered an article in detail about these cheap bluetooth modules. There is one manufacturer from China named JIELI who has been working on these BT nodes for a long time. Although the information is not open sourced, so we can not make any changes to the firmware without proper software. Some of the datasheets are shared in the previous article when I am designing my own board using them.

This article is sponsored by PCBWAY. I have created my own BT5.0 with USB-C, you can see the whole project in a github repo here. After plugging an external battery as a power source we can convert any wired headphones/earphones into BT controlled. The PCB is shared below. I am pleased by the quality of PCBWAY services, the PCBs are awesome and work well.

Bluetooth 3.0 and 5.0 Testing RIG/CASE:

IMG_3356.PNG

I am using 5.10 volts out from a constant power supply. The signal is taken from an online signal generator, maxed to all levels @3500Hz sine wave. I chose this signal specifically because it is not much low and not much high frequency comes in hearing range. If we choose between low and high frequency extremes there will be a certain kind of attenuation in signal. I do not want to go in depth but they are because of digital filters used inside the chip. They have a wavy effect in the pass and stop band. To make the test more ideal, the sine wave chosen here is sampled at 44.1KHz which surpasses the nyquist limit almost 40 times. So obviously it is an ideal signal, an ideal 3500 Hz sine wave.

mini_IMG_3372.png

Test 1 - Peak-Peak Amplitude Test:

mini_IMG_3357.png

Both the bluetooth has onboard signal conditioning circuit, in 3.0 we have seen a high amplitude pulse superimposed in signal which is nothing but due to its low resolution will talk about it later. The peak-peak output of 3.0 is 1.90V and in case of 5.0 it is 2.15V. Which is 13% increment over 3.0 Gen BT.

Test 2- Resolution and Number of Bits:

mini_IMG_3368.png

Due to not open sourced documentation we can not get the exact number of bits, and resolution but from a signal engineer perspective we can see something on a scope. It is basically the DAC resolution but here I have seen something different, A high frequency wave superimposed over 3500 Hz wave, which can be seen through FFT but here I don’t available that option. In the case of 3.0 this superimposed wave is of somewhat a lower frequency than 5.0 so it looks awful here. By the way overall 5.0 gives me a smoother signal which also I can see when hooking it with an amplifier there is no any HUM or noise in 5.0 on the other hand 3.0 performs very much worse.

Test 3 - Noise in Ideal Mode:

mini_IMG_3371.png

Here ideal mode is defined as the bluetooth is connected to the source but there is no signal given. The noise is compared with both BT modules. Ideally we should get a straight line when there is no signal but that is not the condition with these DSPs. I have seen a P-P noise of 650mV in 3.0 and 158mV in 5.0. This is where the 5.0 dominates and eliminates the competition. It is almost a 400% reduction in noise levels.

Test 4 - Power Consumption in Ideal Mode:

mini_IMG_3355.png


Here ideal mode is defined as the bluetooth is connected to the source but there is no signal given. In this both the BT modules perform the same. Both are consuming 40mW of power.

Test 5 - Power Consumption in Full Signal Mode:

mini_IMG_3373.png


When both BT modules output...

Read more »