About the RetroFlag cases! Surprise surprise.... They can cut off power!

edmaul69

@cyperghost im really confused. Retroflag says that their script does safe shutdown and safe reset. And to me it appears to be doing just that. How is this better?

cyperghost

@edmaul69 They do a safe shutdown by killing every instance of emulationstation binary but this method may fail if there is a emulator running in background. These may be a edge example but it's an improper way to terminate emulation station and is not clean way to save metadata.

Furthermore.... the reset button. It's just a waste of option with the original script as it just acts as a system reboot. The multi_switch script just resets the emulator (if there is one is running) and you turn back to ES main menu, or you restart just ES without performing a reboot (usefull if you changed metadata and want to save it, too).

All in all it doesn't matter which way you choose. Imho I would NOT use the original script but would stick to python and modify the original script like I've done here: Get text output from bash into you python script

In the end you decide ... I created the script to cover a lot of usecases and to make work to install switch to a Pie a bit more easier. Furthermore I learned a lot about handling command line parameters (used a uncommon method without shifting every single parameter).

In short why I don't rely on the retroflag script:

Fixed shutdown timer (5 seconds in every case)
The metadata may break in edge cases
Reset button is useless (imho)
(not related to the script itself) They change /boot/command to set UART for LED output
The python libary (GPIOzero) is a real heavyweight (but very comfortable I must agree)
I wanted to do something in bash ... as long as @meleu don't fixed the ES shutdown service (therefore I installed the --es-systemd parameter)

So I hope you are not confused anymore ;)

PWN3D_

@cyperghost

Ok, I've instaled the shutdown_fan script, but it appears as shutdown_fan.sh1 , so I guess it was already there.

Sorry for the confusion about the Power switch , I'll try to be clear :
(The Nespi case switch is turned to ON)

-With the retroflag script, the Power on/off only works to turn on the pi. When I press the Power button to "off", it doesn't do anything. If I want to trun off the pi, i also have to press the reset button, see the retroflag script rolling to the end until it finally turn off the pi.

-With your script, it is the story, the Power off doesn't do anything but as the reset button only restart ES, I can't turn off the pi.

So yes, the Reset button work perfectly, the Power button works only in one way, when I have to turn On the pi.

PS: Today I have tested with a fresh sd card without the retroflag script, but this ended with the same result unfortunatly

PSS: Also I should mention my what I am working with :
-Nespi Case+
-Raspberry Pi 3 B+
-Kitty for SHH
-San Disk Ultra 16GB

cyperghost

@pwn3d_
Then I guess there is something wrong with the case.

-With the retroflag script, the Power on/off only works to turn on the pi. When I press the Power button to "off", it doesn't do anything. If I want to trun off the pi, i also have to press the reset button, see the retroflag script rolling to the end until it finally turn off the pi.

That's very curious. Usually the power button initiates a full power cut off if the GPIO is detected.

-With your script, it is the story, the Power off doesn't do anything but as the reset button only restart ES, I can't turn off the pi.

The reset and and power button are initiated all the same way. As reset works as it should and power does not work. I think I now I understand what may happening. It seems GPIO3 is not proper connected to your PIN header. You may check if it is attached right to the GPIO header. You can also reattach it to a new GPIO if you use ./multi_switch.sh --nespi+ powerbtn=xy & argument.
XY is the GPIO header.....

Because no script works in your setup, the error lies in your case.

PWN3D_

@cyperghost I will check all the wires and connectors right now

Also, if the switch in the nespi case is set to "off" the power button work just fine when I turn off the pi, but as you know it just kill the power.

PWN3D_

@pwn3d_ Oh, I'm getting somewhere : I tried to reattach the wire connected to the GPIO3 , to the GPIO11.

Then I typed : ./multi_switch.sh --nespi+ pwerbtn=11 &
the answer was : -bash: ./multi_switch.sh: No such file or directory

Ps: I have also checked in the /home/pi/RetroPie/scripts directory. I can see the multi_switch script as : *multi_switch.sh
I don't know if the * means anything

mitu

@pwn3d_ said in About the NESPi+ case! Surprise surprise.... It can cut off power!:

I don't know if the * means anything

It means is an executable file/script. Try typing the full pathname

/home/pi/RetroPie/script/multi_switch.sh --nespi+ pwerbtn=11 &

PWN3D_

@mitu Nope, I'm getting the same message :

-bash /home/pi/RetroPie/script/multi_switch.sh: No such file or dirctory

PS: Scripts ... with an s at the end ... yep that was it

cyperghost

@pwn3d_ said in About the NESPi+ case! Surprise surprise.... It can cut off power!:

yep that was it

= it does work now?

Annother question - just curious about the not working GPIO3.... Do you have activated I2C connection somewhere? Maybe that's the reason the GPIO wasn't initiated right.

The case uses the whole standard connection boards (I2C and UART) so I decided to develop command line parameters.

PWN3D_

@cyperghost No ...

But something else did the trick : I just went to edit multi_switch.sh

After "SWITCHTYPES" and "NESPIPLUS" , to #Set GPIOs, I just change GPIO_powerswitch=3 to GPIO_powerswitch=17 (my yellow wire is connected to this GPIO)

After a reboot, I tried the powerbutton, the red light blinked 4 times, I saw a script rolled, then the pi shut down completely !

So to identify the problem, does that mean the GPIO 3 on my raspberry is dead ?

cyperghost

@pwn3d_ said in About the NESPi+ case! Surprise surprise.... It can cut off power!:

So to identify the problem, does that mean the GPIO 3 on my raspberry is dead ?

I don't think it's dead... I think some I2C device is using this. So it can't be initiated. Interesting indeed!

about the command line parameter... you know ... powerbtn=11 is not GPIO17. You should write powerbtn=17 that would do the trick without changing the script. But glad it worked and now enjoy ;)

PWN3D_

@cyperghost said in About the NESPi+ case! Surprise surprise.... It can cut off power!:

@pwn3d_ said in About the NESPi+ case! Surprise surprise.... It can cut off power!:

So to identify the problem, does that mean the GPIO 3 on my raspberry is dead ?

I don't think it's dead... I think some I2C device is using this.

about the command line parameter... you know ... powerbtn=11 is not GPIO17. You should write powerbtn=17 that would do the trick without changing the script. But glad it worked!

Yes, I noticed that, I confused with the number of the pin :)

I2C device? What is this ?

And Thank you so much for your help ! I learned a lot ! ;)

cyperghost

@pwn3d_

Yes, I noticed that, I confused with the number of the pin :)

https://pinout.xyz/# and now click on BCM17 (=GPIO17)
you will see ...

Physical pin 11 = Board numbering
BCM pin 17 = GPIO
Wiring Pi pin 0 = arduino like numbering ;)

In 95% of case we talk about BCM PIN

I2C device? What is this ?

It's a communication protocoll to attach sensors, simple displays, board expanders..... very helpfull for much much purposes. But maybe you activated it. Maybe with sudo nano /etc/modules you see some I2C entries.

And Thank you so much for your help ! I learned a lot ! ;)

You're welcome

PWN3D_

It's a communication protocoll to attach sensors, simple displays, board expanders..... very helpfull for much much purposes. But maybe you activated it. Maybe with sudo nano /etc/modules you see some I2C entries.

I've checked, i see 2 lines :

uinput
I2c-dev

cyperghost

@pwn3d_ Yes... that's it. But don't ask me there is an active I2C module loaded ;) Usually it's just uinput

devnull22

Hi! Thanks for the script, it works fine on my new 3b+ with the nespi+ case.
I am at ease with Linux and scripting in general, not so with GPIO and electronics in general...

Is there a way to shut down the fan when everything is plugged in correctly, and set it back up? I'd like to try my hand at scripting something to start it when temp goes over 65 celsius for a minute or two, and shut it down aftwerwards. So far, started reading on gpio and tried understanding what is done with the shutdown_fan script but it evades me =)

Will update if I figure it out, but help would be appreciated to get a headstart on if a raspi_gpio command could close down the fan without affecting the rest!

cyperghost

@devnull22 said in About the NESPi+ case! Surprise surprise.... It can cut off power!:

Hi! Thanks for the script, it works fine on my new 3b+ with the nespi+ case.

You're welcome

I am at ease with Linux and scripting in general, not so with GPIO and electronics in general...

GPIO is also not very difficult as these operations are the simplest way to use them.

Is there a way to shut down the fan when everything is plugged in correctly, and set it back up?

Yes ... therefore you need the shutdown_fan script. This completly cuts down power

I'd like to try my hand at scripting something to start it when temp goes over 65 celsius for a minute or two, and shut it down aftwerwards.

No this won't be provided by this script. It's possible of course.

So far, started reading on gpio and tried understanding what is done with the shutdown_fan script but it evades me =)

The shutdown_fan script just sets a GPIO to low, this will cut the power to the PIe, too. I just make a test command check like [[ $1 == "poweroff" ]] to just cut power of you want a real shutdown.

Will update if I figure it out, but help would be appreciated to get a headstart on if a raspi_gpio command could close down the fan without affecting the rest!

No... that's not possible. The wiring of the case sets the GPIO just to 5V common power. The script just cuts the power .... that's all. You need to do a complete rewiring of the fan to achieve this. Use a transistor or a (opto)mosfet to achive this. Then a GPIO which can switch to low/high will switch 5v rail to the fan.

cloudlink

With your script, if I execute the following line to restart ES, should it save metadata?

/home/pi/RetroPie/scripts/multi_switch.sh --es-restart

cyperghost

@cloudlink Yes

Ashpool

@cyperghost said in About the NESPi+ case! Surprise surprise.... It can cut off power!:

Write some feedback and sorry for inconvience

I've just bought the NESPI+ case and now am at the stage of RTF -lack of- M part of my research and came up to your script/post(s) here on the Forum. The Arguments provided by you to use your script instead of the one by Retroflag sound valid and I am eager to try it out, but I am confused/puzzled by the shutdown_fan script part. Would you be so kind to elaborate this a bit further (what is it exactly for [whence does it cuts down the power? in general, just if the pi ain't overheating and if so, can a threshold be set? <ok, the last case (heat management) is just wishfull thinking i assume>] (i haven't installed a fan so far into the case), is it neccessary or just needed by some users, ... )

Thanks for the script and in advance for your answer!

P.S.: Yes, I've read through your other Thread (https://retropie.org.uk/forum/topic/17415/multi-switch-shutdown-script), but the talk there about the fan just added up to my confusion :/ [maybe I would understand it better if i actually had a fan installed (so far i assume that the case is providing no power to the fan if the power button is set to off, or why does it have its own connector for a fan? The Concept of the case providing power to the pi-board and then taking power from the GPIOs of that board to provide it to its own fan connector sounds a bit strange to me, as is the thought that there my be a current on the GPIOs after the power is cut off via the power-button...)]