Tuners Rejoice! Free Tuning For M4.4!


Recommended Posts

On 1/26/2022 at 5:13 PM, Chuck W said:

Looks like Aaron at VAST has a solution for me for the NB emulation. 👍

No worries, I've been a bit busy working on two way serial comms. Hooked into the tx and rx of both serial channels (so bypassing the single wire k line but still keeping it functioning for oem diagnostic purposes), so I can send messages to the ecu whilst logging at the same time for whatever purposes I need. Hooked up to an arduino and will be shortly adding sd card for continuas logging and bluetooth for wire free comms and flashing (another useful thing also would be wire the bootloader pin to a relay controlled by arduino so flashing could be done without having to manually flick a hw switch). Serial chan 0 is working fine for flashing and logging etc but having trouble with serial chan 1, but it only supports 9600 baud anyways so not a big loss. My aim is to hopefully free up a decent chunk of xram so that I can tweak certain table values on the fly without having to use an eeprom emulator (hence the need for two way comms while logging to make it alot easier to use). 

Link to comment
Share on other sites

5 hours ago, Midnight Caller said:

Yeah, I totally recommend Aaron. He's doing a great job, aaaaand most important, answering all my e-mails :)

Yeah, I've worked with him before. Solid guy.
He messaged me after my post about this. Just gotta get the other ECU soldered up and everything installed.

Link to comment
Share on other sites

On 12/10/2021 at 11:58 AM, Midnight Caller said:

Yes, Kline is pin 5 on 4.3 and bootpin is 8. Just wondered if anyone used Motronic Flasher for 4.3 too.

 

Did you ever figure this out?

I was messing with this some today, just for kicks. I have a couple extra M4.3 ECUs (-072) and I was seeing if I could write to them.

I can get it to complete a flash (Writing the -628 bin in Motronic Suite) using the flasher in Motronic Suite, but I can't get it to connect properly with my Motronic flasher I have set up in Tuner Pro (which has worked fine for all of my M4.4 flashing). 

Link to comment
Share on other sites

10 hours ago, Chuck W said:

 

It's a slightly modified version of the Motronic Suite flasher with the command line capability added, but whereas it still supports M43 normally - command line only flashes for M44. 

Edited by jenksta
Link to comment
Share on other sites

1 hour ago, jenksta said:

It's a slightly modified version of the Motronic Suite flasher with the command line capability added, but whereas it still supports M43 normally - command line only flashes for M44. 

So, flashing the M4.3 bin in Motronic Suite is doing the same thing then?

Link to comment
Share on other sites

2 hours ago, Chuck W said:

So, flashing the M4.3 bin in Motronic Suite is doing the same thing then?

Yep just saves you a few clicks by TP feeding it from command line params, just don't forget checksums after modifying the bin 👍 

Link to comment
Share on other sites

On 1/29/2022 at 4:16 AM, Chuck W said:

Did you ever figure this out?

I was messing with this some today, just for kicks. I have a couple extra M4.3 ECUs (-072) and I was seeing if I could write to them.

I can get it to complete a flash (Writing the -628 bin in Motronic Suite) using the flasher in Motronic Suite, but I can't get it to connect properly with my Motronic flasher I have set up in Tuner Pro (which has worked fine for all of my M4.4 flashing). 

I used Motronic suite in the end for flashing, there was an issue with an 850R bin (also taken from motronic suite) that caused a no-start condition on the car. I re-flashed an 850 T5 bin and everything was ok.
Reading the software from the ECU with motronic suite apparently failed somewhere because even if the software appeared "legit" to WinOLS and Motronic suite, the maps were somehow f***d up (rpm limiter was set to 1.024.000 or smth).

Link to comment
Share on other sites

5 hours ago, Midnight Caller said:

I used Motronic suite in the end for flashing, there was an issue with an 850R bin (also taken from motronic suite) that caused a no-start condition on the car. I re-flashed an 850 T5 bin and everything was ok.
Reading the software from the ECU with motronic suite apparently failed somewhere because even if the software appeared "legit" to WinOLS and Motronic suite, the maps were somehow f***d up (rpm limiter was set to 1.024.000 or smth).

Thanks for mentioning that there were issues with the MS bins.

I did a quick check of the -628 I used from that, and sure enough, there is something wrong. The rev limiter looks fine, but there is something weird with the major axes.  I did a quick look at an -072 one, and those were wonky as well.

Link to comment
Share on other sites

16 minutes ago, Midnight Caller said:

My experience was with the only T5R BIN from the Motronic Suite. I can't recall right now the suffix but I know that the car didn't start and there were no errors in the ECU.

I'll take a closer look when I have time later. I was looking at these MS bins (-628 and -072 (US-Spec R and T5)) in TP using the VER 0.9.1 XDF that had been up on the M4.3 Wiki. I didn't have a chance to see if things were the same in MS.

Edited by Chuck W
Link to comment
Share on other sites

Just in case it bugs anyone else like it did me, I had an issue where the pre-start listener would be hit and miss when sending commands (such as the begin logging command, which meant I'd start the car, see it wasn't logging and have to turn it off and repeat).

 

Whilst looking at something else I found out that while the OBDII/OEM diagnostic stuff is disabled by the prestart listener as it overrides the serial port settings - there is also code that manually checks the serial port for the 5-baud KWP init (which consumes the byte we send before the pre-start listener has the chance to). So to fix the issue above I knocked up a little bit of code to disable this if pre-start listener enabled.

 

@ 0x1B67E place the following (jump to custom code):

0x02, 0xE9, 0x03, 0x00, 0x00

 

and @ 0x1E903 place the following (custom code, existing bytes should be all 0x02):

0xB4, 0xFF, 0x01, 0x22, 0x90, 0xFD, 0xCB, 0xE0, 0xF5, 0xF0, 0x30, 0xF3, 0x03, 0x02, 0xB6, 0x84, 0x22

 

(same address in both 607 & 608)

TLDR: if you have trouble engaging logging before engine start every now and again patch as per above and should fix it 👍

Edited by jenksta
  • Like 1
  • Upvote 1
Link to comment
Share on other sites

  • 3 weeks later...

I am having difficulty trying to build a basemap for my 1998 V70 AWD automatic transmission running an RN 2002 2.4L LPT B5244T3, 18T turbo, white injectors, stock afm, r Mani, 3" exhaust, NA intake, 960TB.

I was using the 607rev5 basemap which work fine for starting and cruising the car but the CEL comes lit in the mid range with the tune, the car also "feels" less peppy in the bottom end. I have not datalogged with that ECU yet so I'm not sure how bad it is other than my preliminary testing.

I started to think I would be better off using base maps for an LPT motor, so I found the 609 bin and xdf from turboforslund to poke around. I can see the difference between the main ignition timing, Fueling VE, TCV pilot and ldr, ..so I copied over those values from the 609 to the 607rev5 bin. Flashed fine, car starts and cruises maybe better but the CEL blinks at various times in the low mid and mid range, before with T5 basemap I only had midrange CEL.

I know I need to wire in my Spartan WB02 and connect boost source to my other ECU and begin logging to see what's actually happening but I just wanted to check theory that I should be using LPT maps to start vs altering the T5 maps, in the end it doesn't matter if done correctly but for me it's best to start with closest, safest match.

My goal is to be able to run stock boost levels without knock and good feel, then up the boost and investigate timing and fueling changes. Eventually, I will flash another bin for green injectors and 3.25" MAF to support a K24 swap coming up.

So, continue to LPT swap maps or tube the existing 607 maps? I know the differences in the ECU are greater than a few tables for LPT vs HPT but I need to learn where to start.

I am currently running ARD Blue Tune which has been fantastic and that's what I'm aiming for. I wish I could see what the maps inside the ARD file look like but I understand no way to read the flash other than eprom which I don't do.

 

Edited by NJGreenBudd
Forgot 18T
Link to comment
Share on other sites

1 hour ago, NJGreenBudd said:

I am having difficulty trying to build a basemap for my 1998 V70 AWD automatic transmission running an RN 2002 2.4L LPT B5244T3, white injectors, stock afm, r Mani, 3" exhaust, NA intake, 960TB.

I was using the 607rev5 basemap which work fine for starting and cruising the car but the CEL comes lit in the mid range with the tune, the car also "feels" less peppy in the bottom end. I have not datalogged with that ECU yet so I'm not sure how bad it is other than my preliminary testing.

I started to think I would be better off using base maps for an LPT motor, so I found the 609 bin and xdf from turboforslund to poke around. I can see the difference between the main ignition timing, Fueling VE, TCV pilot and ldr, ..so I copied over those values from the 609 to the 607rev5 bin. Flashed fine, car starts and cruises maybe better but the CEL blinks at various times in the low mid and mid range, before with T5 basemap I only had midrange CEL.

I know I need to wire in my Spartan WB02 and connect boost source to my other ECU and begin logging to see what's actually happening but I just wanted to check theory that I should be using LPT maps to start vs altering the T5 maps, in the end it doesn't matter if done correctly but for me it's best to start with closest, safest match.

My goal is to be able to run stock boost levels without knock and good feel, then up the boost and investigate timing and fueling changes. Eventually, I will flash another bin for green injectors and 3.25" MAF to support a K24 swap coming up.

So, continue to LPT swap maps or tube the existing 607 maps? I know the differences in the ECU are greater than a few tables for LPT vs HPT but I need to learn where to start.

 

We're running the same engine in my wife's '97 GLT, but with greens and a 16T. The stock ECU for the car was a -936 and when I originally set it up, I copied the maps etc from the -936 to the -607 to get things going. With the bins from Motronic Suite, the -459 bin is another '98 LPT bin, and I've used parts of that and might be a good starting point for you.


The car is running COP and the ex VVT and runs pretty well right now. I've raised boost thresholds slightly, but haven't gotten too aggressive yet. I have a Spartan 2 and a modded ECU ready to drop in when the weather is a little nicer, so we can do some more tuning on it and dial things in. I'm also wanting to fiddle with the cam timing, but am waiting until we're in "tuning" mode.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share