# HL8548-G modem freezes after KTCPSND

**URL:** <https://forum.sierrawireless.com/t/hl8548-g-modem-freezes-after-ktcpsnd/8490>\
**Category:** Legacy HL Series\
**Created:** [March 30, 2016, 3:08am UTC](https://forum.sierrawireless.com/t/hl8548-g-modem-freezes-after-ktcpsnd/8490 "2016-03-30T03:08:18Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![bezakb](https://avatars.discourse-cdn.com/v4/letter/b/a88e57/32.png) [@bezakb](https://forum.sierrawireless.com/u/bezakb)\
**Post date:** [March 30, 2016, 3:08am UTC](https://forum.sierrawireless.com/t/hl8548-g-modem-freezes-after-ktcpsnd/8490/1 "2016-03-30T03:08:18Z")

</div>

Hi,

I’m trying to follow client mode example of TCPIP exchange from AT document. I get OK response for all commands until KTCPSND command, once I send this one I never get CONNECT from modem and after that modem does not respond to anything (data terminated with KPATTERN, +++, other commands) until I reset it.

Any ideas what is going ion here ?

thanks  
Branislav

my modem is HL8548-G, KGSN returns SV:04

here is my log

AT+CSQ  
AT+CSQ  
+CSQ: 16,99

OK  
AT+KCNXCFG=1,“GPRS”,“mnet.bell.ca.ioe”,“login”,“password”,“IPV4”,“0.0.0.0”,“0.0.0.0”,“0.0.0.0”  
AT+KCNXCFG=1,“GPRS”,“mnet.bell.ca.ioe”,“login”,“password”,“IPV4”,“0.0.0.0”,“0.0.0.0”,“0.0.0.0”  
OK  
AT+KTCPCFG=1,0,“[www.google.com](http://www.google.com)”,80  
AT+KTCPCFG=1,0,“[www.google.com](http://www.google.com)”,80  
+KTCPCFG: 1  
OK  
AT+KTCPCNX=1  
AT+KTCPCNX=1  
OK

+KCNX\_IND: 1,4,1

+KCNX\_IND: 1,1,0

+KTCP\_IND: 1,1  
AT+KTCPSND=1,18  
AT+KTCPSND=1,18 - this is last response from modem, terminated with single ‘\r’. no other response after this until hardware reset

---

<div class="post-metadata">

**Author:** ![bezakb](https://avatars.discourse-cdn.com/v4/letter/b/a88e57/32.png) [@bezakb](https://forum.sierrawireless.com/u/bezakb)\
**Post date:** [March 31, 2016, 5:19am UTC](https://forum.sierrawireless.com/t/hl8548-g-modem-freezes-after-ktcpsnd/8490/2 "2016-03-31T05:19:27Z")

</div>

Seems that the problem was due to very old version of firmware. Once I upgraded to 5.5.14 it started to work.
