> For the complete documentation index, see [llms.txt](https://inacks.gitbook.io/inacks-is3720-i2c-dmx+rdm-receiver-ic/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://inacks.gitbook.io/inacks-is3720-i2c-dmx+rdm-receiver-ic/datasheet/memory-map.md).

# Memory Map

The IS3720 memory map registers are 8 bit wide, and I2C memory addressing requires 2-bytes.

<table><thead><tr><th width="78">Reg</th><th>Register Name</th><th>Register Description</th></tr></thead><tbody><tr><td>0</td><td>-</td><td>Not used.</td></tr><tr><td>1</td><td>DMX_CH1</td><td>DMX Channel 1 value.</td></tr><tr><td>2</td><td>DMX_CH2</td><td>DMX Channel 2 value.</td></tr><tr><td>3</td><td>DMX_CH3</td><td>DMX Channel 3 value.</td></tr><tr><td>...</td><td>...</td><td>DMX Channel 4 to Channel 509 values.</td></tr><tr><td>510</td><td>DMX_CH510</td><td>DMX Channel 510 value.</td></tr><tr><td>511</td><td>DMX_CH511</td><td>DMX Channel 511 value.</td></tr><tr><td>512</td><td>DMX_CH512</td><td>DMX Channel 512 value.</td></tr><tr><td>513</td><td>CHIP_ID</td><td>IS3720 chip identification number (does not change).</td></tr><tr><td>514</td><td>CHIP_REV</td><td>IS3720 chip revision number (may change).</td></tr><tr><td>515</td><td>CHIP_TEMP</td><td>IS3720 chip temperature in ºC (signed value).</td></tr><tr><td>516<br>517</td><td>DMX_START_ADDRESS</td><td>DMX start address of your product.</td></tr><tr><td>518</td><td>IDENTIFY_DEVICE</td><td>Device identification. When set to 1, your product flashes to help lighting technicians locate it.</td></tr><tr><td>519<br>520</td><td>DMX_FOOTPRINT</td><td>Number of DMX channels used by your product.</td></tr><tr><td>521<br>526</td><td>UID</td><td>Unique RDM identifier of your product.</td></tr><tr><td>527<br>528</td><td>CATEGORY</td><td>RDM-coded number classifying your product.<br>See Table 2: RDM Standardized Product Categories.</td></tr><tr><td>529<br>560</td><td>MANUFACTURER_LBL</td><td>32-character ASCII string containing your product company name.</td></tr><tr><td>561<br>562</td><td>MODEL_NUM</td><td>2-byte value identifying your product model.</td></tr><tr><td>563<br>564</td><td>MODEL_LBL</td><td>32-character ASCII string containing your product name.</td></tr><tr><td>565<br>568</td><td>SOFT_NUM</td><td>4-byte value identifying your product software version.</td></tr><tr><td>569<br>630</td><td>SOFT_LBL</td><td>32-character ASCII string representing the firmware name or code of your product.</td></tr><tr><td>631</td><td>RDM_ONLINE</td><td>Enables or disables RDM communication (does not affect DMX) of your product.</td></tr></tbody></table>


---

# 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://inacks.gitbook.io/inacks-is3720-i2c-dmx+rdm-receiver-ic/datasheet/memory-map.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.