COSHIP N8606 Cablebox

If you have learned signals that don't get decoded when you look at them in IR.exe, post your file to the Diagnosis Area then post your question here (including a link to the file).

Moderator: Moderators

Post Reply
jkgtw
Posts: 10
Joined: Tue Mar 10, 2009 9:28 pm

COSHIP N8606 Cablebox

Post by jkgtw »

I just got an other cable box, I try use URC-8910 to learning code and it can't recognised protocol.
The cable box modle number is N8606, made by COSHIP.
The protocol is recognised as GAP-574-1396-16? in IR Scope.

Please help me convert to rmdu for the Slingbox.
https://www.hifi-remote.com/forums/dload ... le_id=9095

thanks!
alanrichey
Expert
Posts: 3533
Joined: Mon Mar 24, 2008 7:14 am
Location: UK/USA

Post by alanrichey »

I actually tried to produce a remote for this box some time ago by loading it onto my Harmony Remote. The learns in that case came out as NEC1, Device 1.246.

It was never proven though.
The Robman
Site Owner
Posts: 21944
Joined: Fri Aug 01, 2003 9:37 am
Location: Chicago, IL
Contact:

Post by The Robman »

This isn't NEC1. I've seen a protocol like this before but don't recall which one it was, so I'll probably have to write something new for it later.

Here are the timings:
https://www.hifi-remote.com/forums/dload ... le_id=9097
Rob
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help!
The Robman
Site Owner
Posts: 21944
Joined: Fri Aug 01, 2003 9:37 am
Location: Chicago, IL
Contact:

Post by The Robman »

Here's your RMDU file:
https://www.hifi-remote.com/forums/dload ... le_id=9099

I found the thread on the other protocol that this one reminded me of here:
https://www.hifi-remote.com/forums/viewtopic.php?t=12226

Here's the tech details:
freq: 38khz
bytes: 5
mid frame burst after 24 bits

leadin: +6000 -2000
one: +550 -1100
zero: +550 -550
leadout: +550 -99930
mid-frame burst: +3650 -3650

There's 5 bytes of data where bytes 1, 2 and 4 are fixed. The OBC is byte5 and byte3 is the complement of the OBC.
Rob
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help!
jkgtw
Posts: 10
Joined: Tue Mar 10, 2009 9:28 pm

Post by jkgtw »

Thank you, Rob!
I've tested, seem power button can't work.

any idea?
vickyg2003
Site Admin
Posts: 7109
Joined: Sat Mar 20, 2004 12:19 pm
Location: Florida
Contact:

Post by vickyg2003 »

It looks like the protocol captures the signal pretty well. I like my timings to be within 50. So maybe we could tweak the lead in time a bit, but we are dealing with remote captures, and ir widget captures, so there might be a some timing differences from the capturing device.

Image


jkgtw, do the other buttons work? Or did the lack of the power button make it so that you couldn't test the rest of the buttons.

The protocol only sends out one copy of the signal if the button is tapped. On the sling box, there is no ability to hold a button down.

jkgtw, on the original remote, do you need to hold the power button in order to power the unit on. Or will a short tap work? If a short tap will work, could you capture a short tap?
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.
jkgtw
Posts: 10
Joined: Tue Mar 10, 2009 9:28 pm

Post by jkgtw »

Thanks for reply.

Every buttons are working except power button.
Anyway, I will capture again on next week.
vickyg2003
Site Admin
Posts: 7109
Joined: Sat Mar 20, 2004 12:19 pm
Location: Florida
Contact:

Post by vickyg2003 »

The code learned to the Power button is being sent by the power button.

There are 2 reasons why this might not work.

1) The power button might need to be held, if so we'll need some repeats to simulate being held.

2) It could also be that the learn on the power key, is not the power code.

Either way, relearning the power code will help diagnose the problem.
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.
The Robman
Site Owner
Posts: 21944
Joined: Fri Aug 01, 2003 9:37 am
Location: Chicago, IL
Contact:

Post by The Robman »

Could you try some experiments using the original remote? Try doing short presses of the button to see if it still works, then try longer presses until you do get it to work. That would confirm that a longer press is needed.
Rob
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help!
Post Reply