Pages: 1 ... 20 21 [22] 23 24 ... 34
Author Topic: Logging ME7 fast and flexible => ME7Logger  (Read 464459 times)
setzi62
Full Member
***

Karma: +142/-0
Offline Offline

Posts: 249


« Reply #315 on: July 15, 2013, 01:18:23 PM »

I have a bunch of additional ecu variables I like to log that are not automatically detected and written out... so when i create a template config file from an ecu file, it requires a bit of work (concatenating various things) etc.

I have a bunch of scripts that take care of this, including one that uncomments/comments lines from the generated config file.

Have you given any thought to making a way to streamline this workflow?

I'm not sure I got fully what functionality you need, but probably the "my_XXX" files can be used for this task.
If you use an ecu file "8D0907551M.ecu", then also the file "my_8D0907551M.ecu" is read by the logger if it exists.
You could store your manually added variables in this file. Same thing for the logger config, a file "my_8D0907551M_template.cfg"
will be read by the logger if it exists.

For the checksums topic, I have to read and look up some things at first.
Logged
setzi62
Full Member
***

Karma: +142/-0
Offline Offline

Posts: 249


« Reply #316 on: July 15, 2013, 01:23:15 PM »

Who will be first to publish a ME7 .dsh dashboard file for winlog?

Here is the dashboard I used for the video and the logger config file if you want to use it.
The usefulness of the logged things is debatable  Wink, just a collection of gauges and numbers
that move/change while you drive...
Logged
setzi62
Full Member
***

Karma: +142/-0
Offline Offline

Posts: 249


« Reply #317 on: July 15, 2013, 01:30:20 PM »

I have to take a look at this.

Setzi, how did you get around 64 variable limit in winlog and the fact that it is not refreshing the variables until you remove and re-add the driver?
I made a logger a long time ago for winlog, but it was not very nice to use because of these problems, so never released it.

I did NOT get around the 64 variable limit. The driver is just a basic example, I must even have forgotten to protect against that limit in Winlog.
But if you are logging variables for graphical display, I wonder if anybody can watch 64 things simultaneously.

The Winlog driver was just the best example to show how ME7L could be integrated into other programs using the shared library.
There will be lots of possibilities to integrate ME7L into your own applications, e.g. remote control of logging and streaming
of log data over network, merging log data with results from other sources, .... I'm looking forward to see what will show up.
Logged
nyet
Administrator
Hero Member
*****

Karma: +604/-166
Offline Offline

Posts: 12232


WWW
« Reply #318 on: July 15, 2013, 03:03:49 PM »

If you use an ecu file "8D0907551M.ecu", then also the file "my_8D0907551M.ecu" is read by the logger if it exists.

Oh wow! I think that solves my workflow issue. Thanks, as usual, setzi. You're my hero.
Logged

ME7.1 tuning guide (READ FIRST)
ECUx Plot
ME7Sum checksum checker/corrrector for ME7.x

Please do not ask me for tunes. I'm here to help people make their own.

Do not PM me technical questions! Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your experience.
Axis
Full Member
***

Karma: +4/-4
Offline Offline

Posts: 91


« Reply #319 on: July 15, 2013, 04:54:56 PM »

But I think it is possible to patch the image so this check is no
longer present and then it should be possible to connect using "double slowinit" even while the engine is running.
I would be happy to look at the code if  I could get some hints of what to look for in IDA pro.
Somehow the need to connect without engine running is even more annoying when using Winlog.
« Last Edit: July 15, 2013, 05:29:14 PM by Axis » Logged
prj
Hero Member
*****

Karma: +903/-420
Offline Offline

Posts: 5787


« Reply #320 on: July 16, 2013, 02:07:47 AM »

I did NOT get around the 64 variable limit. The driver is just a basic example, I must even have forgotten to protect against that limit in Winlog.
But if you are logging variables for graphical display, I wonder if anybody can watch 64 things simultaneously.

WinLog has it's own logging - you can make a datalog, and then you can review this datalog with WinLogView. That's why you might want to log everything.
Quote
The Winlog driver was just the best example to show how ME7L could be integrated into other programs using the shared library.
There will be lots of possibilities to integrate ME7L into your own applications, e.g. remote control of logging and streaming
of log data over network, merging log data with results from other sources, .... I'm looking forward to see what will show up.

I'll rewrite my driver to use the library, and will work with the WinLog author further to lift some limits.
Logged

PM's will not be answered, so don't even try.
Log your car properly.
setzi62
Full Member
***

Karma: +142/-0
Offline Offline

Posts: 249


« Reply #321 on: July 16, 2013, 08:21:18 AM »

I would be happy to look at the code if  I could get some hints of what to look for in IDA pro.
Somehow the need to connect without engine running is even more annoying when using Winlog.

To have double slowinit work while engine is running, I had to patch three locations.
In the image 8D0907551G, 0001, 1037354123, 0261206776 these locations were
found at following fileoffsets:
02B8BC:   3D04 -> CC00    // Replace JMPR by NOP
067026:   3D08 -> CC00    // Replace JMPR by NOP
067EF8:   3D03 -> CC00    // Replace JMPR by NOP

At all three locations it is checked if nmot_w is zero:
82'B8B8: F2F47AF8       MOV     R4, [nmot_w]
82'B8BC: 3D04           JMPR    cc_NZ/NE, L_82B8C6 (82'B8C6)        ; PATCH: NOP

86'7022: F2F47AF8       MOV     R4, [nmot_w]
86'7026: 3D08           JMPR    cc_NZ/NE, L_867038 (86'7038)        ; PATCH: NOP

86'7EF4: F2F47AF8       MOV     R4, [nmot_w]
86'7EF8: 3D03           JMPR    cc_NZ/NE, L_867F00 (86'7F00)        ; PATCH: NOP

If you disassemble the 551G image, you can hopefully determine some code patterns
around the mentioned locations that you can then find also in your image.
Logged
setzi62
Full Member
***

Karma: +142/-0
Offline Offline

Posts: 249


« Reply #322 on: July 16, 2013, 08:26:59 AM »

I'll rewrite my driver to use the library, and will work with the WinLog author further to lift some limits.

That's great, I'm curious to hear what will be the outcome of your work then.
Logged
Axis
Full Member
***

Karma: +4/-4
Offline Offline

Posts: 91


« Reply #323 on: July 16, 2013, 12:07:02 PM »

If you disassemble the 551G image, you can hopefully determine some code patterns
around the mentioned locations that you can then find also in your image.
You gave all I needed, almost too easy.  Smiley
Thank you VERY much!

I'll help those who work with 551M.

Code:
0x2B8BC   3D04 -> CC00    // Replace JMPR by NOP
0x64422   3D08 -> CC00    // Replace JMPR by NOP
0x652C8   3D03 -> CC00    // Replace JMPR by NOP

Not double checked or tested in car, but everything should be ok.

edit:
This 3 position patch worked very well, really nice. Thank you setzi62!  I've not tested the 551M but the same patch in another bin.
From what I can gather I cannot see any problem making this patch permanent.
« Last Edit: July 16, 2013, 03:52:27 PM by Axis » Logged
phila_dot
Hero Member
*****

Karma: +170/-11
Offline Offline

Posts: 1709


« Reply #324 on: July 16, 2013, 07:07:46 PM »

You gave all I needed, almost too easy.  Smiley
Thank you VERY much!

I'll help those who work with 551M.

Code:
0x2B8BC   3D04 -> CC00    // Replace JMPR by NOP
0x64422   3D08 -> CC00    // Replace JMPR by NOP
0x652C8   3D03 -> CC00    // Replace JMPR by NOP

Not double checked or tested in car, but everything should be ok.

edit:
This 3 position patch worked very well, really nice. Thank you setzi62!  I've not tested the 551M but the same patch in another bin.
From what I can gather I cannot see any problem making this patch permanent.

This is not an issue on the S4 M box.
Logged
Axis
Full Member
***

Karma: +4/-4
Offline Offline

Posts: 91


« Reply #325 on: July 16, 2013, 08:32:38 PM »

This is not an issue on the S4 M box.
I thought it was a cluster issue and since mbox binary is widely spread I assumed some would have connection trouble without double-slow.
Ohh well, good thing it only took 5min to find 'em.  Cool
Logged
phila_dot
Hero Member
*****

Karma: +170/-11
Offline Offline

Posts: 1709


« Reply #326 on: July 16, 2013, 08:39:26 PM »

I thought it was a cluster issue and since mbox binary is widely spread I assumed some would have connection trouble without double-slow.
Ohh well, good thing it only took 5min to find 'em.  Cool

You're right in that aspect. I didn't think of it from that angle, so I guess it could be useful to some cross-flashing.
Logged
phila_dot
Hero Member
*****

Karma: +170/-11
Offline Offline

Posts: 1709


« Reply #327 on: July 21, 2013, 10:55:06 AM »

The  -p switch for comport selection doesn't work for me.

I get "unable to open port error" when trying to use any port other than the port 2 default.

I have no problem keeping my cable on port 2, but I thought that I would share. This particular laptop has never run any previous version of ME7L, so I can't confirm that the issue is with the update and not something else.
Logged
nyet
Administrator
Hero Member
*****

Karma: +604/-166
Offline Offline

Posts: 12232


WWW
« Reply #328 on: July 21, 2013, 09:27:13 PM »

com port is too tightly bound with stupid random device driver settings... i prefer using the native ftdi interface (-f)
Logged

ME7.1 tuning guide (READ FIRST)
ECUx Plot
ME7Sum checksum checker/corrrector for ME7.x

Please do not ask me for tunes. I'm here to help people make their own.

Do not PM me technical questions! Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your experience.
nyet
Administrator
Hero Member
*****

Karma: +604/-166
Offline Offline

Posts: 12232


WWW
« Reply #329 on: July 21, 2013, 10:02:41 PM »

If you use an ecu file "8D0907551M.ecu", then also the file "my_8D0907551M.ecu" is read by the logger if it exists.

However, ME7Info doesn't read the my_XXX.ecu automatically? And it will not create a my_XXX-template.cfg automatically?

Quote
You could store your manually added variables in this file. Same thing for the logger config, a file "my_8D0907551M_template.cfg"
will be read by the logger if it exists.

You mean if you specifiy "MELogger logconfig.cfg" it will automatically also read my_logconfig.cfg?

I assume the my_XXX.config doesn't need all the header stuff, just a plain list of additional variables?
Logged

ME7.1 tuning guide (READ FIRST)
ECUx Plot
ME7Sum checksum checker/corrrector for ME7.x

Please do not ask me for tunes. I'm here to help people make their own.

Do not PM me technical questions! Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your experience.
Pages: 1 ... 20 21 [22] 23 24 ... 34
  Print  
 
Jump to:  

Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Page created in 0.107 seconds with 17 queries. (Pretty URLs adds 0s, 0q)