View previous topic :: View next topic |
Author |
Message |
chuliu
Joined: 04 Dec 2010 Posts: 443 Location: Hong Kong |
Posted: Fri Dec 21, 2012 2:07 am Post subject: Need bin file for sharp dv-hrd30 |
|
|
I need the bin file.
When I used my logitech remote, I seem to find a match.
I don't have the necessary gadget( usb ir widget or jp1 remote) on hand.
I would appreciate if someone can generate the file for me.
Thanks. |
|
Back to top |
|
|
alanrichey Expert
Joined: 24 Mar 2008 Posts: 3529 Location: UK/USA |
Posted: Fri Dec 21, 2012 7:33 am Post subject: |
|
|
http://www.hifi-remote.com/forums/dload.php?action=file&file_id=11596
This is probably the most complex device I have seen, with over 70 functions. As you will see from the instructions I have made my best guess on how to allocate the Custom buttons. The following functions are unmapped, so if you want to swap any of them let me know:
BS-Digital
CS-Digital
TV/Radio
HDD
BD
On Screen
Data
C-Code
Backlight
Angle
Audio
Al |
|
Back to top |
|
|
chuliu
Joined: 04 Dec 2010 Posts: 443 Location: Hong Kong |
Posted: Fri Dec 21, 2012 8:03 am Post subject: |
|
|
Thanks. |
|
Back to top |
|
|
chuliu
Joined: 04 Dec 2010 Posts: 443 Location: Hong Kong |
Posted: Mon Dec 24, 2012 10:46 am Post subject: |
|
|
hi alan
If possible can I have the rmdu file?
None of the buttons actually control the device correctly.
If I remember correctly, this remote uses Kaseikyo protocol and we need to specify both device code and sub device code for it to work.
This was when I was in my home town, Taipei, last month, when I had the gadget on hands and actually made the bin file for this remote.
I didn't save it.
I don't know if you used Kaseikyo and both device and sub device code. |
|
Back to top |
|
|
alanrichey Expert
Joined: 24 Mar 2008 Posts: 3529 Location: UK/USA |
|
Back to top |
|
|
chuliu
Joined: 04 Dec 2010 Posts: 443 Location: Hong Kong |
Posted: Mon Dec 24, 2012 11:38 am Post subject: |
|
|
Hi Alan.
You might have misused fijitsu protocol instead of Kaseikyo.
Also, you might have pasted the OBC code into sub dev column in the function tab.
I will try to fix it. |
|
Back to top |
|
|
alanrichey Expert
Joined: 24 Mar 2008 Posts: 3529 Location: UK/USA |
Posted: Mon Dec 24, 2012 11:57 am Post subject: |
|
|
Sorry wrong URL, should be:
http://www.hifi-remote.com/forums/dload.php?action=file&file_id=11596
Have no idea what you mean by your comments. As I said, I just installed it on my Harmony and learned the codes. Comes up with SharpDVD and 8:48 as the device/subdevice. I never did anything with Fijitsu or Kaseikyo protocols and there is no sub-device column in the functions. Sounds to me as though you tried importing the BIN file and it sisn't import properly |
|
Back to top |
|
|
3FG Expert
Joined: 19 May 2009 Posts: 3367
|
Posted: Mon Dec 24, 2012 12:32 pm Post subject: |
|
|
chului,
At one time it was necessary to use the Kaseikyo protocol entry in RM to construct SharpDVD. Perhaps you're thinking that Al used that method. However, newer versions of protocols.ini specifically have a SharpDVD entry, which removes any possibility of mixing up subdevice and OBC. |
|
Back to top |
|
|
chuliu
Joined: 04 Dec 2010 Posts: 443 Location: Hong Kong |
Posted: Mon Dec 24, 2012 9:16 pm Post subject: |
|
|
Ok. But when I opened the rmdu file, it had Fujitsu as the protocol. Is it normal? Also, if you take a look at the functions tab in the rm, several functions have the same OBC code, I don't know I f that is correct. However, the sub dev code in function tab seem to be unique to each others.
When I uploaded the bin file to slingbox, it didn't work either.
I opened up rm, with the protocol at Fujitsu, copied the function names and Sub dev code, opened a new rm instance, paste them into name and obc in the function tab, then export the bin. And the bin file is ok.
Maybe I am using a older version of rm? Not too sure. |
|
Back to top |
|
|
3FG Expert
Joined: 19 May 2009 Posts: 3367
|
Posted: Mon Dec 24, 2012 9:27 pm Post subject: |
|
|
Both SharpDVD and Fujitsu use the same 00F8 executor. Older versions of RMIR had a small bug that sometimes caused mis-identification of such protocols which share an executor. Perhaps you're seeing that. The current released version is 2.02. |
|
Back to top |
|
|
alanrichey Expert
Joined: 24 Mar 2008 Posts: 3529 Location: UK/USA |
Posted: Mon Dec 24, 2012 9:53 pm Post subject: |
|
|
This is the SharpDVD entry in my Protocols.ini. It does sound as though you are using an out-of-date version:
[Sharp DVD]
PID=00 F8
DevParms=Main Device,Sub Device
DeviceTranslator=Translator(lsb,comp,0,8,24) Translator(lsb,comp,1,8,32)
FixedData=00 aa a5 ff ff
DefaultCmd=00 00
CmdParms=OBC=0
CmdTranslator=Translator(lsb,comp) SharpDVDTranslator()
Notes=The SharpDVD protocol is equivalent to Kaseikyo with OEM1=170 and OEM2=90. The only legal device numbers are 15, 31, 47, 63....16*n+15, n=0 to 15
#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 0E 37 00 1C 56 28 F7 E4 22 1C E4 23 1D 8B 11 37 00 08 E4 26 1C E4 27 1D 8B 06 E4 24 1C E4 25 1D 8D 01 46
Code.740=0B 1A 52 80 10 E1 72 10 08 08 01 7F 02 94 19 10 80 03 2B 00 08 07 5D 06 E6 5B E6 69 80 0A E6 5B A9 5F 85 71 A9 68 85 72 4C 00 FF
#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
[Sharp DVD]
PID=00 F8
VariantName=2
DevParms=Main Device:8=143,Sub Device:8=48
DeviceTranslator=Translator(lsb,comp,0,4,28,4) Translator(lsb,comp,0,8,24)
FixedData=03 AA A5 0F FF
DefaultCmd=00 00
CmdParms=OBC=0
CmdTranslator=Translator(lsb,comp) SharpDVDTranslator()
Notes=The SharpDVD protocol is equivalent to Kaseikyo with OEM1=170 and OEM2=90. The only legal device numbers are 15, 31, 47, 63....16*n+15, n=0 to 15
#Code.S3C80=43 8B 52 8B 16 8F 45 08 08 00 CB 00 C4 00 CB 02 6A 27 70 06 8F 03 3D 40 F8 8C 8C 20 01 76 03 01 6B 09 E4 22 1C E4 23 1D 56 28 F7 76 03 02 6B 22 E4 24 1C E4 25 1D E6 29 44 E6 0C E8 F6 01 46 F6 01 0A FB 0D 00 0C EB F4 C6 3E 00 00 B0 4A F6 01 0A AF 8D 01 46
[Sharp DVD]
PID=00 F8
VariantName=3
DevParms=Main Device:4=8,Sub Device:8=48
DeviceTranslator=Translator(lsb,comp,0,4,28,4) Translator(lsb,comp,1,8,32)
FixedData=03 AA A5 0F FF
DefaultCmd=00 00
CmdParms=OBC=0
CmdTranslator=Translator(lsb,comp) SharpDVDTranslator()
Notes=The SharpDVD protocol is equivalent to Kaseikyo with OEM1=170 and OEM2=90.
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 |
|
Back to top |
|
|
3FG Expert
Joined: 19 May 2009 Posts: 3367
|
Posted: Mon Dec 24, 2012 11:47 pm Post subject: |
|
|
Al,
RemoteMaster.jar itself may be out of date; that's where we fixed the bug. I don't think the Fujitsu entry in protocols.ini has changed recently. But of course downloading RMIR 2.02 will also get the latest protocols.ini. |
|
Back to top |
|
|
alanrichey Expert
Joined: 24 Mar 2008 Posts: 3529 Location: UK/USA |
Posted: Sat Dec 29, 2012 10:11 am Post subject: |
|
|
Where do we stand on this one ? Can I delete it off my 'ToDo' list ? |
|
Back to top |
|
|
chuliu
Joined: 04 Dec 2010 Posts: 443 Location: Hong Kong |
Posted: Fri Feb 08, 2013 1:27 pm Post subject: |
|
|
Hi, sorry that I replied to thread so late. But just want to understand more about rm and rmir. The procedure I use to construct the rmdu or bin is: I learn the remote with jp1 remote, then download the learned signal from jp1 with ir.exe, I then mark down the function name, obc code, as well as protocol, device code, and sub device code if any. Then enter them into remotemaster, matching function with buttons. And that is it.
Is there any change to the procedure? When you say the newer remotemaster has protocol.ini and thus won't cause confusion and such, what does it mean? Does it mean one can just select the protocol and no need to worry about the device code and sub device code any more?
thanks. |
|
Back to top |
|
|
chuliu
Joined: 04 Dec 2010 Posts: 443 Location: Hong Kong |
Posted: Fri Feb 08, 2013 1:29 pm Post subject: |
|
|
and thanks alan, the rmdu file and bin in question are all good now. |
|
Back to top |
|
|
|