VEMStune doesn't connect on Vista laptop.

[dnb]

I am using the latest VT (10/9/2009) and it will not talk to any of the 3 ECUs on my bench.

Megatune, however talks happily to all 3.  (2 are running 1.1.59 and the 3rd is 1.1.44.  Yes, I have a good v3ini file for 1.1.59 on MT )

I use Prolific USB to serial converters.  All the drivers were updated yesterday which broke everything for a while, but now it's all right again with the very latest drivers.  My GPS device and converters are fully functional with everything but VT.  My historic Subaru software (from win9x days before USB was established and serial ports were real things) even works.

I therefore conclude the problem is lurking somewhere in VEMStune or relates to my inability to use VEMStune.  From the logs, it looks like VT never tries anything other than 9600 baud to talk to the ECU.  But when I force an ECU to 9600 baud using 'ManmcB67bye' it makes no difference.  (Megatune responds as expected)

I am out of ideas now.  Do I need to upgrade any software that Vemstune relies on?   
And what log files would the developers find useful?  I can't be the only one with this problem, can I?

Thanks

[gunni]

I have got the same exact problem

[dnb]

I don't feel so alone now

Do you have a 1.1.62 MS v3ini file, and would you consider checking my 1.1.59 version?

Thanks

[rob@vems.co.uk]

Dave, please post your ini file I'd like to test it on my bench unit at some point.

[dnb]

Will do Rob.

[dnb]

Here's my ini file for Megatune 1.1.59

http://www.aqyz05.dsl.pipex.com/vemsv3.zip

There are a couple of issues where I don't know what units some things are in, so they are in raw integers (0 to 255) but other than that, it should be OK.

[gunni]

This happens with all the firmwares I have tested using vemstune,
Of course never with megatune.

[Sambas]

Just tested 10-2 release on vista business sp2 and ftdi adapter and got it working. There is one bug that you can't use COM3, missing from ecu config ports list. Port timeout I had to put 10 and use webtool to download used firmware, 1.1.61 in this case. If you need to use com3 the you can manually put it in v3gui.cfg file or change it in device manager.

[dnb]

I have just tested VT on a borrowed XP desktop with real serial ports (same files that my laptop installed from).  It works fine.  I am going to use the USB thingies now.

[dnb]

I have concluded that Prolific USB to serial converters are a work of evil.  They don't work with Vemstune, but the FTDI ones do.

Therefore, don't buy prolific chips to use with VEMS!  (Or Emerald for that matter, but that's another story )

[gunni]

So where you able to get passed with by going with a difference usb adapter or replacing the drivers.

[Arvid]

I have vista and use Sunsway USB Serial Port Adapter RS-232, and the driver from the manufacturer. (http://www.vems.hu/files/ArvidOlausen/Usb%20driver/Win_Vista.zip). It works well for vemstune! The driver who is on vems.hu (PL2303_Prolific_DriverInstaller_10311.zip) work on megatune but not the vemstune. My PC has Core2Duo processor so I had to use imagecfg.exe to patch exe files to always only use 1 processor. 

[gunni]

Just tried the latest vemstune download,

And this has not been resolved yet.

If megatune works, so should vemstune.

[paul_f]

I couldn't get the latest version of Vemstune to connect at all, just garbage was displayed.  The previous version worked okay with my adaptor 

I have gone back to megatune for now

[gunni]

Sambas on anybody on the development team.

When will this problem be fixed?

It´s not going to be possible to use .62 which has been published without making vemstune work
with more serial drivers.

Edit.

Tried it on my gf´s laptop.

Same vemstune software, both real serial port and USB one, no problems on hers.
It runs XP.

Mine with the same usb driver, same vemstune, same actual adapter but running Windows 7 and it has problems.