essb00
-
Posts
372 -
Joined
-
Last visited
-
Days Won
5
Content Type
Profiles
Forums
Events
Gallery
Blogs
Posts posted by essb00
-
-
Your idle position % sits on min clamp 35%, while your idle base position is set 40%. You may need to lower your rpm lockout above target.
Plus, your idle ignition control proportional gain & derivative gain seem to high causing too much idle ignition fluctuation. You may also need to adjust the ISC integral gain.Closed loop idle speed control is supposed to make small corrections to idle variations from target, but not to actually make drastic corrections. Follow the open loop ISC setup procedure in the help file, and when properly tuned by then you can shift to closed loop.
-
14 minutes ago, Rozsko said:
Thanks Essb00, but that is exactly the thing I want to avoid, since I am running out of available custom CAN frames.
So, let me rephrase. Can I use 4 "Spartan 3" on the same ID (950) and assign Lambda1,2,3,4 the same way as you can do with "Link CAN Lambda"s?
Only one CAN-lambda per CAN ID (950, 951, 952, 953 on your case)... Having different ID per device is the only way for the ECU to know from which device it is receiving data from.
-
4 hours ago, Rozsko said:
Bringing back this topic for a quick question after spending some time searching and reading.
If the Spartan3 is set to Link mode on Id#950, then can I connect multiple units and set them up separately for Lambda1,2,3,4 the same way as the Link CAN Lambda? If the CAN Devices tab will only sow real Link CAN Lambdas (as per earlier comment), then I assume not, but wanted to check.
Spartan 3 has serial to USB connection, where you can send commands from computer (using terminal) to change parameters (CAN ID, etc.). You can see overview how to connect on Spartan 3 user manual. This though is quite complicated --- so it might be the best idea to request to have different CAN IDs pre-configured as you order 'em from 14point7.
-
I actually opened the tune file from one of your previous posts - which has similar parameters set I mentioned with this latest one you have.
The time you had your engine running on the log barely had the CAN lambda heating - and then engine stalled.
The idle settings on the start-up map is only sort of a basis - you need to also have the idle parameters tuned to your engine.
Follow the open loop idle ISC tuning in the help file - then if you already had the idle near the target, by then you can use closed loop ISC. -
A few observations about your log.
1. Your base idle position seem to low to reach target idle - and engine stalls once idle startup offset begins to decay
2. Your CAN Lambda is having error 34 at 0:13. Check the connection of your LSU4.9 sensor to CAN lambda.
The following are really not yet relevant but will later on affect how the engine runs:
1. CLL ECT lockout is too low. Put 70°С to 75°C --- if this is too low, CLL would conflict with warmup enrichments.
2. CLL Startup timer too low. Put 30s. --- CAN Lambda need time to heat up and stabilize.
-
-
Try to divide your pre-crank prime table values by 2, then put 0% on first crank prime.
Under analog inputs, on 'Lambda 1', select 'Link CAN'.
Under 'Closed Loop Lamba', try the following settings.
-
Your fuel equation mode is set to 'modelled', but the look of your fuel table is as though 'traditional'.
Try putting 50-60 on your 0-1000rpm @TPS 0%, then try to start. -
This way should work. Try it with your desired conditions.
*Condition below just as sample (as engine fan is already activating with AC as selected in engine fan control).
-
G2 is at zero offset.
-
Hard to guess what's causing it without your tune file and logs (both good runs and the bad runs you had).
-
I'm just wondering, what's the location of the IAT sensor? From idle/vacuum all the way to 280kPa, IAT reading remains constant?
-
The fuel main & fuel table is obviously not yet properly set by your tuner. Even other parameters have not been set.
...so you really can't compare it (yet) with another ECU that has been tuned to your engine.
-
Tried to open your layout file, I got the same message. Seems like it is corrupted.
-
Positive side of your fuel pump relay coil should be powered together with ECU power or ignition switch.
-
Your launch control went active at TPS 50% (LC activation TPS 50%)...
-
On your log launch control is always active, thus launch ignition trim (-5°) is also active.
Disarming speed is by driven wheel - and driven wheel is not assigned a speed source. -
Oh, sorry I didn't see you're using another type of igniter...
-
This seems to work well in my 4A-GE 16V... Whenever I reduce it, I'm having knocks on quick throttle opening at low revs.
*32% enrichment total on normal operating temp.
-
If you have it connected with that diagram, then you're missing +12V on the igniter... The body of the igniter is to Gnd. Check the diagram below (you don't need to connect Igf).
-
...then you need need to check the wiring of your igniter/ignition coil.
-
1 hour ago, maccakpa said:
im just curious when i change fuel type to modelled and change the injector to 850 and attach injector data car doesnt start.
If you don't also change the values on your fuel table, then it would be too lean to start.
You normally should have 60-80% at 0rpm/100kpa - you'd be having to do some trials before you get the sweet spot - plus some adjustments for the cold start enrichments. -
15 minutes ago, stroker said:
Wire-in
Nissan tb48
Then just interchange the wires for Trig 1 & Trig 2.
-
Fault code 11 = An Volt 1 below Error Low Value
What do you have connected to An Volt 1? You might need to check your wirings.
Better connect it to a laptop with PCLink software in order to see what's really going on.
1.5jzgte cold crank no start stormX
in G4x
Posted
Just a quick look at your map...
1. Your pre-crank prime dumps too much fuel at key on - probably why you're getting back fire.
2. You are having trigger errors. Try to lower your trigger arming threshold to values as per below. Maybe a good idea to post a trigger scope log so we can try to see what's going on. Most probably because of the trigger error why you're also not getting any coil dwell in the logs (not firing the coils at all).