Gemalto is now part of the Thales Group, find out more.

You are here

AT^SISR strange behavior on BGS1-E | Thales IoT Developer Community

November 30, 2017 - 11:55am, 2172 views

It return diffirent with 2 kind of internet profile:

With SOCKET+FTP profile it return 1 line "^SISR: <srvProfileId>, <cnfReadLength>" and then exactly <cnfReadLength> bytes and then 1 line of result "OK\r\n"

But with HTTP profile it return "^SISR: <srvProfileId>, <cnfReadLength>" and then 1 emty line "\r\n" and then <cnfReadLength> bytes and then 1 line of result "OK\r\n".

Why HTTP profile need an emty line for? Is it a bug or what?The document did not mention it. May be the empty line is removed in the future? I am so confusing. Please help!