Author Topic: Pixels to ports  (Read 592 times)

Offline rposgood

  • Jr. Member
  • **
  • Posts: 72
    • View Profile
Pixels to ports
« on: March 18, 2018, 07:29:30 AM »
Are there any videos or references that can explain how my layout actually is translated to ports? I will be using a falcon f16v3 controller. I will also be using fpp.

THANKS
Try it..... what's the worst that could happen.

Offline MikeKrebs

  • Full Member
  • ***
  • Posts: 123
    • View Profile
Re: Pixels to ports
« Reply #1 on: March 21, 2018, 10:41:33 AM »
The basics are follow the xlights/vixen/fpp mapping channels.
In fpp, you direct them out the appropriate device (likely e1.31).
The actual port setup is done on the falcon.
If you decide to do it in xLights, you can upload the config to fpp and the falcon.  The models have channel mapping/port config and that corresponds to what you setup on the networks page. Found a video:
https://m.youtube.com/watch?v=NsT80wYkEAg
there a bunch out there. If this one doesn't help, watch one of the others.

Offline Gilrock

  • Supporting Member
  • Hero Member
  • *
  • Posts: 6946
    • View Profile
Re: Pixels to ports
« Reply #2 on: March 21, 2018, 11:01:33 AM »
Yeah in your layout the models are mapped to channels.  It's up to you which ports you want to map these channels.  You can try to use to port configuration in xLights and then auto-upload it to the controller but that is more advanced and places restrictions on how you define your models.  Like I had a 5x17 matrix model to run a bush and I defined it as 5 strings of 17 but in reality it was 1 string of 85 so for auto upload to work it cannot be specified the original way.  If you aren't auto uploading then the way I had it originally works fine.