Is there data size limitation when using module internal connection service to download file from server? | Telit Cinterion IoT Developer Community
July 26, 2016 - 4:15am, 3435 views
Could someone help me to answer my question?
I use the internal Http service of EHS5 module to download the file from server,
and I found the data size I download is smaller than the data which I want to dowload when I use http or TCP connection to download the file from server.
For example:
Originally I want to download data with the data size 100KB from server, but I can only download 16KB from the server.
at^sics=1,contype,gprs0
OK
at^sics=1,apn,"internet"
OK
at^siss=1,"srvtype","socket"
OK
at^siss=1,conid,1
OK
at^siss=1,address,"socktcps://semadev.schiller.fr:8181"
OK
at^siso=1
OK
^SISW: 1,1
at^sisw=1,131
^SISW: 1,131,0
GET /SUS/public/v1/image/2.16.75
6.5.25.4.6.2.2/000001/100K.bin HTTP/1.1
Host: semadev.schiller.fr:8181
Connection: keep-alive
OK
^SISW: 1,1
^SISR: 1,1
at^sisr=1,0
^SISR: 1,16572 //shows only can read 16,572Byte
OK
at^sisr=1,512
^SISR: 1,512
HTTP/1.1 200 OK
Connection: keep-alive
X-Powered-By: Undertow/1
Server: WildFly/8
Content-Length: 98322 //the target data size is 98,322 Byte return by server
Content-Type: application/octet-stream
Date: Thu, 14 Jul 2016 03:52:45 GMT
The following link is the complete log file.
https://www.dropbox.com/s/i3isp1tw73x6i9x/AT%20command.log?dl=0
Hello,
This is a regretion in this FW. The issue is in SSL stack. It should be fixed in the next release.
Temporary I would propose to switch to non ecnrypted socket (just for development phase). You may also try to downgrade to the one of the previous FWs.
Best regards,
Michał
Hi Michal:
I am so appreciated for your reply.
I also tried to downgrade the firmware, but it seems have the same result.
The at command log file can be downloaded with following link.
https://www.dropbox.com/s/elftqr0b0th2tml/at%20command_20160727.log?dl=0
Is there any other method I could try? or I should wait until the next firmware release?
Hi,
Unfortunately there is no workaround for this. I would recommend to contact your supplier and describe the issue. Please let them know that you have already communicated with Gemalto via developers forum. He should contact his dedicated technical sales. This contact person will be able to obtain the information about the aproximate date of the the fix, and let you know via your distributor.
Best regards,
Michał
OK, thanks,