SX260 HS Porting Thread - page 64 - DryOS Development - CHDK Forum

SX260 HS Porting Thread

  • 642 Replies
  • 151995 Views
*

Online reyalp

  • ******
  • 13400
Re: SX260 HS Porting Thread
« Reply #630 on: 05 / June / 2020, 22:13:03 »
Advertisements
These:
Code: [Select]
> =post_levent_to_ui("RotateJogDialLeft",2)
> =post_levent_to_ui("RotateJogDialRight",2)
work just fine
Great, thanks. I updated the wheel functions in autobuild 5516. If you can confirm that work, that would be appreciated
Don't forget what the H stands for.

*

Offline koshy

  • *****
  • 1063
Re: SX260 HS Porting Thread
« Reply #631 on: 06 / June / 2020, 16:14:10 »
Great, thanks. I updated the wheel functions in autobuild 5516. If you can confirm that work, that would be appreciated

With 5516 autobuild I tried the following:
Code: [Select]
> =wheel_left()
> =wheel_right()
> =post_levent_to_ui("RotateJogDialLeft",2)
> =post_levent_to_ui("RotateJogDialRight",2)
All as before, upper two no effect, lower two work.
Same procedure as yesterday: CHDKPTP / Rec mode / Canon Menu / go to middle of something / see if up and down kick in as they should.
Koshy had a little ELPH which wasn't white as snow but everywhere that Koshy went the ELPH was sure to go. (actually an SD, but that detail ruins the rhyme...)

*

Online reyalp

  • ******
  • 13400
Re: SX260 HS Porting Thread
« Reply #632 on: 06 / June / 2020, 16:42:22 »
Same procedure as yesterday: CHDKPTP / Rec mode / Canon Menu / go to middle of something / see if up and down kick in as they should.
:blink:
You're sure it's the updated build? I'm a bit surprised since the change was a fix used on a number of other cameras, and caefix seemed to confirm it worked or hanged something (though I find their posts quite difficult to understand)

Anyway, if you're sure, can you try
=post_levent_for_npt("RotateJogDialLeft",2)
=post_levent_for_npt("RotateJogDialRight",2)

(above is _for_npt, rather than _to_ui. The wheel_ code actually uses the former, although seem to be interchangeable in most cases))

Also try =wheel_left() and =wheel_right() with the Av or Tv control active, instead of the menu.

Thanks again for all your help :)
Don't forget what the H stands for.

*

Offline koshy

  • *****
  • 1063
Re: SX260 HS Porting Thread
« Reply #633 on: 06 / June / 2020, 19:19:35 »
:blink: You're sure it's the updated build?
Who's ever sure. I did re-format re-download re-instate and yes it's still the same.

was a fix used on a number of other cameras
If you want we can test some.

Anyway, if you're sure, can you try
=post_levent_for_npt("RotateJogDialLeft",2)
=post_levent_for_npt("RotateJogDialRight",2)

(above is _for_npt, rather than _to_ui. The wheel_ code actually uses the former, although seem to be interchangeable in most cases))
There we have it, only _to_ui does anything.

Also try =wheel_left() and =wheel_right() with the Av or Tv control active, instead of the menu.
I did, none but _to_ui does do anything there either.
Thanks again for all your help :)
You're very welcome, I enjoy this; feel free to use the "ping" method any time. I'm set up to be notified by Email.
I didn't manage to be around as much as I might have liked to lately.
Koshy had a little ELPH which wasn't white as snow but everywhere that Koshy went the ELPH was sure to go. (actually an SD, but that detail ruins the rhyme...)


*

Online reyalp

  • ******
  • 13400
Re: SX260 HS Porting Thread
« Reply #634 on: 06 / June / 2020, 20:09:01 »
Weird. A few other cams do use _to_ui.

Two things that might help understand this better:
1) With the 5516 build, try the attached script without USB connected. Clicking left or right on the d pad send wheel up / wheel down. Goal is to if _for_npt failing is some kind of interaction with PTP.

2) With PTP you check if using 1 instead of 2 works, like =post_levent_to_ui("RotateJogDialRight",1)?

in that past we found some cameras needed 2, which is the first fix I tried

Finally, the attached build uses _to_ui, 2. Confirm if wheel_left and wheel_right work.
Don't forget what the H stands for.

*

Offline koshy

  • *****
  • 1063
Re: SX260 HS Porting Thread
« Reply #635 on: 07 / June / 2020, 19:33:01 »
1) With the 5516 build, try the attached script without USB connected. Clicking left or right on the d pad send wheel up / wheel down. Goal is to if _for_npt failing is some kind of interaction with PTP.
I might be missing something with that. presses to inner direction pad with macro and flash etc. give "key up", "key right", "key down", "key left" messages as do presses on the actual jogdial surrounding. Rolling the dial does nothing but goes through to the Canon FW and adjusts exposure time for example. Was that what I was supposed to try?
2) With PTP you check if using 1 instead of 2 works, like =post_levent_to_ui("RotateJogDialRight",1)?
in that past we found some cameras needed 2, which is the first fix I tried
This will be what you seek I guess.
These both work:
Code: [Select]
=post_levent_to_ui("RotateJogDialRight",1)
=post_levent_to_ui("RotateJogDialRight",2)
This one works:
Code: [Select]
=post_levent_for_npt("RotateJogDialRight",1)
This one does not:
Code: [Select]
=post_levent_for_npt("RotateJogDialRight",2)So they are different...
Finally, the attached build uses _to_ui, 2. Confirm if wheel_left and wheel_right work.
Didn't try that yet because of the 1 is working business above.
Koshy had a little ELPH which wasn't white as snow but everywhere that Koshy went the ELPH was sure to go. (actually an SD, but that detail ruins the rhyme...)

*

Online reyalp

  • ******
  • 13400
Re: SX260 HS Porting Thread
« Reply #636 on: 07 / June / 2020, 19:45:01 »
I might be missing something with that. presses to inner direction pad with macro and flash etc. give "key up", "key right", "key down", "key left" messages as do presses on the actual jogdial surrounding. Rolling the dial does nothing but goes through to the Canon FW and adjusts exposure time for example. Was that what I was supposed to try?
When you click key left and key right, it calls wheel_left() and wheel_right(). What I want to know is if those cause the Canon firmware to respond as if the wheel has been used.

So, put the camera in a state where the wheel would do something (menu, M, Av, Tv), run the script, click left and right.

Quote
This one works:
Code: [Select]
=post_levent_for_npt("RotateJogDialRight",1)
This one does not:
Code: [Select]
=post_levent_for_npt("RotateJogDialRight",2)So they are different...
:blink:
The original wheel_left / wheel_right that didn't work (tested in https://chdk.setepontos.com/index.php?topic=7889.msg143559#msg143559) code should have been equivalent to =post_levent_for_npt("RotateJogDialRight",1)
Don't forget what the H stands for.

*

Offline koshy

  • *****
  • 1063
Re: SX260 HS Porting Thread
« Reply #637 on: 07 / June / 2020, 20:04:38 »
:blink:
The original wheel_left / wheel_right that didn't work (tested in https://chdk.setepontos.com/index.php?topic=7889.msg143559#msg143559) code should have been equivalent to =post_levent_for_npt("RotateJogDialRight",1)
That might have been my bad, I tried with what was on the camera. That was sx260hs-101a-1.5.0-5296-full. With it both _to_ui (1,2) work while both _for_ntp fail.
Koshy had a little ELPH which wasn't white as snow but everywhere that Koshy went the ELPH was sure to go. (actually an SD, but that detail ruins the rhyme...)


*

Offline koshy

  • *****
  • 1063
Re: SX260 HS Porting Thread
« Reply #638 on: 07 / June / 2020, 20:13:24 »
When you click key left and key right, it calls wheel_left() and wheel_right(). What I want to know is if those cause the Canon firmware to respond as if the wheel has been used.
So, put the camera in a state where the wheel would do something (menu, M, Av, Tv), run the script, click left and right.
Well, up and down should work normally but they all don't get through to the Canon FW. All I get is the script's up/down/left/right text output. Actual jog dial operation gets through and moves the focus on Canon Menu up and down for example.
Koshy had a little ELPH which wasn't white as snow but everywhere that Koshy went the ELPH was sure to go. (actually an SD, but that detail ruins the rhyme...)

*

Online reyalp

  • ******
  • 13400
Re: SX260 HS Porting Thread
« Reply #639 on: 07 / June / 2020, 20:32:29 »
That might have been my bad, I tried with what was on the camera. That was sx260hs-101a-1.5.0-5296-full. With it both _to_ui (1,2) work while both _for_ntp fail.
OK, so the bottom line is _to_ui appears to work in all known cases?

Which build you run shouldn't affect the various =post_levent_... tests, those go directly to the firmware (unless there's some other bug elsewhere, but it's pretty simple)

The script wheel_left / wheel_right functions are implemented using some permutation of post_levent_* and the final parameter being 1 or 2.

Well, up and down should work normally but they all don't get through to the Canon FW. All I get is the script's up/down/left/right text output. Actual jog dial operation gets through and moves the focus on Canon Menu up and down for example.
Left and right should print the name, and make the firmware act as if the wheel were turned, by calling wheel_left and wheel_right. The different builds have different wheel_left and wheel_right implementations.

I want to know which implementation works. What build was the above using?

The other keys like up and down should not do anything other than print the name, and actual wheel inputs are not relevant.
Don't forget what the H stands for.

 

Related Topics