Hi, On 2006-05-11 06:58, St?phane VOLTZ wrote: > after searching the debug data, I think there is no problem in start > position > detection (which is correclty reported to be 'top = 65'). In fact it seems > that it is the value added to the detected y position is bogus. Currently, we > add -2.0 mm which may lead in a negative y movement if the inital y offset is > low.
I had a similar problem in the gt68xx backend, where in certain situations the scan head bumped at the end of the scan area when a debugging option (scan full area) was set. A check if the start position is >= 0 helped to fix this. Bye, Henning
