LTE mPCIe module hardware solution (cellular failover)



  • Have a requirement that I am trying to see how viable it is to integrate this into pfsense rather than buy an external modem.

    Purchased a cradlepoint IBR650-LP4 which is a router with built in LTE modem for both ATT/TMOBILE/VERIZON.  This can also use local broadband and has a cloud managment interface to manage remotely but does not have additional advantages like NTP Server with GPS nor does it have squid which would be very useful for reducing bandwidth consumption!  Also it is priced at about $500.

    Rather than buy an external unit (modem) I was interested in purchasing an Sierra Wireless MC7355 mPCIe adapter.  Listed on supported on pfsense website.

    https://www.amazon.com/Sierra-Wireless-Airprime-100mbps-Unlocked/dp/B00XLAWR3E

    Has anyone had solid experience with this?  Also the unit has a GPS module built in with option for GPS antennae.  I would be curious if it would work with the NTP GPS option built into pfsense.

    If anyone could provide their experience or recommend another module.

    Also provide any recommended hardware including pfsense built that I could add this to the unit.  I noticed pcengines has 3 mPCIe slots and I have one on hand to test with.

    Thanks!



  • Hoping to find a easy solution.  Many posts show problematic setups so if there is something that works best please let me know.  These cards are not cheap so I do t want to have to spend more than needed.

    Thanks



  • I think the MC7354 and MC7355 are good modems. I would consider getting one off ebay. Truthfully if you just want to test cell modules for cheap the MC7700 on ATT can be had for dirt($20USD). I use both currently on my FreeBSD laptops. ATT on MC7700 and MC7354 on TMobile firmware. I even keep a few cheap StraightTalk tablet SIMs active for testing.
    The prime difference is the LTE Bands supported. MC7700 uses ATT B17 while the MC7710 model supports B2 and B4 for Tmobile. Both GSM only.
    While the MC7354/MC7355 can support many bands and can do CDMA or GSM depending on the firmware used. Supports B17,B2,B4 and more.

    There is a fair amount of complexity involved on getting a module usable on pfSense and FreeBSD. Sometimes it helps to have a laptop to get it right before trying out the headless APU. It mainly involves setting the USB composition to something FreeBSD understands. Flashing the newest firmware is a good idea as they update protocols. An external USB/mPCIe adapter board with SIM slot works fine for setup too.



  • I would be interested in a card that can work on t-Mobile, ATT, and verizon.  Is there such a card?

    Any suggestions on this type of card?  For now I will get the MC770 to get my feet wet. :-)

    Also is it possible to use the GPS which is included for NTP?



  • The MC7354/MC7355 will do all those. You might need to sign up to the Sierra site to get the various firmwares. Have you dealt with Verizon on data services? They are very strict on SIMs and you can't simply interchange SIMs between devices. You can call them and they will activate the SIM on a new device, its just nothing like any other carriers. ATT and Tmobile I can do whatever device I want with the SIM. No activation or website to register the gear at. They validate via the SIM only but Verizon SIM ties to the device somehow. You can buy the Verizon MC7750 pretty cheap because they make it so hard to register it. Verizon does have the fastest service in my area, but I digress.

    GPS is available and with AT commands you can either share antenna lead2(nice on laptops) or use the built in GPS antenna connector.
    As for timeserver I am not sure it meets those standards. Don't most stratum timeservers use PPS?
    I guess it depends on the accuracy you desire.



  • I never used the Verizon network so I am unsure how it works with pfSense. I used Linux and its modem_manager. I worry they might use QMI only if I remember the MC7750 correctly.

    Instead of buying an MC7700 why don't you crack open that Cradlepoint mbr600 and check the modem? I know the mbr1200 uses MC7700. Do some homework or take it apart. Might save you some money.



  • Currently using an APu2 from pcengines.  Per your recommendation I purchased an unlocked MC7700.  tmobile and ATT will work for most of the locations so I will start with those carriers.  Possibly even Google fi.

    The only part things get blurry with is the processes to get the adapter ready for pfsense.  Most of the directions are pretty vague and since I am not familiar with Linux or BSD interaction i am a bit hesitant.

    I use Windows but can deploy a virtual linux machine.  Also purchased a USB to PCIe with SIM to test with.

    Not sure if you are available but if the process is pretty routing I could pay you to do a remote walk-through so I could record the process for future deployments.

    Just purchased the cradlepoint.  at $499.99 I am hesitant to mess with it.  Also I had to put into production today so it will be a while before I can get it back.

    I really like the idea of using pfsense because of the option to use squid (Transparent Proxy) and NTP Server (Cradlepoint does not have this though their central management solution is amazing!



  • MC7700 is pretty straight forward and I will help with any problem. Look for the newest firmware and flash it. You need windows for the flasher. The DIP mode firmware is what you want.
    https://source.sierrawireless.com/resources/airprime/software/mc7700-att-approved-firmware-swi9200x_03,-d-,05,-d-,29,-d-,03_dip/

    After applying this you can use it with pfSense. cuaU0.3 is the port for ppp.



  • Great thank you!

    received usb mpcie adapter.  waiting for MC7700 from china :-( long boat ride!



  • Got the card.  But dont know where to find the flasher software to use on windows.  I do a random search and come up with many options.



  • sierra wireless' website has firmware.



  • Downloaded the firmware

    https://source.sierrawireless.com/resources/airprime/software/mc7700-att-approved-firmware-swi9200x_03,-d-,05,-d-,29,-d-,03_dip/

    Downloaded the watcher

    https://source.sierrawireless.com/resources/airprime/development_kits/airprime-mc-series-connection-manager-dip-build-3830/

    Downloaded Drivers

    https://source.sierrawireless.com/resources/airprime/software/airprime-mc-series-windows-drivers-dip-build-3795/

    Initialization failure

    Card shows up during boot of pfsense and also shows as WWAN modem in windows.  Just not sure how to apply the DIP firmware.

    ugen1.3: <sierra wireless,="" incorporated="">at usbus1
    ada0 at ahcich0 bus 0 scbus0 target 0 lun 0
    ada0: <ts32gmsa370 n1126kb="">ACS-2 ATA SATA 3.x device
    ada0: Serial Number D544021971
    ada0: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 1024bytes)
    ada0: Command Queueing enabled
    ada0: 30533MB (62533296 512 byte sectors)
    ada0: Previously was known as ad4




    </ts32gmsa370></sierra>



  • Do I need windows 7?  I am using windows 10.



  • im not at home right now so can't check but I used windows 10 and was able to just select the card and update the firmware.
    If its not a sierra wireless device, you will likely need to convert the device to a sierra OEM model Id before you can flash it. The huwaii modem tool is needed for this.



  • See attached photos






  • What I would do at this point is slip it in a FreeBSD box or pfSense and use the terminal program to determine the current firmware and mode. Here is where I would start.

    
    root@E6420:~ # cu -l /dev/cuaU0.3
    Connected
    at
    OK
    atz
    OK
    ati
    Manufacturer: Sierra Wireless, Incorporated
    Model: MC7700
    Revision: SWI9200X_03.05.29.03ap r6485 CNSHZ-ED-XP0031 2014/12/02 17:53:15
    IMEI: 012626000778678
    IMEI SV: 23
    FSN: CDC0183099710
    3GPP Release 8
    +GCAP: +CGSM,+DS,+ES
    
    OK
    at!udinfo?
    VID: 0x1199
    PID: 0x68A3
    Interface: DIP
    Manufacturer: Sierra Wireless, Incorporated
    Product: MC7700
    
    OK
    
    

    So from ATI and AT!UDINFO? you can glean the firmware and Interface. From there you will plot a strategy.
    You may need to use Win7 and the QMI drivers  to flash it. Then switch it to DIP. Depends on the above terminal info. Post yours please.



  • Do I need to execute another command to get to the # prompt?

    [2.3.3-RELEASE][root@pfSense.localdomain]/root: cu -l /dev/cuaU0.3
    /dev/cuaU0.3: No such file or directory
    link down



  • Do you have any recent Ubuntu or Mint memsticks around. I would check that next to see what it is doing. ModemManager can deal with most any device. The best way to do this is use Ubuntu/Mint with persistant storage from unetbootin for image burning to USB stick.
    That way you can install some tools you might need. ModemManager GUI is the first piece of software I would install there. You might also need putty or your preferred Linux terminal program to talk to the modem.

    I would make sure there is a SIM installed as well. Try connecting via NetworkManager by making a Mobile Broadband connection profile with your APN. The reason we are doing this is the IMEI number might be flagged if the last owner is in arrears. That and your module is using a different IMEI prefix than is usually used on MC7700. Notice mine starts with 0126. That is pretty standard from what I see online.



  • 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



  • 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.



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



  • 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.



  • 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> 
    


  • 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



  • 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!




  • 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.



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



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




  • 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?



  • 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
    


  • 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
    


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



  • 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/





  • 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.



  • 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.



  • 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.



  • @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?



  • @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.

    The Cradlepoint IBR650-LP4 that I am using has a MC7700 and I am using with tmobile with ATT firmware and it has no problem with 4G or LTE speeds.

    http://www.comm2m.fr/images/produits/docs/Cradlepoint/CradlePoint_COR_IBR6x0__DataSheet_comM2M.pdf

    I ordered the wrong was do to a miscommunication that the IBR650 was Tmobile certified but it only has firmware for ATT and Verizon but we have had it in use for more than 2 weeks using tmobile sim and no issues.  Cradlepoint support said it would work.



  • Should be receiving my antenna's today for LTE.  Have yet to order GPS Antenna.

    Question with regards to GPS.  I am not concerned about millisecond accuracy.  I am concerned with accuracy in the 30 second to 1 minute range.  I have fixtures with no real time clock and their programming needs to know what time it is.  If power goes out and internet does not come back I need to make sure they get accurate time but not millisecond timing.


Log in to reply