Perhaps the conceptually simplest approach to disconnect the TX line from the modem is with a phototransistor optoisolator:
+-------------+
| |
DCD----R1-+-|-+ |/---|----TX of server
D | LED >> | |
GND-------+-|-+ |\---|--+-RX of modem (often confusingly labeled "TX")
| | |
+-------------+ +--R2--pulled LO (idle)
There's a huge number of such devices available that would be more than adequate.
A brief inspection of the selection charts at my favorite suppliers
seems to indicate that the Isocom H11AA4X, Isocom TLP521-4, Avago 4N35-000E, Lite-On LTV-816, etc.
all seem adequate.
There are many devices that may sound like what you want, but they won't work for your application:
- optotriac or optoSCR won't work for you: these are designed to work with AC circuits, turning on when commanded to and then turning off at a later AC zero-crossing at the output. Many people try to use them in DC circuits, where they turn on just fine, but it is difficult to get them to turn off, so those people usually end up switching from SCRs to transistors.
- RS232 optoisolators do something completely different.
CAN sounds the most applicable in this case. The distances inside a house can be handled by CAN at 500 kbits/s, which sounds like plenty of bandwidth for your needs. The last node can be a off the shelf USB to CAN interface. That allows software in the computer to send CAN messages and see all the messages on the bus. The rest is software if you want to present this to the outside world as a TCP server or something.
CAN is the only communications means you mentioned that is actually a bus, except for rolling your own with I/O lines. All the others are point to point, including ethernet. Ethernet can be made to logically look like a bus with switches, but individual connections are still point to point and getting the logical bus topology will be expensive. The firmware overhead on each processor is also considerably more than CAN.
The nice part about CAN is that the lowest few protocol layers are handled in the hardware. For example, multiple nodes can try to transmit at the same time, but the hardware takes care of detecting and dealing with collisions. The hardware takes care of sending and receiving whole packets, including CRC checksum generation and validation.
Your reasons for avoiding PICs don't make any sense. There are many designs for programmers out there for building your own. One is my LProg, with the schematic available from the bottom of that page. However, building your own won't be cost effective unless you value your time at pennies/hour. It's also about more than just the programmer. You'll need something that aids with debugging. The Microchip PicKit 2 or 3 are very low cost programmers and debuggers. Although I have no personal experience with them, I hear of others using them routinely.
Added:
I see some recommendations for RS-485, but that is not a good idea compared to CAN. RS-485 is a electrical-only standard. It is a differential bus, so does allow for multiple nodes and has good noise immunity. However, CAN has all that too, plus a lot more. CAN is also usually implemented as a differential bus. Some argue that RS-485 is simple to interface to electrically. This is true, but so is CAN. Either way a single chip does it. In the case of CAN, the MCP2551 is a good example.
So CAN and RS-485 have pretty much the same advantages electrically. The big advantage of CAN is above that layer. With RS-485 there is nothing above that layer. You are on your own. It is possible to design a protocol that deals with bus arbitration, packet verification, timeouts, retries, etc, but to actually get this right is a lot more tricky than most people realize.
The CAN protocol defines packets, checksums, collision handling, retries, etc. Not only is it already there and thought out and tested, but the really big advantage is that it is implemented directly in silicon on many microcontrollers. The firmware interfaces to the CAN peripheral at the level of sending and receiving packets. For sending, the hardware does the colllision detection, backoff, retry, and CRC checksum generation. For receiving, it does the packet detection, clock skew adjusting, and CRC checksum validation. Yes the CAN peripheral will take more firmware to drive than a UART such as is often used with RS-485, but it takes a lot less code overall since the silicon handles so much of the low level protocol details.
In short, RS-485 is from a bygone era and makes little sense for new systems today. The main issue seems to be people who used RS-485 in the past clinging to it and thinking CAN is "complicated" somehow. The low levels of CAN are complicated, but so is any competent RS-485 implementation. Note that several well known protocols based on RS-485 have been replaced by newer versions based on CAN. NMEA2000 is one example of such a newer CAN-based standard. There is another automotive standard J-J1708 (based on RS-485) that is pretty much obsolete now with the CAN-based OBD-II and J-1939.
Best Answer
The normal configuration for an RS-232 link between two pieces of equipment is this:
simulate this circuit – Schematic created using CircuitLab
As shown above as well as changing the voltage levels the line drivers (typically a MAX232 or some similar part) also invert the signals. As long as you use line drivers at both ends of the link (or skip them completely and run the link at logic levels) then you don't need to worry about the signal inversion.
There are also some cheap hacks of RS-232 drivers used for hobbyist systems which invert the signal but don't give the voltage levels required by the RS-232 specification and so you may sometimes see signal levels of 0 to 5 V rather than the -3V to +3V minimum range required by the RS-232 specification. While technically a violation of the specification these will normally work fine at lower speeds.
Hopefully this also explains why you need to be careful not to connect the TTL level serial interface you get out of most processors directly to an RS-232 port. Not only will the signal be inverted and so not work as a data link, few processors can take -15V on their IO pins without going pop.