JP1 Remotes

utmba95 · Joined: 15 Nov 2003 Posts: 40 Location: Austin, TX

I have a 6131 with extender 1. Since I got my IR Widget I am able to debug a couple of long term issues.

1. When I press a button twice very quickly, the remote only sends one command. Is there a way to speed it up so that it recognizes both presses?

2. When I press a button once for a very short duration, the remote only sends the command once. The OEM remote sends repeats for a similar duration button press. Is there a way to send repeats without holding the button down so long?

Thanks.

vickyg2003

utmba95 · Joined: 15 Nov 2003 Posts: 40 Location: Austin, TX

When the 6131 repeats, the waveform looks exactly the like OEM remote. It's just that I have to hold the 6131 button about twice as long to make it repeat than with the OEM remote.

I really have two issues.

#1 where I press the FFWD button quickly twice to get to FFx2 on the DVR, if I press it too quickly I only get to FFx1. This is because the remote debounced my two quick presses into one, or it's just too slow to respond. I'm wondering if this is a function of the remote or if it's configurable. This behavior is the same even if I don't activate the extender after a reset.

#2 the IR booster I built doesn't hold the 38KHz accurate enough, and the DTV box won't always respond to a single sequence (6131) but it will respond when there are repeats (OEM remote). Is there a way to make the 6131 send repeats without holding the key down for soooo long?

The Robman · Posted: Thu Jul 01, 2010 11:37 am Post subject:

mr_d_p_gumby · Posted: Thu Jul 01, 2010 2:50 pm Post subject:

utmba95 · Joined: 15 Nov 2003 Posts: 40 Location: Austin, TX

I uploaded a zip file with my .ir file and .ict files of learned signals. The device is 1377 and the protocol is 162. Are these sufficient to generate a custom protocol sending at least one repeat?

http://www.hifi-remote.com/forums/dload.php?action=file&file_id=8601

mdavej · Expert Joined: 08 Oct 2003 Posts: 4501

Utmba, have you tried the skipToTick command instead of ffwd to see if it works any better? A short press of skiptotick should behave the same as ffwd.

utmba95 · Joined: 15 Nov 2003 Posts: 40 Location: Austin, TX

I'd be interested in trying this out if anybody has time to create a custom protocol. Let me know!

mdavej · Expert Joined: 08 Oct 2003 Posts: 4501

Are you responding to my post? If so, I meant, have you tried skiptotick using the existing protocol? If it works, you may not need a custom protocol. So give THIS upgrade a try.

vickyg2003 · Posted: Wed Jul 14, 2010 10:11 pm Post subject:

The double tap on the 6131 looks like a button hold, not a tap.

Its easy enough to kick out another repeat for a quick press, but the double press is really not what I'd expect to see at all.

Does the unextended remote act the same way on the double tap?
_________________
Remember to provide feedback to let us know how the problem was solved and share your upgrades.

Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.

utmba95 · Joined: 15 Nov 2003 Posts: 40 Location: Austin, TX

vickyg2003 · Posted: Fri Jul 16, 2010 11:00 pm Post subject:

Well when I said it was easy enough, I didn't realize we were talking about the XMP protocol, a nasty beast. Anyway I don't recognize the 016C code. It doesn't appear to be the official version, nor is it the version currently being offered up by RM or KM. I've just been working with another poster to get the XMP up and running on a 7800, and the code being offered up is a lot smaller than the XMP that you have running.

I think it might be beneficial to try rebuilding the 1377 with the newer protocol and see if that improves the situation, but definately save your IR file just in case.
_________________
Remember to provide feedback to let us know how the problem was solved and share your upgrades.

Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.

utmba95 · Joined: 15 Nov 2003 Posts: 40 Location: Austin, TX

Fortunately, it's 0162, not 016C. I was using protocol "pid: 01 62" instead of DirecTV. Switching the protocol to DirecTV I no longer need a custom protocol and save a ton of space, but it behaves the same.

vickyg2003 · Posted: Sat Jul 17, 2010 8:19 am Post subject:

Duh, thanks for the correction. Embarassed

I guess I was a little tired when I revisited this post. I was wondering why I didn't notice this was XMP when I actually looked at the signal, but that still didn't make me question my misread. I am totally unfamilar with the DirecTV protocol so don't know why it is such a big protocol.
_________________
Remember to provide feedback to let us know how the problem was solved and share your upgrades.

Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.

vickyg2003 · Posted: Sat Jul 17, 2010 10:02 am Post subject:

Well I poked around looking for information on the DirecTV protocol and found John Fines Protocol builder file for the JP1 hacked version, but that isn't the right one either. There wasn't any documentation in the decodeIR.htm that I had on this machine, so I don't know what all the code in your executor is trying to do.

This probably isn't a debounce problem, its probably something that can be addressed in the way repeating is handled in the protocol.
_________________
Remember to provide feedback to let us know how the problem was solved and share your upgrades.

Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.