NefMoto

Hello, does somebody knows or can point to way to enable/modify/or put ECU values into its can-messages ?
.. like Boost (vag can-id 0x555) which is available not in all turbo MED9x

thanks

yes, they are stored in ram locations
so any tweaks available here

There is a function read the FR it's called embassies iirc

hey
did you have any success in adding boost pressure 0x555 to canbus??

regards

Same question again:

I like to activate Motor_07 and Motor_05 message on CAN-bus of a MK1 Audi TT with ME7.5

Taking a look into FR, the activation should be done by CW_CAN_S, witch should be a 16bit binery value.
A2L tells differend, CW-CAN_S are 4 times awailible but only in 8bit size..
But all CW_CAN_S values are set to 0xff, so at the end, all CAN-values are enabled.
But why are they not on CAN-bus ?

So I Need to tweak E2 to activiate Motor_05 and Motor_07 too ?

Could this be done by coding ?

Anyone ever worked on this and can give advice ?

BR

there is no way to add this by coding

:(

any other idea to active the Motor_07 message ?

In FR, there seems also a value SY_CAN_Config responcible for different kind of CAN Messages. But I cannot find SY_CAN_Config in A2L ..

No more idea yet, CW_CAN_S should be the right value, but this seems not to work, or got the wrong address in A2L

SY_CAN_Config is a compile-time option, can't be changed in a "ready" binary.
CW_CAN_S won't do that either. You have to research the format of said CAN frame (FR should have this info), then disassemble the binary to find where CAN communication is, then manually add the code for filling out and sending said message. Not an easy task, but totally doable.

Thanks, this is the info I was missing and I don´t want do read  :(

An new compilation is not a task of mine, so no Motor_07 message availibe on my ECU..

Good to know for someone else, who has the same idea and  is looking for that info

there is 2 or 3 unused bytes in ecu outgoing can-bus messages
any value can be added here if you good with ida things :)

I never worked on this yet..

IDA-things normaly needs new compilation and if you need to re-compile, you can also active Motor_07 ID AFAIK.
As long as it needs to have a new complilation for that function, I am out so fare :(


btw and a bit OT.:
I know for other SW, if you re-compile, you will get new addresses and a new *.A2L.
If someone chance the ME7 Software with some additional code, I expact the same, and original A2L or Damos wil not work..
Am I true with this ?

You either:
a) Have source code for ME7, which I doubt
or
b) Couldn't hack your way out of a paper bag and need to do some serious reading.

Ehmm yes, that is what I worte :(

can confirm to this ?

ida is not compiler but dissasembler

and again you cant compile whole binary if you havent sources for that

with ida you can understand how the ecu handles can-bus data, write some code in asm, compile it and change/add it in your file thru hex editor

Thanks again for your explanation  :)

Ok, if I unterstand you right, you just wirte your own code, compile and add the code in hex via editor to the original code. (so, you A2L will not change in this case, good to know !)

But I also need to twique the original code, to jump into the new code and jump back to original, witch will be also done in hex-editor, base on the research of IDA?!

At the end,
if you allready have your own code or twique the original code to use unused space in e.g. Motor_06, Byte 6 (0x488), I can take over this hex-code via hex-editor in my APP software ?
I think CAN-haendler will be the same in all software...