What do you mean by fix AFR target in log ?killerbee wrote:Is there a way or maybe future update to fix afr targets in log , I make very good log but my afr targets were set to 14.7 since I do not use close loop and now want to test autotune but can not modify aft targets
Bugs and Feature reqests
Re: Bugs and Feature reqests
We cannot reproduce this crash, however we know some customers have such issue
clem wrote:WOW autotune rocks ^^ GREAT JOB Guys![]()
btw, when I clear the log with the button, windows says that emu client does not work anymore and I have to close it.
Re: Bugs and Feature reqests
Jadzwin wrote:What do you mean by fix AFR target in log ?killerbee wrote:Is there a way or maybe future update to fix afr targets in log , I make very good log but my afr targets were set to 14.7 since I do not use close loop and now want to test autotune but can not modify aft targets
By the time I made the log the whole afr target table was 14.7 , so now I want to autotune using this log but want to set aft target to 12 and I can not edit the log . So it will be good the autotune function use afr targets from the project file not from the log .
Re: Bugs and Feature reqests
I'm sorry but autotune is log based and it doesn't use tables for calculation.
Re: Bugs and Feature reqests
Hi,
is it possible to get a Boost DC ref table and a Boost target table for each gear?
Because the precentage solution is not really the best one.
Last weekend, I had a car where the turbo is surging at higher gears.
It would be handy to just change the DC in lower revs at higher gears.
With the percentage solution, the boost pressure gets less over the whole rpm and I dont want less power.
Or maybe you have a ohter solution for me?
is it possible to get a Boost DC ref table and a Boost target table for each gear?
Because the precentage solution is not really the best one.
Last weekend, I had a car where the turbo is surging at higher gears.
It would be handy to just change the DC in lower revs at higher gears.
With the percentage solution, the boost pressure gets less over the whole rpm and I dont want less power.

Or maybe you have a ohter solution for me?
-
- Posts:26
- Joined:Wed May 13, 2015 1:59 am
Re: Bugs and Feature reqests
I don't understand. If you mean use my configuration file then yes I did I tried refreshing it for 2,days tried a bunch of things but computer freaks out on the new update,and I just can't get any help. Anyone help me out I'm on older firmware and can't go up cause it over fuels my car and I don't want to wash out my cylinders,and oil and more.Ace-Motorsports wrote:upload your saved rom from the previous firmware, and then try again.
Re: Bugs and Feature reqests
At the moment you cannot use data imported via the KeeLog import for autotune because the KeeLog does not read Lambda target.
Load a log from the KeeLog and select autotune and it just suggest 0 for all of the VE table as it thinks the lambda target is 0.
Also I am having issues with my table switch, I have the table switch set so that when the CAM#2 pin is earthed it switches to table 2, my log (and can be felt when driving) is rapidly flicking between table 1 and 2 but it doesn't always do it, sometimes works fine and other times it flicks between tables rapidly.
I have uploaded a small log file where if you look at 'Table Set' you can see it switching for no reason even though the relay is closed circuit and providing an earth path for CAM#2 pin.
I have changed the wiring, used a different earth location but nothing changes, if anyone cares to suggest why I would love to hear as I have ran out of ideas.
Edward.
Load a log from the KeeLog and select autotune and it just suggest 0 for all of the VE table as it thinks the lambda target is 0.
Also I am having issues with my table switch, I have the table switch set so that when the CAM#2 pin is earthed it switches to table 2, my log (and can be felt when driving) is rapidly flicking between table 1 and 2 but it doesn't always do it, sometimes works fine and other times it flicks between tables rapidly.
I have uploaded a small log file where if you look at 'Table Set' you can see it switching for no reason even though the relay is closed circuit and providing an earth path for CAM#2 pin.
I have changed the wiring, used a different earth location but nothing changes, if anyone cares to suggest why I would love to hear as I have ran out of ideas.
Edward.
- Attachments
-
- TableGlitch.zip
- (787.62KiB)Downloaded 37 times
Re: Bugs and Feature reqests
Already fixed
kornfed2jz wrote:I don't understand. If you mean use my configuration file then yes I did I tried refreshing it for 2,days tried a bunch of things but computer freaks out on the new update,and I just can't get any help. Anyone help me out I'm on older firmware and can't go up cause it over fuels my car and I don't want to wash out my cylinders,and oil and more.Ace-Motorsports wrote:upload your saved rom from the previous firmware, and then try again.
Re: Bugs and Feature reqests
We are aware of it. Lambda and AFR target will be added soon.
What ground do you use for CAM#2 ? Did you enable pullup ?
What ground do you use for CAM#2 ? Did you enable pullup ?
Mobilelpg wrote:At the moment you cannot use data imported via the KeeLog import for autotune because the KeeLog does not read Lambda target.
Load a log from the KeeLog and select autotune and it just suggest 0 for all of the VE table as it thinks the lambda target is 0.
Also I am having issues with my table switch, I have the table switch set so that when the CAM#2 pin is earthed it switches to table 2, my log (and can be felt when driving) is rapidly flicking between table 1 and 2 but it doesn't always do it, sometimes works fine and other times it flicks between tables rapidly.
I have uploaded a small log file where if you look at 'Table Set' you can see it switching for no reason even though the relay is closed circuit and providing an earth path for CAM#2 pin.
I have changed the wiring, used a different earth location but nothing changes, if anyone cares to suggest why I would love to hear as I have ran out of ideas.
Edward.
Re: Bugs and Feature reqests
Sounds great, but what was the reason for this issue?Jadzwin wrote:Already fixed
kornfed2jz wrote:I don't understand. If you mean use my configuration file then yes I did I tried refreshing it for 2,days tried a bunch of things but computer freaks out on the new update,and I just can't get any help. Anyone help me out I'm on older firmware and can't go up cause it over fuels my car and I don't want to wash out my cylinders,and oil and more.Ace-Motorsports wrote:upload your saved rom from the previous firmware, and then try again.
Best regards,
Jan
Jan
Re: Bugs and Feature reqests
Actually there is a problem with importing old project when firmware is upgraded.
So the project after upgrade must be loaded manually
So the project after upgrade must be loaded manually
Re: Bugs and Feature reqests
Feature Request: PID Boost DC direction inverting option.
My electrical wastegate actuator works that way, that an increased DC means a more open wastegate (dc controls the position of the wastegate flap).
Only inverting the "solenoid" output does not help with this issue.
So I hopefully can run closed loop boost control soon
Thanks guys!!!
My electrical wastegate actuator works that way, that an increased DC means a more open wastegate (dc controls the position of the wastegate flap).
Only inverting the "solenoid" output does not help with this issue.
So I hopefully can run closed loop boost control soon

Thanks guys!!!
Fuel Injector cleaning and flow measuring service needed? -> contact me :)
Re: Bugs and Feature reqests
If you select invert it will work as you wish. Think about it still as increase DC increases boost.
Re: Bugs and Feature reqests
Hi,
Thanks for the reply.
That's great, it will be nice to use the Keelog data for autotune even if it just to get a broader picture of any areas in the map that are slightly off that don't get driven in much.
Yes I have 'enable pullup' selected under the cam2 options.
I have the cam 2 pin earthed to the body of the car (about 2 inches from one of the vehicles standard earth points, I have moved it but still the same)
As I run the car on gas and petrol I have separate maps for each fuel, the LPG map on table 2 runs with increased ignition timing and a leaner map so at the moment every time the table switches back to petrol map but I am running LPG, the AFR goes really rich to below 10.0 and the ignition timing drops to the petrol setting.
I have the table switch set through a relay where the LPG live solenoid activates a relay which then earths the CAM#2 pin.
I hope this helps to find a solution to the table switching issue.
Thanks,
Edward.
Thanks for the reply.
That's great, it will be nice to use the Keelog data for autotune even if it just to get a broader picture of any areas in the map that are slightly off that don't get driven in much.
Yes I have 'enable pullup' selected under the cam2 options.
I have the cam 2 pin earthed to the body of the car (about 2 inches from one of the vehicles standard earth points, I have moved it but still the same)
As I run the car on gas and petrol I have separate maps for each fuel, the LPG map on table 2 runs with increased ignition timing and a leaner map so at the moment every time the table switches back to petrol map but I am running LPG, the AFR goes really rich to below 10.0 and the ignition timing drops to the petrol setting.
I have the table switch set through a relay where the LPG live solenoid activates a relay which then earths the CAM#2 pin.
I hope this helps to find a solution to the table switching issue.
Thanks,
Edward.
Jadzwin wrote:We are aware of it. Lambda and AFR target will be added soon.
What ground do you use for CAM#2 ? Did you enable pullup ?
Mobilelpg wrote:At the moment you cannot use data imported via the KeeLog import for autotune because the KeeLog does not read Lambda target.
Load a log from the KeeLog and select autotune and it just suggest 0 for all of the VE table as it thinks the lambda target is 0.
Also I am having issues with my table switch, I have the table switch set so that when the CAM#2 pin is earthed it switches to table 2, my log (and can be felt when driving) is rapidly flicking between table 1 and 2 but it doesn't always do it, sometimes works fine and other times it flicks between tables rapidly.
I have uploaded a small log file where if you look at 'Table Set' you can see it switching for no reason even though the relay is closed circuit and providing an earth path for CAM#2 pin.
I have changed the wiring, used a different earth location but nothing changes, if anyone cares to suggest why I would love to hear as I have ran out of ideas.
Edward.
Re: Bugs and Feature reqests
You are the bestJadzwin wrote:Working on this. Should be ready this week. It will be fuel cut idle
SUKHOI wrote:Hi guys, thank you for the amazing job its just getting better and better with every version you make, good job.
I was wondering if there is a possibility to new idle mode to be used with ALS, there ignition cut idle mode is not that good, as it will run the manifold hotter, as I tried to manipulate the fuel cut to make better idle with ALS, as its working fine, but if there is dedicated fuel cut based idle to be used with ALS it would be much better, as in other ECUs, like cooldown or rotational idle , by cutting fuel event randomly on cylinders to hold the desired idle, as this will remarkably lower the EGT and CLT in very short period, I wish if you can consider this in future versions
Thanks,

Re: Bugs and Feature reqests
I think it has been overlooked.....altmanis wrote:Hi,
is it possible to get a Boost DC ref table and a Boost target table for each gear?
Because the precentage solution is not really the best one.
Last weekend, I had a car where the turbo is surging at higher gears.
It would be handy to just change the DC in lower revs at higher gears.
With the percentage solution, the boost pressure gets less over the whole rpm and I dont want less power.![]()
Or maybe you have a ohter solution for me?

Re: Bugs and Feature reqests
Actually it is not possible due to the lack of enough memory for new tables, especially those are big.
altmanis wrote:I think it has been overlooked.....altmanis wrote:Hi,
is it possible to get a Boost DC ref table and a Boost target table for each gear?
Because the precentage solution is not really the best one.
Last weekend, I had a car where the turbo is surging at higher gears.
It would be handy to just change the DC in lower revs at higher gears.
With the percentage solution, the boost pressure gets less over the whole rpm and I dont want less power.![]()
Or maybe you have a ohter solution for me?
Re: Bugs and Feature reqests
The upgrade firmware bug is already fixed in 1.136
There is also fuel cut based idle
There is also fuel cut based idle
Re: Bugs and Feature reqests
Make sure that you select HALL sensor for CAM#2
Mobilelpg wrote:Hi,
Thanks for the reply.
That's great, it will be nice to use the Keelog data for autotune even if it just to get a broader picture of any areas in the map that are slightly off that don't get driven in much.
Yes I have 'enable pullup' selected under the cam2 options.
I have the cam 2 pin earthed to the body of the car (about 2 inches from one of the vehicles standard earth points, I have moved it but still the same)
As I run the car on gas and petrol I have separate maps for each fuel, the LPG map on table 2 runs with increased ignition timing and a leaner map so at the moment every time the table switches back to petrol map but I am running LPG, the AFR goes really rich to below 10.0 and the ignition timing drops to the petrol setting.
I have the table switch set through a relay where the LPG live solenoid activates a relay which then earths the CAM#2 pin.
I hope this helps to find a solution to the table switching issue.
Thanks,
Edward.
Jadzwin wrote:We are aware of it. Lambda and AFR target will be added soon.
What ground do you use for CAM#2 ? Did you enable pullup ?
Mobilelpg wrote:At the moment you cannot use data imported via the KeeLog import for autotune because the KeeLog does not read Lambda target.
Load a log from the KeeLog and select autotune and it just suggest 0 for all of the VE table as it thinks the lambda target is 0.
Also I am having issues with my table switch, I have the table switch set so that when the CAM#2 pin is earthed it switches to table 2, my log (and can be felt when driving) is rapidly flicking between table 1 and 2 but it doesn't always do it, sometimes works fine and other times it flicks between tables rapidly.
I have uploaded a small log file where if you look at 'Table Set' you can see it switching for no reason even though the relay is closed circuit and providing an earth path for CAM#2 pin.
I have changed the wiring, used a different earth location but nothing changes, if anyone cares to suggest why I would love to hear as I have ran out of ideas.
Edward.
Re: Bugs and Feature reqests
Thanks.
I will give it a try as soon as I get chance ad update here.
I will give it a try as soon as I get chance ad update here.