Adamw
-
Posts
20,023 -
Joined
-
Last visited
-
Days Won
1,278
Content Type
Profiles
Forums
Events
Gallery
Blogs
Posts posted by Adamw
-
-
What ignition coil(s) does it have, many of the duratec coils dont have built-in amplifiers so will need an external one.
-
8 hours ago, RexSR20 said:
I swear that in the trigger offset menu I cant negative values, anyways with the timing light it marks the degrees that are on the table, I will try, thanks
There is 720deg in a 4 stroke engine cycle. The offset can be anywhere between -360 and +360.
Because the crankshaft does 2 revolutions in an engine cycle, the timing light will show "correct timing" regardless of if you are sparking at TDC on the exhaust stroke or TDC on the compression stroke. However then engine will only run if the spark is near TDC compression stroke.
-
It sounds like your ECU is powering up ok initially but dropping out when cranking. This suggests the FET is ok. What is the voltage on pin 45 when cranking?
-
So is the tacho connected to Q26 or to the ignitor? If connected to Q26 has the tacho output been assigned in the software?
-
My thought was the display may stay alive down to say 3V but the processing side may dropout before then.
-
Since the error is at peak torque, this could quite likely be related to ignition noise. Is it using the stock ignition system? Resistor spark plugs?
The other common cause of trigger issues on evos is the cam sensors are quite prone to failure since they get a lot of heat from the turbo and the water outlet right next to it.
Cant really tell which of those is more likely in this case, but generally if the error only happens at high boost then it is ignition system noise, if it only happens at high RPM when hot regardless of boost, then more likely the sensor.
-
It could only be a wiring issue, the brake switch isn't even connected to the ECU so the ecu has no idea you are pressing the pedal. It sounds more like the CAN bus is being interrupted, but I would start by confirming you have 12V at the back of the gauge with the pedal both up and down.
-
Your lambda setup looks correct, I changed the gauge setup a little.
Have you programmed the 2nd AEM O2 to use ID2? Have you programmed the CAN gauge to use 500Kbit?
current viper map, scav pump on, ethanol sensor on WMP1200cc CAN changes.pclx
-
There is a "TDC" every 360degs, so 400BTDC is effectively the same as 40BTDC.
-
Provided you have both a crank and cam sensor, you could wire injectors in pairs like below, set injection mode to sequential. This will give you what we call semi-sequential. The injection events will then be more correctly timed with valve events, just 1 injector in the pair will fire 45deg earlier than ideal and 1 injector will fire 45deg later than ideal. But still better than multipoint group mode where the injection events arent timed with valve events at all.
Inj1 drive to Cyl 1 & 5.
Inj2 drive to Cyl 7 & 2.
Inj3 drive to Cyl 6 & 3.
Inj4 drive to Cyl 4 & 8.
-
With the CAS aligned in the factory position as per the service manual, the trigger offset would usually be around -90 to -100deg.
288 probably means you are sparking at TDC exhaust stroke.
-
I think the cruise PID is just a bit too aggressive. You can see below how noisy TPS delta gets when cruise is active, even at the fixed speed, then where you change the set speed you see the big spikes in both directions. Basically the throttle is fighting every tiny deviation in speed. That over-excited TPS is also constantly triggering accel enrichment so you are probably burning more fuel than it should be too.
Try halving your existing cruise proportional gain. I think Integral and derivate probably are ok but please set the "PID setup" to cruise control before the next log so we have some better data.
-
The attached will be a reasonable starting point. Enter your injector settings, correct engine size, check base timing and all sensor calibrations.
-
I would also check voltage on pin 45 during cranking, if this drops below about 7.5V the ECCS relay can drop out.
-
14 hours ago, Seran said:
Pin 1 and 2 to D22? Not Pin 2 and 4?
Sorry yes, 2 & 4 to D22. I have corrected my original post.
14 hours ago, Seran said:And what would be the trigger edge in the software, Rising?
The distributor has reluctor sensors so you dont have a choice of the edge in the software.
-
I thought most JZ engines have the tacho connected to the ignitor. Does it still have the stock ignitor and coils?
-
Agree with INSW20, the stock sensor is not suitable, I assume the Toyota ECU must have a much lower impedance input or some other form of attenuation to bring it down to a usable voltage.
-
The "noise" on the scope is normal, this is artificial noise caused by a combination of the 8bit resolution and aliasing due to the sample rate. I see the same "noise" even with a clean computer generated signal on the bench sometimes.
The exhaust cam sensors are pretty prone to failing on modified evo's, so if you haven't tried that and still have the other car available you should try swapping that as a test.
But apart from that I would still be concentrating on ignition system noise.
-
The log shows the idle valve is fully closed. So either the throttle is too far open, the stepper is not homing correctly, or it is losing position, so the ecu only thinks it is fully closed, but it is actually not. I would expect to see idle position around at least 20% open when hot. I would change the integral gain to 0.5 as 1.25 is possibly forcing it to move faster than it can actually move.
Your idle ignition proportional gain is also very high at 15, typical is 1.0.
-
That would be fine. Connect dizzy pin 2&4 to D22 which I assume is the black wire. Distributor pin 5 to the grey, distributor pin 6 to the blue.
-
Please continue to communicate with Anthony, I cant help. I suspect the problem is the "0" on the front of the serial number, this is meant to be removed. You need the code for 4471, not 04471.
-
On 4/19/2024 at 7:11 PM, jdniss said:
I'm having trouble keeping a CAN DI activated after an onscreen key press in the G5 firmware - the CAN state reverts to "Fault" after 2 seconds.
I had a look at the help file and noticed the CAN Latching comment - I've tried both Active and Inactive latched states - but any and all configuration still exhibits the same behavior:
The CAN DI triggers into an Active after CAN keypress, activates the output, then after 2 seconds reverts to Fault and terminates the output.This means the ecu hasnt received a CAN message with the DI status for more than 2 seconds. This is a safety feature so if for example a wire gets broken your CAN-controlled cruise control wont get "stuck on". Default realdash behaviour is it only sends a CAN message when a state changes (ie the button is pressed). The "write interval" option is meant to force realdash to send the message at least once every interval regardless of a state change. So it sounds like your .XML is either missing the write interval attribute or has a formatting issue with it, or there is a bug preventing that from working.
You could possibly use the CAN monitor in realdash to see if that message is being transmitted regularly. I assume it shows transmitted messages.
-
Your trigger offset is zero in the G4+ map and 268 in the G4X map. You need to confirm that with a timing light but I would expect similar numbers in both ecu's.
-
I can see in our tech support system that one of our sales team has provided an unlock code to you. Please continue dialog in the support ticket with Anthony if you still have a problem.
Visualizing Rotary Injection Timing
in G4x
Posted
No, I dont think you have got it yet - but I dont blame you when there are popular videos like this floating around. I dont claim to be a rotary expert myself, but there is so much wrong in that video that I can only roll my eyes.
The Link uses E-shaft degrees and it appears he is also talking in E-shaft degrees. But why the hell he is saying at 28:10 (same as "position F" in the schematic above) is 460degs is beyond me. If the E-shaft lobe is pointing to 9o'clock then this is 540BTDC. 460BTDC would have the lobe pointing to about 11:40o'clock.