E1.31 Protocol Disc...
 
Notifications
Clear all

E1.31 Protocol Discussions

63 Posts
18 Users
0 Reactions
37.2 K Views
Posts: 136
Topic starter
(@j1sys)
Estimable Member
Joined: 17 years ago
[#11434]

Greetings -

Subject to DynamoBen's approval I thought I'd open a new thread in the DMX area for GENERAL discussion on the E1.31 Protocol.

I know Ben has been preaching for years that ArtNet, ACN, DMX over Ethernet is the future of DIYC. I happen to agree with him and for that reason took the direction I chose on all of my hardware/software designs. I will try not to mention my stuff too often in this thread. The idea is to continue discussions on things like "How many full universes per second can we push through a 100BaseT connection?" "What is the latency of given transports?" "What is the TTL for in multicast?"

There is a full specification available from ESTA for $40 that I'm sure that Ben has mentioned elsewhere. Since I paid the $40 I am constrained by license agreement from sharing the PDF and also don't want to be part of any other 'Draft' release discussions.

However I believe I can release derivative works and make direct quotes from the document when it is necessary to define the 'specified' interaction of E1.31.

To start it off I've attached the source code of the C# class that I use in my plugins to generate E1.31 packets. They are available elsewhere but may be the starting point for people to understand the 3 layers to the packet and it's format.

This discussion and the discussion of the Vixen plugin belong in this area as they are open source public discussions of industry standards. I will also include a thread describing the work on the LightShowPro plugin which I am working on with David. It may be for a proprietary system but IMHO belongs under the umbrella of DMX discussion.

Also, please don't ignore these discussion because you are a Renard or LOR user. Using E1.31 as a transport mechanism to a gateway device (see I didn't name my product) for ultimate delivery to a Renard or LOR signal chain is part of the beauty of E1.31

So please let the questions and answers begin.

-Ed

to make the .cs file upload I had change it to a .txt file. we might ask macrosill to add .cs, .h, .c files to the allowed list or we will always need to zip them.


62 Replies
Posts: 2171
(@mschell)
Noble Member
Joined: 18 years ago

Ed,
Glad to see this topic raised and discussed. I'm believing that as things go forward, with larger and larger number of channels, etc., we will need to start utilizing better transport protocols to get data to the controllers, etc.

So better to start talking about it now, before it goes mainstream.

I'm excited that we're also talking with developers of different programs, so this becomes more universal.


Reply
Posts: 2630
(@dynamoben)
Famed Member
Joined: 19 years ago

Just so everyone is aware, I'm currently making "building blocks" based around the propeller microprocessor. Not surprisingly one of them has a DMX input but other has Ethernet. I haven't done any code for E1.31 but I hope to in the future. This building block should allow ppl to not only directly drive things like dimmers, leds, and motors but also could be used to build a node.

Hardware is being peer reviewed and then I need to send them to the board house to make protos.

http://doityourselfchristmas.com/forums/showthread.php?t=11109


Reply
Posts: 175
(@aususer)
Estimable Member
Joined: 17 years ago

Its a fascinating discussion.. ethernet controlled lights..
I'll thow in ideas including 802.2q into the fray (I suspect that vlan'ing might have a direct impact on all your calculation of universes too);
and hardware items like PoE (802.3af) - addressing hardware/power ideas too.

I am not a programmer of any sort - I have command/compile level experiance with linux - my "normal" job is NetAdmin and have packet-level understanding of IP networks.

I can't help but see that there is a very logical future for E1.31. (what with 802.3 being so "easy" for joe-blow to get their hands on... and well understood)

I'd love to see the "sourceforge"-style coding effort to turn a linux box into an E1.31 node and make it into (say) a Native Reynard controller (cheap); DMX controller (more expensive); or XYZ protocol. All achivevable at very low costs.
I know that more "professsional" results are achived by the great work of J1SYS etal. but maybe we can start leaveraging of those programmers who cut code for a living?!

In case anyone cares... "Wireshark" now has ACN/E1.31 decoding streams in it - maybe it will help decoding what is being sent out etc...

I look in interest to see if there is anything I can do to progress this subject!


Reply
Posts: 2630
(@dynamoben)
Famed Member
Joined: 19 years ago
aususer wrote:
I'd love to see the "sourceforge"-style coding effort to turn a linux box into an E1.31 node and make it into (say) a Native Reynard controller (cheap); DMX controller (more expensive); or XYZ protocol. All achivevable at very low costs.

Check these out:
http://opendmx.net/index.php/OLA

http://openacn.engarts.com/


Reply
Page 1 / 13
Share: