[ingenieur]

The TD-530 trace.tst does log as well, but TestO is preferable IMO for a number of reasons.

[ninja_zx11]

You were right on pheno!! Finally it worked.Thanks for the idea!!
got job name and other stat name by opening ecu file in tools32 like you suggested and entered like this:

PHP Code:

1|d73n57c0|status_ladedruck_ist|||stat_ladedruck_ist_wert
1|d73n57c0|status_ladedruck_soll|||stat_ladedruck_soll_wert 


But only problem is digit output is in scientific notation

PHP Code:

Ergebnis: Trace Aufzeichnung
----------------------------

Datum     : 04.01.2017 19:14:32 
Baureihe  : E70
Umfang    : Alle Steuergeräte    
JobStatus : OKAY
----------------------------------------------------------------------------------------------
Datum      Zeit       stat_ladedruck_ist_wert   stat_ladedruck_soll_wert   
04.01.2017 19:14:32   1.020919E+003             9.999528E+002              
04.01.2017 19:14:33   1.020919E+003             9.999528E+002              
04.01.2017 19:14:33   1.020919E+003             9.999528E+002              
04.01.2017 19:14:33   1.020919E+003             9.999528E+002              
04.01.2017 19:14:34   1.020919E+003             9.999528E+002              
04.01.2017 19:14:34   1.020919E+003             9.999528E+002              
04.01.2017 19:14:34   1.020919E+003             9.999528E+002              
04.01.2017 19:14:34   1.020919E+003             9.999528E+002              
04.01.2017 19:14:34   1.020919E+003             9.999528E+002              
04.01.2017 19:14:34   1.020919E+003             9.999528E+002              
04.01.2017 19:14:35   1.020919E+003             9.999528E+002              
04.01.2017 19:14:35   1.020919E+003             9.999528E+002 


[pheno]

Originally Posted by ninja_zx11

You were right on pheno!! Finally it worked.Thanks for the idea!!
got job name and other stat name by opening ecu file in tools32 like you suggested and entered like this:

PHP Code:

1|d73n57c0|status_ladedruck_ist|||stat_ladedruck_ist_wert
1|d73n57c0|status_ladedruck_soll|||stat_ladedruck_soll_wert 


But only problem is digit output is in scientific notation

PHP Code:

Ergebnis: Trace Aufzeichnung
----------------------------

Datum     : 04.01.2017 19:14:32 
Baureihe  : E70
Umfang    : Alle Steuergeräte    
JobStatus : OKAY
----------------------------------------------------------------------------------------------
Datum      Zeit       stat_ladedruck_ist_wert   stat_ladedruck_soll_wert   
04.01.2017 19:14:32   1.020919E+003             9.999528E+002              
04.01.2017 19:14:33   1.020919E+003             9.999528E+002              
04.01.2017 19:14:33   1.020919E+003             9.999528E+002              
04.01.2017 19:14:33   1.020919E+003             9.999528E+002              
04.01.2017 19:14:34   1.020919E+003             9.999528E+002              
04.01.2017 19:14:34   1.020919E+003             9.999528E+002              
04.01.2017 19:14:34   1.020919E+003             9.999528E+002              
04.01.2017 19:14:34   1.020919E+003             9.999528E+002              
04.01.2017 19:14:34   1.020919E+003             9.999528E+002              
04.01.2017 19:14:34   1.020919E+003             9.999528E+002              
04.01.2017 19:14:35   1.020919E+003             9.999528E+002              
04.01.2017 19:14:35   1.020919E+003             9.999528E+002 


That's good! However the resolution, data samples per second won't be as good as with TestO.

Hey, you're gonna need to write a perl one-liner to convert those values into decimal notation

[ninja_zx11]

Originally Posted by pheno

That's good! However the resolution, data samples per second won't be as good as with TestO.

Hey, you're gonna need to write a perl one-liner to convert those values into decimal notation

Thanks Pheno for giving me that idea which helped me to make it run!! I just wanted to make it run.I know its not user friendly and not much useful.I can tell you that your TestO rocks!!

Regarding perl programming, I think its gonna be over my head
I can program CNC machines but not Perl programming. Also i don't need inpa to log that stuff.Testo is good!!

[pheno]

Thanks and You're welcome!

I'm happy to hear you've found TestO as a useful tool. Feel free to suggest new features. And report bugs if you find any. :-)

[DWR]

I'll share my suggestion in public. Some parameters are already flying around the CAN Bus. No need to make requests if things like rpm are already updated and transmitted at a good rate. If CAN sniffing and UDS requests could be integrated, logging could speed up.

[pheno]

Originally Posted by DWR

I'll share my suggestion in public. Some parameters are already flying around the CAN Bus. No need to make requests if things like rpm are already updated and transmitted at a good rate. If CAN sniffing and UDS requests could be integrated, logging could speed up.

Yes, that would be nice!

I have used inexpensive USBTin interface to read messages from CAN Bus and it seems to work okay.

Does anybody know if some more popular interface like ELM327 support streaming messages from CAN Bus ?

[pheno]

Any suggestion for good tool to watch messages in CAN bus ?

[Mik325tds]

Originally Posted by DWR

I'll share my suggestion in public. Some parameters are already flying around the CAN Bus. No need to make requests if things like rpm are already updated and transmitted at a good rate. If CAN sniffing and UDS requests could be integrated, logging could speed up.

That is generally a good idea but keep in mind that via the OBD port, only the diagnostic bus is accessible. In order to trace the much more interesting PT-CAN you'll have to splice into wires.

[pheno]

Originally Posted by Mik325tds

That is generally a good idea but keep in mind that via the OBD port, only the diagnostic bus is accessible. In order to trace the much more interesting PT-CAN you'll have to splice into wires.

Yes, that's true. And also there are number of interfaces that all work in a different way in terms of controlling them programmatically. ELM327 is very common but somehow I don't trust those cheap knockoff clones that most probably everyone own

[DWR]

Originally Posted by Mik325tds

That is generally a good idea but keep in mind that via the OBD port, only the diagnostic bus is accessible. In order to trace the much more interesting PT-CAN you'll have to splice into wires.

Are you saying there is nothing on the D Bus, without a diagnostics request?
If so, at least we can get rpm from that port as an analog signal.

[Mik325tds]

Originally Posted by DWR

Are you saying there is nothing on the D Bus, without a diagnostics request?
If so, at least we can get rpm from that port as an analog signal.

No, there are some standard messages like Klemmenstatus (Ignition status), but other than that it is pretty silent on there as far as broadcasting goes.

[pheno]

Originally Posted by DWR

Are you saying there is nothing on the D Bus, without a diagnostics request?
If so, at least we can get rpm from that port as an analog signal.

Ah, I though you knew about this Two devices will be needed to combine logs

[DWR]

Originally Posted by pheno

Ah, I though you knew about this Two devices will be needed to combine logs

Certainly understood we were talking about 2 different communications protocols. It is possible with other OEMs from just the OBDII port. Still learning this BMW stuff, haha.

[rjahl]

Pheno,

I am trying to log the GS19 and need a little help. I can get a decent data rate with one of the standard multiple parameter jobs with graphs only, when I try logging the data stream seems to stop.

I can select fewer parameters and thing get better. I don't need the 40 plus parameters and can select a fewer number is parameters but the selection process is cumbersome. Is there a way to create a custom job that selects only a few of the available parameters within the job?


Would a trace log help?

[pheno]

Originally Posted by rjahl

Pheno,

I am trying to log the GS19 and need a little help. I can get a decent data rate with one of the standard multiple parameter jobs with graphs only, when I try logging the data stream seems to stop.

I can select fewer parameters and thing get better. I don't need the 40 plus parameters and can select a fewer number is parameters but the selection process is cumbersome. Is there a way to create a custom job that selects only a few of the available parameters within the job?


Would a trace log help?

OK. So you have selected all parameters (about 40+) but when you start data logger it gets slower ? That sounds like a performance issue.. what version of TestO are you using ?

I think data logger should be able to handle 40 params. Inside TestO the data logger should be running in its own thread (added code for that perhaps over a year ago) so it shouldn't add delay / blocking to any reading operations from the other thread that reads data from serial port.

I'll try this also soon.

[rjahl]

Originally Posted by pheno

OK. So you have selected all parameters (about 40+) but when you start data logger it gets slower ? That sounds like a performance issue.. what version of TestO are you using ?

I think data logger should be able to handle 40 params. Inside TestO the data logger should be running in its own thread (added code for that perhaps over a year ago) so it shouldn't add delay / blocking to any reading operations from the other thread that reads data from serial port.

I'll try this also soon.

Yes, you are correct. Select all is much easier than trying to filter the parameters you want each time you try to log. A custom job would help but I can't do that with the ECU either.


I have to admit I'm running an older version of TestO. I think it's something like Sept 2015. I've tried some of your newer versions but have not figured out how to install the GS19 ECU or the translations. Sorry, I just went back to something that worked for me. Trying to prioritize my time.

I can run a large custom jobs with the MSV70 without any issues, so I'm assuming the problem lies with the GS19 ECU setup rather than my laptop. It's an old Intel I7 running windows 7.

Thanks in advance.

[pheno]

Originally Posted by rjahl

Yes, you are correct. Select all is much easier than trying to filter the parameters you want each time you try to log. A custom job would help but I can't do that with the ECU either.


I have to admit I'm running an older version of TestO. I think it's something like Sept 2015. I've tried some of your newer versions but have not figured out how to install the GS19 ECU or the translations. Sorry, I just went back to something that worked for me. Trying to prioritize my time.

I can run a large custom jobs with the MSV70 without any issues, so I'm assuming the problem lies with the GS19 ECU setup rather than my laptop. It's an old Intel I7 running windows 7.

Thanks in advance.

Did you remember to add line: 'gs19d' in /jobs/eculist.txt? That file contains all the ecus that get displayed on the left side. Sounds like that feature needs a GUI editor.

If you have time you're logging you could compare CPU utilization % with older version and current. I remember adding threads resulted in nice performance improvement.

What about translations, what is not working ? In newest versions you can edit them yourself if you take a look at /translation/ folder.

jobs_all_en_EN.txt is a tab delimited file containing mapping from name (result name or job name) into translated string. RES_S is used in data logger and gauge labels otherwise RES_L is used to translate result names. You can edit that file in text editor (remember to save in UTF-8) and just call 'create_translations.bat' which will generate new .qm file for fast lookup.

[rjahl]

Originally Posted by pheno

Did you remember to add line: 'gs19d' in /jobs/eculist.txt? That file contains all the ecus that get displayed on the left side. Sounds like that feature needs a GUI editor.

If you have time you're logging you could compare CPU utilization % with older version and current. I remember adding threads resulted in nice performance improvement.

What about translations, what is not working ? In newest versions you can edit them yourself if you take a look at /translation/ folder.

jobs_all_en_EN.txt is a tab delimited file containing mapping from name (result name or job name) into translated string. RES_S is used in data logger and gauge labels otherwise RES_L is used to translate result names. You can edit that file in text editor (remember to save in UTF-8) and just call 'create_translations.bat' which will generate new .qm file for fast lookup.

Yes, I did add the GS19D in the ECU list. I'll test the newer version again tonight. Sounds like you have made performance improvements, so I try to make that work first.

I'll watch the ECU utilization and let you know.

I'll give the translator another try as well. I was probably not using it correctly.

Is Feb 1017 the latest version?

[pheno]

Originally Posted by rjahl

Yes, I did add the GS19D in the ECU list. I'll test the newer version again tonight. Sounds like you have made performance improvements, so I try to make that work first.

I'll watch the ECU utilization and let you know.

I'll give the translator another try as well. I was probably not using it correctly.

Is Feb 1017 the latest version?

Yes, that's the latest from Feb 21st.

[pheno]

Oh yeah, one thing. On the plot window bottom right you see 'view refresh rate'. Set that to 2Hz for maximum performance. . It only affects how fast the view is refreshed. The data is updated always at max. speed 'on the backgound'. If you have refresh rate 50hz and lots of graphs it will hit CPU.. Thanks.

[rjahl]

Originally Posted by pheno

Oh yeah, one thing. On the plot window bottom right you see 'view refresh rate'. Set that to 2Hz for maximum performance. . It only affects how fast the view is refreshed. The data is updated always at max. speed 'on the backgound'. If you have refresh rate 50hz and lots of graphs it will hit CPU.. Thanks.

Got the latest version up and running. Speed issues seem to be resolved. Copy of log attached. Engine running but car stationary. I ran through a few gear changes to be sure things were working.

The install confused me as there was no ECU directory in the package. Once I added the ECU directory with the ECU files and set up the ODB port all was good.

I'll tinker with the translations next.

Thanks again.