I am working on a much better DMX RX to WS controller, there were flaws in this design, which now I understand them I will be improving, most of the code is written, about 95% in AVR assembler
This will shortly be an "ATTiny85 to WS2801/11/12 NRZ & SPI converter", using the full 512 bytes (170 Pixels) and should be fully compliant with DMX512 (but not RDM)
with this project, you are able to send DMX and change the led lights?
I would like to control these leds via an existing DMX controller. red green and blue faders.
Where in the code does it tell the LEDs what color to be?
j_dunavin:
with this project, you are able to send DMX and change the led lights?
Yes, that is the idea
I would like to control these leds via an existing DMX controller. red green and blue faders.
Where in the code does it tell the LEDs what color to be?
if you are using WS2812 leds then following would occur:
DMX chan 1 = Pixel 1 Green
DMX chan 2 = Pixel 1 Red
DMX chan 3 = Pixel 1 Blue
DMX chan 4 = Pixel 2 Green
DMX chan 5 = Pixel 2 Red
DMX chan 6 = Pixel 2 Blue
etc....
This project really needs a bit more thought and improvement
The ones I made work fine, but some controllers may cause this to go screwy.. on reflection it really needs an overhaul, perhaps all written in asm
The ATTiny13A has only a very small amount of RAM, 60 bytes from memory, therefore I only used 12 channels (4 RGB Pixels) to allow me left over bytes to run my program, it is very tight !!
Current Situation:
I have a PC running an application RCS 64 (rcs64.com) which controls a UNO for the lighting of individual LEDs'. The developers of this application are not prepared to open their source as they want to control the installation of their application from a single exe (understandable as they have a lot of development stuff going on that they are trying to support).
Approach:
My current thought was to implement an UNO driven by RCS64 and for it to connect to a DUE with Tinkerkit DMX Shield on, which would sniff the PWM output and then translate to DMX signals to the PAR CANS.
Status:
Cant get DUE to work with DMX Shield. So thinking of getting another UNO to do the DMX job.
But having seen your work I wonder if you have some other suggestions on how to achieve the objective? Grateful for any thoughts...
The Max485 is a single chip solution to convert the serial data into differential data required for DMX.
I make these little convertor boards for next to nothing as you can buy MAX485 very cheaply, and you only need 0v/5v supply and the serial connection to TX from the Arduino
In my logic the 5 DMX cans, hooked together in a serial fashion with XLR (3 pin), should each be addressed with their own first channel... i.e. 1st can (master) is channel 1 - red, can 2 - Channel 16 - red, Can 3 - Channel 24 etc
When using the DMX Shield I can only get action on the first can and first channel. My send strings from "Serial Monitor" have no effect on the subsequent cans....
In my logic the 5 DMX cans, hooked together in a serial fashion with XLR (3 pin), should each be addressed with their own first channel... i.e. 1st can (master) is channel 1 - red, can 2 - Channel 16 - red, Can 3 - Channel 24 etc
When using the DMX Shield I can only get action on the first can and first channel. My send strings from "Serial Monitor" have no effect on the subsequent cans....
Any suggestions?
Cheers
Paul
Hi Paul
You are right about the addressing, but im not sure why you are getting that results
Personally I would try the information at the following link, it works perfectly and alot of people use it
If your code is too big, I suggest trying a newer version of avr-gcc. I found that newer versions generate significantly smaller code. The version included with winavr if you are using that is quite old
I do not have any programming experience at all, I found this project very compact and functional for installing something inside the DMX controller for the signal monitor.
Help me please .
The chip might have to be changed to a version with more memory - but due to the simplicity of the circuit (and size of components), it can probably be put on a really small PCB...