News:

New Users: Send [email protected] an email with your account name. I've turned off auto-approve to reduce the 100 new spam accounts a day. Thanks, -Jason

Main Menu

What releases and functionality planned for vems 2012

Started by Jamo, January 30, 2012, 10:43:01 AM

Previous topic - Next topic

Jamo

Hasn't been any real updates on the vems firmware page since 1.1.96 being the last official release.  Whats planned for the next few release? When are the knock tables being released for vmes

MWfire

Yes, there will be knock tables and lot of new functions.

ZoLtaR



Jamo

It's all very quiet, must be big changes ahead, not even a new vemstune. Hopefully be bery interesting

DevInAz

do we only know whats coming from the programmers by the actual releases? Or is there a page that says whats being worked on somewhere?

billman

1.2.0 and 1.1.99 are out (not release) but I don't see anything about Knock

Jamo

On the firmware page it says there has been a functionality freeze whilst issues have been addressed which is far enough
1.2.0 or 1.2.1 will be the next release hopefully we will be targetting to install!

Kamuto

Quote from: MWfire on January 31, 2012, 09:33:47 PM
Yes, there will be knock tables and lot of new functions.
so when we are going to get it? :)
Vems installer in Lithuania
[email protected]

ZoLtaR

Exactly, when we can expect new functions with knock control ?

Denmark

I say dont expect anything regarding knock control , then you Will
Not be disapointed ,


I would just love the VEMS to be able to run my Subaru engine , but the ecu lacks input to run the engine right ,
So for me it a change for another ecu ,


Rob did you ever get that Subaru running the syvecs ecu you purchased ?


Thanks
Skassa
working on the boxer

fphil

Quoteexpect anything regarding knock control
It is hard to compete with the knock detection function from the manufacturer of the car ecu. That manufacturer has a work bench, huge clean data to analyse, experience, engineers, everything to make a sensible recognition algorithm adapted to the engine.

I think that a universal solution is unreachable by Vems or any other. I simply expect some tools which helps to define and set some pattern (frequency, level etc) common to those series where a knock as been detected by the driver, listening from headphones, and marked as so onto the log data.

GintsK

Again I should remind: in Russia guys already use knock code for four years. Knock code was prepared by Andrey from Ekaterinburg. And I do not read any complaints about it in their forums. They just use it with their not so good fuel quality....

In official wiki some time ago was 1.1.89 version. I knew who use this code with success. In addition those configs what I see with complaints all was  with wrong settings under knock section.

Andrey has also much more stable engine phase angle reading algorithm what VEMS use for injector angle and cam control. Official firmware has some delay for one cycle or one revolution (!) what makes both functions bad at low rpms or high accelerations. (look at VT raeding for sec trigger angle under free rev - it floats a lot!) His reading stays constant like glued (I mean engine with fixed cam, not VVT)

In addition his firmware mod controls automatic transmission on their RHD Toyotas http://www.tourerv.ru/ widely used in those area.
As I knew he is welcome to share his code with developers. But as we see something did not happening there :(

Gints

Jamo

The official line was the knock code caused the ignition timing to be incorrect?  When can we expect to get all this back into vems? it seems weird the code is ready but not in a firmware for use

billman

Quote from: Jamo on June 14, 2012, 01:55:21 PM
The official line was the knock code caused the ignition timing to be incorrect?  When can we expect to get all this back into vems? it seems weird the code is ready but not in a firmware for use

That's right!

Does Andrey want to share his FW/settings. has he implemented it in newer FW Versions? We have also crap fuel here  :)