dynoiasi

It looks like before going lean you are going much richer than your target (while letting off throttle and immediately when pressing again). If you have closed loop lambda this might lead to very big negative correction which will show up as lean in the following moments. Please excuse me if this advice is stupid, but I am still a Link ECU beginner, however I guess checking your CLL parameters on the log would not hurt. By the way, if you say you want to get rid of the fireball, shouldn't you be concerned with the rich area instead of the lean one? Regards, Florin

Regarding your last answer Adam, maybe you could add the feature of switching map tables (or other inputs) from the user interface to the wish list? For those who have installed a tablet with PCLink inside the car it would make more sense to be able to "simulate" switch actions from the software, rather than wiring and installing mechanical switches to do the same thing. I guess a generic approach where all digital inputs might be assigned to a "software user interface panel" would be worth considering. Just a suggestion to improve an otherwise very good system / software. Best regards, Florin

Many thanks for your opinion Adam. I did not know about the bumps in the road causing false positives and I was wondering why in my log there are very rare but big noise spikes while engine has basically no load. Maybe this might be it, since we certainly have a lot of bumps in this part of the world... One more thing: for me the best way to discern whether some noise is real knock or not, would be to see that after the knock control timing intervention the knock went away on the next stroke or at least it reduced the amplitude. Can you see this on a log? As much as I found you can only see the knock ignition trim tables per cylinder but they are "static" in nature. There is no real time parameter that shows the ignition trim due to knocking but only other ignition trims. Is this true? Best regards, Florin Tufescu

Thanks Adam, with your blessing I created a new topic and uploaded the log file. I had to compress it however since the maximum upload file size is 9 Mbytes. Best regards, Florin

Hello everybody, Since I have not finished yet my DIY "detonation listening device" I made a few runs using only the engine knock sensors and very conservative tuning, trying to spot knock signal waves on the logs. To my surprise I found a few spots that look a little suspicious which I would love to hear your opinion about. It's hard to believe that this might be real knock considering the crazy rich AFR and the low timing but still I would bring these to your attention. My engine is a M50TUB25 with about 9.5:1 compression and a smallish turbo. Problem 1: There's a small spike on cyl2 knock level. It settles back and then rises again along with the boost pressure. Might this be knock, or knock should be an even bigger spike compared to the previous average noise? Problem 2: The cylinder 2 noise seems to raise pretty suddenly but the cylinder 6 even more so. I think that cylinder 6 might be caused however by the RPM cut which happens at the exact same time but I am not quite sure which happened first. I also attached the base map and the log file. The first problem is in the SOL section, the second one in the rpm cut section, timestamps should match the attached screenshots. Thank you very much for you help! Have a nice day, Florin dinmasinapolizuiasi.pclr Log 2019-03-31 6;32;48 pm.zip

Hello, I would like to post here my base map and log in order to get some opinions on the logged knock sensor signal. However I have 1 hour log file (about 20Mbytes) and I don't want to make people that want to help me download so much... So is there a way to trim a part of a log? I know how to create sections, I see that you can export just one section, however if I use export it will output a .csv file format. I guess this is not as good for viewing as the native .llg format. Can I output just part of a log in .llg format?Thanks! Best regards, Florin

I was not aware that the S50 has variable valve timing, thanks!

That is really good news,plug and play is always nice What got me confused was the fact that the "Cam control mode" in the VVT settings also has the possibility to choose "BMW single vanos", like there is still the possibility to control it via the VVT. Maybe it was just experimental?

Thanks Adam for your input. I'll have to look around the engine to find whether there is a reasonably easy way to mount a third sensor. Alternatively, do you think that temporarily connecting just one of the sensors to the Link ECU and using the other for my amplifier would be a reasonable approach? I am not trying to squeeze the last drop of power, so I would suppose that the detonation would occur roughly at the same time on all the cylinders. Would the Link ECU get a smaller overall noise if using just one of the sensors (by half maybe) which I could adjust later, or would that throw an error and completely disable the knock sensing? Thanks! Best regards, Florin

Hello everybody, I have a Link E36 plugin ECU running on a turbo M50TUB25 BMW E36 (single Vanos). Even though I read what some might consider a lot through the help files and through these forums, I am still uncertain whether vanos control works out of the box with this E36 plugin ECU or I need to do some wiring modifications. I see in the E36 base map that comes with the Link software that AUX 3 is configured as CAM-Switch, I see in the logs that it is commanded as expected (ON between 2500 and 4500) and to be honest I think I feel something in the car dynamics at those exact thresholds. These lead me to believe that everything is setup and working. On the other hand I see that VVT is turned off in the configuration file... does VVT refer only to more complicated proportional control of the cam position? Also, I remember seeing somewhere in the help file that you need to modify something to the vanos wiring, like adding/removing some diodes... However I can only find again that information for the double Vanos engines.... To sum things up, I would really appreciate if someone could clarify: is wiring modification needed for the M50TUB25 single Vanos engine to work with the E36 plugin Link ECU or is everything ready to go? Thank you very much! Best regards, Florin

I was thinking of using the fuel consumption signal for this (aux 4) but I guess throttle valve position is a better idea, since using the ASC on a turbo build E36 is unlikely (due to lack of space...).

Hello everybody,, I have a Link E36 plugin ECU controlling a turbo M50TUB25 E36 BMW. I am almost done with the fuel tables and moving onto ignition tuning so I have some questions regarding the specific configuration of the knock control for this engine. I saw that the help files recommend some frequency settings for certain engines, but no recommendation for the M50 engine. So first question is, could someone tell me what type of knock sensor should be selected, what frequency and eventually the rest of the knock control settings? In case I can't find an answer to the previous question I plan to also listen for engine knock, so I also search for advice on this one. My plan is to build a simple audio frequency preamplifier/amplifier and listen with headphones. The problem is that I would like to keep the ECU connected in parallel to my audio amplifier, so I need to know what should be the input impedance of the amplifier in order to not affect the input to the ECU too much. My guess is that something like 100kohm should be fine, am I correct? This is a question to which I hope I can get an answer from the Link ECU hardware engineers, for which I thank them in advance! Best regards, Florin

Hello Tye, Did you manage to configure correctly the knock input? I have the same ECU/engine as you do, and after initial basic tuning of the fuel table I want to move on to ignition mapping. What frequency did you select for the M50 knock sensors? Any help with the configuration would be greatly appreciated. Thanks! Best regads, Florin