Hi,
I have an old RPi 2 plus V2.1 with fresh install of current day bullseye 24/10/22, (kernel says v7.x) that I am trying to find useful employment for. I have hit on a project involving a rotary encoder. I have determined that using the dt overlay, to effect access via the kernel directly, is the way to go.
Research has led me to an article HERE as a template.
I have endeavoured to follow the directions in the article, but don't get the authors result. Perhaps I have missed something and cannot see my omission.
I have contacted the article's author, and he tells me that my Pi 2 plus v2.1 with fresh install of current day bullseye, (kernel says v7.x), is likely further along the Pi evolutionary scale, than the hardware he used, so I doubt that it is a hardware or O/S limitation of my particular Pi.
I suspect that a dependency is missing, although I get no error messages to that effect.
In the article section where the author shows his results under the title "Which should produce output along these lines:", he shows:
Rotary encoder device: rotary@14
Event: event at 1603019654.750255, code 00, type 02, val 01
Position: 1
Event: event at 1603019654.750255, code 00, type 00, val 00
Event: event at 1603019654.806492, code 00, type 02, val 01
Position: 2
Event: event at 1603019654.806492, code 00, type 00, val 00
Event: event at 1603019654.949199, code 00, type 02, val 01
Position: 3
Event: event at 1603019654.949199, code 00, type 00, val 00
Event: event at 1603019655.423506, code 00, type 02, val -1
Position: 2
etc.
I get only:
Rotary encoder device: rotary@14
and no more, despite any amount of rotation of the connected rotary encoder and copious amounts of patience waiting for more.
Thoughts or suggestions as to what I am missing?
Thanks,
Brian H.
I have an old RPi 2 plus V2.1 with fresh install of current day bullseye 24/10/22, (kernel says v7.x) that I am trying to find useful employment for. I have hit on a project involving a rotary encoder. I have determined that using the dt overlay, to effect access via the kernel directly, is the way to go.
Research has led me to an article HERE as a template.
I have endeavoured to follow the directions in the article, but don't get the authors result. Perhaps I have missed something and cannot see my omission.
I have contacted the article's author, and he tells me that my Pi 2 plus v2.1 with fresh install of current day bullseye, (kernel says v7.x), is likely further along the Pi evolutionary scale, than the hardware he used, so I doubt that it is a hardware or O/S limitation of my particular Pi.
I suspect that a dependency is missing, although I get no error messages to that effect.
In the article section where the author shows his results under the title "Which should produce output along these lines:", he shows:
Rotary encoder device: rotary@14
Event: event at 1603019654.750255, code 00, type 02, val 01
Position: 1
Event: event at 1603019654.750255, code 00, type 00, val 00
Event: event at 1603019654.806492, code 00, type 02, val 01
Position: 2
Event: event at 1603019654.806492, code 00, type 00, val 00
Event: event at 1603019654.949199, code 00, type 02, val 01
Position: 3
Event: event at 1603019654.949199, code 00, type 00, val 00
Event: event at 1603019655.423506, code 00, type 02, val -1
Position: 2
etc.
I get only:
Rotary encoder device: rotary@14
and no more, despite any amount of rotation of the connected rotary encoder and copious amounts of patience waiting for more.
Thoughts or suggestions as to what I am missing?
Thanks,
Brian H.
Statistics: Posted by hambonius — Sat Jan 04, 2025 7:54 pm