News:

LATEST RELEASE:  FPP 6.3 - Download from here - https://github.com/FalconChristmas/fpp/releases/tag/6.3

+-+-

+-User

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

+-Site Stats

Members
Total Members: 15649
Latest: zj023
New This Month: 53
New This Week: 0
New Today: 0
Stats
Total Posts: 128335
Total Topics: 15780
Most Online Today: 58
Most Online Ever: 7634
(January 21, 2020, 02:14:03 AM)
Users Online
Members: 4
Guests: 43
Total: 47

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

help getting started, next step? by Poporacer
January 28, 2023, 05:10:18 PM

Trying to configure LOR CF50D Floods on FPP Pi Player with PiCap by half.fast
January 28, 2023, 03:19:37 PM

wifi issues on BBB running fpp v6.3 by k6ccc
January 28, 2023, 02:04:23 PM

BBB / FPP sending data to ESP32 WLED by srwmemphis
January 28, 2023, 04:39:02 AM

raspberry PI 3 / PI 4 by mrfix1
January 27, 2023, 07:13:55 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

Powered by EzPortal
Powered by SMFPacks Menu Editor Mod