Config Help.....

[Tony C]

thats strange thought i would dload megalog viewer to view the datalog, and its gives me different data out come to what the vems log viewer does :-(

it also dont show the 50.2 lambda target at 6260rpm BUT shows duty cycle at 52.0
and target lambda at 0.875 and lambda at 0.730

do i take it that my vemslog viewer is coruptted?

have just done VE analyzer and the VE table has changed according to the megalog viewer.
will try it tomorrow.

think i need to get my arse in gear and get  1.1.74 and VT running on the ecu.
thing is im into race season and show season now and dont want the car out of action like last weekend 

[Tony C]

also what should ego show? it stays at 100 and has the odd spaz and goes to 101-103

[mattias]

Don't tune old firmwares with VemsTune, upgrade them.

Some of the realtime data has had an increase in resolution, so the old firmwares report some things in an incompatible format.

[Seight-v8]

tony,

I am sure there's some problems with V1.1.44 that why i stopped using it...

Although i cant remember that much something about lambda tables sticking.

Your ego correction should if your table is right show 100%, any deviation is the amount of correction in fueling from the lambda sensor is done by the ecu, so table needs tuning.

Still your best option is upgrade firmware & vemstune, and get it running.....

Just the learning curve is hard, and i'm still not over it yet.

good luck

scott

[Tony C]

i agree scott since going to 1.1.44 i have had nothing but probs,
car ran fault free on 1.0.73 after rob sorted out a few config issues,

i will get the car onto 1.1.74 but at present like i said cant have it not drivable,
im reluctant to go racing this year on this firmware version as im not 100% happy with the hic cups its having, plus im not going to run the gas until its upgraded,

[Seight-v8]

tony,

post up your latest config or vemslog, and someone might be able to help.

scott

[Sprocket]

Tony, I am a little confused as to which Log viewer you are using. I did point out to you a while back that 1.1.44 logs do not work with VemsLogger and that you have to use Megalog viewer instead.

[Tony C]

ahhhhhhh right,
well im using megalog viewer any hows now,

i hope to end all these probs soon (i hope)

[Tony C]

still not having any joy with upgrading,

i did what i was told regarding downloading programers note pad etc and copying old config into it,
but i gather i didnt do it right as the car still didnt want to know,
i can build the engines, and tune them, but do you think i can get them to start and run on a new firmware :-(
anyone else think they can help out someone who aint got a clue :-D

[Sprocket]

Can you not just connect your PC to the ECU with 1.1.44 and then run Vemstune, check the com port in vemstune and then select 'downloawd config' then upgrade the firmware, then upload the config you downloaded with vemstune? worked for me from 1.1.47.

For cranking enrichments, you need to make note of the pulse width cold and hot from 1.1.44. Then in the new firmware, set the cranking VE value as a percentage of your 'Required Fuel' value that will give you your old hot cranking pulse width. This will now represent a value of 100% in the cranking enrichment table.

The crank enrichement table can now be extrapolated with the value of 100% in the hot area (70*C and above). You now need to work out what the percentage value is that will give you the same pulse width as the old cold crank pulse width. Taking the old cold PW and divide it by the old warm PW, then multiply the result by 100, this will gove you the -40*C value. All other values could then be tuned to give a linier graph, basicaly duplicating what you already have in 1.1.44

If you really really really get stuck, send me a PM, and We can discuss it further. I can help a little more now that I have a little more time on my hands, now that im not going to get my engine back in the car for any events untill september, lol

[Tony C]

hi sprocket,
i did the above first time round mate and things went screwy,
so gave up and reverted back to 1.1.44,
this would be ample if the kickback was cured and it had a shift light function :-D

[Seight-v8]

tony,

This is what i did.

in version 1.1.44, i took a screen shot from the pc of each tab window, and saved them all, then printed them out on to paper with 4 on a page (under printer settings).

Then upload the version you want to use, then using the paper copies, manually change all the settings one by one. There maybe a few that are new, or different so these will take trial & error to set correctly.

But you should be able to make it fire & drive, by doing this, just takes time to do.

I now do this for each new firmware i upload...and save them for future reference.

Plus i can quickly see if anything has changed or been altered after config upload.

hope this helps.

scott

[Tony C]

Cheers scott,
Im a bit reluctant to start playing to much as meant to be racing at the retro show this sunday coming with the guys from my v8 forum, BUT also really want the new firmware on before i race the car, catch 22 eh?
I may bring the ecu in from the car dload the config and msq to the pc and laptop
open the msq on the pc upload the new firmware from laptop and VT and upload the config if it allows (which i doubt as dont recognise it)
I recon im going to have to go through page by page cross ref from pc to laptop (1.1.44 to 1.1.74) to get it running on 1.1.74, fingers crossed its running before the weekend, unless anyones got a simpler way?

[Tony C]

errrrr umm
can some one tell me how to upgrade the firmware on VT please???
i goto tools->firmware->firmware upload.
error screen comes up -> could not save config
click ok then a vemstune.exe error screen comes up and says:
vemstune.exe has stopped working,
a problem caused the program to stop working correctly,
windows will close the program and notify you if a solution is available.


any ideas???
i get gauge readings in VT,
but as its a 1.1.44 version i cant do anything else :-(

[Tony C]

mmmmmm
will upload new firmware on the PC (xp)
but not on laptop (win7) with usb adapt.