There is an instruction AA 80 that does ORA #80h in the protocol. This just ORs 80h to the device upgrade hex byte(i.e. 07 becomes 87). It might be easier to just change the instruction to AA 00 and then modify the hex bytes to be 87, 86. You can then add in other hex bytes like 47,46 for Plug2; C7,C6 for Plug3; 27,26 for Plug4. The top nibble value is from reversing the bits in the Plug#(0011 -> 1100, 0101 -> 1010).

now i have two devices attached and it works fine!
thank you for your help!

If I understand it right, with the Protocol i could use 15 Devices now.
to use more devices I must make a new Protocol as example with "AA 01" (Range is AA 00 to AA FF)
so I could max use 255 Devices (reminds me of IP Protocol)
are I'm right?

the harder part (for me to understand) is to make new Device Upgrade Codes,
FD 00 => this is the Protocol
E1 00 => ? I think this must be something for the buttons on the remote
47 => Device X on
46 => Device X off

If you want to use more than 15 devices, you can adjust the fixed data in the device upgrade.

FD = Protocol ID
00 = number table (not used)
E1 = Bitmap of what buttons on remote are defined. first bit is Numbers. 2nd bit is Volume keys, next is Channel keys. I used all keys so top nibble is E.
00 = Fixed Data. For next device upgrade, use 80(Auto/1001). Next is 40(Auto/1002) and then C0, 20, A0, 60, E0, 10. I think number is similar to the plug# address.

You can use up to 15 plug #s. Just put the hex data in top nibble of byte. Plug2 is 4 so 47 ON, 46 OFF. Normally you use RM or KM to create device upgrade codes which assigns functions codes to each button.

Your old remote was a JP1.2 remote and needed a protocol formatted for the Motorola machine language, this remote is a JP1.3 remote and needs a protocol that has been written in the Samsung language.

I didn't see a link to your upgrade in this thread. Could you post a link to your upgrade so that we can take a look at what's different?_________________Remember to provide feedback to let us know how the problem was solved and share your upgrades.

Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.

Hey Binky, I noticed that you did some modifications to this protocol, do you happen to have any commented source for this protocol?

Also is there a list of function names so we can create a proper KM file for this upgrade?_________________Remember to provide feedback to let us know how the problem was solved and share your upgrades.

Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.

Normally I work on protocols for the HCS08 processor, but I've downloaded this and will have a look. If it falls off my radar again, don't hesitate to bump the thread.

Oh and if I do get it running, you are going to "owe" me. I want an explanation of "asphalt dancer" because it conjers up all sorts of images _________________Remember to provide feedback to let us know how the problem was solved and share your upgrades.

Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.

Somehow I have not discovered this thread until now. Actually, in 2008 I wrote an article in a German forum on this. There I show that it is actually compatible with the, in Europe, fairly widespread RF controlled switches from Intertechno. These are also available in Europe using several other names, Düwi,... The Intertechno stuff (with the exception of the most recent products) has a house code A to P, and a device address 1 to 16 (just like X10...). They have a 16 position switch for the house code, and one for the device address. They have only the two commands power_on and power_off; these are also used when dimming. The "Home Command Control Center" is nothing else but an IR->RF converter, transforming 950nm light into 433MHz radio, preserving the 36 kHz modulation. It is functionally equivalent to half of a IR extension using RF, like the well known Marmitek "pyramides".

The "Home control receiver" does not use mechanical rotary switches, but electronic memory (flash?). The "learning procedure" is nothing but assigning house number and device address.

Newer Intertechno equipment uses a more modern selection than the really quite anacronistic 16-housenumbers-16 deviceaddresses scheme.

The 16 different "devices" in, e.g. the URC-7781 are for the 16 different house numbers. 2200 for "A", 2201 for "B", and so on.

I based my assumptions on the fact that there's a URC-8305 Kameleon in the pic and when I opened the manual for that remote it explicitly says that it controls the OFA light kit and the only setup code available in that particular remote is 0167.

In case anyone is still curious about this mystery, it looks like the One For All HC-8000 and HC-8010 uses a kind of a funky X-10 variant where are listed as invalid. Whereas the HC-8030 isn't even recognized by IR Scope.

EDIT: Opps, never mind. Somehow I missed that this thread had multiple pages. Looks like Vicky and Blinky already created an upgrade for the HC-80xx series. I'm probably just opening up a can of worms with the HC-8300._________________Remotes; JP1.2: Comcast URC-1067, JP1.3: Insignia NS-RC02U-10A, JP1.4 OARI06G, JP2.1: Cox URC-8820-MOTO (still trying to figure out how to make them self-aware.)