He has added a "Letters to the Editor" article today:
https://darko.audio/2019/06/letters-to-the-editor-squeezebox-dutch-dutch-more/
pputzer's Profile: http://forums.slimdevices.com/member.php?userid=36842
View this
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.
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:
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
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
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)?
SteliosD wrote:
> Hello,
> I have been trying to remove the text at boot and add a custom image
> instead.
> I couldnt find any similar posts for picoreplayer , only some posts for
> tinycore.
> So far i have managed to remove some of the text and the raspberry pi
> logo via editing the
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 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
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
So after building a piCorePlayer with the 'RaspTouch'
(https://www.audiophonics.fr/en/boitiers-diy-boitiers-divers/rasptouch-chassis-accessories-and-touchscreen-7-kit-diy-black-p-11250.html)
chassis (very nice, but costly), I moved the SBT from the living room to
replace the "broken" SB3 in the
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,
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
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,
JoeMuc2009 wrote:
>
> > > >
- did IR Blaster work previously? How did it stop? Did it become
> more and more unreliable, or did it fail at one point?
> > >
>
It did work before, but after a move, the SB3 was set up again in a new
place. When that happened, the blaster did not
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
philippe_44 wrote:
> If you are in NAM, I fix these as a hobby b/c I want to help the LMS
> ecosystem to stay alive as long as possible. Just send it to me
I assume NAM means North America? Thanks, but unfortunately, Im living
in Europe. Is there a forum for region-based "adoption offers" for
I'm also thinking of abandoning my aging SB3 (late Logitech era, all
black). While the SB3 itself works fine (though the reported WIFI
strength is very low), the IR emitter seems to be fried - no output
generated by IR blaster (checked with a phone that reliably can see the
IR diodes firing). Of
I've got an SB3 that seems to be in good working order, except that IR
blaster is not able light up IR diodes plugged into the headphone jack.
I'm assuming it's probably the capacitors, but replacing those is beyond
my soldering skills.
karlek wrote:
> When you hold the Left Arrow key, you get to the Settings.
> There under
> #2 Current Settings you'll find
> ##16 Factory Reset
>
> I think, this should trigger the desired reset (but I didn't try ;) )
Thanks! I was looking under "Settings" after normal boot-up, not in the
I'd like to sell my old SB3 (classic), but the remote took some damage
from a leaking battery, so the upper buttons (Sleep, Power, Skip/Pause,
Add) are not working anymore (not sure if that could be fixed using
conducting lacquer?). The arrow keys and everything below are working
fine, so I was
chill wrote:
> I'm no expert, so does this look to anyone else as though the mixer
> volume change request was initiated by iPeng at [21-03-29
> 18:24:00.4061]? That would be odd if so, because my phone was lying
> untouched on the table. I don't recall exactly when was the last time I
> had
23 matches
Mail list logo
