cbDrift

I've saw a Plazmaman air to water intercooler (generic) kit - the end tanks would need fiddling to suit the turbo outlet and intercooler placement - but its do-able: https://plazmaman.com/product/wrx-96-99-pro-series-intercooler-kit-2/ I also saw the FMIC from Process West with an interesting end tank design: https://processwest.com.au/product/282/ I was hoping to find a fabricator to advise about end tanks like this, that could be used to recess an FMIC closer to the radiator and not interfere with the crash bar. The rules don't say you cant modify the rad/hood latch supports or front panelwork between the chassis rails or behind the crash bar The Plazmaman stuff flows well and could work up to any hp level I'd ever reach on a street car - but a FMIC with the Process West design could be a lighter option? Thanks heaps for your input I'll check with Plazmaman and see what sort of cooling they can do at 2bar worth of positive input pressure going into it, if they flow so well, air may pass through before being cooled enough?

I've got the nice link plugin - tick i've got the nice "supporting mods" upgrades (fuel pump, injectors, turbo, intake, exhaust) - tick But a cross for - the heat soakable top mount intercooler.... It needs to be replaced, but the laws here in NZ prevent the *factory* front crash bar removal or modification :\ Cant insure a roadcar with illegal mods either :\ There is an exception being considered to our rules here tho, but its not a "live" rule, yet... The cert guy i was talking to mentioned this was talked about in his last training session - so i have some hope... Anyone in NZ know an engineer somewhere they would recommend, that I could talk to about this? Anyone, anywhere, know of an FMIC that would retain the front crash bar at all? I'm very happy to take this to pm's or to another forum, but with all the plugin g4x v11 people in here i just wanted to get their attention / input.

Thankyou yet again!

@OrgDawg Hows the dash going? Did you get it all working in the end? If so - what did you do to make it happy - and does it display all the channels you needed etc?

Sorry to reply to a super old post - but I would replace that iat sensor with a gm style one - my old honda used those plastic sensors as well, and the sensor body can heatsoak from a hot engine bay and affect your iat reading, making the ecu think the air temp is way hotter than it really is. The gm style iat keeps the sensor and the body/plug bit separate so that heatsoak in the engine bay isnt an issue - and solved the flakey readings the ecu was seeing from the factory plastic sensor for me. sensor location was in a rubber intake pipe, i suspect if you had the sensor mounted in an alloy intake tube it would still heatsoak - but the gm sensor should still be less of an issue than the full plastic one. on my k series both sensors had the same callibration data so it was a straight swap.

Having a user selectable option to auto start pc datalogging when connecting to the ecu - or having pc datalogging turned off as the default when connecting to the ecu would be cool. I drive everywhere with a laptop connected for datalogging stuff, and it annoys me when I have forgotten to start it and something happens that i wish i could have caught. I have not found this in PCLink Version 7.2.3411 from Nov 30 2023 build.

With people commenting about it in the g5 forum, its probably on a list somewhere already - but I didn't see it in the wishlist forum so I'll add it in here anyways -Being able to see the serial number for the usb connected ecu in the "search for ecu" box would be cool - currently it just reads 0's for me on my ecu -Having a button to say "set as default ecu" in the search box for people who only have one ecu they will tune and don't want to have to select it every time the app starts would also be very cool. -Have a menu option under the "ecu controls" menu to select the default ecu from anything PCLink has connected to. -Have another menu option to clear the default ecu setting as well. -If pc link "sees" the default ecu in the list of connected ecu's available to it when it does the "search for ecu" - just connect to that with no dialog box popup. These are not currently in PCLink Version 7.2.3411 from Nov 30 2023 build

mine did that when the canbus / ecu can modules were not initialising correctly, the developer discord was helpful and at the time i emailed the powertune mailbox and the dev had time to remote in and sort it out for me, a broken config file and missing canbus module file from memory that the onscreen menus didnt sort out. there was a script file he ran to re-download all the canbus modules, reset the options to select the newly downloaded can module and it was away laughing again. the onscreen menus didnt show any errors - it just didnt display any can data. theres some error logs you can view but you need to connect to the dash with a terminal emulator and trawl through things with a command line. it is a super cool and very hackable dashboard, but i ended up selling mine and going over to a haltech dash for the haltech ecu i had on my old honda because it couldnt display all the same stream info as the ic7 - back at that time - it probably can now im guessing, but other small niggles put me off it (afr and target afr used different scales, no cam angle target display, glitchy rendering of data under the dial gauge sweep needles, needing to recompile my fixes and hacks every time they updated the firmware) and the ic7 just worked outa the box due to coming from the same maker as the ecu. not really an option for most but if i do get a digital dash sometime for my link ecu, i'll get the link dash

so i was poking around in my datalogs and discovered the "knock level global" and "knock level detected" values the link ecu does windowing and filtering and we have the very nice per cyl "knock table level" values to refer to the manual says the knock level global is a general value of all knock levels combined and knock level detected knock level global minus knock threshold value in my datalog i get knock table levels far below the set threshold level but i can get a knock level global reading above the threshold level and a knock level detected value thats positive. i dont have my audio knock gear handy at the moment (yay messy storage units) - so going only off datalogs, how much weight should i give the global and detected levels if the table levels are well below the threshold value? context : had it tuned on the dyno perfectly with no knock by the workshop - super happy with the results - then I went and upgraded the turbo since the tune and have removed some timing so i didnt get spikes above the threshold but after viewing the "newly discovered (for me) global and detected levels" and not having my knock gear handy im wondering if i should continue to trust the table levels or nuke more timing based on the detected level? the left hand red highlighted bit seems to be sus but the right hand one has a spike when the table values are down relatively speaking.... neither went above the tuned threshold its going down to the dyno again next weekend and these spikes only appeared after i started to wash out the 100 octane to get back onto to 98 octane for the upcoming tune. i get it tuned on 98 (with this time also getting a flex fuel tune with a blend of e100) and normally run it on 100 octane to have a "safety buffer" over the 98 it was tuned on - and that does quieten down the detected table level readings - but then i "discovered" the global and detected datalogged channels aircon was not switching off or on at the time - and the downpipe from the turbo is *very* close to the firewall after the turbo change (i guess it really could have used a few more smacks with the clearance tool) - so should i watch the table levels - or the knock detected stuff until it gets back on the dyno next week?

I know Adam spent quite a bit of time daily driving a GRB to get the "base map" setup - and sort out canbus stuff so that things work. I was wondering if there is a list anywhere of things that "match" the features of the factory ecu - or dont match - or work different... Eg - the SI drive knob in a factory ecu changes how the diff controller works and boost curves etc - in the link you can assign that can input of the SI drive knob to functions - but does things like the diff controller take that as a can input and use its own maps for things - or does the factory ecu take the SI drive input and controls the response of the diff controller. What does the auto/manual switch do on the link and what does the traction control button do in its 3 modes on the link? Boost im not worries about thats easy to sort - but i was wondering more if the SI drive knob still made changes to factory controllers - or if the link ecu only has one "setting" that it sends out to the controllers? I might be badly wording this but if someone can understand my gibberish and point me at a "link handles these things these ways for a v11 plugin and these things are done different from factory ecu's" that would be epic. ... Or if our favorite overworked person, Adam, can put up a blurb about it as I am very curious to know how the interface between the link ecu and the diff controller works Thanks in advance to anyone who knows and can reply - I am notoriously blind and bad with google-fu about things so theres a good chance if the info exists - i've not found it so i dont mind being called a dummy if someone points me in the right direction

Thank you so much for the reference to study and the "dummies guide to adding tables" for me Greatly appreciated thank you!

I see that on the cold start page - there are multiple tables - but if i create a new page - i cant add tables to it and it only displays one table when i choose something from ecu settings. in the help file it says ctrl-f12 to add a new table graph - but this does nothing, where the other view shortcuts work and open an editor for that option. I want to make a new page with a few different tables on it to allow me to finetune some things and have a compare working at the same time so i want larger table views than the cold start screen. how can i do this - its gotta be something simple that im missing right?

Hey Adam (or anyone else who knows the answer and is not guessing at it like me) I'm just about ready to send my GRB (cold air intake, tmic, injectors/pump, exhaust) down to the dyno shop i love the most, to get the boost controller setup and take it off wastegate only, and give it a proper retune after fitting a new turbo and had a couple of questions about the base map settings and tables if you have a moment. Is the "Charge Temp Approx" table for the base map setup setup for a factory top mount or did you do your dev work with a front mount on your test mule? Also the "Fuel Charge Cooling Coeff" of 15% in the basemap - is that an arbitrary number or was that what worked out to be perfect for NZ BP/Mobile 98 octane? Would you know offhand if NPD 100 is going to be significantly different for that setting from 98 fuels and require a change at all? I'm not planning on running any Gull, or ethanol in the car for now and want a 98 tune and then run it on NPD for that extra knock prevention (sorry to everyone outside NZ - these are questions for fuels we get here - not sure what you guys have on pump anywhere else) And randomly - my question a while back about the afr changing and being leaner on the road in lower gears under full load (7% leaner in 1st compared to 5th) and was there a per gear fuel correction table available (i made one for onboost vs rpm in the end) , was mostly sorted by changing to ID1050xds injectors and using the plug and play data for a g4 ecu - now its muuuuuch closer in 1st than the old (larger) injectors I had installed last time it was tuned and when I asked the question.

Hiya, does anyone know if there is a way to do fueling correction per gear - not just a single value percentage change per gear, but a small table (even 8x8 is useful) per gear of a percentage change for fueling? I come from a haltech background on a honda k series and now ive finished with that, im in a turbo with a link and i'm wondering how to be able to correct what i see on the wideband vs the target fueling like i could with the haltech If you floor it in first and run through the gears on a dragstrip or motorway onramp - first gear logs as not getting close to target fueling till after 6k rpm, second is better, 3rd closer again, 4th where the car was tuned being great... how much of this disparity in lower gears is the timelag between rpm going up quickly - and the exhaust gas getting to the sensor (just after the turbo in the downpipe) ...or is the logging accurate - and the engine is actually running (sorry not lambda) leaner than 13:1 on pump gas with over 100kpa of positive manifold pressure in it? seeing i have a subaru - internet legendary for letting the pistons go when you dont want them to - i'm a bit worried about this. on the haltech - there was an 8x8 correction table per gear, and it made a huge difference in power output (butt dyno said "awww yeah" tyres did not) in the lower gears, and the logging showed that fueling tracked more accurately to the targets in all gears after it was setup. i cant see how to get the same sort of deal with the link system tho, is there a way to do this? I'd like to be able to do (rpm vs load or tps) with the table holding a percentage correction to fueling - one table per gear. and finally - i see there is a counter in the stats screen for the number of stores - the haltech was a realtime store with every change when you were connected - the link is a write the differences type deal when you tell it to (both systems have their good and bad points) is there a limit on the number of stores you have before the link ecu will start getting failures with writes? theres some stuff i love with the haltech i had, over the link, theres some stuff i love with the link over the haltech - its a learning experience and a half

Awesome - thank you heaps for that