[ninja_zx11]

Hi folks, Would like to log actual boost vs requested boost readings(just for the curiosity sake) on my X535D M57.I searched and found that can be done via testo.I used to check on my VW TDI using vagcom and it was a straight forward and easy process.I haven't checked ISTA-D yet.

Could anybody please suggest me the easiest and simplest way to see live graph of requested and actual boost while driving.In that way i can have better picture of my boost control system which includes all the turbo related valves and charge pressure sensor.Thanks.

[Yozh]

I found the demanded vs actual torque in Torque is somewhat useful. What mileage is your E70 and are you having any issued?

[Thecastle]

Originally Posted by Yozh

I found the demanded vs actual torque in Torque is somewhat useful. What mileage is your E70 and are you having any issued?

Yes, but the problem with torque is its very low resolution. The sample rate is something like 1-.1.5 seconds which will miss a lot of transient behavior. But I'd be interested in a good answer for high speed logging.

[ninja_zx11]

Originally Posted by Yozh

I found the demanded vs actual torque in Torque is somewhat useful. What mileage is your E70 and are you having any issued?

Hi Yozh, I don't have any error codes on my E70 but sometimes i feel that it lags power at low rpms.But if i push the skinny pedal all the way then it moves like it should and feels quite torquey and powerful.It has 110k Kms(68k miles).

That's why i just want to make sure that my actual boost values are in line with the requested values.Will try to dig more on ISTA-D.It may have something.

[ninja_zx11]

One more thing i would like to mention that last year when i removed intake manifold to do the glow plug controller, I cleaned my intake manifold thoroughly as there was lots of carbon inside and i also cleaned both ports(went as deep into the ports as i could with wooden scrapers) of all cylinders by first plugging the ports by rag and then scrubbing, vacuuming out all the gunk.

Then i found that my charge air pressure sensor was quite plugged with the carbon but i had no codes.I cleaned the hole of the sensor but after doing everything,i didn't notice any change in the engine behavior or drive.I am just suspecting that i could be running lean(too much actual boost) because of the charge air pressure sensor slow or not able to give proper response due to carbon.But its just a guess without taking a look at the proper boost numbers.

[TDIwyse]

Originally Posted by Thecastle

Yes, but the problem with torque is its very low resolution. The sample rate is something like 1-.1.5 seconds which will miss a lot of transient behavior. But I'd be interested in a good answer for high speed logging.

That's really slow. I've found it can log up to 5 things and get 3 to 4 samples per second reliably. At 3 "things" I get ~5 samples per second. But you must make sure that the display page only has the parameters you're logging, otherwise the additional displays will slow down the sample rate... For a 4th gear pull, that sampling rate is pretty good at capturing the engine behavior.

TestO has a much better sampling rate vs items sampled tradeoff. But it's not as convenient ...

[DWR]

Originally Posted by TDIwyse

That's really slow. I've found it can log up to 5 things and get 3 to 4 samples per second reliably. At 3 "things" I get ~5 samples per second. But you must make sure that the display page only has the parameters you're logging, otherwise the additional displays will slow down the sample rate... For a 4th gear pull, that sampling rate is pretty good at capturing the engine behavior.

TestO has a much better sampling rate vs items sampled tradeoff. But it's not as convenient ...

At some point we reach the limit of response time of the DDE. Also, some parameters have inherently higher priority. For example, rpm logs quite quickly. Pheno and I are discussing an idea that could speed up Testo. I'll just say for now it involves syncing and combining data streams.

[TDIwyse]

Originally Posted by DWR

At some point we reach the limit of response time of the DDE. Also, some parameters have inherently higher priority. For example, rpm logs quite quickly. Pheno and I are discussing an idea that could speed up Testo. I'll just say for now it involves syncing and combining data streams.

Nice.

How many versions of TestO is Pheno up to now? I'm probably 20 or 30 versions behind :-)

[ninja_zx11]

Originally Posted by DWR

At some point we reach the limit of response time of the DDE. Also, some parameters have inherently higher priority. For example, rpm logs quite quickly. Pheno and I are discussing an idea that could speed up Testo. I'll just say for now it involves syncing and combining data streams.

Hi DWR, Could you please guide me how can i see a live graph of requested boost vs actual on Testo?Thanks

[ninja_zx11]

Fired up Testo and was able to generate the graph but i haven't driven with testo connected as weather is really bad.The graphs below are with engine off.

Response time doesn't look bad as in the bottom it says 11.6 msg/sec(i asume msg as messages).But i used ICOM.

Could anybody please have a look at the pics if i am looking at the right values?I need just actual vs requested boost graph.Thanks

[TDIwyse]

Originally Posted by ninja_zx11

...
Could anybody please have a look at the pics if i am looking at the right values?I need just actual vs requested boost graph.Thanks

It's been awhile since I've used TestO, but I think that looks right. 1000 hPa = 14.5 psi. Those values are in "absolute pressure", so it's measuring atmospheric pressure plus whatever boost the turbo is adding.

[ninja_zx11]

Originally Posted by TDIwyse

It's been awhile since I've used TestO, but I think that looks right. 1000 hPa = 14.5 psi. Those values are in "absolute pressure", so it's measuring atmospheric pressure plus whatever boost the turbo is adding.

Thanks TDIwyse! will try to log it while driving.

[Yozh]

There is a good amount of info on TestO in a thread called "INPA Logging" started by iaknown. 16 pages, but once you get through it, it is fairly easy to figure out TestO. Probably a good time to send appreciations to Pjeno

[ninja_zx11]

Yes Yozh lots of info in that thread.Testo is a nice piece of software and Pheno definitely deserves appreciation from us.

I am gonna log with ICOM as soon as weather gets better and will post results here.

[pheno]

@TDIwyse: yep, TestO for Android would be nice :-) Looks like I'm getting absorbed in electronics so that'll have to wait.

@ninja_zx11: Seems the msg/sec (messages per second) is not giving right numbers I'll have to fix that.

The 'job: 54ms' on bottom right show time to send a request and read a reply from DDE. 54ms is a very good number ! you're looking at ~20 FPS data refresh rate. The logfile has timestamps and you can verify the speed from there. I have a speed of something around 100ms with 12 data points.

[ninja_zx11]

Thanks Pheno for chiming in!!

So i tried to log it and i found that log values are little shifted from each other.I mean if you look at the end of log in a csv file,one column goes further down and it also reflects while generating a trace because desired boost trace should be little ahead of actual boost trace.Am i doing something wrong?Please suggest.Thanks
This time i Used k+DCAN cable just because of ease of use.

Please remove .txt from the name of csv file.

[pheno]

Thanks ninja_zx11 it's great to be on this forum and to give some help. So if you want params to be in sync please use 'File Logger' from Tools->Data Logger. I know there's that 'Save all graphs' but that saves only individual graphs in separate files. I guess I should make it more clear..

So the procedure goes like this (this is what I usually do):

1. create custom job and start it
2. press 'mark all' to get graphs
3. press F2 or Tools -> Data Logger. On the right side you can see what params will be logged
4. press 'Start' .. and 'Stop' when done

If you want to use nice visualization program I can suggest Megalogviewer. Free version has some limitation on amount of rows but other than that works okay.

[ninja_zx11]

Originally Posted by pheno

Thanks ninja_zx11 it's great to be on this forum and to give some help. So if you want params to be in sync please use 'File Logger' from Tools->Data Logger. I know there's that 'Save all graphs' but that saves only individual graphs in separate files. I guess I should make it more clear..

So the procedure goes like this (this is what I usually do):

1. create custom job and start it
2. press 'mark all' to get graphs
3. press F2 or Tools -> Data Logger. On the right side you can see what params will be logged
4. press 'Start' .. and 'Stop' when done

If you want to use nice visualization program I can suggest Megalogviewer. Free version has some limitation on amount of rows but other than that works okay.

Thanks a lot for the explanation!! Will report back again..

[Yozh]

Any progress. I've been logging here and there. Curious as to your findings. I think with TestO we need a list of all useful parameter names that we can use.

[TDIwyse]

Originally Posted by Yozh

Any progress. I've been logging here and there. Curious as to your findings. I think with TestO we need a list of all useful parameter names that we can use.

Here are some that I found useful (when creating the custom job, typing in the short name/abbreviation, like INMOT, is faster, but not all parameters seem to have an abbreviation):

INMOT - STAT_MOTORDREHZAHL_WERT - Engine RPM
ITLAL - STAT_LADELUFTTEMPERATUR_WERT - Charge Pipe Air Temp, C
IPLAD - STAT_LADEDRUCK_IST_WERT - Actual Absolute Boost Pressure at MAP, mBar
SPLAD - STAT_LADEDRUCK_SOLL_WERT - Boost Pressure Set Point, mBar
IPRDR - STAT_RAILDRUCK_WERT - Actual Rail Press, bar
SPRDR - STAT_RAILDRUCK_SOLL_WERT - Rail Press Setpoint, bar
STAT_LUFTMASSE_WERT - MAF reading
ILMMG - STAT_AFS_mAirPerCyl_IST_WERT - ILMMG - Air mas per cylider
SLMMG - STAT_AirCtl_mDesVal_SOLL_WERT - SLMMG - Air mass expected
STAT_Exh_pTrbnUs_FULL_WERT - Exhaust manifold drive pressure sensor
STAT_LSU_rLam_WERT - Lambda sensor
ITAVO - Oxidative Catalyst EGT sensor

[DWR]

Finding things in this forum can be very frustrating. A while ago I published translations for hundreds of parameters, but you would be hard pressed to find it ... in fact, I can't find it.

See Attached. Remove "txt" file extension and open as a spreadsheet.

[pheno]

A few months ago I incorporated a translation system in the program. Translated text can be seen in the parameter table at column INFO.

Translation texts are defined in testo/translations/jobs_all_en_EN.txt and format of that file is CSV. You can freely edit and add your own texts. Be sure to maintain encoding as UTF-8. Editors usually don't change it without user knowing it. When done execute 'create_translations.bat' and new translation file is compiled.

I've added some most common translations according my best knowledge. Please report any odd sounding translation text :-)