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
Further progress:
All stuff under http://www.blushingpenguin.com/mark/lmilk/
- I extracted all of the keypresses in the Hauppauge "database" [1].
These are in IRcodesets.xml which includes their region/device/vendor
mappings. This amounts to 9,170 blocks of data of which I have just
included
What would be handy is doing a i2c capture of a well known IR protocol
from the JP1 worksheets for the keys 0-10 and cross referencing them
back together. Would also be nice to find two protocols that only
differ in carrier frequency (38 & 56 kHz) and see what changes.
OK, I have no idea how
Some rambling thoughts.
Taking a look at the bytes, there's basically only a hunk of 10 or so
bytes in the middle that changes between the three Ir commands (1,2,3).
What would be handy is doing a i2c capture of a well known IR protocol
from the JP1 worksheets for the keys 0-10 and cross
Hi everyone
I have added:
http://ivtv.writeme.ch/tiki-index.php?page=Monitoring+I2C+Bus
to the ivtv wiki, if anyone has further information / experience relating to
the use of cheapi2c it may be useful to others if you add information to the
page.
Best Regards
Trev
On Wednesday 03 Aug 2005
What I notice is this appears to be an upload into registers 01-63,
followed by an "execute" command. Note the first byte in the addr 70
writes is 01, then it sends 4 bytes, the next write starts at 5, goes 4
bytes, etc until it writes 0x61-0x63. Then it sends a 0x40 to register
0, which is p
Mark Weaver wrote:
If you look at the 123 send log, you can see that each button in the
code set produces an enormous amount of data. This data doesn't
appear to be set up or anything -- in "normal" winTV use, each button
really does send that amount of stuff. Changing the code sets around
I haven't looked at them properly yet. The device at 0x71 is the known
IR receiver device that is already supported in LIRC being polled, and
therefore pretty obviously the transmitter has address 0x70.
OK, replying to myself here :)
If you look at the 123 send log, you can see that each but
Mark,
Thanks for doing this.
> I have managed to get this working by using a 4050 CMOS buffer chip as
> indicated by Trev Jackson. I will write this up a bit later with some
> pictures for anyone else who wants to do the same thing, it might be
> useful for those like me who don't have much in t
I have managed to get this working by using a 4050 CMOS buffer chip as
indicated by Trev Jackson. I will write this up a bit later with some
pictures for anyone else who wants to do the same thing, it might be
useful for those like me who don't have much in the way of electronics
skills.
In
Trev Jackson wrote:
Hi Mark
There is probably nothing wrong with your parallel port, Pin 12 and Pin 13 are
inputs to your computer and depending on how your parallel port is
implemented the voltages could quite reasonably be different between the
pins.
OK, this does seem to be the case as the
Hi Mark
There is probably nothing wrong with your parallel port, Pin 12 and Pin 13 are
inputs to your computer and depending on how your parallel port is
implemented the voltages could quite reasonably be different between the
pins.
To check the parallel port voltages try running the command:
l
I'm assuming you have a resistor in-place and the parallel connector
attached to another PC, as in my follow-up email?
The parallel port on the capture PC I was using is buggered -- it's
outputting +4.15V on pin 13, and +2.8V on pin 12. Really odd -- I tried
probing the parallel port on the
Bryan Mayland wrote:
Allan Stirling wrote:
I'm assuming you have a resistor in-place and the parallel connector
attached to another PC, as in my follow-up email?
I have a question about that. I wanted to build my own one of
these, but where does one get an 800 ohm resistor? My only pa
Jim Reith wrote:
I have a question about that. I wanted to build my own one of these,
but where does one get an 800 ohm resistor? My only parts supplier is
radio shack. Will a regular 1k ohm 1/4 watt work or do I have to put
like a 1k and a 4.7k in parallel and call it close enough?
I have
At 02:12 PM 8/2/2005, you wrote:
Allan Stirling wrote:
I'm assuming you have a resistor in-place and the parallel connector
attached to another PC, as in my follow-up email?
I have a question about that. I wanted to build my own one of these,
but where does one get an 800 ohm resistor? M
Allan Stirling wrote:
I'm assuming you have a resistor in-place and the parallel connector
attached to another PC, as in my follow-up email?
I have a question about that. I wanted to build my own one of
these, but where does one get an 800 ohm resistor? My only parts
supplier is radio s
Mark Weaver wrote:
I'd like to get the IR blaster on my PVR-150 working with LIRC, so
to this end I've got the parts for a cheapi2c device to capture
traffic from the Windows application. There have been some other
posts on the list about this, but I don't think anyone has actually
gotten ar
I'd like to get the IR blaster on my PVR-150 working with LIRC, so to
this end I've got the parts for a cheapi2c device to capture traffic
from the Windows application. There have been some other posts on the
list about this, but I don't think anyone has actually gotten around
to doing a captu
Mark Weaver wrote:
I'd like to get the IR blaster on my PVR-150 working with LIRC, so to
this end I've got the parts for a cheapi2c device to capture traffic
from the Windows application. There have been some other posts on the
list about this, but I don't think anyone has actually gotten aro
I'd like to get the IR blaster on my PVR-150 working with LIRC, so to
this end I've got the parts for a cheapi2c device to capture traffic
from the Windows application. There have been some other posts on the
list about this, but I don't think anyone has actually gotten around to
doing a captu
21 matches
Mail list logo
