9 Apr
2007
9 Apr
'07
9:17 a.m.
Chuck Guzis wrote:
On 8 Apr 2007 at 16:24, Jules Richardson wrote:
Hmm, so maybe the trick is to find someone selling an old MK3 board, rather
than the MK4...
No - but when I last trawled the web for info on
the CW (about a year ago) I
was getting the impression that what little "officially sanctioned"
documentation and example code there was out there was squarely aimed at Windows.
There is definitely a register-level description and source code for
the MK3 out there that shows how to get the PCI resource values from
the BIOS. Myself, I use my own code to drive the cards; I've
never needed code
from others.
I must admit I tend to write my own code for things like this - but I like to
be able to see what others have done just to avoid any gotchas which might
otherwise slow progress - hence it's useful to have a repository somewhere.
The data from the catweasel is basically a series of
counts between
pulses.
Hmm, that's interesting. Does it store fixed length counts in the buffer, or
does it use variable-length counts with a couple of bits of "header" to say
how many bits the count takes up?
Either way, it got me wondering if there's some really oddball stuff that the
CW can't read because the count between pulses is just too long. It's too
early here to reason it out :-)
It's a bit difficult looking at a data stream
from the CW
and figuring out what you're looking at. I've got a little Windows
utility that takes any track and plots the data on a time axis,
changing from 1 to 0 with every pulse. The graphical representation
really helps to figure things out, particularly when dealing with
someone's idea of GCR.
I was thinking the same thing with this concept of over-sampling the entire
track into a buffer; it's going to be a heck of a lot easier to decode the
data while looking at a graphical utility.
cheers
Jules