0.10.11 crashed during logfile playback (input tracer)
Posted: Sun Oct 16, 2011 10:24 pm
Hi Matt,
I was reveiwing a HCR32 log file tonight and just finished collecting data into input tracer (wideband??) when nistune crashed.
W7 32bit
nis 0.10.11
opened logplayer
opened input tracer
set value to 'max'
selected 'battery' in the tracer's dropdown
ran log player at full speed
tried to move the logplayer window to see the input tracer one, it ignored the mouse drag request as it was busy running through the log file.
the log player window became active after it finished parsing the log file and then I moved the window, no sooner than letting go of the mouse button after dragging it nis crashed.
also noticed that input tracer values were off, the max values in the input trace were higher than the ones listed at the bottom of the traced data (grey section below were it states min, max, average etc).
also log player is only working correctly if used at x1. if used at anything like x1/4 the red line value do not correspond to map values.
eg. log player might say tp(load)=10 but the fuel map value is 40. it seems as though the log player view is at a greater resolution but its actual reference position that is displayed is not coeesponding in a fuel map.
KR
Sime
I was reveiwing a HCR32 log file tonight and just finished collecting data into input tracer (wideband??) when nistune crashed.
W7 32bit
nis 0.10.11
opened logplayer
opened input tracer
set value to 'max'
selected 'battery' in the tracer's dropdown
ran log player at full speed
tried to move the logplayer window to see the input tracer one, it ignored the mouse drag request as it was busy running through the log file.
the log player window became active after it finished parsing the log file and then I moved the window, no sooner than letting go of the mouse button after dragging it nis crashed.
also noticed that input tracer values were off, the max values in the input trace were higher than the ones listed at the bottom of the traced data (grey section below were it states min, max, average etc).
also log player is only working correctly if used at x1. if used at anything like x1/4 the red line value do not correspond to map values.
eg. log player might say tp(load)=10 but the fuel map value is 40. it seems as though the log player view is at a greater resolution but its actual reference position that is displayed is not coeesponding in a fuel map.
KR
Sime