Page 1 of 2

My first upgrade

Posted: Wed Jan 03, 2007 10:42 pm
by roy67ss
Hi people,

Finally got around to trying to upgrade my URC10820. 4 days ago I started reading and using RM, IR, and KM. I succesfully created my first upgrade file. Here is a link https://www.hifi-remote.com/forums/dload ... le_id=4045

One of you experts might want to check it out and let me know if I screwed up anything. It works good so I think it's OK.

Xmas showed up 2 more new units to try and create upgrades for - a Pioneer DVR-640H-S and a Yamaha HTR 5850. I think these will be a little trickier to code, from what I've read.

I want to thank all you guys working on these programs.

It will be nice when map and jpg files are done for this 10820 remote for RM images folder.[/url]

Posted: Thu Jan 04, 2007 7:41 am
by The Robman
Did you create the upgrade from scratch? If so, you probably didn't notice that there are a couple of upgrades for this unit already in the file section that you could have used.

Posted: Thu Jan 04, 2007 9:01 am
by roy67ss
I made it from scratch, Rob. I had the 10820 buttons learned to what made sense for me for several months. And, I thought it would be a good place to start.

I have downloaded a couple of files for the other 2 units that may provide a stsrting point for them. The thing is that these units are brand new and have more options than any allready out there.

One question, are the upgrade files permanently stored in the remote other than being editable?

Roy

Posted: Thu Jan 04, 2007 9:28 am
by vickyg2003
It takes an active write to remove an upgrade from memory. The upgrade will remain in the EEPROM even if the batteries are removed.

To remove the upgrade you can upload an IR file that does not contain the upgrade, or you could do a 981 reset.

Posted: Thu Jan 04, 2007 9:29 am
by The Robman
roy67ss wrote:One question, are the upgrade files permanently stored in the remote other than being editable?
That depends on what you mean by "permanent". The upgrade resides in the fake "EEPROM" area of the flash memory, it will stay there forever (even if you remove the batteries) as long as you don't do anything to cause it to be removed, such as doing a 981 reset.

Posted: Thu Jan 04, 2007 9:30 am
by johnsfine
roy67ss wrote:One question, are the upgrade files permanently stored in the remote other than being editable?
Depends on the meaning of the word "permanently".

The upgrades are not disturbed by leaving the remote without batteries (none of the settings are).

The upgrades are removed by a 981 reset performed on the remote itself (along with all the settings).

The upgrades are not disturbed by a 980 reset (which clears most other settings).

The upgrades are totally replaced by whatever is in the current .ir file every time you upload via your jp1.2 cable.

Posted: Thu Jan 04, 2007 2:57 pm
by roy67ss
The upgrades are totally replaced by whatever is in the current .ir file every time you upload via your jp1.2 cable.
That is what I thought and no doubt would have discovered when uploading my next upgrade.

Is anyone working on the map/jpg files for this remote for RM images folder?

Thanks for the replies,
Roy

Posted: Thu Jan 04, 2007 3:04 pm
by The Robman
Great minds think alike, eh? Notice how John and I wrote almost identical replies at the same time. 8)

Posted: Thu Jan 04, 2007 4:10 pm
by kupakai
roy67ss wrote:Is anyone working on the map/jpg files for this remote for RM images folder?

Thanks for the replies,
Roy
It's already in

https://www.hifi-remote.com/forums/dload ... le_id=3508

If you already have the latest RDF from the file section, though, don't replace it with the one in here.

Posted: Thu Jan 04, 2007 4:54 pm
by Mark Pierson
The Robman wrote:Great minds think alike, eh? Notice how John and I wrote almost identical replies at the same time.
And Vicky beat you both to the punch! :eek:

Way to go Vick!!! :wink:

Posted: Thu Jan 04, 2007 5:20 pm
by The Robman
You go girl! :lol:

Posted: Thu Jan 04, 2007 6:17 pm
by roy67ss
kupakai - I must have missed that one when I was searching for the most recent files, which I think I have.

Thanks, that should stop the warning I get when RM can't find those files.

I am using this https://www.hifi-remote.com/forums/dload ... le_id=3801 rdf file. It was the newest one I could find.

I am curious about why the L1-L3 keys are @function keys. I thought they were the same as any other 'normal' key. I understand why the M1-M3 keys are considered @functions. And, I'll have to do some reading about those 'phantom' buttons.

roy

Posted: Thu Jan 04, 2007 6:53 pm
by The Robman
roy67ss wrote:I am curious about why the L1-L3 keys are @function keys. I thought they were the same as any other 'normal' key. I understand why the M1-M3 keys are considered @functions. And, I'll have to do some reading about those 'phantom' buttons.
Buttons labelled with the "@" sign will be programmed as keymoves because they are not part of the keymap for the selected device mode. The L and M buttons will never be programmed as part of a built in setup code as they are intended to be programmed by the end user, using macros or learning.

Posted: Thu Jan 04, 2007 6:56 pm
by vickyg2003
I am curious about why the L1-L3 keys are @function keys. I thought they were the same as any other 'normal' key. I understand why the M1-M3 keys are considered @functions. And, I'll have to do some reading about those 'phantom' buttons.
L1-L4 are never assigned by a device. So they are always assigned using Keymoves, or learning. The Transport keys (VCR) are never assigned in a TV code, so if you were creating a TV setup code these would have an @ too. Does that help?

Posted: Fri Jan 05, 2007 5:04 pm
by roy67ss
I realised that those keys would not be used by any code entered. I just thought the L keys would be used for extra 'normal' buttons learned that aren't on the OFA remote and the M keys were normally reserved for macros. At least the manual sort of leads one that way.

Thanks all for the added clarification.

BTW, I created another file last night for the Pioneer PVR 640H-S that has every original remote key as well as an eject key code that the original didn't have. I'll post it later once all have been checked out.

Roy