Additional Key #4
Comments
|
Changed this settting to "macro_key" and made it read-only. |
|
msigd --query does a lot of stuff, need a simpler verification algorithm. It can be done through a key or a separate utility. |
|
Options for msigd will get an overhaul at some time. |
|
unknown490 => |
|
unknown4=0 => unknown4=1 => |
|
unknown460 => |
|
unknown480 => |
|
unknown4:0 => |
|
unknown4;0 =>
|
|
unknown4<0 => values like |
|
unknown670 => |
|
|
perhaps 00620 - pip_input? |
|
no pip it's pip |
|
Tip: power button is software controlled, |
|
unknown6:0 => |
|
|
|
Thanks a lot, should all be fixed now. |
|
hmm..unknown readonly |
|
I looked for something about note: command order is 0 1 2 3 4 5 6 7 8 9 : ; < = with lead 5800 with lead 5b00 |
|
All of those should have been covered by us with the exception of
|
|
yep, perhaps there is something interesting among them. e.g. For "PS" there was |
|
quick_charge was changed on your feedback to screen_info |
|
Yes, that command uses exactly the |
|
|
I am running out of ideas :-( |
|
I have changed the quick_charge parameter to a write only parameter. Can you please check this works? If not, I am going to remove it completely. |
|
not works, sad :( |
One unknown less :-) Also added some potential settings for testing (issue #4). These however need to enabled in the source and recompiled.
|
:-( You can replace UNKNOWN with PS. Then these settings will be compiled into the source and you can check if they are enabled. CAUTION: This is just blindly trying to find the missing setting. |
|
try get all unknown, also try set it - no result. |
|
Looks like unknown160 has triggered a timeout error. After a timeout error the monitor needs some seconds to react again. In the worst case you have to do a plug/unplug power cycle. |
|
Looks like 'grep', PS is not freezed. A little later, I still try to get/set them one at a time. Log without 'grep'. |
|
maybe write test function for all unknown? do
loop |
|
Here's my last idea. unknown190 is supported. |
|
yep, i try it first, no result. |
|
Is the quick charge setting supported in the Windows OSD Creator App? |
|
i dunno, no have windows. |
|
The information is critical. If it is not supported there, there is practically zero chance we find the setting. |
Added a section to readme.md which describes settings which are currently not supported.
#!/bin/sh
#----------------------------------------------------------------------
# Description: Check list unknown values
# Author: John Wehin
# Created at: Fri Apr 24 16:53:13 SAMT 2020
#----------------------------------------------------------------------
#
declare -a StringArray=("unknown160" "unknown190" "unknown1@0" \
"unknown210" "unknown271" "unknown280" \
"unknown435" "unknown440" "unknown450" "unknown470" \
"unknown700" "unknown710" "unknown720" "unknown730" "unknown740" \
"unknown860" "unknown870" "unknown880" "unknown890" "unknown8:0")
SERIAL=$(./msigd -f serial)
echo "==== ---- Check GET ---- ===="
for val in "${StringArray[@]}"; do
echo "--- Check ${val} ---"
CHECK=$(./msigd -f ${val} 2>&1)
CHECK_CODE=$?
SERIAL_CHECK=$(./msigd -f serial)
if [ "$SERIAL" = "$SERIAL_CHECK" ]; then
echo "TIMEOUT: OK -- RESULT: $CHECK_CODE"
else
echo "TIMEOUT: FAIL -- RESULT: $CHECK_CODE"
exit 1
fi
echo -e "$CHECK"
echo "-------------------"
done
echo "==== ---- Check SET ---- ===="
for val in "${StringArray[@]}"; do
echo "--- Check ${val} ---"
CHECK=$(./msigd --${val} 0 2>&1)
CHECK_CODE=$?
SERIAL_CHECK=$(./msigd -f serial)
if [ "$SERIAL" = "$SERIAL_CHECK" ]; then
echo "TIMEOUT: OK -- RESULT: $CHECK_CODE"
else
echo "TIMEOUT: FAIL -- RESULT: $CHECK_CODE"
fi
echo -e "$CHECK"
echo "-------------------"
done |
|
i found how get state :-) try set also get/set without error values 0 or 1 |
|
so unknow310 is quick_charge? |
|
On the MAG series |
|
|
|
On the MAG321 i can read and set unknown210 which on the MAG271 and MAG241 is the black tuner setting - no visible effect or changes to the OSD. Looks like unknown310 (eye saver on MAG) behaves like this on the PS series. The only way understand how to set quick charge would be a Win 10 in a virtualbox. This allows to use wireshark to log the usb communication between the OSD windows app and the monitor. |
Also fixed a bug in displaying values. Modified some "unknown" display.
|
|
|
Updated code and documentation. Thanks a lot! |
|
Closing this now. Adding script provided has been marked in a separate issue. |
Step 1
./msigd --query --info --debugresult
unknown110 : 000Step 2
Press key
Step 3
Wait any time
Step 4
./msigd --query --info --debug
result
unknown110 : 001Step 5
./msigd --query --info --debug
result
unknown110 : 000Resume:
I think “unknown110” means “001” if the button was pressed before checking and reset button state. For sure there is also the ability to configure the action at press of a button
It would be nice if wait_key appeared for scripts and the ability to connect a button like /dev/input
The text was updated successfully, but these errors were encountered: