Here is some Perl code to show the differences between the DMX and PixelNet serial packets:
#
# Assemble PixelNet packet
#
if ($Protocol eq 'PIXELNET') {
$channel_data = chr(170) . $channel_data;
}
#
# Assemble DMX packet
#
if ($Protocol eq 'DMX') {
$channel_data = "\x7E\x06" . chr($length & 0xFF) . chr(($length >> 8) & 0xFF) . chr(0) . $channel_data . "\xE7";
}
Notice the DMX packet has more header information and the trailing break byte. PixelNet simply has the the leading chr(170) byte.
So, no, you can't just send a DMX stream to a PixelNet device or vice versa and have things work correctly.
rrowan - Yeah, I also noticed the 4096 byte anomaly. Reading the specs, we should be sending the start byte followed by 4096 channels of data in bytes - 4097 bytes. But the PixelNet dongle doesn't seem to like that - it wants just 4096 bytes. I mentioned this before, but no one seemed to be aware of or had experienced it. I think we are really limited to 4095 channels in a PixelNet Universe in the current dongle firmware as the 4096th byte can't be sent/received by the dongle.
Also, if you are interested in talking to the EtherDongle, catch up with me - I have both Java and C# code that generates E1.31 packets. Both have worked successfully with the EtherDongle. Check this out - a Vixen 3 E1.31 output module I wrote: You are not allowed to view links.
Register or
Login