3B / ABY / ADU 463 hp @ 1.8 bar power kit from ebay
Collapse
X
-
nope. That turbo should be able to produce more power then this, for less money. Go for custom mapping and original parts. This guy is a copy-cat and his parts are of no good qualityLast edited by Bram; 3 March 2010, 13:17. -
That is an interesting point, it would be nice to see where people bought their stuff, what the service was like and how much it cost. Like VEMS, where is the best place to buy in the UK?Comment
-
or the settings that they are using with their Vems..because none say nothing about it?? it is too hard t do the engine tune with Vems??
RED Mitsubishi Lancer Evolution VI TME nº 16 of 250
BLACK Mitsubishi Lancer Evolution VI TME nº 189 of 250
LWB Audi Sport Quattro projectComment
-
I guess there is a VEMS forum for that, but yes a guide to setting for each setup would be nice.
Perhaps a new thread is needed though!Comment
-
Buy it from A4kquattro or Pnanassy in US or Hungary.
Do not get hung up on it being bought in the U.K as these two guys knowledge of VEMS setup outstrips the U.K guys as they mainly do Audi only installs.
Certainly with my purchase from Pnanassy i'm running firmware versions way before anyone else on the forum or u.k with no issues after Peter has tested the new feautures.
On the vems forum DnB and Rob have done a few installs in the U.K, how audicentric I don't knowComment
-
Nice Jamo, cheers!
I think (in a new thread) I will set up a google docs form that enters details of purchases/ suppliers/ costs/ comments etc into a spreadsheet that can be viewed by any forum member..Comment
-
running non official firmwares is a choice not a priveledge, and especially on people who are just starting on vems i would suggest a stable version. Once the engine is working nicely on that, switching to any other testing/hyper/super new version is certainly easier but not necesseraly better.
I understand the need for pnannasy, a4quattro, dnb, gintis and the rest of them to keep testing and give feedback to the developers about the latest firmware that pops out, but im not sure all users want that as well.
It's up to anyone's preference, but working on an older but stable version gives no problems with running whatsoever, so a newer version is not a MUST.
Besides once again vems has announced the 'soon' the official version will be out with all glitches and problems solved.
BTW mine even still on RS232 port communication, it still gets stuck from time to time on vemstune+ it vems havent developed a good enough megalogviewer to provide easy tuning.Comment
-
Prove to me the newer ones are unstable on my audi and not as stable as 1.1.27, amazing it's not stable on who's say so? My supplier wouldn't have given me it otherwise. I had initial problems because of easily sortable issue that I now know to look for on any 1.1.6x version.
I have run both 1.1.27 and the newer 1.1.6x and the newer one works better and I have switched between the two recently whilst checking acceleration enrichment and I'm not going back to 1.1.27
Regarding Vemstune, it has never stuck for me as I know the correct settings for it that aren't documented but are now known, since version 2010-01-08 it has been 100% stable.
I've had it running for over an hour at a time on a run collecting data and tuning, no issues on a USB connector.
If you want to stay on 1.1.27 that;s fine I will tell other members it's a myth that version 1.1.6x is unstable and can't be used as it simple can with the correct setup.Comment
-
This is turning into an ineteresting for sale thread
As far as versions go, I am with Jamo, if no one was to test the new ones then there would never be any improvements. Having said that it is good to also have proven reliability. It depends on what you want really, and I am very much of the opinion that new stuff should be tested and not just by others.
I got win 7 on the release day of the RC, thats a Beta effectively, but is also a MAJOR improvement on Vista, which goes to show that some new releases can be far better than the previous versions straight out the box!Comment


Comment