New test:
The red is right-going raster, blue is left-going. So they make an error appear twice as wide. Each row has a calibrated overlap or gap that would make them line up on that row if the overlap or gap is equal to the timing error’s distance.
Left gap is TON, right is TOFF.
You find the row with the closest to no gap or overlap, like this:
Find the row where the left ON gap looks closest, and note the signed row number.
Say TON was 50, SPEED was 7000, and it’s labeled “/-16”
Then use this equation to determine the correction:
(new TON)=(old TON)+(1,000,000/SPEED)/(ROW)
(new TON)=50+(1,000,000/7,000)/(-16)
=50-8.92
=41
The closest row will likely be different for TON and TOFF. Iterate both each time.
If you have reached 0, stop iterating that parameter.
The correction should decrease by at least one row each time, so you should be at the zero row in at most 8 iterations.
If it’s not meeting up on any row, reduce speed by say a factor of 4 on red and blue layers and run to get it “ballpark”
I think I’m seeing that changing JUMP DELAY is having an effect here- if you change it, you need to change TON by the same amount. I’m not sure how this works. JUMP SPEED is having a stronger effect on net runtime for rasters (Fill or Image) than it should, whereas increasing the JUMP DELAYs only had a small effect.
tcon_tcoff_test_v02.lbrn2 (1.9 MB)