Real-time data logging?
Nov 5, 2008, 02:42 PM
#16
Evolved Member
Thread Starter
iTrader: (2)
Join Date: Nov 2003
Location: Mtz, CA
Posts: 606
Likes: 0
Received 0 Likes
on
0 Posts
I would get it if it was stable and read knock. I heard it crashes now and again and if it did watch knock might be worth the $95 over the $25 of EvoScan....when it's released for the X...if it is, that is. Haha.
Nov 6, 2008, 01:54 AM
#23
Evolved Member
iTrader: (1)
Join Date: Jun 2008
Location: Kanagawa, Japan
Posts: 1,018
Likes: 0
Received 0 Likes
on
0 Posts
Nov 6, 2008, 10:07 AM
#24
Evolved Member
Thread Starter
iTrader: (2)
Join Date: Nov 2003
Location: Mtz, CA
Posts: 606
Likes: 0
Received 0 Likes
on
0 Posts
But still no knock detection....and I haven't heard from them regarding it. I talked to EvoScan and when it comes out for the X it will detect knock. So I'd wait...plus it's cheaper.
Nov 6, 2008, 03:21 PM
#25
Evolved Member
iTrader: (1)
Join Date: Jun 2008
Location: Kanagawa, Japan
Posts: 1,018
Likes: 0
Received 0 Likes
on
0 Posts
razorlab,
I just started to test out PCMSCAN. I noticed that it logs absolute load %, which seems to be similar to the load % the ECU uses.
Example, at 3800 RPM 3rd gear it says I'm hitting 230 load and my IGN timing is 13 degrees. I looked at my IGN map and it seems to be right on. I've done multiple runs with different maps and I seem to be getting similar results when I cross reference it to the ECU maps. When the IGN timing isn't correct, it usually reflects the low octane map which means it must have used knock correction. So far this program seems to be pretty good, I'll have to hook up my WB to it for further testing.
I just started to test out PCMSCAN. I noticed that it logs absolute load %, which seems to be similar to the load % the ECU uses.
Example, at 3800 RPM 3rd gear it says I'm hitting 230 load and my IGN timing is 13 degrees. I looked at my IGN map and it seems to be right on. I've done multiple runs with different maps and I seem to be getting similar results when I cross reference it to the ECU maps. When the IGN timing isn't correct, it usually reflects the low octane map which means it must have used knock correction. So far this program seems to be pretty good, I'll have to hook up my WB to it for further testing.
