CINTERION PCS3 -> Downloading problem in TCP transparent mode | Telit Cinterion IoT Developer Community
October 5, 2016 - 3:17pm, 6113 views
Hallo all,
I have one interesting problem with which I need help.
One year ago I ended development work on our project in USA. Station which contain ****m CINTERION PCS3 have availability for upgrade of FW of our station, but we can speak about this problem as generall problem.
Around one year everithing worked fine, without problems, and few month ago began coming claiming that stations are not able upgrde their self.
I found out that problem is in additonal data which coming as redundant data somewhere inside of our FW (see picture - yellow part)
Fact about this problem:
- blocks of 12 ***** 0x20 (ASCII space character) are added inside our FW
- it is repaeting pseudo-periodicaly, that mean in most case after 671 Bytes +/- few Bytes, or mutiplied of that number like after 1340 or after 2016 Bytes!
I check in documentation if I will find anything, I found something related with unsolicited messages, that this messages are additional signaling on RING0 pin, but also there was short information that if this is not possible you can setup also BREAK transition, but nowhere was descripted what or which shape is BREAK.
In documenation is write that not solved unsolicited answers can disturb activ transmition in any case, so in that case I should stop data flow on mdm (****m) port and switch to command **** via "+++" and I would be able to read "problem"....I did this but no problem was there!
Do somebody help me with this, what can mean this sequence of 12 ***** 0x20, from where it could come, or what can be 671 Bytes ( if any size of something or treshold or whatever )
Thanx a lot!
Matus
Hello,
Please write more details about the solution. The "Station" device uses the PCS3 as a modem? Is CDC-ACM interface used or AT commands? It downloads the firmware from some web server? Where have you traced the data? Why do you assume that the problem is inside the PCS3? Has anything been changed like PCS3 or Station firmware, network operator, firmware server, etc.? Is is possible that the file is corrupted or there is some bug in the "Station" software? It could look like some buffering problem.
Best regards,
Bartłomiej
Hi Bartlomiej!
We was already solving any problem together, but it was about other typ of modem...
Brifly, we are developing weather stations, which gathering data on field and then sending they on our server.
This stations with problems, are working in USA and are using CDMA carrier, they are using PCS3.
I am using UART for comunication MCU <-> PCS3, not USB.
I didn't sey yet that problem is in PCS3, not as conclusion of this problem.
But fackt is that everithing worked fine one year without problem, I didn't change nothing in our fw regarding communication via this modem, and suddenly I am getting more and more claiming about stop upgrading of our fw of stations.
It looks like came any changes in CDMA network, with which modem have maybe problems, because that upgrade was tested by me in past and I would not release something which is not working!!!
I have report from that time where is possible to see that uprgarde of stations's FW working well, and also I repeated test now exactely with that old FW ( I made something like restore point in test ) and this attempt also fault!
So what can I think, when something which worked in past, I didn't make any changes in code, and suddenly it is not working nowadays?! Only that can came changes in carrier network.
According test in USA:
We are using there stations, which are using for communication one typ of station UMTS and second typ CDMA. I am loaded to both station the same FW and set conditions on our server ( located in Austria - EU ) for upgrade new FW ( again the same FW for both stations used UMTS and CDMA too ). Via UMTS everithing is working nicely, upgraded successfully, in CDMA case it fault...both stations was *** 10cm each other on the table in California! This is answer on rest your questions, if we have no problem in our FW and so on, simply on our server and in our FW is no problem, because we are using exactly the same settings for communication for all stations...but data which come to station over CDMA contain that starnge redundant data ( in past it worked without redundant data for CDMA case too ).
What you can see on picture is result from descripted test ( CDMA on left side vs. UMTS on right side )!
I really need help with this!
If you have additional questions, or hints, feel free to ask :)
Thank you!
Matus
Hallo Bartłomiej!
Do you think than any upgrade of modem could help me?
In example new FW of modem if is existing now is there version v2.1...
or we are using in USA Verizon, is there any possibility use any OTA via casll, except *22899?
Hello,
This is very strange. From what you have described it really looks like the type of network is a key.
Please check the firmware version with ATI. It would be the best to start with the latest firmware. And please also paste the AT^SCFG? output. I assume that the PCS3 firmware was not changed.
Could you also write more about how you are using the module for data transfer - are you using internet services over AT commands, dialup connection etc.
Is there any other scenario when the station receives data, is it working without problems? Were you able to test downloading of the same file that you have been using before? Is there a possibility to test with some other CDMA network provider?
Regards,
Bartłomiej
Hi Bartłomiej!
Version of FW for ****m is 2.100, and you right this version was not changed since time when I bagan work with it ( or I didn't find newer version of FW too )
I am using more or less default settings for that ****m:
AT^SCFG?
^SCFG: "Call/Speech/Codec","0"
^SCFG: "CDMA/PrivMode","0"
^SCFG: "CDMA/AutoAB","autoa"
^SCFG: "CDMA/Operator/Store","Verizon"
^SCFG: "CDMA/System/CaiRev",6
^SCFG: "CDMA/TetheredNai","enabled"
^SCFG: "Ident/Manufacturer","Cinterion"
^SCFG: "Ident/Product","PCS3"
^SCFG: "MEopMode/Airplane","off"
^SCFG: "MEopMode/CFUN","0","1"
^SCFG: "MEopMode/PowerMgmt/LCI","disabled"
^SCFG: "MEopMode/PowerMgmt/VExt","high"
^SCFG: "MEopMode/PwrSave","disabled","0","50"
^SCFG: "MEopMode/RingOnData","off"
^SCFG: "MEopMode/RingUrcOnCall","on"
^SCFG: "MEShutdown/OnIgnition","off"
^SCFG: "Radio/Band","3072"
^SCFG: "Serial/USB/DDD","0","0","0409","1E2D","0070","Cinterion","PCS3",""
^SCFG: "URC/DstIfc","mdm"
^SCFG: "URC/Data****/Ringline","on"
^SCFG: "URC/Ringline","local"
^SCFG: "URC/Ringline/ActiveTime","1"
^SCFG: "cdma/sip/ppp","**********@vzw3g.com"
- bolded lines means what I changed for our work but this have no influence for this issue.
There are no possibility to use other operator, we have contract with Verizon but not directly but via Kore, which is company which are providing contreacts with ie Verizon for nonresidents of USA. I dont know exactely details about their backgroud but we are using Verizon profile for ****m as you can see in log (^SCFG: "CDMA/Operator/Store","Verizon")
In that time when it worked it was tested in Utah in USA, but then after year I repeated test in that area on the same station, and didn't work any more, now test station are moved to California...the same results.
I can send you log how I am establishing connection wit our server if you will see something suspect :):
AT^SCFG="MEopMode/PwrSave","disabled"
^SCFG: "MEopMode/PwrSave","disabled","0","50"
OK
AT^SDPORT=6
OK
AT\Q3
OK
AT+CTZU=0
OK
AT+CMEE=1
OK
AT^SLED=2
OK
AT+CMGF=1
OK
AT&W
OK
AT+CFUN?
+CFUN: 1
OK
AT+CFUN=4
OK
^SYSSTART AIRPLANE MODE
AT^SCFG="Radio/Band","3072","0"
^SCFG: "Radio/Band","3072"
OK
AT^SCFG="CDMA/Operator/Store",0,"Verizon"
^SCFG: "CDMA/Operator/Store","Verizon"
OK
AT+CFUN=1,1
OK
^SYSSTART
AT$MDN?
$MDN: **********
OK
AT+CIMI
310006144722842
OK
AT^SREG?
^SREG: 0,1
OK
###### REGISTRED TO HOME NETWORK #####
AT^SDPORT=2
OK
AT^SCFG="MEopMode/RingOnData","on"
^SCFG: "MEopMode/RingOnData","on"
OK
AT^SCFG="MEopMode/RingUrcOnCall","on"
^SCFG: "MEopMode/RingUrcOnCall","on"
OK
AT^SCFG="URC/Data****/Ringline","on"
^SCFG: "URC/Data****/Ringline","on"
OK
AT^SCFG="URC/Ringline","asc0"
^SCFG: "URC/Ringline","asc0"
OK
AT$MDN?
$MDN: **********
OK
AT^SCFG="cdma/sip/ppp","**********@vzw3g.com","vzw"
^SCFG: "cdma/sip/ppp","*********@vzw3g.com"
OK
######### CDMA PPP SET CORRECTLY - GENERATED BY SYSTEM #########
AT^SICO=201
OK
AT^SISX="HostByName",201,"AnyURL.something"
^SISX: "HostByName","***.***.***.***"
OK
AT^SISS=0,"srvType","TCPclient"
OK
AT^SISS=0,"conId","201"
OK
AT^SISS=0,"address","***.***.***.***:80"
OK
AT^SISO=0
OK
^SISW: 0,1
AT^SIST=0
CONNECT
:
:
{ DATA FLOW }
:
V
As you can see in this log I tried RING signalizing, bud without success ( I thought about that if that 12 x 0x20 was not BREAK sequence or something )
Next test what I did (without success):
- upgrade of PRL via *22891
- Preferred roaming **** ( AT^SCFG="CDMA/AutoAB","..." ) <- tested all posibility
- filtering of Bands ( AT^SCFG="Radio/Band","..." ) <- tested all posibility
- Disable Neagle algorithm in service profile ( AT^SISS=0,"address","***.***.***.***:80;timer=0"
- lengthen Timer to *** for Neagle algorithm
Hello,
Thank you for the detailed information. I can't see anything bad there. We would like to try to reproduce this. Have you tried to do this without your device using just a PC? Could you prepare such a scenario?
Regards,
Bartłomiej
Sure that I tried it via PC too, all the same ;)
Hi Bartłomiej,
do you know find out, or tell me what is different between Transparent **** acitavated via ^SIST
and no-transparent which I have to control via ^SISR for reading and ^SISW for write?
I made one test and preliminary it looks like transparent **** stop working...I need more test for this but till now it looks like that....
In the transparent **** you open the transparent channel to your application which can then exchange the data with the remote host. With SISW and SISR you need to use AT commands for each write and read operation. Transparent **** should be much faster.
Could you also check if ATI1 command returns some more precise information about the firmware version?
Regards,
Bartłomiej
I know what is different btw ^SIST, ^SISR and ^SISW from "user" view...
I would like to know if you don't know about background of those processes, because in transparent **** is suddenly any problem...it looks like, and by ^SISR / ^SISW it working....
Regarding ATI1:
Cinterion
PCS3
REVISION 02.100
A-REVISION 01.000.07
Pages