Using the F16V4 as an interface between a DMX controller and LED strips?

[geeman1082]

Hi All.  Is there a way to configure the F16V4 to accept DMX signals from a DMX controller as an input and then use those signals to drive some WS2812B LEDs?  The manual makes no mention of receiving DMX signals (only outputting them), I got conflicting answers from some chatbots, and I couldn't find anything when searching the forum, so I think I know the answer, but I also understand that this wouldn't be a common application for the F16V4, so I thought I would at least post the question and get a definitive answer.  Thanks.

(To answer the obvious question, this would permit me to standardize on components for some potential commercial applications.)

[darylc]

No

[MikeKrebs]

As an alternative, a DMX to SPI converter could be used. Better to get a dedicated device that can handle it? Maybe something like:
https://www.superlightingled.com/dmx512-to-spi-converter-dsa-for-led-strip-light-kit-p-1240.html

A home built solution might be able to handle this. For 20 bucks, get a WT32, add some input components, and do some DMX in, e1.31 out.

[k6ccc]

It would not make much sense to tie up a F16 controller that can drive many thousands of pixels using a communications protocol that can only support 170 pixels.

[geeman1082]

As an alternative, a DMX to SPI converter could be used. Better to get a dedicated device that can handle it? Maybe something like:
https://www.superlightingled.com/dmx512-to-spi-converter-dsa-for-led-strip-light-kit-p-1240.html

A home built solution might be able to handle this. For 20 bucks, get a WT32, add some input components, and do some DMX in, e1.31 out.

That of course is the other option.  I'll look at that specific option you mentioned.  Thanks for the reply.

[geeman1082]

It would not make much sense to tie up a F16 controller that can drive many thousands of pixels using a communications protocol that can only support 170 pixels.

Thanks for the reply.  I'm told the typical projects will indeed include thousands of pixels (understanding that each universe can only control 170, as you noted), and we expect to be using the Falcon controller for other projects (which would typically be stand-alone, controlled by a Pi running FPP), so standardizing on the F16V4 seemed like a good idea if it could handle the task.  But I guess that's not going to be in an available option.

[geeman1082]

For the record, here is the release note that made me think it might be possible, and maybe just not documented yet because it was only added 6 months ago ... but I perhaps I was trying to read what I wanted to be and not what it really is:

Build 33 : 2024-11-20
 - Enh : Add an input action for next/prior/first playlist looped
- Enh : Add DMX input mode for low channel count -> large pixel count control
- Enh : Add player command to turn on/off test mode
- Fix : Universe counter incorrect when multiple E1.31 rows defined

[darylc]

For the record, here is the release note that made me think it might be possible, and maybe just not documented yet because it was only added 6 months ago ... but I perhaps I was trying to read what I wanted to be and not what it really is:

Build 33 : 2024-11-20
 - Enh : Add an input action for next/prior/first playlist looped
- Enh : Add DMX input mode for low channel count -> large pixel count control
- Enh : Add player command to turn on/off test mode
- Fix : Universe counter incorrect when multiple E1.31 rows defined

The F16v4 doesn't have hardware to receive DMX input.  I expect that is a mistake in the release notes.  The F16v5 and F48v5 likely has hardware to receive input on its Smart Receiver ports so perhaps they accept DMX through those with that new feature?  Contact support@pixelcontroller.com directly to find out and let us know.