Originally posted by DRabbit ....
If there ends up being a user installable firmware update that "improves" the issue, that will be a good development. I just don't know why they can't seem to ELIMINATE the problem.
Good Morning,
This is in no way a defense of Ricoh, but there are several types of software problems that can occur, particularly in embedded real time systems - and the K3 falls into that category, that can be extremely difficult to find. Fixing them is the easy part. Finding them is very frustrating. The act of instrumenting the software, can change the nature of the problem or even eliminate it - thus making finding them all the more difficult. The best way is monitoring the system in real time, externally with external equipment. Unfortunately, that is pretty much a lab situation.
Characterizing the problem, getting it to repeat, so that one can understand the conditions and then to track it down is more art than science. Then toss in some hardware variations across components, where the problem occurs only with percentage of a component (usually near an operating limit) and you have just created an even tougher problem.
Also, what is even tougher is that the users see the problem, not always manifesting itself always in the same way - thus is becomes almost a random event. In some instances its an environmental problem - temperature induced.
Anyway, just my two cents worth on the problem....