I have Been programing Rti for around 2 years and remotes in general for over 6.

I now have 1 T2-C and a Rp-6 with a Rm-433 in my loft and the same set up in my family room.

There is no shared equipment and each T2-c is set to communicat with its respective rp-6.

Both remotes are talking to each Rp-6. Both Rp-6's "see" all commands sent from each remote. The R6-6's only do something if it is the correct Rp-6 beeing talked to. Problem is if someone is in both rooms the Rp-6's get overloaded and they work on a first come first serve basis.

I found the setting for Zone codes but that is system wide. Will I just need to have 2 seperate files with different zone codes?

you would need 2 separate files

each RP6 will still receive all remotes (show signal in activity) even with separate zone codes: so any improvement would be limited

The XP8 has a more powerful processor that could address this

I just tried the 2 seperate system files with different zone ids.

It works basicaly the same . If one remote is issueing a volume up for several second and the other remote tries to do anything. The first remote has priority.

If there is no way around this, thats crap.

I just never noticed this on any of my installs because I was just looking for correct communication routing and everything working on an individual basis.

Now that I have it in my home and am using it, I find the problems.

I have a similar situation: 2 RP-6's in same house/different areas set on different zone codes

I am hoping to replace one RP-6 with an XP8: other RP6 connected to expansion port/ put everything back to common zone code

I heard the XP8 can do simultaneous/quicker processing and is designed to address this: we shall see...

i thought u had to use ir routing for things such as this... as in go into loft rp6, tell it which ir port to use on each press or something along those lines. i havent used an rp6 yet, but the thread caught my attention.

wouldnt u go into family rm remote and tell it to use ir port one-cable box, fam. rm rp6??? And same for upstairs??? I always thought that was what the ir routing was for

Yes you are right as far as routing goes. However the rf antennas (Rm-433) see all remote comunication. If I am using the Family remote theantenna for the family sees it and does what is needed, however the antenna for the loft remote also sees it and know not to do anything. the problem with that is while it is receiving and not doing anything, if the Loft remote tries to get it to do something, it is paying attention to the other remote because it started talking first.

Does that make sence?

Yes it makes sense and is a problem with every RF system.

I spent a 1/2 hour troubleshooting a multi-zone,four remote system once.
Everything had worked perfectly for over a year.
Suddenly, everything quit working.

When I located the remote that was stuffed in the recliner that was pushing a button, the problem was solved.

Wow!

You just do not forsee crap like that... I bet they were ready to blame the problems on you!

I just had a client email me to tell me how dissatisfied he was with the RTI product. It was just an issue with an incorrect page link in MY programming (beta version for the project). He at least understood after I told him what the issue was but most won't.

i 2nd that!!! i got a client now who is on his 3rd t2c!! For one, he is the client from hell who wants something for nothing, didnt want the t2+, he HAD to have color but didnt like the price. I been there a dozen times for service calls cuz his remote doesnt work!! i THINK HE IS THROWING IT ACROSS THE DAM ROOM but u cant tell them that!! Everytime i do go there, i load up the t2c in about 10 mins, go through it entirely, and it work like a charm everytime!! This guy is IRATE w me!! Im so done w this guy

You can tell them that if you can tell them exactly why you know it to be so.

Next time you're there, inspect it and write up the inspection but don't tell him unless he asks what you're doing. Note especially the position of the battery under its clamp. Then if you're called back for a problem, note if the battery has moved. I found with a T2+ that a drop will often cause the battery to slide under the cover, and the more it has moved, the worse was the incident. One T2+ with a broken battery terminal might have been broken from the battery pushing sideways against the connector. Better remote design would have prevented the battery from moving -- an indentation in the surface for the battery to nest in -- but anyway, this is a great crash and smash indicator.

Ernie,

thats a great idea!!! thanx i appreciate it. Im going to start to look at that and makes notes of it. Lets be honest, we ALL drop remotes every now and again. I drop mine atleast once every 2 months!! It usually doesnt hurt it, but one BAD drop could destroy the whole thing...

I have considered putting thses into the remotes of problem customers [Link: shockwatch.com]


Below is blurb from my install Warrantee


Contractor shall not be held liable and customer agrees to hold contractor harmless for damage caused by acts of God or misfortune, such as but not limited to: Lightning, earthquakes, floods, tornados, hurricanes, mud slides, fire, settling of structure(s), intentional destruction of property, robbery, neglect, war, acts of terrorism, damage caused by federal state or local law enforcement and or military personal, damage caused by children or pets, damage caused by animal(s) or insect(s), damage caused by organic or inorganic things not native to this planet, damage caused by misuse or abuse, damage caused as a result of work performed by others, products installed by others and / or modifications made by others or the home owner, Or any other event which is outside the scope of contractors control or obligation(s).