11-22-2022, 05:26 AM
Ummm.
This pin #5 is apparently in INPUT mode since the script is reading its state (and because the table in the script’s header says the pin is “IN”). I don’t know squat about wiringpi but I’d be surprised if the gpio command automagically forces a change in a pin’s mode when you write to it.
Secondly, if pin #5 is in INPUT mode, then the HAT must be driving it, not sensing it. Not so sure I’d want to be experimenting driving in reverse using my Pi’s GPIO pins.
I was thinking of experimenting in terms of using a breadboard with switches and current-limiting resistors to see what other pins do (like that mysterious “disk status” pin called out in the parameters table in the HAT’s Wiki entry). But I’ve become cautious that way—I’m too old to be doing smoke tests like I used to.
Just my 2-cents worth. If I’m wrong, it wouldn’t be the first time
Regards,
Kent
This pin #5 is apparently in INPUT mode since the script is reading its state (and because the table in the script’s header says the pin is “IN”). I don’t know squat about wiringpi but I’d be surprised if the gpio command automagically forces a change in a pin’s mode when you write to it.
Secondly, if pin #5 is in INPUT mode, then the HAT must be driving it, not sensing it. Not so sure I’d want to be experimenting driving in reverse using my Pi’s GPIO pins.
I was thinking of experimenting in terms of using a breadboard with switches and current-limiting resistors to see what other pins do (like that mysterious “disk status” pin called out in the parameters table in the HAT’s Wiki entry). But I’ve become cautious that way—I’m too old to be doing smoke tests like I used to.
Just my 2-cents worth. If I’m wrong, it wouldn’t be the first time
Regards,
Kent
