Hi T, I have a few of the HUAWEI modems. I can send you the e156 and e160 if you need to test. The e156 seems to make four TTYs . 0/1/2/3 I am not sure why this takes place. I have been asking HUAWEI for the complete specifications on their modems but they are a pain about it. I need the heat and power dissipation as well for what I am using them for.
AT+CLAC gives a lot of commands but as I am sure you know it is not easy to figure out what they all mean. There might be a command that will change this behavior. I will let you know if I get a copy of the specs. -nxn On Aug 19, 3:26 pm, Thanasis <[email protected]> wrote: > Hi, > > Just to close this issue, I would like to confirm your findings. I've > got my hands on a E220 and seems to work like what you've said (dual > ports etc). > > Can you please copy your initial post to the tracker (http:// > code.google.com/p/smslib/issues/list) in order to serve as a reminder > (and have your name as well)? > > Thanks. > > On Jul 14, 11:57 pm, bitsmith <[email protected]> wrote: > > > When I plug in the Huawei USB stick, two tty devices get generated, > > usually > > /dev/ttyUSB0 and /dev/ttyUSB1. > > > smslib can be used on either of them - however, it seems that CMTI > > will > > only be indicated on the second one (usually /dev/ttyUSB1). > > > Apparently, umtsmon (umtsmon.sourceforge.net) knows about this > > behaviour > > and I remember to have seen in it's debug log something of using > > /dev/ttyUSB0 for connection and /dev/ttyUSB1 for control. > > > For my test with smslib I have created a small program, that > > 1) discovers all active ports using > > CommPortIdentifier.getPortIdentifiers() > > 2) creates a gateway on each of these ports > > 3) tries to activate each gateway by adding it to a temporary Service > > and > > starting the service > > 4) if this is successful, basic parameters like manufacturer, model > > and serial number are read from the gateway. This is used to > > decide > > if the port is a port that is currently occupied by my target > > device > > 5) the temporary Service is then stopped and if the port qualified, > > the > > Gateway is added to another (common) Service object. > > > After all ports are through, I end up with the common Service object > > with > > two Gateways attached. This is the Service, I use for further SMS > > processing. > > It will accept the CMTI from whichever port the UMTS stick decides to > > send it to. > > > Even though this type of discovery works for me, I would appreciate to > > have > > a function within smslib to do it. Such a function could also be used > > to select > > the correct ATHandler based on information read from the device. > > > ... but that's only a proposal for enhancement - not strictly > > necessary. > > > On 13 Jul., 18:15, Thanasis <[email protected]> wrote: > > > > Hi, > > > > Thanks for this - This device is much discussed here. > > > > However, I am a bit confused... What do you mean by two ttys??? Do you > > > mean that smslib is required to manage to ttys for one modem? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "SMSLib for Java User Group" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/smslib?hl=en -~----------~----~----~----~------~----~------~--~---
