Where to go?

[star882]

Originally Posted by anatech

Hi star882,
Just how far apart are your components?

Okay, then use RS-232. If you can live with lower data rates, use a current loop. The fact that SPI and I2C is normally used inside a chassis doesn't preclude it's use outside. As for RS-485, that's what I'm running my test gear on. I'm more than just a little familiar with it. I would not run it very far though.

Best, Chris

Maybe use something like CAN bus. RS-232 is only two ended so it will not be practical for any large setup (too many ports needed). RS-485 (in its most basic form) is essentially RS-232 but on a half duplex differential pair.

SPI would need more wires than other buses so it is not as practical. I2C could be used (and HDMI and related connections use it for control), but how would you ensure that powered off nodes do not load down the network? And it is nowhere as suitable for use outside equipment as buses that are designed for it. (CAN bus is originally designed for automotive use and is very fault tolerant. It is also used in certain digital HVAC controls.)

I suppose you could use Ethernet for both control and data on digital sources. But it is very complex to implement.

[MJL21193]

Originally Posted by anatech

Hi star882,
Just how far apart are your components?

Originally Posted by Geek

(Bad Geek)

Cheers!

Originally Posted by SY

I had the same thought, but I didn't want to make Chris blush.

Here now fellas, don't be hittin' on my girl now...

[SY]

Nope, just tweakin' Chris. Star does not wear orange.

[Saturnus]

Originally Posted by Glowbug

Whatever kind they can't see, and doesn't impact their shoe/clothing/gifts budget.

Correct. And therefore the answer is neither of the choices since only a class-D design will do that (not to mention sound better than any of the other antiquated design technologies).

[rok-n-rol]

I'm confused, Iggy Pop had favorable results modulating a large lighted tube on top of his speaker cab yet his large amp was in discreet secondary position. Should I be thinking large discretes or maybe it is all about the speakers motorvating vibrating mass.

[Juergen Knoop]

thank you people!
I have made up my mind on topolgy and look of my next amp.
Hm, how do I close this poll? Can't see any controls?
Regards

[SY]

Originally Posted by Juergen Knoop

Can't see any controls?

That's true of most women.

[Andrea:]

I bet girls love this poll

[Juergen Knoop]

ok, then don't close the poll!

[anatech]

Hi Stuart,

I had the same thought, but I didn't want to make Chris blush.

Me blush?


Hi star882,

Maybe use something like CAN bus.

Good choice.

SPI would need more wires than other buses so it is not as practical.

Not so fast! The number of wires isn't really a problem unless it gets out of hand. Use a connector that computers use, then just use the cables already designed and terminated. You could use any standard signaling protocol. RJ-45s or USB connectons would also work, but they might not be as robust. However, they are set up for differential signals. Another good choice with mechanical trade-offs that probably aren't that serious. It's not like this hardware is difficult to source.

All SPI, CAN or I2C signaling is already done for you if using micro-controllers. The PIC series micro-controllers are popular in home audio, coding is already done, so all you have to do is hand off your data to the port designated for I/O. Many of these protocols will handle serial memory IC's on the bus in case you need to expand. Then there are the micro-controllers themselves that include good sized memory. It should be easy to set the other components so that the main unit will auto recognize the device and also do some automatic switching for you. One power button for the system now, no matter how finely split up your system is.

How about using RFID? No wires for control purposes. All the subsections already exist, you just need to assemble the blocks and adjust your programming to fine tune. Even Ethernet has application specific devices that you can implement by reading app notes. The one big problem with Ethernet is that the bandwidth is much higher than you really need. How much latency is acceptable in your control loop? 100 ~ 200 mS?

You can prevent a single device failure from taking down your machine network by using transformer coupling on the line. Use high frequencies. The other option would be to simply use star wiring, the master being your control amplifier (preamp in today's lingo).

There are so many choices here that will all work. I'd lean towards the CAN bus, or even SPI. Almost any will work well. The differential signaling would be the most tolerant of noise. Anything designed for use in a car would have zero problem running between system chassis' either.

-Chris