6 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHIgnition range reset
Leading reported evidence
Replace timing
Performed · outcome unconfirmed
No successful repair reported for this finding.
0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that performed work without a confirmed outcome
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Leading evidence: 'Replace timing' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, the most frequently mentioned possible cause is 'overspeed event(s)' (1 discussions; 0 report identifying it and 1 suggest it). The most frequently discussed action is 'Check overspeed entries' (1 discussions). For that action, 0 discussions report a resolution and 0 report an unsuccessful attempt. No action has an explicit, attributable resolution report under the current rules. These are forum reports and suggestions, not a confirmed diagnosis.
Source reports, not a diagnosis or a success probability. Counts refer to discussions and can overlap.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that suspect a cause
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suspected cause
If overspeed entries are found and if the difference between the current hourmeter and the status when the last overspeed event was recorded is less than 50 operating hours, there is a high probability that the damage was caused by overspeed event(s).
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion
If such faults or symptoms are present together with engine damage, the VAL that was created must be checked for overspeed entries.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion
The info you would need to access and change (not erase) is located in a area on a surface mount chip - not the flash memory eprom that contains the engine operation.
Replace /rest all fuctions including the displays kms/miles
Suggestion or failed attempt
No successful repair reported for this finding.
0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion
In theory this key allows you to change/rest all fuctions including the displays kms/miles.
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion
The info you would need to access and change (not erase) is located in a area on a surface mount chip - not the flash memory eprom that contains the engine operation.
These are separate views of the same evidence. Frequency alone does not establish a fix, and these counts must not be added together.
overspeed event(s)
No successful repair reported for this finding.
0
Identified cause
1
Suspected cause
0
Reported fixes
Read evidence and context
Discussions that suspect a cause
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suspected cause
If overspeed entries are found and if the difference between the current hourmeter and the status when the last overspeed event was recorded is less than 50 operating hours, there is a high probability that the damage was caused by overspeed event(s).
Counts describe captured discussions, not unique people or a diagnosis. Author identities are not reliably stored. Exact duplicate evidence is counted once across matching discussions; one discussion counts at most once per action/state. Multiple repairs reported together remain a combination. Suggestions and failed attempts do not establish a fix. Matches cover whole discussions and can include related faults, model variants and incomplete threads.
6 eligible posts · 0 unverified posts · 1 discussions match the subject in their title or opening post.
Rennlist: 1 discussions
0 evidence records excluded for query context · 0 excluded by outcome qualification · 0 adjusted by outcome qualification.
0 acknowledgements have no verified action link; they do not establish a repair result.
Generation: 20261026T213932Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
--------------------------------------------------------------------------------
Hi all, new to the forum
I own a 996 turbo, but the Mrs has a C2 which is fantastic.
The Mrs has been a silent watcher on this forum for a while now, I had a questions to ask so thought this would be the perfect time for us to sign up.
I'm currently in the process of selling my 996 turbo for a used 997 turbo which i have paid the deposit for ( can't wait). I had a few people come down and look at my 996, however they were detered because of the values in Range 1 and Range 2. This beats me as i've only but pampered the car!
What is the best way for me reset this? I've herd softronic is the key but i'm not sure where or how I can purchase this?
If anyone can help, we would be very greatful
You have to change out the ECU. Only Bosch have the internal software to re-set these ranges, engine hours, serial numbers etc. I don't believe even the dealer level has access to 'alter' data - just transfer it to a new ECU. The ECU uses a Siemens C16x based CPU - at least on the 7.1 ver in Porsche's between 2002 and 2006. Companies such as GIAC have cracked the C++ code used to write to the motronic eprom where the engine mapping is stored. The info you would need to access and change (not erase) is located in a area on a surface mount chip - not the flash memory eprom that contains the engine operation. Bosch use an access code to unlock the firmware to enable updating. Most programs such as GIAC don't need to access this section of the Motronic system to alter commands to the engine - hence no one wastes their time. The program is locked out for consumer protection but also for proprietary reasons.
However...
There is one company that *claims* they sell a device that plugs into the OB2 port that can read the keylog and display it. In theory this key allows you to change/rest all fuctions including the displays kms/miles. From what I understand - to use this tool would be illegal - but it is sold in Europe for more then $1200 euro.
+1
Unfortunately it can be done.. but you won't get this information from here.
This engine speed is not exceeded when the vehicle is driven normally. However, driving and operating problems (e.g. �changing to the wrong gear� on vehicles with manual transmission) or manipulation (e.g. tuning) can cause the maximum permitted engine speed to be exceeded when the vehicle is driven.
Overspeed events are stored in the DME control unit. The following values are also recorded:
- Number of ignition attempts in each overspeed range 1), and,
- Status of the hourmeter during the last overspeed event 2).
1) Overspeed range = Defined rev ranges with classification of expected engine damage, e.g. engine damage possible, ... probable, ... very probable, engine damage has generally occurred; see section ⇒ 'Rev ranges'.
2) For technical reasons, overspeed events are entered in a preset time interval. As a result, there may be entries in a higher rev range (e.g. range 2), while no entries are stored in the lower range.
Typical faults and symptoms as a result of overspeed events may include the following:
* Damaged valves and/or pistons (impact marks on the valve, valve impressions on the piston, valve bent).
* Cylinder liner damage (even �piston seizure�).
* Damaged or displaced connecting rod bearings.
* Loosened or loose fastening screw(s) on the crankshaft pulley.
* Loosened or loose fastening screw(s) on the camshaft gear.
* Loosened or loose connecting rod bolts.
* Cracked timing chain(s).
* Changed timing.
* Irreparably damaged clutch elements (pressure plate and/or drive plate).
* Vibrations and/or engine imbalance due to irreparably damaged clutch elements.
* Vibrations around the transmission.
* Defective synchronisation.
If such faults or symptoms are present together with engine damage, the VAL that was created must be checked for overspeed entries.
If overspeed entries are found and if the difference between the current hourmeter and the status when the last overspeed event was recorded is less than 50 operating hours, there is a high probability that the damage was caused by overspeed event(s).
The value �50 operating hours� should be seen as a guide. The possibility of engine damage occurring much later due to previous overspeed event(s) cannot be ruled out.
DME stores number of ignitions over 6 ranges of rpm for the 997s and 2 ranges for the 996s and the operating hours of the overrev occurrence.
