a6_quattro

@Simon Just for clarification: 1) You claim that you (read Link) deliver what they say. If you buy a product that claims, from the specifications, to handle a certain functionality, that just fullfill the specs to a certain degree, you are happy and doesn't care? I don't. The behaviour of the closed loop idle control with e throttle is not on the on the expected level. The level is on a laboratory level in a school Project. 2) Never specifed it at just a bug but as a misbehaviours/bugs. 3) This isn't the first time I report this as you cartainly now. You have had plenty of time to deal with this. But as I said, I'm going to install a nother ECU from another manufactuer and hopefully be able to sell the Fury. Regards Hans

Sadly, given the this info, I have to go to another ECU brand that is more trustworthy in what they say in the specification and actually deliver. Who knows whats under the surface when you find such obviuos misbehaviours/bugs. /Hans

Tried with a mail to [email protected] but no answer, could someone from Link take this issue seriuos and do something about it? @Simon: It's still a bugg present that you thought you fixed unfortunatelly. Can't be so much more that a day to fix this for a developer. 1) Fix that when during Hold Timer and going to open loop the value doesn't get zero, set ISCL CL Trim(%) = 0 in that case. Example, coming to a red light and you get green light when the CL Idle Control is in Hold timer, if a trim value of, for example, 1% has been set it stays and is applied to the throttle in open loop causing a idle way to high. 2) Comment out the value added to ISCL CL Trim(%) when going in to closed loop, usually the first time you are in closed loop it adds around 1%. Can't see any good with this... 3) Set the ISCL CL Trim(%) = 0 every time going in to closed loop idle, do not keep the last trim value and apply it next time in closed loop. This "semi learnt value" isn't working very well. Thanks in advance Hans

@Adamw Have you had the time to review the log and tune?

Sent log and tune to you now Adam.

I'm happy that you'll spend some time to look through the log Adam, and yes, I saw that you no longer work there. I send it when I'm home tonight. Thanks Hans

@Adamw Could I email this to you? @cj I Think I'm using the latest firmware, 3632. Edit: firmware version 3631 is what I'm usling.

Hi Having a issue with E-throttle CL Idle Control that looks like this: 1) Car comes to a stop for example in a traffic light -> Hold Timer starts and adds about1% (can't say exactly because it seems more random) to the throttle. 2) Idle when Hold Timer stops is now about 1300 rpm 3) Before the CL Idle Control has taken it down to 850 I get green light and starts to move 4) Becuase I have open loop after 2 kph its now in open loop. 5) The value that was added in Hold Timer is still added even when in open loop wich get the car to idle at about 1300 rpm and also have that value through the hole throttle map. I have investigated this by my self and can't find another reason for this other than a bug unfortunatelly. Even if it looks like Link Team has stop developing the G4+ platform they should look this through and come with a solution. The car is a daily and not a drag car or drifter so this causes me to turn of key to kill LinkECU and restart to get the car to be drivable in the city enviroment. I have of course logs but this should be easily simulated in a virtual enviroment. Regards Hans

Is it possible to configure cruise control only via DI input and make it work? For example: DI 7 = Cruise On Switch DI 8 = Cruise Set Switch DI 9 = Brake Switch. /Hans

Hi These settings work fine with my Bosch 0 280 750 146. Hans

I'm starting to get really anoid of the total silence from the Link team. it would be decent if youcould give me some hint when in time you have the new release planned? Just give me a hint and I consider if a change of brand is nescessary because this has taken far to long time to fix. Other brands seems to be more "on their toes" so I'm not going to waste time waiting for something that never going to happens and promised when purchasing the product. /Hans

Whats the status on the update? It's been on hold for a while...

This bug is still present in the new firmware unfortunatelly. Wonder why Link engineers didn't take care of it?

Is the reported issue with CL Idle control for e-throttle fixed? Regards Hans

Adam Whats the status on this?

Hi Adam Yes, it happens regulary and it looks like it's a random value, sometimes it's negative and sometimes it's a positive value. I've noticed that the ISC Offset (%) holds a value that changes over time despite that idle control is in open loop in the log file. Just a thought, could it be this that introduces a value to Trim? Is this some kind of "learnt value" thats taken from last time it was in closed loop? Maby thats correct, couldn't find anything in help file and its extremely difficult to guess when I don't know anything about the strategi around this. Just trying to help role out the obvious. Hans

Adam Now when I got your attention, I can record a log with other settings on PID and idle control. Don't hesitate to ask as I'm driving the car every day with exactly the same problem. As I mention for you by mail, my idle is almost like OEM so that's NOT the problem. Throttle control is good following target so that can't be a problem with that settings in my eyes either. The problem is coming from open and going to closed loop THEN there is a value added randomly. Sometimes it's a small negative and when coming from open loop at next stop there is suddenly a positive value added. Tried with all possible settings on idle control with 2D table and 3D, zeroed out all kind of load compensations an so on. When such things happens randomly, usually there is something strange going on in the code or the strategi being coded up. To sum up: 1. Not all possible PID settings being tried out but the one being tried provides a good throttle control following target as it should 2. To investigate why this happens I tried different settings and also zeroed out all possible settings, I think, that could interfer with the idle control 3. Idle control on both closed and open loop is good 4. When going from open to closed loop the E throttle ISC CL Trim randomly adds a arbitrary value Focus around the E throttle ISC CL Trim and what's happens there and not the PID settings is my advice as an novice mapper. Regards Hans

I'm tired of "work arounds" that never work because the toolbox is to small for DBW. And for the issue that I described above you can't possible do a work around. I'm fully aware of the different compromises that the different aftermarket ecu:s has, had VEMS before this ecu. So one of the reasons I bought Link Fury was the spec it had. If it claims to have some particilary support it should have it, simple as that. If Link have had knowledge of this flaw for a long time then it's really time to fix it.

Should you interpret the silence from Link as "buy another ecu"?

It would be very nice if the Link team could investigate this issue and fix the bug in the next sprint. In my opinion, if you have support in the software that claims to handle closed loop idle control, then you have to make it work. Its extremly frustrating to have this behaviour on a street car and driving in town for example. When going from open to closed loop the rpm suddenly rises because of the E throttle ISC CL Trim add value of no reason. So far I'm very satified with the product except for cl idle control with e throttle. Have tried many different PID settings for the throttle so that is rouled out of the equation. The respons and behaviour of the throttle is good.

Hi all Could this be caused by the integral term not being zeroed out when going from open loop to closed loop? In my case for example, I have added values for AC and Power steering, the integral is quite large when going from open to closed loop causing the throttle percent go from 3.7 to 5.0. This is just a thought...

Ok, but would that help in my case? Wouldn't it add the same value when going from Hold - Speed to Hold - Timer regardless of the speed lock out value?

Hi Ok, here's the base map. Link base map.pclr

Hi Could someone help me understand why 1.4% is added to target by E throttle ISC CL Trim at file time 1.42.184? It's when idle status goes from Hold - Speed to Hold - Timer it adds the 1.4%. Regards Hans Log 2018-04-30 1;58;32 pm.llg

Hi Did you figure out what the problem was? Regards Hans