I'm trying, without success, to build a remote for the Humax-JC 4100 which uses this protocol. A couple of issues:
1. It requires a lead-out time. Is this just guesswork or is there a way of working it out ?
2. It talks about the value of G, but IRScope does not give me a value for G ?
Clues ?
Kaseikyo-G
Moderator: Moderators
-
vickyg2003
- Site Admin
- Posts: 7109
- Joined: Sat Mar 20, 2004 12:19 pm
- Location: Florida
- Contact:
Re: Kaseikyo-G
For that you look at the quiet time between signals, and divide it by 1000, to get the value closest to 20, 33, 44 or 70.alanrichey wrote:I'm trying, without success, to build a remote for the Humax-JC 4100 which uses this protocol. A couple of issues:
1. It requires a lead-out time. Is this just guesswork or is there a way of working it out ?
I've never seen a G decode. Looks like quite a complicated signal as I read in the protocol notes2. It talks about the value of G, but IRScope does not give me a value for G ?
Clues ?
In the past whenever I don't see a parameter I leave it blank. So if no G value is listed I'd leave it alone, but this is just a case of the blind leading the blind.Use this for a decode of ??Kaseikyo-wx.yz. For example, for a decode of ??Kaseikyo-84.87, device 5.88, OBC=31, G=71, enter 84 as OEM1, 87 as OEM2, 5 as Device, 88 as SubDevice, 31 as OBC, and 71 as G
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.
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.
Al,
First upgrade your copy of DecodeIR.dll to version 2.45. Assuming you're using IRScope, you want the W32 version even if you have 64 bit Windows. So rename DecodeIR245W32.dll to DecodeIR.dll in your IRScope folder. That should give you decodes which include the G parameter. You can either use this decode with your existing protocols.ini, but you'll need to swap the values for OBC and G. Or, replace the Variant=3 Kaseikyo-G entry in protocols.ini with this one. Make sure you're replacing Variant 3 of Kaseikyo-G, and not Variant 1 or Variant 2. In this new entry, the protocol is called just Kaseikyo.
Now, about the lead-out. The 00F8 executor can send 4 different lead-outs. Make sure to not use 33mS, because that one sends only 40 bits instead of the normal 48 bits! It definitely will not work. All of the other 3 lead-out times are used in UEI executors, so follow Vicky's approach to find the closes fit.
First upgrade your copy of DecodeIR.dll to version 2.45. Assuming you're using IRScope, you want the W32 version even if you have 64 bit Windows. So rename DecodeIR245W32.dll to DecodeIR.dll in your IRScope folder. That should give you decodes which include the G parameter. You can either use this decode with your existing protocols.ini, but you'll need to swap the values for OBC and G. Or, replace the Variant=3 Kaseikyo-G entry in protocols.ini with this one.
Code: Select all
[Kaseikyo]
PID=00 F8
VariantName=3
DevParms=OEM1=84,OEM2=87,Device:4=5,Sub Device=88,Leadout(mS):20|33 only 40 bits!|70|44=3
DeviceTranslator=Translator(4,8,0) \
Translator(lsb,comp,0,8,8) \
Translator(lsb,comp,1,8,16) \
XorCheck(4,24,15,4) \
Translator(lsb,comp,2,4,28) \
Translator(lsb,comp,3,8,32)
FixedData=03 D5 15 35 E5
CmdParms=OBC=0,G=0
DefaultCmd=00 00
CmdTranslator=Translator(lsb,comp,0,8,0) Translator(lsb,comp,1,8,8)
Notes=Use this for a decode of Kaseikyo-M.N For example, for a decode of Kaseikyo-84.87, device 5.88, OBC=31, G=71, enter 84 as OEM1, 87 as OEM2, \
5 as Device, 88 as SubDevice, 31 as OBC, and 71 as G. 4 Lead-out times are available, but 33mS sends only 40 bits, omitting G from the transmission.
Code.S3C80=45 91 52 8B 18 8F 45 08 08 00 DA 00 C6 00 DA 02 7D 27 70 06 D1 03 40 40 F8 92 68 55 26 20 01 08 03 37 03 0B 37 00 13 56 28 F7 C4 22 1C 8B 0B 37 00 05 C4 26 1C 8B 03 C4 24 1C 8D 01 46
Code.6805-RC16/18=11 24 52 20 18 8F 45 08 08 00 63 69 01 63 3A 13 C2 00 31 25 A8 49 3E 20 86 13 28 2A 9D 3C 58 03 5A 0B 00 5A 22 B6_79 B7_64 B6_7A B7_65 01 5A 0A B6_77 B7_6F B6_78 B7_70 17_7B 03 5A 12 B6_75 B7_6F B6_76 B7_70 20 08 A6 2A B7_6F A6 80 B7_70 CC 01 B2
Code.HCS08=20 1B 23 4A 52 8F 45 08 08 00 D5 00 DE 00 D5 02 95 27 84 06 D0 03 54 41 0C 92 7C 55 3A 3C AC B6 60 A4 03 27 0F A1 01 26 02 17 A2 4A 48 8C 97 9E CE 7A 35 74 CC FF 5C
Code.MAXQ610=34 6D 52 14 10 00 10 00 10 00 30 00 E9 02 81 00 3F 00 CA 04 C9 0A 46 06 02 03 03 01 0B 42 54 06 71 72 73 74 75 76 01 0A 42 56 05 71 72 73 74 75 81 10 04 52 38 40 02 42 54 06 71 72 73 74 75 76 80 04 52 38 42 02 42 54 06 71 72 73 74 75 76Now, about the lead-out. The 00F8 executor can send 4 different lead-outs. Make sure to not use 33mS, because that one sends only 40 bits instead of the normal 48 bits! It definitely will not work. All of the other 3 lead-out times are used in UEI executors, so follow Vicky's approach to find the closes fit.
-
alanrichey
- Expert
- Posts: 3533
- Joined: Mon Mar 24, 2008 7:14 am
- Location: UK/USA
-
alanrichey
- Expert
- Posts: 3533
- Joined: Mon Mar 24, 2008 7:14 am
- Location: UK/USA