Quectel is a leading supplier of wireless communication modules and antennas. Full stop.
If you're in the IoT or embedded systems space, you've seen the name. But the real question—especially if you're sourcing components for a commercial project—isn't just what they offer. It's which of their products actually fit your specific application, and where the common pitfalls hide. I've been handling module procurement for 4+ years, and I've personally made (and documented) about 15 significant mistakes. Roughly $12,000 in wasted budget. I now maintain our team's sourcing checklist.
Here's the condensed version of what I've learned, starting with the most important bit.
What Does Quectel Offer? (The Fast, Honest List)
They have one of the broadest portfolios in the industry. You can find a module for damn near any cellular or GNSS application. Their catalog spans these general categories:
- 5G Sub-6 GHz & mmWave modules: High throughput for routers, gateways, industrial PCs.
- 4G LTE (Cat 4, Cat 6, Cat 12, Cat M1/NB2): The bread and butter for most IoT projects. Think asset trackers, telematics, smart meters.
- LTE Standard (Cat 1, Cat 1 bis): Cost-optimized for voice and medium-speed data.
- NB-IoT and LTE-M modules: For low-power, low-data-rate applications like smart city sensors.
- GNSS modules: GPS, GLONASS, BeiDou, Galileo, QZSS receivers. Standalone and combined.
- Antennas: A huge selection covering all the above bands, plus combo antennas.
The thing is, the portfolio is so wide that the wrong module can look like the right one on paper. That's where the mistakes happen.
The L80-R: My Favorite Example of a 'Good' Module Gone Wrong (Rookie Mistake)
In my first year (2021), I made a classic error with the Quectel L80-R.
The L80-R is a fantastic ultra-compact GPS module. It's 10.1 x 9.7 mm, low power, and supports concurrent GPS and GLONASS. Perfect for a portable tracker we were building. Specs fit. Price was right. I ordered 500 of them for a prototype run.
The problem? I didn't check the interface.
The L80-R has a UART interface. I just connected it to our MCU's UART pins, wrote the driver, tested it on a breadboard. It worked. I was smug. We sent the order. When the production boards came back, 50% failed in field testing.
The issue: the L80-R outputs at 1.8V logic. Our MCU was a 3.3V device. The L80-R datasheet clearly states this. I skipped that line. The voltage mismatch caused intermittent communication failures, especially in cold temperatures. We had to spin a new board with a level shifter, re-validate, and re-order. That mistake cost $600 in redo plus a 2-week delay.
Lesson: For the L80-R (and most Quectel GNSS modules), you absolutely need to verify the I/O voltage and interface type against your host processor. Don't assume UART is just UART.
How to Use a Multimeter with Quectel Modules (It's Not a Joke)
This sounds like a beginner question, but I've seen experienced engineers get this wrong. When you're testing a module on a new board, you're not testing the module's functionality. You're testing your power supply and connections.
Here's the procedure we now use for every first power-on:
- Continuity test BEFORE power. Check that VBAT, GND, and VDD_EXT are not shorted. This catches solder bridges. (I once wasted a day chasing a ghost fault; it was a bridge on a 0.5mm pitch LGA package.)
- Power supply voltage at the module pins. Set your multimeter to DC voltage. Measure across Pin 1 (VBAT) and the nearest GND pin. You need 3.3V to 4.2V, ideally 3.8V. Anything below 3.2V and the module will not register on the network.
- Check VDD_EXT. This is the module's internal 1.8V output (for the L76K, L80-R, etc.). If this pin is at 0V, the module isn't booting. (Note to self: check this first before blaming the firmware.)
- Check the PWRKEY pin. With the module powered, PWRKEY should be high (1.8V). Pull it low to GND for at least 100ms to turn the module on. Measure the voltage drop. If it doesn't go low, your transistor or button circuit is wrong.
That's it. It's simple. The mistake I see people make is testing at the power supply output instead of the module pin. A 0.1V drop across a thin trace is enough to cause a no-boot condition. Measure at the destination.
How to Use a Blood Pressure Monitor (Yes, Really)
This might seem disconnected, but stay with me. Quectel modules are used in remote patient monitoring devices, including blood pressure cuffs. The engineering challenge isn't the BP sensor—it's the wireless transmission.
A good BP monitor uses an MCU to read the pressure sensor, then sends the data via a Quectel NB-IoT module (like the BC95 or BC66) to a cloud platform. The common failure point? The power management.
The NB-IoT modules draw bursts of current (up to 200mA) during transmission. The small, coin-cell-powered MCU can't supply that. We had a prototype where the BP reading was accurate, but the data never reached the server. The module was browning out during the uplink burst.
Solution: You need a supercapacitor or a small lithium battery to supply the peak current to the module. The MCU wakes up, collects data, then the module transmits using the stored energy. The module's VDD_EXT can even wake the MCU. It's a classic nesting doll problem.
So, if you're designing a BP monitor with a Quectel module, think in terms of power architecture first. The sensor and the algorithm are secondary to the power system.
When NOT to Use a Quectel Module (Honest Limitations)
I recommend Quectel for 80% of projects. But not all.
Avoid them if:
- You need a module with a specific, hard-to-find form factor that only another vendor provides. Example: Certain miniature, pin-compatible modules for existing designs.
- Your application requires an RTOS like Zephyr with a pre-built driver framework. Quectel's primary ecosystem is Linux and Android. They support RTOS, but the drivers are often less mature.
- You need immediate, local engineering support in a time zone where Quectel's presence is weak. Their FAE is good, but response time varies by region. A large SIMCom or Telit distributor might have faster on-the-ground support.
But if you need a broad portfolio, industrial reliability, and good documentation (once you know where to look), they're a solid choice.
Total Cost of Ownership (TCO) Reality
The cost isn't just the module price (pricing accessed January 2025). It's the development time, the compliance testing, and the antenna matching.
I compared two projects: one using a generic Chinese module and one using a Quectel BC66. The generic module was $2.50 cheaper per unit. But it required 3 extra weeks of development to get CE certification passed (the generic module's internal design was different than the reference design). The Quectel module passed on the first submission because we could use their CE test report. The $2.50 savings? Wiped out by the delay and rework.
Total cost of ownership includes module price + engineering hours + certification risk. Quectel's value is lower risk, not always lower price.
The Final Checklist
If you're about to order a Quectel module, especially something like the L80-R or an NB-IoT module, do this:
- Read the interface section (not just the specs) of the datasheet.
- Check the I/O voltage on every pin you plan to use. Get a level shifter if mismatched.
- Design a power system that handles peak current. Add a capacitor or a battery, especially for cellular modules.
- Use their reference design for antenna layout. Changing the antenna footprint introduces impedance mismatches and fails radiation tests.
I've made every one of these mistakes. You don't have to. The cost of learning from my errors: $12,000. The cost of learning from yours: less, if you use this guide.
