-
Notifications
You must be signed in to change notification settings - Fork 45
VCP Version: 2.1
Manufacture year: 2016
Controller manufacturer and model: MStar
Firmware version: 5.0
Features x0B and x0C are supported. Calculated color temperature = 6500 degrees Kelvin.
EDID model name is generic "LG IPS FULLHD"
Never sets the Unsupported Feature bit in replying to a GETVCP request for an unsupported feature. Instead retuns a success response with all response bytes = 0.
ASCII serial number is missing.
Never sets the Unsupported Feature bit in replying to a GETVCP request for an unsupported feature. Instead retuns a success response with all response bytes = 0.
ASCII serial number is missing.
VCP Version: 2.1
Manufacture year: 2015
Controller manufacturer: Mstar
Controller model: mh=x00, ml=xff, sh=x00
Firmware version: 3.7
Features X0B and X0C are not supported. Cannot calculate color temperature.
No serial number in EDID.
When brightness (VCP feature x10) is changed, it reverts to the original value after approximately 1 second. The same behavior is seen on Windows using ClickMonitorDDC and softMCCS, so this is clearly a monitor issue. This problem is not observed for other features.
VCP Version: 2.2 (from the capabilities string)
Manufacture year: 2020
Controller manufacturer: unknown (feature xc8 unsupported)
Controller version: unknown (feature xc8 unsupported)
Firmware version: 3.4
The EDID model name is generic "LG UltraFine".
This 5K monitor appears to have been built with only Macs in mind. It has no buttons, and no on screen display (OSD).
Despite an extensive list of features in the capabilities string, getvcp for most returns with the unsupported feature bit set in the response packet. The only features in the capabilities string that can be read using getvcp are: 0x10 (brightness), xFD (manufacturer reserved), xFF (manufacturer reserved). In particular, getvcp of feature xDF (VCP version) fails. Per the MCCS specification, this feature must be supported as of MCCS 2.0.
The following features unknown to MCCS are not listed in the capabilities string, but return a value for getvcp: xD1, xD3, xD5, xDD
This monitor also supports USB access to the Virtual Display Panel, but the only feature supported through this interface is 0x10 (brightness).
VCP Version: 2.1
Manufacture year: 2019
Controller manufacturer: RealTek controller number: mh=0x00, ml=0xff, sh=0x00
Firmware version: 3.24
EDID version: 1.3
EDID model name is "LG Ultrawide". No ASCII "serial number". (Binary serial number not checked)
Malformed capabilities string. (The "cmds" segment is named "UM69cmds")
Values ( parsed):
0f: DisplayPort-1
10: DisplayPort-2
11: HDMI-1
Has 1 HDMI, 1 DisplayPort, 1 USB-C Alt DP
Users report that it does not support DDC on the DisplayPort input. (See issue LG 29UM69G fails switching input) on github.
Github user mbastian resported:
After more than four months of back and forth with German support I've got this:
Our Korean software development takes note of reports of this kind, but this does not lead to customer feedback. Wwe do not see any need for further action here.
At first they where denying that DDC was even supported, when I've pointed them to the manual and spec sheet then they insisted that it only applied to the OSD. Finally they escalated it. I've explained in detail what my problem is, asked if there is a firmware update or an undocumented ddc feature.... and all I got is a not very nice "Don't bother us again!"
And Github user AndyKassell reported this response from LG tech support:
We have had a response from our Technical Team and they have advised that our monitors do not support DDC-CI officially. Some models are able to issue some commands such as brightness, contrast etc, but if there are issues with this, it would not be considered a fault as it is not guaranteed to work. I apologise for any frustration this causes.
Users of all these recent LG displays report similar problems with VCP feature X60 (Input Source). getvcp 60 always returns x00, which is not a valid value. setvcp 60 flashes the screen, sometimes opens the OSD, never sets the value
Users report this monitors do support featrue x60
No model name string in EDID. The binary model number is set (x7702 = 30471)
No ASCII serial number in EDID. Binary serial number is present
VCP version: 2.1
Controller manufacturer: MStar (sl=x05)
Controller Model: mh=x0, ml=xff, sh=x00
Firmware version: 3.4
Manufacture year: 2019
Properly sets the Unsupport VCP Code bit in a GETVCP response.
VCP version: 2.1
Controller manufacturer and model: STK
Firmware version: 0.1
Manufacture year: 2014
Feature codes are not separated by blanks in the vcp() section of the capabilities string.
No serial number in the EDID.
When responding to a Get VCP Feature request, the monitor never sets sets the Result Code field of the VCP Feature Reply to Unsupported VCP Code.
Instead, it always reports No Error.
For unsupported VCP codes, all bytes in the response (MH, ML, SH, SL) are set to x00.