Closed Barzille closed 1 year ago
Did you test, if the RPi can be started again with the on off shim after you shut down?
Yes. That’s not working as it is still somehow powered
Do you use a gpio button for shutdown command or the button on the onoff shim?
At first the onoff shim button. Now I connected a push button to the shim -> same behaviour
But this is only the trigger as I mentioned above the shutdown command itself results in the same outcome
When I power the RPi via direct current connection and not via the onOff Shim it has the same behavior (red light stays on), so it seems to me that the shim is not cutting the power connection, maybe it's defect. I have ordered a new one and will let you know once I checked that.
And btw is this my clean shutdown config for the shim:
# Config for cleanshutd
# Commented out values will be reverted to defaults,
# and may not work on any given board.
# OnOff SHIM uses trigger 17 and poweroff 4
# Zero Lipo uses trigger 4 and poweroff off
# pHAT BEAT uses trigger 12 and powerof off
# Default values are trigger 4 and poweroff off
daemon_active=1
trigger_pin=17
led_pin=17
poweroff_pin=4
hold_time=2
shutdown_delay=0
polling_rate=1
Unfortunately my Phoniebox w OnOffShim has a hardware defect, so I can’t check. Will get back to you as soon as I tested it.
Does this work now?
I haven’t received the new one yet
I just tried with a new shim, same behavior. Is there anything I could check or look for in special?
btw this is my gpio_setting.ini
[DEFAULT]
enabled: True
[VolumeControl]
enabled: True
Type: TwoButtonControl ;or RotaryEncoder
PinUp: 5
PinDown: 6
pull_up: True
hold_time: 0.3
hold_repeat: True
timeBase: 0.1 ;only for RotaryEncoder
functionCallDown: functionCallVolD
functionCallUp: functionCallVolU
functionCallTwoButtons: functionCallVol0 ;only for TwoButtonControl
[PrevNextControl]
enabled: False
Type: TwoButtonControl
Pin1: 22
Pin2: 23
functionCall1: functionCallPlayerPrev
functionCall2: functionCallPlayerNext
functionCallTwoButtons: None
pull_up: True
hold_time: 0.3
hold_repeat: False
[PlayPause]
enabled: True
Type: Button
Pin: 27
pull_up: True
hold_time: 0.3
functionCall: functionCallPlayerPause
[Shutdown]
enabled: False
Type: Button
Pin: 3
pull_up: True
hold_time: 2
functionCall: functionCallShutdown
[Volume0]
enabled: False
Type: Button
Pin: 17
pull_up: True
hold_time: 0.3
functionCall: functionCallVol0
[VolumeUp]
enabled: True
Type: Button
Pin: 24
pull_up: True
hold_time: 0.3
hold_repeat: True
functionCall: functionCallVolU
[VolumeDown]
enabled: True
Type: Button
Pin: 16
pull_up: True
hold_time: 0.3
hold_repeat: True
functionCall: functionCallVolD
[NextSong]
enabled: True
Type: Button
Pin: 23
pull_up: True
hold_time: 0.3
functionCall: functionCallPlayerNext
[PrevSong]
enabled: True
Type: Button
Pin: 13
pull_up: True
hold_time: 0.3
functionCall: functionCallPlayerPrev
[Halt]
enabled: False
Type: Button
Pin: 21
pull_up: True
hold_time: 0.3
functionCall: functionCallPlayerPauseForce
And this is the syslog after pushing the onOff Shim Button:
pi@raspberrypi:~/RPi-Jukebox-RFID/settings $ sudo tail -f /var/log/syslog
Dec 20 17:23:05 raspberrypi systemd[1]: man-db.service: Succeeded.
Dec 20 17:23:05 raspberrypi systemd[1]: Started Daily man-db regeneration.
Dec 20 17:23:06 raspberrypi systemd[1]: apt-daily.service: Succeeded.
Dec 20 17:23:06 raspberrypi systemd[1]: Started Daily apt download activities.
Dec 20 17:23:06 raspberrypi systemd[1]: Starting Daily apt upgrade and clean activities...
Dec 20 17:23:07 raspberrypi systemd[1]: systemd-hostnamed.service: Succeeded.
Dec 20 17:23:08 raspberrypi systemd[1]: apt-daily-upgrade.service: Succeeded.
Dec 20 17:23:08 raspberrypi systemd[1]: Started Daily apt upgrade and clean activities.
Dec 20 17:23:19 raspberrypi systemd[1]: Started Session 4 of user pi.
Dec 20 17:23:33 raspberrypi systemd[1]: phoniebox-idle-watchdog.service: Succeeded.
Broadcast message from root@raspberrypi (somewhere) (Sun Dec 20 17:29:37 2020):
BCM 17 held low, system shutdown in 0 minutes
Dec 20 17:29:37 raspberrypi systemd[1]: systemd-rfkill.socket: Succeeded.
Dec 20 17:29:37 raspberrypi systemd[1]: Closed Load/Save RF Kill Switch Status /dev/rfkill Watch.
Dec 20 17:29:37 raspberrypi systemd[1]: Stopped target Timers.
Dec 20 17:29:37 raspberrypi systemd[1]: Stopped target Graphical Interface.
Dec 20 17:29:37 raspberrypi systemd[1]: Stopping Session 3 of user pi.
Dec 20 17:29:37 raspberrypi systemd[1]: Stopped target Multi-User System.
Dec 20 17:29:37 raspberrypi systemd[1]: Stopping Samba SMB Daemon...
Dec 20 17:29:37 raspberrypi systemd[1]: Stopping Lighttpd Daemon...
Dec 20 17:29:37 raspberrypi systemd[1]: Stopping LSB: exim Mail Transport Agent...
Dec 20 17:29:37 raspberrypi systemd[1]: gldriver-test.service: Succeeded.
Dec 20 17:29:37 raspberrypi systemd[1]: Stopped Check for v3d driver.
Dec 20 17:29:37 raspberrypi systemd[1]: Stopping Regular background program processing daemon...
Dec 20 17:29:37 raspberrypi systemd[1]: Stopping Configure Bluetooth Modems connected by UART...
Dec 20 17:29:37 raspberrypi systemd[1]: Stopping Authorization Manager...
Dec 20 17:29:37 raspberrypi systemd[1]: Removed slice system-bthelper.slice.
Connection to raspberrypi closed by remote host.
Connection to raspberrypi closed.
I have a similar issue. With the update to 2.2 the shutdown over GPIO does not work. As soon as the part in the gpio-settings.ini the section [shutdown] is enabled with "enabled : True" the other buttons don't work anymore, and most interestingly, the sound does not work anymore as well.
I have a similar issue. With the update to 2.2 the shutdown over GPIO does not work. As soon as the part in the gpio-settings.ini the section [shutdown] is enabled with "enabled : True" the other buttons don't work anymore, and most interestingly, the sound does not work anymore as well.
Could you please show your gpio_settings.ini?
[VolumeControl] enabled: True Type: TwoButtonControl PinUp: 6 PinDown: 5 pull_up: False hold_time: 0.3 hold_repeat: True timeBase: 0.1 functionCallDown: functionCallVolD functionCallUp: functionCallVolU functionCallTwoButtons: None
[PrevNextControl] enabled: True Type: TwoButtonControl Pin1: 26 Pin2: 13 functionCall1: functionCallPlayerPrev functionCall2: functionCallPlayerNext functionCallTwoButtons: None pull_up: False hold_time: 0.3 hold_repeat: False
[PlayPause] enabled: True Type: Button Pin: 12 pull_up: False hold_time: 0.3 functionCall: functionCallPlayerPause
[Shutdown] enabled: False Type: Button Pin: 3 pull_up: False hold_time: 2 functionCall: functionCallShutdown
[Volume0] enabled: False Type: Button Pin: 17 pull_up: True hold_time: 0.3 functionCall: functionCallVol0
[VolumeUp] enabled: False Type: Button Pin: 5 pull_up: True hold_time: 0.3 hold_repeat: True functionCall: functionCallVolU
[VolumeDown] enabled: False Type: Button Pin: 6 pull_up: True hold_time: 0.3 hold_repeat: True functionCall: functionCallVolD
[NextSong] enabled: False Type: Button Pin: 26 pull_up: True hold_time: 0.3 functionCall: functionCallPlayerNext
[PrevSong] enabled: False Type: Button Pin: 13 pull_up: True hold_time: 0.3 functionCall: functionCallPlayerPrev
[Halt] enabled: False Type: Button Pin: 21 pull_up: True hold_time: 0.3 functionCall: functionCallPlayerPauseForce
Is the „Halt“ or „Shutdown“ section in any way related to the onOff Shim? Meaning: should I enable any of it to have the shim working?
If you are using the button or button connector on the shim itself, the GPIO settings are irrelevant.
If you experience a "restart" with your onoffshim, it could also be, that you have a capacitor attached to +5v or +3,3 pins and GND. It is normally suggested to use this capacitor to enable a short powersupply if your powerbank switches from or to charging and would normally loose power. Other areas are you are a fool like myself and use this capacitor for your selfmade amplifier and don't see this problem :)
I see a power cut off when I attach powercord to the powerbank, but that's ok for me. And as mentioned before my main problem is that the shim as well as the system shutdown command powers down the raspi, but is not dropping the power supply so the raspi keeps on with a red light. But it's not possible to start up the device again without removing the power connection from the powerbank to the raspi.
What do you mean with the last sentence? German is fine too ;) @matthias-pelger
Sorry for bad english, still in holiday mode :)
Also auf Deutsch: Ich hatte das gleiche Problem, als ich einen Verstärker selber gelötet habe und zur spannungsstabilisierung des Verstärkers einen größeren Elko zwischen +5V und GND gehängt habe. Dieser verursachte genau das Phänomen: Raspi ging aus und sofort wieder an. Das liegt wohl irgendwie daran, dass der OnOffShim es nicht mag wenn er nach dem Ausschalten noch mit Spannnung "von hinten" versorgt wird. Bei mir hat eine einfache Diode, die verhindert das Strom vom Elko zurück zu Raspi fließt gelöst.
Daher der Vorschlag: prüfe mal alles was da an +5V und +3.3V an den Pins vom OnOffShim hängt ob da irgendwo noch ein Stromimpuls kommen könnte der den Shim wieder einschaltet.
Danke 👍 Das hatte ich auch vermutet und alle anderen Pins, ich nutze das Extension Bord, auf andere gesteckt, so dass jetzt nur noch der shim und der hifiberry miniamp sich Pins teilen. meine Button LEDs werden zwar auch über 5V Dauerstrom versorgt, aber über andere Pins :(
Hmm, wäre es nicht möglich, dass der Shim auf alle 5V Pins gleich reagiert? Würde vermuten, dass die geteilt ist und nicht getrennt wird.
Hm, du meinst ich sollte mal alle 5V Pins abkoppeln?
genau, also testweise und dann einzeln wieder dran bis der fehler wieder auftritt.
Ich habe jetzt auch mal das Extension Board abgenommen und den OnOff Shim direkt auf den Pi gestöpselt, aber leider immer noch das gleiche Problem. Es sind auch keine weiteren anderen PINs angeschlossen/belegt.
Ich habe hier eine ähnliche Beschreibung gefunden, das werde ich mal überprüfen: https://forum-raspberrypi.de/forum/thread/44762-phoniebox-onoffshim-schaltet-den-rpi-nicht-aus/
Hat leider auch nicht geholfen, ich habe jetzt mal einen RPI4 bestellt, mal gucken ob das da besser läuft und ggf. checke ich noch mal die Lötstellen.
Closing for now as there was no activity for a long time. Feel free to reopen a new issue, if the issue persists with current version 2.4 (or beta 3.2).
Bug
What I did
Powering down using onoff shim or using "sudo shutdown -h 0" or using ./scripts/playout_controls.sh -c=shutdown helps.
What happened
I expected this to happen
The Raspi is disconnected and shutdown completely so I can restart it using the shim
Further information that might help
Software
Base image and version
Branch / Release
master
Installscript
Hardware
RaspberryPi version
Raspberry Pi 3 Model B Rev 1.2
Other notable hardware