Darrow Posted August 2, 2023 Report Share Posted August 2, 2023 (edited) Update 3: Most likely the last update on this thread. Car is running fine while it is parked. Have not taken it on the road. Still need to put the rest of the car back together. The company I purchased the G4X from loaded a base map and there was a 3000 rpm lockout. The ~2500 rpm breakup was a rev limit. Changed to 6500 and all is well. Update 2: Adjusted master fuel and that fixed the rough idle. Engine does die when releasing the throttle from ~2000rpm. Current issue: None Getting breakup ~2500rpm. Hard to tell since I release the throttle as soon as it happens. Logfile: https://drive.google.com/file/d/1-jvSlj1MLFjoEy3Dku13zS0xCNOeK5fz/view?usp=sharing I almost feel I can take it on the street for a gentle drive. Hello, Just got done with getting the engine up and running albeit poorly. I need to work through a few more issues that I am hoping I can get some help with. First thing is that I am new to Link and not that familiar with going through the data to spot issues. Any tips on that are always appreciated. If anyone has any tips on creating display views in PC Link please let me know. Issues I am having: (Power is via a Razor PDM) 1) Fixed: Neither my wired in or CAN Lambda sensor is showing a reading. The wired in sensor is throwing a code 60 and CAN Lambda is silent. CAN lambda is wired in with the ecu, coils, injectors and e-throttle, Lambda 1 and has a capacitor across +12v and ground. Update 1: CAN Lambda works. I didn't fully set it up. 2) Fixed: The engine runs rough similar to a misfire. Tailpipe smells a little rich but without Lambda I cannot validate. Update 2: Was running way lean. Changed master fuel from 10 to 15. 3) Fixed: Engine initially goes up to 1300 rpm on start then tails off to an rpm significantly below the idle rpm setpoint. Revving the engine up smooths out the engine a little then starts to run rough after a few seconds. Update 1: Changed idle control to closed loop and idle now holds to table values. 4) Fixed: On the longer logfile there is a bit where depressing the brake kills the engine. I disconnected my brake trigger from the cruise control DI pin and depressing the brakes no longer kills the engine. Since this is a DI I wouldn't think this would cause the engine to die. Update 1: Had brake tied to stop switch instead of stop nc. Changed to stop nc. 5) Fixed: Update 1: Engine dies when giving quick throttle blip/hold higher RPM and then release throttle. Update 2: Changed master fuel from 10 to 15. 6) Fixed: Hunting idle. Update 2.5: Changed from closed loop idle to open loop idle. Any help is appreciated. Thank you in advance. Extra info: Base timing and timing offset has been set. Timing creep at higher rpm has not been performed due to running issues E-Throttle has been calibrated and actuates as expected when manually operated Injectors and coils tested for correct wiring Injectors are 550cc Coils are R35 coils Latest ecu file attached for anyone interested. 2023-08-05 Update 3.pclx Edited August 5, 2023 by Darrow Update 3 Quote Link to comment Share on other sites More sharing options...
DerekAE86 Posted August 2, 2023 Report Share Posted August 2, 2023 Upload your tune file please Quote Link to comment Share on other sites More sharing options...
Darrow Posted August 2, 2023 Author Report Share Posted August 2, 2023 Attached. Thank you. 2023-08-02.pclx Quote Link to comment Share on other sites More sharing options...
DerekAE86 Posted August 2, 2023 Report Share Posted August 2, 2023 40 minutes ago, Darrow said: 1) Neither my wired in or CAN Lambda sensor is showing a reading. The wired in sensor is throwing a code 60 and CAN Lambda is silent. CAN lambda is wired in with the ecu, coils, injectors and e-throttle, Lambda 1 and has a capacitor across +12v and ground. Your CAN Lambda hasn't been configured under CAN -> CAN Setup. I'm not sure there's a point to putting a cap between 12v and ground. I would double check the wiring for the LSU4.9 because the ECU controller seems to just be reporting a problem. 47 minutes ago, Darrow said: 4) On the longer logfile there is a bit where depressing the brake kills the engine. I disconnected my brake trigger from the cruise control DI pin and depressing the brakes no longer kills the engine. Since this is a DI I wouldn't think this would cause the engine to die. You've got DI5 as "Stop Switch". This isn't supposed to be wired to your brake pedal switch; this is a engine kill switch. At no point does DI7 go high in this log (the Input assigned to "Brake NC") Quote Link to comment Share on other sites More sharing options...
Darrow Posted August 2, 2023 Author Report Share Posted August 2, 2023 Derek, Thanks for the look. Thought CAN Lambda was setup. It is under CAN 2. Is there something that I am missing? Well I can say the kill switch works. I will reassign to DI7. Quote Link to comment Share on other sites More sharing options...
DerekAE86 Posted August 2, 2023 Report Share Posted August 2, 2023 6 minutes ago, Darrow said: Is there something that I am missing? Yes, you have to go to CAN -> CAN Setup and assign "Link CAN-Lambda" to one of the channels as per page 11 of the manual: https://linkecu.com/documentation/canlambda.pdf Darrow 1 Quote Link to comment Share on other sites More sharing options...
Darrow Posted August 2, 2023 Author Report Share Posted August 2, 2023 (edited) Derek, Thanks for pointing that out. I thought I followed the instructions all the way but obvious I didn't Things are improving. Brakes no longer kill engine, Changed idle control to closed loop, Lambda 2 (CAN Lambda) now has values. Continued issues: Still runs rough. Lambda 1 has code 60. Might be a day or two before I can get time to verify wiring. New issue: -Now that I have stable idle I can rev the engine. Log file shows a couple of slow revs that have a sluggish response and then a quick rev that kills the engine. Edit: Its actually a hold at ~2000 rpm then release throttle that killed the engine. -Lambda 2 will occasionally flash red on the Runtime Values - Fuel screen. Not sure if this means anything. Again, not familiar with sorting through all the data. New log and updated tune file attached. 2023-08-02 Update 1.pclx PC Datalog - Idle fixed Throttle blip kills engine 2023-08-2 8;06;06 pm.llgx Edited August 2, 2023 by Darrow clarify Quote Link to comment Share on other sites More sharing options...
DerekAE86 Posted August 2, 2023 Report Share Posted August 2, 2023 12 minutes ago, Darrow said: -Now that I have stable idle I can rev the engine. Log file shows a couple of slow revs that have a sluggish response and then a quick rev that kills the engine. -Lambda 2 will occasionally flash red on the Runtime Values - Fuel screen. Not sure if this means anything. Again, not familiar with sorting through all the data. You're going very lean when revving; around 2.600 lambda (39:1 AFR) so your fuel map is wayyyy off. I think theres something in the first start part of the help file that tells you to adjust your master fuel to scale the fueling. As for the Lambda2 flashing red - that's just when it exceeds the low or high limits that have been assigned to that particular parameter: Note that these arent saved inside your tune file, but rather on your "Layout" configuration for PC Link. So the values that appear for me are the ones I use and have set on my Laptop. Darrow 1 Quote Link to comment Share on other sites More sharing options...
Darrow Posted August 2, 2023 Author Report Share Posted August 2, 2023 Derek, Really appreciate the help. I knew red wasn't good but it wasn't tripping the fault counter but then I did look at the fault log for this run. Still getting used to the PCLink interface. I will look into the fueling table. I am using a base map from the business that sold it to me but did an adjustment due to the different injectors (~250cc to 550cc) I am using. Hoping I can move past the wiring gremlins and move on to tuning. Just need the engine tuned enough to drive it to get it tuned on a dyno. Quote Link to comment Share on other sites More sharing options...
Adamw Posted August 2, 2023 Report Share Posted August 2, 2023 13 minutes ago, Darrow said: I will look into the fueling table. Adjust the master fuel to get it somewhere in the ballpark, not the fuel table. I would expect a master more like 15ms for 550cc injectors. Your injector dead time of 0.5s is unlikely correct either. Darrow 1 Quote Link to comment Share on other sites More sharing options...
Darrow Posted August 2, 2023 Author Report Share Posted August 2, 2023 (edited) Adam. Thanks. Attached is the 'generic' data sheet on the injectors I have. Since the dead time moves with battery voltage and pressure I used this chart. On the chart I believe it is battery offset that is the injector dead time. 12v and 4bar is ~.8s so with ~13v I set it to .5s. Definitely let me know if I am off base on that but that was my logic. I will still adjust as part of the larger fuel picture. 22S-XX-0550-XX_Injector_Characterization_Summary.pdf Edited August 2, 2023 by Darrow Clarity Quote Link to comment Share on other sites More sharing options...
DerekAE86 Posted August 2, 2023 Report Share Posted August 2, 2023 6 hours ago, Darrow said: but it wasn't tripping the fault counter It won't. these high/low limits are just for visual indicators within PCLink for the guage displays. You set your error high/lows elsewhere Darrow 1 Quote Link to comment Share on other sites More sharing options...
Darrow Posted August 3, 2023 Author Report Share Posted August 3, 2023 20 hours ago, Adamw said: Adjust the master fuel to get it somewhere in the ballpark, not the fuel table. I would expect a master more like 15ms for 550cc injectors. Your injector dead time of 0.5s is unlikely correct either. Adam, you are spot on. Changed the master to 15ms and smoothed out the idle. I increased the dead time and nothing really changed. Changed the table and added about .25s to each spot from 10v to 16v. Quote Link to comment Share on other sites More sharing options...
Darrow Posted August 4, 2023 Author Report Share Posted August 4, 2023 Things are getting better. Able to get it started and have a smooth idle. Now working to fix a sputter at ~2500 rpm. I believe it may just be a lean condition. Could be timing. Not really sure. This is what I don't know about tuning and I am looking to learn. Tomorrow I will get a bit more time to play around and adjust fuel. I am hesitant to play around with timing much at all. I do have a couple of bosh knock sensors but not sure how much faith I can put in those. Anyway. I am running out of upload space here so g-drive links will be used. I really appreciate the help is getting my project road going. Log file: https://drive.google.com/file/d/1-jvSlj1MLFjoEy3Dku13zS0xCNOeK5fz/view?usp=sharing Quote Link to comment Share on other sites More sharing options...
Darrow Posted August 5, 2023 Author Report Share Posted August 5, 2023 Done with initial set up. Thanks to Derek and Adam Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.