Re: [AVR-Chat] Re: Any general length considerations for SPIbusses?
2004-11-24 by David Jones
>>> washer@trlp.com 25/11/2004 2:32:00 am >>> I'm a newbie at playing with HW.. I've been a software guy forever. Sorry for leaving out details. I've got a couple of different situations. 1) I want to have a remote AVR with an LCD that shows system status. Nothing major, but with any of say 20 inputs( think automobile, door open, oil pressure low, ignition on, etc). The LCD needs to be updated with things change. The AVR/LCD unit will be ~10 feet from the main controller. 2) Think home alarm/automation system. Temp sensors, door sensors, smoke alarms, motion detectors, etc. These "sensors" will be up to ~100 feet away In neither case do I need much speed. I don't have any hard number here, but I'd thinking tens of bits/second is all I need. p.s. What is LIN?? - jim For option 1, RS232 will do the trick. Just implement your own simple protocol. For option 2, RS485 is one of the standard solutions for long cable runs. Once again, implement your own simple protocol. Both solutions can use the same protocol and UART within the AVR. Simple. Don't muck around with the more complex busses, there is no need to use them. Dave :)