LTE mPCIe module hardware solution (cellular failover)

kapara

Got this from the diagnostics in windows.

ATQ0V1E0 - OK
AT+GMM - MC7700
AT+FCLASS=? - +FCLASS: (0-1)
AT#CLS=? - COMMAND NOT SUPPORTED
AT+GCI? - COMMAND NOT SUPPORTED
AT+GCI=? - COMMAND NOT SUPPORTED
ATI1 - Manufacturer: Sierra Wireless, Incorporated
Model: MC7700
Revision: SWI9200X_03.05.14.00AP R5164 CARMD-EN-10527 2012/05/29 19:13:25
IMEI: 359469040373130
IMEI SV: 11
FSN: CDC3434279310
3GPP Release 8
+GCAP: +CGSM,+DS,+ES
ATI2 - Manufacturer: Sierra Wireless, Incorporated
Model: MC7700
Revision: SWI9200X_03.05.14.00AP R5164 CARMD-EN-10527 2012/05/29 19:13:25
IMEI: 359469040373130
IMEI SV: 11
FSN: CDC3434279310
3GPP Release 8
+GCAP: +CGSM,+DS,+ES
ATI3 - Manufacturer: Sierra Wireless, Incorporated
Model: MC7700
Revision: SWI9200X_03.05.14.00AP R5164 CARMD-EN-10527 2012/05/29 19:13:25
IMEI: 359469040373130
IMEI SV: 11
FSN: CDC3434279310
3GPP Release 8
+GCAP: +CGSM,+DS,+ES
ATI4 - Manufacturer: Sierra Wireless, Incorporated
Model: MC7700
Revision: SWI9200X_03.05.14.00AP R5164 CARMD-EN-10527 2012/05/29 19:13:25
IMEI: 359469040373130
IMEI SV: 11
FSN: CDC3434279310
3GPP Release 8
+GCAP: +CGSM,+DS,+ES
ATI5 - Manufacturer: Sierra Wireless, Incorporated
Model: MC7700
Revision: SWI9200X_03.05.14.00AP R5164 CARMD-EN-10527 2012/05/29 19:13:25
IMEI: 359469040373130
IMEI SV: 11
FSN: CDC3434279310
3GPP Release 8
+GCAP: +CGSM,+DS,+ES
ATI6 - Manufacturer: Sierra Wireless, Incorporated
Model: MC7700
Revision: SWI9200X_03.05.14.00AP R5164 CARMD-EN-10527 2012/05/29 19:13:25
IMEI: 359469040373130
IMEI SV: 11
FSN: CDC3434279310
3GPP Release 8
+GCAP: +CGSM,+DS,+ES
ATI7 - Manufacturer: Sierra Wireless, Incorporated
Model: MC7700
Revision: SWI9200X_03.05.14.00AP R5164 CARMD-EN-10527 2012/05/29 19:13:25
IMEI: 359469040373130
IMEI SV: 11
FSN: CDC3434279310
3GPP Release 8
+GCAP: +CGSM,+DS,+ES

FranciscoFranco

I would use putty and see if you can talk AT to the modem there in Windows. Look in your device manager to find the correct AT terminal COM port. You want to run the at!udinfo? command to see the Interface Mode.

The thing is Windows above Version 8 now uses MBIM only mode which is non-standard and offers no AT command facility. Windows also slips in special MBIM only firmware updates to the Sierra modems via Windows Updates. You defiantly don't want a MBIM-only module. I wouldn't have a ethernet wire anywhere near Windows. Download the firmware, flash it and escape.

There is a Sierra Windows utility for switching between DIP and QMI mode as well. No flashing required.

kapara

That is my issue. No windows 7. I will. Hold out a system with windows 7.

FranciscoFranco

I would try first with Ubuntu and make sure it connects. Like I say the IMEI numbers can get blacklisted. You seem to have an OEM variant looking at the picture(SKU=110-1882). That is why it uses a different IEMI prefix(3594). Plus you can tell by the 2012 firmware date it is an early model. Plus it is marked A0 module. I think 1882 SKU is Panasonic OEM number.

I can tell you the earlier modules sometimes need to be brought up to date in stages. See if you can find something from 2013 for firmware then do the newest..

Have you tried flashing with the newest QMI firmware from Windows. I think it may be in QMI mode as per your pfSense output.
Then you could flash with DIP firmware. You probably also need the Windows QMI drivers to load the card. Also the Sierra watcher is only DIP for QMI it uses a different app called Skylight watcher.

FranciscoFranco

I say its in QMI mode because my dmesg looks like this;


root@E6420:~ # dmesg |grep u3g0
u3g0: <sierra 0="" 3="" wireless,="" incorporated="" mc7700,="" class="" 0,="" rev="" 2.00="" 0.06,="" addr="">on usbus1
u3g0: Found 6 ports.</sierra>

FranciscoFranco

Also the modules PID changes for QMI mode. So if you can pull up a terminal you can switch it to DIP. Then install DIP drivers in Windows and flash it with DIP firmware.

https://gist.github.com/mmv-ru/1a52c10a4d5577a5ed30

kapara

Finally got it to work. I guess not giving up eventually pays off!

Found a post regarding a tool to switch from QMI to DIP

Post:

https://forums.lenovo.com/t5/ThinkPad-T400-T500-and-newer-T/T430i-and-MC7700-in-DIP-mode-will-not-boot-System-is-Halted-Was/td-p/3367435

Tool:

http://hptouchpad4g.com/Support/sierra/windows/ModeSwitch/BZ31018_DIP_QMI_ModeSwitch.zip

I probably read over 80 forum postings before I could find this!

After running tool PC required reboot and now device is DIP mode

Output from my Putty attached.

Ok so now the next step. How to get this working with Carrier T-Mobile on the pfsense!

Capture.PNG_thumb

FranciscoFranco

From here it is a matter of choosing what interface you want to call it. Either OPT or WAN for your failover.
So go to PPP and make your connection. Use your APN for T-Mobile and cuaU0.3 to connect, From there check your logs to see it connect or wait for it to acquire a DHCP address. It will show up on the dashboard.

kapara

My APN? What is that and how do I find it?

FranciscoFranco

It comes up under Interfaces>PPP
Use cuaU0.3. My screenshot is an example with no modem.

screenshot2.png_thumb

FranciscoFranco

So you make your cellular interface under Interfaces>PPP connection from the tab and save. Then go to interfaces and add a new interface and use the PPP connection. You might want to research LAGG for the failover part.
Make sure you can connect first. Did you connect with FreeBSD/Ubuntu or Windows just to make sure the modem is OK?

kapara

I did not try in Windows as I do not know exactly how in Windows. Is that with the Watcher?

Also here is the output for pfsense after configuring modem with T-Mobile in PPP. Not working. I have yet to receive my antenna so not sure if that will prevent this from moving forward but I would think it should get some type of signal.

Jun 13 02:09:57	ppp		[opt1_link0] Link: reconnection attempt 54
Jun 13 02:09:57	ppp		[opt1_link0] CHAT: +CGDCONT=1,"IP","fast.t-mobile.com"
Jun 13 02:09:57	ppp		[opt1_link0] CHAT: Detected Hayes compatible modem.
Jun 13 02:09:57	ppp		[opt1_link0] CHAT: Dialing server at *99#...
Jun 13 02:09:57	ppp		[opt1_link0] CHAT: ATDT*99#
Jun 13 02:09:57	ppp		[opt1_link0] CHAT: Invalid dial init string.
Jun 13 02:09:57	ppp		[opt1_link0] MODEM: chat script failed
Jun 13 02:09:57	ppp		[opt1_link0] Link: DOWN event
Jun 13 02:09:57	ppp		[opt1_link0] LCP: Down event
Jun 13 02:09:57	ppp		[opt1_link0] Link: reconnection attempt 55 in 3 seconds
Jun 13 02:10:00	ppp		[opt1_link0] Link: reconnection attempt 55
Jun 13 02:10:00	ppp		[opt1_link0] CHAT: +CGDCONT=1,"IP","fast.t-mobile.com"
Jun 13 02:10:00	ppp		[opt1_link0] CHAT: Detected Hayes compatible modem.
Jun 13 02:10:00	ppp		[opt1_link0] CHAT: Dialing server at *99#...
Jun 13 02:10:00	ppp		[opt1_link0] CHAT: ATDT*99#
Jun 13 02:10:00	ppp		[opt1_link0] CHAT: Invalid dial init string.
Jun 13 02:10:00	ppp		[opt1_link0] MODEM: chat script failed
Jun 13 02:10:00	ppp		[opt1_link0] Link: DOWN event
Jun 13 02:10:00	ppp		[opt1_link0] LCP: Down event
Jun 13 02:10:00	ppp		[opt1_link0] Link: reconnection attempt 56 in 1 seconds
Jun 13 02:10:01	ppp		[opt1_link0] Link: reconnection attempt 56
Jun 13 02:10:03	ppp		[opt1_link0] CHAT: +CGDCONT=1,"IP","fast.t-mobile.com"
Jun 13 02:10:03	ppp		[opt1_link0] CHAT: Detected Hayes compatible modem.
Jun 13 02:10:03	ppp		[opt1_link0] CHAT: Dialing server at *99#...
Jun 13 02:10:03	ppp		[opt1_link0] CHAT: ATDT*99#
Jun 13 02:10:03	ppp		[opt1_link0] CHAT: Invalid dial init string.
Jun 13 02:10:03	ppp		[opt1_link0] MODEM: chat script failed
Jun 13 02:10:03	ppp		[opt1_link0] Link: DOWN event
Jun 13 02:10:03	ppp		[opt1_link0] LCP: Down event
Jun 13 02:10:03	ppp		[opt1_link0] Link: reconnection attempt 57 in 4 seconds
Jun 13 02:10:07	ppp		[opt1_link0] Link: reconnection attempt 57
Jun 13 02:10:07	ppp		[opt1_link0] CHAT: +CGDCONT=1,"IP","fast.t-mobile.com"
Jun 13 02:10:08	ppp		[opt1_link0] CHAT: Detected Hayes compatible modem.
Jun 13 02:10:08	ppp		[opt1_link0] CHAT: Dialing server at *99#...
Jun 13 02:10:08	ppp		[opt1_link0] CHAT: ATDT*99#
Jun 13 02:10:08	ppp		[opt1_link0] CHAT: Invalid dial init string.
Jun 13 02:10:08	ppp		[opt1_link0] MODEM: chat script failed
Jun 13 02:10:08	ppp		[opt1_link0] Link: DOWN event
Jun 13 02:10:08	ppp		[opt1_link0] LCP: Down event
Jun 13 02:10:08	ppp		[opt1_link0] Link: reconnection attempt 58 in 2 seconds
Jun 13 02:10:10	ppp		[opt1_link0] Link: reconnection attempt 58
Jun 13 02:10:11	ppp		[opt1_link0] CHAT: +CGDCONT=1,"IP","fast.t-mobile.com"
Jun 13 02:10:11	ppp		[opt1_link0] CHAT: Detected Hayes compatible modem.
Jun 13 02:10:11	ppp		[opt1_link0] CHAT: Dialing server at *99#...
Jun 13 02:10:11	ppp		[opt1_link0] CHAT: ATDT*99#
Jun 13 02:10:11	ppp		[opt1_link0] CHAT: Invalid dial init string.
Jun 13 02:10:11	ppp		[opt1_link0] MODEM: chat script failed
Jun 13 02:10:11	ppp		[opt1_link0] Link: DOWN event
Jun 13 02:10:11	ppp		[opt1_link0] LCP: Down event
Jun 13 02:10:11	ppp		[opt1_link0] Link: reconnection attempt 59 in 1 seconds

kapara

I am a dummy

I forgot to ad the SIM back to the pcengines board.

Still not connecting but getting different response.

Jun 13 02:45:43	ppp		[opt1_link0] Link: reconnection attempt 8
Jun 13 02:45:45	ppp		[opt1_link0] CHAT: +CGDCONT=1,"IP","fast.t-mobile.com"
Jun 13 02:45:45	ppp		[opt1_link0] CHAT: Detected Hayes compatible modem.
Jun 13 02:45:45	ppp		[opt1_link0] CHAT: Dialing server at *99#...
Jun 13 02:45:45	ppp		[opt1_link0] CHAT: ATDT*99#
Jun 13 02:45:45	ppp		[opt1_link0] CHAT: The remote modem did not answer.
Jun 13 02:45:45	ppp		[opt1_link0] MODEM: chat script failed
Jun 13 02:45:45	ppp		[opt1_link0] Link: DOWN event
Jun 13 02:45:45	ppp		[opt1_link0] LCP: Down event
Jun 13 02:45:45	ppp		[opt1_link0] Link: reconnection attempt 9 in 3 seconds
Jun 13 02:45:48	ppp		[opt1_link0] Link: reconnection attempt 9
Jun 13 02:45:48	ppp		[opt1_link0] CHAT: +CGDCONT=1,"IP","fast.t-mobile.com"
Jun 13 02:45:48	ppp		[opt1_link0] CHAT: Detected Hayes compatible modem.
Jun 13 02:45:48	ppp		[opt1_link0] CHAT: Dialing server at *99#...
Jun 13 02:45:48	ppp		[opt1_link0] CHAT: ATDT*99#
Jun 13 02:45:48	ppp		[opt1_link0] CHAT: The remote modem did not answer.
Jun 13 02:45:48	ppp		[opt1_link0] MODEM: chat script failed
Jun 13 02:45:48	ppp		[opt1_link0] Link: DOWN event
Jun 13 02:45:48	ppp		[opt1_link0] LCP: Down event
Jun 13 02:45:48	ppp		[opt1_link0] Link: reconnection attempt 10 in 4 seconds
Jun 13 02:45:52	ppp		[opt1_link0] Link: reconnection attempt 10
Jun 13 02:45:52	ppp		[opt1_link0] CHAT: +CGDCONT=1,"IP","fast.t-mobile.com"
Jun 13 02:45:52	ppp		[opt1_link0] CHAT: Detected Hayes compatible modem.
Jun 13 02:45:52	ppp		[opt1_link0] CHAT: Dialing server at *99#...
Jun 13 02:45:52	ppp		[opt1_link0] CHAT: ATDT*99#
Jun 13 02:45:52	ppp		[opt1_link0] CHAT: The remote modem did not answer.
Jun 13 02:45:52	ppp		[opt1_link0] MODEM: chat script failed
Jun 13 02:45:52	ppp		[opt1_link0] Link: DOWN event
Jun 13 02:45:52	ppp		[opt1_link0] LCP: Down event
Jun 13 02:45:52	ppp		[opt1_link0] Link: reconnection attempt 11 in 4 seconds
Jun 13 02:45:56	ppp		[opt1_link0] Link: reconnection attempt 11
Jun 13 02:45:56	ppp		[opt1_link0] CHAT: +CGDCONT=1,"IP","fast.t-mobile.com"
Jun 13 02:45:56	ppp		[opt1_link0] CHAT: Detected Hayes compatible modem.
Jun 13 02:45:56	ppp		[opt1_link0] CHAT: Dialing server at *99#...
Jun 13 02:45:56	ppp		[opt1_link0] CHAT: ATDT*99#
Jun 13 02:45:56	ppp		[opt1_link0] CHAT: The remote modem did not answer.
Jun 13 02:45:56	ppp		[opt1_link0] MODEM: chat script failed
Jun 13 02:45:56	ppp		[opt1_link0] Link: DOWN event
Jun 13 02:45:56	ppp		[opt1_link0] LCP: Down event
Jun 13 02:45:56	ppp		[opt1_link0] Link: reconnection attempt 12 in 2 seconds
Jun 13 02:45:58	ppp		[opt1_link0] Link: reconnection attempt 12
Jun 13 02:45:59	ppp		[opt1_link0] CHAT: +CGDCONT=1,"IP","fast.t-mobile.com"
Jun 13 02:45:59	ppp		[opt1_link0] CHAT: Detected Hayes compatible modem.
Jun 13 02:45:59	ppp		[opt1_link0] CHAT: Dialing server at *99#...
Jun 13 02:45:59	ppp		[opt1_link0] CHAT: ATDT*99#
Jun 13 02:45:59	ppp		[opt1_link0] CHAT: The remote modem did not answer.
Jun 13 02:45:59	ppp		[opt1_link0] MODEM: chat script failed
Jun 13 02:45:59	ppp		[opt1_link0] Link: DOWN event
Jun 13 02:45:59	ppp		[opt1_link0] LCP: Down event
Jun 13 02:45:59	ppp		[opt1_link0] Link: reconnection attempt 13 in 3 seconds

FranciscoFranco

No Antenna-no work. I think your in good shape.

kapara

Going to buy a GPS antenna also and see if I can get this to work. This document shows the the GPS interface supports Active 3v antenna. Looking to use this for NTP server.

My module shows that pfsense found 6 interfaces. Interested if it will be easy to find which one it corresponds to. Document shows how to activate power on GPS.

https://source.sierrawireless.com/resources/airprime/application_notes_and_code_samples/airprime-gps_active_antenna_supply/

kapara

Another nice tool I found while searching the internet:

https://www.open-electronics.org/at-command-tester-the-free-online-software-tool-to-test-gsm-at-commands/

FranciscoFranco

I had gpsd working with my MC7700. On pfSense packages are limited so only some features from it work(no perl). xgps does work.

No PPS so as a time server it is limited. Found it good for Arm with RTC modules keeping poor time.

With AT commands you can set which antenna jack to use for GPS signal. So instead of using the dedicated GPS antenna jack you can set it to ANT2 and use the data antenna built into a laptop to receive GPS signal. The AT command is in the Extended AT Command Guide.

FranciscoFranco

I am wondering why you are trying to get the MC7700 going on T-Mobile.
If you notice my post on the first page MC7700=ATT and MC7710=TMobile

It should still work but I doubt it will get LTE. It will fall back to 3G in the 1900-2100 frequency range.
MC7710 is more expensive. So much so you should consider the MC7354/MC7355 for TMobile.

q54e3w

Just to add my understanding here, with the cm & em7455 and perhaps it matches with other models, is that they sell them with carrier approved firmware's with different product codes, however its all the same hardware so you can refresh with either generic of carrier specific firmware. I tried to get my EM7455 to register on ATT network using the carrier specific firmware and couldn't, I had to use generic and configure ATT settings to connect which i think has something to do with approved devices on the plan I am using.
Certainly the price for the Dell & Lenovo variations of the EM7455 is half the Sierra Wireless model (80usd vs 150usd) but they can easily be changed between variations as needed. The only pain is that on reset the Dell and Lenovo models revert to their original status codes and need reconfiguring. Once up and running, they are the same. Thats my current understanding.

kapara

@q54e3w:

Just to add my understanding here, with the cm & em7455 and perhaps it matches with other models, is that they sell them with carrier approved firmware's with different product codes, however its all the same hardware so you can refresh with either generic of carrier specific firmware. I tried to get my EM7455 to register on ATT network using the carrier specific firmware and couldn't, I had to use generic and configure ATT settings to connect which i think has something to do with approved devices on the plan I am using.
Certainly the price for the Dell & Lenovo variations of the EM7455 is half the Sierra Wireless model (80usd vs 150usd) but they can easily be changed between variations as needed. The only pain is that on reset the Dell and Lenovo models revert to their original status codes and need reconfiguring. Once up and running, they are the same. Thats my current understanding.

Do you have step by step directions for how to do this?