I feel a bit presumptuous making a Bug report because this may well be down to my inability to use the software correctly - however:
I'm using Multiecuscan 2.0 and cannot get the "settings/interfaces" dialogue box to remember any settings.
I had previously used the free version of 1.9 with a KKL/Vag interface to clear airbag fault codes - but recently I've needed to replace a window regulator. So I acquired an ELM327 (modified) cable and spotted also that the software had been upgraded so I installed that too.
I'm pretty confident that I've got the drivers installed properly; the interface checks out on all the tests and can be found and correctly described with "Scan for Interfaces" and is reported as working.
But when I close that dialogue box and try to connect to an ECU the software tells me I need to have an ELM cable - (whuch of course I do). Having read on here about the problem with some interfaces I checked if I could at least contact the Engine ECU - but then the message I get is that "Port 1 doesn't exist".
When I open the settings/ interface dialogue box again I see that there are no interface settings recorded there.
Any help or insight would be very much appreciated
MES 2.0 settings/interface
Re: MES 2.0 settings/interface
Well - I seem to be able to answer my own question here.
I uninstalled 2.0 and reinstalled 1.9. I then found that the dialogue box in question in the earlier version has a tick box where you can tick "OK". That portion of the dialogue box is missing on the newer version - so you can't save it - not on my netbook anyway.
I uninstalled 2.0 and reinstalled 1.9. I then found that the dialogue box in question in the earlier version has a tick box where you can tick "OK". That portion of the dialogue box is missing on the newer version - so you can't save it - not on my netbook anyway.
Re: MES 2.0 settings/interface
Hmmm this is getting annoying now:
I didn't uninstall 2.0 but made a fresh installation of 1.9 on the Win 7 partition (ELM327 will work on Win7) of my netbook to confirm that it was the new update that was the problem.
However my old KKL cable will only work on XP so I uninstalled 2.0 from the XP partition of the netbook - but the 1.9 installer will not let me put it on because it says I have a newer version already installed (when clearly I haven't because I just uninstalled it and ran CCleaner Registry Cleaner to remove any stray registry entries).
Clearly the uninstaller leaves orphan entries in the registry that I cannot shift so I am unable to downgrade to the earlier version.
So now I am unable to use my KKl interface (hope my airbag light doesn't come on)!!!
I didn't uninstall 2.0 but made a fresh installation of 1.9 on the Win 7 partition (ELM327 will work on Win7) of my netbook to confirm that it was the new update that was the problem.
However my old KKL cable will only work on XP so I uninstalled 2.0 from the XP partition of the netbook - but the 1.9 installer will not let me put it on because it says I have a newer version already installed (when clearly I haven't because I just uninstalled it and ran CCleaner Registry Cleaner to remove any stray registry entries).
Clearly the uninstaller leaves orphan entries in the registry that I cannot shift so I am unable to downgrade to the earlier version.
So now I am unable to use my KKl interface (hope my airbag light doesn't come on)!!!