Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

USB GSM Huawei E173 does not reconnect to network after disconnect #7

Open
aeratek opened this issue Jul 20, 2014 · 4 comments
Open
Labels

Comments

@aeratek
Copy link
Contributor

aeratek commented Jul 20, 2014

Huawei E173 dongle is able to successfully connect to T-Mobile network using current configuration/code. When in a low-coverage area and it disconnects, it does not reconnect to the T-Mobile network, until the device is restarted.

@aeratek aeratek added the bug label Jul 20, 2014
@transistorize
Copy link
Member

I was reading this FAQ in the GPSD documentation, and it might explain why this Huawei dongle behaves this way, for the same reasons: http://www.catb.org/gpsd/faq.html#sleep

@aeratek
Copy link
Contributor Author

aeratek commented Jul 26, 2014

Ok. I think you're saying that this paragraph is the relevant one that
gives us next actions in trying to resolve both the GPS and GSM dongle
reconnection issues:

There is a solution to this problem: create a stable gps-usb device that is
actually a symlink which gets modified by hotplug events, and give gpsd that
device when you invoke it. You'll need these replacement udev rules
http://www.catb.org/gpsd/70-persistent-usb-gps.rules [1], and the
experience required to patch them so the vendor ID in the last one matches
your GPS hardware (look in your lsusb output).

[1] http://www.catb.org/gpsd/70-persistent-usb-gps.rules

On Mon, Jul 21, 2014 at 2:14 PM, Bryan Valentini notifications@github.com
wrote:

I was reading this FAQ in the GPSD documentation, and it might explain why
this Huawei dongle behaves this way, for the same reasons:
http://www.catb.org/gpsd/faq.html#sleep


Reply to this email directly or view it on GitHub
#7 (comment)
.

@trevorcarlson
Copy link
Contributor

Guys,

From my experiments, the modem automatically gets assigned to the /dev/gsmmodem device when it is configured properly. Can you double-check that that link is being set up? We then just have to update the scripts to point to there (See the kinisiinternet script that I recently updated [1]) and we'll be set to go (with an auto restart function added as well).

[1] https://github.com/kinisi/kinisi-agent-nodejs/blob/master/scripts/kinisiinternet

@aeratek
Copy link
Contributor Author

aeratek commented Aug 12, 2014

I started up a Raspberry Pi B+ with the USB dongle in the top-most USB port (same physical location as the Raspberry Pi model B, but the B+ has two additional USB ports next to it in the corner now). I went to /dev/ and didn't see a /gsmmodem link set up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants