Problem with the Prop Blade and DMX
I am using the ENTTEC DMX Pro with the Prop Blade and the "Prop Blade DMX-512 Demo Ver 01.0" gotton from http://brilldea.com/product_PropBlade.html
The only changes made to the program it the G1 side was turned on and added debug into the main loop.
The main problem i see with the code it that the DMX.level(0) returns a 2-246
this check that the data in the buffer is "dimmer" data and not RDM or other (part of the protocol)
The only changes made to the program it the G1 side was turned on and added debug into the main loop.
The main problem i see with the code it that the DMX.level(0) returns a 2-246
this check that the data in the buffer is "dimmer" data and not RDM or other (part of the protocol)
full code is included.CODE said...
repeat
'BS2.Debug_Str(string("Spin-Up World!",13))
'Check the address, if it is good, then update
if DMXAddress <> 0
BS2.Debug_Str(string("c="))
BS2.Debug_DEC(DMX.level(0))
BS2.Debug_Str(string(","))
repeat t0 from 0 to (_OffScreenArray - 1)
BS2.Debug_DEC(t0)
BS2.Debug_Str(string("="))
BS2.Debug_DEC(DMX.level(t0))
BS2.Debug_Str(string(","))
BS2.Debug_Str(string(13))
'Check that the data in the buffer is "dimmer" data and not RDM or other
'if DMX.level(1) == 0
'Gather the data from DMX buffer and place it in the LED Painter buffer
repeat t0 from 0 to (_OffScreenArray - 1)
chvalues[noparse][[/noparse]t0] := DMX.level(DMXAddress + t0)
'BS2.Debug_Str(string("DMX ACTIVATED",13))
'Update the LED Painter
WindowUpdate
DMX received said...
c=246,1=4,2=8,3=16,4=32,5=64,6=128,7=0,8=0,9=0,10=0,11=0,12=0,13=0,14=0,15=0,16=0,17=0,18=0,19=0,20=0,21=0,22=0,23=0,24=0,25=0,2
6=0,27=0,28=0,29=0,30=0,31=0,32=0,33=0,34=0,35=0,36=0,37=0,38=0,39=0,40=0,41=0,42=0,43=0,44=0,45=0,46=0,47=0,48=0,
Comments
A small note about the Propeller DMX-512A driver, which I think you might understand. The driver that I wrote gathers all the data from a DMX frame. This include the start byte as well as the 512 slots of data. In other words the driver can receive data that isn't dimmer data, so that is why there is a qualifier in the demo code you are looking at to make sure the start byte is 0 for dimmer data. A month or two ago I was looking at the RDM spec and realize that there is an adjustment in the DMX timing to make it better for RDM reception. The DMX-512A driver, as of yet, hasn't been adjusted for this. I will work on this though at some point in the future.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Timothy D. Swieter, E.I.
www.brilldea.com - Prop Blade, LED Painter, RGB LEDs, uOLED-IOC, eProto for SunSPOT, BitScope
www.tdswieter.com