Skip to content
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

k10d only gets 288 bytes status? #23

Closed
msmeissn opened this issue Mar 27, 2017 · 5 comments
Closed

k10d only gets 288 bytes status? #23

msmeissn opened this issue Mar 27, 2017 · 5 comments

Comments

@msmeissn
Copy link
Contributor

I bought a K10D and it reports only 288 byte status, instead of 392 bytes.

I adjusted the table, but the ipslr_status_parse_k10d function seems to parse more than 288 bytes?

@msmeissn
Copy link
Contributor Author

./pktriggercord-cli --debug --status_hex > k10d.log

k10d.txt

@asalamon74
Copy link
Owner

I'm quite sure that 392 is the correct number. Several users reported that pktriggercord handles K10D correctly and the parse function also requires more that 288 bytes.

The official Pentax Remote Assistant 3 requires firmware version 1.20 or later.

What is your firmware version? I've just commited a new feature pktriggercord-cli --read_firmware_version might work for K10D and print out the firmware version. Can you upgrade to 1.20 or later?

Someone already reported this error two years ago, I suggested firmware upgrade but got no response.

@msmeissn
Copy link
Contributor Author

yeah, i just bought it used and did not update the firmware (yet).

Firmware version: 1.00.00.07

@msmeissn
Copy link
Contributor Author

I updated the firmware to 1.31.00.19 now and the size is now 392 bytes

asalamon74 added a commit that referenced this issue Mar 29, 2017
More details can be found here: #23
@asalamon74
Copy link
Owner

I've added this info to the webpage and to README.md
Thanks for testing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants