JP1 Remotes

Mark Pierson wrote:Hmmm... for 2 commands, you'd be better off using a dummy upgrade (no button assignments) and Key Moves for them in IR, with a full-blown upgrade for the other 27 commands, setup to your liking in KM. That beats the heck out of the DC overhead!

I still need DC for the receiver. And I don't understand what I need that dummy for. Can't I put keymoves onto 27-cmd upgrade?
But this gave me an idea - I created a keymove on these buttons to invoke built-in 0775 device. Guess what - didn't work.

Thanks to everyone involved! I combined your suggestions and made it work.

It was pretty simple - I just compared my layout with built-in and found out that only 3 keys are missing and one is not where I wanted it to be. And they were NOT the two refusing to work properly in upgrade. So I set mode to built-in device and keymoved missing buttons from tiny 3-keys device upgrade. Mistery remains unsolved, but remote works.

Just one more question for now. What is the difference between EFC and Hex cmd in IR's keymover tab? I could only make it work as Hex cmd. If I put EFC in there and push the button the LED goes on for about 10 sec and then all the settings in the remote (e.g. setup codes) become messed up.

wwwoholic wrote:Just one more question for now. What is the difference between EFC and Hex cmd in IR's keymover tab? I could only make it work as Hex cmd. If I put EFC in there and push the button the LED goes on for about 10 sec and then all the settings in the remote (e.g. setup codes) become messed up.

Is it possible the protocol being used was a 2-byte protocol? If that is
the case, you currently need to enter as HEX the 2-byte value instead
of the EFC.

sfhub wrote:Is it possible the protocol being used was a 2-byte protocol? If that is
the case, you currently need to enter as HEX the 2-byte value instead
of the EFC.

Yeah, that's the case.

Hi,
I have the following situation, it's an example of two learned buttons:
1 SAT power Nokia 13 80 8 08 082
Nokia 53 64 32 20 019
Nokia 80 8 12 0C 050

4 SAT select Nokia 13 80 8 08 082
Nokia 53 64 33 21 011
Nokia 80 8 92 5C 176

The rest are similar, they always the first two lines (one or the other) and obviously, last line describes the real EFC of the key.

I'm trying to create a Device combiner on KM with the following parameters:

00 ED 0D 50 08 35 40 20 50 08 0 x
00 ED 0D 50 08 35 40 21 50 08 1 x

And then on Functions, assign the EFCs 050 to protocol 0x and 176 to protocol 1x.

Am I right?
or
Did I make a mistake generating the Fixed Data?

I promise to leave the GalaxisSAT KM file if somebody help me. It's the last device I have not working with my URC9910.

Regards.

jjfuertes wrote:I'm trying to create a Device combiner on KM with the following parameters:

00 ED, 0D 50 08 35 40 20 50 08, 0 x
00 ED, 0D 50 08 35 40 21 50 08, 1 x

I don't know any details regarding the Nokia protocol, but I don't think you can set this up with the Device Combiner.

Even if you could, I can't seem to figure out how you came up with the above data. The Nokia protocol (00 ED) uses only 2 bytes of Fixed Data, but you're showing 8, which is obviously not correct.

Mark,

I created the fixed data with the real fixed data for the devices plus the hex code of the EFC.

That's incorrect. The Device Combiner only needs the PID and the Fixed Data to be entered in the table on the Setup sheet.

As I said, I don't think you can use the DC for this anyway...