News:

Server migration complete, Welcome to version 2.1.1

+-+-

+-User

Welcome, Guest.
Please login or register.
 
 
 
Forgot your password?

+-Site Stats

Members
Total Members: 15659
Latest: PaulDzRGB
New This Month: 9
New This Week: 3
New Today: 0
Stats
Total Posts: 128433
Total Topics: 15791
Most Online Today: 48
Most Online Ever: 7634
(January 21, 2020, 02:14:03 AM)
Users Online
Members: 4
Guests: 31
Total: 35

Error- Cannot Ping e1.31 Channel Data Target

Started by MichaelnotMike, December 05, 2022, 05:25:30 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

MichaelnotMike

Cannot Ping e1.31 Channel Data Target Is the message I'm getting in FPP.  I'm running version 5.5 on a RPI 3 B.  I reach the RPI/FPP via WiFi - my home network.  FPP is connected to an F16V3 via Ethernet.  I've used this setup for the past 3 years without problem.

I can reach the FPP just fine. Using the proxy access, I can reach the F16V3.  Test mode on the F16 works on every port.

Attached are: the error message, the FPP Output settings, the F16 e1.31 settings and the F16  port settings. The last two are cut off at the bottom because I'm on my tablet.

I cannot get any output.  I used xLights to upload the output settings.

What other info or screenshots would be helpful in diagnosing this problem?

Thanks in advance.
You cannot view this attachment.

rudybuddy

Looks like you're missing a Unicast Address on the E1.31 output page.

MichaelnotMike


MichaelnotMike

Looks like it should be the address of the device I'm sending data to - 192.168.3.40.  I ran a quick search on the manual and remembered the F16 address by looking at the proxy settings. 

I thank you for the quick help. I'll fix this and let you know what happens. 

MichaelnotMike


Poporacer

Quote from: MichaelnotMike on December 05, 2022, 05:25:30 PMI cannot get any output.  I used xLights to upload the output settings.
Based on your screenshots, you did not upload from xLights or you have xLights configured incorrectly

xLights will normally only upload the Universes you are using,
    In your screenshot your controller is showing that it is configured for Universes 1 to at least 22 when in reality you are only using Universes 12-20

xLights will normally configure one Output line per controller AND will configure the correct Unicast address
    In your screenshot, your FPP is configured for 16 lines of Universes and should only be one line and it doesn't include all of the Universes that your controller needs.
If to err is human, I am more human than most people.

Support FPP

+- Recent Topics

F16V3 with 2 expansion boards at 40 fps MAX PIXELS per output? by BirdingPix
Today at 02:49:02 PM

Warning/Error: Network incomplete frames hit 250. by JonD
Today at 10:59:15 AM

F48V4-NS at 40 fps using all 48 pixel output ports? by Poporacer
February 06, 2023, 10:27:09 AM

Unable to update RPi 5.5 to latest version by JonB256
February 05, 2023, 07:23:16 PM

help getting started, next step? by rayster
February 05, 2023, 04:24:09 PM

F48v4NS - Pi or No Pi? by joeyblasko
February 05, 2023, 09:15:33 AM

Huidu Controllers LED matrix by CaptainMurdoch
February 04, 2023, 10:18:47 AM

FPP6.2 universes by darylc
February 03, 2023, 08:48:57 PM

F16v4 Ports vs Universe Configuration Question by k6ccc
February 03, 2023, 09:32:48 AM

Need Expert Advise on F16v4 Ports vs Universe Configuration by Kairus
February 03, 2023, 09:32:33 AM

Powered by EzPortal
Powered by SMFPacks Menu Editor Mod