Moderator: Freon
Evo4Mad wrote:Wanted:
Testers for Wideband cables:
WideBand - Innovate LC-1
WideBand - Innovate LM-1
WideBand - AEM UEGO
WideBand - Zeitronix Zt-2
Evo4Mad wrote:Wanted:
Testers for Wideband cables:
WideBand - Innovate LC-1
WideBand - Innovate LM-1
WideBand - AEM UEGO
WideBand - Zeitronix Zt-2
c-spec wrote:i have th zeitronix setup also, but my are connect to the usb port instead of rs232 serial. i would like to see if it works aswell, thanks
Evo4Mad wrote:You would need to try the virtual com port driver in that case, because I have programmed it to use the serial port COM1. I will try and get hold of some widebands here locally, so that I can try it out myself.c-spec wrote:i have th zeitronix setup also, but my are connect to the usb port instead of rs232 serial. i would like to see if it works aswell, thanks
ECUBlues wrote:I have seen the P0141 and P0136---- both releated to the rear O2 sensor in the USDM Evolutions---- and it seems that there is no check for that code in EVOScan. If I also clear the codes---- it is still there (using a scan tool to pull the code). Support for the codes and datalogging of that sensor would be a nice addition. Other than that..... everything works very well. One other "nicety" would be a "direct" correlation to the fuel and timing maps for load. For example it would help tremendously if you could see the actual load that is referred to in the map. Also if it was possible, knowing where the ECU is pulling its figures from, i.e. when the datalogger states "15-degrees timing" and my maps are 17 on the high octane and 6 on the low octane---- it would be interesting to see how it does it, especially timing on the EVO IX as it has three timing maps.
ECUBlues wrote:I have seen the P0141 and P0136---- both releated to the rear O2 sensor in the USDM Evolutions---- and it seems that there is no check for that code in EVOScan. If I also clear the codes---- it is still there (using a scan tool to pull the code). Support for the codes and datalogging of that sensor would be a nice addition. Other than that..... everything works very well. One other "nicety" would be a "direct" correlation to the fuel and timing maps for load. For example it would help tremendously if you could see the actual load that is referred to in the map. Also if it was possible, knowing where the ECU is pulling its figures from, i.e. when the datalogger states "15-degrees timing" and my maps are 17 on the high octane and 6 on the low octane---- it would be interesting to see how it does it, especially timing on the EVO IX as it has three timing maps.
Return to Data Logging Software
Users browsing this forum: No registered users and 34 guests