Feature request/refinement: Manufacturer PID boolean

[unclewalter]

This is a minor one, but it would be nice. I don't have access to the ANSI E1.20 - 2025 standard, which I think there was some talk of adding a DS_BOOLEAN data type to the PARAMETER_DESCRIPTION response in the forums. Maybe you have access to the latest standard and you may be able to confirm this since I've noticed DMXRouter queries DEVICE_UNIT_NUMBER, which is a later addition to the RDM spec.

But the convention I have noticed in fixture implementations using the 2010 standard is a field is a DS_UNSIGNED_BYTE with a range of 0 - 1, is functionally as a boolean type, such as the display_on and cmy_on messages on a Clay Paky sharpy.

Would be great is if any manufacturer PIDs are reported as a DS_UNSIGNED_BYTE with a 0-1 range, they're rendered as a check box rather than a number.

[fiverecords]

Good call, and yes — I can confirm it from the 2025 edition: ANSI E1.20-2025 adds DS_BOOLEAN (0x0D, 8 bits, "zero = false, non-zero = true") to the PARAMETER_DESCRIPTION data types in Table A-15, along with DS_UID, DS_URL, DS_MAC, DS_IPv4, DS_IPv6, DS_ENUMERATION and 64-bit integers. 2010's DS_UNSIGNED_BYTE is DS_UINT8 now, same code.

For the next version: in the Mfr PIDs table, a parameter that is either DS_BOOLEAN or an unsigned byte with a 0–1 range (your Sharpy convention) will get a checkbox in its Value column. Ticking it will be the SET; the re-read will confirm; a NACK will put the box back to what the device holds; GET-only parameters will show the box read-only. The Type column will also name the 2025 types instead of printing hex.