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: 15487
Latest: cwr89
New This Month: 109
New This Week: 23
New Today: 3
Stats
Total Posts: 126974
Total Topics: 15575
Most Online Today: 82
Most Online Ever: 7634
(January 21, 2020, 02:14:03 AM)
Users Online
Members: 12
Guests: 71
Total: 83

Completely Noob question

Started by lwillisjr, April 01, 2016, 07:09:21 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

lwillisjr

It seems to me I see a lot of confusing (and incorrect?) references to E1.31. So for my own piece of mind can anyone confirm the following?

E1.31 I believe is actually DMX information layered on top of a TCP/IP protocol. Meaning a PC (or network device) with an IP address is sending DMX information to another device on the TCP/IP network with its own IP address.

An E.1.31 device receiving this information would strip off the DMX information and send this to an output(s) as a DMX universe information. I have seen where these outputs can be 3 wire XLR or can be RJ-45 using CAT5. I believe the electrical specification for using CAT5/DMX is RS-485.


This is where I think the confusion comes in because I have seen RS-485 used interchangeably with E1.31, or these RJ-45/CAT5 DMX universe outputs referred to as E1.31. But at this point the DMX information has already been pulled off the TCP/IP layer.

Do I understand this correctly?

David Pitts

Quote from: lwillisjr on April 01, 2016, 07:09:21 PM

E1.31 I believe is actually DMX information layered on top of a TCP/IP protocol. Meaning a PC (or network device) with an IP address is sending DMX information to another device on the TCP/IP network with its own IP address.

An E.1.31 device receiving this information would strip off the DMX information and send this to an output(s) as a DMX universe information. I have seen where these outputs can be 3 wire XLR or can be RJ-45 using CAT5. I believe the electrical specification for using CAT5/DMX is RS-485.

This is all correct. 

E131 controllers receive data via UDP protocol which is encapsulated in an IP packet. Some controllers (Falcon F16V2 among others) receive these data packets and then can then send the data downstream to DMX devices with RS-485 protocol. The connectors used to send RS-485 is typically RJ-45 connectors which leads to confusion since that is what the incoming E131 stream uses also.
PixelController, LLC
PixelController.com

lwillisjr

Thanks David. That makes complete sense to me.

Support FPP

+- Recent Topics

Brightness plugin doesn't have fade option anymore by Zcarpenter
Today at 07:30:52 AM

RPI PICO AND WS2812B by tjkaminski
Today at 07:22:27 AM

FPP connect by darylc
Today at 06:49:10 AM

Very unexpected error message by darylc
Today at 02:54:04 AM

I'm Stumped by saleencb
November 29, 2022, 11:58:52 PM

Raspberry PI 4 won't connect to WIFI by Poporacer
November 29, 2022, 10:45:10 PM

Make FPP turn off ? by Poporacer
November 29, 2022, 10:36:13 PM

FPP not releasing control to WLED when idle by Poporacer
November 29, 2022, 10:35:09 PM

Christmas 2022 Lights by ShadowLight8
November 29, 2022, 05:54:00 PM

FPP and projector by morrydavis
November 29, 2022, 05:42:57 PM

Powered by EzPortal
Powered by SMFPacks Menu Editor Mod