You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The spec states: To turn the display off, Display Level shall be set to 0. To turn the display on full, Display Level shall be set to 0xFF. Any value in between represents a relative intensity setting. If the device does not support relative intensity settings, any non-zero value shall be interpreted as on.
So, it should not be (by default) restricted to the current: ? { name: "Off", value: 0 }, { name: "Full", value: 255 },
The text was updated successfully, but these errors were encountered:
I think this does nicely prove that the "examples" are actually nearly as important as the schema. Once you've got a schema, people are going to want to be able to download all the standardised PIDs in the format of that schema. A bit like the existing header file Scott makes, but given the schema is standardised I'd say it can be even more official.
Or to put it another way, if you provide "examples" of the standardised PIDs people will use them/take them as gospel without checking, so they need to be perfect.
https://github.com/ssilverman/rdm-schema/blob/master/examples/e1.20/DISPLAY_LEVEL.json
The spec states:
To turn the display off, Display Level shall be set to 0. To turn the display on full, Display Level shall be set to 0xFF. Any value in between represents a relative intensity setting. If the device does not support relative intensity settings, any non-zero value shall be interpreted as on.
So, it should not be (by default) restricted to the current: ?
{ name: "Off", value: 0 }, { name: "Full", value: 255 },
The text was updated successfully, but these errors were encountered: