Difference between revisions of "Ericsson F3507g Mobile Broadband Module"
SteveClement (Talk | contribs) (→Other thoughts) |
(added category) |
||
(17 intermediate revisions by 5 users not shown) | |||
Line 20: | Line 20: | ||
[[image:EriccsonWWAN.gif|thumb|Ericsson F3507g WWAN Adapter]] | [[image:EriccsonWWAN.gif|thumb|Ericsson F3507g WWAN Adapter]] | ||
|} | |} | ||
− | |||
== Lenovo Partnumbers == | == Lenovo Partnumbers == | ||
Line 27: | Line 26: | ||
* FRU 43Y6513 (Other) | * FRU 43Y6513 (Other) | ||
− | == | + | Forumthread with [http://www.netbooks.ph/forums/viewtopic.php?f=56&t=1756#p18011 list of FRUs and corresponding firmwares] (scroll down): |
− | + | {| {{prettytable}} | |
+ | ! Firmware !! Date !! FRU !! Remarks | ||
+ | |- | ||
+ | | R1A034 || 2008-05-17 || 43Y6477 | ||
+ | |- | ||
+ | | R1B003 || 2008-07-08 || 43Y6479 | ||
+ | |- | ||
+ | | R1B/1 || 2008-07-30 || 43Y6513 | ||
+ | |- | ||
+ | | R1D06 || 2008-11-07 || 43Y6537 || better performance and stability, fixed many bugs from the previous version | ||
+ | |} | ||
− | + | Unlike other manufactures (Dell, Toshiba etc.) Lenovo does not release the firmware update utility public, so the only way to get a newer version F3507g is by replacing the existing one. | |
− | + | __TOC__ | |
+ | == Overview == | ||
Here are some basics about Ericsson F3507g MiniPCIe WWAN/GPS card (USB ID <tt>0bdb:1900</tt> and <tt>0bdb:1902</tt>): | Here are some basics about Ericsson F3507g MiniPCIe WWAN/GPS card (USB ID <tt>0bdb:1900</tt> and <tt>0bdb:1902</tt>): | ||
Line 48: | Line 58: | ||
'''Note''': | '''Note''': | ||
*apparently, for a while <tt>option</tt> USB-serial driver had claimed USB ID <tt>0bdb:1900</tt>, but this was wrong, and as of kernel 2.6.28.9 that commit was reversed. If instead of <tt>/dev/ttyACM*</tt> you see <tt>/dev/ttyUSB*</tt>, it means that <tt>option</tt> module is loaded. You may need to blacklist it to make sure it doesn't happen. | *apparently, for a while <tt>option</tt> USB-serial driver had claimed USB ID <tt>0bdb:1900</tt>, but this was wrong, and as of kernel 2.6.28.9 that commit was reversed. If instead of <tt>/dev/ttyACM*</tt> you see <tt>/dev/ttyUSB*</tt>, it means that <tt>option</tt> module is loaded. You may need to blacklist it to make sure it doesn't happen. | ||
− | *Support for the CDC Ethernet interface appears only in kernel 2.6.28.8. But if your kernel is older, you can still connect to the net using one of the "Modem" interfaces. | + | *Support for the CDC Ethernet interface appears only in kernel 2.6.28.8. But if your kernel is older, you can still connect to the net using one of the "Modem" interfaces. As of kernel 2.6.33 it is named <tt>wwan0</tt> rather than <tt>usb0</tt>. |
− | As Ericsson's naming scheme suggests, idealy we would use <tt>/dev/cdc-wdm0</tt> for controlling the card, <tt>usb0</tt> as a network device, <tt>/dev/ttyACM0</tt> or <tt>/dev/ttyACM1</tt> as a modem, and <tt>/dev/ttyACM2</tt> for GPS. This works for manual testing, but unfortunately, due to [http://markmail.org/message/2sd7culbgekugow2 limitations] of <tt>chat</tt>, does not play very well in scripts. So, instead of <tt>/dev/cdc-wdm0</tt>, for controlling the card we will use <tt>/dev/ttyACM1</tt>. | + | As Ericsson's naming scheme suggests, idealy we would use <tt>/dev/cdc-wdm0</tt> for controlling the card, <tt>usb0</tt> (or <tt>wwan0</tt>) as a network device, <tt>/dev/ttyACM0</tt> or <tt>/dev/ttyACM1</tt> as a modem, and <tt>/dev/ttyACM2</tt> for GPS. This works for manual testing, but unfortunately, due to [http://markmail.org/message/2sd7culbgekugow2 limitations] of <tt>chat</tt>, does not play very well in scripts. So, instead of <tt>/dev/cdc-wdm0</tt>, for controlling the card we will use <tt>/dev/ttyACM1</tt>. |
==Turning the card on== | ==Turning the card on== | ||
Line 125: | Line 135: | ||
dhclient usb0 | dhclient usb0 | ||
− | and start surfing the net. To disconnect, send | + | and start surfing the net (or use <tt>wwan0</tt> for kernels >= 2.6.33). To disconnect, send |
AT*ENAP=0 | AT*ENAP=0 | ||
Line 186: | Line 196: | ||
Don't forget to <tt>chmod a+x /etc/pm/sleep.d/10sysfsutils</tt>. Create a file called <tt>/usr/local/etc/F3507g</tt> containing the following: | Don't forget to <tt>chmod a+x /etc/pm/sleep.d/10sysfsutils</tt>. Create a file called <tt>/usr/local/etc/F3507g</tt> containing the following: | ||
− | + | '''USB_ID="0bdb:1900"''' | |
− | |||
− | |||
− | |||
'''PIN=""''' | '''PIN=""''' | ||
'''APN="proxy"''' | '''APN="proxy"''' | ||
+ | |||
+ | GPSDPID="/var/run/gpsd.pid" | ||
+ | |||
+ | RFKILL_DEVICE=$(for n in /sys/devices/platform/thinkpad_acpi/rfkill/rfkill*; do if [ "$(cat $n/name)" = "tpacpi_wwan_sw" ]; then echo $n/state; fi; done) | ||
+ | |||
+ | CONTROL_DEVICE () { | ||
+ | echo /dev/$(for n in /sys/class/tty/ttyACM*/device/interface;do if [ "$(cat $n)" = "Ericsson F3507g Mobile Broadband Minicard Data Modem" ]; then echo $n|awk -F '/' '{print $5}'; fi; done) | ||
+ | } | ||
+ | |||
+ | GPS_DEVICE () { | ||
+ | echo /dev/$(for n in /sys/class/tty/ttyACM*/device/interface;do if [ "$(cat $n)" = "Ericsson F3507g Mobile Broadband Minicard GPS Port" ]; then echo $n|awk -F '/' '{print $5}'; fi; done) | ||
+ | } | ||
powerup_F3507g () { | powerup_F3507g () { | ||
echo -n "Powering up F3507g card.." | echo -n "Powering up F3507g card.." | ||
echo 1 > $RFKILL_DEVICE | echo 1 > $RFKILL_DEVICE | ||
− | while [ | + | while [ -z "$(lsusb -d $USB_ID)" ]; do sleep 0.5; echo -n "."; done |
echo "done" | echo "done" | ||
echo -n "Turning on F3507g card..." | echo -n "Turning on F3507g card..." | ||
sleep 3 | sleep 3 | ||
if [ -n "$PIN" ]; then | if [ -n "$PIN" ]; then | ||
− | /usr/sbin/chat -v "" "AT+CPIN?" "SIM PIN" "AT" "OK" "AT+CPIN=\"$PIN\"" "OK" > $CONTROL_DEVICE < $CONTROL_DEVICE | + | /usr/sbin/chat -v "" "AT+CPIN?" "SIM PIN" "AT" "OK" "AT+CPIN=\"$PIN\"" "OK" > $(CONTROL_DEVICE) < $(CONTROL_DEVICE) |
fi | fi | ||
− | /usr/sbin/chat -v "" "AT+CPIN?" "READY" "AT+CFUN=1" "+ | + | /usr/sbin/chat -v "" "AT+CPIN?" "READY" "AT+CFUN=1" "+PACSP" "AT" "OK" > $(CONTROL_DEVICE) < $(CONTROL_DEVICE) |
echo "done" | echo "done" | ||
} | } | ||
Line 209: | Line 228: | ||
powerdown_F3507g () { | powerdown_F3507g () { | ||
echo -n "Turning off F3507g card..." | echo -n "Turning off F3507g card..." | ||
− | /usr/sbin/chat -v "" "AT+CFUN=4" "OK" > $CONTROL_DEVICE < $CONTROL_DEVICE | + | /usr/sbin/chat -v "" "AT+CFUN=4" "OK" > $(CONTROL_DEVICE) < $(CONTROL_DEVICE) |
echo "done" | echo "done" | ||
echo -n "Powering down F3507g card.." | echo -n "Powering down F3507g card.." | ||
echo 0 > $RFKILL_DEVICE | echo 0 > $RFKILL_DEVICE | ||
− | while [ - | + | while [ -n "$(lsusb -d $USB_ID)" ]; do sleep 0.5; echo -n "."; done |
echo "done" | echo "done" | ||
} | } | ||
configure_GPS () { | configure_GPS () { | ||
− | /usr/sbin/chat -v "" "AT*E2GPSCTL=$1,$2,$3" "OK" > $CONTROL_DEVICE < $CONTROL_DEVICE | + | /usr/sbin/chat -v "" "AT*E2GPSCTL=$1,$2,$3" "OK" > $(CONTROL_DEVICE) < $(CONTROL_DEVICE) |
} | } | ||
turnon_GPS () { | turnon_GPS () { | ||
− | echo -n "Starting NMEA stream on $GPS_DEVICE..." | + | echo -n "Starting NMEA stream on $(GPS_DEVICE)..." |
configure_GPS 1 1 1 | configure_GPS 1 1 1 | ||
sleep 1 | sleep 1 | ||
− | /usr/sbin/chat -v "" "AT*E2GPSNPD" "GPGGA" > $GPS_DEVICE < $GPS_DEVICE | + | /usr/sbin/chat -v "" "AT*E2GPSNPD" "GPGGA" > $(GPS_DEVICE) < $(GPS_DEVICE) |
− | start-stop-daemon --start --exec /usr/sbin/gpsd -- -P $GPSDPID $GPS_DEVICE | + | start-stop-daemon --start --exec /usr/sbin/gpsd -- -P $GPSDPID $(GPS_DEVICE) |
echo "done" | echo "done" | ||
} | } | ||
turnoff_GPS () { | turnoff_GPS () { | ||
− | echo -n "Stopping NMEA stream on $GPS_DEVICE..." | + | echo -n "Stopping NMEA stream on $(GPS_DEVICE)..." |
start-stop-daemon --stop --pidfile $GPSDPID | start-stop-daemon --stop --pidfile $GPSDPID | ||
configure_GPS 0 1 0 | configure_GPS 0 1 0 | ||
Line 238: | Line 257: | ||
} | } | ||
− | + | turnon_WWAN () { | |
− | echo -n "Starting | + | echo -n "Starting WWAN connection..." |
− | /usr/sbin/chat -v "" "AT+CGDCONT=1,\"IP\",\"$APN\"" "OK" "AT*ENAP=1,1" "OK" > $CONTROL_DEVICE < $CONTROL_DEVICE | + | /usr/sbin/chat -v "" "AT+CGDCONT=1,\"IP\",\"$APN\"" "OK" "AT*ENAP=1,1" "OK" > $(CONTROL_DEVICE) < $(CONTROL_DEVICE) |
echo "done" | echo "done" | ||
} | } | ||
− | + | turnoff_WWAN () { | |
− | echo -n "Stopping | + | echo -n "Stopping WWAN connection..." |
− | /usr/sbin/chat -v "" "AT*ENAP=0" "OK" > $CONTROL_DEVICE < $CONTROL_DEVICE | + | /usr/sbin/chat -v "" "AT*ENAP=0" "OK" > $(CONTROL_DEVICE) < $(CONTROL_DEVICE) |
echo "done" | echo "done" | ||
turnoff_F3507g | turnoff_F3507g | ||
Line 258: | Line 277: | ||
} | } | ||
− | Give the correct '''PIN''' and find the '''APN''' for your wireless provider [http://www.pinstack.com/carrier_settings_apn_gateway.html here]. Append the following lines to your <tt>/etc/network/interfaces</tt> file | + | Give the correct '''USB_ID''' and '''PIN''', and find the '''APN''' for your wireless provider [http://www.pinstack.com/carrier_settings_apn_gateway.html here]. Append the following lines to your <tt>/etc/network/interfaces</tt> file |
iface F3507g inet manual | iface F3507g inet manual | ||
Line 274: | Line 293: | ||
iface usb0 inet dhcp | iface usb0 inet dhcp | ||
− | pre-up . /usr/local/etc/F3507g; ifup F3507g; | + | pre-up . /usr/local/etc/F3507g; ifup F3507g; turnon_WWAN |
− | post-down . /usr/local/etc/F3507g; | + | post-down . /usr/local/etc/F3507g; turnoff_WWAN |
Configure <tt>/etc/wvdial.conf</tt> to look like this: | Configure <tt>/etc/wvdial.conf</tt> to look like this: | ||
Line 290: | Line 309: | ||
Now broadband connection could be started in the same way as you start any other network interface, just by saying <tt>ifup usb0</tt> (or <tt>ifup 3G</tt>, if connecting via <tt>pppd</tt>). To shut it down, say <tt>ifdown usb0</tt> (or <tt>ifdown 3G</tt>). Similarly, GPS interface is started by <tt>ifup gps</tt> and turned off by <tt>ifdown gps</tt>. Once you get a fix, you can use your favourite GPS mapping application like [http://www.tangogps.org tangogps]. The "cold start" seems to take quite a bit however, and sometimes it cannot get a fix if indoors. | Now broadband connection could be started in the same way as you start any other network interface, just by saying <tt>ifup usb0</tt> (or <tt>ifup 3G</tt>, if connecting via <tt>pppd</tt>). To shut it down, say <tt>ifdown usb0</tt> (or <tt>ifdown 3G</tt>). Similarly, GPS interface is started by <tt>ifup gps</tt> and turned off by <tt>ifdown gps</tt>. Once you get a fix, you can use your favourite GPS mapping application like [http://www.tangogps.org tangogps]. The "cold start" seems to take quite a bit however, and sometimes it cannot get a fix if indoors. | ||
+ | |||
+ | ==Using F3507g with ifup / ifdown== | ||
+ | The [http://vog.github.io/wwan-helper/ wwan-helper] script is a simpler alternative to the "Scripting everything" section. It has slightly different chat scripts that establish a WWAN connection more reliably, even in case of a partially-initialized modem. It retries as often as necessary until the WWAN connection is really established. The downside is that it doesn't (yet) enable GPS. To use it, simply download wwan-helper: | ||
+ | |||
+ | git clone <nowiki>https://github.com/vog/wwan-helper.git</nowiki> /etc/wwan-helper | ||
+ | |||
+ | and configure your APN and PIN in <tt>/etc/wwan-helper/config</tt>: | ||
+ | |||
+ | APN=web.vodafone.de | ||
+ | PIN=1234 | ||
+ | |||
+ | Finally, add wwan-helper to the pre-up and post-down hooks: | ||
+ | |||
+ | ln -s ../../wwan-helper/wwan-helper /etc/network/if-pre-up.d/wwan-helper | ||
+ | ln -s ../../wwan-helper/wwan-helper /etc/network/if-post-down.d/wwan-helper | ||
+ | |||
+ | That way, no special settings in /etc/network/interfaces are needed, just the plain standard entry: | ||
+ | |||
+ | iface wwan0 inet dhcp | ||
+ | |||
+ | (Reminder from the [[#Overview|Overview]] section: If you have a Linux kernel 3.2 or older, use <tt>usb0</tt> instead of <tt>wwan0</tt>.) | ||
==Using F3507g with NetworkManager== | ==Using F3507g with NetworkManager== | ||
Line 299: | Line 339: | ||
== SMS with wammu/gammu == | == SMS with wammu/gammu == | ||
− | You can use [http://wammu.eu/ Wammu] to receive | + | You can use [http://wammu.eu/ Wammu] to receive and send SMS. |
− | After installing wammu (with the usual <tt> | + | After installing wammu (with the usual <tt>apt-get install wammu</tt> or whatever), choose to configure it "Manually": |
port=/dev/ttyACM0 | port=/dev/ttyACM0 | ||
− | connection= | + | connection=at |
(credits: [http://www.thinkpad-forum.de/thinkpad-software/linux-und-osx/p633662-sms-mit-der-ericsson-3507g/ linrunner]) | (credits: [http://www.thinkpad-forum.de/thinkpad-software/linux-und-osx/p633662-sms-mit-der-ericsson-3507g/ linrunner]) | ||
− | Sony Ericsson F3507g configuration [http://wammu.eu/phones/sony-ericsson/ | + | Sony Ericsson F3507g configuration [http://wammu.eu/phones/sony-ericsson/3595/ explained on wammu website] |
==Other thoughts== | ==Other thoughts== | ||
− | While <tt>AT+CFUN=*</tt> and <tt>AT+CPIN=*</tt> are pretty standard commands for wireless modems and are well-documented, it appears that the commands <tt>AT*E2GPSCTL</tt> and <tt>AT*E2GPSNPD</tt> are unique to the Ericsson F3507g card. All credit for discovering them goes to "Nickolai Zeldovich" who left a comment in this [http://redmonk.com/sogrady/2008/09/24/apone/ thread]. I imagine one could find them via a USB sniffer on a working Windows machine (or a Linux machine with Windows running in a virtual machine). Another way to get them is to try to look for "gps" string in Windows drivers. What is interesting, F3507g supports a few other AT-commands with "GPS" substring (you can get all supported AT-commands by sending <tt>AT*</tt> to <tt>/dev/ttyACM1</tt> after activating it with <tt>AT+CFUN=1</tt>). Anyway, there is a [http://www.natisbad.org/E4300/Dell_Wireless_5530_AT_cmd_ref.html project] aiming to document all AT-commands for the Ericsson F3507g card. | + | While <tt>AT+CFUN=*</tt> and <tt>AT+CPIN=*</tt> are pretty standard commands for wireless modems and are well-documented, it appears that the commands <tt>AT*E2GPSCTL</tt> and <tt>AT*E2GPSNPD</tt> are unique to the Ericsson F3507g card. All credit for discovering them goes to "Nickolai Zeldovich" who left a comment in this [http://redmonk.com/sogrady/2008/09/24/apone/ thread]. I imagine one could find them via a USB sniffer on a working Windows machine (or a Linux machine with Windows running in a virtual machine). Another way to get them is to try to look for "gps" string in Windows drivers. What is interesting, F3507g supports a few other AT-commands with "GPS" substring (you can get all supported AT-commands by sending <tt>AT*</tt> to <tt>/dev/ttyACM1</tt> after activating it with <tt>AT+CFUN=1</tt>). Anyway, there is a [http://www.natisbad.org/E4300/Dell_Wireless_5530_AT_cmd_ref.html project] aiming to document all AT-commands for the Ericsson F3507g card. The project links to a full reference which no longer works. The new link appears to be [http://developer.sonyericsson.com/cws/download/1/707/466/1277362028/DW-65054-dg_at_2006--10_r17a.pdf] |
==Related Links== | ==Related Links== | ||
*[http://www.ericsson.com/solutions/mobile_broadband_modules/docs/mobile_broadband_module_datasheet_print.pdf Ericsson Datasheet] | *[http://www.ericsson.com/solutions/mobile_broadband_modules/docs/mobile_broadband_module_datasheet_print.pdf Ericsson Datasheet] | ||
− | *[http://www.natisbad.org/E4300/Dell_Wireless_5530_AT_cmd_ref.html | + | *[http://www.natisbad.org/E4300/Dell_Wireless_5530_AT_cmd_ref.html F3507g - AT commands reference] |
+ | *[http://developer.sonyericsson.com/cws/download/1/707/466/1277362028/DW-65054-dg_at_2006--10_r17a.pdf Sony Ericsson AT commands reference] | ||
*[http://www.pinstack.com/carrier_settings_apn_gateway.html Carrier internet Settings (Apn, Gateway, etc)] | *[http://www.pinstack.com/carrier_settings_apn_gateway.html Carrier internet Settings (Apn, Gateway, etc)] | ||
*[http://mbm.sourceforge.net/ MBM project website (Support for f3507g/f3607gw in NetworkManager, kernel drivers, gps control software etc)] | *[http://mbm.sourceforge.net/ MBM project website (Support for f3507g/f3607gw in NetworkManager, kernel drivers, gps control software etc)] | ||
Line 321: | Line 362: | ||
* Ubuntu 8.10 kernel suffers from the "option" regression mentioned above. However both CDC ACM and CDC Ethernet interfaces are treated correctly by Ubuntu 9.04 kernel. | * Ubuntu 8.10 kernel suffers from the "option" regression mentioned above. However both CDC ACM and CDC Ethernet interfaces are treated correctly by Ubuntu 9.04 kernel. | ||
* Playing around with the device under Linux can cause it to disappear under Windows Vista. Issue + Fix described [http://forums.lenovo.com/t5/T400-T500-and-newer-T-series/Ericsson-f3507g-doesn-t-appear-under-Vista32-anymore-but-works/m-p/138874 here] | * Playing around with the device under Linux can cause it to disappear under Windows Vista. Issue + Fix described [http://forums.lenovo.com/t5/T400-T500-and-newer-T-series/Ericsson-f3507g-doesn-t-appear-under-Vista32-anymore-but-works/m-p/138874 here] | ||
+ | |||
+ | ==Troubleshooting== | ||
+ | Under certain circumstances the device may disappear completely from your system or refuse to connect to a network even though everything worked fine up to now. In such a situation one of the following methods could solve the problem: | ||
+ | * Use the killswitch to reset the card. Switch all rf devices off, wait about 30s (all wireless leds should be off), switch them on again and wait for the card to appear. Use 'lsusb' to find the device. | ||
+ | * Shut down, remove the battery, take out the SIM, clean the SIM slot, insert the SIM and battery and start your Thinkpad again. | ||
+ | * Disable the card in the BIOS: go to "Config", "Security", "I/O Port Access" and switch "wireless wan" to "disabled". Save, restart and boot. Then do the same thing again and enable it again. | ||
+ | If the last method doesn't show any success on windows, support will consider your card to be broken and send you a new one while your Thinkpad is still covered by the warranty. | ||
+ | Please note that Linux can revive a locked up card that can't be discovered on windows after using the last method. If even Linux can't find the device it's definitely broken and needs to be replaced. | ||
==ThinkPads this adapter may be found in== | ==ThinkPads this adapter may be found in== | ||
Line 327: | Line 376: | ||
*{{W500}} | *{{W500}} | ||
*{{X200}}, {{X200 Tablet}}, {{X301}} | *{{X200}}, {{X200 Tablet}}, {{X301}} | ||
+ | |||
+ | [[Category:WWAN Adapters]] |
Latest revision as of 15:41, 22 January 2021
Ericsson F3507g Mobile Broadband ModuleThis is a Ericsson WWAN Adapter that is installed in a Mini-PCI Express slot NOTE!
Specific versions of this card may come pre-configured for a certain carrier (AT&T)
Features
|
Lenovo Partnumbers
- Option PN 43R9152 (AT&T)
- FRU 43Y6537 (AT&T)
- FRU 43Y6513 (Other)
Forumthread with list of FRUs and corresponding firmwares (scroll down):
Firmware | Date | FRU | Remarks |
---|---|---|---|
R1A034 | 2008-05-17 | 43Y6477 | |
R1B003 | 2008-07-08 | 43Y6479 | |
R1B/1 | 2008-07-30 | 43Y6513 | |
R1D06 | 2008-11-07 | 43Y6537 | better performance and stability, fixed many bugs from the previous version |
Unlike other manufactures (Dell, Toshiba etc.) Lenovo does not release the firmware update utility public, so the only way to get a newer version F3507g is by replacing the existing one.
Contents
- 1 Ericsson F3507g Mobile Broadband Module
- 2 Features
- 3 Lenovo Partnumbers
- 4 Overview
- 5 Turning the card on
- 6 Turning the card off
- 7 Using the card as a wireless modem
- 8 Using the card as a GPS receiver
- 9 Scripting everything
- 10 Using F3507g with ifup / ifdown
- 11 Using F3507g with NetworkManager
- 12 SMS with wammu/gammu
- 13 Other thoughts
- 14 Related Links
- 15 Bugs
- 16 Troubleshooting
- 17 ThinkPads this adapter may be found in
Overview
Here are some basics about Ericsson F3507g MiniPCIe WWAN/GPS card (USB ID 0bdb:1900 and 0bdb:1902):
- the card will not work without an inserted SIM, even the GPS function. If you want to use just GPS, any SIM would work, even if it is not attached to any active account with any GSM provider.
- the card provides three CDC ACM interfaces (CONFIG_USB_ACM=m), two CDC WDM interfaces (CONFIG_USB_WDM=m) and one CDC Ethernet interface (CONFIG_USB_NET_CDCETHER=m), and identifies them as
for n in `ls /sys/class/*/*{ACM,wdm,usb0}*/device/interface`;do echo $(echo $n|awk -F '/' '{print $5}') : $(cat $n);done usb0 : Ericsson F3507g Mobile Broadband Minicard Network Adapter ttyACM0 : Ericsson F3507g Mobile Broadband Minicard Modem ttyACM1 : Ericsson F3507g Mobile Broadband Minicard Data Modem ttyACM2 : Ericsson F3507g Mobile Broadband Minicard GPS Port cdc-wdm0 : Ericsson F3507g Mobile Broadband Minicard Device Management cdc-wdm1 : Ericsson F3507g Mobile Broadband Minicard PC SC Port
Note:
- apparently, for a while option USB-serial driver had claimed USB ID 0bdb:1900, but this was wrong, and as of kernel 2.6.28.9 that commit was reversed. If instead of /dev/ttyACM* you see /dev/ttyUSB*, it means that option module is loaded. You may need to blacklist it to make sure it doesn't happen.
- Support for the CDC Ethernet interface appears only in kernel 2.6.28.8. But if your kernel is older, you can still connect to the net using one of the "Modem" interfaces. As of kernel 2.6.33 it is named wwan0 rather than usb0.
As Ericsson's naming scheme suggests, idealy we would use /dev/cdc-wdm0 for controlling the card, usb0 (or wwan0) as a network device, /dev/ttyACM0 or /dev/ttyACM1 as a modem, and /dev/ttyACM2 for GPS. This works for manual testing, but unfortunately, due to limitations of chat, does not play very well in scripts. So, instead of /dev/cdc-wdm0, for controlling the card we will use /dev/ttyACM1.
Turning the card on
First, check whenever the SIM is protected by PIN by sending
AT+CPIN?
to /dev/ttyACM1. You can do it with any terminal terminal program like cu or minicom. If the answer is
+CPIN: READY
then the SIM is unlocked. If the answer is
+CPIN: SIM PIN
you need first to unlock it by sending
AT+CPIN="YOUR-PIN"
to /dev/ttyACM1. Now the card can be turned on by sending
AT+CFUN=1
to /dev/ttyACM1. The answer should be
+PACSP0
Don't try to do anything until you see it. To force GSM-only connection, send
AT+CFUN=5
to /dev/ttyACM1. To force WCDMA-only connection, send
AT+CFUN=6
to /dev/ttyACM1.
Turning the card off
To put the card into energy-saving mode (this is the default), you can send
AT+CFUN=4
to /dev/ttyACM1. To remove all power from the card, send
AT+CFUN=0
to /dev/ttyACM1. Be carefull with the last command. It turns the card completely off, and it will no longer accept any AT-commands before the hard reset. To physically reset the card flip the wireless switch off, and then on. You can do the same by sending echo 0 > /sys/devices/platform/thinkpad_acpi/rfkill/rfkill0/state (to turn off) and then echo 1 > /sys/devices/platform/thinkpad_acpi/rfkill/rfkill0/state (to turn on).
Using the card as a wireless modem
Once the card is turned on, there are two ways to connect to the net. The first one is just to use the card as any "normal" GPRS modem and start pppd daemon on one of /dev/ttyACM*. The other way is to use CDC Ethernet interface. It is supposed to be more efficient, but it requires a pretty recent (>=2.6.28.8) kernel.
Connecting to the net via pppd
For the first approach, the easiest way to do it is to use wvdial. For example, to connect to AT&T Wireless network, your /etc/wvdial.conf would have to be something like this
[Dialer 3G] Modem = /dev/ttyACM0 Init1 = AT+CGDCONT=1,"IP","proxy" Stupid mode = 1 phone= *99# Username = * Password = *
Note: if you are using a SIM from a different mobile provider, you may need to change the access point name (APN) "proxy" in Init1 string and Username/Password to something else. You can find the appropriate APN here.
Connecting to the net via CDC Ethernet interface
The second approach works for kernels >=2.6.28.8. Configure the APN by sending
AT+CGDCONT=1,"IP","proxy"
to /dev/ttyACM1. Instead of "proxy" you may need to use to something else. Find the appropriate APN here. To initiate the connection, send
AT*ENAP=1,1
to /dev/ttyACM1. Now, if your wireless provider lets you in, you are connected. Launch dhclient
dhclient usb0
and start surfing the net (or use wwan0 for kernels >= 2.6.33). To disconnect, send
AT*ENAP=0
to /dev/ttyACM1.
Using the card as a GPS receiver
Once the card is turned on, we can use it to get GPS info via NMEA protocol. First, you have to configure the a few NMEA options. It is done by sending
AT*E2GPSCTL=X,Y,Z
to /dev/ttyACM1. Here
- X can be 0 (NMEA stream turned off) or 1 (NMEA stream turned on)
- Y can be an integer form 1 to 60, and sets the frequency of how often the card emits the NMEA sentences
- Z can be 0 (DGPS is turned off) or 1 (DGPS is turned on)
so, to configure the GPSr to update every 5 seconds, and turn DGPS on, you would send
AT*E2GPSCTL=1,5,1
to /dev/ttyACM1. Once the GPSr is configured, we can get the NMEA stream on /dev/ttyACM2 by sending
AT*E2GPSNPD
to /dev/ttyACM2. Once you do that, /dev/ttyACM2 will no longer accept any new AT-commands. But you still can change the the behavior of the NMEA stream by sending the appropriate
AT*E2GPSCTL=X,Y,Z
to /dev/ttyACM1. Now you can read the NMEA stream by saying
cat /dev/ttyACM2
or better yet, start gpsd interface on /dev/ttyACM2.
Note: There is a now a sourceforge project dedicated to the Ericsson Mobile Broadband modules. Gps control sw that does the above automatically is available and also a graphical user interface. Details are available on the MBM Wiki.
Scripting everything
Install the packages
apt-get install sysfsutils gpsd wvdial
In order to save the power, let us use sysfsutils to completely power off the WWAN card on boot. Append the following line to /etc/sysfs.conf
devices/platform/thinkpad_acpi/rfkill/rfkill0/state = 0
It will power down the card on boot, but when the laptop wakes from sleep, in some cases the card is powered up again. To re-apply these settings on wake-up, create a script named /etc/pm/sleep.d/10sysfsutils:
#!/bin/sh case $1 in (hibernate|suspend) ;; (thaw|resume) /etc/init.d/sysfsutils start ;; *) echo "somebody is calling me totally wrong." ;; esac
Don't forget to chmod a+x /etc/pm/sleep.d/10sysfsutils. Create a file called /usr/local/etc/F3507g containing the following:
USB_ID="0bdb:1900" PIN="" APN="proxy" GPSDPID="/var/run/gpsd.pid" RFKILL_DEVICE=$(for n in /sys/devices/platform/thinkpad_acpi/rfkill/rfkill*; do if [ "$(cat $n/name)" = "tpacpi_wwan_sw" ]; then echo $n/state; fi; done) CONTROL_DEVICE () { echo /dev/$(for n in /sys/class/tty/ttyACM*/device/interface;do if [ "$(cat $n)" = "Ericsson F3507g Mobile Broadband Minicard Data Modem" ]; then echo $n|awk -F '/' '{print $5}'; fi; done) } GPS_DEVICE () { echo /dev/$(for n in /sys/class/tty/ttyACM*/device/interface;do if [ "$(cat $n)" = "Ericsson F3507g Mobile Broadband Minicard GPS Port" ]; then echo $n|awk -F '/' '{print $5}'; fi; done) } powerup_F3507g () { echo -n "Powering up F3507g card.." echo 1 > $RFKILL_DEVICE while [ -z "$(lsusb -d $USB_ID)" ]; do sleep 0.5; echo -n "."; done echo "done" echo -n "Turning on F3507g card..." sleep 3 if [ -n "$PIN" ]; then /usr/sbin/chat -v "" "AT+CPIN?" "SIM PIN" "AT" "OK" "AT+CPIN=\"$PIN\"" "OK" > $(CONTROL_DEVICE) < $(CONTROL_DEVICE) fi /usr/sbin/chat -v "" "AT+CPIN?" "READY" "AT+CFUN=1" "+PACSP" "AT" "OK" > $(CONTROL_DEVICE) < $(CONTROL_DEVICE) echo "done" } powerdown_F3507g () { echo -n "Turning off F3507g card..." /usr/sbin/chat -v "" "AT+CFUN=4" "OK" > $(CONTROL_DEVICE) < $(CONTROL_DEVICE) echo "done" echo -n "Powering down F3507g card.." echo 0 > $RFKILL_DEVICE while [ -n "$(lsusb -d $USB_ID)" ]; do sleep 0.5; echo -n "."; done echo "done" } configure_GPS () { /usr/sbin/chat -v "" "AT*E2GPSCTL=$1,$2,$3" "OK" > $(CONTROL_DEVICE) < $(CONTROL_DEVICE) } turnon_GPS () { echo -n "Starting NMEA stream on $(GPS_DEVICE)..." configure_GPS 1 1 1 sleep 1 /usr/sbin/chat -v "" "AT*E2GPSNPD" "GPGGA" > $(GPS_DEVICE) < $(GPS_DEVICE) start-stop-daemon --start --exec /usr/sbin/gpsd -- -P $GPSDPID $(GPS_DEVICE) echo "done" } turnoff_GPS () { echo -n "Stopping NMEA stream on $(GPS_DEVICE)..." start-stop-daemon --stop --pidfile $GPSDPID configure_GPS 0 1 0 echo "done" turnoff_F3507g } turnon_WWAN () { echo -n "Starting WWAN connection..." /usr/sbin/chat -v "" "AT+CGDCONT=1,\"IP\",\"$APN\"" "OK" "AT*ENAP=1,1" "OK" > $(CONTROL_DEVICE) < $(CONTROL_DEVICE) echo "done" } turnoff_WWAN () { echo -n "Stopping WWAN connection..." /usr/sbin/chat -v "" "AT*ENAP=0" "OK" > $(CONTROL_DEVICE) < $(CONTROL_DEVICE) echo "done" turnoff_F3507g } turnoff_F3507g () { [ -z $(grep gps /etc/network/run/ifstate) ] && \ [ -z $(grep usb0 /etc/network/run/ifstate) ] && \ [ -z $(grep 3G /etc/network/run/ifstate) ] && \ ifdown F3507g }
Give the correct USB_ID and PIN, and find the APN for your wireless provider here. Append the following lines to your /etc/network/interfaces file
iface F3507g inet manual up . /usr/local/etc/F3507g; powerup_F3507g down . /usr/local/etc/F3507g; powerdown_F3507g iface 3G inet wvdial pre-up ifup F3507g post-down . /usr/local/etc/F3507g; turnoff_F3507g provider 3G iface gps inet manual up . /usr/local/etc/F3507g; ifup F3507g; turnon_GPS down . /usr/local/etc/F3507g; turnoff_GPS iface usb0 inet dhcp pre-up . /usr/local/etc/F3507g; ifup F3507g; turnon_WWAN post-down . /usr/local/etc/F3507g; turnoff_WWAN
Configure /etc/wvdial.conf to look like this:
[Dialer 3G] Modem = /dev/ttyACM0 Init1 = AT+CGDCONT=1,"IP","proxy" Stupid mode = 1 phone= *99# Username = * Password = *
Note: you may need to change the access point name (APN) "proxy" in Init1 string and Username/Password to something else. Find the appropriate APN here.
Now broadband connection could be started in the same way as you start any other network interface, just by saying ifup usb0 (or ifup 3G, if connecting via pppd). To shut it down, say ifdown usb0 (or ifdown 3G). Similarly, GPS interface is started by ifup gps and turned off by ifdown gps. Once you get a fix, you can use your favourite GPS mapping application like tangogps. The "cold start" seems to take quite a bit however, and sometimes it cannot get a fix if indoors.
Using F3507g with ifup / ifdown
The wwan-helper script is a simpler alternative to the "Scripting everything" section. It has slightly different chat scripts that establish a WWAN connection more reliably, even in case of a partially-initialized modem. It retries as often as necessary until the WWAN connection is really established. The downside is that it doesn't (yet) enable GPS. To use it, simply download wwan-helper:
git clone https://github.com/vog/wwan-helper.git /etc/wwan-helper
and configure your APN and PIN in /etc/wwan-helper/config:
APN=web.vodafone.de PIN=1234
Finally, add wwan-helper to the pre-up and post-down hooks:
ln -s ../../wwan-helper/wwan-helper /etc/network/if-pre-up.d/wwan-helper ln -s ../../wwan-helper/wwan-helper /etc/network/if-post-down.d/wwan-helper
That way, no special settings in /etc/network/interfaces are needed, just the plain standard entry:
iface wwan0 inet dhcp
(Reminder from the Overview section: If you have a Linux kernel 3.2 or older, use usb0 instead of wwan0.)
Using F3507g with NetworkManager
Work is ongoing to add support for Ericsson Mobile Broadband Modules to GNOME NetworkManager / modem-manager. More information is available on the MBM project website and the MBM wiki.
The F3507g card (in a ThinkPad T400s) works out of the box on Fedora 11. No configuration is needed beyond setting the data plan provider in the nm-applet GUI.
Using mbm-gpsd gps works flawlessly with the F3507g on Karmic Koala with modemmanager packages from Ubuntu PPA, the mbm-gpsd installed by source using the description from here and knowing the PIN of your SIM card.
SMS with wammu/gammu
You can use Wammu to receive and send SMS.
After installing wammu (with the usual apt-get install wammu or whatever), choose to configure it "Manually":
port=/dev/ttyACM0 connection=at
(credits: linrunner)
Sony Ericsson F3507g configuration explained on wammu website
Other thoughts
While AT+CFUN=* and AT+CPIN=* are pretty standard commands for wireless modems and are well-documented, it appears that the commands AT*E2GPSCTL and AT*E2GPSNPD are unique to the Ericsson F3507g card. All credit for discovering them goes to "Nickolai Zeldovich" who left a comment in this thread. I imagine one could find them via a USB sniffer on a working Windows machine (or a Linux machine with Windows running in a virtual machine). Another way to get them is to try to look for "gps" string in Windows drivers. What is interesting, F3507g supports a few other AT-commands with "GPS" substring (you can get all supported AT-commands by sending AT* to /dev/ttyACM1 after activating it with AT+CFUN=1). Anyway, there is a project aiming to document all AT-commands for the Ericsson F3507g card. The project links to a full reference which no longer works. The new link appears to be [1]
Related Links
- Ericsson Datasheet
- F3507g - AT commands reference
- Sony Ericsson AT commands reference
- Carrier internet Settings (Apn, Gateway, etc)
- MBM project website (Support for f3507g/f3607gw in NetworkManager, kernel drivers, gps control software etc)
Bugs
- Ubuntu 8.10 kernel suffers from the "option" regression mentioned above. However both CDC ACM and CDC Ethernet interfaces are treated correctly by Ubuntu 9.04 kernel.
- Playing around with the device under Linux can cause it to disappear under Windows Vista. Issue + Fix described here
Troubleshooting
Under certain circumstances the device may disappear completely from your system or refuse to connect to a network even though everything worked fine up to now. In such a situation one of the following methods could solve the problem:
- Use the killswitch to reset the card. Switch all rf devices off, wait about 30s (all wireless leds should be off), switch them on again and wait for the card to appear. Use 'lsusb' to find the device.
- Shut down, remove the battery, take out the SIM, clean the SIM slot, insert the SIM and battery and start your Thinkpad again.
- Disable the card in the BIOS: go to "Config", "Security", "I/O Port Access" and switch "wireless wan" to "disabled". Save, restart and boot. Then do the same thing again and enable it again.
If the last method doesn't show any success on windows, support will consider your card to be broken and send you a new one while your Thinkpad is still covered by the warranty. Please note that Linux can revive a locked up card that can't be discovered on windows after using the last method. If even Linux can't find the device it's definitely broken and needs to be replaced.