I am at a customers now. THey were having probelms with there remote (T2C) and that it wasn't turning on TV or changing channels. There is onr T2C hooked up to a RP1.

After checking it out, no commands really sem to be sent at all. When I tried sending a shutdown all of the comonents. the IR led's kept flashing and would not stop. I unplugged the power leading to the IR connection block, which also powers the RP1 and nothing seems to work.

I have attempted to send the system file again to the remote as well as the processor and no go.

I can see on the processor the RF light blinking, when commands are sent but the status light is off.

Any thoughts? Bad processor or bad remote or something else?

I have also tried to pull the config off of the processor as well as the remote into a new system file to see if it looked ok or seemed corrupt but that part seems ok. Its as if the processor isn't sending any commands or the connection block is bad thus not sending any IR.

Thoughts?

You may have a high level of interference which is causing the processor to emit signals - try relocating the processor and see if it behaves the same way..

I don't think interference is the issue. It never was before and nothing here has changed. I just played around with it a little more and I see that when I press commands on the T2C the status light does not emmit at all. I tried unplugging the phoenix power connetor and pluggin it back in again and after a couple of tries I got the status light to light up with commands and turn on the first component and then the emmitters just constantsly blink. If I unplug again and then try it again I get nothing.

this happened to me a few weeks ago w/ a t2c, major interference all of a sudden w/ a new cable box they had upgraded to in the house. rp1 was there for a yr then got fried, swapped it out and worked!!!

Plug the power directly to the RP-1 instead of the connecting block, from my understanding you can damage the connecting block by powering it directly; causing the unit to become none responsive or demonstrate the erratic behavior you are experiencing.

You could verify the T2C is OK by creating a temporary system file without the RP1, of course this will only verify IR operation from the T2C.

The description you give does sound like the RP1 is failing or subject to some inteference. You could unplug the power to the equipment around it, and test for proper indications on the RP1. I've had cable DVR's that were in service become erratic using HDMI, where they had been fine before, so it wouldn't surprise me if some RF characteristic suddenly changed, and became a problem.

Also don't rule out the possible bad connecting block or power supply. Try power directly to the RP1 without the connecting block, just to see if it's operation changes in any way.

I've installed a few RP1's with power feeding through the connecting block, and never observed any go bad from this setup. But if this is a known issue, I could just be lucky.

Good luck

Just to note : I had this problem recently when the unit was next to Floruecent lights, and then another case when I had a bad batch of IR codes. Change the config and see if it behaves that way as someone mentioned. Use an entirely different config file for both the remote and processor.

You probably already figured it out but if you haven't try turning the ir level on the connecting block up or to max. I found more then a few times if I had the connecting block loaded up with emitters.....the default setting wasn't enough to send a stable signal. It was enought to see the emitters flash but the signal didn't make it through. Upon tuning up the signal on the block it worked perfectly.

GL

Designer Mike is the Winner :).

I also called RTI and they said that it technically should work connecting the power to the block first but for some reason, that engineering can't figure out, something degrades over time and then you get the problem I was experiencing. This is why it has been working for two months.

I cut the power lead and spliced in an 18/2 cable to reach the RP1 from the outlet and plugged it in direct. Everything now works perfectly fine.

WTF? Does this mean that I can look forward to systems failing because we connected power to the block they supply? That's the way we do it on most of our jobs.

No shit, I am gonna be f#ckin pissed if this hold true powering the block. I do like Greg does...

I too, hope this doesn't hold true. In some systems I have had to move the RP-1 because of a UPS backup given interference and powering the RP-1 with the connecting block.

Thats just great... Is RTI gonna comp us for having to go back to switch out those RP1s? I hate it when things like that crop up.

There isn't a problem with the Rp1 at all. The issue is the connecting block itself. Something happens over time that causes the power flowing through the connecting block to degrade over time. If you plug the power supply direct to the RP! or snip the lead and extend it, like I just did, the RP1 then works fine and all is normal. I also removed the 12v wire that was running between the rp1 and the connecting block as well so no power flows to the connecting bloack anymore.

After Designer Mike mentioned what the cause could be I re-read the RP1 manual. It does say to hookup the power direct to the RP1. IT also says that the 12v power lead connection on the phoenix connector is directly tied to the power in connection on the Rp1. So technically it can be powered remotely by pushing 12v to the 12v lead on the power connector. I quess not through the connecting block. The connection block does come with the Rp1 and there is not mention or diagram saying that you can just hookup the power adapter to the connection block and then run wire to the RP1 terminals for power. I like all of you ASSUMED that this is logical and makes sense.

According to the manual, there is no need to amplify the connnecting block at all, unless you are driving more than 10 emmitters. Then the connecting block needs to be amplified. Wonder if one would still have this problem using a xantec connecting block instead. I of course am not going to test this out and have to go back again at a later date. Just safer to run an extra cable or one with more conductors to hookup power the Rp1 direct.

Your right... Probably my fault for being stupid. And doing what I am told... Usually is.