dma logger + live tune
Thread Starter
Newbie
Joined: Jun 2014
Posts: 96
Likes: 44
From: Russia
dma logger + live tune
Hi guys.
For the past 5 years I have been fond of tuning Mitsubishi. During this time, a huge number of add-ons have been written for the stock control unit.
I was fundamentally not happy with the speed of logging parameters of existing loggers.
It turns out that almost all stock firmware have the ability to use DMA logging (evo 6-10) and for this purpose I wrote my logger about a year ago.
Avaliable 100Hz (100 frames per second 48 bytes or 24 parameters of 2 bytes each), 200Hz, 800Hz, Cas interrupt, etc.
It supports address requests for RAM addr values and mut tables (engine + AT)
100 Hz log example: https://cloud.mail.ru/public/5FSC/2dU2Ls9as
Now I am working on improving my dma logger.. added some plots, dash and etc.
https://www.facebook.com/groups/2638...8259224558681/
Also, for my new project, I am working on a live tune client.
It parses the Ecuflash definition xml and adds all possible tables for the tracer (2d, 3d + all scaling for correct view and edit). Some tables are already available for editing online.
https://www.facebook.com/groups/2638...8263204558283/
some live map tests in car on ugly camera
If this is interesting to anyone, I would be happy to hear suggestions for revision my program
For the past 5 years I have been fond of tuning Mitsubishi. During this time, a huge number of add-ons have been written for the stock control unit.
I was fundamentally not happy with the speed of logging parameters of existing loggers.
It turns out that almost all stock firmware have the ability to use DMA logging (evo 6-10) and for this purpose I wrote my logger about a year ago.
Avaliable 100Hz (100 frames per second 48 bytes or 24 parameters of 2 bytes each), 200Hz, 800Hz, Cas interrupt, etc.
It supports address requests for RAM addr values and mut tables (engine + AT)
100 Hz log example: https://cloud.mail.ru/public/5FSC/2dU2Ls9as
Now I am working on improving my dma logger.. added some plots, dash and etc.
https://www.facebook.com/groups/2638...8259224558681/
Also, for my new project, I am working on a live tune client.
It parses the Ecuflash definition xml and adds all possible tables for the tracer (2d, 3d + all scaling for correct view and edit). Some tables are already available for editing online.
https://www.facebook.com/groups/2638...8263204558283/
some live map tests in car on ugly camera
If this is interesting to anyone, I would be happy to hear suggestions for revision my program
pisyakot - looks very interesting. 
Where can I get a copy? I've been looking for something like this since ziad stopped supporting his .NET live tune app years ago. EvoScan can only log at 10Hz and you need greater definition in many cases.
Where can I get a copy? I've been looking for something like this since ziad stopped supporting his .NET live tune app years ago. EvoScan can only log at 10Hz and you need greater definition in many cases.
Newbie
Joined: Apr 2014
Posts: 4
Likes: 0
From: Malaysia
Airtrek Turbo live tuning
Hi guys.
For the past 5 years I have been fond of tuning Mitsubishi. During this time, a huge number of add-ons have been written for the stock control unit.
I was fundamentally not happy with the speed of logging parameters of existing loggers.
It turns out that almost all stock firmware have the ability to use DMA logging (evo 6-10) and for this purpose I wrote my logger about a year ago.
Avaliable 100Hz (100 frames per second 48 bytes or 24 parameters of 2 bytes each), 200Hz, 800Hz, Cas interrupt, etc.
It supports address requests for RAM addr values and mut tables (engine + AT)
https://www.facebook.com/groups/2638405116210760/permalink/2788217817896155/
100 Hz log example: https://cloud.mail.ru/public/5FSC/2dU2Ls9as
Now I am working on improving my dma logger.. added some plots, dash and etc.
https://www.facebook.com/groups/2638...8259224558681/
Also, for my new project, I am working on a live tune client.
It parses the Ecuflash definition xml and adds all possible tables for the tracer (2d, 3d + all scaling for correct view and edit). Some tables are already available for editing online.
https://www.facebook.com/groups/2638...8263204558283/
some live map tests in car on ugly camera https://www.youtube.com/watch?v=MqncvVgQCMQ
If this is interesting to anyone, I would be happy to hear suggestions for revision my program
For the past 5 years I have been fond of tuning Mitsubishi. During this time, a huge number of add-ons have been written for the stock control unit.
I was fundamentally not happy with the speed of logging parameters of existing loggers.
It turns out that almost all stock firmware have the ability to use DMA logging (evo 6-10) and for this purpose I wrote my logger about a year ago.
Avaliable 100Hz (100 frames per second 48 bytes or 24 parameters of 2 bytes each), 200Hz, 800Hz, Cas interrupt, etc.
It supports address requests for RAM addr values and mut tables (engine + AT)
https://www.facebook.com/groups/2638405116210760/permalink/2788217817896155/
100 Hz log example: https://cloud.mail.ru/public/5FSC/2dU2Ls9as
Now I am working on improving my dma logger.. added some plots, dash and etc.
https://www.facebook.com/groups/2638...8259224558681/
Also, for my new project, I am working on a live tune client.
It parses the Ecuflash definition xml and adds all possible tables for the tracer (2d, 3d + all scaling for correct view and edit). Some tables are already available for editing online.
https://www.facebook.com/groups/2638...8263204558283/
some live map tests in car on ugly camera https://www.youtube.com/watch?v=MqncvVgQCMQ
If this is interesting to anyone, I would be happy to hear suggestions for revision my program
Cheers
It turns out that almost all stock firmware have the ability to use DMA logging (evo 6-10) and for this purpose I wrote my logger about a year ago.
Avaliable 100Hz (100 frames per second 48 bytes or 24 parameters of 2 bytes each), 200Hz, 800Hz, Cas interrupt, etc.
It supports address requests for RAM addr values and mut tables (engine + AT)
https://www.facebook.com/groups/2638405116210760/permalink/2788217817896155/
100 Hz log example: https://cloud.mail.ru/public/5FSC/2dU2Ls9as
Avaliable 100Hz (100 frames per second 48 bytes or 24 parameters of 2 bytes each), 200Hz, 800Hz, Cas interrupt, etc.
It supports address requests for RAM addr values and mut tables (engine + AT)
https://www.facebook.com/groups/2638405116210760/permalink/2788217817896155/
100 Hz log example: https://cloud.mail.ru/public/5FSC/2dU2Ls9as
Trending Topics
You're saying you're getting 48 byte * 800HZ DMA logging through the Openport 2.0 K-line interface on an Evo VIII/IX with stock, unmodified firmware?
Something doesn't add up. 800Hz * 48 bytes would require a bitrate of over 300kbps. Even 100Hz * 48 bytes is 38.4kbps, significantly higher than the default baud rate.
In the past, we've seen patches to add DMA logging functionality to the firmware, but I've never seen any mention of DMA logging functionality built-in to the factory firmware. Surely one of the past firmware modders would have found it by now.
In the past, we've seen patches to add DMA logging functionality to the firmware, but I've never seen any mention of DMA logging functionality built-in to the factory firmware. Surely one of the past firmware modders would have found it by now.
Last edited by Construct; Feb 28, 2020 at 01:02 PM.
Did some searching. Found the OP's other posts on a Russian forum:
https://www.drive2.ru/l/529841185481...age=0#comments (Use Google Translate)
Key section via Google Translate:
If I'm reading this correctly, the claim is that there is a DMA logger common to many Mitsubishi ECUs. The only evidence is the OP's videos on YouTube though. Would be great if we could get some more information.
https://www.drive2.ru/l/529841185481...age=0#comments (Use Google Translate)
Key section via Google Translate:
And I remembered that at the beginning of any firmware lies a code associated with the exchange of data. And it’s especially nice that this is on all mitsu machines, i.e. be it H8 percent - evo 5-6 \ galanti \ vry, or SH7052 / 55 - evo 7-9, lancers 9, tracks or even m32r - Evo x, lancer X, etc.I really did not want to disassemble this hell. But the party said it was necessary!
Dismantled everything to the cog and realized the scale of the tragedy. From the factory there is the possibility of logging at higher speeds, but what really is there. space, Japs damn geniuses 😀
There are a huge number of DMA logging modes, I counted 7-8. Until filling in the interruption of the crankshaft sensor. But we are interested in the main 3, namely 100Hz, 200Hz and 800Hz logging. Which ~ is equivalent to 100, 200, 800 frames with data per second, and this is sooo fast. What is more than enough for any of the possible tasks.
And the best part is that you can log data from the MUT table, as well as any RAM memory addresses without any flashing. And this is a very nice bonus.
Dismantled everything to the cog and realized the scale of the tragedy. From the factory there is the possibility of logging at higher speeds, but what really is there. space, Japs damn geniuses 😀
There are a huge number of DMA logging modes, I counted 7-8. Until filling in the interruption of the crankshaft sensor. But we are interested in the main 3, namely 100Hz, 200Hz and 800Hz logging. Which ~ is equivalent to 100, 200, 800 frames with data per second, and this is sooo fast. What is more than enough for any of the possible tasks.
And the best part is that you can log data from the MUT table, as well as any RAM memory addresses without any flashing. And this is a very nice bonus.
Last edited by Construct; Mar 1, 2020 at 11:36 AM.
Thread Starter
Newbie
Joined: Jun 2014
Posts: 96
Likes: 44
From: Russia
You're saying you're getting 48 byte * 800HZ DMA logging through the Openport 2.0 K-line interface on an Evo VIII/IX with stock, unmodified firmware?
Something doesn't add up. 800Hz * 48 bytes would require a bitrate of over 300kbps. Even 100Hz * 48 bytes is 38.4kbps, significantly higher than the default baud rate.
Something doesn't add up. 800Hz * 48 bytes would require a bitrate of over 300kbps. Even 100Hz * 48 bytes is 38.4kbps, significantly higher than the default baud rate.
I don’t think anyone did this. :-D
Did some searching. Found the OP's other posts on a Russian forum:
https://www.drive2.ru/l/529841185481...age=0#comments (Use Google Translate)
Key section via Google Translate:
If I'm reading this correctly, the claim is that there is a DMA logger common to many Mitsubishi ECUs. The only evidence is the OP's videos on YouTube though. Would be great if we could get some more information.
https://www.drive2.ru/l/529841185481...age=0#comments (Use Google Translate)
Key section via Google Translate:
If I'm reading this correctly, the claim is that there is a DMA logger common to many Mitsubishi ECUs. The only evidence is the OP's videos on YouTube though. Would be great if we could get some more information.
Yes, that's right. H8, SH7052/7055, m32r. I plan to release a logger with some donation. Because all of this took me a ton of time
Newbie
Joined: Mar 2020
Posts: 1
Likes: 0
From: Amarillo,TX
Very cool stuff. I'll follow along eagerly. I'd be happy to send a donation if the fast logger stuff can be shared. If I get some time I'll fire up IDA and poke around again.
Newbie
Joined: Mar 2026
Posts: 1
Likes: 0
From: Oxford UK
Nice one, are you planning on releasing this program?
I have a JDM E7 ECU running 90556701 Tephra SD rom but would be really cool to have live mapping via Openport 2 at least. It's the only major bug bear I have with it having to reflash instead of livemap.
I see my rom has DMA patch code, but not sure how to use it as think it's only available on Openport 1.3 normally (which I don't have the cable so never tried).
Some of the other features such as DBW support, ignition vs fuel cut limiters, per cylinder knock control, warning alarms etc. would be really cool too if they can be merged alongside tephra but I guess this is not possible.
I have a JDM E7 ECU running 90556701 Tephra SD rom but would be really cool to have live mapping via Openport 2 at least. It's the only major bug bear I have with it having to reflash instead of livemap.
I see my rom has DMA patch code, but not sure how to use it as think it's only available on Openport 1.3 normally (which I don't have the cable so never tried).
Some of the other features such as DBW support, ignition vs fuel cut limiters, per cylinder knock control, warning alarms etc. would be really cool too if they can be merged alongside tephra but I guess this is not possible.
Thread
Thread Starter
Forum
Replies
Last Post
