mike2016

just get a cheap windows laptop dedicated for tuning. easiest solution.

i'm going to wire in a combination Bosch oil pressure/temp sensor. for the sake of cleaner wiring, can I use factory AFM signal pins? (RB26) but they are labeled as AN Volt Since AN Temp is also volt based, aren't they the same thing? what's the reason for labeling them as Volt / Temp ?

Well explained. Thanks Adam.

i don't fully understand the logic of this setting. for example in this log, in the latter part of the log starting around 3:10 when there's a sudden throttle change, lambda goes way too lean. Is this due to lag of the lambda sensor, or should i increase the async injection time?

yep. since wall wetting off, start up has been consistent and never failed once.

changed wall wetting comp to 0, and enabled asynch inj 0.5ms. no more failed starts! i think a lockout setting for wall wetting comp should be added

got it! i'll give that a try and report back

i know... if any setting will start the car, it should do it every time with the same result. on the same setting, one day i can go on without any issue. then next day, first start up fails and floods the engine. i didn't touch accel enrich/wall wetting yet, as i want to get the start up issue sorted first.

here's a dropbox link. it won't let me attach anymore files... https://www.dropbox.com/s/pjwr7ybqojptado/13 - fuel map adjust and cold start adjust.pclx?dl=0

I also tried taking out more fuel from pre-crank or crank enrich, one at a time... similar results. it's very inconsistent.

I've been messing with this startup issue for days.... i can't seem to figure out why. it was never an issue on the G4+. I tried several different settings - old g4+ cold start, Link basemap cold start, setting from another tuner. 3 different settings. same thing. it's completely random. sometimes it starts up perfectly fine, next day it would start then stall (1 bang then dies immediately). same for warm/hot engine startup. if it doesn't start properly on the first try, it would flood the engine and will take a lot of cranking to start it up again. and it starts up super rich at 0.65-0.68 lambda i did 4 different startup logs today. the 1st one shows lambda at 1.3 at cranking, but the other 3 are close to target. the 1st start up almost failed but it started. the other 3 are perfect start ups. I tried bigger "pre-crank prime" and lower "crank + post enrich", or lower "pre crank" and bigger "crank + post enrich". similar results. 1st one seems to have less failed starts. PC Datalog - 2021-03-22 6;03;34 pm Cold Start 1.llgx PC Datalog - 2021-03-22 6;05;49 pm Cold Start 2.llgx PC Datalog - 2021-03-22 6;10;15 pm Cold start 3.llgx PC Datalog - 2021-03-22 6;17;46 pm Cold Start 4.llgx

another thing i thought of about the start up then stall issue, can the long cranking contribute to this? i adjusted the post start enrichment table to match crank enrichment. it improved but still stalled randomly, but less stalls. maybe due to longer cranking times, some fuel got "purged" out?

Perfect! I'm glad to do whatever testing on my side as needed, just let me know. Link / Adam is the best

Thanks Adam. didn't know post start take over that quick and would have such a big effect. i thought "crank enrich hold time" would kind of do the same... i'll make some adjustment to post start. if you see any other issues please let me know....

Here's a few log files. i logged 5 different starts. the trigger is picking up RPM as soon it starts cranking. another thing that I've been trying to solve after G4X upgrade, the car would randomly fail to start. it fires up for like split second but won't continue to start. if it fails, it will become very difficult to start again ~ have to keep cranking for 5+ seconds, maybe due to flooded cylinder? you can see in the file "6:44pm Start then died". it logged a bad start, then attempt to restart that took a long time. and all the "successful start" have a little dip in RPM right after start. it's completely random, at all temperature level. I copied over all the G4+ cold start settings over, and tried the G4X base map settings, they all behave similar. tried adjusting crank enrichment / precrank prime...etc , nothing really helps. PC Datalog - 2021-03-9 6;42;14 pm.llgx PC Datalog - 2021-03-9 6;43;11 pm.llgx PC Datalog - 2021-03-9 6;44;01 pm Start then died.llgx PC Datalog - 2021-03-9 6;56;28 pm.llgx PC Datalog - 2021-03-9 6;57;07 pm.llgx

Arming threshold and fuel are sorted. Identical to the old setting in the G4+ (we did intensive trigger scope not long ago trying to sort out the g4x issue end up being swapped pins on the ecu connector) oddly enough, the G4+ started in half the time required, almost like factory Even some tuner I talked to said this is common with G4X. it just doesn’t make much sense why. all ecu see the signal the same way Tomorrow I’ll observe the trigger signal while cranking. I believe it only becomes “active” after some cranking

Upgraded to G4X from G4+ on my R32 GTR. it has NZ wiring trigger setup. It used to start like factory with G4+, now on G4X it takes twice as long to start. I was told this is normal on G4X as it needs to see 2 full revolution of engine rotation before it syncs is there any way to make the start up faster?

BNR32 GT-R Had to sacrifice speed speed to make room for VVT signal (DI1-4 only). I have speed signal wired to DI 9 via expansion loom now on the G4X. the speed is very erratic, not usable at all. does G4X have same limitation where wheel speed must be used in DI 1-6 only? Couldn't see anything in Help browser in the G4X. in G4+ it says only 1-6 can be used for speed signals.

G4X is working properly now! changed the firing order to 300ZX and it started right up! Sorry to have wasted everyone so much time, and thanks so much for you and your team's help. I appreciate it. I had no idea the shop who built the car used a 300Z ECU until now, i don't know what the reason was .... I changed the pins back to factory on the ECU connector after we confirmed G4X is working.

Will test in a bit when i get home! Well, I just confirmed with the shop who did the initial build. they DID modify the pins on the ECU header so they can use a 300Z ECU.

that's a good point!! if the firing order is wrong that explains everything! i found a picture i took of the G4+ a while back when i added expansion loom. can't really tell what it is but i have a feeling it's a 300Z board. i'll be home in an hour or so, to double check what board the G4+ is

I just talked to my builder, he said Jason from Link USA has a bunch of log files from their cars, they are the same setup as mine. maybe try reaching out to Jason and get some of those files and compare?

i'll try adjusting the fuel later today and see what happens. after it started earlier today, it won't start anymore on the second try. as i wanted to get 2 different logs. it's inconsistent. but why the same setting / map runs perfectly fine on G4+ but not the G4X? are we missing something here?

I uploaded the files to 02-18 folder. It managed to start and ran for a few seconds, lots of backfires. very rough. throttle does nothing. Jono and I did a scope on G4+ while it's running and cranking, i uploaded those as well. I'll try to swap the ECU later today and do a PC log.

Done. added to dropbox. i'm not sure which one is newer, so i downloaded all 3 files. 1 of them might be the same file as last one i sent.