Jeff07971 wrote: 
> Hi Cliveb,
> 
> You don't actually have to do any scripting to do this its built into
> pCP (SL actually)
> 
> I use Powerswitch3 for my SB3's and pCP built in for my pCP based
> players
> 
> All drive 16A SSR's directly
> 
> Jeff
> 
> 32631
> 
Well, my apologies for not finding out about this! A genuinely
embarrassing face-palm moment on my part.

That said, I have now tried playing around with the Squeezelite Power
on/off GPIO settings, and haven't been able to make it work. Let me just
ask a couple of questions to make sure it does what I'm hoping for:

1. The help for the setting says: "Squeezelite will toggle this GPIO
when the Power On/Off button is pressed"
I interpret this to mean that when I click the power button for the
picoreplayer in the LMS web interface (and by extension, if I switch the
player on/off using a Duet controller or phone app such as Squeezer), it
should toggle the GPIO pin. Is that correct? I hope it is, because
that's exactly what I want it to do.

2. What numbering for the GPIO pins is used in this setting? Does it use
the physical hardware pin numbers, the (non-sequential) RPi numbering,
or some other scheme?
I ask this because I've tried both physical and RPi numbering, and
neither seem to work.
For example, if I set the Squeezelite to use GPIO 13, is this the
physical pin #13 (aka GPIO 27 in RPi-speak), or physical pin #33 (aka
GPIO 13)? I've tried checking both pins with a multimeter, and neither
seem to toggle. Pin #33 (GPIO 13) stays stubbornly high, and pin #13
(GPIO 27) stays stubbornly low.
Another way of asking the question:
If I set the Squeezelite power on/off to GPIO 13, which physical pin
will it control?



Transporter -> ATC SCM100A
------------------------------------------------------------------------
cliveb's Profile: http://forums.slimdevices.com/member.php?userid=348
View this thread: http://forums.slimdevices.com/showthread.php?t=113507

_______________________________________________
discuss mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/discuss

Reply via email to