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: 15648
Latest: zj023
New This Month: 53
New This Week: 12
New Today: 3
Stats
Total Posts: 128304
Total Topics: 15779
Most Online Today: 52
Most Online Ever: 7634
(January 21, 2020, 02:14:03 AM)
Users Online
Members: 4
Guests: 26
Total: 30

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

Trying to configure LOR CF50D Floods on FPP Pi Player with PiCap by tbone321
Today at 12:36:16 PM

raspberry PI 3 / PI 4 by mrfix1
Today at 07:13:55 AM

help getting started, next step? by K-State Fan
Today at 04:42:36 AM

Bug in newest release by tbone321
January 26, 2023, 06:14:26 PM

Cannot Connect to F48V4-NS Through Rasberry Pi by Poporacer
January 26, 2023, 03:13:43 PM

new piCaps in the works? by Bwinter
January 26, 2023, 11:25:32 AM

DIY voucher request by CaptainMurdoch
January 26, 2023, 11:14:38 AM

Which volume to grow during setup? by RickR
January 26, 2023, 09:55:17 AM

F16v3 Won't boot or power on by chiefwarrant
January 26, 2023, 06:56:34 AM

Simple single Channel DMX Output trigger by info@trans-mission.tv
January 26, 2023, 05:33:54 AM

Powered by EzPortal
Powered by SMFPacks Menu Editor Mod