VemsTune and 1.1.6x release

[emil@vems.se]

http://vems.hu/download/v3gui/VemsTune-Install-2009-12-15-testing.exe
Now with another patch that at least fixed my problem with not connecting at all.

EDIT: I was a little bit quick in posting the link, wasnt complete on the web server, but now it is.
dnb: Hope this test release solves your non-connecting problem
One small problem with todays release is the default setting for write delay, it is 5 mS,
I would recommend to start from 30, if loosing connection try higher (40?)

[dnb]

Success on all counts! 

No connection problems, and no intermittant connection drops with either usb device. 

[gunni]

The forum works 

[dnb]

Now I can get logging and stuff, I have some questions:

GWarm (the warmup enrichment) settles at 290% when the engine is warm (CLT >70C) when it should be 100%.  Megatune's log from my logging hack for firmware 1.1.63 shows 100% as it should.

Similar for GBaro - it sticks at 128%, but it seems to do that in Megatune logs too.  (I'm sure it used to do something a long time ago!!)

Given the car runs OK and hits lambda targets like it should do, I am thinking it's logging related and nothing serious.

BTW, it's worth noting that the crank fuelling and warmup seems to have changed in 1.1.63 to 1.1.59 and my Megatune hack does not have this, so you can't edit a couple of tables. 

[Jorgen]

Now I can get logging and stuff, I have some questions:

GWarm (the warmup enrichment) settles at 290% when the engine is warm (CLT >70C) when it should be 100%.  Megatune's log from my logging hack for firmware 1.1.63 shows 100% as it should.

Similar for GBaro - it sticks at 128%, but it seems to do that in Megatune logs too.  (I'm sure it used to do something a long time ago!!)
 

I checked my last logs with the 2009.12.14 VT build and GWarm behaves itself, it reads 100 with a warm engine. This is with 1.1.64 firmware. GBaro is stuck at 128% in all my logs it seems but I usually have barometric correction disabled for a number of reasons.

Jörgen

[Jorgen]

I checked some old logs I did with a 1.1.63 developer only release and the GWarm was at 290 with a fully warm engine then. It was higher while the engine was warming up. Obviously a log issue back then. I'm now running 1.1.64 in the test cars and it seems to be fixed.

My earlier logs with the internal SD card logger show 100%GWarm as expected even back with 1.1.61.

Jörgen

[dnb]

Thanks.  It had all the hallmarks of logging - the engine would have hydrolocked if it was really enriching by 290%...

I have 1.1.64, so I might give that a go when I get back home unless there is an obvious mistake in the INI file.

[dnb]

Just started looking at 1.1.64 in anger.  Most of it looks good, but there are a couple of little things:

1.  Gamma enrichment appears to be misreported - it seems to be 2.55 times too big.  (I'm sure that's just a logging issue)

2.  The tacho output (I use the P259 on my test car because I have no other spare outputs) now seems to not work at all. 

ETA:  Tacho output does work, but I couldn't get the config to properly enable it until I used the "Assign Output Channels" dialog and restart VEMStune.  I can't get the fault to happen again, so it was probably an isolated comms problem.  VEMStune crashes a lot when I used the trigger player - could be related...   

[mattias]

BTW, it's worth noting that the crank fuelling and warmup seems to have changed in 1.1.63 to 1.1.59 and my Megatune hack does not have this, so you can't edit a couple of tables. 

So you can't access them through MegaTune? That's obvious.
There are two tables (1x4) now for cranking and afterstart . Warmup is the same size and table as earlier.

[dnb]

You could edit them with Megatune, but I haven't time to rewrite the ini file to sort it out - VEMStune now works properly. 
The tables are actually 2x4 - there is a temperature and a fuel scale.  (Same temperature scale for both tables)

In fact, you can access the tables through Megatune, but not in a nice way.  The crank table in my modified ini file uses the same addresses as parts of the new table.

[Jorgen]

Just started looking at 1.1.64 in anger.  Most of it looks good, but there are a couple of little things:

1.  Gamma enrichment appears to be misreported - it seems to be 2.55 times too big.  (I'm sure that's just a logging issue)

2.  The tacho output (I use the P259 on my test car because I have no other spare outputs) now seems to not work at all. 
   

Sami and I saw the gamma enrichment issue, in his test bench it would bottom out the gamma enrich in the real time data when a trigger was not applied. He applied an audi trigger, I use a simple signal generator to stimulate the ecu with a simple trigger input. I still had the problem after applying trigger.

What kind of trigger do you use?

There is also a range problem with the reported enrichments, there is a new scale going up to 376% and there seem to be a missmatch somewhere. Christmas has stalled development, we will hopefully be able to sort this out shortly.

Jörgen

[dnb]

Trigger is standard 36-1 on the crank.  No cam trigger.  The gammae issue seems to be there with or without the trigger.

Whatever the problem is, it doesn't stop the car running and it doesn't stop the car achieving lambda target even when using a narrow ego control window.  I am therefore fairly convinced it's logging/reporting related.

Let me know if there's any testing I can do - I'm off work until the 4th Jan so I have plenty of time.

[Tony C]

after dnb's recomendation to convert the v8 to 1.1.64 and to use VT (thanks emil for the link)
and after the probs i had/having with 1.1.44 i am going to go ahead,
been reading the help files,
but bit confussed on how to save or mod a msg file?
is that the projects bit on VT?
will be setting the new version up on the v8 in the next few days but wanted to have a play with the current msq to get use to the functions/settings of VT,

[dnb]

The file format is a bit different in VT - it doesn't use a .msq file any more.  The easiest way is to connect your ECU to the laptop and save a Vemstune cfg file before you flash the new firmware.  You can then write this back on after upgrade and change the bits you need to - it'll complain about the things it thinks are daft.

[Sprocket]

The file format is a bit different in VT - it doesn't use a .msq file any more.  The easiest way is to connect your ECU to the laptop and save a Vemstune cfg file before you flash the new firmware.  You can then write this back on after upgrade and change the bits you need to - it'll complain about the things it thinks are daft.

Such as the Lambda and ingition tables, which are a different size?

I am going this route when the engine goes back in the car, but its looking like the back end of Feb or march even, so hopefully the development team will have everything sorted, progress is steaming along!!!