E1.20 RDM (Remote Device Management) Protocol Forums

E1.20 RDM (Remote Device Management) Protocol Forums (http://www.rdmprotocol.org/forums/index.php)
-   RDM Interpretation Questions (http://www.rdmprotocol.org/forums/forumdisplay.php?f=5)
-   -   MINIMUM_LEVEL (http://www.rdmprotocol.org/forums/showthread.php?t=1202)

docsale April 2nd, 2014 03:37 AM

MINIMUM_LEVEL
 
Hi,

looking at this PID description, I was'nt able to fully understand how a responder should behave in response to MINIMUM_LEVE settings: if "On Below Minimum" = 1, what is dimmer supposed to do if DMX512 input is 0? It has to stay to minimum or turn off?

Thanks

Francesco

ericthegeek April 2nd, 2014 10:28 AM

1 Attachment(s)
Hopefully this graphic will help explain the behavior.
http://www.rdmprotocol.org/forums/at...1&d=1396455699

Edit:
The forum software rescaled the image so it's a bit hard to read. Here's the text:

The graphic on the left:
One Below Minimum=1 A.K.A "Preheat"
Light output never goes below the minimum level.


The graphic on the right:
One Below Minimum=0
No light output until a minimum level is reached.
Typical behavior for dimmable fluorescents

docsale April 2nd, 2014 10:52 AM

Quote:

Originally Posted by ericthegeek (Post 2777)
Hopefully this graphic will help explain the behavior.
http://www.rdmprotocol.org/forums/at...1&d=1396455699

Edit:
The forum software rescaled the image so it's a bit hard to read. Here's the text:

The graphic on the left:
One Below Minimum=1 A.K.A "Preheat"
Light output never goes below the minimum level.


The graphic on the right:
One Below Minimum=0
No light output until a minimum level is reached.
Typical behavior for dimmable fluorescents

Hi,

thanks for the support. So, in the "Preheat" configuration, output never goes OFF even if DMX512 is 0? To me it sounds quite strange but, if this is the standard requirement, i will follow it!!!

ericthegeek April 2nd, 2014 11:01 AM

Quote:

Originally Posted by docsale (Post 2778)
thanks for the support. So, in the "Preheat" configuration, output never goes OFF even if DMX512 is 0? To me it sounds quite strange but, if this is the standard requirement, i will follow it!!!

Preheat is commonly used with incandescent lamps. By keeping the filament glowing at a very low level you can get much faster response when you want a fast turn-on. It's a major energy waster so not used as often as it was in the past, but still a useful feature. In shows with lots of flashing, it can also improve lamp life.


There's no requirement that you offer a preheat function. If your product supports preheat, you can use this PID to control and report it, but if you don't want to offer this feature, you don't have to. It's entirely your choice. It depends on the kind of product you are building, and the needs of your customers.

este_ August 1st, 2014 12:44 PM

1 Attachment(s)
Mostly, MINIMUM_LEVEL will go together with MAXIMUM_LEVEL. When setting both, the usable fader travel will be narrowed (between the yellow dotted lines).

Attachment 43

There is a simple way to widen the fader range. Simply calculate OUTLEVEL = INLEVEL*(MAX_LEVEL-MIN_LEVEL) + MIN_LEVEL and you can make use of the full fader range. We have added a parameter (flag) to do so and this would be a nice complement for the "ON_BELOW_ZERO" Flag. Maybe this option could be added to the MIN_LEVEL PID in future versions.

zano_villa January 20th, 2021 01:43 AM

Hello,

here's a question about Split levels in Minimum level PID.
If I correctly understand about Increasing and Decreasing definitions, I infer that Increasing minimum Level has to be set higher than Decreasing one.....
Is my interpretation correct?
If not, could you explain better this topic?
Thank you

ericthegeek January 21st, 2021 09:21 AM

From the protocol perspective, it doesn't matter. You can put any value in either field.

But in most cases those fields are used to provide hysteresis for applications and lamp types that need it. In those cases, yes, you'd expect the "increasing" value to be greater than than the "decreasing" value.

zano_villa January 21st, 2021 01:49 PM

Quote:

Originally Posted by este_ (Post 2816)
Mostly, MINIMUM_LEVEL will go together with MAXIMUM_LEVEL. When setting both, the usable fader travel will be narrowed (between the yellow dotted lines).

Attachment 43

There is a simple way to widen the fader range. Simply calculate OUTLEVEL = INLEVEL*(MAX_LEVEL-MIN_LEVEL) + MIN_LEVEL and you can make use of the full fader range. We have added a parameter (flag) to do so and this would be a nice complement for the "ON_BELOW_ZERO" Flag. Maybe this option could be added to the MIN_LEVEL PID in future versions.


(INLEVEL*(MAX_LEVEL-MIN_LEVEL))/MAX_DMX_LEVEL + MIN_LEVEL

ericthegeek January 21st, 2021 10:37 PM

There's not one "correct" equation. Dimmer curves (the DMX to output level mapping) is the subject of endless debate. este_'s equation might work for some users. But, if the user wants levels to match between fixtures with and without preheat, then it's not the best choice.

From the standard's perspective, any output mapping is acceptable. You can also expose multiple dimmer curves via RDM to give flexibility.


All times are GMT -6. The time now is 05:50 PM.

Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2021, vBulletin Solutions, Inc.