Choose between LTE Cat-1 bis and 5G RedCap from the data your product must send, the networks it will use and the work needed to integrate the module. For small telemetry uploads, start by checking whether Cat-1 bis meets the update window. For larger transfers, compare a documented RedCap module and its fallback path.
Compare quotations for the full part number at the same quantity, with the required firmware, features and delivery terms. Put antenna, power, software and approval work beside the module price in the BOM review.
The decision below uses LTE Cat-1 bis as a category and Quectel’s RG255C LGA series as a concrete RedCap example. Start with throughput and network requirements, then check the selected variant against the board and deployment.
The short refresher
LTE Cat-1 bis uses a single cellular receive-antenna path and has category maxima of 10 Mbps downlink and 5 Mbps uplink. Check the module’s regional bands, operator acceptance, SIM and roaming arrangements for each market. See 5G for IoT: the basics for the wider network context.
RedCap is part of 3GPP Release 17. Quectel lists the RG255C LGA series with theoretical peak rates of 223 Mbps downlink and 123 Mbps uplink, 5G Sub-6 SA and LTE Cat 4 support. Use the regional variant’s band list and operator deployment information to assess that option. Our 5G RedCap Explained article covers the technology background.
The comparison
| Selection point | LTE Cat-1 bis | RG255C LGA RedCap example |
|---|---|---|
| Data-rate reference | Category maxima: 10 Mbps DL / 5 Mbps UL | Manufacturer theoretical peaks: 223 Mbps DL / 123 Mbps UL |
| Network path | 4G LTE; check bands, operator and roaming | 5G Sub-6 SA with LTE Cat 4 support; check the regional variant and operator |
| Antenna planning | Single cellular receive path; check other RF functions separately | Use the selected variant’s RF-port and antenna requirements |
| Transfer test | Check payload and firmware-upload time on the target LTE network | Check those transfers on intended SA service and on LTE fallback |
| Power and cost | Measure the reporting cycle; quote the exact configuration | Measure the same cycle and fallback use; include integration work in the comparison |
Use the peak rates to screen candidates, then measure upload and download times with the payload, SIM and network planned for the product. Record the acceptable update window before deciding that a higher radio category adds value.
When Cat-1 bis meets the product requirements
Start with Cat-1 bis when the required payload and update window fit the measured LTE throughput. Confirm the target operators, band variants, voice requirements and roaming plan, then test registration and transfers with the intended SIM and firmware.
For a 2G/3G replacement, compare the existing board’s supply, pinout, host interface, RF paths and command handling with the new part. The 2G/3G migration roadmap connects that review with operator retirement dates.
When to evaluate a RedCap module
Evaluate RedCap when larger uploads, multiple connected devices or firmware-update windows exceed what the tested Cat-1 bis connection delivers. Calculate the transfer target from the actual file size and available time; test it on the deployment network. Use the module lifecycle and operator roadmap when planning the product’s service life.
For 5G SA operation, confirm the intended operator’s RedCap support, bands and SIM provisioning. Then check the selected module’s LTE capability and test registration and application recovery when SA service is unavailable. The RG255C LGA product entry provides a starting point for that regional-variant review; the M.2 version is a separate hardware form.
Review a shared-board option
If two modules are proposed for one board, compare their hardware guides pin by pin. Record supply limits and transients, logic levels, USB or other host interfaces, RF ports, layout keep-outs, thermal requirements and firmware changes. Use the compatibility matrix to decide which changes the board needs.
Request the manufacturer’s compatibility notes and lifecycle information for both full part numbers. Link the comparison to the board revision and firmware build being evaluated, so the hardware and software teams work from the same configuration.
The cost nobody puts in the spreadsheet
Estimate the antenna work, supply and thermal design, host software changes, integration tests and applicable product approvals alongside the module quotation. Power draw depends on the chosen hardware and operating cycle: measure registration, transmission, receive windows and sleep under comparable conditions.
For a battery product, record energy per reporting cycle and the required downlink delay. The PSM and eDRX guide helps define that timing; the power-supply checklist helps plan transient measurements at the load.
The questions to ask before you commit
- Which full part number, regional bands, hardware form and firmware are quoted?
- Which operators and SIM arrangements support the planned LTE or RedCap service?
- How does the application recover when the preferred network is unavailable?
- What antenna, supply, thermal and host-software changes are needed?
- Which approval documents cover the selected module, and what work remains for the finished product?
- What are the price, lifecycle status and delivery terms at the required quantity?
The short version
Choose the module that meets the measured payload and update window on the intended networks, fits the power budget and has an acceptable integration plan. Cat-1 bis can meet telemetry needs; a documented RedCap option is worth comparing when transfer requirements justify it. Keep the tested network and fallback configurations in the selection record.
Send the candidate part numbers, destination operators, data and update requirements, host interface, power budget and quantity. We can use those inputs to prepare a module comparison and quotation. Browse supporting documents in the Datasheet Center.