Pages: [1] 2
Author Topic: SIMOS 18.1 Crashing. Trying to resolve with VehiCAL (logs attached)  (Read 6149 times)
armada
Jr. Member
**

Karma: +0/-0
Offline Offline

Posts: 26



Hi All,

I'm a hobbyist tuner. Recently, I've got myself an Audi A3, 2.0T and started playing with SIMOS18.1 ECU. I'm flashing the car with VW_Flash and using VehiCAL Advanced protocol to log it. I've studied FR pretty good now and understand the underlying concept of the torque model, however, I got into some weird problem with engine completely dying off at 6000+ RPM. It just instantly "off" the power, I got a message that I have a drivetrain issue and if I'll try to press the throttle even all the way up, I got absolutely no power even to roll 5 km/h. I've connected VCDS after that event and there is an error "ECU Malfunction". If i restart the car, the problem is gone. I thought that it may be some sort of diagnostic limiter, however, after logging some parameters in VehiCAL I couldn't confirm that theory. All the limiters are raised and it could be seen in the log. Maybe someone could help me understand what is the issue?

Here are some logs (marked the event in Orange):
https://docs.google.com/spreadsheets/d/10PYyJS5fitmIfC1Nu-4TKPgXtoRJ9rUMi27jSwDJO-Q/edit#gid=300693618
https://docs.google.com/spreadsheets/d/1bHxRQNeWQoJsvFRBX8Y4A9RJHsoGjeeWVnh9hQiNFTI/edit#gid=1395486954

P.S.
I have a LPFP and HPFP upgraded, IS38 hybrid turbo.

Thanks.
Logged
ktm733
Hero Member
*****

Karma: +18/-9
Offline Offline

Posts: 661




You're files request permission. Also for a beginner for you to go straight is38 and lpfp upgrade you're jumping mountains before learning to crawl my friend. Go back to stock and start tuning from there if you really want to get some where. There is no actual tuning help on the simos 18 platform other than bits and pieces.  Posting your mod file might help people guide you.
Logged
armada
Jr. Member
**

Karma: +0/-0
Offline Offline

Posts: 26



Sorry, permissions fixed. I've tuned stage 1 on stock IS20 turbo successfully before switching to IS38 hybrid.
Logged
armada
Jr. Member
**

Karma: +0/-0
Offline Offline

Posts: 26



Block is 5G0906259L (SC800S5000000). Ori+Mod file attached.
Logged
prj
Hero Member
*****

Karma: +1072/-485
Offline Offline

Posts: 6040



You need the exact error code, then look up what sets it.
Most likely you forgot to raise a monitoring map.
Logged

PM's will not be answered, so don't even try.
Log your car properly - WinOLS database - Tools/patches
armada
Jr. Member
**

Karma: +0/-0
Offline Offline

Posts: 26



You need the exact error code, then look up what sets it.
Most likely you forgot to raise a monitoring map.
Thanks for the insight. I'll read the exact error code later today with VCDS. Regarding monitoring map: do you refer to torque monitoring map or mg/stroke one (for torque intervention)? If I look at "Limitation of engine torque" and "Maximum indicated torque due to power limitation" they look way above indicated engine torque that I'm outputting.
Logged
prj
Hero Member
*****

Karma: +1072/-485
Offline Offline

Posts: 6040



First the code.
Logged

PM's will not be answered, so don't even try.
Log your car properly - WinOLS database - Tools/patches
armada
Jr. Member
**

Karma: +0/-0
Offline Offline

Posts: 26



First the code.
The code is P060C00 (Internal Control Module Main Processor Performance). It's passive after car restart. I've also read a freeze frame:
Ambient Air Pressure: 970 mbar
Coolant Temperature: 97 C
Engine RPM: 6052.25 RPM
Intake Air Temperature: 19 C
Malfunction Frequency Counter: 1
Normed Load Value: 100.0 %
Odometer Reading: 38970 km
Logged
IamwhoIam
Hero Member
*****

Karma: +52/-115
Offline Offline

Posts: 1070



That's a monitoring fault code.
Logged

I have no logs because I have a boost gauge (makes things easier)
bamofo
Sr. Member
****

Karma: +34/-3
Offline Offline

Posts: 420



ip_tqi_ref_sel_mon[0]
Logged
armada
Jr. Member
**

Karma: +0/-0
Offline Offline

Posts: 26


« Reply #10 on: May 27, 2022, 08:40:36 AM »

ip_tqi_ref_sel_mon[0]
Thanks. Really appreciate your input. I guess for stage 1 this stock table was fine, but it is no more. One question: does it affect the torque received by DSG for its operation (just as ip_tqi_ref_n_m_air_vvl_cam_X do) or I can simply bump up these limits?

P.S. Just for the information: I have a TVS Engineering Stage 3+ DQ250 gearbox tune.
Logged
ktm733
Hero Member
*****

Karma: +18/-9
Offline Offline

Posts: 661



« Reply #11 on: May 27, 2022, 11:33:51 AM »

Thanks. Really appreciate your input. I guess for stage 1 this stock table was fine, but it is no more. One question: does it affect the torque received by DSG for its operation (just as ip_tqi_ref_n_m_air_vvl_cam_X do) or I can simply bump up these limits?

P.S. Just for the information: I have a TVS Engineering Stage 3+ DQ250 gearbox tune.

100% these tables will alter torque the tcu see's based off maf readings... well map
Logged
armada
Jr. Member
**

Karma: +0/-0
Offline Offline

Posts: 26


« Reply #12 on: May 27, 2022, 02:06:54 PM »

Understood. Should I increase (extend) the axis value for MAF (mg/stroke) or the values in the Z-axis (Nm) themselves? I can see that I'm hitting just 405 Nm before hitting ECU reset event. That's nowhere near the limit of this map at the load that I am.

Couple of additional questions if I may (most likely for prj as VehiCAL developer):
1. When I was logging with VCDS I was seeing 1389 mg/stroke limit (because of logging routine limitation I guess as the load goes higher than that). What is the name of the parameter to log maf load in mg/strokes in VehiCAL? Can it go over 1389?
2. Manifold air pressure (= MAP) shows 2560 at max. Is this a physical limitation of the 2.5 bar MAP sensor? I guess I had 3.0 bar sensor based on ip_prs_up_thr_mes table (top value is 3000). How does the ECU calculate the load after that (MAF is calculated after all)?
3. Is it OK that I'm in DTM_ECONOMY mode of Actual state of the torque dynamic state machine IGA intervention instead of DTM_HIGH_DYNAMIC?

Really looking to your insight.

BTW, the issue was with ip_m_air_cyl_max_stnd_vvl and not ip_tqi_ref_sel_mon.
« Last Edit: May 27, 2022, 03:53:30 PM by armada » Logged
armada
Jr. Member
**

Karma: +0/-0
Offline Offline

Posts: 26


« Reply #13 on: May 29, 2022, 06:25:11 AM »

New logs:
https://docs.google.com/spreadsheets/d/1auJz_Nc5Cwmq6K1PHdpURxwkGiR3wMNBUYNrV5DgyUI/edit?usp=sharing

I've marked 2 issues. 1st in green, 2nd in yellow. Within them I've marked the problem in red. So, actually what I see is maf_stk_cbk_av[0][0] (Actual gas mass in the cylinder, bank and lift specific) is higher than maf_sel_mon[0](Mass air flow signal (process monitoring) (engine configuration selective)). In the first case it leads to ignition intervention, in the second (I guess) it throws me into limp home mode. I can find the data definition for this parameter in FR, however, I cannot find where this process monitor is located (no calibration reference). Maybe someone can point me in the right direction?

So, I'm back to P060C00 and U112300 codes at exactly 6000 rpm after the second event.

BTW, when I try to log with VehiCAL wastegate position\setpoint I got 0 all the way in the log (psn_wg and psn_wg_sp).

To sum up:
1. How can I increase maf_sel_mon[0] limits?
2. How can I overcome P060C00 codes? Any ideas for logging additional parameters that could help? Definitely not related to ip_tqi_ref_sel_mon[0] as for the given mg/stroke and rpm I have a limit of at least 520 NM there. I've tried searching in FR what sets this error to exclude things one-by-one, however, couldn't find such information there.
3. Why psn_wg and psn_wg_sp displaying 0?

Thanks.
« Last Edit: May 29, 2022, 11:36:40 AM by armada » Logged
prj
Hero Member
*****

Karma: +1072/-485
Offline Offline

Posts: 6040


« Reply #14 on: May 29, 2022, 01:38:39 PM »

100% these tables will alter torque the tcu see's based off maf readings... well map
Why don't you just stop posting when you have no idea WTF you are on about.
Monitoring maps do not affect the torque output whatsoever.

Set the 7x1 out of the way, to 900nm or so.
Also 520nm is not enough, this is indicated torque limit, it's not real tq.

Move all that shit out of the way to at least 700nm or above.
Logged

PM's will not be answered, so don't even try.
Log your car properly - WinOLS database - Tools/patches
Pages: [1] 2
  Print  
 
Jump to:  

Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Page created in 0.023 seconds with 17 queries. (Pretty URLs adds 0.001s, 0q)