SManager V1.3.0
Posted: Thu Oct 25, 2007 12:55 pm
SManager V1.3.0 is available for download. This is a release version but there are some changes which might generate some support calls, and as we'll be closed next week (for SEMA), then for the moment it is not an automatic download.
Please read fully these instructions before downloading the new version. If you're not comfortable with the changes or don't understand them, wait until the general release in about two weeks time.
Specific changes are:
? Added fuel overrun cutoff rpm / tps table.
? Added moving idle speed vs coolant temperature.
? Added calculate overall fuel trim based on fuel pressure and displacement changes.
? Added Wideband Lambda Parameters.
? Added overheating protection.
? Added lean protection.
? SManager now prompts to save un-saved datalogs when closing.
(see the help file for more information)
The main change is that the wideband voltage to lambda conversion has been moved from the application (SManager) to the ECU (calibration). Thus the wideband options have moved from the 'Settings' window to the 'Parameters' window. This means that the ECU can now work out lambda, which has enabled us to use lean protection. These can be found under a new 'Protection' tab in the 'Parameters' window.
There are some issues which you need to be aware of with the change in lambda conversion:
- The lambda conversion table is smaller, but the vast majority of users are using the AEM, PLX or innovative widebands, which only require two points to define the conversion.
- The lambda calculation is now calculated by the ECU and stored in the datalog. The upshot is that if you change the voltage/lambda conversion, your datalogged lambda will not change. The second thing to be aware of is that datalogs made with a previous version do not contain the lambda, and therefore must be converted when the datalog is loaded. If you won't want to be prompted each time you load a datalog, then re-save it with V1.3.0
- From experience with the K-Series lean protection settings, don't set the lambda too high and the duration too short. Otherwise you'll get lean cuts every 10 seconds on a less than perfectly tuned engine. The aim is to use settings which will protect the engine, rather than enforce an ideal a/f ratio. eg setting the maximum lambda to 12.5:1 with a trigger time of 20 ms under boost will trigger far too often. A setting of 13.5:1 with 250 ms trigger will work. Remember, the aim is to prevent engine damage rather than enforce good a/f ratios, and at low boost any engine will handle 13.5:1 for considerable time without damage.
Read and understand the above above paragraph again, then you can download SManager here.
Please read fully these instructions before downloading the new version. If you're not comfortable with the changes or don't understand them, wait until the general release in about two weeks time.
Specific changes are:
? Added fuel overrun cutoff rpm / tps table.
? Added moving idle speed vs coolant temperature.
? Added calculate overall fuel trim based on fuel pressure and displacement changes.
? Added Wideband Lambda Parameters.
? Added overheating protection.
? Added lean protection.
? SManager now prompts to save un-saved datalogs when closing.
(see the help file for more information)
The main change is that the wideband voltage to lambda conversion has been moved from the application (SManager) to the ECU (calibration). Thus the wideband options have moved from the 'Settings' window to the 'Parameters' window. This means that the ECU can now work out lambda, which has enabled us to use lean protection. These can be found under a new 'Protection' tab in the 'Parameters' window.
There are some issues which you need to be aware of with the change in lambda conversion:
- The lambda conversion table is smaller, but the vast majority of users are using the AEM, PLX or innovative widebands, which only require two points to define the conversion.
- The lambda calculation is now calculated by the ECU and stored in the datalog. The upshot is that if you change the voltage/lambda conversion, your datalogged lambda will not change. The second thing to be aware of is that datalogs made with a previous version do not contain the lambda, and therefore must be converted when the datalog is loaded. If you won't want to be prompted each time you load a datalog, then re-save it with V1.3.0
- From experience with the K-Series lean protection settings, don't set the lambda too high and the duration too short. Otherwise you'll get lean cuts every 10 seconds on a less than perfectly tuned engine. The aim is to use settings which will protect the engine, rather than enforce an ideal a/f ratio. eg setting the maximum lambda to 12.5:1 with a trigger time of 20 ms under boost will trigger far too often. A setting of 13.5:1 with 250 ms trigger will work. Remember, the aim is to prevent engine damage rather than enforce good a/f ratios, and at low boost any engine will handle 13.5:1 for considerable time without damage.
Read and understand the above above paragraph again, then you can download SManager here.