REMOTE_ADDR Corruption?


#1

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


#2

@robd0506,

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

Regards

Matt


#3

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.


#4

@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


#5

topic could be a duplicate/same issue: