Problems with FTP upload (BGS2T) | Telit Cinterion IoT Developer Community
December 3, 2016 - 4:51pm, 4348 views
Hy all,
I am currently working on a project with a BGS2T terminal to upload data from a microcontroller to a ftp server.
However, the communication, configuration and upload is working. My only problem is, that if i write a 'char'-number to the module the uploaded file is showing me the corresponding ascii-sign. I have changed the paramters of the AT^SISW commands (binary and interactive text ****) but it makes no difference. If a put data in form of a string to the module everything is fine.
I dont want to convert my binary data into its ascii-sign by adding an offset!
Hope someone can help me!
Greets, Daniel
Hello,
Could you paste a log and ATI1 reply?
Regards,
Bartłomiej
Hy,
the problem was myself i think. The uploaded data was here and if I use the right editor then I can ready my data successfully.
I have no log because I am communicating with the module via a microcontroller.
Greets, Daniel
Thanks for the infromation. So the problem is solved.
Regards,
Bartłomiej
Hi!
I have a problem with upload data to FTP. After AT^SISW command i send data from microcontroller to BGS2 module. I try to use both command format is AT^SISW=0,1500 , and AT^SISW=0,1500,0 to switch module to binary ****. Whan in data stream meet 0x0D byte, then this byte is lost. What could be the problem?
Hi,
where did you notice that this 0x0D byte is missing? I assume you see that it is not present on server? Could you also provide response for "at^siss?" command?
Best Regards,
Tomasz
Hello!
I'm not sure where byte is missing. Microcontroller always fills in massive of data equals 12000 bytes in RAM. This massive сcontains mixed data strings (clear hex, and rearable ASCII symbols). All strings ended 0x0D, 0x0A. Whan i see file size at FTP, then size of file less then 12000 bytes. After research file in HEX Editor at the computer, i not find all 0x0D bytes.
In what moment i shell issue "at^siss?" command?
AT^SISS?
^SISS: 0,"srvType","Ftp"
^SISS: 0,"conId","0"
^SISS: 0,"alphabet","0"
^SISS: 0,"address",""
^SISS: 0,"tcpMR","10"
^SISS: 0,"tcpOT","6000"
^SISS: 1,"srvType",""
^SISS: 2,"srvType",""
^SISS: 3,"srvType",""
^SISS: 4,"srvType",""
^SISS: 5,"srvType",""
^SISS: 6,"srvType",""
^SISS: 7,"srvType",""
^SISS: 8,"srvType",""
^SISS: 9,"srvType",""
OK
Ok, what is the extension of file you are writting to? If .txt could you check if this problem is still present with .bin or .hex file extension? You can also try to configure SISS type to image (from at spec -> at^siss -> address -> ftp -> "type": [a)scii | i)mage | d)irectory] )
I use file extension *.bin
Yes! All work correct with parameter ;type=i
Thank you!!!