Converting RAW from Girder to Pronto?

[Easley]

It there a way to convert the RAW code in Girder to Pronto code? I am trying to document all my settings and this would be very helpful.

Steve

[jrhees]

Yes, but its not all that fun

There are several documents that tell about the Pronto format. Armed with those and the RAW format details you have what you need to do it manually. If there's enough interest I can probably be pursuaded to put this into the Girder plugin or some sort of utility.

The RAW format you see in Girder is very simple: It always begins with 'R' to indicate RAW. The next 4 digits are a hex value of the delay value between codes. Pronto handles this delay by making it the last PAUSE of the last burst pair.

Following these is the actual burst data, starting with the initial burst. Each burst or space is represented by two *or* 4 digits. Two will be used if the duration is less than 0x80 cycles long. If the dureation of the burst or space is >= 0x80, then 4 digits will be used to extend the duration to a 15-bit value (with the MSB bit 15 set to a 1).

The RAW format does not require bursts and spaces to be paired -- ie., the sequence can end with a burst -- and often does. When converting this to a Pronto code you would take the Inter-code Delay value and make it the final space.

The timing value for bursts and spaces is similar to Pronto -- each value is in carrier cycles. The *exception* is the inter-code delay value, which is in units of 51.2uS.

The last detail is if there is a code in the 'Code2' box, then this would be the 'repeating' code and the code in the 'Code1' would be the 'once' code. The 'Code2' box's contents in this case will not have an 'R' in front.

-Jon

[hvyemtal]

This would really be very helpful. There is a utiltiy (IRTOOL) for the JP1 project that decodes the Pronto Code and will automatically give the used protocol, device code, and command code. Maybe it will be useful in future developments of the USB UIRT. There is also decode_IR_DLL that can be used to write programs to analize the IR streams.

Check it out it on the yahoo news group below
http://groups.yahoo.com/group/jp1/

[ebariaux]

I don't know if there has been any follow-up on this but I just wanted to write that little converter tool from UIRT code to raw CCF code.

I tried to implement what was described here but the device did not react when I fired the CCF code I have generated.

First remark/question: I don't have a USB-UIRT but an old serial UIRT so I used raw code learned with that device. Does this follow the same format as the USB-UIRT?

Then, supposing I have the beginning of my raw UIRT code like that:
R0342B1550D080C1F0C090C

Am I correct to "interpret" it like this:

R => raw data
0342 => inner-code delay => * 51.2uS

B155 => initial burst
0D => space

08 => burst (LED on)
0C => space (LED off)

1F
0C

09
0C


Thanks for any info,

Eric.

[jrhees]

No, not quite. The UIRT2 did not support 16-bit durations [bit 7==1](other than the inter-code space). So, the B1 is the first pulse, and 55 is the first space, etc. For the UIRT2, bit 7 is part of the 8-bit duration.

-Jon

[ebariaux]

Thanks for the info,

the first hack at the converter did not work but I'll look a bit more into it and I'll post here when I have something working.

Eric.