I think the Open DMX USB widget behaves as a raw serial port so you need to generate DMX packets 'manually' by sending break (sequence of zeros longer than a character) before each message. At the moment [comport] doesn't have the capability to send breaks but I think it could be done. Since the computer has to time the breaks it can happen that they are out of spec and the DMX equipment doesn't always get the messages. The Pro handles serial comms with the computer separately from the dmx so the timing is always correct.

Martin

On Wed, Jul 1, 2015 at 2:56 PM, Peter P. <peterparker@fastmail.com> wrote:
* Martin Peach <chakekatzil@gmail.com> [2015-07-01 14:46]:
> Here's a patch that uses [comport] to talk to an entec DMXUSBPro.
Would that also work with the DMX USB (non-Pro)? Does anyone know what
the difference between these two models is? I seem to remember vaguely
that the Pro does buffer messages locally and reschedules them.