JP1 Remotes

vickyg2003 wrote:I find this kind completely uncomprehendable, although sitting here staring at it, do I start counting from 0, and then skip counting for anything that has a comma in it?

If so then I could also count the numbers then I could point the errors where there are more setup types than = signs in the device setups section. As you note, I reported there were 6 device types in the remote by counting those = signs.

mr_d_p_gumby wrote:

vickyg2003 wrote:I find this kind completely uncomprehendable, although sitting here staring at it, do I start counting from 0, and then skip counting for anything that has a comma in it?

If so then I could also count the numbers then I could point the errors where there are more setup types than = signs in the device setups section. As you note, I reported there were 6 device types in the remote by counting those = signs.

It might help to always print the device type number in your report. That way you'd see the way the entries would be interpreted by IR/RMIR.

For the device type number, think of it like this: Start by initializing a variable to -1. Then read & parse each line. If no device type number is present (no comma), add 1 to the previous value in the variable and use that as the device number. If a device type number is present, use it and update it to the variable.

The more complicated case is where you find device type numbers such as $0202. In this case, split the high and low bytes into two values. Treat them as separate values (use two separate variables, both initialized to -1; use the same logic independently for each). The low byte is the device type number. The high byte is a secondary device type number used only in older remotes.

vickyg2003 wrote:If I'm reading this correctly,

0 implied 0
0,2 specific 2
1 implied 3?

Is that correct?

vickyg2003 wrote:Which is high, which is low?

vickyg2003 wrote:
I can make changes to the report if anyone can give me rules. However, trust me, you don't want ME to try to correct the RDF's!!!!!! I know Chris was extremely busy, and if memory serves me right there was something else we were waiting on before Chris was going to spend time on this, but for the life of me I can't remember the details.
.

$22 values and behaviors (quite possibly incomplete or just plain wrong.)
In general, device buttons and Setup always respond with a blink. In the description below "all" means all buttons except Devices and Setup. I haven't checked to see if actual IR signals are sent, except for $0F.

Byte $23 bit 0: Power
         bit 1: Ch+
         bit 2: Ch-
         bit 3: Vol+
         bit 4: Vol-
         bit 5: Mute
         bit 6: Last
         bit 7: Fav
Byte $24 bit 0: Info
         bit 1: Exit
         bit 2: Up
         bit 3: Down
         bit 4: Left
         bit 5: Right
         bit 6: OK
         bit 7: Guide
Byte $25 bit 0: Pg+
         bit 1: Pg-
         bit 2: A (yellow)
         bit 3: B (blue)
         bit 4: C (red)
         bit 5: D (green)
         bit 6: Macro1
         bit 7: On Demand
Byte $26 bit 0: Macro2
         bit 1: Menu
         bit 2: (phantom1)
         bit 3: Day+
         bit 4: Day-
         bit 5: 1 
         bit 6: 2-9 or 0 (didn't narrow down)
         bit 7: 2-9 or 0 (didn't narrow down)
Byte $27 bit 0: 2-9 or 0 (didn't narrow down)
         bit 1: 2-9 or 0 (didn't narrow down)
         bit 2: 2-9 or 0 (didn't narrow down)
         bit 3: 2-9 or 0 (didn't narrow down)
         bit 4: 2-9 or 0 (didn't narrow down)
         bit 5: 2-9 or 0 (didn't narrow down)
         bit 6: 2-9 or 0 (didn't narrow down)
         bit 7: (dash)
Byte $28 bit 0: Aspect
         bit 1: (skip forward)
         bit 2: (skip back)
         bit 3: List
         bit 4: Live
         bit 5: (rewind)
         bit 6: (play)
         bit 7: (fast forward)
Byte $29 bit 0: (pause)
         bit 1: (stop)
         bit 2: (record)
         bit 3: PIP
         bit 4: Swap
         bit 5: Move
         bit 6: PIP Ch+
         bit 7: PIP Ch-
Byte $2A bit 0: Input
         bits 1-7: (?) (unknown, but definitely not buttonF1 or buttonF2)