JP1 Remotes

Rob knows what he is talking about here, so follow his advice. 8)

I did indeed - and it worked! :D

I didn't even need to make a second upgrade - I copied the colour keys from the built-in setup code CBL/1068.

These "key copy" keymoves should be useful for a few other things too.

Thanks for ...

Yeah sorry, I wanted to keep it brief and not bore everyone with the background that I didn't think would be necessary (and I didn't realise the key moves issue was caused by the protocol). Thanks for putting up the link to the upgrade file too, I should have thought of that.

I considered other ...

Ok I'd better explain what I'm trying to do or this won't make much sense...

I have a Pace NTL cable box which is already supported as standard by the Kameleon, using setup code 1068. This code gets a special mention on the OFA website:
http://www.oneforall-int.com/?pag=50&faqitem=21

However, the ...

Just downloaded v9.07 of KM but there's no change. Key Moves Not Allowed, and the colour buttons are greyed out in the Buttons sheet.

So if it's not the remote that doesn't allow key moves, could it be the IR protocol that my device upgrade uses?

I gather it's quite an unusual one - Protocol ID ...

The Key Moves sheet in KM just says "Key Moves Not Allowed" and all the boxes are greyed-out - so I assume that this remote doesn't support key moves?

I have a URC-8206 (Kameleon 6) remote, which I'm trying to build a device upgrade for.

Each of the 6 "device modes" on this remote illuminates a different set of buttons that can have functions assigned to them. There is also a row of 4 coloured buttons (a la Fastext) at the bottom of the remote ...

Resetting the remote with Other/981 fixed it!

And uploading an upgrade via the modem with IRToWav now works perfectly! Nice work!

Here's the entire image that caused the screw-up, as requested.
https://www.hifi-remote.com/forums/dload ... le_id=4199

Thanks again,
J.

Yes I tried the 980 reset, no effect, I will try 981 this evening and will upload the wav and IR image that caused the problems.

Thanks yet again for the update! It looks like it might work now...

However, while waiting for that update, I had a go at uploading a complete image to the remote using the previous version of IRToWav. But it's killed my remote!!! :(

Now, in every device mode, the buttons are all mixed up... so e ...

Sounds promising but I'm now back to the unsupported version error that I was getting before...

Alain, thanks (again!) for updating IRtoWav. The new version solves the error message, so we are definitely making progress! It successfully generates a wav file when run from either the command line or from Export To Wav in IR.EXE.

However, I still can't get the upgrade to work. The remote now ...

Everything is set up as described in the thread above but the error message mentioned in there is different to the one I'm getting.

I'll have a go at running it on my work PC...

Having tried a few more things, I now think that I didn't manage to generate a new WAV file at all - I think that when I used the "Export To Wav" option from IR.EXE, it was just re-naming the existing upgrade.wav file to the new filename I supplied.

I also found that from the command line, I get ...

Ok, I've finally tried the new version of IRToWav but am still having problems.

If I run it from the command line, I get the following error:

Exception in thread "main" java.lang.UnsupportedClassVersionError: IRToWav (Unsupported major.minor version 49.0)
at java.lang.ClassLoader.defineClass0 ...

Thanks for that, I will try again with "1021" for the signature. (How do you find this out by the way??)

Seems a shame that IRToWav doesn't support this remote, I'm sure it would only take a minor tweak to fix this limitation (hint to the author! :wink: )...

edit: WOW!!! The fix appeared as I was ...