HomeTheaterdude's profile

Contributor

 • 

1 Message

Friday, August 26th, 2016 4:14 PM

Pace 8010 repeated number button commands

I am a home theater installer and we integrated a system with one of these boxes that worked great for a while, but my customers have complained of the number keys not accepting repeated presses of the button. What I mean is say you are entering channel 1005. It will accept 1,0, 5. Any number key will only be accepted the first time, a second press will not until another key is pressed first. Of course the at&t remote will work just fine. If it makes difference I am integrating with an RTI control system. I have already checked with RTI and all of their equipment is functioning normally.  Was there a firmware update that was pushed to these cable boxes?

Community Support

 • 

254.6K Messages

8 years ago

Hi @HomeTheaterdude,

 

Can you provide more details like make/model for Universal remote and how it interfaces with our TV receivers? Is this with IR TV remotes? This may take some time to investigate so any details you can provide will be helpful (screenshots, images of products)

 

regards,

ATTU-verseCare

Contributor

 • 

3 Messages

8 years ago

I have this exact same problem. I am also an installer and I'm also using an RTI control system (XP6) with a wired IR emitter stuck on the faceplate of the U-verse STBs. There are three STBs - IPH8010 and two ISB7005 boxes. They all react the same way. This seems to have presented once the software update was made and the user interface (guide, menu, etc) was updated. The original U-verse remote works just fine. I can provide details of the IR code library being used if necessary.

Contributor

 • 

3 Messages

8 years ago

 

On the RTI forum, I received the following reply from a seasoned installer:

 

***********

Almost sounds like it's acting as a toggle bit code. On the commands giving you issues learn a 2nd set of commands...I.E. 1 and 1a, 2 and 2a and so on. Learn each code twice so for 1 press the 1 as usual and for 1a do the same.

Now make the button a macro and use the toggle a/b command in the drop down and put both codes in the brackets and test again.

************

 

I'm not sure when I can test this, but if you get chance to, please post the results back here or in the RTI forum in the IR section.

 

Thanks

Contributor

 • 

1 Message

8 years ago

Did you have any luck learning all the A and B commands for the IPH 8010?

Tutor

 • 

4 Messages

8 years ago

I'm having the exact same issue.  I have an iRuleathome setup with iTach IP2IR (ethernet to IP gateways).  Everything has been working perfectly well for the last couple of years.

 

IPH8010 now won't take various key inputs when repeated.  Numbers repeated don't register neither do fast forward.  The light on the front of the box flashes so I know it's being received.

 

Example:  1111 is displayed as 1, however 1234 works.  2222 is displayed as 2, however 2345 works just fine.  Pressing fastward once works.  You can press it 500 times and it will not go any faster.  The out of box remote however works just fine.

 

I think it started with the lastest software that was pushed the IPH8010.  All other IR for all other devices works perfectly.  This seems like a problem with the last software for the IPH8010.

Contributor

 • 

3 Messages

8 years ago

It was the software update that created the issue. The box now needs to receive a toggle command from the remote. For example, you need the commands duplicated in a library and label them a and b for each number or command. Then your program needs to call 1a and then with the next press of 1, call 1b. Same for any other command that won't repeat. Your remote programming software will need to have a macro set up with this toggle command and you'll have to set this for every number or command that doesn't repeat. I can give an example for RTI, but I would have to look at others to illustrate. Funny enough, my Nevo remote still works flawlessly. Go figure.

Good luck!

Teacher

 • 

12 Messages

8 years ago

Yes, it is the update. I too have the problem. All programmed remotes can no longer be used for anything that requires pressing the same remote button twice in a row. For example, if I want to tune to channel 1000, the ISB-7500 will not accept the last two zeros and I end up on channel 10. There is no workaround.

 

I do have some advanced software that lets me look at the content of the signals being sent, and perhaps I can edit the commands before learning them so that my programmed remotes will work.

 

However, unless AT&T fixes this bug, everyone in the home theater installation business is going to be VERY unhappy!!

Tutor

 • 

4 Messages

8 years ago

As a workaround could we use pronto hex codes???  I've been trying to find online buy unsuccessful.  I tried to duplicate the device in irule and configuring the toggle but it's not working.

Tutor

 • 

4 Messages

8 years ago

Just to follow-up I tried adding both learned proto hex and global cache codes and neither is working when configured to toggle.  As the very least I can't seem to make it work.

 

I'm going to open a ticket with AT&T and point back to these threads.  I suggest everyone else having issues do the same thing.

 

Thanx!

Tutor

 • 

4 Messages

8 years ago

I've opened ticket J44940776.  I suggest others having this issue reference my ticket to try to get it escalated.

Contributor

 • 

1 Message

8 years ago

If they wont let us reference your case, can you post what you put in it, and we can replicate it?

Tutor

 • 

3 Messages

8 years ago

Has anyone found a working solution for this yet? I tried the toggle, no luck. Opened case J57025572, referenced BillinSoFL's ticket #, and they are sending me a Pace 8110 to replace the 8010. Also for reference, I have a very similar setup as BillinSoFL says he has, iRuleathome with iTach IP2IR.

Contributor

 • 

1 Message

8 years ago

Has anyone made any progress on the above issues?

Tutor

 • 

3 Messages

8 years ago

OK, I made some progress. Ended up using my iTach to learn the commands. As mentioned by others, it is a toggle issue. the button on remote has to toggle between 2 different commands. as stated, i use irule, so this was as simple as adding pronto codes (2 for each button), setting toggle for each affected button and adding both commands to the button. i removed the delay that gets added between them, but i'm not sure that is necessary. I've only had a chance to learn 1 button so far, but i will try to finish up all the affected buttons later. Here are the IR commands for the '1' button. will post more later.

 

[1_A] 0000 0071 0000 0024 000F 000A 0006 000A 0006 0016 0006 000A 0006 001C 0006 0010 0006 000A 0006 000A 0006 000A 0006 000A 0006 0016 0006 0010 0006 0016 0006 000A 0006 000A 0006 000A 0006 0010 0006 0CC7 000F 000A 0006 000A 0006 0016 0006 000A 0006 001C 0006 0010 0006 000A 0006 000A 0006 000A 0006 000A 0006 0016 0006 0010 0006 0016 0006 000A 0006 000A 0006 000A 0006 0010 0006 0E10
[1_B] 0000 0071 0000 0024 000F 000A 0006 000A 0006 0016 0006 000A 0006 001C 0006 0010 0006 000A 0006 000A 0006 000A 0006 0016 0006 0016 0006 0010 0006 0016 0006 000A 0006 000A 0006 000A 0006 0010 0006 0CC7 000F 000A 0006 000A 0006 0016 0006 000A 0006 001C 0006 0010 0006 000A 0006 000A 0006 000A 0006 0016 0006 0016 0006 0010 0006 0016 0006 000A 0006 000A 0006 000A 0006 0010 0006 0E10

Tutor

 • 

3 Messages

8 years ago

3rd time trying to post this.... i think the first 2 failed due to the length of post

 

Ok, so my setup is working good now. In addition to the above steps, I had to make sure that each command was set at repetition 1. Below is a link to all the commands that works for me (since pasting them here didn't work):

 

http://pastebin.com/zYijdjrV


NEED HELP?