Looking for DMX512 schematics

[DynamoBen]

The forum has a few examples; one posted by me. I too am using the OpenDMX device for transmitting. Keep in mind that a "real" DMX transmitter transmits much quicker than the OpenDMX device (44Hz). I found that my code worked well when attached to the OpenDMX but didn’t work reliably on a standard lighting console. Have fun!

[RussMartin]

Holy smoke!

I assume you mean that your receiver didn't work on a standard console? How reliable/unreliable was it--total fiasco or just partial?

My ENTTEC (running under LightFactory, not the freeware stuff) runs the few DMX512 devices I've tried.

How did you arrive at the 44Hz (!) figure? Scope, specs, what? If it's truly that bad, I'm going to send the package back.

Can you give me a link to your code and/or schematic?

Thanks!

[DynamoBen]

I assume you mean that your receiver didn't work on a standard console? How reliable/unreliable was it--total fiasco or just partial?

My ENTTEC (running under LightFactory, not the freeware stuff) runs the few DMX512 devices I've tried.

My receiver worked fine at the slower speed of the ENTTEC (25-30Hz) but didn't run so well at full speed on a console (44Hz). I am trying to narrow down the bottle neck. The ENTTEC device runs DMX devices just fine, it’s an inexpensive way to produce DMX on a PC which is why I'm using it. That being said I still do final testing on a commercial lighting console.

How did you arrive at the 44Hz (!) figure? Scope, specs, what?

The DMX spec is where I get this number. With all the testing I've done the fastest the ENTTEC can transmit reliably is about 33Hz. Beyond that you start to see periodic errors. Visually you would never notice these errors I used a DMX tester to determine the highest refresh rate the ENTTEC could handle.

If it's truly that bad, I'm going to send the package back.

Not sure what you mean here.

Can you give me a link to your code and/or schematic?

The best resource is the search at the top of the page. There are a number of posts on this topic. In the search field type DMX* and you will get several hits. Beyond that learn and understand the protocol. Once you do all that it’s fairly easy to create the code.

[RussMartin]

Since posting my reply, I had the opportunity to talk with the US sales rep.

Apparently, with the OpenDMX, the computer is having to do all the timing chores in software. How close the result is to the "standard" 44 frames per second depends on how much other stuff the computer is trying to do at the same time. When too many demands are made on the computer, he said it starts "dropping" packets.

He also suggested that the USB DMX Pro is a way to eliminate the problem, for $95 US over the cost of the OpenDMX.

http://www.enttec.com/index.php?main...name=dmxusbpro

Thanks for helping me out with this!

[bcd]

Russ,

44 times a second is not a bad refresh rate. The DMX spec allows upto a 1Hz refresh rate, although the fades look a bit 'jumpy'. I own a Martin Lightjockey system and it has the options for 44Hz, 22Hz and 11Hz transmission.

44Hz is fine for most moving rigs. Personally I have code that will transmit DMX from a PIC at 80Hz, but that runs a tight loop with only 24 channel frame, but have found that a quick refresh can sometimes freak out some of the cheaper Chinese style scanners.

The Enttec stuff is great, but I would recommend the USBPro interface as it is also isolated and has some more funky software options.

From the Enttec site on the USB Pro: http://enttec.com/index.php?main_men...name=dmxusbpro
<snip>
# Refresh Rate configurable from 1 to 40Hz with a full 512 channel frame
# Break configurable from 96uS to 1.3mS
# MaB configurable from 10.6uS to 1.3mS
</snip>

Bill.

[grich]

sorry my mistake