JP1 Remotes

chico_woodhill · Joined: 05 Oct 2003 Posts: 52

Hi - True beginner here.

I have a Fujitsu plasma TV. With an RS-2116 I can get most of the functions to work using the built-in Fujitsu TV device, but the on/off key only turns the TV off. I can't turn it on with the button.

The 2116 correctly learns the on/off code from the Fujitsu remote but, alas, not onto the Power button.

Furthermore, using IR to determine the protocol/code tells me it's a Fujitsu protocol, which KM apparently doesn't support. How might I proceed with this to get a properly working power button?

Relevant Info:

Built in setup code: 0683 (RS-2116)

Learned Code info from IR:
Protocol = Fujitsu Dev=112 OBC=0 Hex=FF EFC=181

The learned code starts with (+3280 -1630), then repeats (+420 -404) with an occasional (-1228) thrown in.

Thanks,

Jay (chico_woodhill)

Mark Pierson · Posted: Thu Jan 22, 2004 8:48 pm Post subject:

In KM, I believe that the Sharp DVD protocol is the same as Fujitsui.

However, for just that single command, you can create a key move in IR.

Bound Dev = TV
Bound key = Power
Device Type = TV
Setup Code = 0683
EFC/Hex Cmd = DF 78 (Hex Cmd radio button selected)
_________________
Mark

chico_woodhill · Joined: 05 Oct 2003 Posts: 52

No luck.

I created the the key move in IR, but the power key has no effect on the TV.

I also tried using the Sharp DVD protocol (stored code 0630) but none of the keys have any effect on my Fujitsu TV (PDS4203).

Any ideas?

May I ask how you got the EFC/Hex Cmd = DF 78? Was it from the info I posted or from a separate source? How does that relate to the learned data stream as viewed in IR?

The Robman · Posted: Fri Jan 23, 2004 4:40 pm Post subject:

Hey Chico,
I would recommend that you try hex code "DE FF" for the "Power" function, and "DE 7F" for the "Power On" discrete code. Just FYI, the hex code assigned to the power button is "DE BF" which is obviously the discrete off code.
_________________
Rob
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help!

chico_woodhill · Joined: 05 Oct 2003 Posts: 52

Thanks Rob. I'm out of town right now but I'll try it when I get back.

Jay (Chico)

chico_woodhill · Joined: 05 Oct 2003 Posts: 52

gjarboni · Posted: Thu Jan 29, 2004 1:33 am Post subject:

johnsfine · Posted: Thu Jan 29, 2004 6:57 am Post subject:

The Robman · Posted: Thu Jan 29, 2004 11:18 am Post subject:

chico_woodhill · Joined: 05 Oct 2003 Posts: 52

Thank you all!

The Robman · Posted: Thu Jan 29, 2004 1:48 pm Post subject:

The Robman · Posted: Thu Jan 29, 2004 2:28 pm Post subject:

OK, I did some research and found this thread where Jon defines the Fujitsu format, as follows:

{38k,400}<1,-1|1,-3>(8,-4,20:8,99:8,0:8,D:8,S:8,F:8,1,-110)+

Breaking out the important parts, we get...

20:8, (which in LSB-COMP hex is D7)
99:8, (which in LSB-COMP hex is 39)
0:8, (which in LSB-COMP hex is FF)
D:8,
S:8,
F:8

The fixed data for the TV/0683 code is "03 D7 39 FF DE". The first byte is a control parm used by the executor can can be ignored for this example. As you can see the next 3 bytes of the fixed data matches the first three parts of the Fujitsu protocol as defined by Jon.

The next 2 bytes of Fujitsu are the device and sub-device codes. The device code is part of the fixed data, and is hex value DE (decimal 132), and the unit code is the 1st byte of the variable data, and is also DE.

So, based on this, I would have expected the learned signals to be displayed in IR.exe as using the Fujitsu protocol, with a device code of 132 and a sub-device code of 132. Whereas what you found was device 112 and no sub-device, which doesn't jive with the data. So, either you made a typo or there's a problem with DecodeIR.
_________________
Rob
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help!

chico_woodhill · Joined: 05 Oct 2003 Posts: 52

OK, plenty to digest here!

I already speak hex and binary and did assembly programming in the 70's and 80's, so I have the background (hopefully) to grasp this. But it's the little bits and pieces that only come together only after multiple questions and answers that cause the whole picture to start to coalesce.

Thanks for the responses. I'll sit down with a piece of paper and my hex calculator and try to figure out what you've all told me. Apologies in advance for the inevitable upcoming questions....

Chico

The Robman · Posted: Thu Jan 29, 2004 4:55 pm Post subject:

Instead of using a hex calculator, I would recommend using Excel.

To convert a decimal number (in cell A1) into binary, you would enter

=DEC2BIN(A1,8)

Let's say that the protocol in question is LSB, you will want to reverse the order of those binary bits, which you can do like this...

=mid(b1,8,1)&mid(b1,7,1)&mid(b1,6,1)&mid(b1,5,1)&mid(b1,4,1)&mid(b1,3,1)&mid(b1,2,1)&mid(b1,1,1)

Now, if you want to convert that binary string back into hex, you'd do this...

=bin2hex(c1,2)

If the protocol is LSB-COMP, you should comp the decimal number by subtracting it from 255 before you convert it to binary, like this...

=DEC2BIN(255-A1,8)

If you find yourself looking at a bunch of hex codes for buttons and you have no idea whether the signal is LSB or MSB or whether it's comp'd. Enter the hex code in one column in Excel and in the next column convert it to binary, then look for patterns. It's always a good idea to start with the numeric buttons if possible as these are often in ascending OBC secquence.

Btw, I think this thread has gotten WAY too advanced for the Beginners forum, so I'm gonna move it.
_________________
Rob
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help!

johnsfine · Posted: Thu Jan 29, 2004 5:29 pm Post subject: