Dangerous Dave

It could be something got corrupted or you inadvertently change a setting somewhere, it can happen (I once managed to change my fuel cut speed to 0 mph so as soon as I moved the engine died )

I ran my modified 609 binary (logging, also with COP and WB control) on my 850 and it worked ok, so either there is no immo enabled on the 609 or it worked due to my ecu being originally a 609 (just I have fitted an ostrich to it). The logging is added to the binary and doesn't remove the evap diagnosis like in the 608rev5b. This means that not all the parameters can be logged due to the 608rev5b version re-purposing some addresses from the evap routine. And also doesn't include map switching. Theoretically (not been tested, though should work) I have added logging to other binaries: 448/449/611/612. A flag/switch sets the byte to 0 or 1, a scalar will allow you to set it to any value (up to 255). As it needs to be 1 or 0 I just used a flag/switch. Have you restored the original value at 0xC8ED in your 609 binary? It should be 0x79 (118 decimal). Good news on the logging rate! Did changing the 't' to an 'l' work?

There is a logging version of the 609 that I've created (I don't know if anyone else has done any). I'll have to dig it out and check it before posting it.

Let us know if it works any better Thanks bud, it's a long work in progress lol. Ok, from the images you posted it is sending the wrong letter to engage logging. If you see it says 0x74 and below it says 't'. It needs to send an 'l' so if you just change that 't' to an 'l' it should change the 0x74 to 0x6C and should work. Then in the ADX Header Data tab change the Connection command to 'Engage logging' and change the Monitor command to 'Listen for data frame'. That should remove the listen silence and give you a faster data stream. Hope this helps

That's because the auto/manual location in the 609 binary is different to the 608. For the 609 binary add the flag parameter and point to 0xC8FC Can you post a screenshot of your Definition setup in tunerpro? Post the ADX Header Data and the engage logging

Send What pin/input is your wideband connected to?

Excellent info there buddy! Only thing is the 0.34 is used for the 350cc 608 binary and in the 315cc 305 binary for my LPT 850 AWD which makes things even more confusing. But like you say, 315cc in the formula seems to work for other people. I'm using 0.29 at the moment (which is the 350cc/440cc) but will lower it to 0.24 I worked out my mpg from fuel used on a journey (filled to the brim then drove 30 miles to my workplace then filled up again). Worked out to approx. 21MPG and that was highway cruising 50-70mph. I just wanted to get my injector settings spot on to rule out any issues in that area.

Yes it is rather confusing as there is very little information about minimum injection times anyway. I've seen lots of figures for the greens (some saying 1.10ms, some 0.5ms). Also I thought the stock value was 315cc (as the first injectors on M4.4 were that size) but as you say the XDF states 350cc. I'm trying to figure out why I cannot get more than 22mpg at cruise.

What TEMIN is everyone using for Greens?

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?