VemsTune and 1.1.6x release

[emil@vems.se]

Im leaving vt running tonight online over usb, to see what happens in the morning
So far the only difference i can see is that update frequency is ~1hz lower (21..22hz instead of 22..23)

[gunni]

The desktop is already staying alive and working 100% as I would have expected.
So first try on the XP desktop is running 15minutes without a hitch.

I will also try to install the USB adapter and test it on my XP machine, and report back.
Maybe this is really a Vista / Win7 problem

EDIT Update.

I´m now using my desktop and the usb adapter with the drivers Emil provided.
And there are no signs at all of any problems , already running 10minutes which is by far better then using Windows 7.

So it´s not VT and not the USB adapter but Windows 7 that is causing the problems on my laptop.

[GintsK]

Some weeks ago wiki suggested some new-tested prolific driver. I tried it and trash out it - I had a lot more problems than with old driver. You can find my post in wiki. Seems I have no connection issues with VT (not tested on last VT).

[Denmark]

if i try to run Firmware web tool, VT chrash every time

/Skassa

[Jamo]

Works for me and it's found version 1.1.64 for download!!!! what the 

anybody got any details on 1.1.64? changelog does not reveal anything.

[dnb]

I tried the new VT last night.  It's no better at connecting than before.

I really fail to see why it's such a problem.  Megatune works just fine.  My GPS software works just fine.  Even my old Subaru data logger (written in 2001 when I had a real serial port) works just fine.

The only thing that doesn't work is VemsTune.  I must therefore conclude that the problem lies within VemsTune and NOT within my USB to serial devices.  Changing drivers and generally messing around with computer settings is not a good solution - especially when no other software I use seems to need it - so please either explain why it's so hard and why VemsTune is so revolutionary in its use of the serial port that I need new drivers for a device which to my mind works perfectly well.  Or even better, just fix Vemstune!

Sorry for the rant - I'm getting angry about VemsTune now that it's costing me customers and making support very difficult.

[lugnuts]

I agree, it's ridiculous some of the things I have seen with the VEMS software, firmware, and hardware.
I miss the Autronic days where the thing just worked, 100% of the time, and that was that.

Example 1:
Firmware "updates" often have 5 new features, but they also seem to have 5 new bugs!???

Why can't the "old" be left well alone, and the "new" just added and tested?

If a customer were to read the "Firmware Updates" notes/comments on the wiki - they would be hard pressed to fine one that would assure any confidence at all. 

Example 2:
VEMSTune is released with nothing but bugs, software crashes, some people have connection issues, at first it did not have offline editing (useless), does not work with MegaLogViewer, so the datalogging is useless, etc.

Just stop with the "updates", and release something that works!!!


Example 3:
Hardware - Why is it even an option or an afterthought that the speed input is protected for over 5 volts, or the analog inputs are not protected from 12v ruining the mcp3208 chip, etc.

It's a support nightmare trying to fix all of these problems. Customers make mistakes. If I can spend $0.50, $5.00, or even $50.00 in hardware to prevent a problem from happening, please give me that option!

[lugnuts]

I wonder what kinds of backgrounds the developers have.
What other interfaces have they used before?

What are they used to using, that makes VEMSTune seem like something useable?

What computers and OS do they use? Since they don't seem to have any problems with VEMSTune?


It's just that....working with VEMS, I often get the feeling that I am on a different planet.

[Jamo]

I'm beginning to wonder what i've let myself in for 

Is there no way to get megatune to work with the new firmwares as a workaround for users?

[dnb]

I have Megatune working (but not exhaustively tested yet - only I have used it in anger) with 1.1.63 so don't worry too much!

[Jamo]

Any details of how you've done this?

[dnb]

I just edited the vemsV3.ini file to match the header (*.h) file for the 1.1.63 firmware.  All the data except the instructions is supplied with the firmware. 

Send me an email and I'll reply attaching the file.   It's not guaranteed to be perfect, but I am fairly sure it's OK. 

[Jorgen]

I have had some trouble recreating the connection problems with the USB adapters recently. Can those of you who have problems connecting try post some information about your system? We really want to recreate it so that we can find and eliminate the problem.

Something like this:

VEMSTune version (development release date)
Laptop brand, model: Lenovo X61
Processor: Intel Core2Duo T7300
OS (Also 32 or 64 bit): XP 32 bit.
USB-RS232 adapter brand: ST Labs (From Webshop)
USB-RS232 driver version: v2.0.13.130 (XP driver) Released 2009-12-02
Problem description: Current configuration not tested yet.

Jörgen Karlsson
Gothenburg, Sweden.

[Jorgen]

Hi,

Thanks for helping us test the software but please keep in mind that VemsTune is an early development release, the current version is 0.10.7. We hope that the first release candidate will be released 2010-01-28 or 2010-02-04.

I'm preparing for the next HU trip, I hope that we will have a RC1 when I leave HU the next time.

It's interesting to see that Mega Log Viewer is so highly regarded. I only thought that a very small number of users used it. I have failed to find a version that support VEMS at all out of the box.

I hope that our log analysis will provide a superior integrated analysis solution which eliminate any reason to use MLV. It must be preferred compared to an export-analysis-import solution like MLV. The vemscfg format used in VEMSTune is a development of the native config and tables files used by VEMS and when megatune goes out the door the msq format may become problematic to support.

Jörgen Karlsson
Göteborg

[dnb]

Thanks for replying to the thread Jorgen I'll start with the fault reports:


VEMSTune version:  All versions up to and including 0.10.7 (2009.12.04)
Laptop brand, model: Fujitsu Siemens Amilo
Processor: Intel Core2Duo T5250
OS (Also 32 or 64 bit): Vista 32 bit.
USB-RS232 adapter brand: Unbranded Prolific
USB-RS232 driver version: 3.3.2.105 Released 2008-10-27
Problem description: Cannot connect to ECU. (even though Megatune can)

Same laptop with FTDI USB device: (will get version later)
Problem description: Connects, but drops connection repeatedly with defined time period until VEMStune is restarted.  Sometimes it's 30 seconds, sometimes 10 minutes - this changes each time Vemstune is started. 

Please make it reliable before making it pretty!