Multi Switch Shutdown Script!

BiZzAr721

I created a fork of Adafruit-GPIO-Halt. I made the change to (void)system("/home/pi/RetroPie/shutdown.sh");

I'm confident I can compile it from there. Should I put a call to multi_switch.sh --generic powerbtn=21 in the script or should I call to it directly before compiling?
There is a call in rc.local to /usr/local/bin/gpio-halt 6 & (6 being the gpio pin used, which can be changed)
If I set it to gpio 2 SDA or gpio 3 SCL, arcade controls will not work. Maybe that explains why raspi-gpio causes loss of controls. (Is it possible to get raspi-gpio to not monitor those pins?)

cyperghost

@BiZzAr721 I think it works with multi_switch.sh --generic powerbtn=21 and you do not need the Adafruit-GPIO-Halt.

If you compile the source code now with your changes you can add ANY command to the script you've created. Then you can just add path/to/multi_switch.sh --es-poweroff

BiZzAr721

@cyperghost Looking forward to giving it a try this evening. I'll edit this post with the results.

EDIT:
I recompiled GPIO-Halt, and pointed the script to your script. It worked great!
@cyperghost I appreciate all I have learned from you since the OpenBOR days lol What you do here for the community is a beacon of your character. Not only are you always willing to help, but you also take the time to explain and help others improve their skills.

It may not be much, but I thought it to be rewarding to fork the Adafruit Gpio-halt git, and compile it (and have it work!).

Thanks!

cyperghost

@BiZzAr721 Thanks you for your kindly words but I also asked question regarding coding in the beginning and @meleu helped me a lot, too.

BiZzAr721

@cyperghost Is always great to have a community of likeminded people who share a common interest, be it skydiving, retro gaming, or whatever. You end up with a diverse group of people with various skills all sharing ideas & talents, which usually transcends beyond political or religious differences.

mth75

@janderclander14 said in Multi Switch Shutdown Script!:

ne short press, quits the current emulator or restarts emulationstation. One long press (3 sec) restarts the system.

I attach here the code just in case someone finds it useful (it assumes multi_switch.sh is in /home/pi). You may add this as a python call to /opt/retropie/configs/all/autostart.sh

This was next on my list :-) ...

y-ello

Does it work with Raspberry Pi 4?

quicksilver

@y-ello yes it does, I'm using it with my pi4 in the argon one case.

Initial_G

@quicksilver said in Multi Switch Shutdown Script!:

@y-ello yes it does, I'm using it with my pi4 in the argon one case.

Hi @quicksilver, I was looking to set this up when my Argon one arrives.

I wanted to ask, could you share how you have your setup? from your above comment
https://retropie.org.uk/forum/topic/17415/multi-switch-shutdown-script/207

did you just install the power button/fan script from Argon one?
& then just modify the argononed.py to something like:
os.system("reboot") -> os.system("bash /path/to/multi_switch/multi_switch.sh --es-reboot")
os.system("shutdown now -h") -> os.system("bash /path/to/multi_switch/multi_switch.sh --es-poweroff")
is anything else needed?

Thx!

quicksilver

@Initial_G that's exactly what I did. Just make sure the multi switch script has the proper permissions as well.

On a side note (not related to the shutdown script) I also used the fan speed utility script to adjust when the argon one case fan turned on. I found it turned on at too low of a temp and I set it so that it wouldn't turn on unless it got to 65c. I prefer passive cooling as much as possible and only want fan as a last resort. Even with my pi overclocked the fan almost never needs to come on.

Initial_G

@quicksilver said in Multi Switch Shutdown Script!:

@Initial_G that's exactly what I did. Just make sure the multi switch script has the proper permissions as well.

On a side note (not related to the shutdown script) I also used the fan speed utility script to adjust when the argon one case fan turned on. I found it turned on at too low of a temp and I set it so that it wouldn't turn on unless it got to 65c. I prefer passive cooling as much as possible and only want fan as a last resort. Even with my pi overclocked the fan almost never needs to come on.

Cool thx for the quick reply, I think I'll update the fan temps too :)

Initial_G

@quicksilver

did you have to update the pulsetimes in the argononed.py?
as a test I changed:

	if pulsetime >=2 and pulsetime <=3:
		#os.system("reboot")
		os.system("bash /home/pi/RetroPie/scripts/multi_switch.sh --es-restart")
	elif pulsetime >=4 and pulsetime <=5:
		#os.system("shutdown now -h")
		os.system("bash /home/pi/RetroPie/scripts/multi_switch.sh --es-reboot")

so I can trigger the ES restart with double tap but whenever I try to hold for 3s, it seems to just poweroff, instead of triggering the reboot from multi_switch (which I've tested ok when I made the double tap trigger it). So now I've just left the double tap of the power button to do a reboot

Ideally I'd like someting along the lines of:
double tap: ES restart
hold for 3-5s: reboot
hold for 10s: power off

quicksilver

@Initial_G I didn't play with the pulse times, but if you get that part of it working the way you like it id be interested as well.

Quackwalks

@quicksilver I'm also curious to know what steps I should take to have a proper power button and fan with the argon one case.

quicksilver

@Quackwalks place the multi_switch.sh on your pi somewhere like /home/pi/RetroPie/scripts/multi_switch.sh and make sure it has executable permissions. Then modify your argononed.py script (im assuming you have already installed the default argon one script) located at usr/bin/argononed.py and look for this section and modify it to look like this:

if pulsetime >=2 and pulsetime <=3:
		#os.system("reboot")
		os.system("bash /home/pi/RetroPie/scripts/multi_switch.sh --es-restart")
	elif pulsetime >=4 and pulsetime <=5:
		#os.system("shutdown now -h")
		os.system("bash /home/pi/RetroPie/scripts/multi_switch.sh --es-reboot")

The fan script utility is installed and can be modified using the booklet instructions that came with your argon one. I cant find my instructions so youll have to look that up.

Quackwalks

@quicksilver You are awesome.

Rion

@quicksilver said in Multi Switch Shutdown Script!:

@Initial_G I didn't play with the pulse times, but if you get that part of it working the way you like it id be interested as well.

Yea me to. 😊

Ashpool

A general thanks to the folks having an Argon1 and who are tinkering with the argon script to call cyberghosts one!

But I still have some questions: The Argon1 Manual says for action Long Press >=5s the Function is a Forced Shutdown, as this is working even without installing the script, my assumption is: a >=5sec Press simply cuts the power and doesn't provoke any script (So nothing of the save stuff-things, that a controlled shutdown from cyberghosts script will be invoking is performed) :( Inside the argononed.py I cannot even find anything that can be configured 'bout the >=5sec timing.
So, I will state two hypotheses I want to have clarified:
a) a correct shutdown (writing Meta Stuff/etc.) with cyberghosts script would mean something like this

os.system("bash /home/pi/RetroPie/scripts/multi_switch.sh --es-poweroff")

b) a shutdown via the Argon1 Case Button with a press >=5sec is, from within a running system, a worst case scenario as it just cuts the power. So a regular Emulationstation Shutdown should be used instead (If the 3-5sec press is used for a restart)?

cyperghost

@Ashpool You should use a correct name to tag me ;)
Nevertheless, I don't own a ArgoneOne. But there is a small IC that is attached to I2C-bus on this housing. AFAIK it writes only two values to the flash, one for a reboot and one for shutdown. So the case "knows" how to enable/disable the power source.

So you are correct - by using the multi_switch call you can perform a save shutdown but the long press action with the sudden power cut is performed by the ARGON ONE hardware. No chance to change anything with a simple script.

You can take a look to BATOCERA - here the script was modified to perform some more actions. Take a look at the script here

Rion

@cyperghost is correct. Sadly without re flashing the IC there is nothing we can do.

I more in depth explanation can be found here by Spiros Papadimitriou.

Read under hardware protocol.

Maybe something can be learned from Spiros Papadimitriou rewrite of the script?