VemsTune and 1.1.6x release

[lugnuts]

<<< 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'm a big fan of the MLV, but I am excited to see Datalogging being regarded as a high priority with the VEMS developers.

- I sell more ECU's based on the quality of the MLV when compared to other ECU brand's datalogging.
- It puts me in a very bad position to be losing this feature (MLV) in search of newer firmware / features.


- What problems do you have with MLV and VEMS? (I used from 1.076 to 1.53 firmware so far with MLV)



My favorite MLV Features:
- Can scale any log channel min and max (useful to visually line-up several lines in the graph)
- Having several graphs total (up to 4 total, keeps the clutter, uncluttered)
- Can convert MAP to Boost(Psi)
- Ability to customize log channel Names (by modifying VEMS MT ini files)
- Can hide the Dashboard, gauges, and Field Select for un-obstructed graph viewing
- Can keep the cursor centered
- Can adjust the amount of data that takes up the screen horizontally
- can choose any color for graph lines, background, etc.

General Data Logging Requests / Recommendations:
- "One Key Touch" when PC Logging (save the file naming for later, after the log is completed
- Internal SD Logging (like to use this ASAP)
- ECU setting to automatically turn internal Logging ON/OFF (I use 3,500 rpm with other ecu brands)
- Ability to "zero out" or "shift" the time line in the log display (for example, when the car launches, make this "0.00 seconds"
- Integrated logging within the ECU interface (It is good that VEMSTune logging will do this)



<< 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. >>

- This is great. I just need to have my MLV until this is fully ready!

[GintsK]

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.

Jörgen Karlsson
Göteborg

It means you never tried it? IMO any of last two years versions work with VEMS out of the box. LT401Vette is author of MLV he has just 10 posts here but result is awesome. I have little modified MSGraph.properties file for supporting other tables like Boost table. But main tables and analyzer is compatible as is.

Jörgen, you realy need try how it works. To overcome this piece of software is hard to reach goal. Especially in ease of use, visual representation, speed and stability.

I can afforce good points of MLV:
-easy to read information about current, minimal maximal values for each chanel
-easy to migrate over all datalog, easy to catch any point in datalog under cursor
-current engine working point representation on numeric tables
-possibility to compare two datalogs with overlying
-live logging: MLV can read file currently logged by tuning program
-averaging calculations of marked area of datalog for each chanel
-possibility to create calculated channels
-possibility to define range of any channel (automatic by default)
-save necessary/desired chanels combination (alpha-N, boosted, n/a S-D engine).
-not laggy
- no bugs!

And here is no word about VE analyser. Just viewer.

Gints

[gunni]

I have narrowed my problems down to the OS being Vista or Windows 7.
Absolutely NO problems with XP based OS´s on desktops or laptops serial port or prolific usb adapter.

VEMSTune version - ALL
Laptop brand, model: Packard Bell
Processor: Intel T1600 Core duo
OS (Also 32 or 64 bit): Windows Vista first and then Windows 7 32bit
USB-RS232 adapter brand: SEWELL 1103
USB-RS232 driver version: All driver versions
Problem description: Random "ecu not connected" , occurs between 0-10minutes, mostly within the first 2minutes, Input stream from
ecu is corrupted and tables become corrupt if refreshed. I have configured the vemstune.exe to run on a single processor but that did not help things.

In MLV i have designed a graph line that represents the correct VE based on gve, lambda readings, lambda target, air temp compensation, EGO control. This makes VE tuning literally an hours job or less and makes datalog based tuning ultra easy.
Using the MAX and MIN, I make GVE and VE correct have the same max and min, all I have to do is look at those lines and see how far off they are, the closer they are the less fine tuning or any tuning is needed.

I have used MLV for all my tuning , both live tuning and offline tuning. It´s real nice to be able to jump into MLV that is trailing a live file and review something quick that you missed during a conversation with the driver. So there is no need to repeat the same load site.
Especially things like MAT and CLT that you may have missed while looking at other gauges.
I have even made MLV work with a ecu that outputs a format no where near VEMS and MS I like it that much.

So datalog related I think it´s important that a very easy to manipulate (custom graph lines through mathematical functions combining many data inputs) program is used within VT - I reccomend you guys take a look at the Race Technology datalogging software and how it allows you to create complex data channels and helps in making very complex formulas from simple table inputs, such as temp at 30C = 2v , 60C = 5v , 90C = 5.5v . This makes changing hard Voltage numbers into meaningful figures that are accurate.

I have also never had to do anything to MLV to make it work with any megatune log file ms or vems. It even works better with Vems then MS because of the lambda target and lambda channels that I use for Gve calculations

I have yet to be able to tune with VT so I can´t comment on that, but I think the
lambda target / lambda bar gauge to be very clever and will probably be very helpful.

One important aspect I think needs to be addressed is the use of h[2] table names and any other hex values to be bad.
but I´m sure this will disappear eventually.

[Arvid]

Hi Jørgen. To me it looks like that vemstune do not like the Core 2 Duo processor. I have to modify vemsTune.exe, vemsTune-c.exe, and VemsLogger.exe with imagecfg.exe. So that they use only one core.

Uploaded imagecfg.exe and imagecfg.bat files to make it easier for everyone to test.
http://www.vems.hu/files/ArvidOlausen/IMAGECFG-2.zip

Computer nr1.
Firmware: 1.1.62
VEMSTune version (2009.12.04)
Laptop brand, model:Hp NX9420
Processor: Intel Core2Duo T5600
OS : Vista 32 bit SP2.
USB-RS232 adapter brand: ST Labs (From Webshop)
USB-RS232 driver version: (19.11.2009 V 3.3.10.140 works ok)     (31.01.08 v 3.3.0.1 also works on my computer)
Problem description:The ecu will become disconnected after 2-5sek.
Problem  solution :I had to use imagecfg.exe to patch exe files to always only use 1 processor.

Computer nr2.
Firmware: 1.1.62
VEMSTune version (2009.12.04)
 brand, model:MSI
Processor: AMD Penomen 2 X4 810
OS : Windows 7 Ultimate 64bit
USB-RS232 adapter brand: ST Labs (From Webshop)
USB-RS232 driver version: (19.11.2009 V 3.3.10.140      (31.01.08 v 3.3.0.1 )
Problem description:The ecu will become disconnected after 2-5sek.
Modify vemsTune.exe, vemsTune-c.exe, and VemsLogger.exe with imagecfg.exe  does not work on this computer :-(



Arvid Olausen
Høyanger, Norway.

[emil@vems.se]

Thanks for the input
I would like to add one thing to the reports if possible,
in the folder where you have installed vemstune, a file called "filelog.txt" is created every time the program starts, might be only when using Vemstune-c.exe

Please copy this after a failed connection, and either post link here or email to me ( emil@vems.se )

thanks / Emil

[gunni]

Email Emil

[Jamo]

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. 

Sent a mail the other bud did it get through ok?

[Jamo]

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

I find myself slightly discouraged by that statement 

I've just bought a VEMS recently and will be running a pirate version of 1.1.63 and my car is booked to be mapped the start of Jan

But if VEMS tune is still in development release and no R1 candidate is being released until the end of jan why is there no official megatune support until the R1 is out?

I hope I do not find myself in a situation where I will be out of pocket because the vemstune will not be stable enough to use as I know there are other issues such as the lambda values being incorrect at present.

[gunni]

You can always use a older firmware version.
As they do have almost all the features and have run thousands of cars now.

[dnb]

Sent a mail the other bud did it get through ok?

I replied too.  I assume it hasn't arrived, so I will send it again.

BTW it fixes the lambda reporting error too

[Jamo]

You can always use a older firmware version.
As they do have almost all the features and have run thousands of cars now.

I didn't buy an ecu with 1.1.63 to downgrade it heh

Bys the by DnB has come up with a great option if vemstune isn't up too the job for me   

[dnb]

My email seems to not be working at the moment.  Looks like the ISP has "upgraded" its server again...

I have put the file here:  http://www.aqyz05.dsl.pipex.com/vemsv3.zip

The file should be put in the mtcfg folder of the project you wish to use and MT should read it.

It should work with the main features including logging and table editing, but it may not scale some of the more obscure parameters correctly.  Please tell me if I've made any mistakes or omissions and I'll correct them.

[emil@vems.se]

Today there was a new test version published,
There is a new settings called "inter write delay", if you had problems with usb-rs232 adapters, try to change this to 40 mS to start with, and see if it works better. Vemstune has to be restarted for this value to be active. This has proven to solve the loosing connection problem on some computers

I had a setup which refused to connect at all here,
found another fix for this that will be included in next test version

There is still a bug in prolific's driver that is hard to get around, it crashes with AIM stream on before port is opened.
Recommendation for people with AIM enabled is to first start vemstune, then turn ECU on, this will keep the driver from crashing.


thanks / Emil

[dnb]

Still no go with the new VEMStune and prolific adaptor (as expected).  I will try the FTDI adaptor and the dropping comms issue in the morning.

[gunni]

Win7 40ms and there are no more problems.
Prolific driver for Windows 7 is 2.0.019 by Prolific and comes from the link emil put up.

At 50ms when I changed the TPS the Battery voltage would change... Which is very strange.

EDIT.
Still going strong 50minutes, So this is resolved for me at least.