JP1 Remotes

1. Device: Magnavox MFX 450
2. Type of device: audio receiver
3. JP1 Remote model: URC-8810B00
4. JP1 user? Yes
5. Still have original remote? yes
6. Checked Yahoo file section? yes
7. Checked Pronto file section yes

I have a somewhat working code, 1189, I just don't know how to get that into keymaster from IR.exe so I can add to it. I don't mind learning the commands I need to extend the upgrade, I just would like to not have to start from scratch.

Thanks

Audio/1189 is a combination of RC5 and RC5x signals. Since you say it's only "somewhat" working, it might not be the best starting point and you might not need RC5x protocol.

So the decision depends on what parts of Audio/1189 work. And also, if you learn a few of the more obscure functions from the original remote and decode with IR.EXE, are any of them RC5x and how many different RC5 device numbers are included.

In Audio/1189, most of the digits seem to be intended to be discrete input select signals rather than real digits. If the original device supports real digits and you want those, an upgrade could easily include them.

The only RC5x signals in Audio/1189 are on the 6 and 9 keys. If those aren't working functions for your device Audio/1189 probably isn't a good starting point.

The basic functions (such as vol, power and arrow keys) are in RC5 device 16, and the 8810 seems to lack any simple RC5 setup code for device 16. But I expect several upgrades are already posted that are better starting points if a simple RC5 device 16 upgrade is where you should be heading.

Okay to be more specific, the volume, mute, channel and balance controls work. The original remote has input buttons that have to be held down to turn on the receiver and switch inputs. I would like those and the surround mode buttons to work, everything else I can live without. The only functions I might use the 6 or 9 keys for are switching inputs

Sorry for my ignorance, but how do I tell between RC5 and 5X signals?

Tommy,
The best approach here would be to follow the normal path of learning all the buttons from the original remote and using that data to create a new upgrade.

IR.exe will do a good job of detecting the signals, regardless of whether they're RC5 or RC5x.

For all the time it's taken you so far trying to use the 1189 code, you could easily have done the learning and created the upgrade by now.

tommyboy22481 wrote: Sorry for my ignorance, but how do I tell between RC5 and 5X signals?

Learn the signal from the original remote.
Download to IR.EXE.
Make sure you have the DecodeIr.dll somewhere that IR.EXE can find it.
Click on the signal within IR's learned signals tab abd it will decode it, including telling you the protocol (RC5 or RC5x and the device number).

If there are no RC5x signals and a limited veriety of RC5 device numbers, then a simple RC5 upgrade will be easiest. Otherwise, some combo such as the one Audio/1189 uses is required.

Okay I will do that and let you know if there are any problems. Thanks for the help.

I just scanned my collection of CCF files for matches on the CH+ and CH- commands of Audio/1189 (because matches on its vol commands are too common). I found several files matching that and picked one at random and extracted the following command list

16 ... 13 ... {Mute}
16 ... 15 ... OSD
16 ... 16 ... {Vol+}
16 ... 17 ... {Vol-}
16 ... 22 ... +
16 ... 23 ... -
16 ... 24 ... +
16 ... 25 ... -
16 ... 29 ... Spkr A / B
16 ... 34 ... S. Direct
16 ... 37 ... Surround Mode
16 ... 38 ... Sleep
16 ... 80 ... `Up_Arrow
16 ... 81 ... `Down_Arrow
16 ... 82 ... {Mute}
16 ... 82 ... OK
16 ... 83 ... Exit
16 ... 85 ... `Left_Arrow
16 ... 86 ... `Right_Arrow
17 ... 0 ... 0
17 ... 1 ... 1
17 ... 2 ... 2
17 ... 3 ... 3
17 ... 4 ... 4
17 ... 5 ... 5
17 ... 6 ... 6
17 ... 7 ... 7
17 ... 8 ... 8
17 ... 9 ... 9
17 ... 11 ... Freq. Direct
17 ... 15 ... RDS
17 ... 30 ... Seek `Up_Arrow
17 ... 31 ... Seek `Down_Arrow
17 ... 32 ... {Ch+}
17 ... 33 ... {Ch-}
17 ... 37 ... `E5
17 ... 41 ... Memo
17 ... 43 ... P. Scan
17 ... 45 ... FM
17 ... 46 ... AM
17 ... 63 ... Tuner
17 ... 120 ... PTY

It's all RC5. The first number is device and the second is OBC.
I expect most of those commands will be right for your device, and it shouldn't be too hard to put them into KM and try.

Use learning and decoding for any that are missing or wrong.

A simple RC5 upgrade only supports three halves of device codes, so you could support device 16 for OBCs 0 to 63 and for OBCs 64 to 127 and device 17 for just OBCs 0 to 63. That would leave out PTY from the above list (whatever that is).

If it leaves out a few things you want it's best to patch those in with KeyMoves. If it leaves out a lot you want, it's best to use a combo protocol.

BTW, I think RM's support for RC5 protocol is a little better than KM at guiding a beginner through the issues of three half ranges (as I described above). But the upgrade shouldn't be hard with either.