Weird load calc. with log analyzer
What are all of your settings?
Typically bad output comes from bad input..
Make sure your injector scaling is set correctly, same with Injector Voltage Latency.. Frequently people put in the wrong value, or forget to set it.. The result will end up being unexpected numbers.
Sometimes missing data in the logs can cause it too.
Typically bad output comes from bad input..
Make sure your injector scaling is set correctly, same with Injector Voltage Latency.. Frequently people put in the wrong value, or forget to set it.. The result will end up being unexpected numbers.
Sometimes missing data in the logs can cause it too.
Originally Posted by MalibuJack
What are all of your settings?
Typically bad output comes from bad input..
Make sure your injector scaling is set correctly, same with Injector Voltage Latency.. Frequently people put in the wrong value, or forget to set it.. The result will end up being unexpected numbers.
Sometimes missing data in the logs can cause it too.
Typically bad output comes from bad input..
Make sure your injector scaling is set correctly, same with Injector Voltage Latency.. Frequently people put in the wrong value, or forget to set it.. The result will end up being unexpected numbers.
Sometimes missing data in the logs can cause it too.
Last edited by Drifto; Oct 2, 2006 at 09:55 PM.
BTW I won't be actively supporting the log analyzer any longer since I've released the first betas of my own logging tool. Just too time consuming to support the program when all the functionality is already built into the new Logger anyway.
I don't think the problem is the load calculation with the analyzer..
There are only two configurable settings, Injector Scale and 14v latency..
Therefore something is either logging improperly, or not logging at all, or your experiencing the "wideband bug" where Evoscan occasionally logs the incorrect amount of data items and therefore has too few or too many commas and the wrong value is in one of the columns because of it.
Again, There isn't much I can do, the software is no longer being developed or supported, and if its a problem with a log in Evoscan itself, well, the new version is due to be released the end of this week and he did say he will include load and other configurable items in the logger itself.
Or you can use my MitsuLogger beta 3, I thas some minor glitches, however it does log all of the items you need and load calculations are built in already.
There are only two configurable settings, Injector Scale and 14v latency..
Therefore something is either logging improperly, or not logging at all, or your experiencing the "wideband bug" where Evoscan occasionally logs the incorrect amount of data items and therefore has too few or too many commas and the wrong value is in one of the columns because of it.
Again, There isn't much I can do, the software is no longer being developed or supported, and if its a problem with a log in Evoscan itself, well, the new version is due to be released the end of this week and he did say he will include load and other configurable items in the logger itself.
Or you can use my MitsuLogger beta 3, I thas some minor glitches, however it does log all of the items you need and load calculations are built in already.



