Pages: 1 [2]
Author Topic: NLS/LC B_gsch script workaround?  (Read 2367 times)
redrum667
Newbie
*

Karma: +1/-3
Offline Offline

Posts: 15


« Reply #15 on: April 11, 2025, 03:32:18 PM »

Some news !  Sad

I extracted my original flash file from my ECU (using kess so not the full read).
I used Me7Info to see the definitions (idk exactly what i should call them) and begin to work on a automated script to add the DSG-Farts-Spark-Cut

I'm really surprised, i cannot find definitions for b_zwget neither b_gsch  Huh

HWNumber          = {0261208088}
SWNumber          = {1037369383}
PartNumber        = {022906032CB }
SWVersion         = {5604}
EngineId          = {MOTRONIC ME7.1.}

If someone want to check the .ecu file see attached
Logged
redrum667
Newbie
*

Karma: +1/-3
Offline Offline

Posts: 15


« Reply #16 on: April 11, 2025, 03:37:32 PM »

Dump your whole ECU, more than half the code is not in the extflash.

I'll do that, what I was thinking when I read the launch.php script (NLS & LC ME7.X) is that the script adds functions in a “rather simple” way. I wanted to adapt it to simply add the ignition cutoff on gear change, but I couldn't find the definitions for b_gsch and b_zwget, they could be defined elsewhere in the MPC/uC for example?
Logged
redrum667
Newbie
*

Karma: +1/-3
Offline Offline

Posts: 15


« Reply #17 on: April 13, 2025, 01:20:12 PM »

UPDATES

To achieve what I want to do, I need to find the address where b_zwget will be stored at runtime. Using ME7info.exe I thought it was going to be easy (not at all  Grin), I have neither the b_zwget variable nor B_GSCH so I can't write my function because I won't be able to “tell the ECU” what to do when b_zwget starts populating because I don't know where it is.

I've tried to find .kp, .a2l, damos and others but I can't find any that answer my question, the only thing I've found is a golf 5 R32 damos that I pull out of I don't know where  Huh (but which shares the same PartNumber = {022906032CB } as my car)
and which tells me when I open it via WinOLS in the RAM folder that B_ZWGET is at address FDAA and B_GSCH is at F062C.

The “problem” is that I'm not 100% sure of the info because even if the flags are at the same address between winols & the .ecu there are some differences... Undecided

From now on, what I'm going to do is directly log the car and look for the address of this damned “b_zwget”, unless someone has the answer to my question and can provide me with the address, but in the meantime I'm going to work on it solo and keep on searching the forum for info because I won't have the car to hand for a few days.

I'm writing this just for the record...
« Last Edit: April 13, 2025, 01:21:47 PM by redrum667 » Logged
redrum667
Newbie
*

Karma: +1/-3
Offline Offline

Posts: 15


« Reply #18 on: April 14, 2025, 12:07:09 AM »

Here is my bin just in case
Logged
prj
Hero Member
*****

Karma: +1095/-516
Offline Offline

Posts: 6176


« Reply #19 on: April 14, 2025, 01:27:50 PM »

Look at the FR where it's used, find other variable located by ME7Info that is used "close" by tracing this variable you will find your bitfield.
Logged

PM's will not be answered, so don't even try.
Log your car properly - WinOLS database - Tools/patches
rogerius
Full Member
***

Karma: +71/-7
Offline Offline

Posts: 130


« Reply #20 on: April 15, 2025, 01:18:28 AM »

Here is my bin just in case

I think B_gshc is FD1A.9.
Logged
BlackT
Hero Member
*****

Karma: +80/-42
Offline Offline

Posts: 1470



« Reply #21 on: April 15, 2025, 05:33:53 AM »

UPDATES

To achieve what I want to do, I need to find the address where b_zwget will be stored at runtime. Using ME7info.exe I thought it was going to be easy (not at all  Grin), I have neither the b_zwget variable nor B_GSCH so I can't write my function because I won't be able to “tell the ECU” what to do when b_zwget starts populating because I don't know where it is.

I've tried to find .kp, .a2l, damos and others but I can't find any that answer my question, the only thing I've found is a golf 5 R32 damos that I pull out of I don't know where  Huh (but which shares the same PartNumber = {022906032CB } as my car)
and which tells me when I open it via WinOLS in the RAM folder that B_ZWGET is at address FDAA and B_GSCH is at F062C.

The “problem” is that I'm not 100% sure of the info because even if the flags are at the same address between winols & the .ecu there are some differences... Undecided

From now on, what I'm going to do is directly log the car and look for the address of this damned “b_zwget”, unless someone has the answer to my question and can provide me with the address, but in the meantime I'm going to work on it solo and keep on searching the forum for info because I won't have the car to hand for a few days.

I'm writing this just for the record...
Post that A2L you have Then I can find what you are looking for in your file
Logged
redrum667
Newbie
*

Karma: +1/-3
Offline Offline

Posts: 15


« Reply #22 on: April 15, 2025, 01:06:34 PM »

Post that A2L you have Then I can find what you are looking for in your file

Here is the V632.a2l

Also the Damos_r32.ols (022906032CD) is the file i found where you can see the RAM in Winols.

What i did was looking into Damos_r32.ols, some bits arent the exact same as mine but some are at the same RAM address when i crosscheck with my own .ecu file made with ME7INFO.
Logged
rogerius
Full Member
***

Karma: +71/-7
Offline Offline

Posts: 130


« Reply #23 on: April 16, 2025, 02:24:32 AM »

I think B_gshc is FD1A.9.
and
I think B_zwget is FDAA.7
Logged
fknbrkn
Hero Member
*****

Karma: +210/-24
Offline Offline

Posts: 1511


mk4 1.8T AUM


« Reply #24 on: April 16, 2025, 03:18:33 AM »

you can use migs_w for your routine aswell
Logged
redrum667
Newbie
*

Karma: +1/-3
Offline Offline

Posts: 15


« Reply #25 on: April 16, 2025, 03:01:47 PM »

you can use migs_w for your routine aswell

So you advise me to not bother using b_zwget and directly check migs_w?
Logged
Pages: 1 [2]
  Print  
 
Jump to:  

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