JP1 Remotes

If putting a “unnecessary” dev_xxx before the first real key in the macro always works that might be a reasonable limitation.

jeajea wrote:If putting a “unnecessary” dev_xxx before the first real key in the macro always works that might be a reasonable limitation.

No I need to figure out what is going on with this. Can't have it depending on a kludge to work. I've had some really screwy things going on with this remote, and interrupts..... Perhaps I left a line out somewhere, I need to check this against my other extenders to make sure I have the watchdog timer setup correctly.

Doh, where was my head. I've been fretting over nothing.

DSM's need to be at least two keys long in order to work. adding '00' to the hex, either before or after the key works just great. I will check to see if that's in my documentation.

However, I did find one place ECA5 which was 64, but if changed to 01 works much better.

Edit:
It was in the documentation, it just didn't address DSM because I didn't think that a macro would ever be one key.

So I changed the documentation to say.

This remote uses 2 byte EFC’s. It is important that you remember this when using the special protocols. If you write a DSM, Pause, ToadTog command that results in the HexCmd field containing just one byte, it won’t execute. You might end up with just one hex byte if you are just trying to force a ToadTog on or off, or a one key macro, or a pause command that results in one byte. If the HexCmd column shows one hex byte, you’ll need to pad that hex command with $00 or some do-nothing key.

I've updated the link once more.

I'm hoping to put this in the extender area next week.

So please let me know if there are any more problems.

I have been running your latest update for 3.5+ days with no issues.

I have started using your extender. Since I am a newbie, I have what may be a stupid question. Some of my device upgrades are in RM and some in KM. I am unable to assign certain buttons such as "discrete on" and "discrete off" in KM. Is this because KM needs the extender built into it? Does it not use the RDF file that you provided? If it does, I am not sure how to add it.

KM does not use the RDF. KM is hard coded for the 10820n, some of the phantom codes that the extender uses were in the base remotes RDF, others were not.

Its easier to use RM to build an upgrade that has the additional keys. If you are already using RM, just open your km files in RM and create an RDMU that has the extender buttons.

You can always add keymoves by hand in IR, but this gets tedious if you use the same upgrade in several remotes.

I never knew that RM could open a KM file. My assumption about KM not using RDF files was correct though. I am good to go for now. I will get back to you on the PS3 adapter protocol when I have everything else ironed out. Thank you very much!

I've changed the RDF to indicate that this is Extender Version A and have moved it from the diagnosis area into Extender area.

I'd like to especially thank jgfarrell (John) for all the preliminary error reports and systematic testing.

Hi Vicky

Thanks for the hat tip and also thanks again for sharing your work with us.

W-a-a-a-y back in the Commodore 64 days I tinkered around quite a bit with 6502 assembly language so I have some idea of the time and effort that goes into something like this.

John

Vicky, I noticed that, in writing macros, "Shift-phantom3" shows up as "Xshift-Key0," and "Shift-phantom4" becomes "Xshift-Power." Is that normal for this 10820N extender?

jetstar52 wrote:Vicky, I noticed that, in writing macros, "Shift-phantom3" shows up as "Xshift-Key0," and "Shift-phantom4" becomes "Xshift-Power." Is that normal for this 10820N extender?

Hi Jetstar, you'll find that you can't assign anything to the Shift-Phantom3. It won't take a keymove or a macro. I'm actually surprised it will let you use the Shift-Phantom3 in a macro. If you check the 10820N keyset document that came with the extender you'll see that you can't shift the those Phantom keys, although I should have allowed phantom 3 to be shifted, that was an oversight on my part.

The first thing I do when I write an extender is make a keycode chart to make sure that there are not conflicts, and as you have discovered if you shift the keys that are above 40, you get conflicts with the xshifts.

If you need more phantoms I can add them to the RDF. You'll see that I have room for at least 15 more unshiftable Phantom codes.

If you check the 10820N keyset document that came with the extender

That's a BIG "if..."

OK, I can avoid the keys not on the keyset. Thanks again for all your help!

Well I made a keyset code, and then found that the base RDF had some different values and so mine are not coordinated. I just changed my rdf so that I have all the phantoms that I intended.

Do you need more than 10 phantoms?

I think 10 should be plenty. Thanks so much! Is the new RDF in the extender file?