Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Servoblaster interfering with NeoPixel rpi_ws281x library #94

Open
prutsky opened this issue Sep 17, 2017 · 3 comments
Open

Servoblaster interfering with NeoPixel rpi_ws281x library #94

prutsky opened this issue Sep 17, 2017 · 3 comments

Comments

@prutsky
Copy link

prutsky commented Sep 17, 2017

I run one servo on a Pi Zero (v1.3) on GPIO4.

For my project I also installed a NeoPixel stick. This uses GPIO18. How can I make Servoblaster not interfere with the NeoPixel GPIO?
As soon as I make install Servoblaster, the NeoPixel does not work anymore as it should. When I uninstall ServoBlaster the NeoPixel LEDs work as they should.
Where can I tell ServoBlaster to not use GPIO18, or is this kind of exclusion not possible?

@amigatommy
Copy link

amigatommy commented Oct 21, 2017

To use only GPIO4 for servoblaster, edit file /etc/init.d/servoblaster:
hang on "--p1pins=7" at the line beginning with "OPTS="
This tells servoblaster to use only GPIO4 as channel 0.
Now you can set servo 0 on GPIO4 to a pulse width of e.g. 1.2ms at the shell prompt:
echo 0=120 > /dev/servoblaster

@amigatommy
Copy link

amigatommy commented Oct 21, 2017

It should work, but i have nearly the same problem with onewire on GPIO4. I defined only
GPIO17 in the /etc/init.d/servoblaster, but onewire dont work anymore, when servoblaster is active.

@srcshelton
Copy link

Apologies, I've only just seen this - please see take a look at my reply at srcshelton#1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants