sulky_ has quit [Remote host closed the connection]
sulky_ has joined #qi-hardware
sulky_ has quit [Ping timeout: 240 seconds]
qi-bot has quit [Remote host closed the connection]
DocScrutinizer05 has quit [Disconnected by services]
DocScrutinizer05 has joined #qi-hardware
sulky has joined #qi-hardware
qi-bot has joined #qi-hardware
sb0 has joined #qi-hardware
__20h___ has quit [Ping timeout: 250 seconds]
pcercuei has joined #qi-hardware
pcercuei has quit [Quit: leaving]
pcercuei has joined #qi-hardware
eintopf has quit [Ping timeout: 244 seconds]
eintopf_ has joined #qi-hardware
eintopf_ is now known as eintopf
sb0 has quit [Quit: Leaving]
DocScrutinizer51 has quit [Ping timeout: 244 seconds]
DocScrutinizer51 has joined #qi-hardware
fengling has quit [Quit: WeeChat 1.4]
sb0 has joined #qi-hardware
fengling has joined #qi-hardware
fengling has quit [Ping timeout: 240 seconds]
fengling has joined #qi-hardware
pcercuei has quit [Ping timeout: 244 seconds]
pcercuei has joined #qi-hardware
fengling has quit [Quit: WeeChat 1.4]
whitequark has quit [*.net *.split]
roh has quit [*.net *.split]
roh has joined #qi-hardware
whitequark has joined #qi-hardware
pcercuei has quit [Quit: leaving]
SSomeOne has joined #qi-hardware
pcercuei has joined #qi-hardware
dandon has quit [Quit: .]
dandon has joined #qi-hardware
wildlander has joined #qi-hardware
pcercuei has quit [Ping timeout: 265 seconds]
<roh>
hm. anybody played with miniature (<3mm diameter) cmos cameras before?
<roh>
i got some for free and am wondering how to get them to talk to me.. it got i2c, some vout line and a '4mhz' labeled one. still not sure if i need to provide a clock in there or what
<whitequark>
probably has ntsc output
SSomeOne has quit [Quit: Leaving]
<roh>
whitequark: maybe... any idea why 4mhz?
<roh>
ntsc should eat 4.433 something i thought
<roh>
or 3.5something
<roh>
well.. i found a 3.6864 oscillator in the misc parts box and hooked it up.. voila.. there is the i2c working somehow. a device on 0x36 which wasnt there before
luke-jr has quit [Excess Flood]
luke-jr has joined #qi-hardware
<DocScrutinizer05>
hook your scope to vout
<DocScrutinizer05>
but I'm afraid you will need to initialize the thing via I2C
<DocScrutinizer05>
not exactly simple to guess or RE how to do that
<roh>
hm. scoped it. i2c dumped it... and i guess my clock is too far off... anyhow.. the available brief-sheet says its not anything normal like regular video... 400x400 pixels says that quite directly.
<roh>
i fear i need to build some digizer extra for this
<DocScrutinizer05>
err, teh horizontal "pixels" (correctly lines) are irrelevant in a CVBS signal. And 400 lines vertical would be "normal" for NTSC, I.E should still show a picture when the frame rate is 45 to 65Hz
<DocScrutinizer05>
worst case use an old CRT TV, those are usually even more tolerant against out-of-specs framerates, vertical resolution lines etc. Just the line frequency should be 15kHz to 16KHz
<DocScrutinizer05>
attaching a scope to vout you's easily see the line frequency, either it's TV ~16kHz, or VGA ~32kHz
<DocScrutinizer05>
problem would be progressive n H * 400 V for TV, you have interleave there and so a usual TV could only show cope with max ~700/2 lines per frame
<DocScrutinizer05>
progressive
<DocScrutinizer05>
VGA works also with 60Hz frame rate but 400 progressive, so the line frequency is twice as high
<DocScrutinizer05>
aka 640H*400Vprog@60
<DocScrutinizer05>
while PAL TV is nH*~512Vinterleave@50
<DocScrutinizer05>
oops sorry NTSC has 486V
<DocScrutinizer05>
and VGA 640*480
<DocScrutinizer05>
bottom line: as long as you see a semi-decent CVBS signal on vout, you'll most likely find a monitor (or TV) to sync and display that signal
<DocScrutinizer05>
nasty when vout has a serial digital signal though
<roh>
some omnivision devices have an 16bit id register at address 0x300a
<DocScrutinizer05>
to 25
<roh>
so i just guessed that 69 30 is this.. at 0xa
<DocScrutinizer05>
:nod:
<DocScrutinizer05>
no manuf logo?
<roh>
and voila.. some google brought up http://www.ovt.com/products/sensor.php?id=49 , which is the first sensor ive looked at today which had some kind of analog out at all and is small enough to fit what i see as case (its 5.5mm total diameter and has a 2.2mm tool-shaft)
<DocScrutinizer05>
nah on the sensor, but you already found it
<DocScrutinizer05>
here you are 400*200@60, "full @30"
<roh>
well.. thats my best guess so far. i am not sure at all... the numbers is just plain guessing from the i2cdump
<roh>
if that pcb in the handpiece would not have been labeled with silkscreen at the solderpads for the cable from the camera and to the monitor... i would still not have power on it.
<roh>
the 2 leds in the head get their own vcc and seem to like 20mA at 6.0-6.1V just fine... and my 'doctor friend' who uses these on a daily basis gave me his best guess when testing out different currents about how bright its on the original device