NefMoto

There is a text file where it explains all you need to do to get it installed. 

You need to dl a dll file for win7 to work properly.  The main key is to change the volume id.

Most will recognize the screen name in the text file if you have been around that released it.


*New direct link:
http://www.socals4.com/repair/ecux.rar

Link to the other forum, if you have to register it takes 10 min to be able to dl the files.  I am not the original poster of the files, it was a member "J_amb_o"

http://www.digital-kaos.co.uk/forums/f173/ecu-explorer-vag-logging-194138/?highlight=ecu+explorer

**See a few posts below for an installer i attached to help the process.

Not sure about the tool included to change the volume id.
Google "volumeserial.exe" for an easier one.

PS If you are running any other proggys that use that id (iirc etka, elsa), you will have to reinstall them.

Well that's a biggie!  ;D

I created an installer, just click on it and it will run.  it will ask for a password, put in "nefmoto"  No need to mess with the other files.  the installer is not a crack for this software or any means to get the software for free, it just helps out to install what is provided in the other forums rar file.

Once it closes restart your computer.

I have tested it on xp, win7 32 and win7 64 bit and it works fine.  Win 7 you may get some security popups, just ok them or run it as admin.

So to simply install ecux to your computer:

run my installer
restart
run the ecux setup
enter in the correct registration info found on the text file from the other link
import the registration when it asks
dl the missing dll file and install it if you get an error. (see attached for the file).
done.

To make sure the program is installed correctly, go to the about screen and you should see all the fields filled in, if not you need to edit the registry and re-install the program again (see some posts below on how to edit the registry).  

Also if you try to associate properties and it closes, you need to make sure the volume id is ok, if not, run my installer again.

To install the dll file, unpack it, move the dll to the windows\system32 folder
at the command prompt, (you can do run>cmd to get the prompt) type in regsvr32 MSSTDFMT.DLL " It should say "success" or "done" or something, restart computer, and now it will work.

would you mind posting the .dll needed for Win7 64-bit?

cheers!

edited the above post^^  attached with instructions how to install it, you may also if on win 7 need to run as admin at the cmd prompt, in the search on the start menu, type CMD, you will see it come up on the top of the list, right click it and run as admin :)

very nice, thanks infinkc

x2

I screwed up and entered the wrong name and company the first time.  I uninstalled the program then ran the registry editor again and restarted the computer.  Then I re-installed the program and it's still starting me at step 3 of the registration where it's asking me for the wrong dll.  :-\

I posted on QW, but figured I'd ask here too for the archives.

Does changing the volume name affect the Bentley manual?

wrong dll? or missing dll? screen shot?

Sorry, I mean wrong registration file.  I entered the wrong name and company because I wasn't paying attention so it gave me a registration code that starts off "Darrick|Darrick|54b3a2de...", so the registration file included won't match.

regedit
go to:
hkey current user\software\vb and vba program settings

delete the ecuexplorer folder completely

now re-install the setup file, chose repair.  
run the program it should prompt for the info again, once its entered it should prompt for the reg file.

Victory.  Thank you!

I'm running windows vista on my computer. Could I get this to work?

Well... the short answer is no. I ran into this same problem. As it turns out most if not all ported/hacked programs work with xp. Some work with 7. Your best bet would be to set up a virtual machine on your vista. This will allow you to run programs meant for xp on your vista based computer. I don't really understand how it works, but it will. Hope that helps.

ECUx runs just fine on Vista. I have never had a compatability problem running XP programs on Vista. A VM is definitely not necessary.

i can also confirm this.  ECUx runs on Vista and Win7 just fine.  don't even need to run as admin.  also - altering volumeID works fine in both OS's, however you DO need to open CMD as admin to run volumeID.exe.

ALSO NOTE - if you're going to change volumeID on your tuning laptop that already has TunerPro w/ MTX ME7 checksum plugin activated - the plugin activation key is related to the volumeID.   if you change it - it will no longer work and you will need a new key.

thats pretty funny to think cause im sure a majority of us will have the same vol id for the tuner pro act key.

i am getting am error "runtime error 9 subscript out of range" any help please?

this is an amazing find  :o

help please. i got exux installed but when i run the program and try to go to settings, i get the run time error 713 class not registered blah blah blah i need the following "msstdfmt.dll" which i tried to put into the system 32 folder but when i did the command prompt and type in regsvr32 msstdfmt.dll it pops up and says the module failed to load make sure the binary is stored in the specified path, which i know it is. anyway any help would be greatly appreciated, thanks in advance

is anyone even still reading this post or should i start a new one? can no one help me get this figured out?

are you at an administrator cmd prompt?

ie... windows key, then type cmd, then Ctrl+Enter

I do apologize. I hate being the guy that spreads misinformation. What I was told was exactly what I posted earlier. Again I apologize. Has anyone gotten galetto to work on vista? Or Winols?  Thanks.

yes i was in administrator cmd prompt. i even tried putting the file into the syswow64 file and doing regsvr32/64 with no success either...

problem solved. i had to uninstall ecux and then run the cmd regsvr32 msstdfmt.dll then reinstall ecux and it works fine now. i didnt even have to go through the registration process.

I am very close to having this all done, I'm getting hung up on the msstdfmt.dll file though as well.

When I try to run "REGSVR32 msstdfmt.dll" in cmd prompt, it says:
"The module may not be compatible with the version of Windows that you're running. Check if the module is compatible with an x86 or x64 version of regsvr32.exe"

I am running Windows 7 Pro. What am I doing wrong?

PS: whoever wrote the .txt file, READTHISFIRSTORIFUCKINGCUTYOU is awesome. lol.

I get a cool error when try to load the properties file in the new group.

(http://i101.photobucket.com/albums/m56/ejgsjeep/ECUXerror.jpg)

edit: got it now. had to download some missing .ocx files in my registry. also, for windows 7, i had to place everything in the sysWOW64 folder instead of the system32 folder.

now i just can't get ECUX to sync with my ECU. i have an M box ecu, and am using the VAG120 file with it, but i keep getting "ECUX can't authenticate your ECU" or something like that. I've been reading other forums that I may have to do the pin43 hardwire to get it to work, haven't got that far yet.

does ecux works with all cars?

I am getting the error: write of main specifier failed. It pops ups in a ecu acquisition window when press "start" for logging. Any ideas?

Sofar, I am getting error:
Correct password!Volume iD will now be changed...
The system cannot find the file specified.
'x' is not recognized as an internal or external command,
operable program or batch file.
Restart your computer now.

Managed to get through the mess of instructions, files, etc. and it seems "ECU Explorer" is running.
Next, plan to plug in original VAGcom cable and/or ebay cable (bought because Nefmoto did not work with VAGcom original cable, but with cheap ebay cable).
Looks like I need a data file that fits my ECU and/or car.
Car is: 2002 Allroad 2.7T 6 spd

My ECU is now labeled (after flashing with tune) according to VAGcom scan:

8D0 907 551 M (tuner apparently used S4 file)
(the original ECU label before flashing was: 4Z7 907 551 L for the Allroad).

Is there a file I should look for to start logging. If so, does anyone have a suitable file?

Trying to install on windows 7 now and I keep trying to change my volume ID and it's saying access is denied. I'm logged in as admin, what it is??

I got it work (I think) on Win7 (32bit).
Downloaded and used the 'install' routine (above).

Program starts etc. but I get error message; still need
- 'group' file
- the 'other' file

I want to use on:
- 2002 Allroad tiptronic 4Z7 907 551 M
- 2002 Allroad manual 6 spd (original label: 4Z7 907 551 L; after tune flash now: 8D0 907 551 M)
- 1998 A4 1.8T manual 8D0 907 557 N

Can someone post up the 2 file types I need to get started?

Also: is there a 'operator manual' that an be downloaded?

You guys need to follow EXACTLY, STEP BY STEP, instructions that come with ECUx to correctly install it. Don't assume anything. Just do it step by step.

After successful install, you will still need to do extra steps for windows 7. I posted on audizine what needs to be done.

Don't PM me about it though. If you can't get ecux working, download me7 logger (which is far better than ecux anyway) from this forum and forget about ecux pos.

Thanks.

Got everything working (it seems) on my win7.
But can't do anything. Apparently, 'associate property' file is missing.
I open group file "M Box".
I have a manual 2002 Allroad.
Do I need the "120" file?
a) what file extension do these 'property files' have (so I can search for it)
b) is it autmatically installed (if so, in what property). It seems the property file needs to be 'imported'
c) can someone send/post the property file I can use?
d) if not: is it 'generated'? How?

If property file is needed, but not included with the install, and/or cannot be obtained: seems I wasted a lot of time trying to install ECUx.

You imported .ERF file during install, right? (e.g. FOLLOW THE INSTALLATION INSTRUCTIONS EXACTLY)

It won't matter though since logging Allroad is hard with EcuX since some stuff is blatantly missing or converted to wrong values in definition group for allroad.

Win7 32. Installed. Program opens. But does not seem to have/find the 'group' and/or 'property file'.
Where did I miss?


"21. Now you need to load a group file. I've included a couple in this RAR. Most of you will probably use MBOX, a couple ABOX. Anyone else can go fuck themselves or try all of them.

22. Once the group file is loaded a window/table should pop up. NOW you have to assign a property file that is specific to what ECU you have. For B5 S4s here is which one you will need:


ECU    Property File
A,K    121
C    126
D    125
F    128
H,J    123
M,L    120
T,AA    122

23. It should now say that there is a valid property file loaded (VAG 120 FOR EXAMPLE) on the bottom of your group window/table."

Can I just try again going through the process from A-Z?
Or should I first delete stuff off the computer?

Eureka!!!

Uninstalled first.

Ran the change volumeID routine.
Verified VolumeID is correct.

Deleted the registry entry

-->hkey current user\software\vb and vba program settings
--> delete the ecuexplorer folder completely

Copied the DLL (actually verified it is still in the windows\systems32 folder

Ran 'regsvr32 msstdfmt.dll'

Ran 'repair'

Entered username and company (case sensitive)

In step 3, selected the 'russal adams rsa' file with erf extension

finished.

Now in about, it shows user and company.

selected m box group file.

Seems to work now

(win7 32bit).

will go out and plug in soon to see if I am golden.

Everything finally seems to work with the software, but when connecting to the car (2002 Allroad), "cannot read ECU" or so comes up.
Tried original Rosstech/VAGcom cable and blue ebay (which I use for flashing).

What additional settings do I need to change?

Com port? USB?

Works now! With the Rosstech/VAGcom cable as well as the 'blue ebay'.
Not sure how and why. But did the following:
- in settings: USB, 57600 Baud rate, 'accurate'
- start ECUx
- plug in USB cable first
- ignition on
- plug in OBDII

Used "120" group file.

Looking at the data (exported to CSV) leaves a lot of questions, mainly:
- Unit for time is msec ("314748" means 314.748 sec)?
- How "LONG" can the logs be? Is there a limit? Last date entry in "time" is: 555691. 555 seconds? In my case, I kept the log running for maybe 6 minutes (may 10?); seems a lot of data is 'missing'. From SEVERAL (may 10 at list) WOT only a few lines show Accel position = 100, and only ONE occurence; rest not higher than 50.
- At least 5 runs until limiter (7200 rpm or so), but only 1 sequence reaches 5000 rpm.
- Boost: I assume units are mBar. Actual boost = ActBoost - BarPressure (in mBar)?

Any suggestions what may be going on?

What a huge waste of time. Just use ME7l and ditch ECUx once and for all

I did some log runs yesterday (2002 Allroad manual 2.7T, stage 2).
Everything worked with ECUx.
But not sure about the numbers for MAF. My max reading was 280 g/sec (most in mid to high 275 g/sec). IIRC, the (Hitachi?) MAF I have can only read up to 220 g/sec? If not, what IS the limit of the stock MAF in my car?

Well, just did another log run, this time with VAGcom. Similar MAF readings (275 g/sec). So the 280 g/sec peak ECUx showed could be valid.

That leaves the question: what is the limit for my MAF ? (2002 Allroad manual 2.7T).

Does the old rule of thumb g/sec x 1.25 = cHP hold for the 2.7T? (280 g/sec would equate ca. 350 crank HP)

No point in even trying to estimate HP via MAF... you already have a log, run it through ECUxPlot

And ECUx Plot spits out cHP?
Also: did I miss the torque data? Or not part of the "120" or "M" group, but available elsewhere?

yes.


Torque data from the ECU isn't what you think it is.

Might want to do a quick ME7 refresher.

Humour me because I have missed previous discussion. Which of the multitude of torque variables does VCDS return in Measuring Block 120?

TTQS

nmot
miasrs_w
miist_w
miasrl_w

Can ECUx also be used on other ECUs?
For example: 1998 A4 1.8T manual
8D0 907 557 N

Quoted for truth.

What was the question you are trying to answer?

Friends don't let friends use crippled proprietary buggy abandonware