RE: GlobeTrotter HSDPA Modem -> Failed to find a usable modem character set

[Dan Williams <dcbw redhat com>]

On Thu, 2011-09-15 at 17:15 +0200, richter ecos de wrote:
> Here are the modem type:

It looks like you've got an iCON 225, right?  I've got one too that
works pretty well, but I've got updated firmware that fixed issues like
this.  I'm pretty sure it shipped with a 2007-era firmware originally
and it was somewhat buggy.

Manufacturer: Option N.V.
Model: GlobeTrotter HSDPA Modem
Revision: 2.5.24Hd (Date: Apr 17 2009, Time: 08:59:36)

Unfortunately a firmware upgrade requires Windows.

http://www.option.com/en/support/software-download/mobile-devices-solutions/icon225/

You're looking for the "iCON® 225: SuperFire FW only" update link there.
If you have a locked or branded 225 though, you might not be able to use
this specific update, and you might need to find an updater from the
operator you purchased the device from.

Dan

> : (ttyHS0): --> 'AT+GMI<CR>'
> : (ttyHS0): <-- '<CR><LF>Option N.V.<CR><LF><CR><LF>OK<CR><LF>'
> : (ttyHS0): --> 'AT+GMM<CR>'
> : (ttyHS0): <-- '<CR><LF>GlobeTrotter HSDPA Modem<CR><LF><CR><LF>OK<CR><LF>'
> : (ttyHS0): --> 'AT+GMR<CR>'
> : (ttyHS0): <-- '<CR><LF>2.4.6Hd (Date: Oct 04 2007, Time: 14:11:38)<CR><LF><CR><LF>OK<CR><LF>'
> : (ttyHS0): --> 'AT+CGMI<CR>'
> : (ttyHS0): <-- '<CR><LF>Option N.V.<CR><LF><CR><LF>OK<CR><LF>'
> : (ttyHS0): --> 'AT+CGMM<CR>'
> : (ttyHS0): <-- '<CR><LF>GlobeTrotter HSDPA Modem<CR><LF><CR><LF>OK<CR><LF>'
> : (ttyHS0): --> 'AT+CGMR<CR>'
> : (ttyHS0): <-- '<CR><LF>2.4.6Hd (Date: Oct 04 2007, Time: 14:11:38)<CR><LF><CR><LF>OK<CR><LF>'
> : (ttyHS0): --> 'ATI<CR>'
> : (ttyHS0): <-- '<CR><LF>Manufacturer: Option N.V.<CR><LF>Model: GlobeTrotter HSDPA Modem<CR><LF>Revision: 2.4.6Hd (Date: Oct 04 2007, Time: 14:11:38)<CR><LF><CR><LF>OK<CR><LF>'
> : (ttyHS0): --> 'ATI1<CR>'
> : (ttyHS0): <-- '<CR><LF>Manufacturer: Option N.V.<CR><LF>Model: GlobeTrotter HSDPA Modem<CR><LF>Revision: 2.4.6Hd (Date: Oct 04 2007, Time: 14:11:38)<CR><LF><CR><LF>OK<CR><LF>'
> 
> 
> Bus 002 Device 013: ID 0af0:6971 Option Globetrotter HSDPA Modem
> Device Descriptor:
>   bLength                18
>   bDescriptorType         1
>   bcdUSB               1.10
>   bDeviceClass          255 Vendor Specific Class
>   bDeviceSubClass       255 Vendor Specific Subclass
>   bDeviceProtocol       255 Vendor Specific Protocol
>   bMaxPacketSize0        64
>   idVendor           0x0af0 Option
>   idProduct          0x6971 Globetrotter HSDPA Modem
>   bcdDevice            0.00
>   iManufacturer           1 Option N.V.
>   iProduct                2 Globetrotter HSDPA Modem
>   iSerial                 4 Serial Number
>   bNumConfigurations      1
> 
> 
> Gerald
> 
> 
> > -----Original Message-----
> > From: Dan Williams [mailto:dcbw redhat com]
> > Sent: Thursday, September 15, 2011 5:06 PM
> > To: Aleksander Morgado
> > Cc: Gerald Richter - ECOS; networkmanager-list gnome org
> > Subject: Re: GlobeTrotter HSDPA Modem -> Failed to find a usable modem
> > character set
> > 
> > On Thu, 2011-09-15 at 13:22 +0200, Aleksander Morgado wrote:
> > > > (ttyHS0): --> 'AT_OPSYS?<CR>'
> > > > Sep 15 10:43:34 ThinClient modem-manager[2081]: <debug>
> > > > [mm-at-serial-port.c:298] debug_log(): (ttyHS0): <--
> > > > '<CR><LF>ERROR<CR><LF>'
> > > > Sep 15 10:43:34 ThinClient modem-manager[2081]: <debug>
> > > > [mm-serial-parsers.c:412] mm_serial_parser_v1_parse(): Got failure
> > > > code 100: Unknown error Sep 15 10:43:34 ThinClient
> > > > modem-manager[2081]: <debug> [mm-at-serial-port.c:298] debug_log():
> > > > (ttyHS0): --> 'AT+CSCS=?<CR>'
> > > > Sep 15 10:43:34 ThinClient modem-manager[2081]: <debug>
> > > > [mm-at-serial-port.c:298] debug_log(): (ttyHS0): <-- '<CR><LF>_OPSYS:
> > > > 3,2<CR><LF><CR><LF>OK<CR><LF>'
> > > > Sep 15 10:43:34 ThinClient modem-manager[2081]: <debug>
> > > > [mm-at-serial-port.c:298] debug_log(): (ttyHS0): --> 'AT
> > > > +CMER=3,0,0,1<CR>'
> > >
> > > To me the real issue here seems to be that the reply to "AT_OPSYS?" is
> > > split in a first "ERROR" string and then "_OPSYS: 3,2 OK". The serial
> > > parsers will consider the ERROR part as being a full response, and
> > > therefore ModemManager issues the "AT+CSCS?" command next, and
> > then we
> > > get the second chunk of the OPSYS reply as if it were the reply to the
> > > AT+CSCS... The fix could be to let "ERROR" be considered as a partial
> > > reply by providing a custom regex in the response parsers, similar to
> > > what it was done here:
> > >
> > >
> > http://cgit.freedesktop.org/ModemManager/ModemManager/commit/?id
> > =262ed
> > > b96d50138a724173840fc63ca93ede322c2
> > 
> > That's a really weird response though.  I can't recall having seen a modem
> > return ERROR *and* a valid response.  Perhaps the response there is actually
> > an unsolicited response that's been enabled by the AT_OSSYS=1.  It may be
> > that the modem simply isn't quite ready yet when we start poking it?  That
> > could also be the reason why AT_OSQI=1 is failing.
> > 
> > What Option modem is this again?
> > 
> > Dan
> > 
> 
>