Specifications

List of controls supported by a monitor (optional if you have an include element).
control id attributes are defined in options.xml. If control type is “list” or
“command” without default values, supported values must be defined.
address attribute for control elements and value attribute for value elements are optional if
they are defined in the general options file.
The init attribute in monitor element define the type of the initialization: DDC/CI standard
(“standard”), or Samsung (“samsung”). This attribute is optional, as long as the monitor pro-
file includes another profile which defines this attribute.
You can set a delay attribute in control elements to set the time in milliseconds to wait after
changing the value of this control. If you don't, a default value is used.
include element
Includes another monitor, manufacturer or standard profile, specified by the file attribute.
Note
Monitor profile are read sequentially. Control and init mode redifinitions are ignored, so define spe-
cific controls and init mode before including a generic profile. Caps are also treated sequentially, so
if a control is not in CAPS at the time it is defined, it won't be supported by ddccontrol.
File format:
<?xml version="1.0"?>
<monitor name="%full_monitor_name%" init="[standard|samsung]">
<caps add="%add_caps%" remove="%remove_caps%"/>
<controls>
<!--- value -->
<control id="%control_id%" address="%hex_address%" delay="%wait_time%"/>
<!--- command using a default 0x01 value-->
<control id="%control_id%" address="%hex_address%" delay="%wait_time%"/>
<!--- command -->
<control id="%control_id%" address="%hex_address%" delay="%wait_time%">
<value id="activate" value="%hex_value%"/>
</control>
<!--- list -->
<control id="%control_id%" address="%hex_address%" delay="%wait_time%">
<value id="%value_id%" value="%hex_value%"/>
<value...>
</control>
<control...>
</controls>
<!--- Including VESA generic profile is generally a good idea. -->
<include file="VESA"/>
</monitor>
If a monitor supports exactly the same controls as another one, you can define it as shown:
<?xml version="1.0"?>
<monitor name="%full_monitor_name%">
<caps add="%add_caps%" remove="%remove_caps%"/>
<include file="%include_monitor_id%"/>
</monitor>
Profile file structure
Profile files are used to save the value of some controls.
profile attributes:
• pnpid: indicates the PNP id of the monitor that this profile applies to.
• name: profile name.
Documents for developers
16