Timboj

Hi guys, is this something being looked into for an update?

After moving to 7.2.2 I get this prompt every time the PC Link software is opened or ECU is disconnected. Was this an intentional inclusion? Seems innocuous enough, but it's a step I have to do every time now where I didn't used to have to, but more annoyingly, if my laptop logging was running when I switched the car off, I can't just fire the car up again and continue with logging. I have to power the ECU, connect the PC Link software via the above and then ignition... I've tried uninstalling and reinstalling but it's still there. Can we have this removed or switchable?

Yeah I've got the same issue:

Hi mate, I just found a spare 12v and ground (unused connector in my car) near the cabin fan and then added some DTM2 connectors. You'll have plenty of options to splice into 12v somewhere though.

I noticed my battery charge was down a little so I let it charge overnight and tried again today while still in car. I managed to update so maybe that was the cause?

Hi guys, per advice tried to update to the latest firmware. Can't get past these screens and obviously can't use the car right now.. Uninstalled 7.2.2, downloaded a new copy and tried again. Same result.

Cheers. I'll give that a go. And lower my lambda a touch

Any chance you guys could chime in on this one? Should I read this as reduce the proportional?

Thanks Vaughan

@Adamw Any luck with isolating this issue?

@Adamw It's been slightly improved (larger overshoot/undershoot has been reduced) but I've noticed a lot of noise on the throttle position, and it's definitely noticeable in the rpm: I assume it's the PID settings but I'm still wrapping my head around them... Log and map: https://drive.google.com/file/d/1GSQJJS7pe6VLhOybz0W_WHIXcemPYYaG/view?usp=sharing, https://drive.google.com/file/d/1YpblaNe9HfRxCbb5OEkzmDKGSZfepjdR/view?usp=sharing

Logged example from today if it helps https://drive.google.com/file/d/161e7okAY0gl-nlcaoqJZ6yoXGsVwg6jz/view?usp=sharing

Any idea what's happening here? It doesn't happen every time and typically only happens at startup at roughly operating temp. Looks like it coincides with the ethanol temp. I'm using a Syltech/Continental flex fuel sensor. Map attached. I'll add the log if needed. ethrottle_PID_6.pclx

That's night and day @Adamw, thanks. For what looks like such a small change, particularly low speed gear changing, it has drastically improved the feel. It had gotten to the point where I thought I had some slack had been introduced into the drivetrain (but suspected it could have something to do with the tune) because that unresponsiveness was manifesting into engine speed undulation. I could probably live with the config you've given me but how do I approach adjusting from here? In this example here do I dial back the 20% feed forward? Or in this case, add some to my 4% (-15) cell? Just want to understand how to interpret the data.

Thanks Adam. I'll give it a shot.

Dashpot doesn't appear to be activating around most of the instances in this log: https://drive.google.com/file/d/1BAWqB2atEgnuyxi15vn1ulBy1J_kTi_0/view?usp=sharing, https://drive.google.com/file/d/1tOesf1BAuMzpr_5C4FXJku7h9w1c1_G8/view?usp=sharing Example- all under RPM lockout condition:

Hi guys, what setting should I be looking at that's causing the delay in my throttle closing? It's felt most in circumstances like the second instance where I'm off throttle and clutch in but the revs continue to rise because the throttle stays open momentarily. There are plenty of examples of the throttle following the target pretty closely in terms of responsiveness so my assumption is this is a setting.

Totally agree but what I showed above was ECU calculated and worked fine. After they were captured, I normailsed to 5th gear and then all of a sudden wasn't being logged.

Hi guys, I assume it's something I've done but the fix isn't jumping out at me.. Gear detection was working great: And then it's disappeared from the log ever since? Settings: I'm pretty sure the only thing I changed after calibration was to normalise to 5th (which is the 1:1 ratio), Map and recent log https://drive.google.com/file/d/1X30O2fOWZig1Ug6ozBg-nrZo-Xo_ri8T/view?usp=sharing, https://drive.google.com/file/d/1fOolAWwNVbgaLZ3n5ppF0-9VaU3vyACH/view?usp=sharing

I probably should've just started with that but was curious how it was calculated. The guidance isn't super explicit that the calculated ratio is a byproduct of transmission gear ratio, final drive and tyre size (although they all make sense). Normalising against 5th gear, which for the CD009 is 1:1, actually came out to be pretty close to the calculated vs actual gear ratios so it all worked out.

The gear ratios of a CD009 are widely available so I can provide them, but given the gear detection is based on rpm vs speed does it not also depend on the final drive ratio? Just trying to wrap my head around it.

Yeah, looks like I'm able to report on most of the Link's statuses, excepting 1 and 2. I'll keep playing around with the custom setup all the same. Probably more curiosity/learning at this point.

Thanks @Vaughan. Oh yeah I realised it should be 688 for my SKU but wanted to use your example to confirm the decimal question.

Thanks Vaughan. A couple of questions, when converting 0x2B1 to decimal I get 689. Octal comes out at 1261. Do I use the latter? Also, is it okay to configure both Lambdas parameters in the one stream, or do they require unique streams?

So Haltech were very forthcoming: Do you have a crash course (or something more detailed) in how to turn this into something we can use?