Quote:
Originally Posted by dcb
ac7, I used a way old copy of cooledit. dunno if it still exists.
forgotten, if the changing the vss enable event timing doesn't fix it then I would ask that you set it back to 2ms and then drive with the wonky speed reading and see if distance tracking is still ok at those speeds.
I just took a road test with the stock .72 codebase. Didn't have any issues at 75mph. I didn't have a spot I was comfortable going faster than that within reasonable driving distance. At some speed the pulses WILL be less than the debounce period but I expected it to at least get folks to 80mph @2ms.
|
Hey there,
My vss code is 32816 (8204*4) and it's very very accurate now that i changed it to 1 milisec. Much better, but at 60 mph the vss reading starts slowing down just like it used to at 40 mph. Sometimes I do go faster than 60 and it messes up, is there anyway I can go lower than 1 milisec?
Also, quick question. I tried creating a timer a while back, and it was only accurate within a half a second, is that just the nature of the clock on the board or my code? If my code, I think I can fix it.