How do I pair with a BLE peripheral from a BC127 acting as central? (It has Melody Audio V6.1.0.)
I can scan for it and open a connection, but sending a “PAIR xxxxx” just end in PAIR_ERROR, and I don’t get a SM_PAIRING_AUTH_IND on my BLE peripheral.
My BLE peripheral is a BC118 running custom firmware.
Thanks!
/Thomas Fogh
Anyone?
Right now my peripheral is just running the CSR hr_sensor sample application. I can connect and get notifications but pairing fails using the MelodySmart command PAIR.
If I use my phone and the BLE scanner app (play.google.com/store/apps/deta … blescanner) it works fine.
And I have also tried using a BLE USB dongle and that can also pair.
/Thomas Fogh
Thomas,
Can you upgrade the BC127 to the latest 6.1.4 firmware, I know one of the guys has used this and done what you are trying to achieve although I am having issues with it and neither of us is using custom firmware on the BC118.
Regards
Matt
I’ve upgraded to 6.1.4 but I still get a PAIR_ERROR.
Not sure where the problem is, I have it working as per the attached.
Regards
Matt
BC127 (central) connecting to BC118 (peripheral).zip (1.03 KB)
Hi Matt,
You’re not trying to pair.
I can also create a connection but pairing doesn’t work. I just get a PAIR_ERROR.
Thomas,
Can you send me the sequence you are using in the same way I did so I can compare and play (and ask other people)?
Regards
Matt
You can run the “HR Sensor” sample from CSR on the BC118.
version<CR>
BlueCreation Copyright 2017<CR>
Melody Audio V6.1.4<CR>
Build: 1493828294<CR>
<HT> Bluetooth address 20FABB019008<CR>
<HT> Profiles: A2DP AVRCP HFP BLE SPP PBAP MAP<CR>
<HT> Codecs: SBC<CR>
OK<CR>
status<CR>
STATE CONNECTED[0] CONNECTABLE[ON] DISCOVERABLE[ON] BLE[IDLE]<CR>
OK<CR>
SET BLE_CONFIG=1<CR>
OK<CR>
SCAN 5<CR>
PENDING<CR>
SCAN 0015BC888888 0 <0015BC888888> 06 -91db<CR>
SCAN 0015BC229A54 0 <0015BC229A54> 06 -96db<CR>
SCAN 0015BC888888 0 <0015BC888888> 06 -90db<CR>
SCAN 00025B00B91B 0 <CSR Keyboard> 05 -56db<CR>
SCAN 0015BC123456 0 <0015BC123456> 06 -91db<CR>
SCAN F4F5D8C48A31 0 <UNKNOWN> 06 -86db<CR>
SCAN 0015BC888888 0 <0015BC888888> 06 -93db<CR>
SCAN 0015BC123456 0 <0015BC123456> 06 -92db<CR>
SCAN 00025B00B91B 0 <CSR Keyboard> 05 -56db<CR>
SCAN 0015BC888888 0 <0015BC888888> 06 -87db<CR>
SCAN 00025B00B91B 0 <CSR Keyboard> 05 -56db<CR>
SCAN 0015BC123456 0 <0015BC123456> 06 -91db<CR>
SCAN 00025B00B91B 0 <CSR Keyboard> 05 -58db<CR>
SCAN 0015BC888888 0 <0015BC888888> 06 -92db<CR>
SCAN 00025B00B91B 0 <CSR Keyboard> 05 -55db<CR>
SCAN 0015BC229A54 0 <0015BC229A54> 06 -95db<CR>
SCAN F4F5D8C48A31 0 <UNKNOWN> 06 -80db<CR>
SCAN 0015BC888888 0 <0015BC888888> 06 -87db<CR>
SCAN 00025B00B91B 0 <CSR Keyboard> 05 -58db<CR>
SCAN 0015BC888888 0 <0015BC888888> 06 -94db<CR>
SCAN 0015BC888888 0 <0015BC888888> 06 -87db<CR>
SCAN 0015BC888888 0 <0015BC888888> 06 -92db<CR>
SCAN_OK<CR>
OPEN 00025B00B91B BLE 0<CR>
PENDING<CR>
OPEN_OK 14 BLE 00025B00B91B<CR>
PAIR 00025B00B91B<CR>
PENDING<CR>
PAIR_ERROR 00025B00B91B<CR>Thomas,
I have confirmed that the BC127 does not support bonding hence if you set bonding on with the BC118 (which does support it) the connection will be rejected.
Between these two units you can only set up a connection and send/receive data.
Regards
Matt
Hi Matt,
Must BLE services require encryption, LE Security Mode 1 and either Security Level 2 or 3.
The BC127 also fails to respond to a SM Slave Security Request.
If you want your customers to be able to connect to anything other than Melody Smart modules using BLE, you need to implement bonding.
/Thomas
Thomas,
I don’t get your meaning?
It is just the BC127 that does not implement bonding on BLE, BC118 does so it is just the combo you are using that does not do exactly what you want.
Regards
Matt
Hi Matt,
Yes. So your customers will not be able to connect 3rd party BLE devices to their BC127, like a BLE remote or keyboard.
/Thomas
Thomas,
Yes but this is not typically where the B127 is aimed at. I will point this out to product management and make sure that it is implemented in future modules.
Regards
Matt
Hi Matt,
Thanks! It should be a fairly simple firmware update as you already support this for classic Bluetooth.
/Thomas
Hi,
have there been any changes yet? I’m working with the bc127, Melody V6.1.5., want to use bc127 as central.
It seems that BLE bonding is still not supported or is it not working just for me?! Did anybody make a successfull bonding with the bc127 to any other peripheral device?
Regards
Alex
Thomas,
No nothing has changed, we are about to bring out 7.1 firmware but bonding has not been added as a feature. Like all things we are commercially driven so you will need t push this with your commercial channel so see if you can give them a reason to drive it through.
Regards
Matt
Hi all,
For info BLE Bonding support has been added to Melody 7.
To initiate bonding and start encryption from the BC127, use BLE_SECURITY command with the link ID of the BLE connection.
Regards,
Hi,
I am trying to open a BLE connection from BC127 to my headset. When i send OPEN <bd_addr_of_headset> BLE 0 command, i get a response OPEN_OK but immediately i get another response CLOSE_OK. Below is the snippet of the terminal:
VERSION
Sierra Wireless Copyright 2018
Melody Audio V7.2
Build: 1534785311
Bluetooth addresses: 20FABB075D42 4CECB41AEBF3
Profiles: A2DP AVRCP AGHFP BLE SPP PBAP MAP
Codecs: SBC
OK
STATUS
STATE CONNECTED[0] CONNECTABLE[OFF] DISCOVERABLE[OFF] BLE[IDLE]
OK
SCAN 5
PENDING
SCAN 0E69EF2FBC6F 1 00 -61dBm
SCAN 233ABD62ABF1 1 00 -92dBm
SCAN 0EA4F9059110 1 00 -69dBm
SCAN 02B237266AEB 1 00 -76dBm
SCAN 0EA4F9059110 1 00 -74dBm
SCAN 0E69EF2FBC6F 1 00 -60dBm
SCAN 02B237266AEB 1 00 -83dBm
SCAN 02B237266AEB 1 00 -76dBm
SCAN 0E69EF2FBC6F 1 00 -54dBm
SCAN 233ABD62ABF1 1 00 -81dBm
SCAN 0EA4F9059110 1 00 -59dBm
SCAN 2C41A1C686F0 0 19 -77dBm
SCAN 0EA4F9059110 1 00 -71dBm
SCAN 0E69EF2FBC6F 1 00 -54dBm
SCAN_OK
OPEN 2C41A1C686F0 BLE 0
PENDING
OPEN_OK 14 BLE 2C41A1C686F0
CLOSE_OK 14 BLE 2C41A1C686F0
LIST
LIST 2C41A1C686F0 BLE
OK
BLE_SECURITY 14
ERROR 0x0011
I am currently using Melody v7.2, but still not able to do bonding with headset. Below is my CONFIG:
CONFIG
AUDIO=0 0
AUDIO_ANALOG=15 15 1 OFF
AUDIO_DIGITAL=0 44100 64 100A00 OFF
AUTOCONN=0
AUTO_DATA=OFF OFF
BALANCE=100 100
BATT_CONFIG=OFF 145 4250 1500 150
BC_SMART_CONFIG=68E3 28F0 89F7 D93C ON
BEACON_DATA=0 00 11 22 33 44 55 66 77 88 99 AA BB CC DD EE FF 04 D2 16 2E EE
BLE_CONFIG=0 OFF 40 ON
BLE_CONN_PARAMS=128 12 24 40 0 400 100 400 400 64 400 400
BT_STATE_CONFIG=0 0
BT_VOL_CONFIG=A 60 10 1
CLASS_1=OFF
CMD_TO=20
COD=240404
CODEC=0 OFF
DEEP_SLEEP=OFF
DEVICE_ID=0001 0002 0003 0004 0005 0006 0007 0008
ENABLE_BATT_IND=ON
ENABLE_LED=ON
ENABLE_SPP_SNIFF=OFF 0 0 0 0 0
GPIO_CONFIG=ON 0
HFP_CONFIG=OFF ON OFF OFF OFF OFF
HIGH_SPEED=OFF OFF
LOCAL_ADDR=20FABB075D42 4CECB41AEBF3
MAX_REC=2
MM=OFF OFF 0 OFF OFF OFF OFF OFF
MUSIC_META_DATA=OFF
MUSIC_OLD_AVRCP=OFF
NAME=BC-075D42
NAME_SHORT=BC075D42
PIN=0000
PROFILES=0 2 0 2 2 1 2 1 0 0 1 0
REMOTE_ADDR=000000000000
SPP_UUID=00 00 11 01 00 00 10 00 80 00 00 80 5F 9B 34 FB
SSP_CAPS=3
TWS_CONFIG=OFF 1 2
UART_CONFIG=9600 OFF 0
USB_HOST=OFF
VREG_ROLE=1
OK
So could you please let me know, am I doing correctly or need any configuration change?
Regards,
Manish
So is the headset currently bonded to something else? I think you might need to play with the SSP_CAPS value to get it working.
Regards
Matt