REMOTE_ADDR Corruption?

[robd0506]

Hello,
I am trying to use AUTO_CONN=2 on a new project, and I am running into problems with the REMOTE_ADDR configuration. The value seems to be getting corrupted. I have verified this with V7.1 and 7.2 of the firmware.

set REMOTE_ADDR=0123456789AB
OK
get REMOTE_ADDR
REMOTE_ADDR=01234589AB0067
OK

Is there a known work-around or a fix in the works?

Thanks!
Rob

[mlw]

@robd0506,

I presume the unit does not auto connect to the device in question (might just be an incorrect reading length issue)?

Regards

Matt

[robd0506]

Thanks for the reply.
Yeah, it won’t connect to the device. I’m not sure what you mean by length issue, but the above was from a TeraTerm session.

[mlw]

@robd0506,

I meant that it could have been that the firmware was incorrectly reading the address out of memory but might have been ok to connect to the the BT device but given it refuses to connect then it does sound like a firmware issue. For this you are going to need to push it though your commercial channel to have tickets raised, etc.

Regards

Matt

[alho]

topic could be a duplicate/same issue:

BC127 Auto Connect with AUTOCONN=2 not working

Hi there, I’m trying to reconnect using the AUTOCONN=2, but it doesn’t work for me. I tried it with a mobile phone (HFP) and a BLE device. I paired them both, so they are in the Paired Device List (PDL). But when I manually set the remote address, then WRITE and RESET the bc127, it does not autoconnect to the defined address. Nothing happens on console except the start-up code (…READY). But the configurations stayed permanent, the AUTOCONN and the REMOTE_ADDR is set. If I use AUTOCONN=1 it’s…