Quote1.0.78 is now useable, including SD logging and MAT-enrich tuning.
Vemstune will get some convenience
and warning features, eg. if HIGHBOOST=0 but ECU is in highboost (table kpa unit=2 kPa) mode.
See
http://www.vems.hu/wiki/index.php?page=GenBoard%2FUnderDevelopment%2FFirmwareChanges
1.0.78 seems good so far, officially testing, but basically ready for release.
* after uploading config, you MUST __MANUALLY__ ADJUST
* MAT correction (enrichment) (X and Y axis, 8+8 values, use defaults)
* N2O (disable)
* use recent [vemstune]
vemsTune-Install-2008-08-06.exe or later to set these
* and to set SD log parameters (automatic logging to SD card after engine start) and save [SD log] and convert to csv for analysis
http://www.vems.hu/download/SD/v3SDcard.htm
Am I seeing two things.
a SD card logger.
a New GUI?
It looks like it doesnt it? Having tested the GUI I find that it crashes almost all of the time, so I'd stick to using MT with the .ini file provided.
Regarding the SD card, theres even some info on how to set it up: http://www.vems.hu/download/SD/v3SDcard.htm
On my XP it crashes too.
Yea it crashed on my Vista as well.
IÃ,´m also seeing duty cycle boost control, Am I too assume itÃ,´s working with 1.0.78 firmware?
The .ini file for Vemstune does that work with MegaTune? Is that what yourÃ,´s saying.
I am digging though having the gauges when your tuning which wasnÃ,´t possible with MT, i.e I always used the VE table and not the live tuning bit. cause I donÃ,´t like that view :)
All the complaints I've ever had have been about the lack of a live table (no +&- function on cells or rows).
About a year ago I did this:
Some more development on the Table Editor, which is still very much in Alpha and effectively non-functional (no ECU interaction).
Ctrl-L allows editing of the load table.
Ctrl-R allows RPM table editing.
Ctrl-C copies the content of the selected cell.
Ctrl-V pastes the copy into the selected cell or group of cells.
F9 changes to VE table.
10 changes to Ignition table.
11 changes to Lambda table.
Select a group of cells in the main table:
Page Up to increase the cells' value.
Page Dn to decrease the cells' value.
Type a numeric value to set the selected cell's
Bounds checking for keyed entry (0-255 for VE, xx.(25|50|75) for ignition, 0.7->1.x for lambda) Lambda does not scale correctly - please advise
Small increment with q|+|Pg Up
Small decrement with w|-|Pg Dn
Large increment with e|Ctrl +|Ctrl Pg Up
Large decrement with r|Ctrl -|Ctrl Pg Dn
Paint value - Ctrl Up, Down, Left, Right
Download from http://www.vems.co.uk/VEMSTech/table.zip
No one seemed bothered so I didnt carry on development.
DAMN
That needs to be in the table tuning those are AWESOME commands and desperately needed.
I use Megatune 2.25p1.
It allows to select any square region on table and do + - * and =.
http://www.diyautotune.com/videos/megatune/megatune225p1_multicell_select.wmv
Very usable!
GUI allows select row or column = less usable. Allways need some region.
Do you have an executable? I'll put together a MegaTune download with the correct .ini files if you do.
Cheers
Rob
It is here: http://not2fast.com/megasquirt/mt/2.25/mt225p1_setup.exe
IRC megatune.exe was enough.
Hi,
Ooohh, this all looks good ;D
Please gimme the + & - setup, I really miss that!
Cheers,
Gavin :)
Will we get this 1.0.78 with that megatune in package?
Quote from: mr_g on August 13, 2008, 08:22:03 AM
Will we get this 1.0.78 with that megatune in package?
It feature stands in any package on my PC: just replace megatune.exe
I usually put the MegaTune+Vems firmware packages together so I'll be doing this when I'm happy that 1.0.78 is working well.
If you want to set up a test package with MT
I have a great candidate to test some of the things on.
most importantly duty cycle boost control.
The VE table tuning functions in the p1 MT package.
http://kotisivu.dnainternet.net/sakrkorh/vems/firmware_1.0.78.zip
Is this yours Rob?
It doesnÃ,´t seem to have the live table editing bits.
That aint mine, you might want to try dropping those binaries that Gints posted and you should have the live table stuff.
Rob, you could be nice to us, and compile a complete packede of the 1.0.78, with every thing needed.
There are some new things in the 1.0.78 packede, that are on the wiki side, and i will try to upload that to the Subaru when i get the time...
/Skassa
Quote from: gunni on August 28, 2008, 07:13:53 PM
http://kotisivu.dnainternet.net/sakrkorh/vems/firmware_1.0.78.zip
Is this yours Rob?
It doesnÃ,´t seem to have the live table editing bits.
It have. Be little more accurate with mouse!
Quote from: GintsK on August 29, 2008, 07:58:08 AM
Quote from: gunni on August 28, 2008, 07:13:53 PM
http://kotisivu.dnainternet.net/sakrkorh/vems/firmware_1.0.78.zip
Is this yours Rob?
It doesnÃ,´t seem to have the live table editing bits.
It have. Be little more accurate with mouse!
What are the commands?
I wasnÃ,´t getting anything to work testing and live editing and multiple cells
Just watch this video!
http://www.diyautotune.com/videos/megatune/megatune225p1_multicell_select.wmv
Hope this helps!
Gints
Got it :)
this is an excellent upgrade.
Now having a working lambda meter in the VE table would be nice.
Have any of you tried the 1.0.78?
It seems that i need to take out lots of fuel in the ve table, and even lowering the req fuel, to get the car running, this is if i write 100 in the MAT enrichment.
I have disabled the N2O settings, and have made a new load and rpm bin, as this gets totaly wrong, when uploading this, over the 1.0.73, that was in before.
I have now put back in the old 1.0.73, to get the car running again, as it seems a bit random with the fuel needs....sometimes it needs more sometimes it needs less????
And i did not cure the start/cranking error i got,this week i will try a small adaptor board add-on, to see if it can cure the cranking problems, and make it start like its supposed to.
This is a small print that will change the signal from the cas and cam to a 4+1 signal,so i hope that the vems can run that, without problems
/Skassa
I havenÃ,´t yet.
What is causing different PW?
Quote from: gunni on September 15, 2008, 05:30:48 PM
I havenÃ,´t yet.
What is causing different PW?
Yes that is the question, i dont know, but the fuel requrement is not the same with 1.0.78 as it is with 1.0.73, lots of fuel needs to be removed from the ve table.
I could be nice to know the scaling that is used to the MAT enrichment, the scale in megatune goes to 155, i dont know if that means :'(
:o :o :oTHIS IS A TEST RELEASE - USE AT YOUR OWN RISK :o :o :o
I've done a new candidate of this:
http://www.vems.co.uk/VEMSTech/VemsMT1.0.78rc2.zip
It has a new version of makeconfig.exe which copes with the extended configuration properly.
:o :o :oTHIS IS A TEST RELEASE - USE AT YOUR OWN RISK :o :o :o
Quote from: Denmark on September 15, 2008, 05:34:17 PM
Yes that is the question, i dont know, but the fuel requrement is not the same with 1.0.78 as it is with 1.0.73, lots of fuel needs to be removed from the ve table.
I could be nice to know the scaling that is used to the MAT enrichment, the scale in megatune goes to 155, i dont know if that means :'(
All I can find is this: http://www.vems.hu/wiki/index.php?page=MembersPage%2FPhatBob%2FFieldReport
Quote from: Denmark on September 15, 2008, 05:34:17 PM
Quote from: gunni on September 15, 2008, 05:30:48 PM
I havenÃ,´t yet.
What is causing different PW?
Yes that is the question, i dont know, but the fuel requrement is not the same with 1.0.78 as it is with 1.0.73, lots of fuel needs to be removed from the ve table.
I could be nice to know the scaling that is used to the MAT enrichment, the scale in megatune goes to 155, i dont know if that means :'(
What is needed is the FULL explanation of the fuel calculations for each firmware.
then we could see the relationship and difference that are causing this strangeness
Quote from: [email protected] on September 15, 2008, 11:38:22 PM
Quote from: Denmark on September 15, 2008, 05:34:17 PM
Yes that is the question, i dont know, but the fuel requrement is not the same with 1.0.78 as it is with 1.0.73, lots of fuel needs to be removed from the ve table.
I could be nice to know the scaling that is used to the MAT enrichment, the scale in megatune goes to 155, i dont know if that means :'(
All I can find is this: http://www.vems.hu/wiki/index.php?page=MembersPage%2FPhatBob%2FFieldReport
Okay,Thanks,
This gives me a idea on a start up setting.
Thanks,this will be helpfull.
/Skassa
Edit. I cant get the GUI Vems Tune GUI to work, for what ever reason. Also MT 2.25p3 looks and works like any other MT :-\
What am I doing wrong :-[
Edit,Edit GUI Vems Tune GUI seems to work now for me with only a coupel of glitches that causes a crash, but, i have not yet connected to the ECU :D
Whats the score with the Megatune 2.25p3? It doesnt look like that, that is in the video linked above, and I cannot select and modify any more that one cell. And, there are no task buttons on the top right.
Quote from: Sprocket on September 21, 2008, 03:34:16 AM
Edit, GUI seems to work now for me with only a coupel of glitvhes, but, i have not yet connected to th ECU :D
Whats the score with the Megatune 2.25p3? It doesnt look like that, that is in the video linked above, and I cannot select and modify any more that one cell. And, there are no task buttons on the top right.
Are you see multiple cells editing video?
Im seeing the video, and I like it.
Is that version of MT actualy available?
Look in this thread for it.
You have to be meticulous with the mouse to be able to select.
After selecting the top right buttons show up
Good man :) You are right
:D Im useless lol :-[
;D
Ok just upgraded, here is the MAT table after letting the car sit and idle for quite a bit,
I just kept EGO control as close to 100% as when the intake heated up the ego had to keep adding a little bit of fuel.
So by using the MAT table I was able to keep the EGO at 100%.
I also changed to 16x14 tables, I had to re do them from the old ones but that only took a little time.
Injection output and ignition output settings went missing, but that was a easy fix as well.
(http://myndasafn.bmwkraftur.is/d/62866-1/mat_correction.gif)
IÃ,´m also seeing that my intake is a super blistering HOT air intake.
Now we just need
MAT Ignition table to go with it.
In the MAT fuel table I think there should be a lambda gauge, is that hard to change?
This is really great with some examples on how to get this to work,
great,
Skassa
Nice to have something to take the place of the "fake airden low limit" at long last! (remember to change it to a smaller number if you were using it...)
Does anyone know if this new MAT enrichment COMPLETELY takes the place of the old one based on ideal gas laws (that gave 100% fuel at 20C and reduced it above this) or is yet another multiplying factor in the fuelling calculation?
I can now add a calculator for this setting to my data analysis and setup program :)
DonÃ,´t use those settings though,
as IÃ,´m still using the fake air dense, as well as that is before I changed the inj open time and that changed the VE table alot,
and now itÃ,´s alot lower , will probably change when I take the fake air dense away.
Quote from: gunni on September 27, 2008, 04:45:29 PM
In the MAT fuel table I think there should be a lambda gauge, is that hard to change?
Its a case of editing the vemsv3.ini file. It makes sense that the lambda gauge should be on there.
Ahh thanks for that :)
IÃ,´ll have a gander at it and see what I can do with it.
I had a play, and the gauge is easily changed, by changing the gauge = matGauge value.
Which gauge you decide to use is up to you, but I think the EGO Correction gauge is a little better than just the lambda gauge, as that shows the actual correction.
Just a thought on this, would it not be easier for us humans, to keep the corrections all in a similar format where the Warmup correction is base line at 100%. At the moment it looks like the MAT corrections are baselined at 0%.
Just makes it easier as you wouldnt then get confused, one less thing to think about.
While Im here, For a while I have been wondering what the 'coolant' bins are for and how to work it. What does it actualy do?
I'm with you on keeping all of the corrections biassed to the same thing! It's confusing at the moment as to which things are "no correction" at 0% and which are "no correction" at 100%.
Ok just one other thing.
Boost Control Alternate settings
Boost control target offset - what is this, what does it affect. (im looking at this as an N2O control ;) )
Some how I worded my post wrong, I was thinking more of the lines of having a lambda and or other gauges in the 2d VE table.
I like that format when tuning and not the 3d view.
right now I have to go in and out repeatedly
Quote from: gunni on September 30, 2008, 10:52:34 PM
Some how I worded my post wrong, I was thinking more of the lines of having a lambda and or other gauges in the 2d VE table.
I like that format when tuning and not the 3d view.
right now I have to go in and out repeatedly
All eyes are on Phil Tobin's new GUI software as a solution for the piss-poor tuning software we're mired with. ;D
Rob
Rob - is there a reason why in the XML files, the sparkTable has been renamed advanceTable? Also, the lambda MAP and RPM bin names have changed... (Annoying for those of us who rely on these names in our analysis software!)
BTW I have added code to my analyser to normalise GEGO corrections to a fixed temperature so that better VE table tuning is possible. It also gives a corresponding new table for MAT enrichment. I'll be testing it tonight.
Quote from: dnb on October 01, 2008, 11:19:57 AM
Rob - is there a reason why in the XML files, the sparkTable has been renamed advanceTable? Also, the lambda MAP and RPM bin names have changed... (Annoying for those of us who rely on these names in our analysis software!)
They got renamed for MLV compatibility
If there's a list of changes (other than those I've mentioned), I'd appreciate it!
also AFR side has changed like "lambdaTable" to "afrBins1" and output channel from "afr" to "AFR(WBO2)"
Rob and others,
I'd like to say a big "Thank You" for your efforts here. I don't get in here much but I do get a ton of valuable information here.
I'm attempting to sell these things for a living, and a useable, "non geek" GUI is critical.
I will gladly offer any input and testing that I can.
If someone wants to help me with some changes I am trying to make, I would pay them for their efforts.
I'm mainly interested in streamlining and un-geeking the look and function of the software. I have done some work already (organized tuning and output functions better, added help, got rid of coolant bins and other useless settings), but I am not nearly an expert.
As for hotkeys and useability, I'm used to Autronic software - with which I would challenge anyone on the planet to tune an engine as quickly and effectively.
About Phil Tobins new GUI - does anyone here talk to him personally? De we have his blessing to use the program (or is it exclusively for m---squirt?)
His Megalogviewer program is excellent and I would like him to be involved with our projects.
Kevin
Lugnuts9 (AT) MSN (DOT) com
Hi,
I have to say, I'm with him! ^
The VEMs tune looks good and should do things like FW update easily compared to what we have now.
Unfortunately we don't seem to know who's behind it or when it will be completed?
Realistically speaking it doesn't matter who does the software as long as it is user friendly :)
Have we got any programmers on this site with a few spare weeks to knock something up? ;D
Cheers,
Gavin :)
I emailed Phil when I saw his software and he was all for implementing VEMS into it.
I donÃ,´t know where it is at the moment but his software looks very promising,
known as Tunerstudio, He did tell me that heÃ,´d have a working setup soon enough.