Recent Posts

All of this for a simple xml file

Making this XML file requires sitting in IDA for hours and manually searching for addresses, this is assuming you know RE.
People who know RE to this level usually get paid over 100$ per hour. A comprehensive XML that has a lot of addresses (not just a few) would cost anywhere between 300$ to 1000$ to make.
This is assuming the person making it has a similar a2l file.

I developed technology to automate this process, that still requires having at least a similar A2L file though, which again is really not easy to get for Volvo.

So yes, you can pay 100$ for credits for my software and log your car for all of eternity. Minimum purchase is 50$ btw, because that's also the price of the cheapest service, but advanced protocol without prior sub costs 100$.
Or you can continue complaining here and hope that somebody is gonna spend hours to make you the "simple xml file". Probably not going to happen.
This is a DIY forum not a "tune my car for free" forum. So if you need an xml file for your software, start learning RE, then make the xml file and post it here Come back in 5 years when you have accomplished said task. Or pay for a shortcut.

I am guessing you don't work for free, so where does the entitlement come from that you expect other people to?
What do you bring to the table that would motivate someone to use their time to help you?

A Bin file extracted from my current vida install doesn't really get me anywhere without prior knowledge of how this all works.

Nobody said anything about a bin file, that link has software to extract the locations of loggable identifiers from VIDA (those do not help you with a XML though because they are not ram addresses) and on ME7 there is a lot of important stuff missing for tuning.

There seems to be a pattern here. Embracing ignorance and making a ton of (false) assumptions. Not going to get very far with that attitude on here.

LDRPID is only part of the problem, the bigger issue is that load will stop getting calculated correctly, there are more mods required.
If you don't need over 2 bar boost just fit 3 bar sensor and underscale, it works reasonably well enough.

A Bin file extracted from my current vida install doesn't really get me anywhere without prior knowledge of how this all works.  Since I've posted I have gotten the following:

 - prj promoting his logging software in the form of "credits" with a x credit minimum purchase.
- prometey with a bin file for an essentially different car which I appreciate but it basically serves me no good with no prior knowledge of how any of this works.
- and you, athlon for giving me the link to a GitHub in order to extract a bin file from my current install of vida.  Then what?

All of this for a simple xml file in order to load it into the open source OpenMoose program so I can see what's going on with my car from a hobbyist perspective.  Does anyone even use this or is this entire thread full of people who have already worked out what's needed and have kept it in the "inner circle" 

The "simple xml file" you wish for is a collection of memory addresses people have worked out with disassembly through their knowledge of computer science. People are not out to do charity here, some do and they are very kind to do so, but if you read the forums it's about discussing and helping each other learn. If you're not here to learn, I don't think you're gonna get very far. If you simply wish to tune your software for green injectors, you can get away with it by copying over the values from a software using greens, such as the R binary prometey attached for you. Learn about what's needed to change injectors here https://s4wiki.com/wiki/Tuning and then change maps accordingly. If you can't find an XDF for your file then you'll have to make your own. Conveniently, there are a lot of defined maps for different binaries here, where map contents remain the same but at different addresses. If you know anything about hex editing you should be able to find what you need without a sweat. To help you out, KRKTE @ 0x1636A for 50QKHJ. If you want to find logging parameters on your own, learn disassembly. Prometey even put out an almost fully defined .ida file for his own software here, our favourite russian is doing a lot for the volvo community

This might help: https://github.com/spnda/volvo_vida_db

A Bin file extracted from my current vida install doesn't really get me anywhere without prior knowledge of how this all works.  Since I've posted I have gotten the following:

 - prj promoting his logging software in the form of "credits" with a x credit minimum purchase.
- prometey with a bin file for an essentially different car which I appreciate but it basically serves me no good with no prior knowledge of how any of this works.
- and you, athlon for giving me the link to a GitHub in order to extract a bin file from my current install of vida.  Then what?

All of this for a simple xml file in order to load it into the open source OpenMoose program so I can see what's going on with my car from a hobbyist perspective.  Does anyone even use this or is this entire thread full of people who have already worked out what's needed and have kept it in the "inner circle" 

[3940]

However, there are other maps in the addresses you provide.

I don’t understand what you are talking about - “there are other cards”
If your firmware is 06A906032FK 3940, then the KFZW and KFZW2 maps are 100% located at the addresses indicated above.
The rest of the “fantasies” don’t matter.
Or the ECU has been updated and the firmware inside is already different from the data on the housing label.
Post here your ecu dump.

I wanted to start a conversation regarding making that patch available. There are some people who did it already, however this information stays closed source and nobody is willing to share informations.

So i do share at least my research on that topic, which may or may not help someone to develop that patch. Maybe someone else will share some more informations.

All the informations which i cover apply to the 1K8907115F_0040 binary.

Lets start:
Generally speaking the Wastegate Duty Cycle is driven using a PID System. It takes certain parameters(refer to FR) and produces the duty cycle out of it. In Bosch Terms its called LDRPID.

If you inspect the A2L, you will notice that most variables related to the LDRPID like ps_w are scaling only to 2.5 bar.

One of the exceptions which you can find is the variable pvd_w which is scaling to 5 bar. Its explicitely written in the description("Wertebereich von 0...5120hPa" = values from 0-5120hpa").

pvd_w is "Pressure before throttle valve".

However this value is never used in LDRPID. LDRPID uses pvdkds_w. pvd_w is converted to pvdkds_w at some point in time. pvdkds_w is scaling only to 2.5 bar. Both pvd_w and pvdkds_w are uint16 datatypes.

So how does this scaling work? Lets make a example:
pvd_w(in RAM): 0xFFFF
pvd_w(as human readable value): 5 bar

pvdkds_w (in RAM): 0xFFFF
pvdkds_w (as human readable value): 2.5 bar

So after closer inspection of the code, i found the point where its getting converted. You can find that code in 0xca1a4:
"rlwinm     r6 ,r3 ,0x1 ,0xf ,0x1e"
what it basically does is: pvdkds_w = (pvd_w & 0xffff) << 1;
"Easier" said its: pvdkds_w = 2*pvd_w

So the first step to making that 5120 patch, is to remove the "multiply * 2" in the conversion to let it go up to 5 bar instead of 2.5 bar. However this is only the first step of the journey, as you will have to adjust all the maps in the LDRPID to make sure its working correctly. Some maps will need multiplying by 2, some will need dividing by two. I assume some other vars needs patches as well. One example is maybe fpvd_w, which has similar logic.

To remove the conversion you can use:
add        r6 ,r3 ,r0 instead the rlwim.
                           

Hope it will help someone one day. For now its too big as a task for me alone. Will report back if i get new informations.

This might help: https://github.com/spnda/volvo_vida_db

You can use my tool to log it. Not free, but you do not need a parameter file, as that is provided automatically by the server.

Your logging software looks amazing however it would be hard to justify the purchase with zero knowledge of what I'm doing as far as tuning goes.  Would be nice to just have a simple xml file for openmoose just to be able to mess around with since it has the capability already

You can use my tool to log it. Not free, but you do not need a parameter file, as that is provided automatically by the server.

It's R file.

Thank you!  I loaded up tunerpro and selected that bin for comparison to my personal bin.  SO many undefined items between the two I dont really feel comfortable editing anything based on that especially since its a AWD R file and mines an already modified FWD 2.5T file.  Just dont know enough about the verbiage and such unfortunately. 

And since I dont have a quick way to reflash to stock option without buying a VIDA sub, I guess I am just gonna hold off on anything related to this for now.  There seems to be an abundance of information in this thread that would help me, but only if I had some sort of previous knowledge of how this all works or at least the stock bin file for my own car.

I also was going to at least try to do some logs using OpenMoose, but I just realized that you need the param xml file, which I cant seem to find anywhere in this thread or using the google machine.  So I'm up a creek two times.