defjux23

First things first, please ignore the knock target table being set oddly. Second things second, why does the knock level seem to stop working about a third of the way into the log? Files: https://drive.google.com/drive/folders/1ZQBVC4W3GBIexqa0mXo2B952G5KlY1O9?usp=sharing Thanks! Dan

Thanks all for the information! Dan

Hello! Would someone be able to explain what the following CAN Outputs are when using an AIM Dash? Limit Flags LSB Limit Flags MSB Thanks! Dan

Thanks, I'll adjust! Dan

Hello! I am having an odd idle stumble on warm-up that I am not sure where it comes from. Something is pulling e-throttle closed and I'm not sure what. Any thoughts? Idle is lovely otherwise. Dan E-Throttle Test.llg Idle Stumble.llg 9.25.22.pclr

Thanks!

We updated the firmware and the turbo speed would read for a few seconds and then go to zero. We grounded the DI- and no luck, same issue. By happenstance, our mechanic held the DI- wire in his hand and all of a sudden the turbo speed started to read properly. After talking with an electrical engineer friend, we decided to try the smallest capacitor we had, 104 picofarad, from DI- to ground and now the turbo speed reads properly. Thoughts? Dan

Sure enough, we were out of date. We will update. Thanks! Dan

Hello! We are working on getting a downshift blip for our Mitsubishi Evo Time Attack car and wondering if there are is a good starting point for Overrun Down Shift Throttle Trim values. Thanks! Dan

Adam, We've switched and not getting any reading from either DI 15+ or DI 16+. We switched back to DI 3 and it worked as expected. We've ensured we turned on the new DI to Turbospeed and disabled DI 3. Any thoughts? Dan

Many thanks!

Adam, Bringing this back from the dead. We are wanting to move the turbospeed to DI 15. Do we run the input to the + and ignore the - or do we ground the -? Thanks! Dan

Thank you for the update. Just wanted to confirm, we would like it though if APS could be used so we can leave on silent throttle. Thanks! Dan

Has this been updated for e throttle? I can't see an update in any firmware releases. Thanks!

Thanks for the additional information.

I'm concerned about two things, obviously it's possible with our setup to over-advance. We are looking into a mechanical solution to stop that. Second, damage to the phaser when turning on/off the test and opening the base offset window. Perhaps we've wired something wrong on our end, but something in the solenoid/phaser area made a very strange noise while turning on and/or off the tests. Maybe it was just the valves contacting the pistons. Unfortunately we can't be quite certain.

Would you have an order of operation to be as safe as possible to not cause any over advance? I assume it would be 1) Turn off VVT. 2) Set Base Offset. 3) Shut off Engine. 4) Enable Cam Test. 5) Start Engine and find cam offset. 6) Set cam offset value. 7) Shut engine off. 8) Enable VVT. 9) Start engine and we should be complete. Correct? Any other words of advice?

When vvt is enabled after the test is done, would the activation of the solenoid possible cause the cam to fully advance?

To be a bit more specific. When turning on/off the Cam Angle Test and opening up/closing the Base Trigger Offset window, does the VVT solenoid get activated in a way that could advance the cam timing? Thanks in advance!

What's the best way to utilize the Cam Angle Test to set the Offset... or better yet, what's the best procedure for setting up VVT in general? Can activating the test while the engine is running cause the solenoid to advance the cam? While preparing our engine for the dyno we turned on the Cam Angle Test and noticed an awkward sound and our intake valves touched the pistons. We noticed the same sound when using the set base trigger offset as well. VVT tables were all zeroed.

Thanks!

Hello all! I have a Garrett GTX3582R Gen II turbo with a 10 blade compressor wheel. According to Garrett, their turbospeed sensor outputs at 1/8th input frequency. Using the Link provided equation, I set my calibration to 7500 and now turbospeed reads extra high on our AIM Dash, for example 93 rpmx1000 at idle. I've checked my CAN multipliers and everything is set to 1. Seems like everything should be right, what am I doing wrong here? Dan Evo Before Dyno.pclr LINK_Pro Awe Thunder_@20190316_075205_007515.xc1 PDM32 Pro Awe V1.7.zconfig

Adam, Would you be able to add Boost Target from the Link CAN Output? That way we can confirm we are trying for the right target on screen. Thanks! Ended up figuring this out on my own. The one thing we noticed is that with our sequential transmission, neutral is no longer labeled as N and reverse is no longer labeled as R on the AIM display. Now they are labeled as 11 and 10 respectively. Would the custom CAN XC1 cause these changes? Thanks! Dan

Beautiful! Thank you!

Many thanks! What's the best way to go about using 0,1,2,3,4 to match my desired boost levels? Forgive me, I am completely new to boost control management with the Link. Also, is there any workaround to see the PWM output for our water pump on the display? If not, not the biggest deal, but it would be nice to confirm we are in the desired state on track. Thanks for your effort!