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?