> For the complete documentation index, see [llms.txt](https://www.multi-module.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.multi-module.org/using-the-module/protocol-details/m-link.md).

# M-LINK

## Details

**Protocol Number:**  78\
**Autobind:**  No\
**Channel Re-mapping:**  No\
**Extended Limits:**  Yes\
**Failsafe Support:**  Yes\
**Receiver Match:**  Yes\
**Telemetry:**  Yes\
**Option Value:**  N/A\
**Firmware Version:** v1.3.2.30

## Notes

{% hint style="warning" %}
Failsafe **MUST** be configured once with the desired channel values (hold or no pulses are not supported) while the RX is up (wait 10+ sec for the RX to learn the config) and then failsafe **MUST** be set to RX/Receiver otherwise the servos will jitter.
{% endhint %}

Telemetry: the 2 RXs I have are sending different information in different format

* RX-5: RX\_RSSI=RSSI=sort of RSSI or link quality, RX\_LQI=number of connection lost, TX\_RSSI=RSSI from the TX perspective, TX\_LQI=percentage of received telemetry packets
* RX-9-DR: A1=RX Batt (Ratio=12.7), **RX\_RSSI=TX\_LQI**=percentage of received telemetry packets **from the TX** perspective **not RX**, TX\_RSSI=RSSI from the TX perspective, TX\_LQI=percentage of received telemetry packets

## Channel Assignment

| CH1 | CH2 | CH3 | CH4 | CH5 | CH6 | CH7 | CH8 | CH9 | CH10 | CH11 | CH12 | CH13 | CH14 | CH15 | CH16 |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | ---- | ---- | ---- | ---- | ---- | ---- | ---- |
| CH1 | CH2 | CH3 | CH4 | CH5 | CH6 | CH7 | CH8 | CH9 | CH10 | CH11 | CH12 | CH13 | CH14 | CH15 | CH16 |


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://www.multi-module.org/using-the-module/protocol-details/m-link.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.