Follow up…
Tested GPIO18, GPIO19 with a simple LED / Python script. Everything worked as expected.
import RPi.GPIO as GPIO
import time
GPIO.setmode(GPIO.BCM)
GPIO.setwarnings(False)
GPIO.setup(18,GPIO.OUT)
GPIO.setup(19,GPIO.OUT)
print "LED on"
GPIO.output(18,GPIO.HIGH)...
> I should have been more explicit. I'm using a RaspberryPi 3B+. Are the pins the same?
I realised that was a dumb question.
Follow up hopefully not as dumb…
Is there are mapping from GPIO 18/19 to port 1/2?
I'll take a stab and say yes… GPIO 18 = Port 1 data, GPIO 19 = Port 2 data?
I'm going to check the pins on the board to see if any of the solder is busted or the connections don't look right.
> They are GPIO18 and GPIO19 and on pins 12 and 35.
I should have been more explicit. I'm using a RaspberryPi 3B+. Are the pins the same?
Thanks for the hint Al.
I ran the tests with power going into each of the 12v and 5v but with different data sources.
End result is:
* 5v lit up when powered by the 5v and with port 1 data
* 12v did not light up when powered by the 12v with port 2 data
Seems like the port 2 data is not...
From the manual
> Using the WS2811 outputs disables the onboard audio and external usb audio must be plugged in and configured if needed.
Is this still the case with the rPi-28D+?
I had a fully working display which consisted of a mix of 5v strip and 12v pixels. The display was powered by a rasberry pi 3 and a rPI-28 controller.
A week ago I decided to update FPP from v3.3 to the latest which included a full os reinstall.
When I plugged everything back in the 5v lights...