Please set the camera to Tv mode and execute the following command:

pktriggercord-cli --shutter_speed 1/1000 --status_hex

What is the output? Does it change the shutter speed of the camera?

Hi! I have a similar problem with my K-30 (firmware v 1.01).

I've tried GUI app and it seems, that it did't change some settings. When I tried to get picture, it opened mirror for several seconds and picture was overbright (it showed 9999" on the camera display). Also I noticed that app showed Av mode, but camera was set to Tv.

I've tried to reset all camera settings to the factory values and tried your command. It seems, that it applied 1/1000 from cli, but didn't apply settings from GUI app. Now it shot with (apparently) 1/1000, at least it showed it on camera display. Also, "focus" button had no effect after settings reset.

I tried to:

1. Unplug USB cord and plug it again.
2. Send cli command again.
3. Started GUI app.

Shutter speed setting started to apply but with a huge lag. Though, no focus and wrong mode indicator.

First file (k-30.txt) is before factory reset, others are after your command with different shutter speeds (1/1000, 1/100, 1/30).

k-30.txt
k-30-1.txt
k-30-2.txt
k-30-3.txt

EDIT: I've updated firmware to v 1.06, and it started to work for me. Seems, that it correctly works, when camera is powered on first, in manual mode (M) and with auto-focus (AF.S), also with kit lenses, and USB cord connected after settings on camera changed. Also, seems that gtk version is not convenient to change settings. It would be better, if combobox was used instead of slider for shutter speed etc, because slider sends updates to camera more often, then necessary, returns to the previous position etc, and camera responds too slowly. Probably, cli version is more useful for scripting anyway. @asalamon74 could you please provide several sentences about right camera settings and connection order in the guide?

Lots of issues here

Strange bugs: The original guy who added K-30 support also reported similar things. Shutter speed changing to 9999s, strange exposure modes. If he was not able to fix these bugs (although he had a K-30), I don't think I'll be able to fix the bugs without a K-30. I've updated BUGS file.

Firmware: I also added this fact to the BUGS file

Connection: It really sounds strange because my K-x prefers connecting the USB cable first and turning on the camera later. Also added this info to the BUGS file.

GUI: To tell the truth I don't really like (or use) the GUI. The controls show the values read from the camera (updated every 2 seconds) and allows the user to change the values. Maybe someday I'll reorganize the GUI and eliminate this problem. Or hopefully someone else will do it and send me the patch.

Well, it seems that one can go just so far without official protocol description.

I stopped to play with the program, when instead of performing auto-focus it suddenly cause the camera to zoom in and out so quickly that it jumped on the table and powered off, and won't power on again till I removed battery. I'm afraid such a harsh movement can cause a damage to lenses' drive. Strangely, it executed the same exact command several times before that without an issue... May be timing between commands in sequence matters, don't know.

BTW, how did you crack the protocol? Did you use some software tool to log signals on USB port when executed official program in Windows, or something like that? If this does not require some additional equipment and you can provide some not very complex instruction, I may try to do it myself. I may install Windows XP in the VirtualBox on Ubuntu (if this help), though I have no spare PC to install Windows on it.

Yes, an official documentation would be really helpful Since tethering is not officially supported it is also possible that the firmware has tethering bugs.

My program is a fork of the abandoned PK-Remote probably they used an USB-sniffer originally.

A few guys also reverse engineered the firmware and collected info here.