I don't currently have any specific instructions for programming RTI remotes, but hopefully this spreadsheet of PS2 IR codes (courtesy of John Newby) can help. http://www.ir2bt.com/files/PS2%20IR%20Codes.xls

Please share any information you may have on the RTI remotes.

Bruce...


_________________
Bruce Mitchell
www.ir2bt.com

I used the master list to populate the PS2 codes, and it worked quite well. I had to back off the repeat and sustain on a couple of the codes so it didn't repeat the code (like "subtitle"). Also the Standby/Off code was not in the database, at least not where I could find. I simply entered the hex from the supplied spreadsheet from John Newby. Programming discrete power on and off workarounds were quite easy, thanks to the posts in this IR2BT forum.

So far it is a great device that I already have implemented into a RTI T2C and a Pronto TSU-9600.

Brilliant news. Well done marsht.

Just finished installing the IR2BT with the T2C and its working flawlessly. I programmed all of John Newby's hex codes into the ID IR Database and would be happy to save others the work and share the CML with whoever would like it. I'll also send a copy to Bruce so he can share it here with all his RTI customers

Credit and thanks to Jim Bask at RemoteShoppe for sharing his CML file with the IR2BT community.

http://www.ir2bt.com/files/IR2BT.cml

Bruce...


_________________
Bruce Mitchell
www.ir2bt.com

Got my T3 and M2 working with the IR2BT last night. I am also using an RP6. The power down sequence I used was PS (hold for 2-3 seconds), X, X. For the PS button, I had to bump the number of repeats all the way up to 25 (the max) to make it last long enough and work reliably. But so far, so good. I'm still following the other threads in the General forum to see if there is a better power off macro that works in all cases (supposedly with 2.2, the 6 step macro doesn't work with games, but I haven't tried).

Hope this helps some folks.

Dino

dinom wrote:

Got my T3 and M2 working with the IR2BT last night. I am also using an RP6. The power down sequence I used was PS (hold for 2-3 seconds), X, X. For the PS button, I had to bump the number of repeats all the way up to 25 (the max) to make it last long enough and work reliably. But so far, so good. I'm still following the other threads in the General forum to see if there is a better power off macro that works in all cases (supposedly with 2.2, the 6 step macro doesn't work with games, but I haven't tried).

Hope this helps some folks.

Dino

If you're on 2.20 firmware, the sequence you said you're using won't work with games, but the original one will (but won't work with movies).

When you say you bumped up the repeats to 25, what does that mean? Sorry, I haven't used a RTI remote. Is that repeating the same sequence 25 times, or hitting X 25 times?

It repeats the code sequence 25 times (like pressing and holding the button continually). This is not the same as 25 single button hits in a row.

Sounds about right. For the URC MX-950, I went to 30 repeats to be sure it worked reliably.

BlvJohn

I had to go a little bit longer than the maximum 25 repeats for the PS button. I had 2 consecutive commands of the PS button in the macro, each with the maximum 25 repeats, plus I unchecked the default .3 second delay between commands for the first button press(effectively making this 50 repeats of the command). This worked more reliably for me than the single code sequence.

marsht,

I thought of that, but didn't think that having two consecutive commands, even after removing the 0.3 second delay, was the same as one long repeated code. Most IR code streams start with a header or preamble and end with a trailing sequence. I would think just appending two consecutive codes would still not "trick" the receiver into thinking it got one long sequence (since the repeating part is in the middle of the stream), but I'll give it a try anyway.

Also, are you using the PS (3 sec), X, X power off macro, or something else?

Thanks.

marsht wrote:

I had to go a little bit longer than the maximum 25 repeats for the PS button. I had 2 consecutive commands of the PS button in the macro, each with the maximum 25 repeats, plus I unchecked the default .3 second delay between commands for the first button press(effectively making this 50 repeats of the command). This worked more reliably for me than the single code sequence.

dinom,

I have put the power off sequence as a system macro, and have that in my system macro to turn all devices off. I have not fully experimented with how things are working, but it does seem to turn the PS3 off most of the time, except when there is a game loaded. Since my macro has the TV turning off before the PS3 powers off, I don't know exactly what is happening onscreen. I do know that my power off sequence seemed more reliable. I also had to add a delay between system macros, so that the entire sequence could be carried out before the next trigger command was given.

Hmmm, was that as clear as mud?

I followed you

I also had to add some time delays between the system macros. They are all running off the same RP6, so I thought it would take care of it automatically, but it seemed to "skip" over the long PS button press if I didn't add some delay. Looks like you saw the same issues.

Just got mine today and I programmed it into my T2C/RP1 combo, thing works like a champ. I ended up using: power (set repeats to max), down, down, down, up, X, X for my power off code and it seems to be working flawlessly in every scenario powering off. I did have to add time delays between each command to get things to work though.