Future Direction

[DynamoBen]

If a more dedicated design were done, you could still allow expansion capabilities with optional inexpensive dual Berg style connectors. Think Lynx Express 16 where you plug in the wireless board if desired, but in this case it could be anything.

I have no issue with this, but I'm starting to discover the community isn't as interested in learning as it once was. So too much flexibility is a bad thing because you have to write code, there is a balance between functions and capabilities for most they want functions.

Please also consider having as much "on board"/in-field manageability as possible. Using a simple 3 or 4 7 segment display, you could allow for status displays (the name of the board, firmware revision, etc), configuring simple things like DMX start address, and for kicking off test modes and/or set-up modes (all on, all off, ramp all up/down/repeat, cycle through one at a time, blink all, etc.). Although it adds a little bit of cost, the extra capability and usability it adds is seriously nice and really makes the controller (I cannot get anymore) one of the best DMX DIY setups out there.

For my node project I had considered adding an LCD and switches to configure it and allow for those sorts of things and scrapped it for a webpage interface. Personally I prefer the LCD but it requires an enclosure of some sort to work well and adds some to the cost. The risk here is I design it the way I like it and no one is interested. Which is what happened when I designed the PropDimmer, its got a lot of high end features that I love but no one was really into it.

It would be nice if we could also standardize on the enclosure (like a CG-1500 which I still have quite a few of, or the CG-2000 for mounting) as that makes life really easy also.

We could/should be doing this for anything that is likely to be outdoors.

Switching to a prop means ANOTHER set of programming tools I need to get stuff for and remember how to use. Oh- on board programming capability is nice also

This is a double edged sword. If we add on-board programming via USB it means SMT parts or expensive modules. If we go the serial route it means you need a serial port, which is hard to find on PCs these days. If we provide a programming header you need to purchase a $20 programmer. So then what does one do? I'm indifferent I just want to know what people prefer.

[chilloutdocdoc]

I'm not going to bash the design of "easy to configure" but really... we should only be configuring our controllers once or twice per season. I don't see the point in spending $10-30 per board in adding a LCD, or buttons, or all of this stuff, when you can simply just reflash via ICSP or Set it up with a computer.

Maybe it's the cheapskate in me.

[DynamoBen]

What about a DMX/Renard/sACN (or whatever else) tester? I've been situations where I would rather use a handheld controller instead of booting my laptop or I just want to isolate a problem, this could fill both problems.

[chilloutdocdoc]

What about a DMX/Renard/sACN (or whatever else) tester? I've been situations where I would rather use a handheld controller instead of booting my laptop or I just want to isolate a problem, this could fill both problems.

I would SERIOUSLY get behind this.

[critic2]

Personally I need a controller that I can reconfigure since I use them one way for Halloween and another for Christmas, so that concept will live on. But I see other Prop based projects here that are being quickly adopted by people but only a handful of folks use the PropController. So I see two groups, devs and users. Devs want flexibility but users want build and play. I guess I'm wondering if we should cater to the users since there is a high learning curve between the two groups?

BTW regardless of direction all of the code a schematics will continue to be open source.



I could go as high as 128 w/o breaking a sweat.

I am currently a user, but want to be a devs. I can't read this site quick enought!! Learning something new EVERY DAY.
I love DIYC. Yea, I'm hooked...

Chuck P.

[DynamoBen]

I am currently a user, but want to be a devs.

Spin is a pretty friendly language to learn, nice to see another Propeller head in training. ;)

[dirknerkle]

Spin is a pretty friendly language to learn, nice to see another Propeller head in training. ;)

But don't you get dizzy going 'round and 'round like that??? I fall down enough as it is... that would make it even worse for me!!!

[Materdaddy]

What about a DMX/Renard/sACN (or whatever else) tester? I've been situations where I would rather use a handheld controller instead of booting my laptop or I just want to isolate a problem, this could fill both problems.

I would love this. One of my goals for the year is to design a DIYC tester (unless I can get somebody else to do it... Tom Sawyer anyone?). I don't know what all I want, but I do know of a few things:
* Send out Renard data (stand-alone). Test controllers via RS485 without the PC. Maybe simple ramps for a configurable amount of channels?
* Receive Renard Data - to see if a controller is repeating data and give some sort of diagnostics
* Test SSRs - Loop through your standard 1-4 channels of an SSR.
* Act as an SSR - This would be LEDs driven by a controller to test the SSR output from your controllers
* All of the aforementioned functions, but replace "Renard" with DMX/sACN (or whatever else).

[DynamoBen]

That's a big list, I think for this tester I'm going to limit it to data only. I will most likely model it after this.

I think everything will be through hole, but I will likely include the SMT USB parts on the board for those that don't want to buy a prop-plug. Initially I will focus on DMX and sACN support since those are easily testable for me and then widen the data type options down the road.

[Zeph]

I just want to say that as a newbie to DIY animation and these microcontrollers (but not to programming), I'm really glad to have an option which supports user programmability. I've just discovered the PropController, and do not yet know what it's capable of, but I'm interested in learning development. Everybody using Spin seems to say it's fun and powerful, so that intrigues me. (I do want to get some simple and supported controllers like Ren 24ss working for this year before going too deep into development myself - of something which might not work).

I'm speaking up in response to the question of whether some in the community are still interested in development - interest is not dead!