News:

LATEST RELEASE:  FPP 8.0 - Download from here - https://github.com/FalconChristmas/fpp/releases/tag/8.0

+-+-

+-User

Welcome, Guest.
Please login or register.
 
 
 
Forgot your password?

+-Site Stats

Members
Total Members: 16527
Latest: DDSchrader
New This Month: 15
New This Week: 7
New Today: 1
Stats
Total Posts: 133162
Total Topics: 16553
Most Online Today: 108
Most Online Ever: 7634
(January 21, 2020, 02:14:03 AM)
Users Online
Members: 2
Guests: 36
Total: 38

What is the second pin used by FPP for Pixel Strings?

Started by lrhorer, December 24, 2023, 12:25:39 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

lrhorer

I would search the forum for an answer to this, but right now search is disabled.  I want to add the capability to control a second string from my Raspberry Pi, and of course FPP supports that.  I know the first string employs pin 12 (GPIO 18), but what pin does the second string use?

Poporacer

If you mouse over the ports, it will tell you! It is 19
You cannot view this attachment.
If to err is human, I am more human than most people.

lrhorer

Thanks!  Not here, it doesn't.  Right now I am only running 5.5.  I presume it works in later releases?

GPIO 13 would have been my first guess, followed by 19.

CaptainMurdoch

The old driver uses PWM to drive WS281x pixels on the Pi, so it is fixed at GPIO 18 and 19.  The new DPIPixels driver which allows 24 strings of pixels on the Pi uses the 24 RGB pins assigned to the DPi output and any can be used in any order because the pinout is determined by the cape eeprom image.
-
Chris

Support FPP

+- Recent Topics

Powered by EzPortal
Powered by SMFPacks Menu Editor Mod