LOGMAP
Log Maps monitor and store a pre-defined parameter into the map at sites corresponding to those of a base map. For example, a Lambda log map would log the lambda parameter, based upon the fuel map. As the load and speed approach a particular site in the fuel map, the value of lambda is logged into the lambda log map at the corresponding site. As more values of lambda are collected for that site, the site value is averaged out. As engine load and speed changes, the log map is built up to show how lambda changes across the entire load and speed map.
The weight of a site is the number of data points collected to produce the average value. Setting the weighting to a low value (such as zero) will give higher priority to new data coming in. Setting it to a higher value will reduce the priority of new data coming in. This can also be used to initiate auto mapping for selected sites as auto mapping will not start for a site until the weighting has exceeded a certain value.
| Field Name | Definition |
|---|---|
| LOGMAP | This is entered as is, and defines the values as a log map. |
| Name | Name of the log map. |
| Reserved | Leave blank. |
| Map Base | Map Name Reference β This must be provided, and indicates the base map May be left blank |
| Log Parameter | Parameter Name Reference |
| Remove Time (ms) | Integer β Time that a site must be located for before values are logged. |
| Weight Time (ms) | Integer β Time over which a linear significance value is applied to a recorded value. |
| Filter Limit (%) | Integer β Readings that deviate from the most significant recorded value exceeding this percentage will be dropped. |
| Create Mod Map | Boolean β may be 0, 1, ’true’ or ‘false’. Generates an additional map that can be used to enter a desired value for the parameter being logged at a particular map site. This map is used to perform auto mapping. |
| Site Accuracy (%) | Integer β affects the weighting given to recorded values depending upon how close to the centre of a site the current axis positions are. |
| 100% weighting (%) | Integer β affects the shape of the site accuracy filtering. |
| Filter Type | “bell” or “proportional”, defaults to “proportional” |
| Secondary Filter Parameter | (Parameter Name, blank for no secondary filtering) |
| Secondary Filter Minimum | Real β cutoff point for the secondary parameter, below which logging will not take place. |
| Secondary Filter Maximum | realβ cutoff point for the secondary parameter, above which logging will not take place. |
| Tertiary Filter Parameter | (Parameter Name, blank for no tertiary filtering) Pls note that this feature is not yet supported in GW and is not stored in v3.15 GIN files. |
| Tertiary Filter Minimum | Real β cutoff point for the tertiary parameter, below which logging will not take place. Pls note that this feature is not yet supported in GW and is not stored in v3.15 GIN files. |
| Tertiary Filter Maximum | realβ cutoff point for the tertiary parameter, above which logging will not take place. Pls note that this feature is not yet supported in GW and is not stored in v3.15 GIN files. |
| Max absolute change (+) | specifies the constraints imposed on the change value. When auto mapping is started, GW takes a copy of the base map in its original state. The base map is not changed by more than the absolute or percentage change from its original state. |
| Max % Change (+) | |
| Max absolute change (-) | |
| Max % Change (-) |
Example:
1[LOGMAP,Lambda,,Fuel,Lambda,200,400,10,true,75,25,proportional,,,,,,,10,50,10,50]Generates a Lambda log map. This has the Fuel map as a base, logging against the Lambda parameter. There is no secondary/tertiary parameter filtering in this example.