Dangerous Dave

Welcome back! You've got a lot of catching up to do 😁

Awesome, that's what the forums are for Good luck!!

I have them both in my Tunerpro directory. Here are all 4 files: https://www.dropbox.com/s/f1f6gz8uf6rijf8/msvcp100.zip?dl=0 Otherwise install the Microsoft Visual C++ 2010 package. Though there may be an issue with the msvcp100.dll in win 10 http://forum.tunerpro.net/viewtopic.php?t=4439

Ok, looks like we're getting somewhere, maybe a Windows 10 issue. Have you tried changing the permissions for the dll? Or running tunerpro as administrator? Also see this thread

Ok, on the Menu bar goto 'XDF>View/Edit XDF Header Info' then click the 'Checksums' tab. There should be a checksum listed called 'Checksum plugin by Simply Volvo' Click 'Edit Selected' and see if it looks like this:

Have you put the motronic 4.4 checksum plugin into the tunerpro plugin folder?

The processor sends a command which enables pin A16 on the eeprom (see 28f010 eeprom datasheet). This enables the upper 4 sectors (0x10000 to 0x1FFFF) of the eeprom to be read by the processor. It constantly switches between the two blocks, some of the code is duplicated. Please read the six text files here: https://www.piese-volvo.ro/droid/volvo/rev5/ They contain all the info on how the map switching and logging works

The are extra maps added to the 608 binary which can be selected before the engine is started. This is why you have found the extra map at 0x8088. The ecu only uses one map at a time. You can select each map by fully depressing the throttle pedal, then the MIL will flash multiple times depending on which map is selected. The checksums are different because the data in Block 0 is different to Block 1. You really don't need to worry about the checksums though as the tunerpro plugin calculates it for you.

There is no info how to disable the immobiliser on any m4.4 binaries (none that anyone has shared anyway). The 608 binary does not have the immobiliser enabled which is why it is used for the modifications. It could be as simple as disabling the setting of the immobiliser bit, all the info is already posted, you just need to research a little.

It will probably be the 0261204305 binary like my 850AWD is.

First thing, if you can, connect to the ecu using realterm then send an 'L' to enable permanent logging (until battery or ecu is pulled). Your should get a response from the ecu with a 'L' in it. If you get that response then you can try the logging again. Let us know how it goes.

In the 608 binary there is a gear dependant boost control option at C9A3 (configbyte for gear dependant boost control in the XDF) though I don't know how effective it is as I've not fully tested it before. FYI this option is not in the 305 binary.

My apologies, I got the units wrong. The injector voltage correction is in milliseconds. So the max correction is 4.9725ms. At 5V and 5.99V it shouldn't matter too much as most of the time the battery voltage is at 12 to 14V whilst the engine is running. I'm not sure in what situation a battery voltage as low as 5V would arise let alone the engine being able to run at that voltage. So just run it at the maximum correction value for those low voltages.

I've been having issues with the fuel mileage. It was terrible before I started my mods but now it's even worse. I want half with running the 608 binary, little glitches were happening and it's meant for the 2.3 engine. Plus there are many differences in the maps between the two. So I've gone back to running the 305 binary which is the original for my 2.5 lpt engine. I've transferred over the logging code as well as COP and wideband control. Using exactly the same fueling and ignition maps I had in the 608 binary on a cruise it's gone from 26mpg to 38mpg. On a 70 mile run the other

Here is a complete list of the steps for the injector constant, injector voltage correction and minimum injector time. The maximum voltage correction allowed for injector opening is 4.9725ms https://www.dropbox.com/s/88cuzfqplrg5o67/Injector Calculations.ods?dl=0