A D-Bus ddcutil service for control of DDC Monitors/VDUs
The aim of this service is to make it easier to create widgets and apps for ddcutil. The service's client interface is now quite stable, but there may be some additions or tweaks if new requirements are discovered.
The service is written in C. It has very few dependencies (glib-2 and libddcutil) and is consequently quite easy to build. Once built, running the executable should make a ddcutil service available on the D-Bus Session-Bus.
Testing using the d-feet D-Bus interactive GUI:
- start d-feet;
- press the
session-busbutton in the d-feet header; - search for
ddcutil. - click on
com.ddcutil.DdcutilService - open the Object Path
com/ddcutil/DdcutilServiceand navigate down to thecom.ddcutil.DdcutilInterface - Double-click methods and properties to run or view them.
Method inputs can be supplied as CSV, for example, Method Input to GetVcp could be
1,'',0x10
This would access display 1, blank-edid '', DDC VCP Feature code 0x10
(brightness). VDU's are identified either by display-number or base-64-encoded
EDID.
Several bash and python scripts that demonstrate using the service are included in
the examples
folder. They cover the use of the dbus-send command line utility
and the python dasbus and QtDBus libraries.
The service was developed with the assistance of amendments to libddcutil by @rockowitz.
The current intention is to eventually package it with ddcutil/libddcutil.
When using this service, avoid excessively writing VCP values because each VDU's NVRAM likely has a write-cycle limit/lifespan. The suggested guideline is to limit updates to rates comparable to those observed when using the VDU's onboard controls. Avoid coding that might rapidly or infinitely loop, including when recovering from errors and bugs.
Non-standard manufacturer specific features should only be experimented with caution, some may have irreversible consequences, including bricking the hardware.
Detailed documentation can be found in the two manual pages:
- ddcutil-service.1 - Command line options and service overview.
- ddcutil-service.7 - Detailed D-Bus API documentation.
There is an official Tumbleweed RPM:
The same page also provides links to unofficial builds I've done for Leap.
Mark Wagie (yochananmarqos) has kindly provided AUR packaging:
Maciej Wójcik (https://gitlab.com/w8jcik) has kindly
provided a collection of unofficial debian/ubuntu packages along with instructions
for installing the required versions of libddcutil:
Check/modify the dependencies specified in the Makefile:
libddcutil-devel>= 1.4.0glib2-devel>= 2.40 (gio-2is normally part ofglib2)
The names of required development packages may vary depending on which distribution you are targeting.
Check the install PREFIX in the Makefile and make any changes required
for your circumstances, and issue make install or sudo make install
as appropriate.
Manual steps for installing a dbus-daemon service file for auto-starting and auto-restarting the service are as follows:
- Edit
com.ddcutil.DdcutilService.serviceand set the Exec location of the service executable (can be anywhere). - Install to:
/usr/share/dbus-1/services/com.ddutil.DdcutilService.serviceOr maybe to:$HOME/.local/share/dbus-1/services/com.ddutil.DdcutilService.service - Install the executable at the location set in step 1.
- Logout and login to a new session.
- Check service is available (use d-feet or any other test program).
Installing the service file is optional. The service file enables autostart of
the service by dbus-daemon. The service executable can be manually started
without the service file being installed.
The vdu_controls GUI has been modified to use the service by default, see:
https://github.com/digitaltrails/vdu_controls
The source includes an ddcutil-client (ddcutil-client.c and
man page ddcutil-client.1). Packaging and deployment of the client is optional.
If busctl or dbus-send is available, they will be about as fast.
A purpose built client is mostly a convenience for those that might
want a syntactically straight forward command line interface.
Thanks go out to Sanford Rockowitz (rockowitz) for libddcutil, ddcutil and all the assistance and advice provided during the development of this service.
Thanks also to Michal Suchanek for assistance with the OpenSUSE RPM spec; Johan Grande (nahoj) for the Ubuntu patches; Mark Wagie (yochananmarqos) for AUR packaging; and Maciej Wójcik (https://gitlab.com/w8jcik) for debian/ubuntu packaging.
The development IDE is JetBrains CLion-Nova/CLion. Thanks go out to JetBrains for granting the Open Source development license.
- 1.0.10
- Alter the detect-function for ddcutil 2.5.1 (generates more logging/warning info).
- Add a DETECT_ALL option to control whether disabled/powered-off VDU's are to be included in the results from detect.
- Reduce the number of messages generated when polling for hotplug events.
- Fixes to API documentation.
- 1.0.9
- Fixed a GetCapabilitiesMetadata bug that caused some VCP features to lack metadata values.
- Fixed the return of feature-name and feature-description from GetVcpMetadata.
- Fixed potential hot-plug/DPMS polling memory leaks and simplified event locking.
- Recoded hot-plug/DPMS polling to avoid a potential libddcutil assertion failure.
- Fixed code/doc typos, improved code readability/structure, reduced IDE warnings.
- Updated documentation to caution against excessive updates when coding loops, as this may impact VDU NVRAM lifespan.
- Updated documentation to caution against experimenting with non-standard features, as it may risk damage to the VDU.
- Added an optional ddcutil-client, a fast counterpart to ddcutil. Not built/packaged by default (unnecessary).
- 1.0.7
- Slightly improved setvcp diagnostics.
- Fix methods failing with return code DDCRC_OTHER (-3022) when only some i2c devices are accessible.
- 1.0.6
- Add SetVcp/SetVcpWithContext NO_VERIFY (no retry) flag option.
- Match the behaviour of the ddcutil command, default to verify-and-retry for all set-vcp method calls.
- Default to verify-and-retry for all libddcutil versions.
- Replace the stateful DdcutilVerifySetVcp property with the stateless NO_VERIFY flag.
- Fix the ServiceFlagOptions property so that it lists all flag options.
- Check the status returned by libddcutil ddca_init() and exit on error to prevent any inconsistent behaviour.
- Cleanup the --prefer-polling and --prefer-drm options to make them consistent with each other.
- 1.0.4
- Provide an API flag RETURN_RAW_VALUES which disables GetVcp high-byte masking of Simple Non-Continuous features.
- Provide the --return-raw-values command line option for the same purpose.
- 1.0.3
- Reduce unnecessary logging.
- Improve the description of the service's signals in ddcutil-service.1.
- Correct the typo in option name --prefer-drm (it was mistakenly called --prefer-dma).
- For simple VCP-features, only return the low-byte, for some VDUs the high-byte might contain junk.
- 1.0.2
- Added VcpValueChanged D-Bus signal which triggers if the SetVcp method succeeds. This is to allow multiple clients to be aware of changes made by each.
- Added SetVcpWithContext which accepts a client-context to be returned with the VcpValueChanged signal.
- ServiceEmitSignals renamed to ServiceEmitConnectivitySignals to avoid confusion.
- Command line option --emit-signals renamed to --emit-connectivity-signals for the same reason.
- Fix ServiceEmitSignals property assignment so that it correctly toggles hotplug signals.
- Fix hotplug polling so that it remains an option no matter what version of libddcutil is in use. ]()
- 1.0.1
- Use gcc with -Wformat-security for safety and to match Arch and Ubuntu defaults.
- Calling ddca_init() before verify_i2c() to fix runtime error for libddcutil >= 2.1.
- 1.0.0
- Initial Release