May 19, 2012, 07:46:34 PM

Author Topic: ECG hyperDMX - the spec  (Read 1708 times)

Offline j1sys

  • Community Project Designer
  • Full Time Elf
  • *****
  • Posts: 166
  • Country: us
  • There are no rules, and those are the rules.
    • View Profile
    • Joshua 1 Systems Inc.
  • State: Outside of AU/NZ
ECG hyperDMX - the spec
« on: October 06, 2010, 09:33:15 AM »
Greetings -

Just a few notes about the new hyperDMX option soon to be available on the ECG-DMXRen8 and ECG-DR4.

hyperDMX is a combination of options that will allow up to 4 universes of data to be sent down a single RS-485 DMX line. It can be used for any use by any DMX controller designer but its principle use is for high pixel count LED protocol bridges that use DMX universes to drive pixel strings.

hyperDMX adds two options to the standard DMX slave software:

  • The option of using alternate start codes (ASC) to multiplex up to 4 universes over a single line. This is allowed under the DMX standard and will play well with other controllers that only accept the default start code of zero. The trade-off is that in order to send two universes you must allow for approximately 50ms updates, to send three universes 75ms, to send four universes 100ms.

  • The option of increasing the transmission rate to a non-standard multiple of the standard 250Kbps. Depending on the distance between transmitter and receiver a simple RS-485 point-to-point connection is more than capable of working at much higher speeds and modern microcontrollers are capable of handling the faster rates. Being non-standard this option will not play well with other controllers on the same line. We feel that since its purpose is to transport multiple universes to a single controller which then drives up to 2048 channels (approx 680 pixels) that this deviation can be acceptably managed.

The approximate update rates that can be performed using variations of these options are as follows:

Warp 1*
250Kbps
Warp 2
500Kbps
Warp 3
750Kbps
Warp 4
1Mbps
1 Univ25ms13ms9ms7ms
2 Univ50ms26ms18ms14ms
3 Univ75ms39ms27ms21ms
4 Univ100ms52ms36ms28ms

*Warp 1 is the only speed that is standard friendly

We fully expect that the ECG-DR4 will be able to support any of these rates on all four slaves simultaneously. So for an ECG-DR4 you could drive four hyperDMX capable pixel controllers each with four full universes at a 28ms update rate.

Due to design limitations and total bandwidth limitations we expect that the ECG-DMXRen8 will only be able to drive an aggregate total of 16 universes also. So with 8 slaves it would only be able to do a mix that totals 16 universes. One example would be: 4 universes on Slave #1, 4 universes on Slave #2, 2 universes on Slave #3, 2 universes on Slave #4, and 1 universe on Slaves #5-8. This would allow standard DMX devices on Slave #5-8 and hyperDMX compatible devices on Slave #1-4. Any other mix that does not exceed sixteen total universes should be acceptable. We will not limit you to 16 universes we just believe that you may start experiencing overruns and dropped packets if you exceed  that number.

Of course neither the ECG nor the DMX controller will probably be able to detect the transmission speed that is set and therefore must be independently configured to operate at the desired speed. This may lead to some additional confusion during hookup and testing.

Well, enough for now, back to work on the software that makes this all work ....

-Ed

Offline Wombat

  • Full Time Elf
  • ***
  • Posts: 119
  • Country: 00
    • View Profile
Re: ECG hyperDMX - the spec
« Reply #1 on: October 06, 2010, 09:44:52 AM »
* Wombat bows to the Master Po

Offline mschell

  • Full Time Elf
  • ***
  • Posts: 146
  • Country: us
    • View Profile
    • Christmas in Applegate
Re: ECG hyperDMX - the spec
« Reply #2 on: October 06, 2010, 11:50:59 AM »
Nice stuff.  It's amazing what some smart folks come up with...

Of course, this means that I'll have to come up with lots more $ to fund the pixels and controllers, etc...but at least I already bought the DMXRen8! ;D
Mark
Kernersville, NC USA

Offline Cypress1138

  • New Elf
  • *
  • Posts: 1
    • View Profile
Re: ECG hyperDMX - the spec
« Reply #3 on: October 07, 2010, 01:59:39 AM »
Its funny but I have been thinking that with RGB pixels and their associated high (insane?) channel counts that DMX may not be the protocol to use. But then once again people vastly smarter than me are way ahead and are already working on a solution! This will be very interesting to follow!

I agree with Wombat and bow to the Master Po

Offline j1sys

  • Community Project Designer
  • Full Time Elf
  • *****
  • Posts: 166
  • Country: us
  • There are no rules, and those are the rules.
    • View Profile
    • Joshua 1 Systems Inc.
  • State: Outside of AU/NZ
Re: ECG hyperDMX - the spec
« Reply #4 on: October 07, 2010, 07:25:35 AM »
E1.31 direct to the pixel level is the great way to go but not ready (from me) right now and this will help people quadruple their capacity on TP3212 units RIGHT NOW if needed.

It will always be part of the communication/wiring arsenal and there are place's where it may be used for years to come.

There is not always one 'right' answer to fit all solutions.

Someone else, either here or on chat, mentioned DVI as  the high pixel protocol of choice for the pro world. All protocols should fit the solution, not the other way around.

-Ed

Offline j1sys

  • Community Project Designer
  • Full Time Elf
  • *****
  • Posts: 166
  • Country: us
  • There are no rules, and those are the rules.
    • View Profile
    • Joshua 1 Systems Inc.
  • State: Outside of AU/NZ
Re: ECG hyperDMX - the spec
« Reply #5 on: October 11, 2010, 11:24:26 AM »
IT'S ALIVE!!!

Just got hyperDMX transmitting 16 universes (4 per slave) out a DR4 (into the bit-bucket) at 25ms updates from Vixen.

Next to retro-fit to the DMXRen8 and test it's limits.

There is now a Warp5 for 1.5Mbps to give a little more headroom for 25ms updates with 4 full universes.

So v1.3 with hyperDMX is coming soon to an ECG near you!!!

-Ed

Offline AussiePhil

  • Administrator
  • Dedicated Elf
  • *****
  • Posts: 1047
  • Country: au
    • View Profile
  • State: Australian Capital Territory AU
Re: ECG hyperDMX - the spec
« Reply #6 on: October 11, 2010, 11:39:53 AM »
Ed

Great news
-----------
Bridge to engine room, warp factor 9.

Och, if I give it any more she'll blow, Cap'n!
------------

Phil
Be Kind - Be Nice - Join In
It's your Forum

Offline budude

  • Full Time Elf
  • ***
  • Posts: 126
  • Country: us
  • Way behind schedule - again...
    • View Profile
    • Christmas in San Jose!
Re: ECG hyperDMX - the spec
« Reply #7 on: October 11, 2010, 01:30:48 PM »
Geez - - I'm almost afraid to get on this forum anymore - I feel like anything I have now is from the Stone Age!  :)  Next year should be a lot of fun...
Brian

Offline mrpackethead

  • Unsocialable Elf
  • Full Time Elf
  • *
  • Posts: 452
  • Country: nz
    • View Profile
Re: ECG hyperDMX - the spec
« Reply #8 on: October 11, 2010, 01:32:03 PM »
warp factors.. nah thats old hat..   

Now to think up something new
Regards Andrew / 付强
www.stellascapes.com
skype: mrpackethead

Want to talk blinky?  blinkychat is here

Offline fathead45

  • Full Time Elf
  • ***
  • Posts: 133
  • Country: us
  • Fiedler Xmas
    • View Profile
Re: ECG hyperDMX - the spec
« Reply #9 on: October 20, 2010, 03:45:38 AM »
wooohoooo i love it.  awesome job guys.  so in theory i could run 24 universes off my 6 TP woot woot.  great day.  maybe my 70ftx14ft video wall might live just yet haha.

Offline RPM

  • New Elf
  • *
  • Posts: 11
    • View Profile
Re: ECG hyperDMX - the spec
« Reply #10 on: March 12, 2011, 07:23:10 AM »
Greetings -

Just a few notes about the new hyperDMX option soon to be available on the ECG-DMXRen8 and ECG-DR4.

hyperDMX is a combination of options that will allow up to 4 universes of data to be sent down a single RS-485 DMX line. It can be used for any use by any DMX controller designer but its principle use is for high pixel count LED protocol bridges that use DMX universes to drive pixel strings.

Do you have the HyperDMX protocol published somewhere so a controller designer can implement it in their designs?

Offline j1sys

  • Community Project Designer
  • Full Time Elf
  • *****
  • Posts: 166
  • Country: us
  • There are no rules, and those are the rules.
    • View Profile
    • Joshua 1 Systems Inc.
  • State: Outside of AU/NZ
Re: ECG hyperDMX - the spec
« Reply #11 on: March 17, 2011, 10:01:24 AM »
Robert -

Sorry so long getting back to you. Spec = paperwork = four letter word!!

I thought I had included it here but think I only sent it via email to Tabor for their hyperDMX implementation.

Timing - ALL timing remains the same except the option of increasing the bit rate. So when i crank up the bit rate to multiples of 250kbps I will send the DATA faster but still have the same MTBF,MAB,etc. for all other interframe timing.

Start Codes - simple non-standard (could not play well with others) start code 0 - 1st univ, 1- 2nd univ, 2 - 3rd univ, 3 - 4th univ.

The way it works in real life is that the speed and the multiple universes are functionally independent. you can actually send four universes at 250kbps you just have to insure a slower than 100ms updates rate. you can also use just one universe but crank the speed up to allow for faster updates (faster than 25ms).

As stated elsewhere since the MTBF,MAB,etc. timing is static the update rates calculations are not linear, especially for short universes.

Since the purpose of this design was to squirt a lot of data over a single point-to-point connection we decided that the deviation from the standards shouldn't cause any interoperability problems since no other simple DMX should/would be listening in.

-Ed

Offline RPM

  • New Elf
  • *
  • Posts: 11
    • View Profile
Re: ECG hyperDMX - the spec
« Reply #12 on: March 17, 2011, 12:24:53 PM »
Robert -

Sorry so long getting back to you. Spec = paperwork = four letter word!!

I thought I had included it here but think I only sent it via email to Tabor for their hyperDMX implementation.

Timing - ALL timing remains the same except the option of increasing the bit rate. So when i crank up the bit rate to multiples of 250kbps I will send the DATA faster but still have the same MTBF,MAB,etc. for all other interframe timing.

Start Codes - simple non-standard (could not play well with others) start code 0 - 1st univ, 1- 2nd univ, 2 - 3rd univ, 3 - 4th univ.

The way it works in real life is that the speed and the multiple universes are functionally independent. you can actually send four universes at 250kbps you just have to insure a slower than 100ms updates rate. you can also use just one universe but crank the speed up to allow for faster updates (faster than 25ms).

As stated elsewhere since the MTBF,MAB,etc. timing is static the update rates calculations are not linear, especially for short universes.

Since the purpose of this design was to squirt a lot of data over a single point-to-point connection we decided that the deviation from the standards shouldn't cause any interoperability problems since no other simple DMX should/would be listening in.

-Ed

Ed,

Thanks for the explanation.  I think I'll setup one of my dimmers to test out the protocol.

  Robert

Offline kool-lites

  • Full Time Elf
  • ***
  • Posts: 140
  • Country: au
    • View Profile
    • BaulkoLites
Re: ECG hyperDMX - the spec
« Reply #13 on: March 21, 2011, 09:06:10 AM »
Since the purpose of this design was to squirt a lot of data over a single point-to-point connection we decided that the deviation from the standards shouldn't cause any interoperability problems since no other simple DMX should/would be listening in.
-Ed

Do I understand correctly, normal DMX equipment can not be used on the Hyper DMX "Universe"?
The best analogy I can think of is the current DMX / Renard mix installation some ppl have.  If you use HyperDMX and plain old DMX, you will need to in effect use two separated networks.
The benefit of Hyper DMX in jamming more data down a single P2P connection.  The saving is great particularly if you have an "all" hyper DMX equipment installation.  Other than the obvious savings of several lengths of Cat5 and several DMX dongles ( ignore the type at this stage), am I missing any other savings?


Offline David_AVD

  • Community Project Designer
  • Dedicated Elf
  • *****
  • Posts: 1317
  • Country: au
  • Technology Mad Man
    • Facebook.com/http://www.facebook.com/pages/Audio-Visual-Devices/297531996950791?sk=info
    • View Profile
    • Audio Visual Devices
  • State: Queensland AU
Re: ECG hyperDMX - the spec
« Reply #14 on: March 21, 2011, 09:46:39 AM »
Correct, "Hyper DMX" is not compatible with standard DMX.
Sure, everyone's always in favour of saving Hitler's brain, but put it in the body of a great white shark... oooooh, suddenly you've gone too far!