Page 1 of 2
IO-DATA cable box
Posted: Wed Oct 08, 2008 12:04 pm
by pacneed
Hi, recently I got a URC8910 and a JP1 cable and tried to analyze IO-DATA's cable box (similar to the one slingbox currently supports like IO DATA's "KD300" or "ST200") to control by slingbox, but using IR tool gave me such information as follows

:
protocol device sub-device OBC Misc
Gap-582-1703-40? 128 232 50 80.E8.12.0.32
Gap-582-1703-40? 84 232 84 80.E8.12.0.54
Gap-582-1703-40? 99 232 99 80.E8.12.40.63
Gap-582-1703-40? 115 232 115 80.E8.12.50.73
I have read as many comments in the forum as I could and came to understand that Gap-xxx.... means "unsupported protocol " by IR tool right now and hence PB is to be used to create some info for protocols.ini.
So would you please someone help me doing it? What do I need to do first?
Thank you.
http://www.hifi-remote.com/forums/dload ... le_id=5831
Posted: Wed Oct 08, 2008 1:49 pm
by Capn Trips
While you wait for someone to help you out, you can give it a try yourself using
protocol builder. There is a
guide for using PB with simple protocols which yours actually appears to be.
Of course, I'll bet that Rob has already prepared you an upgrade while I've been typing this.
Posted: Wed Oct 08, 2008 4:08 pm
by The Robman
Does this remote only have 6 buttons? If there are more buttons that you didn't learn, please learn a complete set of buttons and post the file(s).
Posted: Wed Oct 08, 2008 6:14 pm
by pacneed
Okay, Capn. I will try it. Thanks!
Hi Rob, I uploaded the file with more learned buttons. Thanks!
http://www.hifi-remote.com/forums/dload ... le_id=5833
Posted: Thu Oct 09, 2008 9:35 am
by pacneed
So far, what I understand is as follows. Would someone help me how I can make sure the correct "leadout" and "style"?
freq: 37.735hz
leadin = +9000 -4500
0 pair = +582 -552
1 pair = +582 -1690
leadout= ?
style = ?
I am trying to understand little by little. . .
Thanks.
Posted: Thu Oct 09, 2008 8:52 pm
by The Robman
Here's an upgrade for you to try...
http://www.hifi-remote.com/forums/dload ... le_id=5837
Could you please state what the model number of the cable box is, and what the four L1-L4 buttons really are?
Posted: Fri Oct 10, 2008 7:43 am
by pacneed
Thank you very much, Rob! I have checked and it works! (I can change the channels via Slingbox!)
The product is IO-DATA T100, and L1-L4 buttons are something I just pushed some buttons so it could learn more. You are amazing!; thank you very much.

Posted: Fri Oct 10, 2008 8:39 am
by The Robman
pacneed wrote:The L1-L4 buttons are something I just pushed some buttons so it could learn more.
Those buttons have different codes on them than the other buttons, so it appears that they are different buttons than the complete set that you loaded. If they are in fact different buttons, could you tell me what they are so I can include them in the upgrade. If you have forgotten what they are, could you re-learn all the buttons that you didn't include in the main set so I can decode them and include them.
Thanks.
Posted: Fri Oct 10, 2008 11:29 am
by pacneed
Hi Rob, I tried re-learning the buttons again, and I uploaded the codes in the following link.
http://www.hifi-remote.com/forums/dload ... le_id=5841
Thanks!
Posted: Tue Oct 14, 2008 12:44 am
by pacneed
I have been trying to figure out how Rob made this protocol, and I am
getting to see this thing so interesting!
But would please someone help me understand the following?
Upgrade protocol 0 = 01 FF (S3C8+) IOData (PB v4.00)
44 8C 32 8B 12 CF 4D 08 08 01 21 01 06 01 21 03
31 D4 FD 11 A7 08 B7 8D 01 46
End
1) Looking at the data of the above protocol in the protocol-builder,
I see the signal times,
'1'Burst on 578, off 564
'0'Burst on 578, off 1674
but when I see the learned signals in the IRTool, the signal times are
+582 -552 or +550-574 for "1",
and +582 -1690 or +550 -1700 for "0".
How ca I get the number like "578"? Is it something like "somewhere
between"?
2) How can I find out what "lead-in style" and "lead-out" styles are?
Thank you.
Posted: Tue Oct 14, 2008 7:59 am
by The Robman
The timings are approximate, there doesn't need to be an exact match. The timing and structure of your signals is very similar to the NEC1 protocol, so I used an NEC1 file as a starting point and then just adjusted things to match the structure of your signals.
Posted: Tue Oct 14, 2008 7:14 pm
by pacneed
Okay, Rob. I will study NEC1 protocol. Thank you for your help!
Posted: Wed Dec 24, 2008 11:04 am
by pacneed
It's kinda late to ask, but I do want to clarify one thing about this protocol. Please help!
Upgrade protocol 0 = 01 FF (S3C8+) IOData (PB v4.00)
44 8C 32 8B 12 CF 4D 08 08 01 21 01 06 01 21 03
31 D4 FD 11 A7 08 B7 8D 01 46
End
My question is:
In the upgrade you made it states,
['1' Burst] ON (uSec): 578
OFF (uSec): 564
['0' Burst] ON (uSec): 578
OFF (uSec): 1674
Taking the general concept that "zero pair will have smaller times than the one pair", I thought "578" "1674" pair was 1.
So, how did you find out 0 pair was "578" "1674"?
Thanks.
Posted: Wed Dec 24, 2008 11:37 am
by The Robman
The polarity of a signal is subjective, so it doesn't actually matter which whether you get the 1/0 thing backwards. I agree that the long gap pairs are 1 and the short gap pairs are 0, when looking at an NEC signal, but like I said earlier, I grabbed an existing PB file for the NEC1 signal and built the new executor based on that. UEI is quite consistent in programming their executors with the 1s and 0s reversed (we call that "COMP") and the PB file that I grabbed was based on a UEI executor.
When you're entering the data into KM, if you're calculating the OBCs based on the 1s having the long gap, and you know that the executor is written with the 1s having the short gap, you would need to select one of the COMP styles. In this case, as the signal is LSB, you would select LSB-COMP as the style.
Posted: Wed Dec 24, 2008 12:47 pm
by pacneed
Thank you very much for your quick reply and the clarification!
Please let me clarify one more thing.
Only does the "second command code" seem NOT to be "COMP" when putting the values in RM. How did you firgure out about it?
Thank you.