BX3105 fails to connect to Holux M-1200E BT GPS device


#1

I have tried connecting to a Holux M-1200E BT GPS device but recieve the following:

ets Jun 8 2016 00:22:57

rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0x00
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff80b8,len:8
load:0x3fff80c0,len:460
ho 0 tail 12 room 4
load:0x40078000,len:16040
ho 0 tail 12 room 4
load:0x40080000,len:296
entry 0x40080060

READY

+SRBTINQ: “00:1b:c1:07:d9:7e”,001f00,-71
+SRBTINQ: “00:1b:c1:07:d9:7e”,001f00,-71
OK

+SRBTSTATE: 1,2,1
OK

+SRBTCFG: 1,0,“00:1b:c1:07:d9:7e”,SPP,0
OK

+SRBTPAIR: “00:1b:c1:07:d9:7e”,0,34

Looking this up the is a failure to pair with HCI code I assume 0x34 “Reserved Slot Violation”.

I am able to connect to a Garmin GLO using this same command sequency just fine. I am able to connect to this same Holux M-1200E just fine from other BT devices. So it seems there is some incompatability between the BX3105 and the Holux M-1200E? The Holux is an old BT Classic 1.2 device, perhaps this is a hint as to the issue?

Any suggestions for how to connect to the Holux greatly appreciated. I am new to the BX3105 and may well be doing daft things …


#2

Hi,

What firmware are you running on the unit (at+fmr)? P1 firmware is due but in the next week or so on the FOTA server, this might fix it.

In theory the BT 1.2 should not affect the unit connecting because it should all be backward compatible.

Regards

Matt


#3

Thanks Matt:

R1.3.0.201816011422.BX310x_1


#4

Will,

That’s reasonably recent for what we have released (the latest is 1.3.1). You will need to test the P1 firmware when it comes out in the next week or so, if it still fails then I think you will need to push back into your commercial channel for some support.

Regards

Matt


#5

Sounds like a plan, thanks!