DirecTV H-20 troubles

Danny Campbell

This thing is driving me crazy. I am using the SP function of the send_command on several of these units located in different rooms. Nothing is consistent. For example, if I try to get it to switch to channel 14, I send it a SP for the 1 and the 4. Sometimes I get 14, but other times I get 1144 or 144, or 444 or 111.

All of these systems (5) are NI-3000s. I have tried a variety of IRL files, and even PULSE commands. I have tried adjusting the pulse time, and have changed the CTON and CTOF values, but nothing seems to work.

Does anyone know the secret? I've never had this much trouble with any IR device before.

vining

Have you tried direct from IR edit. Under tools in IR edit go to actuate where you can send an IR command direct to your device 5001:9:0 or what ever it is from IR edit. You can change the pulse time as well. I had an similar issue 2 weeks ago where I was getting double commands everytime I pushed the cursor up or down arrow for TV cursor control. Playing with the IR edit you can verify if the IR code itself is at fault, adjust the pulse time to see if that's the problem. Otherwise is most likely your code that's the problem. Sounds like your pulse time is on the boarder where sometimes it works and sometimes you get doubles. 2/10th worked for my situation.

I ended up using Set_Pulse_Time prior to the event and then changed it back to default (5/10th) afterwards (it's global and may have a negitive effect other IR devices if left at the new setting). I might have tried the CTON to change it but I'm not using 'SP' commands and actually didn't know it existing back then.

]
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
more buttons......................

BUTTON_EVENT [dvTPTV,158]// TV HLN Vid 1
BUTTON_EVENT [dvTPTV,159]// TV HLN Vid 2 
BUTTON_EVENT [dvTPTV,160]// TV HLN Vid 3
BUTTON_EVENT [dvTPTV,161]// TV HLN P Off same as HLP 
BUTTON_EVENT [dvTPTV,162]// TV HLN P On same as HLP  (**Button.input.channel**)
    {
    PUSH:
	{
	nButton = (BUTTON.INPUT.CHANNEL)
	set_pulse_time (2)
	pulse [dvTV,nButton]
	to [dvTPTV,nButton]
	set_pulse_time (5)
	}
    }

Danny Campbell

I'll give the IREdit actuate a try when I'm there tomorrow.

Thanks.

GSLogic

I always seems to use the SP command, it's great for stacking multiple pressed IR commands. Try setting the CTON /CTOF times for your device.


DATA_EVENT[dCABLE]
{
ONLINE:
{
SEND_COMMAND DATA.DEVICE, "'CTON', 3" //IR SEND ON
SEND_COMMAND DATA.DEVICE, "'CTOF', 3" //IR OFF BETWEEN SENDS
}
}

joelw

Danny Campbell wrote:

This thing is driving me crazy. I am using the SP function of the send_command on several of these units located in different rooms. Nothing is consistent. For example, if I try to get it to switch to channel 14, I send it a SP for the 1 and the 4. Sometimes I get 14, but other times I get 1144 or 144, or 444 or 111.

All of these systems (5) are NI-3000s. I have tried a variety of IRL files, and even PULSE commands. I have tried adjusting the pulse time, and have changed the CTON and CTOF values, but nothing seems to work.

Does anyone know the secret? I've never had this much trouble with any IR device before.

Yes. Try moving the IR emitter about 1/4" to one side of the IR receiver window. Out of around 50 hughes receivers, I've had this problem on ~10 units.

DHawthorne

joelw wrote:

Yes. Try moving the IR emitter about 1/4" to one side of the IR receiver window. Out of around 50 hughes receivers, I've had this problem on ~10 units.

I've had this with various devices, and it seems sat receivers in general are more likely to have it than others. The explanation: their IR sensors are too sensitive and subject ot saturation. Moving the emitter weakens the signal enough that it doesn't overload the sensor anymore. It's one of the first things I try now when I have a wonky IR device. If moving the emitter is not viable, you may be able to decrease it's output by flipping the element over in the emitter shell. If you pop the shell off, you will see the LED has a lens on one side, and not the other. Most emitters default with the lens facing the output side. Flip it over so the lens is facing out and the emitter output will be decreased.

joelw

DHawthorne wrote:

If moving the emitter is not viable, you may be able to decrease it's output by flipping the element over in the emitter shell. If you pop the shell off, you will see the LED has a lens on one side, and not the other. Most emitters default with the lens facing the output side. Flip it over so the lens is facing out and the emitter output will be decreased.

Yes this was a trick AMX promoted for their Xantech OEM emitters, in the mid to late 90's.

Chip Moody

I forget if it was here or on another forum, but I've seen at least one person mention they had a great amount of luck with putting a piece of electrical tape over the IR window with a pinhole in it, (the tape, not the IR window) then putting the IR emitter on the tape...

- Chip

Danny Campbell

I finally got them working today. If I held the emitter back away from the receiver it worked fine. Since we were using the big patches to hold them in place, I turned the lens toward the receiver, and folded a small bit of copier paper over 4 times and placed it between the emitter and the receiver. That did the trick.

The H-20 places the receiver flush with the outside edge of the cabinet, where most devices have them sunk about 1/2" behind the smoked plastic. That probably helped make them more sensitive.

Anyway, thanks for everyone's suggestions.

mstc

Reduce Emitter Output

Reduce emitter output by adding a resistor in series with the emitter to reduce the amount of current flowing through it. Try 470 ohms, 1/4 watt. Although folded paper is a workable solution, this is probably a more *proper* way of achieving the output reduction. The down side is that you (or someone) will have to operate a soldering iron and apply shrink tube to accomplish it.

JMHO Kol