pputzer wrote:
> The original wiring I had was correct. The missing piece was that the
> gpio-poweroff overlay needs "active_low" to be enabled (either the
> posting by Audiophonics contained a typo, or they changed the board
> later on). With the wiring according to the Audiophonics pictures an
pputzer wrote:
> The original wiring I had was correct. The missing piece was that the
> gpio-poweroff overlay needs "active_low" to be enabled (either the
> posting by Audiophonics contained a typo, or they changed the board
> later on). With the wiring according to the Audiophonics pictures an
Hi all,
The original audiophonics sript sds.sh had this:
Code:
echo "ShutDown : GPIO17=in, Low"
echo "BootOK : GPIO22=out, High"
echo "SoftSD : GPIO04=out, Low"
gpio -g mode 04 out
gpio -g write 04 0
gpio -g mode 17 in
gpio -g write 17 0
gpio -g mod
audiophonics wrote:
> Now that PiCore discontinued our custom script and is including the
> standard overlays, we should consider to offer the "overlay" version.
Actually that's not totally correct. The new version includes a script
that uses your GPIO values as default and works with your modu
The original wiring I had was correct. The missing piece was that the
gpio-poweroff overlay needs "active_low" to be enabled (either the
posting by Audiophonics contained a typo, or they changed the board
later on). With the wiring according to the Audiophonics pictures and
these settings, everyt
paul- wrote:
> The audiophonics documentation is confusing. And I didn't help, as I
> was referring to this power board.
>
> https://www.audiophonics.fr/en/raspberry-pi-and-other-sbc-accessories/audiophonics-pi-spc-v2-power-management-module-for-raspberry-pi-p-10912.html
>
> But my board has a
The audiophonics documentation is confusing. And I didn't help, as I
was referring to this power board.
https://www.audiophonics.fr/en/raspberry-pi-and-other-sbc-accessories/audiophonics-pi-spc-v2-power-management-module-for-raspberry-pi-p-10912.html
But my board has an IR remote on it, so per
Here's the actual cabling (when the button triggers a shutdown, i.e.
reversed from what I read from the documented pin layout):
27316
Normal operations:
27317
Shutdown triggered (but not complete):
27318
Shutdown complete (but power not cut):
27319
+-
paul- wrote:
> the shutdown is gpio 17, active high, and pull down
Same result. According to Audiophonics images, these are the pin-to-GPIO
mappings:
[image:
https://www.audiophonics.fr/20981-thickbox_default/audiophonics-pi-spc-ii-power-management-power-supply-for-raspberry-pi.jpg]
[image:
ht
the shutdown is gpio 17, active high, and pull down
piCorePlayer a small player for the Raspberry Pi in RAM.
Homepage: https://www.picoreplayer.org
Please 'donate'
(https://www.paypal.com/cgi-bin/webscr?cmd=_donations&business=U7JHY5WYHCNRU&lc=GB¤cy_code=USD&bn=PP%2dDonationsBF%3abtn_donateC
paul- wrote:
> Poweroff is gpio 22, active high
27315
With this setting, the power button never stops blinking after switching
on power. Pushing it again does not trigger a shutdown. When shutting
down the device from the web interface, it does not power off.
+---
Poweroff is gpio 22, active high
piCorePlayer a small player for the Raspberry Pi in RAM.
Homepage: https://www.picoreplayer.org
Please 'donate'
(https://www.paypal.com/cgi-bin/webscr?cmd=_donations&business=U7JHY5WYHCNRU&lc=GB¤cy_code=USD&bn=PP%2dDonationsBF%3abtn_donateCC_LG%2egif%3aNonHos
paul- wrote:
> The settings would be what is printed, just add pull down on gpio 17.
>
> Thanks for letting me know about the getopt issue, there is a hard path
> set in the script.
I'm actually not sure which overlay (corresponds to which "Signal"
(BootOK, ShutDown)?
---
The settings would be what is printed, just add pull down on gpio 17.
piCorePlayer a small player for the Raspberry Pi in RAM.
Homepage: https://www.picoreplayer.org
Please 'donate'
(https://www.paypal.com/cgi-bin/webscr?cmd=_donations&business=U7JHY5WYHCNRU&lc=GB¤cy_code=USD&bn=PP%2dDonatio
paul- wrote:
> The defaults should work for the module, as I used that board to develop
> the setup. But,Ill check it out.
I've experimented a bit more. When disabling the overlays and instead
using the pop-powerbutton.sh script from the home directory (after
linking /bin/busybox to /usr/bin/g
If you meant the GPIOs, Im using the button/power supply together with
an Audiophonics HAT, which has special pins for this. So I am using the
standard GPIOs, but I dont know what the overlay settings should be. (I
think I know, but then the shutdown sometimes only happens after the
next reboot
paul- wrote:
> The GPIO on the rpi has default values for the internal pullup/down
> resistors, we can change them, but not until the kernel finishes
> booting, that can be too late. You need to use a GPIO that matches. IN
> the case of Audiophonics, use the GPIO connections that they recommend
The GPIO on the rpi has default values for the internal pullup/down
resistors, we can change them, but not until the kernel finishes
booting, that can be too late. You need to use a GPIO that matches. IN
the case of Audiophonics, use the GPIO connections that they recommend.
piCorePlayer a sm
I've experimented a bit more. "Pull" has to be set to "up", otherwise
nothing at all happens when I press the button in its operational state.
However, while it has worked when I did a test run, it now appears to
only switch off the RPi after the next reset. Very strange.
--
paul- wrote:
> The defaults should work for the module, as I used that board to develop
> the setup. But,Ill check it out.
I meant the technical default (in the kernel), not the one in the GUI.
Id have to check, but I think they at least differed.
Gesendet von iPhone mit Tapatalk
--
The defaults should work for the module, as I used that board to develop
the setup. But,Ill check it out.
piCorePlayer a small player for the Raspberry Pi in RAM.
Homepage: https://www.picoreplayer.org
Please 'donate'
(https://www.paypal.com/cgi-bin/webscr?cmd=_donations&business=U7JHY5WYHC
paul- wrote:
> Can you let me know how its connected and what rpi you are using, Ill
> setup a test here.
It's an RPi 3B+ connected via WiFi.
When I tried shutting off again last night, it did so only after a
reboot finished. Maybe the overlay settings are not quite right yet?
(Pin 22, active
Can you let me know how its connected and what rpi you are using, Ill
setup a test here.
piCorePlayer a small player for the Raspberry Pi in RAM.
Homepage: https://www.picoreplayer.org
Please 'donate'
(https://www.paypal.com/cgi-bin/webscr?cmd=_donations&business=U7JHY5WYHCNRU&lc=GB¤cy_code
I've got the new Audiophonics PI-SPC II connected with the power button
from the RaspTouch case and after some fiddling, it works - sort of. The
button stops blinking on boot up, and the shutdown handler gets
triggered when there is absolutely no load. As soon as a song is
playing, it takes sever
paul- wrote:
> Which power board do you have? The new model? Link to what you have
> please.
>
> The shutdown-monitor extension was designed for the new board, although
> it will be able to work with any board when we release 5.0
Ah, sorry, I forgot to mention that.:( rpi3B. standard edition
Which power board do you have? The new model?
piCorePlayer a small player for the Raspberry Pi in RAM.
Homepage: https://www.picoreplayer.org
Please 'donate'
(https://www.paypal.com/cgi-bin/webscr?cmd=_donations&business=U7JHY5WYHCNRU&lc=GB¤cy_code=USD&bn=PP%2dDonationsBF%3abtn_donateCC_LG%
Hey Frank
I can confirm that the procedure still works, I have just made a fresh
card and completed the install.
Remember that after loading the extension, you need to click the reset
button.
Also remember to check the Audio output settings for the player after
the reboot.
And don't forget yo
ftarz wrote:
> I have an AUDIOPHONICS I-SABER V4 DAC ES9023 TCXO that is installed in a
> RaspTouch case with a Raspberry Pi 3B+ running piCorePlayer V4.1.0. The
> case power button is wired to the switch and LED pins on the DAC.
>
> The DAC and RPi will power-up when I press the case power but
28 matches
Mail list logo
