Since you're likely considering this to be a DIY system, here's the results of a survey I took a couple years ago that categorized the typical kinds of support issues that arose. What was surprizing to me were the numbers of times simple cabling issues came up. And if you spend a few minutes reading through the hundreds of postings related to "controller won't work" or "can't communicate" or "how do I make a cable?" you'll likely discover that making a simple cable with only 2 or 3 connections is more difficult than many new to DIY Christmas lighting can handle. But those folks are exactly the ones who often "go for the big system."
http://www.doityourselfchristmas.com/wiki/index.php?title=Troubleshooting/Solutions
In product development, it's usually a good idea to remember who the target customer is. In this hobby, it's quite natural that users will "bite off more than they can chew." I don't know if this will influence your project or not, but I thought this information might be helpful to you. After all, not everyone is ready to step behind the wheel of a Ferrari...
I've done RS485 half duplex in many of the designs I've done over the years. With some of the DMX controllers I've designed though, I've left them as receive only. This is because I wanted an isolated DMX front end and having 2-way comms capability added too many parts.
Firmware upgrades "over the wire" are nice, but there has to be a balance between complexity, cost and actual requirements. Cost seems to be the big one, as few of the DIY designs seem to consider an isolated DMX input important.
As I see it, in a DIY arena the target audience is the person creating and designing the project. Since JHinkle and others in this thread are mostly tickling their own fancy, I wouldn't try to discourage them. I don't always follow my own advice in this area (many Tom Sawyer projects), I still think that doing something for yourself and more or less ignoring the community at large is a good way to go. Many projects will end up languishing, but one or two might strike the fancy of someone beyond the originator, and take off from there.
dirknerkle wrote:Since you're likely considering this to be a DIY system, here's the results of a survey I took a couple years ago that categorized the typical kinds of support issues that arose. What was surprizing to me were the numbers of times simple cabling issues came up. And if you spend a few minutes reading through the hundreds of postings related to "controller won't work" or "can't communicate" or "how do I make a cable?" you'll likely discover that making a simple cable with only 2 or 3 connections is more difficult than many new to DIY Christmas lighting can handle. But those folks are exactly the ones who often "go for the big system."http://www.doityourselfchristmas.com/wiki/index.php?title=Troubleshooting/Solutions
In product development, it's usually a good idea to remember who the target customer is. In this hobby, it's quite natural that users will "bite off more than they can chew." I don't know if this will influence your project or not, but I thought this information might be helpful to you. After all, not everyone is ready to step behind the wheel of a Ferrari...
This site may be a do it yourself place but I quite often do it my way. This site has a lot of followers and few that lead. I applaud anyone that explores the do it my way avenue. Creativity spawns innovation!
Anytime someone explores a new way of doing something here and is willing to share how they did it, I think is a plus to the DIY community.
One other caveat to bi-directional communications is that the system can give real-time failure analysis. Maybe a controller is starting to fail but it’s not visible via the light outputs. The controller could monitor all it inputs and outputs and either report back immediately or store errors for later queries. Cars do that. You may not know that there is a problem in modern engines because the computer will adjust for an intermittent sensor or simulate an in range one and adjust so you can at least get home.
I know that controlling Christmas lights isn’t nearly as hostile of an environment but boy when its crappy outside and my lights aren’t working; it would be nice to have a few shortcuts to getting it working. Maybe it’s a controller and you can just swap it out but maybe it’s not.
Vixen 3 will open a new world of capabilities that we didn’t know that we needed. Six years ago, who knew that we would have the capability to control thousands of channels in any color you wanted?
Originally posted by ErnieHorning
One other caveat to bi-directional communications is that the system can give real-time failure analysis. Maybe a controller is starting to fail but it’s not visible via the light outputs. The controller could monitor all it inputs and outputs and either report back immediately or store errors for later queries. Cars do that. You may not know that there is a problem in modern engines because the computer will adjust for an intermittent sensor or simulate an in range one and adjust so you can at least get home.
That's what I did for the last 10 yrs before I retired. If you have a Chrysler/Jeep - then your radio, cluster, body controller, CAN Gateway, or 4-wheel drive controller has me in it.
I know the DIY community is not ready for that level of engineering yet.
When I initially designed this controller, it was going to have integrated SSRs - 24 of them. I had the ability to measure current draw out of each each channel, monitor the controller's own power supply, and OAT (outside air temp). I could not use a 42 pin dip cpu - not enough I/O - so I had a larger pin count one that had to be surface mounted.
I have the "Hobby" version of Eagle which limits my designs to 6x4. When I went to layout, I found I had 10 lbs of stuff and only a 5 lb bag.
Immediate system redesign - the current monitoring was trashed and the SSRs were made external - I just purchased 40 SSRneons - I think that is well constructed board.
I found a RS485 to Ethernet converter - it actually supports full duplex RS485 (Neteon GW215). I can communicate with it directly by IP address and port number. I will write some custom software to interface with my controllers (for test and firmware flashing) and I will have my "output controller" in Vixen 3 - communicate directly using an IP address instead of a Window's virtual COM. That way I can form my own message frames and deliver them as a unit instead of one byte at a time.
I have now locked down my system and design. Parts have been ordered - I will go out for board prototypes next week.
Joe
