cj.surr

+1 If not in virtual logic, it would be nice to at least have functions available for log viewing and dash gauges. For example, I would like to be able to log/gauge AFR error (afr - afr_target) or water injection flow ({water pressure - map} * coef}).

As far as I can tell, this is not possible with the G4+. It would be nice if there were a few options for smoothing sensitivity on analog input signals to suppress noise and spikes. For example, my water injection pressure sensors that are being driven by a 20hz solenoid, I can see every time the solenoid opens (150 kpa spikes - see image). Another sensor I am planning on adding is exhaust manifold pressure, and I am anticipating I will have the same problem. Thanks

I was referring to using the main RPM limit as a safety for additional parameters, as was suggested below.

Ok, that's what I was thinking originally... So I still have the question - why does using "cam level" cause an erratic engine rpm reading, when "cam pulse 1x" seems to work fine (but shows errors)? Thanks

Thanks, I wasn't aware of that difference. I will try the S52 and M52 settings. I am not sure how this would be any different than a generic 60-2 and cam level sensor though? I don't understand what the "cam pulses" means. I believe I turned cam test on, then disabled the vvt control and I was able to get a solid reading of 290deg so that's what I set the trigger offset to. But, like I said, this was with "cam pulse 1x" in trigger 2 settings, because "cam level" caused erratic engine rpm. So like Adam said, I think this is why I was getting the cam error. So Aux 3 that my cam is on should be set to "vvt cam solenoid" instead of "cam-switched" if I am using VVT control, correct? Yeah, it works fine with the Link (I've tested it), it's just a basic solenoid valve. I would bet that it could be driven with pwm for variable control, but I wonder if the lifetime of the valve would be compromised from the rapid open/close. Thanks CJ

Trigger 2 has always been set to rising edge. I took the cam angle from "Intake/LH" parameter and put it into the offset in the "Trigger 2 VVT" menu. I am not really sure what the purpose of that angle setting is. I recorded a handful of trigger logs (attached). I can't figure out how to view them without being connected to the ecu to open the trigger logger. They looked OK at quick glance when I was recording them. I also have the datalog from when I took the trigger logs. I tried the S52 trigger pattern with the same crank angle offset and it wouldn't start. There were some weird settings preloaded with it that I changed to my current settings and it didn't help. By default it had the 1/2 triggers as reluctor/reluctor (stock is hall/optical). Also the crank angle offset was 275 vs the -325 that I found. I don't know why these would be different, my 60-2 wheel is the same that is on all of this style engine. There is only cam phasing on the intake cam for the S52B32. It is controlled with a simple ON/OFF from the ECU. The cam phasing was not continuously adjustable until the next generation dual Vanos M54 and M52TU. I have those settings because I want to tune without VVT first, then add a 4D map to trim fuel based on cam angle because the Vanos is slow to react and makes a big difference in VE. 1-2deg is not signficant in my mind, I'm sure that's just from slop in the helical gearing of the Vanos. It will advance over 20 degrees, IIRC. Should a simple ON/OFF VVT be configured in the VVT settings at all, or just in the aux output? I was kind of confused by that part. Obviously there should never be a square wave going to the solenoid. The S52B32 is indeed half moon, but not infinitely variable, and only one cam has VVT. The M52TU is in fact infinitely variable, but that's also a dual VVT motor. So which setting should I be using? Like I said, chosing "cam level" causes an erratic RPM signal. Log 2019-07-3 12;25;54 pm trigger test.llg Trigger Scope Log 2019-07-3 12;24;46 pm.llg Trigger Scope Log 2019-07-3 12;25;00 pm.llg Trigger Scope Log 2019-07-3 12;25;08 pm.llg Trigger Scope Log 2019-07-3 12;25;15 pm.llg Trigger Scope Log 2019-07-3 12;25;20 pm.llg Trigger Scope Log 2019-07-3 12;25;31 pm.llg Trigger Scope Log 2019-07-3 12;25;42 pm.llg

Car is down for maintenance, I won't be able to get one for a few days. Trigger log looked fine to me. 60-2 wheel has no faults. Cam sensor had a sharp square wave and 50% duty cycle, once per cam rotation.

It is possible to convert duty cycle to an analog voltage (to be measured by the Link) using an external circuit. I am not sure about such a low frequency as 5hz, but it's likely possible with the right components. https://www.codrey.com/electronic-circuits/pwm-to-voltage-module-v1/

The engine is a BMW S52B32 US. I am using an M54 camshaft sensor because the stock one is not a standard vr/hall. It seems to be working well - trigger logger shows what I believe is a "cam level" style - high for one rotation, then low for next rotation. Cam angle #1 shows the proper angle and I have that offset in the "trigger 2 VVT" menu. However, if I set trigger2 to be "cam level", i get a lot of noise on the rpm signal (~100rpm jumps several times per second). Filtering did not help much. When I set trigger 2 mode to "1x cam pulse" my rpm signal is perfect and cam angle still shows the correct value. The "inlet/lh cam error counter" does increase about +1 per second with either mode. It seems like everything else is working fine, I'd just like a way to confirm that the engine is actually firing the injectors sequentially before I spend the time tuning the fuel map. Also, I don't think it's related, but I had to set my trigger 1 to "falling edge", even though it goes high when there is a missing tooth. If I use "rising edge" I get occasional blips to sky high rpm randomly. The timing was checked and adjusted. I had to change the ignition delay down to 60 us (e36 base map was 115! - caused at least a few degrees of retard) to get the timing to be consistent to redline. I attached my tune and a driving log with those settings Thanks! E28.pclr Log 2019-06-28 11;55;02 pm.llg

Have you checked that all ignition outputs are wired to the correct coils? In other words, doing an ignition test on coil 3 actually fires coil 3 and not another coil. If this is wasted spark, then my comment doesn't apply...

I don't think you can set a delay on the main RPM limit. And even if you could, you wouldn't want that. That's your main RPM limiter. +1 to improvements in the engine protection side. At least a couple extra GP tables would help a lot. I'd rather see tables with the Z axis being your protected variable; with engine protection coming in if that variable is exceeded, with a delay for engagement and disengagement. Doing that would allow for user defined variables on the x, y and z. But I realize that it would be a lot of work to go away from RPM limiter method. Also, I am missing the AFR Error (Actual - Target) parameter that I am used to on other ECUs.

Wouldn't there be an issue with using the main RPM limit with an input such as fuel pressure? I could see that a small, momentary dip in fuel pressure would cause the limiter to be activated. And when the fuel pressure returns, the limiter would be very quickly deactivated. In other words, you would want a delay for entry and deactivation of a limiter based on any analog input. I haven't tried this, but I would like to, which is why I am curious. I see that using a GP limit allows for a delay and "Exit Decay Rate" that could work those out.

OK, thank you.

No, it goes to pin 14 (I think - I can't find the numbering scheme) on connector B. It is labeled as N/C on the wiring pinout.

My harness has a blue/white wire that does not show up on the pinout. Is this an 11th Digital Input? Thanks

I am trying to drive a PWM water injection solenoid that draws about 4.75A max. It would be rare for this output to see more than 50% DC. Aux outputs are only rated for 2A, Injector outputs are rated for 5A but I am not seeing the option to use them as a general purpose PWM. Is there any possible way to do this? I'd rather not set up an external transistor. Thanks

I'm seeing now why that limit is there... 500hz max frequency. Is there an internal fuse for the +5v supply? I just got my unit in and I don't like how the +5v wire is split to go to different sensors right near the ECU connector. Unless there is an internal fuse, then that would be alright.

Also a comment... I am configuring a turbo speed sensor for a Borg warner EFR. Per the manual - The divider for the EFR sensor is 8 That gives me 6000 * 14 Teeth / 8 = 10,500 PCLink is telling me the max value is 10,000. The limit close enough for my sensor, but doesn't make a lot of sense.

Ah, got it. Thanks!

I have been reading that Virtual Aux can be stacked to gain additional conditions. I am planning to have multiple levels of engine safety and I believe I will need to stack multiple Virtual Aux. However, when I am going through the available switch conditions, I only see Virtual Aux 1 as an option. I believe I will need at least one more Virtual Aux to be selectable as a switch condition. Am I missing something here or is only the first Virtual Aux meant to be stacked? Thanks CJ

How long will the battery on that tablet last in sleep mode? It would be nice if you could wake it from sleep and have PCLink already running.