atproto icon indicating copy to clipboard operation
atproto copied to clipboard

Socket Client - Can't send hex 0x00

Open ivanroberto opened this issue 11 years ago • 2 comments

Hi Igrr,

On socket client, using +CIPSENDI, It works for 0xFF, 0x01, etc. But i got an error if i try to send 0x00, as you can see in the code below:

AT+CIPSENDI=0,"\xFF"

OK

+CIPSENDI:0
AT+CIPSENDI=0,"\x01"

OK

+CIPSENDI:0
AT+CIPSENDI=0,"\x00"

ERROR

Thanks again

ivanroberto avatar Nov 28 '14 17:11 ivanroberto

Hi, yes, it's actually mentioned in the documentation (search for \00). Need to rework things a bit to implement that. On Nov 28, 2014 8:33 PM, "ivanroberto" [email protected] wrote:

Hi Igrr,

On socket client, using +CIPSENDI, It works for 0xFF, 0x01, etc. But i got an error if i try to send 0x00, as you can see in the code below:

AT+CIPSENDI=0,"\xFF"

OK

+CIPSENDI:0 AT+CIPSENDI=0,"\x01"

OK

+CIPSENDI:0 AT+CIPSENDI=0,"\x00"

ERROR

Thanks again

Reply to this email directly or view it on GitHub https://github.com/igrr/atproto/issues/26.

igrr avatar Nov 28 '14 18:11 igrr

OK Igrr. Thanks for your attention. I will need this because a have to transffer binary data.

No worries. Thanks for your time

ivanroberto avatar Nov 28 '14 19:11 ivanroberto