Difference between revisions of "Talk:10338"
| Line 1: | Line 1: | ||
| − | [[Image:10338-purple-image.jpg]] | + | --[[User:Andrey.filippov|Andrey.filippov]] 16:49, 3 December 2007 (CST)[[Image:10338-purple-image.jpg]] |
Several of our 10338 sensors are producing images of this nature (single purple-ish color.) | Several of our 10338 sensors are producing images of this nature (single purple-ish color.) | ||
| Line 12: | Line 12: | ||
--[[User:Ekratzer|Ekratzer]] 11:18, 3 December 2007 (CST) | --[[User:Ekratzer|Ekratzer]] 11:18, 3 December 2007 (CST) | ||
| + | |||
| + | What cable length are you using? It looks like the signal phase is wrong. You may try &byr=0..3 in ccam.cgi parameters, but that is just to verify the problem, to fix it you'll need to adjust that phase (see [[Adjusting_sensor_clock_phase]])--[[User:Andrey.filippov|Andrey.filippov]] 16:49, 3 December 2007 (CST) | ||
Revision as of 14:49, 3 December 2007
--Andrey.filippov 16:49, 3 December 2007 (CST)
Several of our 10338 sensors are producing images of this nature (single purple-ish color.)
Some of the sensors produce this type of image 100% of the time, others 50% of the time (after reboots), and still others work fine.
I have tested with 7.1.5 from sourceforge and (as of today 2007-12-03) the latest from CVS with the same results.
Is this a bad sensor? Has anyone seen this behaviour?
(note: the lens is a fisheye.)
--Ekratzer 11:18, 3 December 2007 (CST)
What cable length are you using? It looks like the signal phase is wrong. You may try &byr=0..3 in ccam.cgi parameters, but that is just to verify the problem, to fix it you'll need to adjust that phase (see Adjusting_sensor_clock_phase)--Andrey.filippov 16:49, 3 December 2007 (CST)
