4G/3G/2G/GSM/GPRS/GNSS HAT, Compatible with Raspberry Pi 5/4B/3B/Zero/Zero W/Zero 2W/Pico/Pico W/Pico WH, LTE Cat-4 4G / 3G / 2G Support, GNSS Positioning, Global Band

I bought this to use it for an in-car mobile WiFi hotspot, do I need the 4g connectivity. At first it did not connect no matter what I did, I thought it could be a carrier issue? My SIM is on Simple Mobile btw. after a ton of trial and error, I was able to get it working by executing "route add -net 0.0.0.0 usb0". While it did not show it was connected through the UI, I was able to browse and load content. Apparently it's an issue with the network manager on the bookworm based Debian 12 version of Raspbian OS, after switching to the legacy (Debian 11) version of the OS, it seems to work with no issues. So the only things you need to do in order to set it up for 4g Internet is: -download minicom "sudo apt-get install minicom" -make sure Host device is off, insert sim, plug into GPIO headers, plug Device in from the USB (not USB to uart) port to a USB port on the Host device. - start Host device, if the 4g light does not start blinking or turn on, you may need to manually switch the modem on, press and hold the power button for about 5 seconds to turn on manually. -Open terminal, type "minicom -D /dev/ttyUSB2" to connect to the Device. When in minicom, press Ctrl+a then press "e". This turns on echo mode so you can see what you're typing. -Input the command "AT+CUSBPIDSWITCH=9011,1,1", you may need to copy and paste it into the terminal because sometimes it'll be outputting signal commands and interrupt you while you're typing. Also, this command ensures the Linux driver is loaded, if you need this for Windows, you need to change the 9011 to 9001. -set your apn by inputting the command "AT+CGDCONT=1,"IP","wholesale", replace wholesale with whatever your apn for your carrier is. -you should be connected, if not try "route add -net 0.0.0.0 usb0", you'll need to add that to your startup script if that fixes connectivity. If anything gets messed up, you need to dig in and fix it because, as far as I could find, there's no factory reset command. I do recommend you have a little AI assistant ready to help, Gemini was a huge help in me gaining an understanding of the whole serial communication part and diagnosing the connection issues. The online documentation is super helpful and there's a handful of AT commands to help you diagnose if you have any issues. Just search "waveshare 7600" and go to the product page from their website and there's a wiki link toward the very end of the page that leads to the documentation.

I was actually hoping to make my own Raspberry Pi 4 powered cell phone using this product. At first everything seemed great. Ubuntu has the kernel modules already included for this and it was detected right away and I was able to configure the internet connection right in the Ubuntu settings application. Sending AT Commands to do all actions (SMS and Phone Calls) works great as well. However, when trying to do everything at once I run into issues ALL the time. It is not just a AT Commands multiplexing issuing either. The device will get into a bad state where all of a sudden nothing works and requires I fully shutdown the Pi and short the HAT to get it to clear any state. Then when I bring everything back up everything will work for a while again. It is just too bad it can't be reliable enough to make a day to day use cell phone with. Customer support was actually quick to respond although their answer was not all that helpful. I still really appreciated the effort, especially with the quality of my question/message I sent. Maybe they will have some recommendations for how to fix this? I am considering ditching the project altogether or trying SixFab's LTE-M board instead.

You can buy all the electronics from this company they don’t give you any examples and leave you high and dry when it comes to putting any of these electrics to actual purposeful use. This is the 2nd device I bought from waveshare completely different from the last. Both projects ended in the ditch as waveshare only provides drivers. Waveshare does NOT have any tutorials on how to use their devices only to show them working in a non realistic scenario. You’d think a gps module would come with instructions to run with GPSD in NMEA universal coordinates but NOPE. They give you a software that outputs Chinese. Don’t buy ANYTHING waveshare!

This device works fine with Google Fi on a Raspberry Pi 5 using the stock RNDIS host driver. Three important notes: 1) With most RPi5 Heatsinks you will need a riser for the 40 Pin GPIO connector. Here is the one I used https://www.amazon.com/dp/B08C2DJBT2?ref=ppx_yo2ov_dt_b_fed_asin_title 2) Google Fi you will need an adaptor for the SIM card, here is the one I used: https://www.amazon.com/dp/B00M9P5RXO?ref=ppx_yo2ov_dt_b_fed_asin_title&th=1 3) VERY IMPORTANT !!!! Be sure to use the USB port opposite of the GPIO on the Modem Marked as USB, not the one marked USB to UART. See Photo! 4) Below are the commands to issue to the RPi5 to make it work! sudo mmcli -L # Verify ModemManager detection # Blacklist conflicting drivers echo "blacklist cdc_ether" | sudo tee /etc/modprobe.d/blacklist-cdc.conf echo "blacklist option" | sudo tee -a /etc/modprobe.d/blacklist-cdc.conf # Load cellular modules sudo modprobe qmi_wwan sudo modprobe usb_serial sudo modprobe usb_wwan # Persist across reboots echo "qmi_wwan" | sudo tee /etc/modules-load.d/cellular.conf sudo update-initramfs -u reboot

Works perfectly for it’s intended purpose. Read the manual and had no trouble getting it online. Just bought a SIM card and activated service on Mint mobile (t-mobile). It rides along in my Tesla on a raspberry pi and supplements connectivity. Only wished it had longer ipx connectors so I could get the antennas in a better position. An easy fix with a secondary purchase.

I was able to get this working with the Pi ModemManager daemon, which is the most convenient way and requires no startup scripts. You do have to initialize the HAT with AT commands first as others have posted. I was having trouble with the device at first, it would mysteriously stop working after an hour or so and would work again only after rebooting the Pi. Out of frustration I asked an AI and it made a key suggestion that provided the fix; "USB Power Management / Suspend The Pi may put USB devices to sleep to save power, causing the modem to "disappear." Disabling USB autosuspend can often resolve this: Add usbcore.autosuspend=-1 to your /boot/cmdline.txt. Ensure it is on the same line as the other kernel parameters (space‑separated). " Also be careful with the SIM card holder. You have to push it sideways to unlock it and lift the clamp. Then when the card is in place you can push the clamp down on the card and lock it in place by pushing sideways in the other direction. Once the SIM7600 is detected by ModemManager (e.g., sudo mmcli -L shows something like /org/freedesktop/ModemManager1/Modem/0 [QUALCOMM INCORPORATED] SIMCOM_SIM7600G-H), you can manage it as follows. Get modem details sudo mmcli -m 0 This shows modem status, SIM info, signal strength, and network details. Check SIM status sudo mmcli -m 0 --command='AT+CPIN?' Verifies whether the SIM is ready or PIN‑locked. Create a GSM connection (via NetworkManager) with your APN # Replace the APN value; example APN shown is 'super' sudo nmcli connection add type gsm ifname '*' con-name myconnection apn super Enable and connect the modem sudo mmcli -m 0 --enable Monitor status (watch for state changes) sudo mmcli -m 0 -w The ifconfig command should show you a wwan0 interface if things are working properly. Then you should be able to; ping -I wwan0 google.com

I've been developing a private, self-hosted replacement for Google Voice running on a Raspberry Pi and after porting out my GV number to a real cellular provider, the SIM7600X was meant to be the link between my software and the cellular network. This device is generally a pretty nice unit and I've been able to wrench at it to get it to do MOST of the things that I need it to do, however there are some serious limitations which are so problematic that it pretty much makes it unsuitable for my (and I imagine many other people's) needs. Pros: - Clean and compact hardware package. Fits nicely atop a Raspberry Pi, which you'd expect from any well-designed hat. - Easy and fast software integration. Even on Linux, getting the device going is a pretty straightforward matter of downloading the package, decompressing it, then building and installing the software. Once you get the kernel module loaded everything works as it should. - Stable hardware and solid cellular connection. I've found that once it's up, it's up. I've had no problems with any random disconnects or other hardware weirdness which interrupt the operation of the unit. I can start it up, leave it be, then come back to it a week or two later to find everything is still working as it should. - Extensive documentation. The manufacturer covers a lot of stuff in the docs which is very helpful for many of the tasks you'll want to do with this device. - Responsive support. I've been able to fire off questions to the manufacturer, and without fail they've gotten back to me within just a few days - often with very helpful and detailed instructions. Cons: - UNACCEPTABLE: No native MMS support. It's 2025, folks. MMS is a pretty basic function, and the lack of support here is shocking. I understand that MMS and SMS are largely being superseded by RCS, however MMS and SMS are still important as a fallback technology. MMS and SMS are also important simply for providing support for communicating with older devices. (I am waiting to hear back from the manufacturer on the device's support for RCS, though I expect to be disappointed yet again.) - UNACCEPTABLE: No multi-party call support. Not as shocking as the lack of MMS support, but this is still really bad. Being on a call with someone and then conferencing in a third party is pretty common. My software architecture was originally designed where the server would place a call to my phone, wait for a connection, then place a second call to the desired number and immediately conference the two external calls together. This is simple functionality which is not possible with this device. - Simultaneous internet and modem operation doesn't work. I found that once you've established a connection to the internet through this device, pretty much anything you'd otherwise be doing with it stops working. Even incoming SMS messages aren't seen by the device while the internet connection is active, with all of the messages queuing up at the cellular provider. Only after disconnecting from the internet do the queued messages make it through, arriving in one big dump. Now to be fair I haven't explored this particular problem in great detail so this is potentially a workable issue, but I haven't had any success developing a workaround yet. - Gaps in the documentation. While there is a wealth of good info in the available documentation, there are a lot of functions that are either not covered at all or aren't clearly and/or fully explained. For example, in the previous bullet point I mentioned connecting to the internet. The AT command to activate the internet connection (AT+CUSBPIDSWITCH=9011,1,1) works as expected, but since that kills most of the other functionality of the unit, I needed to terminate the connection to get things back to where I needed them to be. I struggled for a really long time trying to find the proper AT sequence to kill the internet connection without doing a full hardware reset. Bringing the network interface down didn't work. Even power-cycling the device didn't suffice, as it simply re-established the internet connection on startup. I discovered pretty much by accident that the aforementioned AT command actually performs a toggle within the modem's internal configuration, so the same command to connect can also be used to disconnect. I'm glad I figured it out, but it's something that this isn't covered in the documentation anywhere that I could find. Overall I would rate this device as "okay" and I'm still working with it as best I'm able. For anyone else, unless you are looking for something genuinely bare-bones, I can't recommend it.

I was able to use it to access the internet and receive calls so far, after a lot of searching and googling I came across a guide to setup a different module but it worked for waveshare module, google "mPCIe Modem QMI Interface Internet Connection Setup #2" and open the "embeddedpi" website, I connected the module to the raspberry pi 4 using both the gpio "gpio is needed for the AT commands" and the usb the one that says "usb" NOT the "usb to uart", when communicating with the module using minicom I used the /dev/ttyUSB3, I think this module uses ttyUSB2 and ttyUSB3 for the AT commands. BTW the signal strength was pretty good -60s to -70s dbm in the United States.