DDM 2.0 CLI (command line interface)

WriteActiveInput [DVI2/HDMI/DP2,etc] = switches active input
ReadActiveInput [DVI2/HDMI/DP2,etc] = switches active input
RestoreFactoryDefaults = restores factory defaults
AutoSetup = executes an autosetup (analog only)
ReadColorPreset = read the current color preset
WriteColorPreset = set the color preset
RestoreLevelDefaults = restores level defaults
RestoreColorDefaults = restores color defaults
WriteBrightnessLevel X = sets brightness to X% (0-100)
ReadBrightnessLevel X = sets brightness to X% (0-100)
WriteContrastLevel X = sets contrast to X% (0-100)
ReadContrastLevel X = sets contrast to X% (0-100)
WritePowerMode [on/off/standby] = sets the display power mode (standby should be used for central control.)
WriteOptimalResolution = switches to optimal resolution
WriteEALayout [X] = changes Easy Arrange grid type to X (0-48) where 0 is to turn off EA layout
Rescan = rescans display hardware
ReadControl X Y = sets hex control X to hex value Y
WriteControl X Y = sets hex control X to hex value Y
IncreaseControl X Y = increases the value of control X by Y
DecreaseControl X Y = decreases the value of control X by Y
WritePxP [Off/PiP/PBP Main Sub1] = Change PIP/PBP settings
WriteSubInput [DP1, DP2, HDM1... etc}] = Change the subinput
SwapVideo = Swaps the main (primary and sub inputs between 2 PCs
SwapUSB = swaps the usb inputs on the main and sub inputs (for 2 PBP mode only)
Zoom = switches between PxP and fullscreen mode
Exit = terminates the program

Thanks Chris, those commands are really helpful.

Unfortunately, when running the supposed "CLI" commands on the command line (powershell in windows terminal), I don't get any results on the command line. I would expect "ReadActiveInput" to return something like "DP1" or "HDMI".

I looked at the DLL files shipped with the DDM 2.0 and it looks like the CLI is actually a background process of the GUI app running in Windows. From my quick look I think the issue is that the output from the CLI is lost in the background task running it.

I got multiple questions about that:

1. Could Dell make a proper CLI that runs standalone and only uses the Dell Monitor SDK to access and set those values without the graphical (GUI) application?
2. When making this CLI, could you please use standard command line parameters used by basically the majority of software in this world now? Which is "-" or "--" for parameters and a "--help" parameter to get the information you posted above.
3. With DDM 2.0 the readme.txt file is missing which contains the information you posted in this and other threads. It would be nice if this was added back to the installation directory.

Would it be okay if I use the "DellMonitorSDKDLL.dll" file to write my own CLI and put the source code on GitHub? Or is that against Dell's license?

With DDM 1.x, you can go to the installation folder and execute "ddmcmd.exe /GetActiveInput" from a console, which should returns something like: "GetActiveInput = Thunderbolt". There is, however, no easy way to get the current PIP/PBP mode.

Didn't have any luck with that either. I tried it, but it doesn't give me the name of the input unfortunately.

.\ddmcmd.exe /GetActiveInput
GetActiveInput =

But I found a better solution to my problem. The aforementioned SDK is actually publicly available, including actual documentation https://www.dell.com/support/home/en-au/drivers/driversdetails?driverid=gx6gp

I will try to use this to build my own CLI and then hopefully publish it on GitHub. Once it is done I will post it here.

Have you made any progress on this?

Have you managed to use the SDK to build your own tools? Is it publicly available?

This issue should be resolved in DDM 2.1 with the command ddm.exe /console start /readactiveinput