-
Notifications
You must be signed in to change notification settings - Fork 39
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
Support for K-1? #10
Comments
Someone was planning to add support but haven't sent me the patch yet. If you're ready to test it I can try to add support. What operating system do you use? |
Hi, I would be glad to help. I am using openSuSE Leap 42.1. Best Regards, Karsten
|
I've commited limited support for K-1, please clone the latest code and compile it. The program should recognize the camera. First I suggest to test the following command, please copy the output here: pktriggercord-cli --status_hex --debug |
Hi, here is the output using the windows version I found here.
|
The latest release (0.84.00) does not support K-1, only the development (0.84.01) version. Since it's quite difficult to compile the program for windows I attach a windows test version here. |
Thanks. This is the output:
|
I am on a business trip until Friday and don't have the camera with me. Best regards, Karsten |
I've modified the code, I attach the new windows test version. Please execute the same command and also give me the following information:
|
Hi Folks, I just gave it a trial. It seems it doesn't recognizes the camera. `
DVD RW AD-7700H
diff: 0.000357
DVD RW AD-7700H
diff: 1.000800
DVD RW AD-7700H
diff: 2.001229 ` |
The camera should be set to MSC mode. Can you test it as root? |
That is the output using the new windows version you posted above:
The lens used is an 35 mm prime lens : DA 35mm F2.8 limited. The new code has another interesting effect: Using MSC mode. |
@Knubbel Getting better. I attach a new version. A few important fields still need to be found. Please set the camera to M mode and shutter speed to 1/1000 and execute the same command, after that to the same for 1/2000. The difference should show the place of the shutter speed field. PcS: Similar thing has been reported for several cameras with a top LCD. My K-x has no such thing so I cannot debug it. |
That is the output at 1/1000 (setting the camera must be done prior to pluging in the USB cable as the camera is inaccesible afterwards in PC-Sync mode). pktriggercord-cli.exe --status_hex --debug
|
And now again in M mode but with shutter at 1/2000:
|
Just as a side comment: |
@Knubbel I've fixed a few more things, hopefully most of the important fields will be parser correctly in this version. Plase test it. I cannot find the value 65534 in the status buffer. You might test taking a picture using the following command: ./pktriggercord-cli --debug --file_format dng -o test1.dng |
Okay, did it as root and in MSC-Mode.
|
Here is my result using the latest windows exe posted above:
|
Then I tried taking an picture using the command
It actually did trigger the shutter, but the output in the command line window soon starts rushing by neverendingly. Below is the beginning of it, later it seems to just repeat a couple of lines.
|
@Knubbel Hmm. Bufmask looks empty. I suggest to change the camera to bracketing mode (3 pictures, +- 1EV) and check the status reading after that. If the program does not recognize bracketing mode I'll try to fix it. If the camera recognizes bracketing mode try to take 3 pictures ( --frames 3 ). If it takes 3 pictures and downloads all the pictures after that. If i really takes 3 pictures then the download is buggy. If it takes only 1 picture the exposure is buggy. |
I set the camera to Av mode and to 3 image bracketing. This here is what I get for
|
Then I triggered it using the same command I used last time.
|
@Knubbel Sorry for the slow response. The program correctly recognizes the bracketing mode. Could you please add --frames 3 to the last command? Without that the camera only takes one picture even if the bracketing mode is set. pktriggercord-cli.exe --debug --file_format dng --frames 3 -o test2.dng |
Hi. It is worth mentioning that not a single of the 9 shots is saved on my HDD, it just creates a single zero Byte file named "test3.dng-0000.dng" And again I had to cancel the command line window as it continued neverendingly. Here is the output:
|
Hi, I did do the test on Linux. At the beginning the display is off. Giving the display flashes three times. With the third flash it does one shot. I did do the test with and without mounting the sdcards. Makes no difference. Hope this helps Karsten |
@Knubbel It seems to me Pentax K-1 handles bracketing a different way. On my K-x (after I set bracketing mode) I have to send 3 shutter command to take the three pictures. That's why I suggested --frames 3. K-1 tries to take all the 3 pictures after the first command. Unfortunately I cannot find the bufmask (the field that shows the status of the camera buffers). And downloading the first buffer saves nothing (it opens the file and waits forever). My guess: After the shutter command the camera does not save the image into the buffer. I don't know the reason. Maybe someone later will solve it and send a patch. |
@horemachet Well at least it shows that it works the same for Linux and Windows, so it's not an OS-specific issue. |
Any news on this? |
@horemachet No |
Green button is not working for newer cameras. User mode selector is a read-only field, it is not possible to change it. The 30s shutter speed looks quite bad. What if you first turn on the camera and connect only to the computer later, it solved the same program for an other camera model. If it's not working, please execute
and attach the output here. |
Nope, still doesn't work properly. |
Hi. |
@SM3NSE I've fixed a bug. Here is a new version: |
Can't see any difference. |
@SM3NSE I think I've found the problem: |
"After you take the first image the program should show a thumbnail and a bigger preview." |
@SM3NSE I've fixed a few bugs. Here is the updated version: |
Bulb wait thing is now gone. "After you take the first image the program should show a thumbnail and a bigger preview." Focus button doesn't work. |
I own a K-1 as well and would like to help. Just downloaded the latest zip from this thread and tried it under windows. pktriggercord-cli: unknown option -- servermode (Yes, two times) What else can I do? |
Just downloaded it. Looks pretty good. |
I've modified the code, now it adds the extension automatically. Focus: The log shows no error, probably the camera just ignores the command. Second image not shown: Can you send the debug log for the following process (GUI): Take the first shot, Take the second shot. Do not change anything in between, do not delete the image... |
I've fixed the double unknown option bug. Servermode is not supported in Windows. I've modified the program, now it will print out an error message instead of the general unknown option message. Yes, sometimes it's possible to freeze the camera, removing the battery solves the problem. As you see, K-1 is not fully working, if you send debug log (using the latest zip I've just attached) I'll check it. |
@ ASALOMAN: I´ve got myself a log by invoking pktriggercord --debug 2>status.log and pushing "Take picture" The result: That´s okay for you? Or do you want something else? |
@ti59 Could you see the thumbnail or the preview? The log looks quite strange. After taking the second image the buffer mask only shows 1 image. What if you first turn on the camera and connect it to the PC only later. Does it help? K-70 has a similar limitation, I've created a workaround for that model, but it's not too good, because you have to delete the image before you take the next one. I'll turn on the same for K-1 if changing the connection order does not help. |
@ti59 Could you see the thumbnail or the preview?
Nope. Nothing. No preview.
To prevent an unnecessarily long log I connected the camera, then switched it on and then started the software.
The log looks quite strange. After taking the second image the buffer mask only shows 1 image. What if you first turn on the camera and connect it to the PC only later. Does it help?
Will try over the weekend.
K-70 has a similar limitation, I've created a workaround for that model, but it's not too good, because you have to delete the image before you take the next one. I'll turn on the same for K-1 if changing the connection order does not help.
Interesting enough the Pentax API seems to suffer from similar problems. I´ve tried the sample and while it stores JPGs at least
it doesn´t let me adjust any of the settings and has a tendency to freeze after a while.
_And_ it takes forever (20+ seconds) to connect.
What I would really like to do with the pktriggercord is automatic focus stacking with snails that we have in the woods around here.
I was hoping that it would be possible to change focus programmatically.
…--
Mit freundlichen Grüssen
Laterne Informations-Technik M.Hildebrandt mailto:martin.Hildebrandt@laterne.de
Laterne Informations-Technik M. Hildebrandt e.K.
Bahnhofstraße 35 - 37
31655 Stadthagen
Telefon: 05721 6996
Telefax: 05721 6512
E-Mail : mailto:laterne@laterne.de
Ust.-IdNr.: DE 116507299
Registergericht: Amtsgericht Stadthagen Abt. A
Registernummer: HR 1584
|
OK, as requested by mail I´ve switched on the camera first and then connected USB. The result ist different. |
@ti59 It seems to me if you turn on the camera first, K-1 works quite like K-70. I'm working on some workaround to better support K-70, hopefully it will also work for K-1. Unfortunately it will be quite limited, since we need to delete the first image before taking the second... If you'd like to use it for focus stacking I suggest to use the command line version, it's much better for that. It's quite easy to create timelapse videos. Programmatically changing the focus is not possible (at least no one found the command yet). I'm using a macro focusing rail instead. It is not automatic (although you can buy rails which can be connected to the computer) but gives good result. |
If one could use the 33 focus areas and change them programmatically that would be sufficient. Also of course the camera can change focus obviously. Could be an interesting quest to dig into the firmware to make it happen.:) |
@ti59 Here is our current knowledge about the protocol: http://pktriggercord.melda.info/pentax_scsi_protocol.html There is no command to focus on a specific distance (that would be the best for focus stacking) but command [18 07] can be used to specify the selected AF point. It works for 11 AF-point cameras using the GUI. You click on an AF point than click on focus and the camera will focus on that point. Without live preview it's not too useful to tell you the truth. Command line version does not yet support it, only af selection mode can be selected using that version. It would not be too difficult to add support for this. Right now we send a 32-bit number, 11 bit specifies the selected AF points. K-1 has 33 AF points, I think you already see the problem there. :) If you are using pktriggercord-cli --status_hex after manually selecting different AF points on the camera, you might find the field which stores the selected AF point information, and you might be able to decode it. |
Status buffer contains the selected_af_point, 5 different value for the 5 points you have selected. I've modified to program to print out the numerical value of the selected af point for K-1 if you use I've also modified the program. It was possible to specify the af selection mode using |
I can't see thumbnail or the preview . (shooting and focusing on k-1 no broblem) pktriggercord run on terminal, and click Focus or take picture. $ pktriggercord pslr.c:954:ipslr_next_segment(p) failed: 3 I use mint 19, and installed use apt install pktriggercord bia ppa:dhor/myway. |
@LibertSin What version of the program do you use? If you want to test K-1 support I suggest using the latest version (0.85.00). |
Hello. I'm back. |
@SM3NSE Not much progress lately. In the meantime 0.85.00 was released, so it's possible to test that version, no need for downloading special devel versions. |
Hi Folks,
are there any plans to support the new Pentax K-1 already?
Do you neet some testing support?
Regards,
Karsten
The text was updated successfully, but these errors were encountered: