Output to BBB - P10

[uzelessknowledge]

Thanks Jon.


Travis
Sent from my iPhone using Tapatalk

[Gilrock]

I have mine setup in reverse.  I use the wireless on the PI to connect into my home network because that's only needed to start and stop shows or upload sequence changes.  I like the hard wired Ethernet output to drive data to the controllers.

[gerry]

Same as Gil (setup), and I think most others are doing it that way. The Wifi (connected via the home network to the internet) gets the time.
Used Unicast last year (first year and someone set it up that way for me) , but am using multicast this year for the same lag reasons if one controller is off. (Which in testing is a hassle to have them all connected and on).

[uzelessknowledge]

My remote is driving the controller and wired to router. BBB driving p10 and wired to router. Master is wifi to router only cause it's inside with FMT. It's wired to home network.

I thought this was ok since the master is only sending small packets to tell the others what to do.


Travis
Sent from my iPhone using Tapatalk

[Gilrock]

Yeah if your just controlling slaves it should work fine.  I actually found out by accident that the FPP was capable of controlling slaves that were on a completely different subnet by the sync packets going out the wireless dongle.

[uzelessknowledge]

👍


Travis
Sent from my iPhone using Tapatalk

[tpctech]

I would like to create several sequences in the BBB to drive 4 P10 panels to show song name etc.  I have all these created and working yea!!   What is the best way to trigger these to play either from Xlights on the show computer or PI?

Is there a way to trigger these similar to to model in the time line?  Also is there a way to send out a windows command line or serial string this same way?

Ken

[Gilrock]

I would like to create several sequences in the BBB to drive 4 P10 panels to show song name etc.  I have all these created and working yea!!   What is the best way to trigger these to play either from Xlights on the show computer or PI?

Is there a way to trigger these similar to to model in the time line?  Also is there a way to send out a windows command line or serial string this same way?

Ken

Run the Pi as a Slave and then name the sequences with the same name as what you are running on the Master FPP.  The Master will send sync packets telling the Slave(s) what sequence it's playing and they will look for the same base name and play that sequence.

[uzelessknowledge]

So I changed to multi sync and it caused the show network to become slow and then unresponsive. I had to disconnect the Pi and it helped a little, but resetting the router was the real fix.
I switched back to unicast and had no issues.
Thought and suggestions?

[Gilrock]

Having trouble knowing exactly what you tried.  You said you changed to multi sync then back to unicast.  So I'm thinking you meant you switching to multicast and back to unicast.  That's different than what I was saying.  Multi sync is when you tell one FPP its master and another FPP it's slave.  In the Master you need to find the Multisync settings and check the box beside the FPP that's the slave.  Multicast vs Unicast is just how the FPP communicates to the pixel controllers.

[uzelessknowledge]

Having trouble knowing exactly what you tried.  You said you changed to multi sync then back to unicast.  So I'm thinking you meant you switching to multicast and back to unicast.  That's different than what I was saying.  Multi sync is when you tell one FPP its master and another FPP it's slave.  In the Master you need to find the Multisync settings and check the box beside the FPP that's the slave.  Multicast vs Unicast is just how the FPP communicates to the pixel controllers.

Let's try this again. Funny how my phone has learned to autocorrect to multi sync.

I was referring to what we talked about before. Somewhere around post 13.
I tried multicast and unicast. Multicast slowed down the show network. Unicast did not.

[Gilrock]

So run unicast.  I've used it fine for 2 years.  But I was trying to tell you how to trigger sequences on the P10 panel.  If you read my last 2 posts it should tell you how to do that.

[gerry]

This is what I have done - hope it helps.
The sequence  xxx.xml has effects for all models including the BBB. The xxx.fseq is uploaded to the both the PI-FP and BBB-FP as xxx.fseq. Pi and BBB connected to router via Cat5 which is connected to Pixlite via Cat5 .
PiFP set to master and BBB FP set to slave and multisynch enabled. All universes unique ie no duplicates.

(Unicast / multicast does not matter . If Unicast - all controllers must be on)
PiFp has a Wifi dongle to connect to home network for internet time

On BBB FP , only define universes of panels

Play playlist on master. The PI FP sends data to the Pixlite only (if Unicast) and BBBFP sends data to the panels only.

If u are having an issue with multicast , then switch to unicast.

In the xl setup tab , define all the universes and make sure that Unicast / Multicast is the same as what you are using on the FPs. Then you can use the output to lights and get the same result.

[uzelessknowledge]

Thank you Gil and Gerry.
I think I've got the multicast down.
Thank you for your advice on unicast/multicast.

I do have a question about unicast and all controllers must be one.
Does this mean they must be on if the sequence is built to send data on them OR must be on if the FPP is configured for them?

[JonB256]

I do have a question about unicast and all controllers must be on.
Does this mean they must be on if the sequence is built to send data on them OR must be on if the FPP is configured for them?

If an E1.31 universe is set to Unicast in your transmitting software (Vixen, LOR, xLights, FPP or others), then a response from a controller using that Universe's IP address is expected. If not received, then ARP packets get sent out, slowing down the whole process.

So, Yes, the controller must be on, connected and able to receive and send on the network.

As a side note from a happy Multicast user, my Wireless Router (ASUS RT-N66U) has a setting in it to not forward Multicast packets. I found that 2 seasons ago and all my Wireless congestion complaints went away. Was a lot easier than setting up multiple domains.