Since the XP8 came out, I have been trying RS232 control of components using the new RS232 library: what I have seen is that RS232 does not always give better/ faster control than infrared

So I thought I would ask if others have noticed this as well?

For example, a Fujitsu P63 plasma works great with an IR emitter: but going to RS232 it seems to be a bit less responsive: sometimes the plasma does not respond and I have to resend the command...went back to IR and it seems better

I checked the serial codes and baud rate et al

Does anyone else agree that infrared is sometimes simpler and better?

I still do more IR control than rs232, but I'm implementing rs232 more and more into systems. For some of the components we use there are more discrete control commands available via rs232, such as specific picture color mode commands for Elite plasmas, not available as IR. I have had to alter some command strings to add a slight delay between characters in an rs232 command string to get a device to respond correctly, and I've had to add delays when using a long wire run to a device.

If your commands are indeed working, but just not every time, I would maybe add the delay time between characters. I still consider myself a novice when it comes to the rs232, so I'm hoping some of the rs232 veterans chime in on this, as I can use the info as much as you.

I do like the fact that the emitter does not fall off when using RS-232. :)

I have also been experimenting with the 232 a whole lot more.

As for the Fujitsu: I haven't tried the new library codes, but I did notice something from looking at the codes.

When I did 232 on the Fujis before the library ( I did a lot of them) I did the code like this (Bear with me, I don't have the code in front of me):

G\r
Power On
Q\r

The code in the library looks like this:

G\rPowerOn\rQ\r

My code always worked, bulletproof, every time. I'm betting that whoever put that code in the library at RTI either didn't know any better, or got lazy.


Shoot me an email, and I'll send you an example. It would make a lot more sense that way.

for me it depends on the device and the circumstance. generally we use ir b/c it is just easier. but on tvs, or in racks where we have 3 and 4 switchers, or like someone else said when you just cant get the same control ir.

Receivers
TV
Switchers
Controlable Amplifiers
etc...
These are usually much better via 232.

If it has a direct input on the back I use it (IR or 232). I have done many racks where the only emitters used are on the cable box(es).

Every manufacturer is different. Denon for example does not allow unit ID control via 232 (yet) like they do with IR. It depends on your need and your level of familiarity with the components.

With 232 you have absolute control over the comand strings. With IR you do not have this same absolute control unless you are generating your codes cleanly. I try and generate all of my IR for reliability so for me there is no time difference when using 232. I would rather shoot myself than have to consistantly rely on learned codes (mine or from others).

Springs is fighting with this 232 latency issue in another thread - it seems to be an XP8 problem rather than a RS232 vs. IR thing. According to Springs, he had to switch back to using the RP6 to fix "delays" in the 232 command response.

I'm definitely keeping an eye on this issue and would like to see it solved before I jump on the XP8 bandwagon!

Did you get my email? Did it shed some light on the issue?

thanks: I did but have not had a chance to look yet

I also had an issue with MC-12 RS232 volume ramp up and am beginning to think it is related to XP8 issues reported in other threads

I am about to install a second XP-8 and need to resolve these concerns first

I should get to it over the weekend and will report back

Thanks!!