Support for Samsung GX-1L #36
Comments
|
Samsung GX-1L is basically Pentax *ist DL2, but none of them is supported right know. Adding a new camera requires to add a new line to the camera_models array in I would start be copying the Unfortunately It would be really great if you can add the support. |
|
It actually looks like the GX-1L has been added to camera_models. Unfortunately right now I am seeing issues right at the beginning of the calls. I am attempting to diagnose the issue some but it does not appear to be responding to SCSI calls at all. When testing the response is consistently blank. Any other thoughts on getting any response? The really interesting part is that even though I am getting no response when the LCD changes it tends to make me feel like the camera is hearing something just not saying anything back at this point. Is there a simple way to make very simple calls one by one with some debug information? I am thinking we might be able to find some limited functionality but other calls for status aren't getting anything back. |
|
Does the following output help determine anything? I am unsure exactly what calls are made. pi@raspberrypi:~/Desktop/pktriggercord_PS $ sudo ./pktriggercord-cli --debug Found camera Samsung before connect |
|
Yes, I missed the GX-1L line. I've checked my e-mails,we tried to add support in 2015, but it was not working. Your log shows that the camera is recognized, it's even possible to read some info (like firmware version). Instead of taking a picture, let's start with status reading. What is the debug output of the following command:
|
|
Below is what we have when running pi@raspberrypi:~/Desktop/pktriggercord_PS $ sudo ./pktriggercord-cli --status_hex --debug Found camera Samsung before connect |
|
Note: When running both |
|
I am going down this path a little further and looking into when we are getting an Do you think that is the right direction to investigate? |
|
@tempUser99 A few tips:
|
|
We are indeed getting somewhere now. Although nothing is happening on the camera at least the camera does stay in |
|
@tempUser99 This one actually looks very good. Then program was able to connect to the camera and read the status buffer. Since status parsing is not implemented yet, the fields are not rcorrectly ecognized. You can improve it in two ways:
|
|
What is the correct procedure to attempt to take the picture without the buffer? I will see what I can do to create a parser. |
|
The following command should take a single picture and save it: The output file format will be most likely a pef for your model. Maybe a dng. |
|
I copied over The camera changes from Also interestingly, after running this command a dialog box pops up on the desktop of the raspberry pi running this saying "No object for D-Bus interface". |
|
@asalamon74 Do you have any updated thoughts based on the last output? I have been making a few modifications to try to test but nothing appears to be helpful. |
|
It seems to me that the shutter command (this command tells the camera to take a picture) is unrecognised, and gives and error: This command is the same for all the camera models, so I don't really think we need to change this part of the code. Maybe the camera initialization code should be different. You may try to change the code, but this is only a trial and error approach. For some camera models, upgrading the firmware was helpful. According to the logs, your are using firmare 1.00 (or firmware version reading is not working), upgrading it might help. |
|
I managed to get what looks like the only available copy of 1.02 firmware and I upgraded. Now this is all I see when running:
I am working on getting passed this point, any thoughts? |
|
That is quite strange. After printing the I'll add a few debug messages soon. |
|
I've added more debug messages to the code. @tempUser99 can you please try it again. |
|
I finally was able to get connected again and ran a test with the new debug messages you added. See attached below. |
|
Additionally when attempting to run |
|
@tempUser99 The strange error of printing out only the driveNum disappeared, right now it's possible to connect to the camera again. Unfortunately I don't see too much difference in the logs. Status buffer reading works, taking a picture gives the same |
|
I ran a few more tests, without changing anything to try to better understand what is happening.
|
|
Did you ever proceed in getting this to work? |
|
No update on this issue. *istDL2 is basically the same as GX-1L, so they should behave similarly. |
|
OK - so I did som research: I tried the new Pentax SCSI protocol instead of the old one and - the shutter fires. Now I need to figure out how to transfer an image, this still doesn't work. For now, it reports the following: and this repeats until pslr_disconnect() is called. The entry in pslr_model.c now looks like the following: |
|
Actually, my settings are similar to the K110D. I couldn't find any references as to why the K110D doesn't work, only that it's not working. Do you know more? |
|
@andyboeh I don't remember the exact problem with K110D. Maybe you could try to change 'bufmask_command' to 'true'. |
I am looking at a GX-1L and attempting to get it up and running.
What can I do to help out and get support for this unit?
I have tried a few things and found the first issue begins when attempting to
get_drive_infofrompslr_scsi_linux.c. It appears lines 138-144 are when the check fails on the GX-1L.If we are able to pass those lines successfully it does appears the camera with change from 'PC' on the LED to the normal readout.
Let me know what I can do to help contribute.
The text was updated successfully, but these errors were encountered: