addressable.wiki

Inolux PI (single-trace IC)

1-wire RGB · Inolux Corporation · inolux

Channels
RGB
Bits / channel
8
Supply
3.5–5.5 V
PWM
1.2 kHz
Backup data
no
Packages
13

Inolux calls the IC ‘PI - single trace IC’ in its part-number key (the PC series is the clock-and-data variant, see inolux-pc) and never gives it a chip name. The sheets share one template: ‘Single line data transmission (return to zero code)’, ‘Specific Shaping Transmit Technology’ (each pixel regenerates the signal) and ‘SA-I anti-interference’ (a marketing label; no figures given). The timing table is not the same on every sheet - see the three timing sets - but all sheets agree on 800 kbps, GRB order and the 24-bit frame, so one protocol covers the single-wire PI parts. Drive current is part-level: the part-number letters ‘5R5G5B’ mean 5 mA per channel and ‘PRPGPB’ mean 12 mA (key on the sheet: ‘P=12mA, 5=5mA’). The BrtLed BL- HRGB32K-3-TRB sheet reproduces the PI556FCH electrical and timing tables value for value and uses this protocol.

Refresh & flicker

PWM frequency 1.2 kHz typical on most sheets (1.0 kHz on the PI31, 4.0 kHz on the PI3210 and PI3727). Static current 0.25-1 mA typical. DIN thresholds 0.7 / 0.3 VDD on newer sheets, 3.4 V / 1.6 V on the 2016-2018 sheets. Data rate 800 kbps (the PI22 sheet’s feature list says 750 kbps while its own switching table says 800 kHz). 256 grey levels per channel, 24 bit per pixel sent G, R, B with the MSB first. After power-up the IC self-tests and lights the blue chip (all sheets).

Timing

Sources disagree. This is normal and worth understanding: FastLED's numbers are tuned to drive real parts reliably, including clones, while the datasheet gives the manufacturer's nominal figures. Both are recorded here rather than picking one and hiding the conflict.

Inolux PI (single-trace IC) bit timingInolux PI (single-trace IC) bit timing: a zero bit is 300 nanoseconds high then 900 low; a one bit is 600 high then 600 low; tolerance plus or minus 150 nanoseconds; reset 80 microseconds low1 · Bit encoding, to scaleDINhighlowbit 0 period 1200 nsbit 1 period 1200 nsT0H 300 ±150 nsT1H 600 ±150 nsT0L 900 ±150 nsT1L 600 ±150 ns"0" bit"1" bit020040060080010001200140016001800200022002400time, ns± tolerance on each falling edge2 · One frame: 24 bits, most-significant bit firstDIN170110010007100110101700101100bitch 1 · 8 bitsch 2 · 8 bitsch 3 · 8 bitsChannel order not recorded for this protocol · frame = 24 × ~1200 ns ≈ 28.8 µs · example data, first bits 1 0 1 …3 · RESET / latchlast bits of frame 1first bits of frame 2LEDs latch the data they receivedRESET: DIN low ≥ 80 µs (not to scale)4 · Cascade: each DOUT feeds the next DINMCULED 1DINDOUTLED 2DINDOUTLED NDINDOUTLED 1 keeps the first 24 bits, re-shapes the signal and sends the rest out on DOUT;LED 2 keeps the next 24, and so on. The last LED's DOUT is left unconnected.
T0H 300 / T0L 900 · T1H 600 / T1L 600 ns · ±150 ns · period 1200 ns · reset 80 µs source: datasheet
SourceT0HT0LT1HT1LPeriodRateReset±
datasheet ↗ 300 ns 900 ns 600 ns 600 ns 1200 ns 833 kHz 80 µs 150 ns
Typical values with a +/-0.15 us error. The sheets state TH+TL as 1.25 us +/-600 ns while their own typicals sum to 1.2 us per bit. This is the oldest Inolux set (first issue 2015-12-21 on the PI554FCH sheet).
datasheet ↗ 320 ns 800 ns 640 ns 200 ns 1200 ns 833 kHz 80 µs —
Window table: T code period min 1.20 us; T0H 0.2 / 0.32 / 0.4 us; T0L min 0.8 us; T1H 0.58 / 0.64 / 1.0 us; T1L min 0.2 us; reset >80 us. T0L and T1L print a minimum only, so those two values are minimums, not typicals. The ‘standard’ T1H differs by sheet: 0.6 us on PI15, 0.64 on PI20TA, PI32 and PI33TC, 0.74 on PI20TB, 0.75 on PI3210 and PI3727; T0H standard is 0.3 or 0.32 us.
datasheet ↗ 300 ns 900 ns 900 ns 300 ns 1200 ns 833 kHz 80 µs 150 ns
The PI22 sheet and the PI31TAS sheet (C20884170: T0H 0.2-0.4 std 0.3, T0L min 0.8 std 0.9, T1H 0.7-1.0 std 0.9, T1L min 0.2 std 0.3, reset >80 us) print the 300 / 900 / 900 / 300 ns split instead.

Clones & compatibility

“Compatible” is never stated bare here — each relationship carries how strong the claim is, and what bites if you assume too much.

  • protocol compatible SK6812

    The four typical values of the older sheets (T0H 300, T0L 900, T1H 600, T1L 600 ns, reset 80 us, GRB, 24 bit, MSB first) are the same numbers the sk6812 protocol records from the OPSCO SK6812 rev. 02 sheet, so the framing and timing are interchangeable on those sheets. None of the Inolux sheets mentions SK6812 or WS2812 by name. The newer windowed sheets move the typical T1H to 640-900 ns, and the PI55TA and PI3210 sheets ask for a reset of 200 us, so this is protocol-compatible, not a clone claim. source ↗

  • protocol compatible of this Inolux PI dual-signal (single-trace IC with BIN)

    Same single-trace code, timing windows and GRB frame as inolux-pi (PI33TC sheet, p5-6); the only difference the sheet documents is the second data input BIN that lets the chain 'continue transmission' past a dead pixel.

Library support

Not checked against FastLED, Adafruit or WLED source.

Parts using this protocol

Dating evidence

Evidence, not a release date. A library commit proves the part existed by that date and says nothing about how long before.

  • 2015-12-21 datasheet revision Inolux IN-PI554FCH data sheet revision table: 'Initial release 1.0 12-21-2015' (also on the IN-PI556FCH sheet) ↗ day