Mark Weaver wrote:
Further progress:
Oh my, here we go. Every time you run the haup BlasterCfg application
it sends a block of what appears to be setup data to the TX device.
This is _different_ every time. Subsequent key data blocks are also
different, and only work with the corresponding "boot block". Work =
device reports 0x80 instead of 0xA0 when the data block for a key is
sent to it if the data block was captured with a different boot block.
Now this leaves me completely clueless. See
http://www.blushingpenguin.com/mark/lmilk/ then boot3 and boot4 for an
example. See "boot" for an example with with a boot block + some codes
that work with it; and "thelot4" for a complete capture with a given
boot block + codes that work with that. It does not seem to matter if
you resend the boot block - the captured data blocks simply then "work"
ok. In summary, I really have no idea what it is doing. If anyone can
explain wtf it is doing, then I'd be very grateful.
On to the good news though -- using a captured boot block and a complete
code capture appears to do the trick. I have converted this capture
into some form of database (about 200K (vs 900K) using some rudimentary
compression), mucked about with LIRC so that it supports sending all of
the codes in the database, then used irsend to send the "power" key
until my particular cable box responded. Having found the right
codeset, I can now change channel with it. I'm quite pleased, given
I've never tried that device with the haup stuff!
If there's no more light to be shed, I'll probably consider this end of
project (i.e. works for me). I really am clueless as to what is going on.
I shall provide a patch + some more detailed instructions tomorrow for
anyone else who would like to try this out, it would be appreciated.
Thanks,
Mark (who is pretty happy now)
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
ivtv-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ivtv-devel
