Home › Technical › FPP Players

🎛️ FPP Players — Zone & NDB Mapping

Each FPP (Falcon Player) runs pixel sequences and sends DDP Raw Channel data to NDB controllers. Universe size is typically 8192 or 8193 channels per output.

FPP Player Overview

HostnameIPPlatformZoneFPP VersionNotes
forest-pix110.50.0.11Debian / NUC6CAYHFlowersFPP 9.x-805—
forest-pix210.50.0.12DebianFire——
forest-pix310.50.0.13RPi4MushroomsFPP 9.4—
forest-pix410.50.0.14DebianHuts——
forest-pix510.50.0.15DebianSpring——
forest-minipix110.50.0.20RPi3B+Clocks—CPU 100%
forest-minipix210.50.0.21RPi3B+RainFPP 9.4CPU 100%
forest-minipix310.50.0.22RPi4Garden CentreFPP 9.4MQTT disconnected
forest-minipix510.50.0.24—Confirm——
forest-Music310.50.0.227RPi3BAudioFPP 9.4—
forest-Music410.50.0.228RPi3BAudioFPP 9.4—
⚠️
forest-minipix3 has MQTT disconnected — check broker config.
forest-minipix1 and forest-minipix2 are running at CPU 100% — investigate sequence complexity or resource constraints on RPi3B+.

forest-pix1 — Flowers (10.50.0.11)

Output #NDB LabelNDB IPProtocolUniverse SizeStatus
1NDB610.50.0.55DDP8192Active
2NDB2310.50.0.72DDP8192Active

forest-pix2 — Fire (10.50.0.12)

Output #NDB LabelNDB IPProtocolUniverse SizeStatus
1NDBballs (NDB3)10.50.0.52DDP8192Active
2NDBhem1 (NDB14)10.50.0.63DDP8192Active
3NDBhem2 (NDB24)10.50.0.73DDP8192Active
4NDBhem3 (NDB18)10.50.0.67DDP8192Active
5NDB1sticks (NDB22)10.50.0.71DDP8192Active

forest-pix3 — Mushrooms (10.50.0.13)

Output #NDB LabelNDB IPProtocolUniverse SizeStatus
1NDB410.50.0.53DDP8192Active
2NDB110.50.0.50DDP8192Active
3NDB810.50.0.57DDP8192Active
4NDB110.50.0.50DDP8192Duplicate
⚠️
NDB1 (10.50.0.50) appears twice in forest-pix3 outputs (Output 2 and Output 4). Confirm whether this is intentional (e.g., different channel ranges) or a configuration error.

forest-pix4 — Huts (10.50.0.14)

Output #NDB LabelNDB IPProtocolUniverse SizeStatus
1NDB1110.50.0.60DDP8192Active
2NDB910.50.0.58DDP8192Active
3NDB1010.50.0.59DDP8192Active
4NDB2610.50.0.75DDP8192Inactive (ping fail)
5NDB210.50.0.51DDP8192Inactive
6NDB2110.50.0.70DDP8192Inactive

forest-pix5 — Spring (10.50.0.15)

Output #NDB LabelNDB IPProtocolUniverse SizeStatus
1NDB2010.50.0.69DDP8192Active
2NDB1710.50.0.66DDP8192Active (ping fail)
3NDB1310.50.0.62DDP8192Active (ping fail)
4————Inactive

forest-minipix1 — Clocks (10.50.0.20)

Output #NDB LabelNDB IPProtocolUniverse SizeStatus
1NDB3310.50.0.82DDP8192Active
2NDB2810.50.0.77DDP8192Active (label mismatch)

forest-minipix2 — Rain (10.50.0.21)

Output #NDB LabelNDB IPProtocolUniverse SizeStatus
1NDB710.50.0.56DDP8192Active
2NDB3410.50.0.83DDP8192Active
3NDB2810.50.0.77DDP8192Active (label mismatch)

forest-minipix3 — Garden Centre (10.50.0.22)

Output #NDB LabelNDB IPProtocolUniverse SizeStart ChannelStatus
1NDB2710.50.0.76DDP8193OffsetActive
2NDB210.50.0.51DDP8193OffsetActive
3NDB2110.50.0.70DDP8193OffsetActive
ℹ️
All outputs on forest-minipix3 use offset start channels (universe size 8193). Verify channel mapping if adding new outputs.

forest-minipix5 (10.50.0.24)

Output #NDB LabelNDB IPProtocolUniverse SizeStatus
1NDB1510.50.0.64DDP8192Active
2NDB3210.50.0.81DDP8192Active

Full NDB Assignment Summary

NDB #IPZoneFPP PlayerLabel in FPP
NDB110.50.0.50Mushroomsforest-pix3NDB1 (duplicate output)
NDB210.50.0.51Garden Centreforest-minipix3NDB2
NDB310.50.0.52Fireforest-pix2NDBballs
NDB410.50.0.53Mushroomsforest-pix3NDB4
NDB510.50.0.54Unconfirmed——
NDB610.50.0.55Flowersforest-pix1NDB6
NDB710.50.0.56Rainforest-minipix2NDB7
NDB810.50.0.57Mushroomsforest-pix3NDB8
NDB910.50.0.58Hutsforest-pix4NDB9
NDB1010.50.0.59Hutsforest-pix4NDB10
NDB1110.50.0.60Hutsforest-pix4NDB11
NDB1210.50.0.61Unconfirmed——
NDB1310.50.0.62Springforest-pix5NDB13 (ping fail)
NDB1410.50.0.63Fireforest-pix2NDBhem1
NDB1510.50.0.64TBCforest-minipix5NDB15
NDB1610.50.0.65Unconfirmed——
NDB1710.50.0.66Springforest-pix5NDB17 (ping fail)
NDB1810.50.0.67Fireforest-pix2NDBhem3
NDB1910.50.0.68Unconfirmed——
NDB2010.50.0.69Springforest-pix5NDB20
NDB2110.50.0.70Garden Centreforest-minipix3NDB21
NDB2210.50.0.71Fireforest-pix2NDB1sticks
NDB2310.50.0.72Flowersforest-pix1NDB23
NDB2410.50.0.73Fireforest-pix2NDBhem2
NDB2510.50.0.74Unconfirmed——
NDB2610.50.0.75Huts (inactive)forest-pix4NDB26 (ping fail)
NDB2710.50.0.76Garden Centreforest-minipix3NDB27
NDB2810.50.0.77Rain / Clocksminipix1 & minipix2NDB28 (label mismatch)
NDB2910.50.0.78Unconfirmed——
NDB3010.50.0.79Unconfirmed——
NDB3110.50.0.80Unconfirmed——
NDB3210.50.0.81TBCforest-minipix5NDB32
NDB3310.50.0.82Clocksforest-minipix1NDB33
NDB3410.50.0.83Rainforest-minipix2NDB34
NDB3510.50.0.84Unconfirmed——

Issues & Action Items

#IssueAffectedDetailPriorityStatus
1Duplicate DDP outputforest-pix3 → NDB1 (.50)NDB1 appears as Output 2 and Output 4. Confirm if intentional (different channel ranges) or remove duplicate.HighOpen
2Label mismatchNDB28 (.77)Physical label does not match FPP output config. Used by both minipix1 (Clocks) and minipix2 (Rain).MediumOpen
3Ping failNDB13 (.62)Assigned to forest-pix5 (Spring) but not responding to ICMP. Check power & network cable.HighOpen
4Ping failNDB17 (.66)Assigned to forest-pix5 (Spring) but not responding to ICMP. Check power & network cable.HighOpen
5Ping failNDB26 (.75)Assigned to forest-pix4 (Huts, inactive output). Not responding to ICMP.MediumOpen
6CPU 100%forest-minipix1 (.20)RPi3B+ running at full CPU. Investigate sequence complexity or consider upgrading to RPi4.HighOpen
7CPU 100%forest-minipix2 (.21)RPi3B+ running at full CPU. Investigate sequence complexity or consider upgrading to RPi4.HighOpen
8MQTT disconnectedforest-minipix3 (.22)MQTT broker connection lost. Check broker address, credentials, and network connectivity.HighOpen
9Unconfirmed NDBsNDB5, 9-12, 16, 19-20, 25, 29-31, 33, 35Zone assignment and FPP player mapping not yet verified. Walk site to confirm physical locations.MediumOpen
10forest-pix3 duplicateNDB1 (.50)Appears in NDB registry as potential duplicate. Cross-reference with forest-pix3 output config.HighOpen