View previous topic :: View next topic |
Author |
Message |
simonsezdothis
Joined: 23 Nov 2005 Posts: 71 Location: New Zealand |
|
Back to top |
|
|
binky123 Expert
Joined: 14 Feb 2004 Posts: 1292
|
Posted: Sat Feb 02, 2008 12:58 am Post subject: |
|
|
Your CCF hex code seems inconsistent with what was learned in your .IR file. If you look at IR's MISC column it will decode the 4 bytes for you. If you look at the Learned timings data and scroll down, you can see what is considered a 0 or 1 in the pairs.
I entered the first 3 CCF hex data into IRTool and DecodeIR.dll decoded it in a similar way as I have done manually. The data is listed in LSB order so you reverse the bits.
Code: |
KEY "0" AND KEY 2 BOTH SELECT SOURCE 1
Here is the Speakercraft code for Source 1
0000 006C 0000 0022 0159 00AD
0015 0041 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 80 LSB => 01
0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 00 00
0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 00 00
0015 0016 0015 0016 0015 0016 0015 0016 0015 0041 0015 0041 0015 0016 0015 0016 0C LSB => 30
0015 082E
KEY "1" SELECTS SOURCE 8
Here is the Speaker craft code for source 8
0000 006C 0000 0022 0159 00AD
0015 0041 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 80 LSB => 01
0015 0041 0015 0041 0015 0041 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 E0 LSB => 07
0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 00
0015 0041 0015 0041 0015 0041 0015 0016 0015 0041 0015 0041 0015 0016 0015 0016 EC LSB => 37
0015 072B
KEY "3" SELECTS SOURCE 2
Here is the Speaker craft code for source 2
0000 006C 0000 0022 0159 00AD
0015 0041 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 80 LSB => 01
0015 0041 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 80 LSB => 01
0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 00 00
0015 0041 0015 0016 0015 0016 0015 0016 0015 0041 0015 0041 0015 0016 0015 0016 1C LSB => 31
0015 07D8
|
Your .IR file data fit the pattern I listed previously. You should decode all of your CCF hex data and see if you can come up with a pattern.
I think I should make the protocol use 4 variable bytes for each function and you enter the 4 bytes as needed. Thus, no need to search for a pattern among the bytes. |
|
Back to top |
|
|
simonsezdothis
Joined: 23 Nov 2005 Posts: 71 Location: New Zealand |
Posted: Tue Feb 05, 2008 12:34 am Post subject: |
|
|
Hi. I've looked at all the codes I require and have posted a spreadsheet of them here.
http://www.hifi-remote.com/forums/dload.php?action=file&file_id=5373
Re: Inconsistancies
The codes in this spreadsheet are direct from the Speakercraft software. It was these exact codes I used to "Learn" with my URC-8910 in the original .ir file.
I did this by pasting these codes into IRNHelper and using the USBUIRT to transmit the codes.
Thanks again for your help so far ...
PETER |
|
Back to top |
|
|
binky123 Expert
Joined: 14 Feb 2004 Posts: 1292
|
Posted: Tue Feb 05, 2008 1:11 am Post subject: |
|
|
It looks like I should just modify the protocol to accept 4 bytes and you plug in whatever values you want. Your spreadsheet doesn't seem to show a pattern across all values.
Somewhere along the process, it seems to be losing the first byte value of 1. The CCF Hex says it should be there but the signal learned by the 8910 says it is not. The device also responds to these learned IR codes on the 8910 so maybe the device doesn't care? |
|
Back to top |
|
|
simonsezdothis
Joined: 23 Nov 2005 Posts: 71 Location: New Zealand |
Posted: Wed Feb 06, 2008 3:22 pm Post subject: |
|
|
Yes. - If it's possible to just plug in the values required that would suffice, and be easier by the sound of it. |
|
Back to top |
|
|
binky123 Expert
Joined: 14 Feb 2004 Posts: 1292
|
Posted: Thu Feb 07, 2008 12:10 am Post subject: |
|
|
Code: |
Upgrade protocol 0 = 01 55 (S3C8+) Custom Protocol for MZC-88
42 8E 04 8B 12 CC 45 00 08 01 16 01 06 01 16 03
31 D2 F0 11 A6 08 B7 08 03 F6 FF 36 09 03 08 04
F6 FF 36 09 04 08 05 F6 FF 36 09 05 08 06 F6 FF
36 09 06 8D 01 46 60 C0 1C 08 C0 C0 10 07 1A FA
08 07 AF
End
Upgrade Protocol 0 = 01 55 (HCS08) Custom Protocol for MZC-88
20 15 22 48 04 CC 45 00 08 01 16 01 1A 01 16 03
45 D2 F0 11 A6 08 CB B6 60 AD 17 B7 60 B6 61 AD
11 B7 61 B6 62 AD 0B B7 62 B6 63 AD 05 B7 63 CC
FF 5F 43 AE 08 44 39 64 5B FB B6 64 81
End
Upgrade Code 0 = 0C 2B (CBL/1067) MZC-88
55 00 21 01 07 00 37 01 05 00 35
End
|
I used the device upgrade to test so CH+ sends 01 07 00 37 and CH- sends 01 05 00 35. |
|
Back to top |
|
|
simonsezdothis
Joined: 23 Nov 2005 Posts: 71 Location: New Zealand |
Posted: Tue Feb 12, 2008 4:06 pm Post subject: |
|
|
Thanks for all that.
I haven't been able to get to the MZC-88 to test that for the last few days, but the remote certainly sends those numbers.
I've spent ages trying to figure out how to manually insert another button entry on the Raw Data tab. Alas ... I don't understand what I'm looking at here.
I can see where you've put the values for Chan+ Chan- but that's about it.
Should I be doing this here, or modifying the device upgade first somehow with the additional values?
Thanks again for your help to date.
PETER |
|
Back to top |
|
|
binky123 Expert
Joined: 14 Feb 2004 Posts: 1292
|
Posted: Wed Feb 13, 2008 10:31 am Post subject: |
|
|
Usually you create the device upgrade within KM or RM by listing out the functions on the functions sheet You then assign functions to individual buttons. You then take the device upgrade and paste it into IR.exe. The device upgrade format contains a button-bitmap of which buttons you are using(CH+/CH-) followed by the data. |
|
Back to top |
|
|
simonsezdothis
Joined: 23 Nov 2005 Posts: 71 Location: New Zealand |
Posted: Wed Feb 13, 2008 8:37 pm Post subject: |
|
|
Yes ... sorry, but I can't see how to specify the 4 bytes to send in KM or RM. The results from simply entering the OBC were pretty random
http://www.hifi-remote.com/forums/dload.php?action=file&file_id=5405
Could you perhaps mail me a demo RM file with those two codes in so I can see where you have entered the 4 bytes maybe?
I'm not understanding at this point.
I will also be away for a week from tomorrow night and am unsure as to the availability of Net access.
Cheers
PETER |
|
Back to top |
|
|
binky123 Expert
Joined: 14 Feb 2004 Posts: 1292
|
Posted: Thu Feb 14, 2008 11:06 am Post subject: |
|
|
Here are the steps:
Open up RM's protocol.ini and add the following into it:
Code: |
[MZC-88]
PID=01 55
Code.S3C80=42 8E 04 8B 12 CC 45 00 08 01 16 01 06 01 16 03 31 D2 F0 11 A6 08 B7 08 03 F6 FF 36 09 03 08 04 F6 FF 36 09 04 08 05 F6 FF 36 09 05 08 06 F6 FF 36 09 06 8D 01 46 60 C0 1C 08 C0 C0 10 07 1A FA 08 07 AF
Code.HCS08=20 15 22 48 04 CC 45 00 08 01 16 01 1A 01 16 03 45 D2 F0 11 A6 08 CB B6 60 AD 17 B7 60 B6 61 AD 11 B7 61 B6 62 AD 0B B7 62 B6 63 AD 05 B7 63 CC FF 5F 43 AE 08 44 39 64 5B FB B6 64 81
|
Start up RM. Select your remote. Select MZC-88 Protocol Name.
Click on Functions Tabsheet. You should see 4 columns: Byte0 thru Byte3.
You should change the names in each row to match what that function does. I didn't do it. I just used the Channel Up row and entered 1 7 0 55 into the Byte0-Byte3 columns. The Hex Column should show 01 07 00 37.
Do the same for Channel Down: 1 5 0 53. The Hex Column shows 01 05 00 35.
Click on Buttons Tabsheet. Drag the Channel Up function to the Ch+ button. Drag Channel Down function to CH-.
Click on Output Tabsheet and you should see the Device Upgrade and the Protocol Upgrade. |
|
Back to top |
|
|
simonsezdothis
Joined: 23 Nov 2005 Posts: 71 Location: New Zealand |
Posted: Thu Feb 14, 2008 6:30 pm Post subject: |
|
|
Ah Ha! - Great ... now I understand.
OK well I've created all the upgrades I need, but won't be able to test again now until I'm back in town.
Thanks you again for the time you've spent. I'll let you know how I get on next week. I'll leave the uploads in the file section for now until I'm sure it's all working, then I'll clean it up for you and post an upgrade for other users.
Cheers
PETER |
|
Back to top |
|
|
simonsezdothis
Joined: 23 Nov 2005 Posts: 71 Location: New Zealand |
Posted: Tue Feb 26, 2008 3:49 pm Post subject: THANKS |
|
|
Hi.
Thanks heaps for the work you did on this. Everything seems to work well. I'll go and clean up the test files I posted etc ... do you want me to post the upgrade with an explanation of how it works for other users?
Thanks again.
Peter |
|
Back to top |
|
|
|