awneil
August 11, 2011, 11:58am
1
The TMConsole doesn’t work at 921600 baud.
It’s fine at 115200, 230400, 460800. etc - but not at 921600.
Traces appear to work, but not AT commands in the TMConsole.
When the port is openened, I usually (at 460800 or less) see:
----------------- Port opened -----------------
ERROR
Serial Number AQ0060007208100
OK
+WIMEI: 354662030003544
OK
+WDM: 1
OK
+WOPEN: 6,1024,4096
OK
+WOPEN: 1
OK
“DWL”,“V08b0g”,“”,“Sierra Wireless”,54680,“071609 15:36”,“16bb6f5c”,“00010000”
“FW”,“FW_SRC_744_12.Q2686G”,“R7.44.0.201008311212.FXT001”,“Sierra Wireless”,2146096,“083110 12:12”,“456cf17c”,“00020000”
“OAT”,“0.0.0”,“”,“Antronics Ltd”,1227352,“081011 00:19”,“7085d571”,“00260000”
-“Developer Studio”,“1.2.0.201012171243-R6026”
-“Open AT Embedded Software Suite package”,“2.33.0.201009161739”
-“Open AT OS Package”,“6.32.0.03”
-“Firmware Package”,“7.43.0.201009151513”
-“C-GPS-OPUS-I Open AT Plug-in Package”,“1.7.0.2010”
OK
OK
ie, the responses to all the commands that DS sends after opening the port.
When I open the port at 921600, all I see is:
and commands typed in the command box have no effect - the command appears in the TMConsole window, but there is no response; eg,
Sometimes, after a long delay, (some of) the responses to the initial DS command might appear…
The modems communicate fine with a terminal at 921600.
I’m using one of these FTDI dual USB-to-RS232 converters:
apple.clickandbuild.com/cnb/shop … egoryID=89
I get the same behaviour on both a Fastrack Supreme and a Fastrack Xtend:
“DWL”,“V08b0g”,“”,“Sierra Wireless”,54680,“071609 15:36”,“16bb6f5c”,“00010000”
“FW”,“FW_SRC_744_12.Q2686G”,“R7.44.0.201008311212.FXT001 ”,“Sierra Wireless”,2146
096,“083110 12:12”,“456cf17c”,“00020000”
“OAT”,“0.0.0”,“”,“Antronics Ltd”,1227352,“081011 00:19”,"7085d571
",“00260000”
-“Developer Studio”,“1.2.0.201012171243-R6026”
-“Open AT Embedded Software Suite package”,“2.33.0.201009161739”
-“Open AT OS Package”,“6.32.0.03”
-“Firmware Package”,“7.43.0.201009151513”
-“C-GPS-OPUS-I Open AT Plug-in Package”,“1.7.0.2010”
“DWL”,“V08b0g”,“”,“Sierra Wireless”,54680,“071609 15:36”,“16bb6f5c”,“00010000”
“FW”,“FW_SRC_744_12.Q2687G”,“R7.44.0.201008311212.FSU004 ”,“Sierra Wireless”,2146
096,“083110 12:12”,“456cf17c”,“00020000”
“OAT”,“0.0.0”,“”,“Antronics Ltd”,1226280,“070911 14:56”,"ad9b5f73
",“00260000”
-“Developer Studio”,“1.2.0.201012171243-R6026”
-“Open AT Embedded Software Suite package”,“2.33.0.201009161739”
-“Open AT OS Package”,“6.32.0.03”
-“Firmware Package”,“7.43.0.201009151513”
-“C-GPS-OPUS-I Open AT Plug-in Package”,“1.7.0.2010”
daav
August 22, 2011, 12:09pm
2
Thanks for all the details.
We have indeed noticed such an issue with “recent” firmwares versions; it seems to be an embedded firmware issue. I get in touch with the concerned people to have progress updates on the topic.