> For the complete documentation index, see [llms.txt](https://docs.didge.io/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.didge.io/home/foodcore-sensors/technical/hardware-specs/multitech-gateways/specifications.md).

# Specifications

## 📘 MultiTech MTCAP-LAP3-915-001 – Technical Documentation

### 1. 🔍 Model Overview

The **MultiConnect® Conduit™ AP MTCAP-LAP3-915-001** is an indoor LoRaWAN® Access Point designed for private LoRaWAN networks. It supports LTE connectivity with SIM card integration, enabling reliable backhaul for gateway-to-cloud communication.

<figure><img src="https://2675140142-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPnSdrHOYeIaTHbt8Z0Qc%2Fuploads%2FTGHvNB1qmTsp0boAck8R%2Fimages%20(6).jpeg?alt=media&amp;token=a851ec3a-49b5-40b2-8b1a-73fa9b041c57" alt=""><figcaption></figcaption></figure>

***

### 2. ⚙️ Technical Specifications

| Feature                   | Specification                           |
| ------------------------- | --------------------------------------- |
| **Model**                 | MTCAP-LAP3-915-001                      |
| **Processor**             | ARM926EJ-S                              |
| **Memory**                | 256 MB RAM, 256 MB Flash                |
| **Cellular**              | LTE Cat 4 (with micro SIM card support) |
| **LoRaWAN Compatibility** | LoRaWAN 1.0.2                           |
| **Frequency Band**        | 915 MHz (North America)                 |
| **Backhaul Connectivity** | LTE and Ethernet                        |
| **Power Supply**          | 5V DC (via supplied AC adapter)         |
| **Antenna Connections**   | SMA connectors (LoRa and LTE)           |
| **Operating Temperature** | 0°C to +70°C                            |
| **Certifications**        | FCC, IC, Carrier Pre-Certified          |

***

### 3. 📦 Included Hardware

* MTCAP-LAP3 gateway unit
* LTE antenna (SMA)
* LoRa antenna (SMA)
* Micro SIM slot
* Power adapter (5V DC)
* Mounting hardware (optional)

***

### 4. 🔧 Setup Instructions

#### SIM Card Installation

* Ensure power is OFF.
* Insert a **micro (3FF) SIM card** into the SIM slot.
* Power on the device to enable cellular backhaul.

#### Connecting Antennas

* Attach **LoRa antenna** to the LoRa SMA port.
* Attach **LTE antenna** to the Cellular SMA port.

#### Ethernet and Power

* Connect to Ethernet if required (RJ45 port).
* Power using the 5V adapter.

***

### 5. 🖥️ Configuration and Management

#### Web UI Access (mPower firmware)

1. Connect to the device via Ethernet.
2. Navigate to: `http://192.168.2.1`
3. Login with default credentials (admin/admin) or your assigned credentials.
4. Configure:
   * LoRaWAN packet forwarder
   * Network (LTE/Ethernet fallback)
   * System time and diagnostics

***

### 6. 📑 Documentation & Resources

* 📘 **User Guide (PDF)**:\
  [MTCAP-LAP3 User Manual](https://multitech.com/wp-content/uploads/S000771_MTCAP-LAP3-001.pdf)
* 🛠️ **Developer Portal**:\
  [MultiTech Developer Hub – MTCAP](https://www.multitech.net/developer/products/multiconnect-conduit-access-point/)
* ⚙️ **mPower Software Configuration Guide**:\
  mPower Manual (PDF)

***

### 7. 📬 Support

* **MultiTech Support Center**: support.multitech.com
* **Email**: <support@multitech.com>
* **Warranty Info**: Warranty Policy

***


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.didge.io/home/foodcore-sensors/technical/hardware-specs/multitech-gateways/specifications.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.