Bugs and Feature reqests
Knocksensor 2 is not working, the Software ignores the Input Settings its always input 1 aktive.
The Keyslayout/default.xml file in Version 1.066 is without funktion
Can you make a different check in Software.
example
make offline changes
go online
check data on PC and ECU
Display checkbox "USE PC" or "USE ECU"
when USE PC make a Quicksave from ECU as Backup
It is also usefull when i forget to press F2
The Keyslayout/default.xml file in Version 1.066 is without funktion
Can you make a different check in Software.
example
make offline changes
go online
check data on PC and ECU
Display checkbox "USE PC" or "USE ECU"
when USE PC make a Quicksave from ECU as Backup
It is also usefull when i forget to press F2
Re: Bugs and Feature reqests
Keys definition works in 1.067 (not released yet). There is an option in software (Tools / customise keys).
The second issue with checking tables in EMU and on PC will be available very soon.
We will check the issue with KS#2
The second issue with checking tables in EMU and on PC will be available very soon.
We will check the issue with KS#2
Re: Bugs and Feature reqests
did you the ks#2 input check ?
Re: Bugs and Feature reqests
No Limits wrote:Knocksensor 2 is not working, the Software ignores the Input Settings its always input 1 aktive.
Jadzwin wrote: We will check the issue with KS#2
I just hooked up both sensor inputs on the test bench and can confirm this. Please take a look as I've assured my clients that they are safe on 93 octane and moderate boost level.

Can you also give us some sort of "knock count" for each ignition event so we can identify offending cylinders. Or, if possible, knock retard for only offending cylinders and a channel to see retard amount for each cylinder.
Re: Bugs and Feature reqests
We have identified the problem with ks#2 input.
We still working on the solution.
We will add information for what ignition events was the knock.
Per ignition event retard control is also possible...
We still working on the solution.
We will add information for what ignition events was the knock.
Per ignition event retard control is also possible...
Re: Bugs and Feature reqests
The problem with knock solved. Now you can also read from the log what ignition event (events) caused the knock.
More information here:
viewtopic.php?f=12&t=235
More information here:
viewtopic.php?f=12&t=235
Re: Bugs and Feature reqests
Just tested and works great! Thanks for the quick update!!!
Re: Bugs and Feature reqests
Very fast for fix it
Re: Bugs and Feature reqests
Hi, I just was wondering if there are any plans for adding flags to the tuning software, like what outputs are enabled, motorsport options on or off, and so on, they are good while tuning as they will be easy to notice
Re: Bugs and Feature reqests
You can find under tool´s the option show assigned outputs to see which output is used.SUKHOI wrote:Hi, I just was wondering if there are any plans for adding flags to the tuning software, like what outputs are enabled, motorsport options on or off, and so on, they are good while tuning as they will be easy to notice
Best regards,
Jan
Jan
Re: Bugs and Feature reqests
Yes I know that, I mean like the flags used in VEMStune, they are interactive and display full data about outputs and functions working, as they are placed on the top bar for easy view, and the color changes when function is activated, I can post a photo later when am on my laptop.Jan32 wrote:You can find under tool´s the option show assigned outputs to see which output is used.SUKHOI wrote:Hi, I just was wondering if there are any plans for adding flags to the tuning software, like what outputs are enabled, motorsport options on or off, and so on, they are good while tuning as they will be easy to notice
Re: Bugs and Feature reqests
Hi!
We are finishing the final release now, we would like to publish it public at 03.01.2015
After that we start to work on new features and then we plan to add such information on the status bar.
We will also publish here the features list that will be implemented.
Now we want to finish Rolling launch control and finish the context help for all features.
We are finishing the final release now, we would like to publish it public at 03.01.2015
After that we start to work on new features and then we plan to add such information on the status bar.
We will also publish here the features list that will be implemented.
Now we want to finish Rolling launch control and finish the context help for all features.
-
- Posts:8
- Joined:Thu Aug 28, 2014 6:09 pm
Re: Bugs and Feature reqests
Some different style gauges would be nice. Like a digital gauge, a target gauge where you see 2 horizontal bars with target and actual. Bar gauges horizontal and vertical.
A trace on the maps when you open a log, then if you scroll through the logs it follows with a crosshair on any map you open, or select a range in the log, and it will highlight all blocks you went through in the maps. I know it works when you open a log and in the same window you open map, then you can see it. But the crosshair does not stay on the map. It would be nice to have an option to choose between automatic scrolling with the mouse like it is now, or a line you have to move yourself. So you can stay on a point in the log and then open a map to see where you are.
A quick math function for correction of logged afr vs target afr. One hit on a button it changes the value in the fuelmap with a calculated percentage. Maybe with some customizable conditions, how many times that block has to be logged before you can make a change with the quick math function. And maybe expand this function over a selectable range of what you logged. With conditions like between x and y TPS, change the fuel map with the corrections from the afr calculation.
Can't wait for rolling anti lag
A trace on the maps when you open a log, then if you scroll through the logs it follows with a crosshair on any map you open, or select a range in the log, and it will highlight all blocks you went through in the maps. I know it works when you open a log and in the same window you open map, then you can see it. But the crosshair does not stay on the map. It would be nice to have an option to choose between automatic scrolling with the mouse like it is now, or a line you have to move yourself. So you can stay on a point in the log and then open a map to see where you are.
A quick math function for correction of logged afr vs target afr. One hit on a button it changes the value in the fuelmap with a calculated percentage. Maybe with some customizable conditions, how many times that block has to be logged before you can make a change with the quick math function. And maybe expand this function over a selectable range of what you logged. With conditions like between x and y TPS, change the fuel map with the corrections from the afr calculation.
Can't wait for rolling anti lag

Re: Bugs and Feature reqests
For log trace, just pause the log. The log will work in background but will not scroll.
For autotune, we plan to add option to do this (eg. you drive the car, press T button and the current VE cells will be modified to AFR Target.
Rolling antilag will be finished in several days...
For autotune, we plan to add option to do this (eg. you drive the car, press T button and the current VE cells will be modified to AFR Target.
Rolling antilag will be finished in several days...
Re: Bugs and Feature reqests
This function works as follow:

All cells above selection are highlighted. If you modify selected cells and the value of modified cells is higher than the velues of cells above, the cells above are modified with the selected cell value.
It helps to build VE tables becasue in general the VE increases with the RPM...

All cells above selection are highlighted. If you modify selected cells and the value of modified cells is higher than the velues of cells above, the cells above are modified with the selected cell value.
It helps to build VE tables becasue in general the VE increases with the RPM...
Re: Bugs and Feature reqests
auto modify is very useful in building first map from scratch...
Re: Bugs and Feature reqests
how hard would it be to have 4 egt ports and injector trims for each injector ? so we can tune each bank for fueling
JSR .....uks fastest mk2 astra now with emu ecu !
Re: Bugs and Feature reqests
This feature is already done. You just need EGT2CAN controller to connect more EGT probes.
Then you assign each probe to fuel injector and you can create correction map in function of EGT
Then you assign each probe to fuel injector and you can create correction map in function of EGT