METADATA not saving - Favorites will never remain tagged

mitu

@cyperghost Maybe the wires are connected to other pins ?

cyperghost

@mitu This can only be answered by @Semper-5 but I assume not!
As I remeber he told me, that the python scripts are working ;)

Yahmez

If it just cuts power upon turning off the power switch it means that the on control pin is not going high on boot.

mitu

@cyperghost Python is a sneaky snake...

cyperghost

@yahmez Can you test the script on your build, too?
@mitu Python is very cool - indeed. But I also checked the way GPIOs are called. It's BCM mode. So Python GPIO = Bash GPIO

Yahmez

@cyperghost I will give it a try this weekend if I can but I have relatives coming to stay so I'm not 100% sure I'll be able to till next week.

Yahmez

@Semper-5
Can you try gpio readall to verify that the on control pin is high?

cyperghost

@yahmez No problem... I would be glad to hear your outfindings but take your time.

Yahmez

@cyperghost I am no coding guy. Does your BASH script enable the internal pullup on 25?

cyperghost

@yahmez No! I don't use wiringpi.... or raspi-gpio.

But would be possible with bash, too

raspi-gpio set $trigger_pin ip pu
echo "monitoring BCM $trigger_pin"

pin_state() {
    raspi-gpio get $trigger_pin | grep -c "level=0 fsel=0 func=INPUT"
}

shutdown_trigger() {
    if [ `pin_state` = 1 ]; then
        echo "BCM $trigger_pin asserted low"
....

Yahmez

@cyperghost That is the problem then, at least part of it.

cyperghost

@yahmez afaik this should work without the pullup. As I said, I sadly have no POLOLU switch available. Is there no connection to ground from the POLOLU to the GPIO?

Semper 5

sorry for the late reply. I'm trying to get out of work.
my GPIO config is exactly as configured in Yahmez's tutorial.
23 reset
24 power
25 power (ON)

my GPIO readall with cyperghost's script
but as we see here, its not looking very live.

just as a reminder, I can get Yahmez's to fire up with no problem - just to rule out the possibility of bad wiring and I did confirm that my wiring looked good to a few other people who are VERY familiar with this mod.

EDIT: SORRY I didn't run the gpio readall with the script running. GPIO 25 has a difference now

Yahmez

@cyperghost No. It will absolutely not work without the pullup. There is a reason I put it in my script :p

cyperghost

@semper-5 ~~Why is GPIO25 set low?~~ Okay corrected now.
@Yahmez Okay, that's interesting.... but I think it's no problem to integrate the script into yours. So I would suggest to remove the GPIO init and just make a call to to PID detection/removal routine.

Yahmez

@semper-5 Looks like the script is not setting GPIO 25 high according to your GPIO readall

cyperghost

@Semper-5 Use sudo command for this

echo "$GPIOpin2" > /sys/class/gpio/export
echo "out" > /sys/class/gpio/gpio$GPIOpin2/direction
echo "1" > /sys/class/gpio/gpio$GPIOpin2/value

With GPIOpin2=25 it will be a self runner ;)

@Yahmez Ah so you tried out without using the pullups? That's interesting. So I should investigate this ;) As I said: No POLOLU switch, no testing area.

So I say thank you to both of you! You should integrate a small 3,3V regulator. Then it's no problem to generate this. So intead of

python os.system("sudo shutdown -h now")

hook to a stripped down script with sudo command

# Detect PID or EMULATOR NAMES
emucall="$(sed '4!d; s/\([\\"]\|[[:alnum:]_]\+=[^ ]* \)//g; s/[][(){}^$*.|+? ]/\\&/g' /dev/shm/runcommand.info)"
espid="$(pgrep -f "/opt/retropie/supplementary/.*/emulationstation([^.]|$)")"

# Handle calls and send TERM signal
if [[ -n "$emucall" ]]; then
    emupid="$(pgrep -f "$emucall" | tr '\n' ' ')"
    pkill -P "$(echo $emupid | tr ' ' ',')"
    kill -9 "$emupid"
    sleep 4
fi    

if [[ -n "$espid" ]]; then
    touch /tmp/es-shutdown && chown pi:pi /tmp/es-shutdown
    kill "$espid"
    exit
fi

poweroff

Yahmez

@cyperghost it's not just the Pololu, but the way everything is wired in the case, the existing switches plus the added parts to convert it for safe shutdown. The Pololu on it's own is straight forward. Pin 25 has a diode between it's self and the switch to protect it from the 5v. It's internal pullup pulls it high. When you hit the switch it connects to ground and pulls gpio 25 down, which the script detects and initiates the shutdown.

cyperghost

@Yahmez But what is the difference to connect a GPIO directly to ground (maybe over an external resistor) or to activate the internal ones? I see there no difference. Maybe you can explain, me?

The internal pullup prevents from floating... yes.. but where is the difference?

Yahmez

@cyperghost Not sure what you mean about the 3.3v regulator but the pin needs a pull-up resistor to work. It can be a physical resistor added to the circuit from the pi's 3.3v rail or it can be the internal pullup. I used the internal pullup in my tutorial because it was cheaper and easier.

You want the pin to be high by default, detect a low, then shutdown.

If you can get the internal pullups working thru bash, it should all work. If you can not, than how about stripping out the shutdown part from my script and calling the bash to exit es and shutdown? Basically have the python handle the pins and the bash handle the exit and shutdown...