Page 2 of 2

Re: Problem transmitting learned codes

PostPosted: Thu 4. Sep 2008, 06:01
by martingu1979
hi!

thanks for the quick response, unfortunately your file also did not work...

meanwhile I have found out that the protocol in use is the ruwido r-step protocol.
it seems to work at 56 kHz which should pose no problem to the rs232 device.

do you have any information regarding this protocol?

thanks in advance


martin

Re: Problem transmitting learned codes

PostPosted: Thu 4. Sep 2008, 06:33
by martingu1979
I have now managed to connect to the box by using a debug cable because I have access to development boxes at work and get the direct output of the /dev/input device when it receives a command.

I have attached the hex file of the comamnd "0". It's only called .rem because of upload restrictions.
As you can see in a hex editor, the command received by the box is 64 bytes long. For convenience, I also include a screenshot of UltraEdit showing the file in hex mode.
for comparison, the command received by irtrans is only 14 bytes long:
Code: Select all
12010330002100


any idea what I can do to make things work ?

thanks

best
martin

Re: Problem transmitting learned codes

PostPosted: Thu 4. Sep 2008, 14:44
by IRTrans
Hi,
the values you get over the RS232 port will be internal command codes - they might have nothing to do with the actual IR Code.

Attached you find a modified .rem file using the correct frequency (56kHz) and timings for your STB.

IRTrans

Re: Problem transmitting learned codes

PostPosted: Fri 13. Feb 2009, 13:32
by Dave
IRTrans wrote:Please try the attached sky-hd-1.rem file.

You will need to relearn the "guide" button - there was some IR noise in that code.

IRTrans


This worked for us with one minor change to the timings - commands should not repeat.

I've attached the rem that works for us.

Re: Problem transmitting learned codes

PostPosted: Fri 13. Feb 2009, 18:37
by IRTrans
Hi,
thank you for that info. I will add the file to the IR Codes section.

IRTrans