Page 1 of 3

Comcast/Pace DC50X Cable Box

Posted: Fri Mar 13, 2009 1:40 am
by alanrichey
A number of people on the Sling Community are asking for a remote for this box. Unfortunately I cannot do it directly as it comes up with the XMP protocol.

The IR files are at https://www.hifi-remote.com/forums/dload ... le_id=6398 , be grateful for any help.

Posted: Fri Mar 13, 2009 1:52 pm
by The Robman

Posted: Fri Mar 13, 2009 2:10 pm
by alanrichey
Hi

Sorry, forgot to mention we have all tried BIN files created using this file and it hasn't worked for anyone. Hence my request for a translation of the 'learnt' codes from the actual box.

Al

Posted: Fri Mar 13, 2009 2:37 pm
by The Robman
If any of the people looking for this code have the Slingbox Pro-HD, ask them to try the built in C1982 code, as this code works the Cisco box and both boxes use the same codes.

If they have PL boxes, ask them to try this RM file which is ONLY for PL boxes:
https://www.hifi-remote.com/forums/dload ... le_id=6236

Posted: Sat Mar 14, 2009 12:21 pm
by tennessee titan
Isn't there another thread (greenough1) going on the is remote??
It refers to the remote by UEI number rather than the cable box, which is the pace box...

Posted: Sat Mar 14, 2009 12:47 pm
by The Robman
Correct, that's this thread, and he has confirmed that this is the correct code, however the Slingbox has problems with this protocol.

Posted: Sat Mar 14, 2009 4:17 pm
by greenough1
I changed the title of the thread to reflect that the comcast DTA is a DC50X.

Axum version not working

Posted: Thu Sep 10, 2009 6:00 pm
by BigDaddy
Hi Robman,


Axum version of this Bin file is not working for some reason. Kindly try and suggest.
https://www.hifi-remote.com/forums/dload ... le_id=7217


Regards.

Posted: Mon Sep 21, 2009 2:54 pm
by Digital Larry
I even tried learning directly with the HAVA and it only picked up Channel Up, digits 3 and 5, and even those are not working reliably.

Any help here is vastly appreciated.

Posted: Mon Sep 21, 2009 6:25 pm
by binky123
Rob posted a BIN file here and the RMDU file here.

In case those don't work, you may have to adjust some values in the 016C Protocol. This post and thread has some notes on what was done for the dreambox. Perhaps something like that will need to be done.

Posted: Wed Sep 30, 2009 4:03 pm
by Digital Larry
Yeah, that apparently works OK for the PL chip (I haven't confirmed this though) but we are using the next generation Axum chip and no love!

Thanks though.

Posted: Wed Sep 30, 2009 5:59 pm
by binky123
I have no info on the next gen Axum chip. I think Robman said the original Axum was compatible with PL bins.

Are you able to load BINs on this next gen Axum chip? If you are able to load BINs, are you able to learn the signals it sends out for the XMP protocol? Perhaps from this, we can tell if we need to make timing adjustments to the protocol(as was done for the dreambox).

Remote Control buttons are irresponsive

Posted: Wed Sep 30, 2009 10:04 pm
by BigDaddy
Apparently it does load the Bin file on Axum Chipset. However the remote functions are irresponsive.


Regards,

Posted: Wed Sep 30, 2009 10:21 pm
by Digital Larry
Rob has assisted with creating an Axum RDF which has worked so far for many protocols. However I'm not at all familiar with the XMP protocol and wonder why the heck all of a sudden these stupid boxes are using it! What happened to good old dependable NEC?!??!?! :evil: :evil: :evil:

Oh, sorry.

As I recall Rob explained to me that Axum used a 2-byte protocol ID and typically there is just a 1-byte size difference between an Axum BIN and a PL BIN. Now I had also seen that Axum could be loaded with some PL BINs without generating an error, but I never saw one that worked. So I don't think that the fact that it could upload a PL BIN means anything - especially since it doesn't work!

Posted: Thu Oct 01, 2009 11:04 am
by binky123
I haven't seen any info on the next gen Axum II chip. It is possible they changed BIN formats and went with a 2-byte protocol id instead of a 1-byte. Some of the newer UEI remotes are also using 2-bytes. Since no one knows the BIN format, there is no use in creating a modified XMP/016C protocol. The XMP protocol is sensitive to the speed of the processor so for certain slingbox models, we had to adjust the timing in the protocol to make it work.