Hsdpa Usb Modem

[Micol Cohn]

Dependingon which USB port I use to connect my HSDPA modem, the network manager will connect to the internet or not. I used to work (i.e. established a internet connection automatically) on all ports, but over time it simply stopped on some ports.

ADDED

One additional information about the modem: if connected via USB it will be available as as harddrive AND as a HSDPA modem (kind of a duality...). In the error case, it will only be shown as a harddrive.

In Windows 7 for my E156G (black "3" Three italy 3G Internet provider) I noted that its works only attachet to an USB HUB, may be a communication issue that the HUB filters. A similar solution happenet for scanner driver over WMWare Windows XP virtualization port.

Two drivers are identifyed with the USB HUB and the original dialer works fine over Windows 7, but only one if I plug it directly on USB notebook port and the device are not fully recognized neither the dialer identify the hardware. The second driver does not appear. So, try to use an USB HUB between the device.

Your modem should work on any usb but hard drives do not on notebooks usually, because not all usb are equal (some do not supply power - or not sufficient for hard disks maybe). On my notebook I have 2 usb and 1 usb+firewire and hard drives that can't be powered on external power source work only on the usb+firewire one. Hard drive that have a PSU work in all usb.

What you need to do is to make sure that when you connect, it is in the right mode. That is to say it should be recognized as the modem and not a compact disk.There are a couple of ways in which you can achieve this,one is to determine the id of the compact disk that it looks like, typically it is sr* where * can be some number.You need to eject it using

Once you have connected your terminal emulator to your modem (typically /dev/ttyUSB0 on Linux), try AT. If you get an OK or ERROR that means you have no problem with serial port configuration because the modem is responding to you. If you get nothing (ei, no reply from the modem), then you probably have a serial connection or modem hardware issue. Personnaly I'm using miniterm.py (on Linux) and the configuration is

Regarding reading the SMSes, at+cmgl=? should reply either ERROR or a list of statuses. If you get ERROR, this means your modem doesn't accept SMS. Otherwise you should get something like +cmgl: ("REC UNREAD","REC READ","STO UNSENT","STO SENT","ALL")

where +XXXXXXXXXXXX is the sender MSISDN and "Test 1" is the message sent in the SMS (its content). Again, if you get ERROR, that means your modem doesn't accept SMSes. If you have sent some SMSes but the list is empty, maybe SMS are blocked on the HLR for this specific SIM.

Hi support,

Is there a way to make the connection block on HSDPA ?

Since the network is working on 3G/UMTS and the ping is very high, when there is downloading data the connection switch over HSDPA and the ping is very low, so I need to have a very low ping.

Exist "HSPA Locker v1.3b by Job 3.14" that makes all this but on PC...

Is there a command on this wonderful firmware on setting in the section of 3G/4G ?

There is no real need to do anything. Once you will create the real load for the mobile network it will allocate you the necessary resources. You should not create the fake load, remember that there are other users nearby.

Hi

You cant force the modem to just use HSDPA. The switch from non-HSDPA, Rel99, to HSDPA is triggered by the 3G network with timers and data buffers.

If you continuously sends ping with certain interval and packet size you, maybe, can keep the modem on HSDPA. The interval and size is dependent on your operators settings. If you know the time it takes today to get low pings, decrease that time a little and start play with the packet size.

But it will "eat" from your data bucket.

I'm using a Huawei E220 USB modem to send and receive SMS messages. I have it plugged into my Ubuntu laptop and am using Gammu to manage it. However this modem I think only works with SMS (text) messages.

The E220 is an ordinary modem that is capable of all the things that modems are capable of. It is a full internet connection, so you can send and receive anything that you can access on the internet with any other connection type. You can access web pages, do downloads, and send both SMS and MMS messages.

Any data enabled modem (GPRS, HSDPA, CDMA) etc is capable of posting MMS messages via HTTP or UDP to the host cellular network. The limitations exist around the carriers implementation of their MMS gateway and understanding what format they require which is dependent on which MMS gateway they are running on their network.

I followed the instructions on the wiki on how to setup this modem (it was recognized as is, I just modified hal and udev rules). I set the wvdial.conf and tried to connect first as a normal, then as superuser. I get the famous:

message. Any ideas? I tried changing permissions on /dev/tts/USB0 (/dev/ttyUSB0 links there), but in vain. I'll put more info if needed (typing this from my Win XP installation, as this is the only way to get the net running ).[SOL

Yeah, I have ttyUSB1 and ttyUSB2 as well. I don't think the problem is within wvdial.conf, because modem won't even initialize, it's more probable it's some kind of permission issue. It's worth to mention, I also tried wvdialconf, and it fails to detect any modems, the same error appears (device or resource busy).

Hey, I just recently went through this and it nearly drove me nuts, had the 'device busy' problem even for root. After many, many days and several aneurysms I finally found my problem, maybe this will help you too.

It turned out that wvdial tries to create a lock file for the usb device in '/var/lock', but for some reason when I looked in '/var' I had no 'lock' directory. I checked my other Arch machine and it has a '/var/lock' directory, so I'm not sure where this one disappeared to.

Cheers to you, mate! It worked like a charm, typing from my Arch box! You've got yourself a free beer (if you ever find yourself in Serbia, that is ). I'd never think of that, you are probably the only one who can understand the amount of work you got me rid of.

- Now wvdial (supplied with correct /etc/wvdial.conf, of course) could estabilish a connection when run as root. I wanted to use wvdial as a regular user, so I googled a bit, and found a better sollution. I could use NetworkManager 0.7 to manage my connection, all I had to do was to ensure NetworkManager detects the modem right (which is where HAL jumps in) and set up a Mobile Broadband connection under System -> Preferences -> Network Connections (GNOME). Modem detection is done via HAL, which scans /usr/share/hal/fdi/information/10freedesktop/10-modem.fdi to identify the vendor and the model. This is the relevant part:

So, HAL fills the key modem.command_sets with appropriate strings once my type of modem has been found. Obviously, my modem was not detected right, because lshal output did not show modem.command_sets key at all.

- After spending some time looking for culprits, I had found out that two files included in the tar archive from the wiki setup guide ( _E220) were to blame, 10-huawei-e220.fdi and 50-huawei-e220.rules specifically. The setup script (also included in the archive) installs the HAL and Udev rules which help identify the modem right, and, in a way, these two prevent HAL from setting the modem.command_sets key. I found out my Huawei E220 is detected with no problems even without these two files, so I simply deleted them, which resulted in correct key, like the lshal output shows:

It's one of those little daemon started by networkmanager-dispatcher that automatically create the lock file and set up modem specific parameters alone. With that i had 100% out-of-the-box compatibility with both huawei and ZTE MF627.

The palm-sized modem uses the USB mini-plug most commonly seen on portable USB hard drives and as the combo charge/data connector on smartphones. A 10cm cable connects the modem to the PC, although the bundle includes a more generous 80cm cable with a second USB plug for instances when a single port can't provide enough power to drive the modem.

Features

The modem itself sports precious little in the way of frills and features. Most of the extra goodness in the Vodafone Mobile Connect package comes through the bundled software and the network's active data compression.

Incoming files are automatically decompressed so there's no need to fiddle with third-party software. Users can also block bandwidth-bloating elements such as video, audio, animation and Web applets.

This enhances speed and makes the most of your monthly download allocation, although it's not ideal for everyone. For example, there's no way to prevent incoming data compression, which some Web developers have reported as an issue when working on the road. (You can, however, disable compression of files sent through your VMC card.)

We were also impressed by the card's software. With SMS and MMS messaging, address book management, connection profiles and a graphical summary of account usage, the console is easily the best client we've seen for any mobile data card.

Performance

As with the latest PC Card, achieving HSDPA speeds with the USB modem relies on the user being within the footprint of what Vodafone calls its "3G broadband" service, which is currently limited to "inner metro" coverage of Sydney and Melbourne.

3a8082e126