![ediabas toolset32 download ediabas toolset32 download](http://3.bp.blogspot.com/-AClMC_99H4s/VefgughKCEI/AAAAAAAADYs/s5AbAVVCNKk/s1600/EDIABAS-5.jpg)
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". But you need to enter the arguments for all 3 modes, it will not accept a single entry. But judging from what I saw, you just need to enter "aus aus aus". Your screenshot does not show all the arguments. 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. There is a service available for repairing this module if you search around for "GM3 repair".
![ediabas toolset32 download ediabas toolset32 download](http://blog.eobdtool.co.uk/wp-content/uploads/2017/02/bmw-icom-inpa-ediabas-ncx-expert-full-software-4.jpg)
SOLVED: This ended up being a hardware problem and no amount of software manipulation was going to fix it. 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): How exactly do you specify the arguments to disable transportmode? Everything I tried just says "ERROR_ARGUMENT" Here is the job in ToolSet32 that I am trying to run (energiesparmode):
#EDIABAS TOOLSET32 DOWNLOAD HOW TO#
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. I have INPA/EDIABAS, NCS Expert, and ToolSet32 all working and communicating with my E53. 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. I’ve been going through a steep learning curve on BMW diagnostic software over the last 2 weeks.