Mausberry Switch Script

thedman!

Hi Chaps,

I'm trying to install a mausberry switch. Its physicaly connected properly...

The instructions to install are:

For Arch:

1. wget http://files.mausberrycircuits.com/setupArch.sh
2. bash setupArch.sh
3. reboot

1. is fine
2. gives the error:

The unit files have no [Install] section. They are not meant to be enabled
using systemctl.
Possible reasons for having this kind of units are:
1) A unit may be statically enabled by being symlinked from another unit's
.wants/ or .requires/ directory.
2) A unit's purpose may be to act as a helper for some other unit which has
a requirement dependency on it.
3) A unit may be started when needed via activation (socket, path, timer,
D-Bus, udev, scripted systemctl call, ...).

Has anyone got any idea how I should get the script installed given this???

Cheers,

Dave.

thedman!

The script of the setup file is:

echo '#!/bin/bash

#this is the GPIO pin connected to the lead on switch labeled OUT
GPIOpin1=23

#this is the GPIO pin connected to the lead on switch labeled IN
GPIOpin2=24

echo "$GPIOpin1" > /sys/class/gpio/export
echo "in" > /sys/class/gpio/gpio$GPIOpin1/direction
echo "$GPIOpin2" > /sys/class/gpio/export
echo "out" > /sys/class/gpio/gpio$GPIOpin2/direction
echo "1" > /sys/class/gpio/gpio$GPIOpin2/value
while [ 1 = 1 ]; do
power=$(cat /sys/class/gpio/gpio$GPIOpin1/value)
if [ $power = 0 ]; then
sleep 1
else
poweroff
fi
done' > /etc/switch.sh
chmod 777 /etc/switch.sh
echo '[Unit]
Description=MausBerry

[Service]
ExecStart=/bin/bash /etc/switch.sh

[Install]
WantedBy=multi-user.target' > /etc/systemd/mausberry.service
systemctl enable /etc/systemd/mausberry.service

PeteB

I used one of these for a while, not on Arch though (don't have one installed now).

Ran through the install instructions after your post, and seemed to install fine... Here is what I get when I follow the steps.

1. Output of wget:

[root@runeaudio ~]# wget http://files.mausberrycircuits.com/setupArch.sh
--2016-04-08 19:08:59--  http://files.mausberrycircuits.com/setupArch.sh
Resolving files.mausberrycircuits.com (files.mausberrycircuits.com)... 50.62.52.1
Connecting to files.mausberrycircuits.com (files.mausberrycircuits.com)|50.62.52.1|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 779 [application/x-sh]
Saving to: ‘setupArch.sh’

setupArch.sh        100%[=====================>]     779  --.-KB/s   in 0s     

2016-04-08 19:09:00 (19.4 MB/s) - ‘setupArch.sh’ saved [779/779]

2. Output of setup:

[root@runeaudio ~]# bash setupArch.sh
Created symlink from /etc/systemd/system/multi-user.target.wants/mausberry.service to /etc/systemd/mausberry.service.
Created symlink from /etc/systemd/system/mausberry.service to /etc/systemd/mausberry.service.

Were you logged in as root when you installed it?

thedman!

Hi Pete,

Thanks for your help. Yes I was logged in a root, i've tried twice since, still get the same message

Dave

PeteB

Ok.... I JUST downloaded and tried it after your post, b/c I want to use it in the future, even though I do not have the board connected now...

After reboot,

systemctl list-units

shows

mausberry.service   loaded active running   MausBerry

edit: In other words, I am trying to say you do not even need the board plugged and the script will still run. AFAIK, it just monitors a GPIO line, and executes shutdown command when it senses the switch being pressed.

hondagx35

Hi Dave,

change the last two lines to

[Install]
WantedBy=multi-user.target' > /usr/lib/systemd/system/mausberry.service
systemctl enable mausberry.service

On arch the unit files should go to /usr/lib/systemd/system.
All enabled services will get symlinked to /etc/systemd/system/multi-user.target.wants/ or where the install section points to.

Frank

thedman!

Thanks for your help so far, I've changed the last two lines to those you have recommended and when I issue

sudo bash setupArch.sh

I get the message "Failed to execute operation: Too many levels of symbolic links"

Thanks again,

Dave.

hondagx35

Hi thedman!,

you have to remove the old symlinks first.

Search for "mausberry.service" and delete all occurrences.

find / -name mausberry.service

Frank

thedman!

Wow! The script has installed properly now and the pi shutdown when pressed so thanks a million for your help people. However it started straight back up again, TBH I expected that, as it is a momentary switch. So I'll experiment with a different switch. However, I've trashed a jumper cable and the switch does nothing at the moment

thedman!

In other words, I am trying to say you do not even need the board plugged and the script will still run. AFAIK, it just monitors a GPIO line, and executes shutdown command when it senses the switch being pressed.

I've just grasped what you've said there Pete!

So in other words if I swap the switch to a latching one, I can remove the mausberry circuit, and it will shut down when I Press the switch. Before I trashed the cable it was shutting down when I pressed the switch and then immediately booting back up, but a latching switch would prevent this.... Hopefully all my replacement parts will arrive tomorrow so I can test this....

thedman!

I've done a clean install of rune. It works perfectly.

Now i'm trying to use this retched Mausberry thing... If I try and install the way the manufacturer tells me get the error I put in post 1.

I have edited setupArch.sh with Frank's code:

[Install]
WantedBy=multi-user.target' > /usr/lib/systemd/system/mausberry.service
systemctl enable mausberry.service

and it seems to install then I change my GPIO pins.

When I press the button, it appears to shutdown, however the screen is still powered on and the two led lights on the pi(3) activity and power(?) remain on constantly, as does the dac. If i press the button (momentary switch) again, nothing happens, I cannot ssh to it. I have to turn the power off at the wall then on again to get it to boot up.

I thought it was supposed to work as follows: When Pi is on, press button, pi powers off (i.e. dead, no lights, nothing) then when re pressed, mausberry releases power to pi and it boots up.

Can someone tell me where i'm going wrong please????

Thanks in advance,

Dave

PeteB

What do you mean when you say this?

then I change my GPIO pins

thedman!

I change it in /etc/switch.sh, from the default ones in the script, 23 and 24 to 17 and 22.

PeteB

Ok, so it worked with the default numbers, but not after you changed it?

thedman!

I will check with the default pins again, the problem with those is that they are shorter so the jumper cables are very loose. I'll try and post the results....

thedman!

Yep, just tested, on the default GPIO pins it works as before, when the switch is pressed, it shuts down (quickly) , then both the screen and the pi power off very briefly, then it all boots up again.

thedman!

No i've changed the pins back on the board and the code, it displaying the same as when it was not on the default pins. Now i'm going to remove all traces of mausberry and reinstall it...

thedman!

Hmmmm, I think the not shutting down thing is a loose connection, when i hold the jumper wires against the pins firmly it shuts down and immediately reboots, if i don't hold them it doesn't shutdown properly...

thedman!

I think I'm gonna look at a Python script like https://www.raspberrypi.org/forums/viewtopic.php?t=63561 and a non-momentary switch...

hondagx35

Hi thedman,

thedman! wroteI thought it was supposed to work as follows: When Pi is on, press button, pi powers off (i.e. dead, no lights, nothing) then when re pressed, mausberry releases power to pi and it boots up.

Yes, it should work this way.

What happens when you execute this command:

echo "0" > /sys/class/gpio/gpio24/value

Please double check your cabling. Those jumper wires break easily.

I think I'm gonna look at a Python script like https://www.raspberrypi.org/forums/viewtopic.php?t=63561 and a non-momentary switch...

This will not help, because it uses the same mechanism.

Frank