There are some detailed documentation I am looking for which I did not find.
For example, I am looking for expected engine behavior on the overrun fuel cutoff - is there some description on this? Is the RPM values changeable in the software? How does the map work? How does the overrun cuttoff work beyond the rpms in the table?
What does selecting gear ratios do? How does this affect the tune?
Why is the overrun fuel cutoff option not available for the ep calibrations?
How does the "disable overrun cuttoff delay" work - what is the expected behavior? What is the default delay? Does this work alongside the overrun table in the advance tab? Does this have higher priority?
Can the knock threshold map be given & defined by the user? Is knock dependent on temperature? If so, can temperature be used to control ignition?
Can the idle control also be given to the user? I see the slider - what does it actually do? What does each point on the slider correlate to?
When will all sensors be added to the display tab under settings as well as the display window? Can you enable a custom "sensor" or function so that a user can define his own "sensor" using arithmetic with sensor data to obtain a realtime postprocessed data? Can we disable some sensors which we do not want to see in the sensors window?
I would like to be able to use lambda overlay to automatically apply changes to the map files. What are the concerns with enabling the user to do this? Can you give the user the ability to control the algorythm for the lambda overlay or allow knobs for the user to play with?
I have asked some of these questions before and have not seen any progress. Can someone help?
fvang
Looking for documentation & questions
I understand what you're getting at.
We'll try to expand the help file to include a deeper explanation of some of the items you've bought up, but in many ways we have found it better to describe the effects of a change rather than the underlying implementation.
For example, the idle control slider changes the feedback lookup on the proportional part of the PID algorithm to match idle valve duty with the delta idle rpm. We?ve found it to be much better to explain the effect ? move the slider to the right if the rpm dips when you release the throttle, move the slider to the left if the rpm hangs above idle speed.
In many other cases what you're seeing is a simplification of what the ECU is doing, and it would be overly complex to explain the exact behavour. Example, the overrun cutoff delay varies by rpm, speed, gear, water and air temperature, throttle release speed and probably some other factors too. Another example, the knock threshold is made from about 20 maps, so making it editable would be overly complex for the user.
Other answers:
- The EP3 code is basically full. It is very difficult to implement any changes to that code.
- Display window will change in the near future.
Hope this goes some of the way to answering your questions.
We'll try to expand the help file to include a deeper explanation of some of the items you've bought up, but in many ways we have found it better to describe the effects of a change rather than the underlying implementation.
For example, the idle control slider changes the feedback lookup on the proportional part of the PID algorithm to match idle valve duty with the delta idle rpm. We?ve found it to be much better to explain the effect ? move the slider to the right if the rpm dips when you release the throttle, move the slider to the left if the rpm hangs above idle speed.
In many other cases what you're seeing is a simplification of what the ECU is doing, and it would be overly complex to explain the exact behavour. Example, the overrun cutoff delay varies by rpm, speed, gear, water and air temperature, throttle release speed and probably some other factors too. Another example, the knock threshold is made from about 20 maps, so making it editable would be overly complex for the user.
Other answers:
- The EP3 code is basically full. It is very difficult to implement any changes to that code.
- Display window will change in the near future.
Hope this goes some of the way to answering your questions.
Hondata
Thanks for your answering my questions.
Any addition of more detailed documentation(however complex) is welcomed. Off course, there may be questions, but this will allow the users to have a more better understanding in what's happening behind the scenes. I would agree that user friendliness would be ideal.
Please keep this in mind for future releases.
Thank you,
fvang
Any addition of more detailed documentation(however complex) is welcomed. Off course, there may be questions, but this will allow the users to have a more better understanding in what's happening behind the scenes. I would agree that user friendliness would be ideal.
Please keep this in mind for future releases.
Thank you,
fvang