Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LG 34G850-B not accepting commands #297

Open
ctvw opened this issue Feb 7, 2023 · 1 comment
Open

LG 34G850-B not accepting commands #297

ctvw opened this issue Feb 7, 2023 · 1 comment
Labels
input source VCP feature x60 lg

Comments

@ctvw
Copy link

ctvw commented Feb 7, 2023

LG 34G850-B

I'm showing that input and power are available, however, I'm unable to actually change the values. Nothing happens. Is it possible that ddcutil is not returning or sending the parameters properly?

(prot(monitor)type(lcd)model(WK95U)cmds(01 02 03 0C E3 F3)vcp(02 04 05 08 10 12 14(05 08 0B ) 16 18 1A 52 60(11 12 0F 10 ) AC AE B2 B6 C0 C6 C8 C9 D6(01 04) DF 62 8D F4 F5(01 02 03 04) F6(00 01 02) 4D 4E 4F 15(01 06 11 13 14 15 18 19 20 22 23 24 28 29 32 48) F7(00 01 02 03) F8(00 01) F9 EF FA(00 01) FD(00 01) FE(00 01 02)

@rockowitz rockowitz added lg input source VCP feature x60 labels Feb 8, 2023
@rockowitz
Copy link
Owner

Feature x60 (Input Source) is problematic on recent LG monitors. See the very long discussion on issue #100, where your monitor is specifically mentioned. It may have to do with how Picture by Picture is controlled using manufacturer reserved features. Some users have tried to figure out the logic by experimentation. See for example, issue #163.

Feature x60 is also peculiar in that on some monitors reading the value succeeds no matter what the input source, on others it succeeds only if sending the command to the current input source.

As background, setting a feature value in DDC entails sending a request packet. If DDC reports success, it only means that the request was received by the monitor, not that the monitor successfully executed the request. There is no reply packet. For this reason, by default, setvcp explicitly reads the value after setting it. (This behaviour can be turned off using the --noverify option.) However, for feature x60 automatic verification is not performed, because, as noted, it is commonly the case that it is not possible to read values once the input source has changed.

Note also that the capabilities string returned by a monitor is often inaccurate. ddcutil reports the string for informational purposes using the capabilities command, but does not rely on it. For example, your capabilities string reports feature x15, which is undefined in the Monitor Control Command Set spec, and is not in the manufacturer reserved range xF0-xFF.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
input source VCP feature x60 lg
Projects
None yet
Development

No branches or pull requests

2 participants