I would like your opinion on RS485 full or half duplex - with specific regard to the DIY community here.
I fell in love with a DIY Christmas light show this year and said - I want to do this. So I'm jumping in feet first.
I've been doing embedded for 30 years and have formed a bias towards micros - much like one forms towards politics and religion. I don't care for PICs. I like Motorola/ Freescale products. So feet first - means do it my way instead of using one of the many fine controllers already on this site.
I have no expectations of a coop buy, etc. If people like how I think and what I will do different with this controller - then it will be available to the community - hardware and software. (It will include a bootloader - so anyone wanting the software and does not have the development tools to flash it themselves - it will be upgradeable using a PC via a COM port).
I currently designed the controller to use full duplex communication. I am running CAT5 as the RS485 link so there are plenty of twisted wire pairs available so half is not required because there is not a limitation of only one pair.
Also - with full duplex - I don't have to add the additional bias circuitry usually required for half.
So I ask - with the thought of others wanting to use the board - Why would you use half instead of full?
Please don't say just because everyone else in DIY uses half.
My opinion is that half is used commercially because the bus only needs a single twisted pair. Wire is expensive. Since CAT5 has 4 pairs - wire is not the issue - so why half?
I ask because if I am missing an important technical aspect here (with respect to DIY Christmas Lighting) - I would rethink my direction.
If someone in the community wanted to use the board and already had existing buses running half - they could just run another one using full. Another bus would probably be required because I'm not currently designing it to use a standard protocol, as in DMX, - so the protocol will be different from other controllers anyway.
So - if you have a technical reason why a new controller board should use half duplex RS485 - please share.
Thanks in advance for your comments.
Joe
Renard uses one-way communications, neither half- nor full-duplex. There isn't any need for communications from the controllers back to the host(PC).
JHinkle wrote:I would like your opinion on RS485 full or half duplex - with specific regard to the DIY community here.So I ask - with the thought of others wanting to use the board - Why would you use half instead of full?
Please don't say just because everyone else in DIY uses half.
My opinion is that half is used commercially because the bus only needs a single twisted pair. Wire is expensive. Since CAT5 has 4 pairs - wire is not the issue - so why half?
I ask because if I am missing an important technical aspect here (with respect to DIY Christmas Lighting) - I would rethink my direction.
If someone in the community wanted to use the board and already had existing buses running half - they could just run another one using full. Another bus would probably be required because I'm not currently designing it to use a standard protocol, as in DMX, - so the protocol will be different from other controllers anyway.
So - if you have a technical reason why a new controller board should use half duplex RS485 - please share.
Thanks in advance for your comments.
Joe
Can think of only a few things here.. . These come from an old geezer who's been in the forefront of many product launches...
If you're designing your own communications protocol, and your own wiring system, it would likely antiquate all or at least almost all of the gear that DIY'ers currently have. This is fine if you're starting out fresh and for yourself, but to a DIY'er who already has a few thousand dollars invested, it doesn't sound so appealing to switch over to something that has no track record.
Secondly, there is plenty of support and problem solving for existing gear. You would have almost none for anyone who took an interest in your equipment. I'm not saying that's necessarily bad, but not having any sort of safety net isn't very welcoming to a DIY'er, and from your standpoint, being the only support avenue, I hope you have a "real job" that will afford you the time to support your product. Take a look at all the "problem threads" published in the last 6-weeks and try to imagine that YOU are the only one providing support.
IMO, an asynchronous protocol makes sense from a lighting perspective because it is more time-sensitive. Redundancy/retries in a duplex protocol are likely something that will increase the accuracy of lighting signals but probably at the expense of a delay, which may make the lighting effect "late" in terms of accurate timing with a musical score. The Renard protocol, for example, was designed to be outbound-only with data integrity relying on good wiring/good physical connections. Additionally, the cat5 wires that interconnect systems now often carry more than just control signal; many users have "DIY-ed" their own cables by adding low-current AC or DC power, ZC signal support, or possibly sensing mechanisms, so in some cases, asynchronous capability is all that's left.
All that said, I think it's fun to be on the leading-edge and to follow one's heart. Without dreamers and tinkerers, we'd still be back using the abacus.
One of my main design points requires that I have a bus with two way communication - firmware upgrades.
I am not going to be pulling cpus out of boards and reprogramming them when I have a firmware update.
I will have firmware upgradeable via the bus. That requires two way handshaking as blocks of data are passed and flashed into the controller.
If I have 10 controller deployed in a field setup - I want two way communication with them ... I want ..
#1. Query - who is alive?
#2. Reflash firmware. This is the big reason. Cost no more in hardware than what is normally on a controller.
#3. Perform debug functions ... control controller's behavior outside of Vixen - debug lighting setup and fuctionality, etc
This is nothing new to me - I expect it. Sounds like its new to this community.
Think automotive. A vehicle has many embedded modules in them. Most are designed so that their firmware is reflashable over the CAN bus. CAN is just a version of RS485 with a custom SCI.
The design would not antiquate what people have. I use DIY SSRs. As I stated earlier - yes someone would not hang this controller on an existing bus - but from what I have read on the forum, most are running multiple buses anyway.
So that is way I was asking about full vs half.
Joe
As I see it, the question of half-duplex versus full-duplex only has meaning when there are just two devices communicating over the line. Is this what you're thinking about, or are you thinking a bussed (party-line) connection scheme, where morre than two devices are connected to the same line? In that case, I'm not certain what you're asking...
