M4.4 data logging

[jamesy12345]

Started a new thread on this to avoid it being discussed across a project thread...

I found some information on the M4.4 wiki page:

http://m44.wikia.com/wiki/Data_logging

It looks like you can log quite a few parameters...

0 NMOT - Current Engine Speed in RPM (factor X*30)
1 TL - Load in MS (factor X*.048)
2 Z_ZYL - Current Firing Logical Cylinder
3 ZWOUT - Actual Ignition Angle
4 ZWBEG - Ignition angle after change limitation
5 ZWNEU - Ignition angle before change limitation
6 DZW_KR - Current recorded depth of knock retard
7 FALLT - Memory of last knock retard depth
8 XFALMIT - Sum of cylinder retard values
9 XFALARO - Address in KR case depth map
10 XFALT5 - Retard value cylinder 5 (maybe)
11 XFALT3 - Retard value cylinder 3 (maybe)
12 XFALT1 - Retard value cylinder 1 (maybe)
13 XFALT2 - Retard value cylinder 2 (maybe)
14 XFALT4 - Retard value cylinder 4 (maybe)
15 Z_ZYL - Current Firing Logical Cylinder
16 ZWGETR - Ignition angle retard for A/T gearbox shift
17 XFK_ANR - Factor of enrichment due to knocking
18 BITS - Assorted flagbits
19 MLH - Air mass, high byte
20 MLL - Air mass, low byte
21 TIH - Injection time, high byte
22 TIL - Injection time, low byte
23 UHLM - MAF VOLTAGE
24 XTRA - LTFT Idle
25 XFRA - LTFT part load
26 XFR - STFT
27 XUSVK - Front O2 sensor voltage
28 XWDKBL - Throttle angle in degrees
29 HFKORR - Overall fuel correction, high byte
30 LFKORR - Overall fuel correction, low byte
31 VMESS - Vehicle speed in KM/H
32 TMOT - Coolant temperature, degrees C (factor X-80)
33 XERG_PS - Boost control setpoint after 1st set of corrections (factor X*.048)
34 XP_SOLL - Boost control setpoint after all corrections (factor X*.048)
35 XP_IST - Current load value as sampled by boost control logic (factor X*.048)
36 XPCP - Current deviation between XP_SOLL and XP_IST (factor X*.048)
37 XTV_VS - Current value from KFTVVSLDR map
38 TVMBEG - Actual output duty cycle to turbo control valve
39 XPCP_TV - Current proportional correction to KFTVVSLDR value to meet target load
40 XPCIHI - Boost control integrator, high byte
41 XPCILO - Boost control integrator, low byte

If you follow these instructions...Tunerpro linky...

The .adx file is the datalogging file that must be setup in TunerPro RT. For bench testing the rev5_test.adx is needed, and for logging in the car you need to use the rev5.adx file. You can find the rev5.adx file here http://droid.arm.ee/volvo/rev5/. To set it up go to Tools -> Preferences -> Data Acq./Emulation and select interface type "use plugin", select the "TunerPro Data Acquision IO interface" plugin (the only one, by default), then select "Configure Plug-in Component" and select "Standard Serial" and specify the COM port number of your serial interface. Then, from the Acquision menu, select Load Definition and feed it the ADX you want to use. Then, from the Acquision Menu, select "Show Dash". You may need to expand the window to see all of the 15 gauges present, I seem to remember it starts out all small on a fresh install.

...you should see this:

[MoleT-5R]

Thanks Jamesey, watching with interest as I'm sure this thread is going to be most useful for all us self-tuners

[Ettienne]

It's basically how rob started, just reading and trying

[Ettienne]

Started a new thread on this to avoid it being discussed across a project thread...

I found some information on the M4.4 wiki page:

http://m44.wikia.com/wiki/Data_logging

It looks like you can log quite a few parameters...

0 NMOT - Current Engine Speed in RPM (factor X*30)
1 TL - Load in MS (factor X*.048)
2 Z_ZYL - Current Firing Logical Cylinder
3 ZWOUT - Actual Ignition Angle
4 ZWBEG - Ignition angle after change limitation
5 ZWNEU - Ignition angle before change limitation
6 DZW_KR - Current recorded depth of knock retard
7 FALLT - Memory of last knock retard depth
8 XFALMIT - Sum of cylinder retard values
9 XFALARO - Address in KR case depth map
10 XFALT5
11 XFALT3
12 XFALT1
13 XFALT2
14 XFALT4
15 Z_ZYL - Current Firing Logical Cylinder
16 ZWGETR - Ignition angle retard for A/T gearbox shift
17 XFK_ANR - Factor of enrichment due to knocking
18 BITS - Assorted flagbits
19 MLH - Air mass, high byte
20 MLL - Air mass, low byte
21 TIH - Injection time, high byte
22 TIL - Injection time, low byte
23 UHLM - MAF VOLTAGE
24 XTRA - LTFT Idle
25 XFRA - LTFT part load
26 XFR - STFT
27 XUSVK - Front O2 sensor voltage
28 XWDKBL - Throttle angle in degrees
29 HFKORR - Overall fuel correction, high byte
30 LFKORR - Overall fuel correction, low byte
31 VMESS - Vehicle speed in KM/H
32 TMOT - Coolant temperature, degrees C (factor X-80)
33 XERG_PS - Boost control setpoint after 1st set of corrections (factor X*.048)
34 XP_SOLL - Boost control setpoint after all corrections (factor X*.048)
35 XP_IST - Current load value as sampled by boost control logic (factor X*.048)
36 XPCP - Current deviation between XP_SOLL and XP_IST (factor X*.048)
37 XTV_VS - Current value from KFTVVSLDR map
38 TVMBEG - Actual output duty cycle to turbo control valve
39 XPCP_TV - Current proportional correction to KFTVVSLDR value to meet target load
40 XPCIHI - Boost control integrator, high byte
41 XPCILO - Boost control integrator, low byte

If you follow these instructions...Tunerpro linky...

The .adx file is the datalogging file that must be setup in TunerPro RT. For bench testing the rev5_test.adx is needed, and for logging in the car you need to use the rev5.adx file. You can find the rev5.adx file here http://droid.arm.ee/volvo/rev5/. To set it up go to Tools -> Preferences -> Data Acq./Emulation and select interface type "use plugin", select the "TunerPro Data Acquision IO interface" plugin (the only one, by default), then select "Configure Plug-in Component" and select "Standard Serial" and specify the COM port number of your serial interface. Then, from the Acquision menu, select Load Definition and feed it the ADX you want to use. Then, from the Acquision Menu, select "Show Dash". You may need to expand the window to see all of the 15 gauges present, I seem to remember it starts out all small on a fresh install.

...you should see this:

There are several bits in that thread that need removing or placing here, as play no part in the threads continuity

[dant5r]

I thought they was a old thread about 4.4 tuning ?

[claymore]

Looks like us with the lowly 4.3's can have a play as well

http://volvospeed.com/vs_forum/topic...-personal-use/

[Ettienne]

I thought they was a old thread about 4.4 tuning ?

There is somewhere I think rob put some stuff up.

[Ettienne]

Looks like us with the lowly 4.3's can have a play as well

http://volvospeed.com/vs_forum/topic...-personal-use/

I guess you can always just replace the ECU for 4.4 if needed.

What's the difference with 4.3 tuning?

[jamesy12345]

I thought they was a old thread about 4.4 tuning ?

Yes but data logging can be used for fault finding also & prior to tuning:

For example I'm getting hold of an S70R shortly that has been mapped.....ignition timing has been advanced but I'd like to install the nitrous kit I had on the T5R. I'd like to know when I'm using the nitrous if it is detonating - no point wasting a bottle of nitrous trying to make power while the ECU is backing it off

Hopefully I can log some information before and after the nitrous to see if the knock sensors are being activated at any time

or I could just make one of these

https://uprev.com/documentation/Knoc...n%20Device.pdf

[MoleT-5R]

There is somewhere I think rob put some stuff up.

There is and great thread it is, I have been following Rob's thread from the outset

http://www.vpcuk.org/forums/showthre...M4-4-Remapping

[jamesy12345]

Looks like us with the lowly 4.3's can have a play as well

http://volvospeed.com/vs_forum/topic...-personal-use/

you lads already have Turbo Tuner!!)

There is and great thread it is, I have been following Rob's thread from the outset

http://www.vpcuk.org/forums/showthre...M4-4-Remapping

lost me on the first post...what software, what cable, how did you get a USB to read COM1 etc. Great that someone is having a go but the text needs to consider the experience level of the reader - I must be more stupid than Rob expects))

As above this thread is more about collecting the information rather than changing it

[Ettienne]

There is and great thread it is, I have been following Rob's thread from the outset

http://www.vpcuk.org/forums/showthre...M4-4-Remapping

Rob got the free software from swede sp and made himself leads and stuff, tbh it's not my thing but he's pretty up on it now. He's mapped at least 4 cars now for others that have been dynod and can write maps taking into account mods already there but there are limits for him as he builds his own database.

However I don't think he's mapping anything at the moment as he is just working on his 244.

[Dream3r]

Wow 8 bit ecu lol. I recognise a few variables that bosch brought forward to me7.

[dant5r]

Yes but data logging can be used for fault finding also & prior to tuning:

For example I'm getting hold of an S70R shortly that has been mapped.....ignition timing has been advanced but I'd like to install the nitrous kit I had on the T5R. I'd like to know when I'm using the nitrous if it is detonating - no point wasting a bottle of nitrous trying to make power while the ECU is backing it off

Hopefully I can log some information before and after the nitrous to see if the knock sensors are being activated at any time

or I could just make one of these

https://uprev.com/documentation/Knoc...n%20Device.pdf

Are you planning to connect your standard s70r ecu to your laptop and data log with tunerpro ?

[jamesy12345]

I guess you can always just replace the ECU for 4.4 if needed.

What's the difference with 4.3 tuning?

some differences between 4.3 & 4.4

http://www.wothrline.com/editerbara_...ch_m43_m44.htm

...M4.4 is very similar to the M4.3 system, but it’s twice as big with its 309kB data size....

Are you planning to connect your standard s70r ecu to your laptop and data log with tunerpro ?

The ecu has been remapped already, but yes I'll be logging via OBD socket before I do any further mods to it

[Dream3r]

Yes but data logging can be used for fault finding also & prior to tuning:

For example I'm getting hold of an S70R shortly that has been mapped.....ignition timing has been advanced but I'd like to install the nitrous kit I had on the T5R. I'd like to know when I'm using the nitrous if it is detonating - no point wasting a bottle of nitrous trying to make power while the ECU is backing it off

Hopefully I can log some information before and after the nitrous to see if the knock sensors are being activated at any time

or I could just make one of these

https://uprev.com/documentation/Knoc...n%20Device.pdf

If I remember right the bin file on Volvospeed has been modified for logging. That means your mapped ecu will need to be running that file as a base.

[jamesy12345]

If I remember right the bin file on Volvospeed has been modified for logging. That means your mapped ecu will need to be running that file as a base.

I'll have a read, thanks for input

http://volvospeed.com/vs_forum/topic...uning-for-m44/

[jamesy12345]

...
10 XFALT5
11 XFALT3
12 XFALT1
13 XFALT2
14 XFALT4
...

These parameters are not explained in the M4.4 Wiki page

If you open the 'rev5.adx' file in text-editor like Notepad, you can see the following description in the code:

XFALT5
Per cylinder retard value 0xFA30, or 0xFA35 + XFALARO if adaptive knock control is enabled. Cylinder order is claimed to be 5,3,1,2,4 in the DAMOS, so this *should* be physical cylinder 5. That may be incorrect, however.

& a similar description for the other 4 cylinders.

On opening the ADX file I noticed that you could make changes to the code, for example delete gauges you don't need, re-size/re-position gauges, change their range & adjust the alarm set points - you can configure limits for the logging. If the parameter goes outside of set limits the gauge will change colour.



Above I made the RPM gauge larger and increased the range of the gauge to from 6500 to 7600 rpm....not expecting to reach this value just experimenting. Shortly after this I realised Tuner Pro has a built in ADX editor....more user friendly

The lines of code for this gauge are below:

<ADXVALUE id="NMOT" idhash="0xA4912B39" title="RPM">
<desc>Engine RPM</desc>
<parentcmdidhash>0xCD50945B</parentcmdidhash>
<units>RPM</units>
<packetoffset>0x00</packetoffset>
<range low="0.000000" high="7600.000000" />
<alarms low="0.000000" high="7600.000000" />
<digcount>4</digcount>
<outputtype>1</outputtype>
<datatype>6</datatype>
<unittype>4</unittype>
<MATH equation="X*30">
<VAR varID="X" type="native" />
</MATH>
</ADXVALUE>

and...

<ADXDGENTRY gaugetype="0" itemidhash="0xA4912B39" left="0" top="0" right="50" bottom="94" arcmin="45" arcmax="315" />
</ADXDASHBOARD>

I think of the ADX file as a list of instructions used by Tuner Pro software to send information to the ECU & display the responses received back in a meaningful way to us.

[jamesy12345]

As pointed out by Dream3r....the XDF and ADF files available on the M4.4 Wiki may not work with all other M4.4 BIN files

At the moment I don't know what BIN file is in the future test mule - Yosser's S70R - it could be the stock BIN '0261204611' or it could be the one from the Volvospeed thread/M4.4 Wiki site - '0261204608'. AFAIK either file could have been used by the guys who did the mapping from T5D5 forum.

Anyway, I'll find out as and when but the above isn't a show stopper as far as logging is concerned - two ways to go with TunerPro anyway...

*Flash the car with the 608 BIN file then modify the tune back to where I want it....then log it...! Sounds a bit extreme for some logging.
*Develop XDF and ADF files to suit the 611 BIN. Easy to say...!

(plus there is also another way to go...bog standard ELM327 stuff but I'll come back to that when I get my head around it)

Some terminology:

BIN - binary file
XDF - bin definition...reads the BIN
ADX - data stream definition....converts info from XDF to graphic form

How to create an XDF:

So, something simple first...idle based on coolant temperature just to demonstrate what can be done. Plus we all have gauges on our real dashboards to confirm the logging.

First off, open your BIN file in TunerPro....go to File menu - Open BIN.

At the top of the TunerPro window it will show your BIN file and if any XDF is selected. I'm using the stock S70R BIN.



To start creating an XDF....go to XDF menu and Create New XDF parameter.

Choose 'Table' for this parameter, then OK, then input the information as below.....



Save your XDF when finished with a name you can link to the relevant BIN. Don't forget to use the conversion factor for the units as per the Wiki page...X-80 for the temperature (click the 'Edit' button on the 'Rows' tab).

The hex addresses for the RPM target values (0xD544) and coolant temperature axis (0xCCB9) I took from the XDF created for the 608 BIN file. Since a nice table & graph can now be displayed in TunerPro, using the same addresses within the 611 file, it means that this info is stored in the same place for the 608 and 611 BIN files....which is good!

[Dream3r]

If the freeware suite and file has been used to map the car then the logging will work, if not it won't.

Just because the axis is in the same place it doesn't mean it's the right axis either. It probably is, but he only way to really know for sure is to have the Volvo damos or dissemble the file.