RS-232 communication “can” be better but it isn’t automatically so. There are a great many variables that affect the outcome.
1.Is the device you are trying to control capable of “2-way” 232 communication? 2.What return data is offered by the device in question? (this varies greatly) 3.What is the value of that return communication? 4.Is there a module available or do you have the programming skill necessary to implement 2-way communication back to your TSU9600?
The reliability of 232 based controls can be superb, but well captured and implemented IR codes can also work in a very consistent manner. The main benefit of a 232 command is that there can be confirmation that the command has taken place, and if not the command will be resent until confirmation is received. This however doesn’t happen automatically and requires scripting dealing with “conditional statements”.
Other useful data that can be displayed such as volume level, current input selections, Current Sound Modes, Disc and track information, etc. Again this dosen't happen by just connecting a DB9 connector, this data is normaly obtained by polling a device and listening for a reply. This reply is then displayed graphicaly on some sort of a "widget".
This is a very simplified answer to 232 functionality on the TSU9600 but it should give you a basic idea, so you can make an educated choice on extenders.
