JP1 Remotes

I've uploaded v0.05 here which adds the multiplexor patch and swaps R_Dev and R_DevA. I've only done testing with an Atlas 3000.

argh! just yesterday I redid my remote using keymoves, but extenders are much better

Just redid everything with the new extender and everything seems to be working perfectly. Thanks binky123.

At the risk of embarrassing premature elation (get your minds out of the gutter and check the spelling of that last word carefully)....

HOORAAAAAYYYY!!!!

Can't wait to test it! Home theater installation is underway, so building the remote with a fully-functioning extender from the git-go (without intermediate multiple-remote workarounds) will be a MAJOR coup!

Thanks unclemiltie, and binky for getting over this (hopefully final) hurdle (and to sriram for testing, since I have been unable to even find a few moments to do THAT little bit!)

I looked at the code that Binky did and it looks like he did find the two issues that were nagging at me on this remote:

1: finding why the Multiplex protocol didn't work. The remote was reloading the device table on every keypress and the patch that Binky has put in does remove that. (and the unload protocol puts the remote back to "virgin" state) The code that binky put in should work on the 3033 and 3000 remotes. (as a side note, is anyone trying this extender on a 2150 (3032?) It should work but I don't have one.

2: finding the mixed up current and active device (R_Dev and R_DevA) is a major step forward. It would have taken me some serious time to find that, but it appears that having them mixed up was causing the spurrious device selection bugs.


Thanks much to Binky for finding these!

now onto making this an "official" release. I'm going to start loading stuff into both my 3000 and 3033 to start debugging tonight now that I fixed my JP1.2/3 cable last night.


-bill

as a side note, is anyone trying this extender on a 2150 (3032?) It should work but I don't have one.

I'll try to get to it. I'm currently buried with with personal stuff, but if I don't report back by June1, give me a kick in the butt and I'll pull it out and give it a test.

UncleMiltie,
I did some testing last week. The device selection issue seems fixed (thanks to all) mostly. LKP with device selection seems to misbehave, when I have the special macros on device keys. I started working to isolate the issue and got my remote locked up pretty solid. I finally got it back by reverting to an older build and re-uploading. I'll try and put some more time in on it and see where it is, exactly. It's much better though overall. Thanks again,
jeff

Anybody get the pause protocol to work?

The last time I looked at it(for the LDKP issue), it seemed ok. The unit time is not exactly 100ms(really 96.8ms). What seems to be the issue? Not delaying at all? Describe the macro you are using or upload the .IR file. I only have the Atlas 3000 so I'll have to convert your 3033 .IR file over.

binky123 wrote:The last time I looked at it(for the LDKP issue), it seemed ok. The unit time is not exactly 100ms(really 96.8ms). What seems to be the issue? Not delaying at all? Describe the macro you are using or upload the .IR file. I only have the Atlas 3000 so I'll have to convert your 3033 .IR file over.

I'll try and get a test IR file setup tonight.
Best,
jeff

The pause doesn't seem to be delaying at all for me. I've uploaded my .ir file here. The macro I'm using for the pause test is the F2 (On Demand) key. I also have the Atlas 3000 so it might be a little easier for you to test. Thanks a lot binky123.

mostly a cleanup of the source code but did include the hex files with notes included to indicate which devices and protocols were included.

More checks against RDF values in the assembly source (not included in this release) to help in building future versions.

Most notable is that I have added support for the Comcast URC-1067 JP1.3 remote (not the URC-1067A JP1.2 remote!) with this version. The hex and assembly files are NOT included in this release since I'm going to let a couple of experts play first and if all goes well that remote will be supported as well.

I think this extender is getting close to a V1.00 release version, keep banging away on it and reporting bugs/issues!


-bill

sriram

Can you please upgrade to V0.06 (just posted) and then re-post your IR file. I'm having RDF mismatch issues and want to take a look at what's going wrong with your pause.



binky

The Pause value is an amount that I typically tune towards the end of the development of the extender. The one in this remote is the one that I used in the URC-9960B01 Kameleon. Thanks for reminding me that I have to tweak that one a bit, it'll be in the next version!

Here's my ir file upgraded to .06. Thanks unclemiltie.

About the Pause:

Here's my ir file upgraded to .06. Thanks unclemiltie.

The Jp1.2 remotes require 2 Hex bytes to trigger ANY protocol. And I'm pretty sure that is true with JP1.3 remotes as well, or any remotes that have 5 digit EFC's for that matter.

Add $00 to the hex string, and I'll bet it works.

I tried $1e $00 and $00 $1e and it still doesn't seem to work