BC127 connecting automatically but not manually

IoT Modules WiFi and Bluetooth Modules
1

Hi there

I am using a BC127 as A2DP source with autoconn=2 and remote address saved. Here my config list:

AUDIO=0 0
AUDIO_ANALOG=22 15 1 OFF
AUDIO_DIGITAL=0 44100 64 100A00 OFF
AUTOCONN=2
AUTO_DATA=OFF OFF OFF
BALANCE=100 100
BATT_CONFIG=OFF 145 4250 1500 150
BC_SMART_CONFIG=68E3 28F0 89F7 D93C
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 128 ON
BLE_CONN_PARAMS=128 12 6 40 0 400 50 400 400 61 400 400
BT_VOL_CONFIG=A A 10 1
CLASS_1=OFF
CMD_TO=20
COD=240404
CODEC=0 OFF
CONN_TO=0
DEEP_SLEEP=ON
DEVICE_ID=0001 0002 0003 0004 0005 0006 0007 0008
DISCOVERABLE=2 0
ENABLE_BATT_IND=ON
ENABLE_CAPSENSE=OFF
ENABLE_LED=ON
ENABLE_SPP_SNIFF=OFF 0 0 0 0 0
GPIO_CONFIG=ON 0 255
HFP_CONFIG=OFF ON OFF OFF OFF
HIGH_SPEED=OFF OFF
LOCAL_ADDR=20FABB0A4C8F
MAX_REC=2
MM=OFF OFF 0 OFF OFF OFF OFF OFF
MUSIC_META_DATA=OFF
MUSIC_OLD_AVRCP=OFF
NAME=SOUNDING-SOIL
NAME_SHORT=SSoil
PIN=0000
PROFILES=0 0 0 2 2 1 0 0 0 0 0 0
REMOTE_ADDR=0019070CB798
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

When I reset the device with the Bluetooth receiver corresponding to REMOTE_ADDR currently discoverable, I works perfectly.

If I start the BT receiver after the reset and follow the procedure:

INQUIRY 10

PENDING
INQUIRY 0019070CB798 “BT0022” 240404 -74db (several times)
INQU_OK

OPEN 0019070CB798 A2DP

PENDING
OPEN_ERROR A2DP

Am I missing a configuration somewhere?

Thanks,
Sebastien

2

I have the same issue. My fix was to implement a timeout that retries the command every 500ms until it spits back an “OPEN_OK”. It’s causing me more problems than it’s worth, so I’ll probably go back to letting the device auto connect, then making sure the right profiles are open.

FYI, the “LIST” command is a little bit better than INQUERY in my experience.

3

Thanks for infos…

I also forgot to mention that it happens with Melody 6.1. Until last week I was working with an older version (5.0) and didn’t have any problem.