Pentax K-3 support?

Status: Beta

Brought to you by: asalamon

This project can now be found here.

#3 Pentax K-3 support?

Milestone: Next_Release_(example)

Status: open

Owner: nobody

Labels: None

Priority: 5

Updated: 2014-03-20

Created: 2014-03-02

Creator: PhXx

Private: No

Is there any hope of adding support for Pentax K-3?
I own the camera. Can I somehow help with this?

Discussion

Andras Salamon - 2014-03-10

I can create a test version. What operating system do you use?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

PhXx - 2014-03-10

I'm currently using ubuntu 13.10.
Also checked out the svn repository, builds and starts up fine (don't have another camera to test...)

Last edit: PhXx 2014-03-11

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Andras Salamon - 2014-03-16
  
  I've added limited support. Could you please checkout the latest SVN version and test it. Attach the output of:
  
  pktriggercord-cli --status_hex
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

PhXx - 2014-03-16

sure,
at first,
./pktriggercord-cli --status_hex
gave no result at all. so I tried:

./pktriggercord-cli --debug

Debug messaging is now enabled.
./pktriggercord-cli 0.81.03
model (null)
device (null)
Checking drive: sg0 ATA
INTEL ...

Checking drive: sg1 RICOHIMG
DSC_K-3

Checking drive: sg2 RICOHIMG
DSC_K-3

camera not found

and repeating...
so I figured that the camera wasn't recognized and added "RICOHIMG" to the list of valid_vendors. this resulted in

./pktriggercord-cli --status_hex
Segmentation fault (core dumped)

and

./pktriggercord-cli --debug
Debug messaging is now enabled.
./pktriggercord-cli 0.81.03
model (null)
device (null)
Checking drive: sg0 ATA
INTEL ...

Checking drive: sg1 RICOHIMG
DSC_K-3

Found camera RICOHIMG
DSC_K-3

id of the camera: c02f0100
read 452 bytes
Segmentation fault (core dumped)

not sure what this means, camera id seems strange to me.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Andras Salamon - 2014-03-16

I've modified the code. Please attach the output of:

pktriggercord-cli --debug --status_hex

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- PhXx - 2014-03-16
  
  ./pktriggercord-cli --debug --status_hex
  Debug messaging is now enabled.
  ./pktriggercord-cli 0.81.03
  model (null)
  device (null)
  Checking drive: sg0 ATA
  INTEL ...
  
  Checking drive: sg1 RICOHIMG
  DSC_K-3
  
  Found camera RICOHIMG
  DSC_K-3
  
  id of the camera: c02f0100
  not found
  read 452 bytes
  Segmentation fault (core dumped)
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
  - PhXx - 2014-03-16
    
    if I change the camera id in the camera_models array to 0xc02f0100, I get
    
    ./pktriggercord-cli --debug --status_hex
    Debug messaging is now enabled.
    ./pktriggercord-cli 0.81.03
    model (null)
    device (null)
    Checking drive: sg0 ATA
    INTEL ...
    
    Checking drive: sg1 RICOHIMG
    DSC_K-3
    
    Found camera RICOHIMG
    DSC_K-3
    
    id of the camera: c02f0100
    found 23
    read 452 bytes
    expected_bufsize: 0
    init bufmask=0x0
    
    and then it gets stuck in the while-loop in get_status(int fd) in pslr.c
    
    btw, the second "drive" gives the same camera id.
    
    If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Andras Salamon - 2014-03-17

What about now?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- PhXx - 2014-03-17
  
  ./pktriggercord-cli --debug --status_hex
  Debug messaging is now enabled.
  ./pktriggercord-cli 0.81.03
  model (null)
  device (null)
  Checking drive: sg0 ATA
  INTEL ...
  
  Checking drive: sg1 RICOHIMG
  DSC_K-3
  
  Found camera RICOHIMG
  DSC_K-3
  
  before connect
  get_status->
  0x0000 | 00 00 00 00 00 00 00 01
  get_status->
  0x0000 | 00 00 00 00 00 00 00 01
  get_status->
  0x0000 | 00 00 00 00 00 00 00 01
  get_status->
  0x0000 | 00 00 00 00 00 00 00 01
  get_status->
  0x0000 | 00 00 00 00 00 00 00 01
  get_status->
  0x0000 | 00 00 00 00 00 00 00 00
  id of the camera: c02f0100
  id: c02f0100, swappedid: 12fc0
  found 23
  read 452 bytes
  expected_bufsize: 0
  init bufmask=0x0
  get_status->
  0x0000 | 00 00 00 00 00 00 00 83
  get_status->
  0x0000 | 00 00 00 00 00 00 00 83
  get_status->
  0x0000 | 00 00 00 00 00 00 00 83
  
  and the two line are repeating until I quit using Ctrl-c.
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

PhXx - 2014-03-17

Last edit: PhXx 2014-03-17

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Andras Salamon - 2014-03-20

Probably the communication protocolo of K-3 differs a bit. I can't fix it, but leave the code as is. Maybe later someone else will fix it.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Log in to post a comment.