Hi all. I have programed in the one to ten numbers in my pronto so i can enter channel numbers without scrolling. The problem is when i go to add a number a second time..for instance...700...the pronto sends the seven, the zero, but the second zero never happens..i get a question mark on my set as to what number am i trying to enter....
whats my work around here?
thanks

You need to put a delay between each digit.

7 delay 0 delay 0

This sounds stupid, however, is there actually a channel 700?

When a channel does not exist it can not tune it.

If this is not the case, a delay may take care of it. I generally do not use delays in the channel macros because it can cause more problems than it solves but if your box is a slow responder it may be required.

How are the codes programmed? Learned? Built in code? pasted hex?

What model cable box? Which provider?

hi,

i have a cable reciever where i have to programm 0-9 and the buttons 1*, 2*, until 9* (19 buttons in total). Others will only have to program on eadditional button like */**(this one is for all channel higher than channel 9)
. Only if you press these buttons the box will wait for another digit. Otherwise - if you press 7 and 0 for example -the box would switch to channel7 and then directly to channel 0. Maybe this will fix your problem?

ageage

my channels go up to 1000.
Thanks for the suggestions.....why would you not want to put the delay in?...what problems come up with that?

Nothing, except your command or macro may not execute properly. A pause is sometimes needed. Adding a slight delay will give the device time to execute the first action before it receives a second.

My motorola box responds fine without any delay between numbers and I have found that sometimes the delays will result in either the first or last number not taking when using learned codes. Also, I find that many of my clients using line of sight IR do not understand the concept of pointing the remote for the entire sequence and even a fraction of a second delay added between numbers can be the difference between a happy user and a callback.

The motorola codes generally can be learned without problem, however, I have found that they can be very sensitive so I have gone to using only cleanly generated codes. This has improved the box response and macro accuracy.

For my moto setups I have the duration of the numbers set as .15. No delays and they work.

added the delays...works great..thanks

My approach to this has been to have no delays on the keypad numbers, thinking that a person can't hit the screen numbers fast enough for the cable box to miss a second same digit. I've never had a problem with that.

Then I have added 0.1 second delays in macros ONLY when there are double digits. This has also always worked.

edit: I just remembered a detail about the delay. It is likely that the delay will need to be the same in every macro. But if I make ten such macros that work, and then find that I need a longer delay for one macro, since I want consistency I would have to go back and modify the delay(s) in each macro.

To avoid this, I alias all of the macros to a separate "digits" page where there is also a button named "delay." Every macro then aliases to the "delay" button for the macro delays.

I initially make this 0.1 seconds. If I find later that it needs to be changed in the macros, I can change that ONE button, and the delays are changed in all the macros all at once.

another good idea from someone who has likely programmed a few remotes!

Ernie... I had 2 code pages at one point. Page one is the one that the customer actually used with #s on it. Those contained database codes and worked just fine. The second page had the database codes with a .1 delay after them. Then I referenced the second pages numbers for macros. It worked but I noticed from time to time the database codes missed here and there. So I upped the duration on the database codes on page one. NEVER MISSED AGAIN! So I went back in and extended every database code to .15. Then I tried referring to page one for the macros...

so
#3 duration .15
#0 duration .15
#0 duration .15

Works perfect.

I always have hidden pages that are just codes in stupid ugly 17x60 (or so) buttons made so I can get almost thirty commands to a page, then I alias every user button to those pages.

Your method required only ten changes of delay lengths. Mine requires one, but it takes more time than yours because every macro has several "delay" commands aliased to the master delay button. I would now get even lazier and change your commands from, say

6... 0.15 second delay

to

6 "delay" button

Then changing the delay on every button requires only changing the length of the delay button, and your method of including a delay as part of the numeral shortens the time it takes to construct macros.

With that, I think we've just about beat the crap out of any programming time-saving that can be done here.