problems with mode2

[Dan C. <dc...@ac...>]

Hi,

I am attempting to restructure a driver i have to generate MODE2 data, and
am running into a few issues. I couldn't find any documentation describing
the expected format of mode2, which makes it bit hard to see exactly where
the data i am generating has differences.

Here's some example mode2 from my driver/remote; the pulse is the very
first thing i get. I cut out the middle, but the end is the very last part
of a press:

pulse 2750
space 750
pulse 550
space 350
pulse 500
space 350
pulse 500
space 350
pulse 550
space 800
pulse 500
space 800
pulse 950
space 400

...

pulse 500
space 800
pulse 500
space 63500

The data is relatively consistent, and i dont get random garbage or
anything.

I know that lircd expects the first mode2 word to be a long space, but i'm
not really clear why; it uses this to sync, but it seems like if i specify
a header (in this case it would be header 2750 750) it should be able to
sync on that.

I gave up using irrecord to try and generate a lircd.conf because it
consistently detects my remote as RC6 (good) then fails to detect the
toggle bit (bad). In raw mode it asks me to hold down a button, then
immediately indicates "Something went wrong." "Try again." - this happens
in an infinite loop, whether or not i'm pressing anything. The default
error rates irrecord uses are a bit high, and my gap/repeat_gap differ, so
i'm not confident it will work for me anyways.

If anyone has any documents or pointers on what exact data lirc needs in
order to be happy i'd be appreciative. I should be able to find a way to
insert mode2 data for the first long space, but i'm kind of concerned that
i'm just going to hit another roadblock in short order (in addition to
making a long series of gross hacks).

Thanks,
-Dan