GPIO rotary volume

[Substring]

@dh04000 Added the python code. You can't do as in the source because it's a gist using several files

[dh04000]

@Substring

Thank you! Now all I have to do is to point out, in the Tweaks section, how to change the gpio, volume increments, and volume range in the script, and the guide is complete.

[Substring]

@dh04000 Thank you very much for your contribution

[dh04000]

@Substring No probs. Thank you and the other Recalbox Mods/Devs for the helping make this work! There is still one more issue though, I need independent verification that this guide works as I wrote it. Would you be able to test it with your rotary encoder?

[Substring]

@dh04000 not before a long time, the main focus for now is fixing bugs for the stable 4.1

[dh04000]

@Substring A long time has indeed passed. Congrats on the 4.1 release! I've been successfully using this gpio program on my arcade machine for the last 5 months. Would you be willing to test the guide I wrote up with your rotary encoder and verify it? I want to finalize my guide in-case someone else wants to set up their own rotary encoder.

[Substring]

@dh04000 Hey !

For now, I just can't test, too many support requests with 4.1

[dh04000]

@substring said in GPIO rotary volume:

@dh04000 Hey !

For now, I just can't test, too many support requests with 4.1

I just bought a Raspberry pi 3, so I need to do a fresh install of Recalbox anyway. I'll use my guide as written, and if the encoder works, I'll consider that the "verification" that my guide works. I'll report back later with the result.

[Substring]

@dh04000 let's do it that way ! Enjoy Recalbox 4.1

[dh04000]

@Substring Well I have good news and bad news.

My guide was 95% successful in guide myself to reinstall gpio rotary encoder support. BUT, when I got to step 4), nano refused to save my changes, citing that I didn't have write permission, even though I had used "mount -o remount, rw /boot" in step 2). I changed the mounting in step 2) too "mount -o remount, rw /" and then I preceded as normal. The rest of my guide worked perfectly.

I realize though, its not a good idea to tell users to do "mount -o remount, rw /". Any idea what happened on my recalbox 4.1 install, that didn't happen on my 4.0 install? "mount -o remount, rw /boot" used to work....

[Substring]

@dh04000 it does work, but maybe you didn't need to edit any file in /boot

I've sent @OyyoDams on a quest for a big python script to manage anything we can do with GPIO configured through an ini file, I notify him so that he gets the code and integrates it to his work

[dh04000]

@substring said in GPIO rotary volume:

@dh04000 it does work, but maybe you didn't need to edit any file in /boot

I've sent @OyyoDams on a quest for a big python script to manage anything we can do with GPIO configured through an ini file, I notify him so that he gets the code and integrates it to his work

Ohhhhhhhh, since the python script is found in /recalbox, then my guide SHOULD read "mount -o remount, rw /recalbox". Correct?

[Substring]

@dh04000 absolutely !

[dh04000]

@substring said in GPIO rotary volume:

I've sent @OyyoDams on a quest for a big python script to manage anything we can do with GPIO configured through an ini file, I notify him so that he gets the code and integrates it to his work

What does this mean?

Also, my guide is complete and I've removed the (Work in Progress) label off the mini-how-to page. Cheers.

[Substring]

@dh04000 It means that he is writing a configurable daemon that will react on GPIO events. And it should handle that volume knob once done.

[OyyoDams]

Hi all,

Yes the project is on a good way. I'll keep you informed

[dh04000]

@substring said in GPIO rotary volume:

@dh04000 It means that he is writing a configurable daemon that will react on GPIO events. And it should handle that volume knob once done.

Sounds good. @OyyoDams I'll test it when its done, just give me a heads up.