Solved Recallbox on/off button

[netcat]

@lackyluuk i am wired EXACTLY like that

Have un remed proper line in config file (through web browser interface)

Rebooted

Confirmed changes are still present in config file

Done all of this a second time on second rasberry Pi3

No results button does NOTHING

Have akso tried with and without reset and power led (these dont work either)

You may see my wiring diagram here

Http://www.780tech.com/rbox.jpg

Have tested with ONLY power switch
AND with power/reset & LED

Cant make even the power led work unless i attach to pin1(3v) + any ground

[netcat]

@supernature2k have you actually seen or made it work (on latest revision of Recalbox)

or are you merely stating a theoretical fact?

[supernature2k]

@netcat

Bro, I created the pin356onoffreset script...
Tested hundred of times, working everyday on my NES recalbox.

And my script is based on the 2 pin56 scripts that are also working.

So... let's try something:

activate the option in recalbox.config (removing the ; at beginning of ONE line)

Then ssh your recalbox and type ls -al

Check in the list of process if you see powerswitch.sh and rpi-pin356-power.py

[netcat]

@supernature2k I apologize if you felt alluded , although I obviously did not realize who you were, I must confess I am gratified the person that developed the script is answering.

if you take a peek at my diagram you can see I am obviously invested in to making it work and have everything wired (To the best of my knowledge) perfectly.

As a side note, several times now after modifying the config file and rebooting the raspberry goes into a mad reboot cycle until I hit tab to get in to emergency mode and than re-exit.
last time it completely lost the config file and I had to copy and paste form the backup file.

Thank you for your input, Please find attached the result of the SSH request.

login as: root
root@192.168.1.9's password:

ls -al

total 68
drwxr-xr-x 12 root root 4096 Jan 1 1970 .
drwxr-xr-x 12 root root 4096 Jan 1 1970 ..
drwxr-xr-x 2 root root 4096 Jan 1 1970 .cache
drwxr-xr-x 4 root root 4096 Dec 11 19:18 .config
drwxr-xr-x 4 root root 4096 Jan 1 1970 .emulationstation
drwxr-xr-x 2 root root 4096 Jan 1 1970 .hatari
drwxr-xr-x 8 root root 4096 Dec 11 21:44 .kodi
drwxr-xr-x 2 root root 4096 Jan 1 1970 bluetooth
drwxr-xr-x 7 root root 4096 Jan 1 1970 configs
drwxr-xr-x 2 root root 4096 Jan 1 1970 logs
-rw-r--r-- 1 root root 7751 Jan 1 1970 recalbox.conf
-rw-r--r-- 1 root root 7752 Jan 1 1970 recalbox.old.conf
drwxr-xr-x 2 root root 4096 Jan 1 1970 ssh
drwxr-xr-x 3 root root 4096 Jan 1 1970 udev
-rw-r--r-- 1 root root 6 Jan 1 1970 update.done

[supernature2k]

@netcat

Ok, so apologize but it's late there... the command is ps -al

One question: your button is on/off or momentary?

pin356onoffreset doesn't work (for now) with a momentary unless you change 1 line in the code.

You can check what needs to be done here

[netcat]

@supernature2k both of my buttons are momentary and I did read the part where it states if you use the

567 script it MUST be permanent on/off switch, even know I read a post where somebody claimed it would work with a momentary pushbutton, I therefore switched to testing only with the 56 script to see if at least I could make it turn on and off

either way, neither script appears to be engaging,

if necessary I can switch the push button for an on/off button, but until I can verify any script is working at all I have halted hardware modifications, also .. as a means of testing the 567 script it would suffice to simply hold the push button in to simulate the ON position of the switch and release it to turn off (Which doesn't work either)

login as: root
root@192.168.1.9's password:

ls -al

total 68
drwxr-xr-x 12 root root 4096 Jan 1 1970 .
drwxr-xr-x 12 root root 4096 Jan 1 1970 ..
drwxr-xr-x 2 root root 4096 Jan 1 1970 .cache
drwxr-xr-x 4 root root 4096 Dec 11 19:18 .config
drwxr-xr-x 4 root root 4096 Jan 1 1970 .emulationstation
drwxr-xr-x 2 root root 4096 Jan 1 1970 .hatari
drwxr-xr-x 8 root root 4096 Dec 11 21:44 .kodi
drwxr-xr-x 2 root root 4096 Jan 1 1970 bluetooth
drwxr-xr-x 7 root root 4096 Jan 1 1970 configs
drwxr-xr-x 2 root root 4096 Jan 1 1970 logs
-rw-r--r-- 1 root root 7751 Jan 1 1970 recalbox.conf
-rw-r--r-- 1 root root 7752 Jan 1 1970 recalbox.old.conf
drwxr-xr-x 2 root root 4096 Jan 1 1970 ssh
drwxr-xr-x 3 root root 4096 Jan 1 1970 udev
-rw-r--r-- 1 root root 6 Jan 1 1970 update.done

ps -al

PID USER COMMAND
1 root init [3]
2 root [kthreadd]
3 root [ksoftirqd/0]
5 root [kworker/0:0H]
7 root [rcu_sched]
8 root [rcu_bh]
9 root [migration/0]
10 root [migration/1]
11 root [ksoftirqd/1]
13 root [kworker/1:0H]
14 root [migration/2]
15 root [ksoftirqd/2]
17 root [kworker/2:0H]
18 root [migration/3]
19 root [ksoftirqd/3]
21 root [kworker/3:0H]
22 root [khelper]
23 root [kdevtmpfs]
24 root [netns]
25 root [perf]
26 root [khungtaskd]
27 root [writeback]
28 root [crypto]
29 root [bioset]
30 root [kblockd]
31 root [kworker/0:1]
32 root [rpciod]
33 root [kswapd0]
34 root [fsnotify_mark]
35 root [nfsiod]
41 root [kthrotld]
42 root [VCHIQ-0]
43 root [VCHIQr-0]
44 root [VCHIQs-0]
45 root [iscsi_eh]
46 root [dwc_otg]
47 root [DWC Notificatio]
49 root [kworker/1:1]
50 root [VCHIQka-0]
51 root [SMIO]
52 root [deferwq]
54 root [mmcqd/0]
55 root [kworker/2:1]
56 root [jbd2/mmcblk0p7-]
57 root [ext4-rsv-conver]
58 root [kworker/1:2]
62 root [kworker/3:1]
80 root /sbin/syslogd -n
83 root /sbin/klogd -n
100 root /sbin/udevd -d
120 root [cfg80211]
121 root [brcmf_wq/mmc1:0]
123 root [brcmf_wdog/mmc1]
124 root [ksdioirqd/mmc1]
156 root [jbd2/mmcblk0p8-]
157 root [ext4-rsv-conver]
177 root /usr/sbin/lircd -n --driver=default --device=/dev/lirc0 --output
186 root [kworker/3:1H]
262 dbus dbus-daemon --system
276 root {S31emulationsta} /bin/sh /etc/init.d/S31emulationstation start
277 root {emulationstatio} /usr/bin emulationstation
293 root [kworker/1:1H]
298 root [kworker/0:1H]
300 root /usr/sixad/official/sixad-bin 0 0 0
305 root {bluetoothcontro} /bin/bash /recalbox/scripts/bluetoothcontrolle
310 root bluetoothd -u
381 root {recalbox-config} /bin/bash /recalbox/scripts/recalbox-config.sh
385 root /usr/sbin/wpa_supplicant -iwlan0 -c/var/lib/wpa_supplicant.conf
387 root [kworker/0:2]
405 root [kworker/2:1H]
416 root [kworker/2:2]
423 root udhcpc -R -n -p /var/run/udhcpc.wlan0.pid -i wlan0
432 root [ipv6_addrconf]
433 root /usr/sbin/ntpd -g
439 avahi avahi-daemon: running [RECALBOX.local]
441 root [kworker/3:2]
445 root /usr/sbin/dropbear -R
457 root smbd -D
459 root smbd -D
461 root smbd -D
462 root nmbd -D
473 root {powerswitch.sh} /bin/bash /recalbox/scripts/powerswitch.sh star
482 root python /recalbox/scripts/rpi-pin356-power.py
484 root node main.js
494 root python /usr/recalbox-manager/manage.py runserver 0.0.0.0:80 --se
506 root /sbin/getty 38400 tty2
655 root /usr/sbin/dropbear -R
728 root -sh
772 root [kworker/u8:1]
1189 root [kworker/u8:2]
1464 root [kworker/u8:0]
1656 root sleep 10
1657 root ps -al

[supernature2k]

@netcat said in Recallbox on/off button:

482 root python /recalbox/scripts/rpi-pin356-power.py

ok so this line tells us the script is running. If your wiring is good, the LED MUST be on.

what if you put a wire between pin 5 and pin 6 while the rpi is running?

[netcat]

@supernature2k tried it.. it does nothing.

did you look at my diagram ?

Http://www.780tech.com/rbox.jpg

that is EXACTLY how I have it wired. also if I plug the LED in to pin 1 (3v) and any ground.. than the led DOES turn on...

I am completely baffled

[netcat]

@netcat Upon reading your last reply, and learning that the script was indeed running, and remembering

"Once you eliminate the impossible, whatever remains, no matter how improbable, must be the truth."

Let me start by publicly apologizing to you and everyone in the community for waiting their valuable time, I am officially an imbecile and upon disassembly and inspection realized I was reading the GPIO UPSIDE DOWN .. not sure how I could be so stupid to do ir the right way when testing the LED on Pin 1 (3 Volts) and then assembling it in to my box backwards (and then do it again the second time around)

but the truth must be told..

I WAS THE GREMLIN, all failures were do to my inability to recognize PIN 1 when assembling the raspberry in to the box.

it is working now perfectly.

I very humbly request you please forgive me for my ineptitude.

[supernature2k]

@netcat

OMG!

I thought about this and told myself "that's not possible, the guy made this diagram with the square upper left..."

Well, we all have been dumb one time when it comes to electronics

Now the last thing you need to do is to modify the 356pin script as I showed you and you can use your 2 momentary buttons + LED and enjoy

[netcat]

@supernature2k in my country "Costa Rica" tgey have a saying

"Al mejor mono se le cae el zapote"

= even tge best monkey drops his zapote sometimes

(Zapote... = some kind of fruit minkeys semingly like)

Thank you again for your patience and suppirt

One more onquiry with 567 script does power button have to ve on/off or can i use tge pushbutton i have in place?

[supernature2k]

@netcat

Read my post above...

To be sure that it'll work with a momentary switch, juste edit the script file.

[netcat]

@supernature2k Thank you so very much have made the recommended changes as per your suggestion.

with this particular raspberry I am now having an issue where recalbox spontaneously goes in to a constant rebooting cycle, if I unplug it a while and plug it back in it boots up just fine, have not tested on second raspberry Pi yet, could this have anything to do with scripts ?

one other matter I would like to inquire if you are interested in, I believe Through One of my arcade machines has a BETABRITE LED sign built in to the top of it... many years ago I worked with Mr. Carlos Santillon whom was one of the coders for DOS based Mame frontend called "ArcadeOS" and he built code in to ArcadeOS so it could send data through the serial port and display on the BETATEBRITE the name of the game being played, would this be possible directly form the GPIO of the raspberry Pi and if so, would you be interested In helping code it?

thank you again for all your help

[supernature2k]

@netcat

Hi, the strange behavior may come from the script. Check if your button is sending false signals.

For the brite thingy, it may be possible to retrieve the game name from configgen then python something to the GPIOs but I have no idea how nor time to look at it.

[netcat]

@supernature2k Thank you so very much for all your help, rebooting was an issue with the power supply, everything else is working to perfection.

[netcat]

@netcat Just spent the past 8 hours documenting this process step by step form beginning to end including hardware and software installation, based on my experience in the process and the very helpful guidance I have received from @supernature2k and others here which was absolutely critical in getting this to work.

if anyone is interested I have published it off my website.

http://www.780tech.com/recalbox/

p.s. it has pretty photos so you cant go wrong.

[supernature2k]

@netcat

This is a very good tuto you made!
Only problem is I think you made a mistake on the GPIO diagram. Your Reset bouton ground goes to pin 4, should be pin 6.

@Global-Moderators we should pin it somewhere

[Substring]

@netcat just read your tutorial, nice step-by-step guide. Though i like when people try to reach the web manager through http://recalbox/ or http://recalbox.local for mac/linux

for your BETATEBRITE thing, of course it's possible. You'd need to know a little python, and most of all, how to send data to your betatebrite

@supernature2k could have eventually been pinned if it was written as a forum post

[ian57]

great stuff, i will modify my pitendo with 2 new buttons

[netcat]

@supernature2k Thank you, Correction made