Skip to main contentSkip to footer

I2C DMX+RDM Receiver Chip – IS3720

āœ… DMX receiver + RDM responder in one chip: receive up to 512 DMX channels.

āœ… Your brand, your product: once configured, RDM controllers show your company, model and software labels. The chip stays transparent.

āœ… Remote addressing: the DMX start address is set from the RDM controller and kept in non-volatile memory.

āœ… I2C at 100 kHz, 400 kHz or 1 MHz, 3.3 V supply with 5 V-tolerant I2C: works with 3.3 V and 5 V microcontrollers.

Volume pricing

Qty. Price
1 - 9 1,95 €
10 - 24 1,85 €
25 - 99 1,70 €
100 - 299 1,35 €
300 - 499 1,23 €
500 - 999 1,11 €
1000 - 7999 1,03 €
8000 + 0,98 €
SKU: IS3720-S8

What is the IS3720 RDM responder chip?

The IS3720 is an RDM responder chip with a built-in DMX512 receiver. It continuously buffers all 512 DMX channels in an internal register map that your microcontroller reads over I2C.

The IS3720 also answers the RDM controller on its own: discovery, device information, labels, DMX start address and identify requests. Lighting operators can find, address and identify your product remotely, without DIP switches or opening the fixture.

Documentation

Your brand on every RDM controller

Your firmware writes your company name, model name and number, software version and product category into the IS3720 over I2C. From then on, RDM controllers display your product, not the chip.

These settings live in non-volatile memory and are only rewritten when a value changes, so your firmware can safely write them at every startup.

Utility

RDM is especially helpful for light fixtures in large installations, such as building faƧade lighting. There, an operator would otherwise spend significant time setting DIP switches on thousands of fixtures across multiple floors and rooms.

It is also invaluable for fixtures embedded in pavement or other sealed environments, like swimming pools and ornamental fountains. Opening those means breaking the ground or compromising waterproofing. Because the IS3720 also reports your DMX footprint, RDM controllers can auto-patch your fixtures.

Why use an RDM responder chip

It moves the whole protocol off your microcontroller:

  • No low-level DMX or RDM details to learn, implement or debug; the IS3720 handles the timing.
  • Fewer ISRs and lower CPU load, with no UART or timers dedicated to DMX.
  • Less flash and RAM, and only two I2C pins (plus an optional INT pin).
  • Less development and testing effort, and a faster time to market.

How the IS3720 RDM responder chip works

The IS3720 has two communication interfaces:

  • I2C (SCL, SDA) to your microcontroller: slave address 22 (0x16), 16-bit register addressing, and 100 kHz, 400 kHz or 1 MHz selected with the I2CSPD pin. The I2C master must support clock stretching.
  • UART (RX/TX, DIR) to an external RS485 transceiver such as the THVD1500, carrying the half-duplex DMX+RDM link. Both pins are open-drain and 5 V-tolerant, with pull-up resistors to the transceiver supply.

The internal memory map holds 632 8-bit registers. Registers 1 to 512 hold DMX channels 1 to 512: reading register 1 returns channel 1, and reading register 512 returns channel 512.

The RDM registers follow. Some are informational, such as MANUFACTURER_LBL, where you write your company name. Others are operational, such as DMX_START_ADDRESS, which tells your firmware the start address set by the operator.

The INT pin pulses whenever the DMX start address or the identify state changes, so your firmware doesn’t need to poll them.

Firmware in three steps

  1. At startup, write your product category, DMX footprint and labels over I2C, plus the UID if your firmware holds a unique one per unit.
  2. Write 1 to RDM_ONLINE to bring RDM online. DMX reception is always active.
  3. In the main loop, read DMX_START_ADDRESS and the channels your fixture uses, and run your identify pattern while IDENTIFY_DEVICE is 1.

From prototype to production

  • Each IS3720 ships with a prototyping UID. For commercial products, program your own ESTA manufacturer ID and serial numbers.
  • On the production line, a provisioning PID lets you write a unique UID to each unit over RDM.
  • Standard version: SO8N, āˆ’40 to 85 °C. On request, with a minimum order quantity: āˆ’40 to 105 °C and āˆ’40 to 125 °C grades, plus UFQFPN 3Ɨ3 mm and WLCSP 1.7Ɨ1.42 mm packages.

Key specifications

Parameter Value
DMX reception 1 to 512 channels, full universe buffered
RDM PIDs 11 (listed in the FAQ)
Host interface I2C slave, address 22 (0x16), 16-bit register addressing
I2C speed 100 kHz, 400 kHz or 1 MHz, set by the I2CSPD pin
Supply 3.3 V; SCL, SDA, RX/TX and DIR are 5 V-tolerant
Supply current 3.5 mA typ., 4.1 mA max. at 85 °C ambient
DMX/RDM line UART (RX/TX + DIR) to an external RS485 transceiver
Non-volatile memory 10,000 write cycles; 30-year retention after 1,000 cycles at 85 °C (characterization data)
Package SO8N; UFQFPN 3Ɨ3 mm and WLCSP 1.7Ɨ1.42 mm on request
Ambient temperature āˆ’40 to 85 °C; āˆ’40 to 105 °C and āˆ’40 to 125 °C on request

Videos

 

This company and the products provided herein are developed independently and are not affiliated with, endorsed by, or associated with any official protocol or standardization entity. All trademarks, names, and references to specific protocols remain the property of their respective owners.

Documentation

Models

Q: Which applications use the IS3720 chip?

A: Professional lighting, including architectural and building lighting, stage and entertainment lighting, faƧade lighting, in-ground lighting, ornamental fountain lighting, difficult-access lighting, digital art installations and animatronics. It is designed for OEMs and device manufacturers.

Q: What are the main advantages of the IS3720 chip?

A: It reduces engineering time and cost and shortens time to market, because DMX and RDM become transparent to both your microcontroller and your engineers. Your microcontroller needs fewer ISRs, less CPU time and less memory, and no dedicated UART or timers. It only uses the I2C pins, and the SO8N package is compact and easy to solder.

Q: How many DMX channels can I receive with the IS3720 chip?

A: From 1 up to all 512. The IS3720 buffers the whole DMX universe, and your firmware reads only the channels it needs, starting at the DMX start address. Reading only your fixture’s channels keeps I2C transfers short and the refresh rate high.

Q: Which RDM PIDs does the IS3720 chip support?

A: It supports 11 standard PIDs: DISC_UNIQUE_BRANCH, DISC_MUTE, DISC_UN_MUTE, SUPPORTED_PARAMETERS, PARAMETER_DESCRIPTION, DEVICE_INFO, DEVICE_MODEL_DESCRIPTION, MANUFACTURER_LABEL, SOFTWARE_VERSION_LABEL, DMX_START_ADDRESS and IDENTIFY_DEVICE. Together they cover all PIDs required by ANSI E1.20-2010.

Q: Will RDM controllers show my brand or INACKS?

A: Your brand. Over I2C, your firmware writes your company name, model name and number, software version label and number, and product category. Labels hold up to 32 ASCII characters. Until you write them, the chip reports its INACKS defaults.

Q: Do I need my own RDM manufacturer ID?

A: Yes, for commercial products. An RDM UID has 6 bytes: a 2-byte ESTA manufacturer ID and a 4-byte serial number. The IS3720 ships with manufacturer ID 0x7FF7 and a random serial number for prototyping. IDs 0x7FF0 to 0x7FFF are reserved for prototyping and not permitted in commercial products, so apply for your own manufacturer ID.

Q: How do I give every unit a unique UID in production?

A: Your firmware can write the UID over I2C while RDM is offline (RDM_ONLINE = 0). For production lines, write the key value 160 to RDM_ONLINE: this enables the provisioning PID 0x8000 (“Update UID”), so each UID can be written over RDM. The UID is stored in non-volatile memory.

Q: What does my microcontroller need to work with the IS3720?

A: Only an I2C master that supports clock stretching. The IS3720 is an I2C slave at address 22 (0x16) with 16-bit register addresses and 8-bit registers, and it reads and writes like an EEPROM. Its I2C pins are 5 V-tolerant, so 3.3 V and 5 V microcontrollers both work. No UART, timers or DMX/RDM libraries are needed.

Q: What external components does the IS3720 need?

A: A 3.3 V supply with 100 nF and 2.2 µF decoupling capacitors, plus I2C pull-up resistors. On the DMX side, an RS485 transceiver such as the THVD1500, with pull-up resistors from RX/TX and DIR to the transceiver supply. Strap the I2CSPD pin to VSS for 100 kHz, VDD/2 for 400 kHz or VDD for 1 MHz. The datasheet includes a reference schematic.

Q: How does my firmware know when the operator changes the DMX address or requests Identify?

A: Read the DMX_START_ADDRESS and IDENTIFY_DEVICE registers, or connect the optional INT pin, which pulses whenever either one changes. While IDENTIFY_DEVICE is 1, your firmware overrides DMX and runs its own identify pattern, such as flashing the light.

Q: Are the RDM settings kept after a power cycle?

A: Yes. The UID, DMX start address, DMX footprint, category, labels, model number and software number are stored in non-volatile memory. DMX channel values, IDENTIFY_DEVICE and RDM_ONLINE start at 0 after power-up, so your firmware brings RDM online at every startup.

Q: Is there an evaluation board for the IS3720?

A: Yes, two. The Kappa3720Ard has the Arduino form factor and also fits STM32 NUCLEO boards; the Kappa3720Rasp has the Raspberry Pi form factor. Both carry an RGB LED that simulates a DMX PAR light and two daisy-chained XLR-3 connectors.

Q: Which packages and temperature ranges are available?

A: The standard IS3720 comes in SO8N for āˆ’40 to 85 °C, and you can order it pre-mounted on a PCB. On request, with a minimum order quantity: āˆ’40 to 105 °C and āˆ’40 to 125 °C grades, and UFQFPN 3Ɨ3 mm or WLCSP 1.7Ɨ1.42 mm packages. Contact sales@inacks.com.

Q: Does the IS3720 make my product RDM-compliant?

A: The IS3720 implements the RDM responder protocol and the PIDs listed above, but it has not been certified by any protocol organization. Compliance testing and certification of your final product remain your responsibility.

Pre-mounted on a PCBNo, Yes

Firmware Examples

Hardware Example

Evaluation boards, Modules & other related products

Evaluation boards, modules, and accessories designed for fast prototyping and easy integration. Featuring standard interfaces and built-in transceivers, they simplify testing and development across platforms like Arduino, Nucleo, or Raspberry Pi. Ideal for adding RS485, RS232, or Ethernet functionality with minimal effort and maximum compatibility.

Have a question?

Fill out this field
Please enter a valid email address.
Fill out this field
You need to agree with the terms to proceed