> 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/is3720-description.md). # IS3720 Description ## What is it and what it does The IS3720 is a 3.3 V operating chip that integrates both DMX Receiver + RDM Responder protocols in a single IC. It buffers all 512 DMX channels in its internal memory map, which is accessible by your microcontroller via I2C. The IS3720 also enables bidirectional communications through RDM, allowing remote configuration and management of your product. This eliminates the need for manual setup, such as physically adjusting the DMX start address. ## Utility RDM is especially helpful for light fixtures in large installations, such as building façade lighting, where an operator would otherwise spend significant time manually setting DIP switches on thousands of fixtures distributed across multiple floors and rooms. It is also invaluable in installations where fixtures are embedded in the pavement or other sealed environments, like swimming pools or ornamental fountain where opening them would require breaking the ground or compromising waterproofing.
## Benefits The IS3720 eliminates the need for engineers to learn and implement the low-level details of the DMX and RDM protocols. This significantly reduces development and testing effort, shortens time-to-market, and enables faster product release. ## How it works The IS3720 features two communication interfaces: * An I2C-serial interface (SCL and SDA pins), operating as slave device (address 22), used to communicate with your microcontroller. * A UART interface (RX/TX and DIR pins), used for DMX+RDM communications. The UART pins operate at TTL voltage levels, while the DMX network uses RS485 voltage levels. Therefore, an external RS485 transceiver, such as the THVD1500, is required to convert between TTL and RS485 levels. The UART pins are 5 V-tolerant. Additional design details can be found in the Hardware Examples section. The IS3720 has an internal memory map consisting of 632 registers, each 8 bits wide, with addresses ranging from 0 to 631. Therefore, accessing any register requires a 2-byte addressing. Registers 1 to 512 correspond directly to DMX channel values. For example, reading register address 1 gets the value of DMX Channel 1, reading register address 512 reads the value of DMX Channel 512, covering the full range of channels. RDM registers are mapped after the DMX registers. Some are informational, such as the MANUFACTURER\_LBL register block, where you write via I2C your company name and it will show up on the RDM controller. Others are operational, such as the DMX\_START\_ADDRESS register block, which indicates the assigned DMX start address to the microcontroller. --- # 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, and the optional `goal` query parameter: ``` GET https://inacks.gitbook.io/inacks-is3720-i2c-dmx+rdm-receiver-ic/datasheet/is3720-description.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.