mapper
-
Posts
368 -
Joined
-
Last visited
-
Days Won
32
Content Type
Profiles
Forums
Events
Gallery
Blogs
Posts posted by mapper
-
-
In the modeled mode doesn't the IAT temps get automatically compensated as part of the Gas law? Theoretically If you set the IAT as a 3D table with gear you should be able to Increase fuel compensation over the closed loop Ftrim limit.
Right the fuel model keeps the AFR constant over a wide range, assumed the charge temp approximation table is tuned properly. Regardless of this, i usually like to richen the mixture a bit up at high IAT's, to cool the combustion chamber and to prevent detonation.
Sure you can add 10% to overcome the closed loop lambda system by 5%, it's a workaround.
It's not that straight forrward as it could be with targed compensation and i it's not the way the CL Lambda is meant to work. So i like to have 6D target compensation.
Maybe the LINK engineers can add an axis option on the 4,5 and 6D tables.
-
Thank Simon for clarify. Yes would be great to get a possibility that closed loop lambda shouts off or goes to a high lambda. Maybe the engineers can integrate a plsusibility check of the signal for error detection.
For example. Input value must change at least once a second while engine is running.
Regarding fault code. Can i setup the fault codes manually from the ALM-CAN. Because it's just a controller without a own display. So would be good to have this infos.
Otherwise i would really like to see a external wideband controller with all the functionality and diagnostics from Link. What i'm aware there is something in development, which is great!
-
Yes I know, thtats what i've mentioned above.
-
Sorry Simon if my question was a bit harsh. The engines we tune cost sometimes a fortune and i would be a very bad and costly mistake if we crash an engine because of a bug I wasn't aware.
I can understand after your explanatian that it isn't as easy as i hope.
Anyhow, I like to make some suggestion that could maybe work for you.
- Programm a additional GPLimit in the background that cuts cylinders at 99% DC, or doesn't work no other limiter anymore after DC has gone over 100%? Add a fault code, that users are aware what happened.
- Span the y-axis of RPM 3D table with INJ DC
- output the DC to another class in the code, setup another RPM limiter that goes active in case DC>100% i don't know how the code looks like, most likely much to complex for me, but maybe it helps to get an idee for a solution.
-
Hi
Just wondering what happens if the internal Lambda controller detects a error. On analogue gauge i use closed loop lambda control just on the low load part of the map, because a fault sensor can force the ecu to take too much fuel out. Consequently the engine could run dangerous lean. I'm aware that there is a setting for the alowable control range for closed loop lambda.
I'm wondering what the closed loop lambda control will do in case of a error:
- if we use the internal lambda controller on the furry or Thunder
- if we use a external CAN-Lambda controller? for example does a ALM-CAN transmit all error codes to the ECU? does the closed loop lambda control shut off in this case or are there a chance that the mixture can go lean as on a analogue wideband?
-
Any update to this?
just had the situation that a too retarded timing has ended up in uncontrollable boost creap and much to high EGT's . Happened because the engine was in a running condition that added up alot of safety retard on different tables.On top of that the engine is very knock limited, so we see already very high EGT's on normal operation conditions. To be exact, it's driftcar that made a standing burnout and bounced for a while on the Revlimiter. IAT, ECT and Rev Limit safety retard added up together which ended up in much too retarded timing. I don't want to reduce the IGN retard on the specific tables, because it's needed if just one condition applies (for example, just high ECT, no revlimit and good IAT's) . Functions as Traction Control, Launch control etc, can sum up the retard even more, to a level that will destroy some mechanical components.
Conclusion: We need a minimum timing table, the settings should allow to choose if it's also applied while Antilag, Launch or Traction control is active.
-
yes as I've written I'm usually use the target overlay already to do gear compensation (Lambda Target Table Overlay spanned Gear or Speed vs RPM)
So i need more tables to alter the target. Otherwise i can't use full time closed loop control. Usually it's a good idea to rich mixture up on situations that are prone to knock. (high temps and loads)
-
Hi Warmup
It is an issue in the firmware however it is so deep in the code that making a fix could open up many more new issues.
We are looking at ways to at least make the tuner more aware the duty cycle is maxed out.
Sorry Simon that's no excuse!!
It's a error that can destroy easily a very expensive race engine! It's not seldom that we have to go up to 90-95% of Injector DC during tuning (because of to small injectors). It's absolutely not acceptable that the revlimiter doesn't work anymore if we have a overboost situation, colder air or what ever that forced the INJ DC to go above 100%. On most engines with hydraulic lash adjuster, ignition cut isn't a option, because that can lead to some mechanical problems (hydraulic adjuster pump up etc.).
-
Sure you can do that with a calc table too, but doesn't fix the inaccuracy the gauge already has. I would use a ALM-CAN wideband or similary CAN based lambda controller and connect it over CAN.
You can find a list of CAN devices, which already a CAN template is available in PC Link, in the help file. That makes the CAN setup very easy.
-
-
May i add to have 4d and 5d tables and many other tables setup as afr compensation overlay. For example i like to add some fuel at high IAT's and high gears.
If I use full time closed loop control, i need to adjust the afr target accordently. Otherwise the closed loop will remove the additional fuel on high iat ( overlay target already used for gear compensation).
similary on warmup of the engine. Most engines run smoother during warmup of we use a bit richer mixture.
-
Setup a Calc table and adjust values until the values match it to the know source. In my case the Dyno wideband. Unfortunatelyy its even not linear. So check afr match at different points.
-
Aem uego Analogue controllers are somewhat of innacurate! usually the display shows already wrong values. The 0-5v output isceven worse. Shows too rich on rich side and too lean on lean side. I used to calibrate them agains my dyno O2 ( Motec PLM)
-
Hi Scott, just spotet the link-can Lambda.
Is a new product comming or does it just refering to the internal lambda?
-
Totaly agree Ducie54. The newest software is useless in this state. But I'm sure the LINK development team will do there best to fix it asap.
-
LINK TEAM you really have to fix it!
There are many currious things going on with the newest software. I was tracktuning a LINK G4+ Plugin yesterday. I run in alot of problems, because i mapped the car on 5.5.4 an have used the newest 5.5.7 to do the track tuning. As soon as i connect the Y- axis on GP2 Limit, 4D, 5D and overlay table have gone crazy. It doesn't matter if I made adjustments on- or offline. It's quite dangeres if the tables axis adjusting it self without knowing it.
Please fix it ASAP! Very urgent!!
-
have a similary problem. After I finished tuning on 5.5.6 I downloaded 5.6.7 to add more than 25 ECU Logging channels. Unfortunately the GP 2 Limit y-axis (set up as Differential Fuel Pressure) is reduced to just one row and y-axis value is zero. If i try to put in other y-axis values, nothing changes.
-
Hi Simon
Unfortunately there is still no comparison chart and old manuals for G3, G2 etc. on the website.
How that get added soon.
-
I found that problem also on other tables. For example if you set Launch table to 3D, while offline.
Beside the other things, great work! Really excited to have more Logging Channels and 3D target Slip map. Can set now Target Slip vs G-force with the Thunder :-)
And just found on the last Impreza, that a 2D Target table could be to less. Required steps change alot with running time (when valve warms up).
-
Have a look at the help file in PC Link Software. You can find everthing you can think of there.
-
Or you can connect a Dash or any other CAN based logger. This way it should be possible to log 80 channels am more with a high logging rate.
Simon can you pleas elaborate what data rates are the values sent to CAN-Bus and how many channels are possible with CAN. As an example with a custome CAN tamplet and Racetechnology Dash 2 pro ?
-
Hi guys,
This is a good suggestion. Currently we have on the request list an item to make the password protection level adjustable.
I know ;-) so would be good if you regard the details I mentioned, when you make the changes.
Besides sorry for so many typos above, hope corrected most of them ;-)
Back to topic.
just sent a new passwort protected map to a customer. After he loaded it to the ECU, the TPS calibration was wrong and all the time at 100%. I used the last map i saved on the ECU as a base. Don't know why that happened. Now, I have to connect via Teamviewer, because i don't want give out the password. And as I mentioned he can calibrate TPS, which works, but don't save it.
-
Have a look a this closed Loop boost control example! Best is if you read through the closed loop boost section of the help file, too.
If you want use openloop, just span the Y-axis to EGT.
Regardless of control method, you must setup an EGT iput first for EGT, an chose than the Input as an axis.
-
You can do that too! Just span WG duty cycle vs EGT or if you use closed loop boost control (recomend that) target boost table with EGT on one axis.
Remember if you use closed loop boowt controll you span usually WG duty cycle table Target boost vs RPM. Fill the table too reach each boost target with the right WGDC. If you do that you can just put im your target map numbers in the target map and use the axis settings for things what you want. E.g. Egt vs rpm.
Regarding the target overlay map. You have to activate it first under "fuel main" > Lambda Target Table Overlay" > ON
Now you find the table in the menu "FUEL, same place as AFR/Lambda Target Table.
closed loop lambda failsafe
in G4+
Posted · Edited by mapper
If we already separate the +- parameter, why not do a Table?
Around idle, there is often more than 5% correction needed to cover all runing conditions (e.g after a hot restart, heat soaking etc.), under WOT and high RPM just a small correction should be applied to prevent lean running as we spoke about. On overrun situations there is often a lean spike which forces the system to go on to the rich limit. This correction are than applied for a small moment at idle, that scholdn't happen and could be limited with a 3d ftrim limit. (set less ftrim limt at load load and high rpm)