Need help with EDIABAS ToolSet32 or other software to clear an error in ZKE

[enginesong]

I’ve been going through a steep learning curve on BMW diagnostic software over the last 2 weeks. A low battery voltage in my ’03 X5 3.0 (E53) caused my main body module (ZKE3_GM4) to go into energy savings mode (also known as transport mode), so I lost windshield wipers, interior light, back hatch release, central locking, etc. Fun.

I have INPA/EDIABAS, NCS Expert, and ToolSet32 all working and communicating with my E53. I would think I should be able to disable this annoying mode on my module with at least one of these pieces of software but I have only found a reference to this mode in ToolSet32 and I am not sure how to specify the arguments to get that to work.

Here is the job in ToolSet32 that I am trying to run (energiesparmode):

http://i1050.photobucket.com/albums/s404/enginesong/BMW%20Diagnostics/toolset32_energiesparmode_job.jpg

How exactly do you specify the arguments to disable transportmode? Everything I tried just says "ERROR_ARGUMENT"

Here is the error I am trying to fix by running that job (error shown by running job "fs_lesen" or by reading the error codes on the GM3 from INPA):

http://i1050.photobucket.com/albums/s404/enginesong/BMW%20Diagnostics/toolset32_fs_lesen_results.jpg


Any help would be greatly appreciated!

SOLVED: This ended up being a hardware problem and no amount of software manipulation was going to fix it. There is a service available for repairing this module if you search around for "GM3 repair". However, the cost of a good working used unit was less than the cost of repair and still gave me some satisfaction at "fixing" the issue myself.

[alexs3d2]

Your screenshot does not show all the arguments... But judging from what I saw, you just need to enter "aus;aus;aus". Aus is off in german and Ein is on. But you need to enter the arguments for all 3 modes, it will not accept a single entry.

[enginesong]

Your screenshot does not show all the arguments... But judging from what I saw, you just need to enter "aus;aus;aus". Aus is off in german and Ein is on. But you need to enter the arguments for all 3 modes, it will not accept a single entry.

Thanks for the quick response!

You are correct, my screen shot does not show the full "Job-Info" page as there are the 3 different arguments listed (PRODUKTIONSMODE, TRANSPORTMODE, and WERKSTATTMODE) but they all have the same format and the default for each is "aus".

I thought you might need to specify all 3 arguements but I was not sure what syntax to use. I'll try "aus;aus;aus" when I get home (should be less than 1 hour from now) and report back.


Thanks for the quick response!

You are correct, my screen shot does not show the full "Job-Info" page as there are the 3 different arguments listed (PRODUKTIONSMODE, TRANSPORTMODE, and WERKSTATTMODE) but they all have the same format and the default for each is "aus".

I thought you might need to specify all 3 arguements but I was not sure what syntax to use. I'll try "aus;aus;aus" when I get home (should be less than 1 hour from now) and report back.


Well, "aus;aus;aus" does seem to satisfy the argument syntax required to run this job. I can now get the job to run with an "OKAY" confirmation status. So thanks for that!

http://i1050.photobucket.com/albums/s404/enginesong/BMW%20Diagnostics/jobcompletedokay.jpg

However, this does not fix the static error set in my ZKE. Running "fs_lesen" still shows "Error 180 Energy saving mode active" as set after clearing it (with both ToolSet32 and INPA). :(

Any thoughts?

[alexs3d2]

You may also need to run the RESET job for your module (I think it will be like STEUERN_RESET) to restart and enter the new mode. If that does not help, then try to find if a STATUS_ENERGIESPARMODE job exists which will tell you if the module is still in that mode.

[cn555ic]

Also could try using NCSexpert using expertmode profile and code the GM4 module back to default with Sg_coderien. Try it as it can hurt.

[enginesong]

You may also need to run the RESET job for your module (I think it will be like STEUERN_RESET) to restart and enter the new mode. If that does not help, then try to find if a STATUS_ENERGIESPARMODE job exists which will tell you if the module is still in that mode.

No "STEUERN_RESET" or "STATUS_ENERGIESPARMODE" available, just the following:

http://i1050.photobucket.com/albums/s404/enginesong/BMW%20Diagnostics/joboptions.jpg

If I clear the error code, which I can do from either INPA or Toolset32, it comes back immediately.

I also tried using NCS Expert/expertmode profile/sg_coderien to reset the module to default. That went as expected but did not clear the error.

Any other ideas?

[enginesong]

The only other piece of software that I have heard may be able to clear this error is DIS. So after multiple hours of getting that working (a huge PITA by the way), I was able to get communication/auto-recognition of my E53.

I did a Quick Delete and the error set in the ZKE was visible. I followed the proceedure for clearing/deleting the error and did another Quick Delete. It did not work.

Error still set - visible in DIS, INPA, and ToolSet32.

[enginesong]

UPDATE (but not a favorable one):

Gave in and took the truck to the closest BMW dealership. 2 hours later, they did no better than I was able to do.

They said the module is bad because they cannot get it to come out of energy savings mode.

I can communicate with the module just fine. I can reprogram options for interior chimes and I can command different components to work through this module using INPA. So the module does work, I just can't get it out of this mode.

[enginesong]

UPDATE 2 - replaced ZKE module with a used one. Recoded it to my vehicle with NCS Expert and then recoded the keys. Everything is working normally again. Maybe should have done this first... Hopefully this thread can help someone else out.

[cmyachtie]

Interesting that I came across this a bit late, but I am on a steep learning curve with all the diagnostic SW pieces, I just got installed on my laptop in the last couple of weeks and getting used to experimenting with them, in particular INPA and DIS is as far as I have gotten thusfar and in trying to fix my issue I did put the car in transport mode (not knowing what it was at that time) with INPA I think and later on when I realized I had actually turned things like interior lights, heater etc off. So I managed to turn them back on I forget now either with INPA under the "Activate" function or with DIS I managed to get rid of the transport mode again.
I just ignored the messages about having to enter the BMW dealer and service phone numbers and all that crap.

And then did a quick delete a couple of times to loose all the messages.

[flipture]

Sorry to bring this thread back from the dead but I'm having trouble entering the arguments correctly I think. I'm trying to reset the counters in the FRM module using the _reset_kurzschluss_sperre job. I thought that I could simply enter 0 and then 1, then 2 etc... running the job in between and do that all of the way through 64 to hit all of the light counters.

Here is the output for the counter status job...

apiJob("FRM_87","status_lampen_kurzschluss_counter","00A8","")


Satz : 0
OBJECT = frm_87
SAETZE = 1
JOBNAME = status_lampen_kurzschluss_counter
VARIANTE = FRM_87
JOBSTATUS =
UBATTCURRENT = -1
UBATTHISTORY = -1
IGNITIONCURRENT = -1
IGNITIONHISTORY = -1
Satz : 1
JOB_STATUS = OKAY
STAT_FL_LINKS_SHORT_CIRCUIT_COUNTER = 168 00 A8 .¨
STAT_FL_RECHTS_SHORT_CIRCUIT_COUNTER = 0 00 00 ..
STAT_AL_LINKS_SHORT_CIRCUIT_COUNTER = 0 00 00 ..
STAT_AL_RECHTS_SHORT_CIRCUIT_COUNTER = 127 00 7F .
STAT_BEGRL_LINKS_SHORT_CIRCUIT_COUNTER = 127 00 7F .
STAT_BEGRL_RECHTS_SHORT_CIRCUIT_COUNTER = 100 00 64 .d
STAT_NSW_LINKS_SHORT_CIRCUIT_COUNTER = 0 00 00 ..
STAT_NSW_RECHTS_SHORT_CIRCUIT_COUNTER = 0 00 00 ..
STAT_FRA_LINKS_VORN_1_SHORT_CIRCUIT_COUNTER = 0 00 00 ..
STAT_FRA_RECHTS_VORN_1_SHORT_CIRCUIT_COUNTER = 0 00 00 ..
STAT_FRA_LINKS_HINTEN_SHORT_CIRCUIT_COUNTER = 0 00 00 ..
STAT_FRA_RECHTS_HINTEN_SHORT_CIRCUIT_COUNTER = 0 00 00 ..
STAT_BREMSLICHT_LINKS_SHORT_CIRCUIT_COUNTER = 0 00 00 ..
STAT_BREMSLICHT_RECHTS_SHORT_CIRCUIT_COUNTER = 0 00 00 ..
STAT_BREMSLICHT_MITTE_SHORT_CIRCUIT_COUNTER = 0 00 00 ..
STAT_SL_BL_LINKS_1_SHORT_CIRCUIT_COUNTER = 0 00 00 ..
STAT_SL_BL_RECHTS_1_SHORT_CIRCUIT_COUNTER = 0 00 00 ..
STAT_SL_BL_LINKS_2_SHORT_CIRCUIT_COUNTER = 0 00 00 ..
STAT_SL_BL_RECHTS_2_SHORT_CIRCUIT_COUNTER = 0 00 00 ..
STAT_KZL_SHORT_CIRCUIT_COUNTER = 0 00 00 ..
STAT_IB_SHORT_CIRCUIT_COUNTER = 0 00 00 ..
STAT_NSL_LINKS_SHORT_CIRCUIT_COUNTER = 0 00 00 ..
STAT_NSL_RECHTS_SHORT_CIRCUIT_COUNTER = 0 00 00 ..
STAT_RFL_LINKS_SHORT_CIRCUIT_COUNTER = 0 00 00 ..
STAT_RFL_RECHTS_SHORT_CIRCUIT_COUNTER = 0 00 00 ..
STAT_BFD_LINKS_SHORT_CIRCUIT_COUNTER = 0 00 00 ..
STAT_BFD_RECHTS_SHORT_CIRCUIT_COUNTER = 0 00 00 ..
STAT_KLEMME_58G_SHORT_CIRCUIT_COUNTER = 0 00 00 ..
STAT_FLC_LED_SHORT_CIRCUIT_COUNTER = 0 00 00 ..
STAT_VFB_SHORT_CIRCUIT_COUNTER = 0 00 00 ..
STAT_BEL_WBL_SHORT_CIRCUIT_COUNTER = 0 00 00 ..
_TEL_ANTWORT = 20 Bytes
0000 : 90 F1 72 70 16 01 A8 A8 88 00 22 00 7F 7F 7F 7F �ñrp..¨¨ ?.".
0010 : 00 64 00 D4 .d.Ô

Any help or guidance would be greatly appreciated.