A DMX controller for multiple RGB pixel strings

[DynamoBen]

The nice thing about the projects from jstjohnz and DynamoBen is you get the source code and schematics. Armed with that information, you can make the modifications needed to swap the ethernet interface for RS485, remove code for features you don't require, and add code for ones you do. That's the great thing about open source.

Exactly, if you don't like they way it was done or you need to do something different remix it to your hearts content. All we ask if that you share the results with the community like we do.

In fact, you might be able to get a head start on the RS485 interface. IIRC, jstjohnz and DynamoBen have mentioned DMX to/from E1.31 gateway functionality. It sounds like you're quite interested in the pixel controller, but need the RS485 interface. I obviously can't speak for them, but perhaps they'd be willing to share information about that as well if asked nicely.

The PropController has the ability to add an RS485 out. At present I have DMX and Renard code to run "legacy" items. DMX in will work too its just a matter of code, in fact I think jstjohnz has some code for that already.

[ptone]

There's nothing wrong with having plenty of options.

100% agree, and I've been following your project with more than a little admiration. I'm going to get some SmartStrings to play with as I think they (for what is available now) strike a decent compromise between a number of factors, and the volume pricing should be pretty nice. BTW PixelNet is actually 4096 channels at 30hz, and using all pairs of a cat5 will be 16K channels per cable. The reserved value of 170 isn't an issue, because this is purely a pixel protocol, and isn't meant to be a general purpose standard for other use, but sit at the pixel end of E1.31 network in the end.

Is there anyone that doesn't think that RGB pixels will be *the* hot item in 2011???

-jim-

Heck no - and I'm working on my own open source contribution for higher level software control. Being Mac based and only E1.31 (no dongle) so far makes already for some swimming upstream work on my part, which is why I'm all for any project using E1.31.

Keep on keeping on.

-P

[Tabor]

I have been watching this thread with interest.

Well done Jim with what looks like a nice controller.

For those who don't know me, I am responsible for all the software in and around the TP3244.

I didn't really want to jump in to this thread as it is about Jims controller, but it seems it has slightly morphed into a discussion about protocols / features etc.

For a little clarification on what HyperDMX is.
You are all pretty much correct that it was a way for us to exploit the high speed UART and high processing power of the PIC32.
Its just a way to send 4 universes of data over one 485 line by using a alternate start code and a higher transmit speed.
The TP3244 uses this fully and is able to out 4 full universes of data to the pixels from the single board.
So the Ethercongateway is capable of 16U from is 4 ports.

I agree with Jim and Ptone I would only see this as an intermediate solution.

So back to normal programming.

By the way Jim, I am jealous of the 8 indepedant cores.

[DynamoBen]

By the way Jim, I am jealous of the 8 indepedant cores.

Don't be jealous join the fun, come to the dark side, be a prophead. ;) I have PropController dev boards if you want to join in.

[jstjohnz]

I have been watching this thread with interest.

Well done Jim with what looks like a nice controller.

For those who don't know me, I am responsible for all the software in and around the TP3244.

I didn't really want to jump in to this thread as it is about Jims controller, but it seems it has slightly morphed into a discussion about protocols / features etc.

For a little clarification on what HyperDMX is.
You are all pretty much correct that it was a way for us to exploit the high speed UART and high processing power of the PIC32.
Its just a way to send 4 universes of data over one 485 line by using a alternate start code and a higher transmit speed.
The TP3244 uses this fully and is able to out 4 full universes of data to the pixels from the single board.
So the Ethercongateway is capable of 16U from is 4 ports.

I agree with Jim and Ptone I would only see this as an intermediate solution.

So back to normal programming.

By the way Jim, I am jealous of the 8 indepedant cores.

I tell you, it does come in handy. My first project was a pixel controller with a single wired DMX input. It didn't take me long to realize that I needed more slots, so I re-did the board to have up to 4 dmx inputs, 2 per RJ-45. On the software side, it was trivial because all I had to do was start 3 more cogs running the DMX receive object.

I don't have a hardware SPI port though, and those 1804s were giving me some fits due to the 10us break timing. With all of the crunching that I am doing between words, I need about 30us to get ready to send the next words (I'm driving 4 strings per cog). Anyway, it's done and so far I'm pleased. Feel free to comment here any time, about anything pixel-controller related. I got a lot of my ideas from looking at the TP3244.

-jim-

[jstjohnz]

Yet another status update. To say this has become an obsession is an understatement. The re-write of the assembly language side is done. I've added support for the 1804 pixels, in addition to the 2801, 6803, and GE. The reverse function is tested and working, the null pixels function is tested and working.

Now it's possible to span multiple DMX universe with a single string or single group of strings, previously this wasn't allowed. Almost all of the web page commands are working, a couple need a bit of polishing (just numeric values right now instead of alpha). There are only 4 ethernet sockets on the wiznet ethernet adapter, so it's not possible to run 4 e1.31 universes and the web server at the same time. I think I have a pretty workable solution though. You can set the web server mode so that it 1) only comes up when forced at re-boot with the program button, 2) comes up automatically for 2 minutes after every reboot (can then be extended with a web command), 3) comes up automatically any time no packets are received on the 4th E1.31 universe for 60 seconds, or you can select both 2 and 3.

You can shut down the web server with a command, or wait for it to timeout, and when it goes down the socket automatically reconfigures to start receiving DMX packets.

The on-board pushbutton can also be used at boot time to force a static network IP, or force the use of DHCP, over-riding the stored parameter.

There are 8 memory pages to hold full sets of configuration data. Configuration changes can be made 'on the fly' and they take effect as soon as confoguration page 0 is saved.



Here's the present list of commands for the web page:
Note that C refers to a cluster number, 1-4. The board can control up to 4 clusters of strings, with up to 4 strings in a cluster. The significance of a cluster is that all strings in a given cluster must be identical in many ways (controller chip type, length in pixels, grouping, etc). Also all strings in a cluster are assigned consecutive DMX addresses, you specifiy the starting DMX channel for the 1st string, the rest follow in order.

Only the 1st 2 letters of command words need to be typed. Numeric parameters must be separated by 1 or more non-digit characters.

BOOT 999 reboots the board
CHIP c n Sets the string controller chip type for string cluster c to type n. Right now this is numeric, later I will enhance this to recognize alpha chip names.
DHCP n Sets default network mode to DHCP or STATIC
DMX c u-sss Sets the DMX start address for string cluster c to universe U slot SSS. The reference to universe here isn't an actual universe number, rather it's a socket number from 1-4. Those sockets are in turn mapped to actual DMX universes. That's probably confusing...
DNS a.b.c.d defines the static DNS server IP address
GATEWAY a.b.c.d sets the static gateway address
GROUP c n Sets the pixels in cluster C to light up in groups of n instead of individually to reduce channel count. Group can be 1-999.
IP a.b.c.d Sets the static IP address
LOAD n load configuration page n (0-7) from eeprom. Page 0 loads automatically at bootup.
NO n No Data mode, if non-0, outputs go dark after nn seconds of no received packets. If 0, lights stay lit according to the last dmx packets received.
NULLS c a-b-c-d defines the number of null pixels on each of the strings in cluster c. Null pixels are extra pixels at the beginning of the string that are never lit, but can be used as repeaters to extend the length of cable between the controller and string. Up to 15 nulls per string, each string can be different.
PIXELS c n Defines the strings in cluster c to be n pixels long. # pixels determines the number of dmx channels needed. If group count is 1, pixels = string length. For grouping >1, string length = group count * # of pixels.
QUIT (n) shut down the web server in n seconds
REVERSED c n indicates which strings in cluster C are reversed. right now this is a numeric entry, will be made alpha =y/n. A reversed string is one that is driven from the 'far' end, in other words the last pixel lights up first. Set string by string.
RGB c n defines the actual order of the RGB color elements in the strings of cluster c. This way the controlling software can always assume R-> G-> B, even if those crazy chinese wire them up GBR.
SAVE n save currently-displayed configuration data to page n (0-7). Page 0 always loads at startup.
STRINGS c n defines the number of active strings connected to cluster c from 0 to 4.
SUBNET n (or) a.b.c.d defines the static subnet mask, may be entered as a dotted quad or # of bits.
UNIVERSE s n assigns a DMX universe number from 1-63999 to socket n (1-4)
WEB n defines what actions cause the web server to come up
ZIGZAG - not implemented yet. My head is still buzzing from trying to figure out which dmx addresses go to which pixel with the RGB, reverse, and nulls options.
I will post an updated doc file with some screen shots of the web pages tomorrow.

-jim-

[budude]

I think you've become the 9th COG in your prop man! Nice work! I'll have to get my bench cleaned up to start playing!

[jstjohnz]

I think you've become the 9th COG in your prop man! Nice work! I'll have to get my bench cleaned up to start playing!

Thanks, my wife will never understand that this is fun!

[griffixdc]

Thanks, my wife will never understand that this is fun!

i think it will be awhile before i start understanding this , i agree though my wife doesn't understand

[michaelc]

Good stuff. Great work! Now when will there be a PCB group buy and Mouser BOM? :D