f16v4 wont play in Player or Master Mode

[Oxytousc]

I'm trying to run a dirt simple sequence on my f16v4 in player or master mode. It was working fine until today when I started getting FSEQ unsupported errors. It'd play and then stop after like 15 minutes. I rebooted it and put in a new SD card. Now it won't let me even click play. No audio. Literally just trying to have Candy Cane effect on loop.You cannot view this attachment.

[rudybuddy]

Assuming you're using xlights...try rendering your sequence using V1 rather than default V2. You can change it in the Preferences > Sequence menu. 

[Oxytousc]

Thanks. That seemed to fix it. Now, if I could only figure out how to get the Raspberry Pi properly working and be able to take the Falcon out of player mode that'd be great--at least I've got lights again.

[Poporacer]

Now, if I could only figure out how to get the Raspberry Pi properly working and be able to take the Falcon out of player mode that'd be great

What is the problem with that? Have you looked in the FPP Manual? It has step by step instructions and networking examples.
https://falconchristmas.github.io/FPP_Manual(6.0).pdf

[Oxytousc]

Yea. I need to find time to actually spend doing it step by step, but it's hard with kids.

And, now, the controller seems to not be playing again--even after switching to V1. It works and then it stops in player mode.

[Oxytousc]

The problem is getting the Pi to output to the Falcon. I can get it half of the way there. I got a few pixels to light up, but that was it. Now I can't even do that.

[Oxytousc]

Well, I somehow stumbled into fixing the Pi outputs. Now, the problem I'm having is the two identical strips of ws2815s that I have outlining the two floors of the house are outputting slightly different colors, despite having the same setup on the Xlights and controller side--when I had them running through just the controller they were outputting sequenced and same colors.

[aquinones3]

I'm following this because I'm having the same issue, I can't get my fpp pi4 to output to my f16v4. I made a proxy seems I can now find it through my pi. But I still can't figure out why I can't sequence anything. 

[Poporacer]

The problem is getting the Pi to output to the Falcon. I can get it half of the way there

Can you explain a little more? What is "half the way there" mean? Are you letting xLights manage your Controller and FPP device? If not, I would highly recommend doing so, it will make your life so much easier. 

Tell us how you have everything connected together with IP addresses. 
Something like:
Computer to Home network Via Wi-Fi
Network switch connected to home network
FPP connected to Switch
F16 connected to Toaster

And a screenshot of your Controller set up in xLights
Did you use FPP Connect? Show us a screenshot of that page as well.

[aquinones3]

My problem is I can't get anything out to the controllers and I'm just stuck. I'm still a newbie, can a show for 3 years on a pi hat but expanded this year with a F16v4 and two smart controllers V2.

so Ive watched all the videos and read the manual like 3 times, I have my wifi setup on my Raspberry pi4 running fpp6.2. I set a static etho connection, and created a proxy. now I can access my falcon f16v4 through the proxy option and opens. but I cannot get the fpp to talk to the f16. no testing works unless I go through the actual board.

[Poporacer]

My problem is I can't get anything out to the controllers and I'm just stuck.

Provide the requested info and maybe someone can help. Without any information we really can't help you. Everyone does things a little different and what works for one, might not work for you.

[aquinones3]

what more do you need to know? for some reason doesn't let me upload pictures on this chat. but my pi is on a separate network hooked up to the wifi

FPP configuration

IP wifi is - 192.168.1.22
netmask - 255.255.255.0
Gateway is my home network 192.168.1.1

eth0

IP - 192.168.0.150
netmask - 255.255.255.0
gateway is 8.8.8.8

DNS
DNS Server 1 - 192.168.1.1
DNS Server 2 - 8.8.8.8

IP Forwarding is on forwarding on the eth0 one only not sure if it needs to be set on both.

my f16v4 configuration is

IP 192.168.0.151
Gateway is 192.168.1.1
Subnet mask 255.255.255.0
DNS 8.8.8.8

controller is set to zcpp

[Poporacer]

for some reason doesn't let me upload pictures on this chat.

You have to reply, not quick reply to get the option to upload/insert pictures. Or go to the Preview, that will allow it

You didn't describe exactly how things are connected so I will assume that your F16 is wired directly to your Pi?

eth0

IP - 192.168.0.150
netmask - 255.255.255.0
gateway is 8.8.8.8

Delete the gateway!

IP Forwarding is on forwarding on the eth0 one only not sure if it needs to be set on both.

You do not need IP forwarding on the eth0, it needs to be on the wlan0 side and a better option is Masquerade/NAT

my f16v4 configuration is

IP 192.168.0.151
Gateway is 192.168.1.1
Subnet mask 255.255.255.0
DNS 8.8.8.8

The Gateway needs to be the device that is bridging your networks and on the same subnet (In your case it will be 192.168.0.150)
This info is covered in far greater detail in the FPP Manual here:
https://falconchristmas.github.io/FPP_Manual(6.0).pdf#page=162

controller is set to zcpp

FPP does not support the ZCPP protocol, you need to choose E1.31 of DDP (If you have the newer firmware)

Are you letting xLights manage your controllers? I would HIGHLY recommend doing so. You still need to configure the inputs and outputs on the FPP and your controller, if you let xLights manage your controllers, it is simply a matter of pressing a couple buttons. If not, then you have to enter all of the information from xLights into both devices in both the input and output sections.

[JonD]

You do not need IP forwarding on the eth0, it needs to be on the wlan0 side and a better option is Masquerade/NAT

Last I knew, if you enable IP forwarding on either interface, it automatically enables it on both.  I don't use the feature, but I have helped enough people that seems to be the case.  In some situations it will not appear immediately, but if you enable it on one interface, reboot, then review the settings after, both interfaces will show it enabled.  You can correct me if I am wrong, but pretty sure that is the case.

[Poporacer]

Last I knew, if you enable IP forwarding on either interface, it automatically enables it on both. 

I just tested it, and it is interface specific. Even after a reboot.