I'm looking for the code format for channel number and delay needed between IR pulses for the receiver to operate well.

I'm assuming the format is xxx[enter].

Is their a delay from power up until the first IR commands is processed?

Thanks!

I'm intrigued by this question, having dealt with that receiver recently.

Mostly the intrigue is, what the heck are you talking about? What are you trying to do? What device will output this code to the receiver, and in what way will it put it out?

If you are talking about the factory remote, the format for the delay is shown below, with each step preceded by } for clarity:

push channel number button
}lift finger
}move finger so it is over a different number button, if appropriate
}lower finger
push channel number button

The time it takes for you to lift your finger, move and lower it again is the delay.


Do you mean hex code for a delay command that is in the factory remote (but actually, to my knowledge, is not)?

Do you mean you need to be sure there is a delay between the individual digits of channel commands, such as 2-2-2? You would program that into an integrated remote using its own delay or some other trick to make sure the receiver knows that there are three 2's there, not one long 2 (or make sure you lift your finger).

You're assuming the format for the delay command is xxx(Enter)? I believe that pushing Enter on the remote will direct you to the number of a channel that you have just entered. Although there is no Enter key on the remote, just "ok" or something like that, so... what do you mean?

I use 1/10 of a second and it is no problem for me. You may be able to go shorter than than but the remote I use doesn't allow me to go any less than that.

I am doing a custom Crestron control program with this unit and need to know the delay from off to the first IR code that can be received. Also, the shortest time between digits and still be recognized as a valid pulse.


I will be using IR, but will be automating the IR commands with Crestron. Just need to know the pulse duration and the delay between pulses.

Thanks vts...I'll give it a shot.

Hey Matt, I use the Hughes HIRD-E86 more than any other box, and I always use the Pronto's with an IR delay of 1/10th of a second in the 'power on' and the 'Fav's logo's' macro's, and it works fine everytime, just like vts said. And after the equipment gets turned on in the 'all on' macro, I set the HD channel to 199-HDnet for a crisp picture everytime time the client turns the system on. Just curious, but is that what you're trying to do?
Hope this helps...
BP

Matt,
Thanks for the info that you are controlling this with a Crestron.

1/10 second should work well, as said; every time I have run into the power on/other command scenario, I have had to try, try again until I work out the shortest 100% reliable delay. I once had a Sony HD-ready TV that required eight seconds between power on and any other command. What a DRAG that was until I located discrete on/off commands and created a system on macro separate from source selection!

Have you considered not turning off the HD DSS receiver? As I understand it, turning the receiver off actually does little more than mute the video outputs and kill the channel 3 modulator. Since this unit has discrete on and off commands, and someone might just manually turn it off, maybe you can find a place in the Crestron program to put a "satellite on" command well in advance of choosing the satellite input. This way, no matter what, the receiver will be on and no delay will be needed.

Ernie you mentioned that this piece has discrete on/off codes. I haven't been able to come accross them. Can you post them here or email them to me at [email protected]

Yeah, I don't plan on turning off the receivers, but will be automating channel selection with a SCALA program. Along with TPS interface and E-control. Should be fun.

I think I found the "World Record-Holder" for power-on delays (excluding projectors)...

I recently worked on a Sharp LC30HV2E (European version) 30" LCD, which takes a FULL 20 SECONDS to recognize any other commands, after powering on... :-)