Pages: 1 ... 8 9 [10]
 on: January 13, 2021, 05:40:05 AM 
Started by Aardschok - Last post by Aardschok
Traction Cheesy

Not really... I got my ESP32 to talk to itself via two MCP2515s and found the likely cause for slow CAN - the MCP2515 library I was using looks to be pretty inefficient and I intend to improve it.

Lost a lot of my work to a hard drive failure though and never found the motivation to pick this up again Sad

I will come back to this at some point... hopefully sooner rather than later

 on: January 13, 2021, 04:28:07 AM 
Started by justinvw2646 - Last post by tao13
I hoped with last night modification for some tables and with cat cleaning complete modification in my 5120 hacked file*start from justinvw file ) , resolve the problem, but nothing.
I modified to 5120 file (justin file) :
  KFMRESNL because i suspected it and i made all 0.
  CLRSHK made 5 was 0

I wrote the file and start the car. First 5 minutes car works ok at idle. After trims begin to work (STFT specially) after 2 minutes coolant temp was 70-75 degree and there idle goes crazy again. I made a log for this and I made a log for 90 degree too , where I arrived with car at home after 5 km running and stop it at idle. In 30 seconds idle goes crazy again at 90 degree coolant temp.
I checked all maps.scalars witch are modified in 5120 file from stock file and and all looks ok.
What is strange I don’t find any byte or something who tell me have other modification exclude maps, like asm changes.
With stock file modified with 4 bar map sensor car stay stable at idle with all maps/scalars same like in 5120 file only was need axis or mapss values divided or multiplied with/by 2.
Other thing who i saw in VCDS in block 8 absolute pressure with engine start is 50mbar with 5120hack file but with stock file (with the same map sensor like 5120 file) i saw 230mbar.
Some suggestion please? I don't know what happen and where is the problem.

 on: January 13, 2021, 04:25:34 AM 
Started by Aardschok - Last post by adam-
Did this gain any further traction? Smiley

 on: January 13, 2021, 04:21:07 AM 
Started by pukacinio - Last post by pukacinio

Rest you can find by trial and error
I can only confirm that rear O2 heater are on bit 5 and bit 6

Thanks mate ! Maybe this will be enough  Wink

 on: January 13, 2021, 03:27:22 AM 
Started by GolfSportWagen - Last post by gt-innovation
Then we are not probably talking about the same injectors... Smiley Smiley

Ones i found and been using for a long time have exactly the same spray angle and long nozzle as the oem as per pdf...

 on: January 13, 2021, 03:05:44 AM 
Started by pukacinio - Last post by BlackT

Rest you can find by trial and error
I can only confirm that rear O2 heater are on bit 5 and bit 6

 on: January 13, 2021, 01:53:43 AM 
Started by ottosan - Last post by ottosan

Nobody replies so I have decided to share my findings.
Beside MAF linearization my problem was the IDLE CONTROL. In particular module LLRRMM.
It is controlling IDLE by controlling torque via ignition angle.
dmllr_w is the varialbe that affects mizsol_w.

I could not imagine that IDLE PID was the problem. Because the engine is heavily modified LLRRMM need to manage less torque to maintain steady IDLE. The stock idle PID was overreacting because the angular momentum and produced torque of the modified engine differs from the stock. It looks like the IDLE PID was constantly increasing and decreasing torque by decreasing and increasing igniton via dmllr_w and the increase/decrease steps where to big . That is the whole story.

I have recalibrated the IDLE PID and now all is fine again. Ignition angle does not oscillates and the RPM is steady.

Still I have the problem with MAF linearization. As I wrote in my previous post I have used already all kinds of formulas to linearize my 98mm maf housing. No matter how I calculate it, it is still not right. Is there a specific approach to linearize custom maf housings?

Thank you


 on: January 13, 2021, 12:44:11 AM 
Started by artec12 - Last post by yangbohan
Thank you! Very good method, I have been researching KFMIOP and KFMIRL, but did not find any calculation method

 on: January 12, 2021, 11:01:43 PM 
Started by bikemaker - Last post by bikemaker

Reviewing my log files it appears I shot myself in my own foot. From the log file I determined I should have turned the ignition off, instead I attempted to READ DTC’s and got an error code. What followed was a failure of my engine to start.

“09/Jan/2021 04:32:28.276: USER: The ECU is in programming mode, and needs the ignition turned off to reset.
If this does not end programming mode, the ECU likely believes the flash memory is not programmed correctly.
09/Jan/2021 04:32:28.296: USER: Reading all ECU DTCs failed.”

When I tried to write the original file I got the following DTC’s which I am certain is why the drive by wire circuits were shut down.

“P0602 Module programming error, P0562 System voltage low, P2128 Unknown DTC, P0123 Throttle/pedal position sensor, P0223 Throttle/pedal position sensor and P2123 Unknown DTC”

All is currently well and I am a little more confident in trying once again to kill the SAI and O2 monitors. Launch control sounds like something I would be interested in. And Tony I am still uncertain if you are saying I should use a 4Z7907551R binary as a base flash instead of –S??? Thanks everyone

 on: January 12, 2021, 04:51:52 PM 
Started by fgawly - Last post by bazaa

I'm in the process of making an XDF for my MED17 CCZA 200PS however, it's my first experience with tuning and this is the car I own. I hoped I can start with an easier architecture however I can't allocate funds right now to get a test rat...

If anyone have any definitions or a kp or anything, kindly share it  Grin Grin

Bin attached here..

Hi This should be of help to you to match up your maps!

Pages: 1 ... 8 9 [10]
Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Page created in 0.021 seconds with 14 queries. (Pretty URLs adds 0s, 0q)