Data Connection

Because LTE Cat M1 is designed for low-bandwidth, low-power telemetry, routing the entire Raspberry Pi operating system to the internet via connection like PPP, ECM, QMI can result in unwanted background data consumption (OS updates, NTP syncs) that depletes your SIM data allowance. We offer two ways to send data, depending on your application's needs.

Path A: The LPWAN Way (Direct Modem IP Stack)

Best for: Strict data caps, battery-powered systems, and pure telemetry.

In this method, the Raspberry Pi OS remains completely offline. Instead of using standard Python requests or socket libraries, your application sends payload data directly to the Telit module via USB using AT commands. The Telit ME910C1-WW has a built-in TCP/IP stack and embedded clients for MQTT, HTTP, and UDP.

How it works: You send AT commands, and the modem handles the TCP handshake, payload delivery, and teardown internally.

The Benefit: Zero background OS data leaks. 100% of your cellular bandwidth is dedicated strictly to the application payload.

Guide: Refer to Section 3.13 for TCP/UDP, Section 3.16 for HTTP and Section 3.22 for MQTT of the Telit module's AT Command guide

Path B: The Standard Linux Way (PPP)

Best for: Edge-computing applications, remote SSH access, or developers who want to use standard Python/Node.js networking libraries.

In this method, you use Point-to-Point Protocol (PPP) to create a standard network interface (e.g., ppp0). Your can use standard libraries (like Python's paho-mqtt or requests), and the OS handles the routing.

How it works: You configure a Linux PPP daemon to keep the connection alive, bridging the modem to the OS kernel.

The Benefit: Faster software development time since you don't have to write AT command parsers in your code.

The Warning: Raspberry Pi OS and other installed packages may consume CAT M1 bandwidth

Guide: Establishing a PPP Connection