> For the complete documentation index, see [llms.txt](https://docs.gxc.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gxc.io/hw/lte/4g-mesh-nodes/gm02/gm02-specification-sheet.md).

# GM02 Specification Sheet

Last Update: 2025-05-07

<h4 align="center">GM02 Mesh Node</h4>

<figure><img src="https://4084968256-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgSxa0NIdBp5aDw7Lf2N9%2Fuploads%2FSVKzQF7XZYoTrlfTNLsG%2Fimage1.png?alt=media&amp;token=1aa822c0-f58c-43bc-b52d-abb2f57d0250" alt=""><figcaption></figcaption></figure>

The GXC GM02 Mesh Node enables a G101 or G501 Access Point to wirelessly connect to the GXC ONYX Gateway Node. This is accomplished using self-interference mitigation techniques, allowing access and backhaul carriers to co-exist in CBRS Band 48. Together with GXC's ONYX Platform for orchestration, management, and SAS registration, the GM02 provides coverage extension and rapid deployment in areas where wired infrastructure is unavailable. &#x20;

### Backhaul

<table><thead><tr><th width="250">Parameter</th><th>Specification</th></tr></thead><tbody><tr><td>Band Support</td><td>Band 48 CBRS (5G Ready)</td></tr><tr><td>Radio Technology</td><td>LTE: CAT12, up to 2CA DL/UL, 2 x 20 MHz</td></tr><tr><td>Antenna Configuration</td><td>1T2R LTE, 2T2R 5G (future)</td></tr><tr><td>Antenna Connector</td><td>2 x Type N connectors</td></tr><tr><td>TX Power</td><td>20 dBm conducted, max 35.2 EIRP, CATB CPE-CBSD</td></tr><tr><td>RX Sensitivity</td><td>-96 dBm per 10 MHz carrier</td></tr><tr><td>Insertion Loss (Filter)</td><td>2.6 dB (typical)</td></tr><tr><td>SIM Support</td><td>Dual-SIM, 2FF, external access</td></tr></tbody></table>

### Hardware Specifications

<table><thead><tr><th width="250">Parameter</th><th>Specification</th></tr></thead><tbody><tr><td>Band of Operation</td><td>Band 48 CBRS</td></tr><tr><td>Antenna Configuration</td><td>2T2R</td></tr><tr><td>Antenna Connectors</td><td>AP Input: 2 x Type N connectors<br>AP Antenna: 2 x Type N connectors</td></tr><tr><td>Max AP Input Power</td><td>33 dBm per port</td></tr><tr><td>Antenna Isolation</td><td>Backhaul Access: 45 dB (minimum)</td></tr><tr><td>Insertion Loss (AP Interface)</td><td>2.6 dB (typical)</td></tr></tbody></table>

<table><thead><tr><th width="250">Parameter</th><th>Specification</th></tr></thead><tbody><tr><td>Power: Nominal Vin</td><td>48 VDC</td></tr><tr><td>Input Voltage Range</td><td>36 V to 60 V</td></tr><tr><td>Isolation</td><td>Input to Field-GND: 2.5 kVDC</td></tr><tr><td>Power Consumption</td><td>20 W (maximum)</td></tr><tr><td>AP Data Interface</td><td>RJ45 1 GbE IEEE-802.3ab, non-PoE</td></tr><tr><td>Wireless Diagnostic Interface</td><td>Wi-Fi diagnostic AP, 2.4 GHz</td></tr><tr><td>Installation</td><td>Pole or Wall Mount *</td></tr><tr><td>Dimensions</td><td>13.9 x 9.7 x 5.3 in</td></tr><tr><td>Weight</td><td>18.75 lb (8.505 kg)</td></tr></tbody></table>

### Environmental Specifications

| Parameter                      | Specification                                                                                                                                             |
| ------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Operating Temperature          | -40°C to +55°C                                                                                                                                            |
| Storage Temperature            | -45°C to +85°C                                                                                                                                            |
| Humidity                       | 5% to 95% RH                                                                                                                                              |
| Atmospheric Pressure           | 751 to 1014 mbar (sea level to 2000 meters altitude)                                                                                                      |
| Water / Dust Ingress           | IP66                                                                                                                                                      |
| Operational Vibration (Random) | <p>+12 dB/octave from 5 to 10 Hz,<br>0.04 m2/s3 from 10 to 50 Hz,<br>-12 dB/octave from 50 to 100 Hz,<br>3 axes x 30 minutes, per IEC 60068-2-64 (Fh)</p> |
| Operational Shock              | 100 half-sine pulses at 50m/s2 with 11 ms duration each of 6 directions, per IEC 60068-2-27 (Ea)                                                          |
| Salt-Fog Corrosion             | 240 hours at 35°C, 5% NaCl salt mist per IEC 60068-2-11 (Ka)                                                                                              |
| Certifications                 | FCC ID 2AZH6GXCMEN002                                                                                                                                     |

### Global Part Numbers

| Part Number | Description    |
| ----------- | -------------- |
| GXC-MEN-002 | GM02 Mesh Node |

* The GXC GM02 is designed to operate in conjunction with a G101 or G501 Access Point, which is required for the GM02 to function. Specifications and ID are subject to change without notice.


---

# 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.gxc.io/hw/lte/4g-mesh-nodes/gm02/gm02-specification-sheet.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.