I'm planning to build a 'miniDSP'
(http://www.minidsp.com/products/minidspkits/2-x-in-4-x-out)+'miniDIGI'
(http://www.minidsp.com/products/minidspkits/minidigi) combo into an
amplifier housing that I already have. The miniDIGI has a couple of
Toslink inputs and a couple of RCA SPDIF inputs. The
I think I've found what I'm after, at Canford.
'TOSLINK PLUG' (http://www.canford.co.uk/Products/44-509_TOSLINK-PLUG)
'TOSLINK PLASTIC OPTICAL CABLE 10 metre coil'
(http://www.canford.co.uk/Products/34-891_TOSLINK-PLASTIC-OPTICAL-CABLE-10-metre-coil)
Just a razor blade needed to make them up
I made a second iteration. I learned the benefits of having a ground
plane (or two!) for signal routing, and I improved the layout so that
its easier to connect switches to GPIO pins without soldering. The
middle column is the switch pins, the right hand column is some commonly
unused GPIO
paul- wrote:
> Let me take a look. The time pressed reported in the gpio.c line is
> very long
Is it milliseconds? I make that 2.3 days. :)
chill's Profile: http://forums.slimdevices.com/member.php?userid=10839
foxsam wrote:
> I installed pcp-sbpd and it seemed to not be working right.
How long ago did you do the installation? Paul provided a nice update
on 23rd April, which now seems to cope with multiple buttons, short and
long presses, the option to define any number of new commands in a
config
I posted the same question in the LMS forum, where I thought it was more
relevant, and got some useful pointers from Michael. So I can now
manually create a preset (by editing server.prefs) and then recall it
from a button press. Still working on creating a preset with a button
press.
But now
I made a command to assign Preset#1 to the last remaining unused long
press on my button board (PRE1=[button,preset_1.single]).
The command triggers fine, but does nothing, and I now realise that I
had confused my presets with my favourites! I've never really bothered
with either, so was
That seems to have fixed it for me, thanks Paul.
Code:
1524941845.0229 6 GPIO.c,102: Short PRESS: 135
1524941845.0229 6 control.c,106: Button CB set for button #:1, gpio pin 23
1524941845.0595 6 control.c,217: Button pressed: Pin: 23, Press Type:Short
A few years ago I dismantled an old SB2 to build it into a pre-amp case,
along with a miniDSP processor board. I removed the IR sensor from the
display board, since the faceplate on my pre-amp would block the default
location, and it was always my intention to mount the IR sensor inside a
remote
Thanks Kev, especially for finding the specific posts in that thread
that are most relevant. Now, if you could just have provided direct
links to those posts, to save me all that scrolling .. :)
I've tried one of my other 38kHz diodes wired up to suit the different
pinout order, but I'm
Many thanks Paul
I'll have a play with that this evening.
Just had a read up on pull-up resistors. I assumed the encoder needed 5V
power for the rotary part to function, but I guess that was a rookie
mistake. Is that the 'resist' option in the sbpd command line? (I won't
have access to my
Right - next challenge (for you, not me, I just have to wait a couple of
days and then run the new command :))
How would we go about adding extra commands to the capabilities of this
tool, other than POWR, PLAY, PREV, NEXT, VOL+, VOL- ? I realise there
aren't many others that make much sense
Yes, that's how I've got it now.
/usr/local/sbin/sbpd -d -s e,12,16,VOLM,1 b,17,PLAY,2,0,POWR
b,27,NEXT,2,0 b,22,PREV,2,0 b,4,POWR,2,0 b,23,VOL+,2,0 b,24,VOL-,2,0
The encoder is now connected to 3.3V rather than 5V. But I don't
understand whether the pins it's using (12 and 16) should have
paul- wrote:
> What commands might you want?
>
Well now you ask, not many from that list actually:
muting
play.single
arrow_up
arrow_down
arrow_left
arrow_right
knob_left
knob_right
knob_push
- I could see the 'muting' option being useful occasionally, e.g. if the
player is part of a synched
Wow - plenty to look at there. I don't think I've ever clicked on the
that help button before.
After a quick skim through, I reckon all I'd personally be interested in
for my headless pCP would be:
mixer volume 100
mixer volume +2.5
mixer volume -2.5
mixer muting
play
stop
power (is there any
paul- wrote:
> Let me look at doing a configuration file for commands.
That would be great, thank you. This tool has inspired me have a more
serious go at integrating a pCP inside my amplifier.
I've been tweaking my PCB design so that it will connect to the RPi
either as a hat (should just
cubii wrote:
> so this evening i tried to use more than one butoon, but if i use this
> code:
>
> /usr/local/sbin/sbpd -d -s e,23,24,VOLM,0 b,12,NEXT b,16,PLAY
>
> Both button will do the same? (both are working, Connected to BCM 12 and
> BCM16 and ground)
>
> What is wrong?:confused:
Was
Thanks Paul - I hadn't even looked in the Extensions section before!
I think I did it correctly, but I still have the same problem. But
maybe I didn't do it properly.
Noob alert! How do I remove the old version? I removed sbpd from
/usr/local/sbin, and I removed sbpd.tcz.md5.txt and sbpd.tcz
Thank you. Just for completeness, in addition to the
rotary-encoder-with-push-button, I've wired up a number of simple push
buttons, and I can get any one of them to do any of the programmed
functions on any of the free GPIO pins, but whenever I try to programme
two buttons it goes wrong.
Pippin's 'announcement of a new tool to use buttons and rotary encoders
on a Raspberry Pi'
(https://forums.slimdevices.com/showthread.php?107001-ANNOUNCE-SqueezeButtonPi-Tool-to-use-buttons-and-rotary-encoders-on-a-RPi)
inspired me have a play with hardware controls for a Pi-based player,
and
I've been making up a system to go into a house where the previous owner
has fitted ceiling speakers into most rooms and has conveniently routed
all the speaker wires into a single location. I thought this setup lent
itself to a system based on multiple Raspberry Pi players with attached
chill wrote:
> There's also a couple of other options:
>
> * Toggle a 6dB increase on analog output level
> * Toggle a 0.80dB increase on analog output level
>
I've found a FAQ on the JustBoom website ('here'
(https://www.justboom.co/faqs/#FAQ-8)) that explains those two se
mherger wrote:
>
>
> TBH I'm very much surprised how much I get out of that little power
> using the same amp...
>
That's good to know. Did you configure the Alsamixer Volume to -8dB
(92%) as advised in JustBoom's technical guide? I assume that's to
limit the output power to what the USB
chill wrote:
>
>
> So to limit the output to exactly -8dB I would want to disable the 6dB
> decrease (is that the same as enabling the 6dB increase?) and disable
> the 0.8dB increase, then set the mixer slider to 92%. I guess a quick
> test with some connected speaker
Apesbrain wrote:
> Nice job. I'd be surprised if 1.5W cuts it, but 40W with the bigger
> power supply should be fine.
I suspect it'll need something between those two extremes - I don't
think they are big speakers. That figure of 1.5W is the rms figure - 3W
is the peak figure. The Amp Zero
Thanks Paul - yeah, I'd forgotten about being able to use different
remotes. I may look into how to make a mapping table. But I've been
running a 3B+ plus button board as my own LMS server and main living
room player for quite a while now, and I find that the physical buttons
largely replace
Greg Erskine wrote:
>
> What are you doing with the IR?
I've enabled LIRC on GPIO17, and my original SB3 remote seems to work
perfectly. The IR signal seems unaffected by the PLA of the panel
around the buttons. But this system is going into a house where there
are no native Slim Devices or
Man in a van wrote:
> There is a command line option for squeezelite which allows it to drop
> the connection if not used
Thank you, that could be useful - I'll investigate. I wonder if it
picks the connection up again when Squeezelite tries to play music
again.
A similar option would be
I'm currently building an integrated amplifier based on a Hypex DLCP
system and 6 channels of Hypex UcD amplification. As a long-time
Squeezebox fan I'm also building in a Raspberry Pi 3B+ running pCP into
the enclosure. This will be connected permanently to the single USB
input on the DLCP.
chill wrote:
> I wonder if it picks the connection up again when Squeezelite tries to
> play music again.
Of course it does! This is the 'Close output setting' option in 'Change
Squeezelite settings'. I tried a value of 5 seconds and it seems to
make absolutely no difference to the ap
You know what? This is an Apple household, so I think Shairport-sync
might be all I need. I hadn't paid much attention to it previously, but
now that I see it is an option in pCP I'll have a play. It would be
nice to have my amplifier as an Airport device.
That was easy, and the result is perfect! My amp now shows up as an
Airplay device, and I can play from my iPhone or my Macbook, or I can
use Squeezelite - if one is already playing I just have to pause the
output to let the other take over the DAC. Very smooth.
Jeff07971 wrote:
> I'm not sure I get what you trying to do with changing codes (JVC) you
> can program irrecord to respond to virtually any code type.
I was hoping to just add one key to the existing lircd.conf file. That
file is configured for the original Squeezebox remote:
Code:
I agree that issuing the halt command is easy enough, but in a setup
that's already using sbpd a script wouldn't be necessary. Isn't it just
a case of adding a new command to sbpd_command.cfg, say:
Code:
XLMS=["stopserver"]
...and then assigning
paul- wrote:
> LMS is the problem..you need to halt the system first. You can
> build or buy power relays. To drop power after the kernel shuts down.
I've been trying to understand the foregoing discussion so that I can
shutdown my pCP LMS server(s) safely. I'd appreciate guidance on
Reading more carefully, it seems like the button should be a momentary
button: "After shutdown, the system can be powered up again by driving
GPIO3 low."
So grounding the pin while pCP is running will call the
pcp-powerbutton.sh script, which issues the 'sudo /sbin/poweroff'
command. Grounding
Grounding GPIO3 apparently performs a 'wake from halt', so it seems
it'll only work if the Pi has been halted (e.g. by /sbin/poweroff?). I
think a toggle switch isn't such a good idea, but using a momentary
button to ground GPIO3, to either halt the system or wake it up again,
seems like the
These settings seem to work for the gpio-shutdown overlay:
'[image:
http://www.cjh.me.uk/MyPhotobucket/cache/DIYHifi/RPi%20Board/Pi%20System/Shutdown%20settings_1024.jpg]'
(http://www.cjh.me.uk/MyPhotobucket/albums/DIYHifi/RPi%20Board/Pi%20System/Shutdown%20settings.jpg)
Grounding GPIO3 while
Interesting. I wonder if it's the hard-wired pull-up resistor that's
different then. Or the fact that I2C uses GPIO3.
Feeling a bit guilty about spamming this sbpd thread with this
discussion
chill's Profile:
In my case I don't have a DAC hat - no hats at all in fact. Testing so
far has been with a bare 3B+.
chill's Profile: http://forums.slimdevices.com/member.php?userid=10839
View this thread:
Thanks Paul - that's got it. It seems that the port doesn't autodetect
or default if the '-A' option is used.
chill's Profile: http://forums.slimdevices.com/member.php?userid=10839
View this thread:
Thanks Paul - that's useful. There are various different ways I can
test my hardware, but it's good to know that it *should* still works the
same.
chill's Profile: http://forums.slimdevices.com/member.php?userid=10839
Hi Paul - thanks for your persistence with this. Im looking forward to
trying this build. Unfortunately that wont be till I get home on Sunday
evening.
chill's Profile:
Tried it on my 4B 4GB - the buttons now seem just as reliable as they do
on my 4B 1G. Great stuff.
chill's Profile: http://forums.slimdevices.com/member.php?userid=10839
View this thread:
Hi Paul
I had go with this, but only on my 4B 1GB (on which the wiringpi-based
version works well). The new pigpio-based version also gives me nice
responsive buttons. So far so good. The big test of course will be to
try it on my 4B 4GB, which gives me erratic behaviour with the wiringpi
Thanks for the explanation. Do you have any ideas why the wiringpi
version only seems to struggle on the 4GB version of the RPi4, and seems
fine on the 1GB version?
I understand that the pigpio callback approach means that sbpd still
needs a bit more of a rewrite to handle the callbacks
The first step in tracing what's causing my unreliable buttons.
I connected the same hardware to a 3B+ running pCP4. From a fresh image
I installed LMS and sbpd, then copied my sbpd command configuration file
and my calling script over from the 4B. All nine buttons seem
completely reliable on
Did that. I transferred the SD card with the fresh pCP6 setup from my
4B 1GB to my 4B 4GB, with no other hardware attached except my button
PCBs, and the buttons are erratic on the 4B 4GB. Switched everything
back over to the 4B 1GB, and the buttons work flawlessly.
So it's something about
paul- wrote:
> I have no idea if it would affect GPIO, but it might be worth a shot.
Thanks Paul - that doesn't seem to make any difference unfortunately.
paul- wrote:
>
> Otherwise, can you do your test with one button on one GPIO pin.then
> I might be able to replicate here on my
Paul Webster wrote:
> GPIO Pull up/down differences?
I can't tell. The gpio utility with wiringpi reports that the expected
pins have their pull-up resistors set, i.e. they have a value of 1.
There's apparently a pintest tool as well, but that's apparently not
part of the pCP6 version of
I reverted both of those things, and I still have unreliable buttons.
So what does that leave? A damaged 4B 4GB? Hardware differences between
the 4GB and the 1GB?
chill's Profile:
chill wrote:
>
> 1) The 4GB has an updated bootloader installed - the one which knocked a
> couple of degrees off the CPU temperature. I might see if I can find
> the original one and put it back on.
Wait, I was getting mixed up. I've done two things to this 4B 4GB.
I can't get any response from the encoder.
I'm using this command:
Code:
sudo /home/tc/sbpd-pigpio -v -M dc:a6:32:03:82:22 -f
/home/tc/sbpd_commands.cfg e,21,20,VOLM,2
There's no output at all with the -v option. With -z I get plenty of
output,
My apologies - I did not spot that you'd changed the encoder command
options. I was about to suggest that a warning isn't necessary,
provided the --help output details the change, and then I discovered it
does! Maybe a warning would help after all :-)
Anyway, with the VOLU command it controls
Thanks for testing Paul. I'm not sure I know what you mean by 'the
callback is getting nailed'.
I did some tests with the -z option. The output from the 4GB looks
different from the 1GB, but I don't know how to interpret it.
First a couple of button presses on my reliable 1GB:
Code:
paul- wrote:
> I've not tested with 2 buttons, can you show be a trace with 2 buttons,
> and long an short presses of each button.
Here's an example where I defined two buttons:
- GPIO 22 short press = MIX- (defined as ["mixer","volume","-5"])
- GPIO 22 long press = MUTE (defined as
Some -z output. I've removed all the discovery.c outputs. The four
button presses in the output below were 25, then 22, then 25, then 22.
Code:
Last login: Wed Aug 21 17:14:18 on ttys000
(base) Chris-Hills-MacBook-6:~ iszch$ ssh tc@192.168.1.4
tc@192.168.1.4's
Hi Paul - I only made this suggestion because I assumed it would be easy
to apply the same mechanism that you're using to limit TRAC requests to
one-per-500ms. If there's more to it than that then I'm not even
convinced that one-increment-per-click is needed, so maybe it's not
worth the effort.
Well I'm not sure whether a single detente should correspond to a single
pulse - I believe it probably should. I'm not seeing that happen
reliably. If I click slowly and accurately I see increments of either 1
or 2, with approximately equal probability. Testing with the original
sbpd on my 4B
paul- wrote:
> I realized that I was just calling the same function irregardless of
> pin, this should fix that.
>
> https://dl.dropboxusercontent.com/s/5mlvm1pyu4q6wgp/sbpd-pigpio
>
> I also tweaked the encoder to hopefully soften up the indexing.
Excellent, thank you. The buttons work
paul- wrote:
> You can read and set pins directly from a shell, there is no need for
> external commands.
>
> https://raspberrypi-aa.github.io/session2/bash.html
Perfect, thank you.
chill's Profile:
Could 'this'
(https://forums.slimdevices.com/showthread.php?110902-Perl-compilation-error-ipn=948878=1#post948878)
be related?
chill's Profile: http://forums.slimdevices.com/member.php?userid=10839
View this thread:
No rush at all on my part - both modes work, so we're only talking about
tweaking the user experience here. My encoder is a 'Keyes KY-040'
(https://thepihut.com/products/keyes-rotary-encoder-module).
chill's Profile:
paul- wrote:
> A few updates.
>
> pigpio library is interesting, but I was using it sort of wrong.here
> is a new sbpd binary, its dynamically linked now.
>
> https://dl.dropboxusercontent.com/s/745gzmr26t8ii35/sbpd
>
> Requirements:
> > > >
- pigpio.tcz - library and tools
pCP doesn't automount by default. I believe it might be possible to
achieve that, but I went a slightly different way by scripting the
mounting process (I run an overnight backup via cron, and I check if the
backup disk is inserted and then mount it).
It's also possible to use the 'pCP Command
My sbpd command line, with all but the 'pcp bs' button removed for
clarity.
Code:
sbpd -M dc:a6:32:03:82:22 -A 192.168.1.4 -P 9000 -f
/home/tc/sbpd_commands.cfg b,27,POWR,2,0,SCRIPT:/home/tc/pcp_bs.sh,2000
The -M, -A and -P options force
paul- wrote:
> Youd have to find a way to do this from command line, then use a script
> fired from sbpd
>
> I dont really have time to figure out how to do this directly in sbpd.
Understood. I guess I naively hoped that it would be easier to simulate
a key press inside sbpd than it would
Jursi wrote:
> Yes that's correct! I changed the volume commands to:
> KEY:KEY_VOLUMEUP-KEY_VOLUMEDOWN
>
> Now the player also shows the volume bar when changing the volume.
That's a another benefit of the new keypress emulation. Previously the
volume control applied to a specific player,
Just wondering if it's possible to redirect the sbpd commands to a
Jivelite installation on a difference device. I know the MAC address
option can be used to send commands to a specific player, but if, say, I
have Jivelite running on a Jogger, can I send keystrokes to that
Jivelite somehow?
Jursi wrote:
>
> Chill, could you provide me the script to call sbpd and pigpiod etc. at
> the startup. That would be awesome!
> And how to call it from the tweaks page.
>
Sure - when I get home I'll update to Paul's latest pcp-sbpd.tcz from
the repository, adjust my script to
Here's my script for launching sbpd at start-up. I originally put the
sbpd command into a script file because I had so may buttons configured
that the command was too long to be launched as a User Command. But
having it as a script now allows for the necessary extra steps, such as
launching
That's neat. Two rotary encoders? One for Jivelite navigation, and one
for volume?
chill's Profile: http://forums.slimdevices.com/member.php?userid=10839
View this thread:
Excellent news. I can't say I've got any bright ideas at this point,
but being able to navigate Jivelite will be very useful. If the encoder
supports a 'push' as well, then I'd probably set that up as the 'right'
arrow, and I'd probably put the 'left' arrow on a long push.
I don't think this is going to be possible via LMS. It is possible to
get one or more players in LMS to play an external source, maybe with
some additional hardware (e.g. a USB ADC), but there will always be a
significant delay, so that the TV picture and the sound will always be
out of sync.
tannaroo wrote:
> ok. what connection/how do I attach my Pi/Hifi Berry Amp to the stereo
> amplifier? HDMI?
The Hifi Berry Amp would not be needed in this case. Audio out from the
Pi to the stereo amp can be achieved in various ways. It depends on the
capabilities of the stereo amp. If the
paul- wrote:
> Chill,
>
> Would you mind testing this out for me.
I'll be happy to. My RPi with an encoder doesn't have a screen or
Jivelite, and my RPi with Jivelite and a screen doesn't have an attached
encoder. The latter is easier to fix, so I'll go t
Can I just say what a great addition this is to sbpd. Controlling
Jivelite with a rotary encoder, so that it behaves like an original
Squeezebox Radio or Boom, is something that quite a few people have
wanted an easy way to achieve I think.
This works perfectly with my encoder:
Code:
./sbpd -v e,20,21,KEY:KEY_UP-KEY_DOWN,2
b,26,KEY:KEY_RIGHT,2,0,KEY:KEY_LEFT,500
I had to adjust the 'Detente Mode' setting to 2, so that each click
moves the cursor one position up or down, but after
Jursi wrote:
> Amazing news,
>
> Could you explain me how to install sbpd from your link and how to setup
> pigpio library.
>
> Thank you!
Install pigpio.tcz from the piCorePlayer repository, then make sure the
daemon is running: just type pigpiod from the command line of an SSH
terminal.
Jursi wrote:
>
> I can't find pigpio.tcz from the repository, any idea why?
>
> I am running 4.1.0
Are you looking in the 'piCorePlayer repository', or the 'Official
piCore repository'? It will be in the former, and I suspect the latter
is the default in pCP4. I did this from pCP5. I
Jursi wrote:
> I am looking from the piCorePlayer repository. 28242
chill wrote:
> I don't know for sure whether pigpio.tcz is available in pCP4 - perhaps
> Paul can comment.
I guess that's the answer then. I'm sorry, I don't know if pCP5
extensions are necessarily compatible
Aki7 wrote:
>
> Ok, just found your script in this threat, tested, but seems to accept
> the POWR button only once - switches off.
> Long keypress is working (NEXT) and short keypress (POWR) is working
> after it. But after this no more acceptance of any key press.
> Can switch back to "On"
Aki7 wrote:
>
> 1570738211.9287 3 sbpd.c,202: Could not connect to pigpiod. Is it
> running?
>
> Seems pigpiod is missing. Tried installing pigpio-dev.tcz from the
> pcp-repository without success (after reboot):
>
It's not missing, but you have to load it before you call sbpd. See
'this
I'm refitting my camper van and I want to include LMS running on a
Raspberry Pi. I've had this for a few years, but in the refit I want to
include a touchscreen running Jivelite. My aim is to flush mount the
screen into one of the furniture panels. I opted for the 7" Official
Touchscreen, and
paul- wrote:
> It should work fine. I think Chill did some tests with 2.
Not me - 'Jursi'
(https://forums.slimdevices.com/showthread.php?107001-ANNOUNCE-SqueezeButtonPi-Tool-to-use-buttons-and-rotary-encoders-on-a-RPi=951571=1#post951
paul- wrote:
> That is surface mount connector. (Look at ralphy's picture) It won't
> work with the through hole pcb design.
Our posts seem to have crossed. I agree. The low-profile through-hole
version might save me enough space - I'll measure up.
Hmm - the Amp Zero's header is surface mount, but there do seem to be
low-profile through-hole versions. I guess the Amp zero relies on the
header pins passing through the PCB socket, which wouldn't be possible
with a through-hole version. I think I need to do some more careful
measuring.
Thanks Kidstypike - that's a kind offer. I'll send you a PM.
Yes, I think I could quite easily live without the case lid, as the rear
of the panel will be safe inside a cupboard. That's probably a much
more sensible approach than desoldering the header!
jemhayward wrote:
>
> and so on, so the encoder is working and sbpd is reading it, but it
> doesn't seem to be communicating with LMS - "mixer","volume","+1"
> sounds right...
Is this running on the same device as squeezelite?
You can specify which player the commands should apply to:
...and do you have more than one instance of LMS running on your
network? You can also specify the IP address (-A) and the port (-P) for
the server, in case it's autodetecting the wrong one.
chill's Profile:
jemhayward wrote:
>
> Are there any diagnostics I can do to make sure the script has
> successfully run, and anything I can use to 'detect' my encoder on those
> pins in case the encoder is broken?
Yes - don't run your script from the User commands section of pCP, but
start it manually, and
That's a marvellous project. The NFC idea is inspired - absolutely
perfect for the younger user.
chill's Profile: http://forums.slimdevices.com/member.php?userid=10839
View this thread:
Whenever wrote:
> I would like to have the remote Powercycle work regularly so that it
> would mostly happen when it has not frozen. If it gets to the full
> frozen state then I would have to unplug.
If you update the Radios to the latest 'Community firmware'
This should be straightforward. You'll need a 'momentary' switch,
rather than a toggle switch, because the action associated with a button
is triggered when the gpio pin is earthed briefly. You can set it up so
that the button issues the 'pause' command when it is pressed. 'Pause'
will pause
chill wrote:
>
> You'll need to install the sbpd extension, and I'm not sure if that also
> installs pigpio as a dependency - if not, install that too.
>
I just checked - the pcp-sbpd.tcz extension does install pigpio.tcz as a
dependency.
The -v option in the command in t
Pommes wrote:
>
> Thing is: now i am at his place where parts like buttons and knobs are
> not readily available.
If you only have, say, a light switch available I guess you could make
it work with that, but you'd have to make it clear that the switch would
have to be toggled one way and then
The audio problem could be the mode that pigpio is using. I cant recall
the details. Ill check when I get back to my laptop and let you know.
chill's Profile: http://forums.slimdevices.com/member.php?userid=10839
View
skywalker wrote:
> Hi,
>
> i have this rotary encoder AZDelivery
> KY-040(https://www.amazon.de/gp/product/B079H3C98M/ref=ppx_yo_dt_b_asin_title_o01_s00?ie=UTF8=1)
> and i conneted
> GND to PIN 25
> + to PIN 1
> SW to PIN 29 (GPIO 5)
> DT to PIN 37 (GPIO 26)
>
>
I have the same encoder. It
What command line options did you use with pigpiod?
Do you have any other devices attached to this RPi?
chill's Profile: http://forums.slimdevices.com/member.php?userid=10839
View this thread:
slartibartfast wrote:
> I read in another thread that wiringPi wasn't used any more with
> piCorePlayer so I wonder where it came from.
>
That's correct. sbpd now uses pigpio instead of wiringpi. If you
install pcp-sbpd.tcz from the piCorePlayer respository, it will install
pigpio as a
1 - 100 of 104 matches
Mail list logo
