tk tom
Gold Member
Tom, the diagnostic software fetches other information, such as run and idle times and peak(?) temperature (I believe).
I'm fully aware of what it displays, but most often it is just extra information not necessarily needed to diagnose a problem with the saw. In one instance it has led me to repairing a saw that had a problem but didn't show yet in symptoms. Every other saw I've seen with specific problems and running issues has been mechanical and the diagnostic hookup has not given me any more insight than what I gained from normal diagnostic procedure, more so it just confirmed what was already known.
The software will display number of times started, hours:mins on the saw, highest carb temp, lowest carb temp, avg carb temp, highest rpm last run, fuel settings h/l, time spent in different run modes during last run (wide open no load, wide open under load, part throttle loaded/unloaded, idling), number of starts ago where a fuel adjustment was made, any error codes (when a sensor senses a condition outside of normal parameters) and number of starts on saw when it first occurred, how many times it has occurred, and the last time it occurred. It only logs data if the saw is run for 60 seconds or longer. There is a test for throttle position sensor function, carb temp, and fuel solenoid function. The error codes gathered from runtime data don't often point to anything other than a lean condition, but that can be gathered from fuel settings and complaints on how the saw runs. The codes and their descriptions are very vague.
These saws are far better off being treated like the machines they are and not overthink the computer inside them. Software updates and pressure/vac tests are these saws best friends.
I would also send my saws to Randy for porting if I had my choice.