RobinHodges

Hi Adam. Thanks for the tip! It's working, but I think I've found a bug / interesting behaviour with my setup. After re-initialising the table, it sets it up as a 3D table (with RPM and MGP(or MAP?) as the axis). Filling this in with waste gate DC values worked. The actuator pulses. I then made it a 2D table (RPM only) then it stops working. It seems you NEED the second axis. I'm happy enough with the 3D table - but it would be good to understand what's going on here. What I did notice is that when you go from the 2D table to a 3D table (press X and add the pressure axis), the 3D table top row is filled in with the DC values from the 2D table, and the rest of the 3D table is 0. The running point on the pressure axis is such that the 0 values are being accessed. Then of course when you set the whole table to non-zero values at the running point, its working. This implies that the 2D table I'm looking at is actually the 3D table, but only top row showing? (with the rest of the tale = 0, hence my DC values are not working). Thanks, Robin

Hi guys. So I've updated the firmware this evening on my G4x Storm (version 6.17.8), and also PC Link (6.17.22). I repeated the open loop boost control test. Sadly WasteGate % DC 1 is still showing 0% even though boost status switches to "open loop" once MAP and rpm constraints are met. This isn't just a display issue. The boost pressure achieved is the same as with boost control turned off completely. Attached is the calibration file and a log file (zipped due to upload file size constraints). Please can you shed some light on this for me. Clearly I'm missing something simple here! Are you able to test my calibration file on a G4x Storm with the same firmware? Thanks! map_13_open_loop_boost_control_wastegate_dc_50.pclx open loop test 1.zip

OK I've just got back from running a test closed loop. The behaviour is similar to the open loop case in that the WasterGate % DC 1 table does not seem to get added into the outgoing wastegate DC command to the valve control (i.e. this feed-forward term is ignored, and I'm only running on the stage 1 spool up then the PIDs). Boost target was a constant 180kpa. WasterGate % DC 1 table was 50% all over. The PID behaviour looks ok (first time I've set this up, so of course it's not optimised). So in both open loop and closed loop cases, the values in the WasterGate % DC 1 table are ignored. Calibration file and log file attached. Thanks!! 180 target dc 50.llgx map_13_closed_loop_boost_test.pclx

Hi Adam. Here's a log from startup and idling for a minute or so. (don't worry about the high idle - I haven't wired in my idle control valve yet). Let me know what other tests I can run for you. Thanks. map_12_openloop_boost_test.pclx startup and idle for open loop boost.llgx

Thanks Adam. Leaving in the trim values of 100% in some places is my mistake. I was playing around with those to be sure they do what I expect once I saw the DC was 0. (i.e. do they add? - in which case I wanted them at 0, or are they multipliers? - in which case I want them at 100%. Looks like they are adders. ) I'll grab a log at idle in a couple of hours. Cheers.

Hi. I'm sure I've missed something simple here, but I can't seem to get the Waste Gate DC% to go above zero. The actuator itself seems to work when in test mode, but when driving the car I can see the WGate DC value is zero the whole time, even when all the conditions to turn on open loop boost control are satisfied (I think). The boost level I am seeing also indicates the waste gate remains closed. Boost Status goes from Off to Open Loop while driving, but WGate DC remains at zero. The help file referrers to Boost Status having more states than this, including RPM Lockout and Map Lockout. I can't see these states when scanning my log file. (my RPM activation was set to 200, so RPM Lockout will never show, but MAP Lockout should). Something's gone wrong! ECU: G4x Storm Firmware Version: 6.16.15 PCLink version: 6.16.26 Attached is a short log and calibration file. Thanks in advance. map_11_openloop_boost_test.pclx open loop boost test.llgx

Hi. I'm just starting to play with my knock sensor gains. (on my G4x storm). The PCLink help file states that the knock tables should be set to a maximum of 1000 (implying perhaps that the measurements do not go much above that??). My knock levels in my last log show values up to ~1600, and do not appear to be saturating yet. Obviously I want to set the sensor gain to maximise the sensor readings, while leaving plenty of headroom to actually capture the knock. So what is the maximum sensor reading allowable before saturation? Thanks in advance.

Hi guys. Just reporting back on this topic. So it turns out the trigger wheel had come loose. Don't ask! It's a sore topic in our house at the moment. After tightening it up, setting base timing and guessing some numbers for master fuel, it started up first time!! Woohoo! Thanks again for the advice so far. Now on with the fun part! Rob.

Thanks Adam. Good to know the overflow error isn't an issue. I have tried different master fuels a few times (from 2ms to a 20ms). Ignition coils are wired into the correct outputs. The first test last night was coil testing one by one, then the injectors (but without observing the flow - only tested by feel). One observation that I forgot to mention that could be really important is that sometimes on cranking it sounds like the engine jams (accompanied with a large voltage drop). Could this be attempting to fire at completely the wrong moment forcing the engine back? Could it be WAY too much fuel entering the cylinders causing some kind of hydro-lock (I hope not!). Sorry if this is pretty basic stuff. It's just so frustrating that I know what I should be doing with all the control tuning once the engine fires up - its just getting to that point! Thanks.

Hi all. I really need some more help to get this engine to fire up. (thanks in advance!) It's a M50B25TU single Vanos (if that changes anything about base timing). See trigger scope above, trigger sensors look 'ok'. Following review of my trigger scope, @Adamw recommended Sync Tooth = 1. Both triggers show active during cranking, no errors (or only when I stop cranking). I just fitted some VW ignition coils (built in igniters) that deliver a strong spark and these haven't altered the base timing at all. I just checked this with a timing light. Each coil pack fires a decent spark when tested (so wiring numbering correct, and they appear to be powered correctly). Injectors fire too when tested individually. I have tried to start with a trigger offset of -261 (the value I determined using the timing light, while locking timing to 0 degrees) and also 99 degrees (-261+360). With 99 it seems to do very little, but at -261 it spits and bangs a bit. The Master Fuel for the base map for the plug in 'BMWLink' ECU, is 20ms. My injectors are around double the flow rate (ish) of standard ones, so I have set Master Fuel =10ms as a first guess. I suspect a massive mistake made on my part with the timing, but I have no idea what that could be. I found TDC using a rod into cylinder 1, made a mark, used a light and adjusted the offest until I hit that mark while at 0 degrees fixed timing. Timing light sensor is clamped around a short HT lead with a small spark chamber (so you can see the spark) in it. So it's coil pack -> HT lead with spark chamber (+ clamp for timing light after spark chamber) -> spark plug. I assume clamping the timing light sensor after the spark chamber would not add any delay / error? See picture of the HT lead / spark chamber tester. I have attached logs for trying to start the engine with -261 degrees timing offset, and for +99 degrees. Also attached is the map file. Also I consistently get a Fault Code 8 - settings overflow. That sounds really bad - like the config isn't loaded properly. I'm using a fresh install of Windows 10, and the latest PCLink and ECU firmware (G4x Storm). Pleas also note I have a problem with my ICV at the moment, so those lines are cut and the system is inactive. I have cracked the throttle open to around 10% for both starting attempts (log files). Please take a good look at my maps and log files. There's something fundamental that's wrong here, I just can't figure it out. Thanks in advance!!! map_4.pclx start_attempt +99 timing.llgx start_attempt -261 timing.llgx

Thanks guys for the quick response! I have to say the help documentation is some of the best I've ever seen for a bit of control equipment. Keep it up!

Here's the section of the help file that states only the 1st tooth after the gap is used to check the cam sensor state: "·The level of the sync signal is sampled only on the tooth after the gap on the crank signal. This means that the level of the sync signal at other crank positions is irrelevant. For this reason a signal with more than one tooth can be used on the cam as long as the signal level is high at the tooth after the gap on the crank signal on one crank revolution and low on the next crank revolution. ·When the tooth after the gap occurs on the crank signal, if the sync signal is low, engine position is set to 0 degrees plus the trigger offset. If the sync level is sampled high on the tooth after the gap then engine position is set to 360 degrees plus the trigger offset."

Hi all, I have a BMW M50B25TU engine, with a VR crank sensor and a hall cam sensor. ECU is a G4x Storm. I'm hoping you guys can give me some tips on configuring my triggers. While I'm aware there is a base map for my engine for the G4x, I need to be absolutely certain my understanding of the trigger setup is correct due to a suspected misaligned crank trigger wheel. While making a mark with white paint where the TDC mark is on the crank trigger wheel (to use with a timing light), I noticed cylinder 1 was a long way off actual TDC (maybe 30 degrees or something). I've since made my own mark to use at real TDC. With this new TDC mark - I managed to establish a timing offset value of -261 degrees (not what's stated in the base map for my engine). I've included a screen grab of my crank and cam sensor outputs on the Trigger Scope. From other scope traces I've seen, mine is indeed offset (trigger wheel misaligned). I assume this isn't a problem - it just needs setting up! When it comes to setting up the cam sync, from what I've read in the help file I should be using Sync Mode = Cam Level. I think this is because I have a hall cam sensor (steady state voltage on a square wave). The question I have at the moment is what is the purpose of the Sync Tooth in the Trigger 1 setup? I thought this was where the ECU looks for a cam pulse (e.g. if you have a VR cam sensor generating a single short pulse). For Sync Mode = Cam Level, the help file indicates that only the 1st tooth on the crank after the missing tooth is used to sample the cam sensor state. So setting the Sync Tooth does nothing in this case?? I've no doubt missed the point here. Just to throw in additional complication, to ensure the Vanos cam angle shift won't affect things surely I want the ECU to sample the cam level pretty much bang in the middle of the square wave? (give maximum movement each direction) That would be roughly on the 20th tooth after the gap on the crank trigger. BUT - apparently only the 1st tooth is used? The map currently uses a Sync Tooth value of 49 which is where the cam level goes high, low. This was a stab in the dark and probably wrong. Clearly sampling here will be on the cam sensor transition, and not on a steady state value. Map, Trigger Scope log and screenshots attached. Thanks guys! (p.s. I am aware about the need for igniters with this ECU. Audi R8 coils standing by. I'll measure base timing again once fitted) map_3.pclx trigger_scope_2.llgx

Ok scratch that. It appears you assign the inputs by first selecting a function, then allocating the input pin.

Hi, Having wired in my G4x Storm, I'm just configuring the inputs. For some reason the analogue input settings appear to be locked (there is a padlock symbol on the right hand side of each config window for each channel). I have exhausted my Google search on this, and I can't see anything in the help file about it. Are you able to advise? Config file attached, and screenshot of the padlock symbol I'm referring to. Thanks in advance. I appreciate this is probably a very basic aspect of the software functionality, but I really cannot find the answer! map_1.pclx