15 captured repliesPartial discussion capture · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHECU setup on 996 turbo engine - Info required pls
Leading reported evidence
Replace into it
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.
Performed · outcome unconfirmed
I’ve got a 996 C4S with an M97.01 swapped into it.
Leading evidence: 'Replace into it' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Adjust most of the settings' (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 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.
Performed · outcome unconfirmed
Control of the N75 must be done externally with a custom made electronics, I use arduino for this.
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.
Performed · outcome unconfirmed
I am using a strongly modified M97.21 engine , you use a Mezger 996 turbo as it seems.
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.
Performed · outcome unconfirmed
I am using a strongly modified M97.21 engine , you use a Mezger 996 turbo as it seems.
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
But I’ve tried adjusting most of the settings on that page with no real difference except going to no home trigger.
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
m97.01 cam trigger wheel pattern is the same (it's the same cam as a 996.2), it should work with the m96/70 option - try the bmw m62 home trigger as a test, and try changing polarity.
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
I think your issue is something else - when you say you're not seeing a cam reading, what do you mean - have you set the cam position inputs on the vvt tab?
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
You must make sure that the PiD is set correctly for the throttle to work satisfactorily (assuming your ecu is just blank to start with), which can be observed by watching the throttle plate and watching how it behaves to inputs.
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.
15 eligible posts · 0 unverified posts · 1 discussions match the subject in their title or opening post.
911uk: 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: 20261027T020439Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
Evening all. Any help greatly appreciated from those that have played with aftermarket ECU settings.
We're coming close to trying to start the project car with the Metzger engine in and it's only now I realise just how complex getting the electronics right is.
I am learning as we go so forgive me if the terminology is out. There is an aftermarket ECU involved so we are starting from scratch.
We have set TDC on the light and established 274 degrees offset,
not 276 as expected. Fire order should be 162435 as per standard and cam triggers are 60-2 as I understand it?
Having checked injectors and coil packs by ear, all are firing the right cylinders (the loom is also new as it's not in a 996) I guess Cam sensors have to be on the right bank is a given and we can start without setting logic on the Variocam plus for start/ tick over.
Is there a factory spec sheet on this as I'd hate to get it wrong now. Injectors are standard (new) (450cc from memory) but we have a twin screw in-tank lift pump and a Bosch 044 in the mix so we are way over 3.8 Bar. Plugs are new.
If we have timed on a light and were at TDC on crank pulley then we can set 0 degrees on #1 and go from there on ignition I assume? Someone mentioned this has to be checked through the plug hole as it may be TDC on #4 but I'm not sure I understand how/why Porsche would do that???
Once done, are we missing anything? We are assuming a 5% throttle position for start up but I have no info on factory injector loads etc. to extrapolate from either. The car will get tuned eventually but for day 1, does anyone have info/ specs about just recreating what Porsche's settings would have been when the engine was in the 996tt??
:?:
Cheers,
Jay
Which ECU are you going to run this on? Setting a standalone up for the first time is a lot of work..
TDC is always cylinder 1, have never encountered an ecu that is any different. You must establish that your offset is correct, but you must establish the cam flag or latch points first, in order to fire the cylinders on the correct cycle.
If it is a Syvecs unit, there are a good many tutorial videos online. For other ecus, you will have to do your research.
You will also need coil saturation information, which can be approximated by measuring the primary resistance of the coil packs. As a very basic rule, the higher the primary resistance, the higher the coil on time. 2ms gets most coils to spark but be very, very careful if the resistance is very low.
Have fun! It is a long road to get all parameters correct. Oh, and about 10-15 degrees of initial throttle angle will get it started once you have correctly populated the tables.
You must make sure that the PiD is set correctly for the throttle to work satisfactorily (assuming your ecu is just blank to start with), which can be observed by watching the throttle plate and watching how it behaves to inputs.
Thanks Mike.
I will speak with the guys in the morning.
I tried Syvecs but they had been struggling with a similar application in the UAE at the time to no avail. Not sure if they have solved it yet. The issue being I wanted CAN functionality to interface with the chassis... It's been a long haul with lots of research and translation.
The ECU has base info for a 996 but being the Metzger, I'd like to ensure the setup on the turbo was the same out of the factory and not make any assumptions as I know the internals are very different.
Now that I think about it though, the key difference is with the 'bottom end' I guess so it may be very similar for the rest, Porsche being Porsche.
Onward we go. We'll get there!
Thanks again.
J
ecu on cayman turbo
Hello,
I also have a cayman 987 bi turbo up and running. I am using a strongly modified M97.21 engine , you use a Mezger 996 turbo as it seems.
I was thinking myself about using a 996tt ECU to control my engine. Mappjng woulld be relativly easy as 996tt ECU has fully documented damos.
This would imply using 996tt MAF and wideband lambdas and a few relaitvly easy changes to the engine wire loom.
Issues will be interaction of the 996tt ECU with the CAN drive and other can signals. The cayman 987 ecu will send CAN messages to control the electric front ventilators, the clima control (switced off when engine overheats) and to PSM.
All this is difficult to implement in the 996tt ECU.
On the other hand you could modify the 987 ECU . Mapping fueling and knock control is straighforward, VariocamPlus is almost the same, so you could probably leave the NA tables.
wiring of the 987 ECU is almost identical to the 996tt ECU.
Control of the N75 must be done externally with a custom made electronics, I use arduino for this.
The hard core gui could probably debug the ECU assembly in IDA pro and adaot the assembler code.
Still open question is the PSM-ECU interaction , which will not work between a 996tt ECU and a 987 PSM.
Currently I am investigating here to find out if using a CAN Bus sniffer and message translater can be used.
For yoru 996tt engine in a cayman: Easier solution is probably to use all electronics from a 996tt donor car.
regards
Andreas
(P.S. my 987 turbo is documented, google "pff.de italian job")
Just been checking your build out. Would love to see more. Turbo's look amazing.
The CAN is a total arse if you try to get the two generatioms talking. 996 was 'almost' CAN whereas the 997 uses it for everything.
Stick to 987 997 technology and it should be easier than mine was. I have an aftermarket ECU in there now.
Pm me. We have learned loads about the 997 CAN
Glad its not just me playing this crazy game!!
8)
Jay,
Any chance i can PM or anything about the 997 can?
i want to use a maxxecu pro on the 997turbo for an engine swap. ive just put a post out asking if anyone had the data. Maxxecu do a plugin for the 996 but not 997.
MaxxECU PRO Plugin ECU for Porsche 996 / 997
MaxxECU PRO Plugin ECU for Porsche 996 / 997
www.maxxecu.com
I have an old map on my laptop written for a syvecs. It's a bit rubbish though. Was loads wrong with it, I've since had it mapped on speed density, but I don't have the new one to hand. It does have the variocam map on it though.
Edit. Ok 997, for CAN data, yes, 996 isn't very sophisticated.
It's a 996 turbo engine map.
Hey everyone, I’m hoping I can get some help.
I’ve got a 996 C4S with an M97.01 swapped into it. Have the Maxx Pro plug and play for the 996 Turbo as we were hoping this would work with the 996 CAN and then we could make the 997 engine work.
The M97 should be same 60-2 crank trigger…and I think I have that working. But the M96 setting for the cam triggers isn’t giving me any luck. Anyone got any advice on settings for the cam triggers?
Thanks! Good luck everyone with the different projects
m97.01 cam trigger wheel pattern is the same (it's the same cam as a 996.2), it should work with the m96/70 option - try the bmw m62 home trigger as a test, and try changing polarity. What does the trigger logger/scope show?
Great to see someone else using Maxx on one of these.
Thanks for the reply! See I thought it would be the same but have had no luck getting any cam readings with this setting. Just stays at invalid. Have tried both polarity settings. If I set it to N+1 on the cam then I do get readings but they jump around all over the place. I’ll try the M62 setting.
The trigger log is from when I had the VR crank sensor rising just to check if flipping the wires reacted correctly, had issues because was cranking slow and uneven. Now I can get the crank so trigger logger to go green most of the time and read rpm. But the Cam signal seems like a decent signal. Was set to falling on this.
Home trigger looks the right pattern and falling edge detected no problem, would be easier to see if zoomed out a little bit, but looks fine.
I think your issue is something else - when you say you're not seeing a cam reading, what do you mean - have you set the cam position inputs on the vvt tab?
Also a small thing and probably unrelated to cam trigger, but green most of the time doesn't sound perfect, you want green all the time (other than on first crank) - have you set unsync'd start?
Hi, sorry for the late reply just been able to get back to the car.
Regarding cam, if I have the VVT cam position inputs set to M96 then the cam position in the data logger stays invalid. If I set it to N+1 and have it set to 4 teeth per cam revolution I get a fairly stable reading of cam position even if currently the position figures are way out, and they also change each time you try and crank it as can be seen in the “N+1 trigger logs"
I’ve tried quite a few different trigger and home settings but M96, M62, N+1, N-1 etc I can’t get any sync (trigger logger doesn’t turn green). If I set the “home trigger”to No or if I turn on unsyc’d start then I do get consistent green on the trigger log. I’ve attached a picture of unsyc’d trigger settings. But I’ve tried adjusting most of the settings on that page with no real difference except going to no home trigger.
I’ve attached some pictures and also logs in the hope that helps, unfortunately can’t attach the trigger log file itself. Appreciate any effort. Feels like it’s going to be something simple but just can’t seem to find what it is at the moment.
This is a source reference. Confirm exact model applicability in the original material.