Using Scanalyzer Protuner
08-02-2011, 11:16 PM
#53
Registered
Thread Starter
Starting it on an internet enabled computer (or VM) will allow the program to update itself.
The crazy thing is that is the only software I feel safe tuning my car with, I wish it did more...
08-04-2011, 10:17 PM
#54
Pt
I use VMware player as a way to run a Windows XP VM, it works rather good this way, I am using a USB/OBD2 dongle, and connecting it to the VM..
I never knew this to be a problem, but there is a way to turn the 100 limit off or on in the flash, I have probably flashed mine 15 to 20 times tops
Starting it on an internet enabled computer (or VM) will allow the program to update itself.
The crazy thing is that is the only software I feel safe tuning my car with, I wish it did more...
I never knew this to be a problem, but there is a way to turn the 100 limit off or on in the flash, I have probably flashed mine 15 to 20 times tops
Starting it on an internet enabled computer (or VM) will allow the program to update itself.
The crazy thing is that is the only software I feel safe tuning my car with, I wish it did more...
08-07-2011, 04:48 PM
#59
Pro Tune
As a note -- there was a tread in a forum (hymee place) Called "a thread to share discovered maps." which No one seems to use -- the Tread or the Forum.
As most of the 623 members signed/logged on for the first and ONLY time -- some as far back as 08', and Most Never Logged on again.
So, as there are a few of us out here still using the pro Tuner, it maybe of some help if these owners of Pro Tuner went back to "Hymee place" and posted there, instead of dragging it thro the Mud on this Forum, just a Ideal
As most of the 623 members signed/logged on for the first and ONLY time -- some as far back as 08', and Most Never Logged on again.
So, as there are a few of us out here still using the pro Tuner, it maybe of some help if these owners of Pro Tuner went back to "Hymee place" and posted there, instead of dragging it thro the Mud on this Forum, just a Ideal
08-07-2011, 05:01 PM
#61
Pt
But I'm just thinking it'll keep it sweeter ?? keep the bad blood out of it.
More direct?? , keeping some of side shows away from the Tuning, or find out what maps do, or are called.
MY 2 C worth.
09-23-2011, 12:32 AM
#62
Hmmmmmm.........
Join Date: Mar 2005
Location: Melbourne, Australia
Posts: 3,564
Likes: 0
Received 6 Likes
on
4 Posts
I want to resurrect this idea that was started in the Hymee forum of sharing "maps". The ProTuner, from what I understood from conversations with Hymee, has a base ROM (.ptc file) that is specific to an ECU type (Not VIN). The ROM is just a bunch of tables and values. What those tables and values are is stored in a CalSpec (.pcs) file, ie at location X is a table that is 16 x 8 cels, etc etc. Each ECU will have a different CalSpec, so someone with an N3J6 ECU may have a table number 38 that is 16 x 8 but that doesn't mean someone with an N3YM will have the same Table at the same location. Prime example in the attached, have a look at the location of the APV Opening parameter. Table 34 on one and 38 on another.
All ProTuner is doing is giving you the ability to modify these table values (you cant change the table dimensions) and write them to the ECU. Each different ECU type has differing numbers of tables and table configurations so are not compatible. What was intended
So what was proposed, the sharing of Maps, is about identifying what ECU you have, what table you have found to do what "job" and the configuration of that table.
Are people interested in sharing new tables they have found? I actually thought someone mentioned you can get access to a document from Mazda that details what each tables is.
All ProTuner is doing is giving you the ability to modify these table values (you cant change the table dimensions) and write them to the ECU. Each different ECU type has differing numbers of tables and table configurations so are not compatible. What was intended
So what was proposed, the sharing of Maps, is about identifying what ECU you have, what table you have found to do what "job" and the configuration of that table.
Are people interested in sharing new tables they have found? I actually thought someone mentioned you can get access to a document from Mazda that details what each tables is.
09-23-2011, 02:38 AM
#63
I don't have ProTuner, but I have been working on disassembling a rom off and on. Right now I'm working through all the DTC subroutines and trying to identify the variables, so I don't have much exciting yet...
For example, that table is one of two tables which are used for the P0138 DTC.
I'll post if I do find anything good.
For example, that table is one of two tables which are used for the P0138 DTC.
I'll post if I do find anything good.
09-23-2011, 03:05 AM
#64
P t
I want to resurrect this idea that was started in the Hymee forum of sharing "maps". The ProTuner, from what I understood from conversations with Hymee, has a base ROM (.ptc file) that is specific to an ECU type (Not VIN). The ROM is just a bunch of tables and values. What those tables and values are is stored in a CalSpec (.pcs) file, ie at location X is a table that is 16 x 8 cels, etc etc. Each ECU will have a different CalSpec, so someone with an N3J6 ECU may have a table number 38 that is 16 x 8 but that doesn't mean someone with an N3YM will have the same Table at the same location. Prime example in the attached, have a look at the location of the APV Opening parameter. Table 34 on one and 38 on another.
All ProTuner is doing is giving you the ability to modify these table values (you cant change the table dimensions) and write them to the ECU. Each different ECU type has differing numbers of tables and table configurations so are not compatible. What was intended
So what was proposed, the sharing of Maps, is about identifying what ECU you have, what table you have found to do what "job" and the configuration of that table.
Are people interested in sharing new tables they have found? I actually thought someone mentioned you can get access to a document from Mazda that details what each tables is.
All ProTuner is doing is giving you the ability to modify these table values (you cant change the table dimensions) and write them to the ECU. Each different ECU type has differing numbers of tables and table configurations so are not compatible. What was intended
So what was proposed, the sharing of Maps, is about identifying what ECU you have, what table you have found to do what "job" and the configuration of that table.
Are people interested in sharing new tables they have found? I actually thought someone mentioned you can get access to a document from Mazda that details what each tables is.
---"document from Mazda that details what each tables is"---
Please, Please Post this so called document, someone , Please
09-23-2011, 04:09 AM
#65
here are a few I don't know if they are right. I haven't bothered modifing them.
N3ZK
2d maps
map 10 6 x 0 [Byte] leading base idle timing?
map 11 9 x 0 [Byte] leading timing coolant comp?
map 12 6 x 0 [Byte] trailing base idle timing?
map 13 9 x 0 [Byte] trailing coolant comp?
map 33 12 x 0 [Integer] cold fast idle? (usless map lol)
maps 34 - 37 7x0 idle maps?
map 263 5 x 0 [Byte] base knock retard?
3D maps
map 6 8 x 7 [Byte] leading timing idle correction A
map 8 8 x 7 [Byte] trailing idle correction A
N3ZK
2d maps
map 10 6 x 0 [Byte] leading base idle timing?
map 11 9 x 0 [Byte] leading timing coolant comp?
map 12 6 x 0 [Byte] trailing base idle timing?
map 13 9 x 0 [Byte] trailing coolant comp?
map 33 12 x 0 [Integer] cold fast idle? (usless map lol)
maps 34 - 37 7x0 idle maps?
map 263 5 x 0 [Byte] base knock retard?
3D maps
map 6 8 x 7 [Byte] leading timing idle correction A
map 8 8 x 7 [Byte] trailing idle correction A
09-23-2011, 04:12 AM
#66
I don't have ProTuner, but I have been working on disassembling a rom off and on. Right now I'm working through all the DTC subroutines and trying to identify the variables, so I don't have much exciting yet...
For example, that table is one of two tables which are used for the P0138 DTC.
I'll post if I do find anything good.
For example, that table is one of two tables which are used for the P0138 DTC.
I'll post if I do find anything good.
what do I do with it? and where is its partner?
09-23-2011, 02:23 PM
#67
Cheers
here are a few I don't know if they are right. I haven't bothered modifing them.
N3ZK
2d maps
map 10 6 x 0 [Byte] leading base idle timing?
map 11 9 x 0 [Byte] leading timing coolant comp?
map 12 6 x 0 [Byte] trailing base idle timing?
map 13 9 x 0 [Byte] trailing coolant comp?
map 33 12 x 0 [Integer] cold fast idle? (usless map lol)
maps 34 - 37 7x0 idle maps?
map 263 5 x 0 [Byte] base knock retard?
3D maps
map 6 8 x 7 [Byte] leading timing idle correction A
map 8 8 x 7 [Byte] trailing idle correction A
N3ZK
2d maps
map 10 6 x 0 [Byte] leading base idle timing?
map 11 9 x 0 [Byte] leading timing coolant comp?
map 12 6 x 0 [Byte] trailing base idle timing?
map 13 9 x 0 [Byte] trailing coolant comp?
map 33 12 x 0 [Integer] cold fast idle? (usless map lol)
maps 34 - 37 7x0 idle maps?
map 263 5 x 0 [Byte] base knock retard?
3D maps
map 6 8 x 7 [Byte] leading timing idle correction A
map 8 8 x 7 [Byte] trailing idle correction A
Thanks
09-23-2011, 02:46 PM
#68
Here are a few I've found :
3D
31 12x16 Closed loop A
32 12x16 Closed loop B
2D
120 19x0 Closed loop Exit Throttle
277 8x0 Calc. Load IAT compensation
278 8x0 Calc. load Baro. compensation
Although all these extra maps are interesting and i have done some experimenting with them . I have yet to alter any of them to the point where i thought that knowing where they are was important to the tune.
With perhaps the exception of the closed loop exit throttle map and the idle maps .
3D
31 12x16 Closed loop A
32 12x16 Closed loop B
2D
120 19x0 Closed loop Exit Throttle
277 8x0 Calc. Load IAT compensation
278 8x0 Calc. load Baro. compensation
Although all these extra maps are interesting and i have done some experimenting with them . I have yet to alter any of them to the point where i thought that knowing where they are was important to the tune.
With perhaps the exception of the closed loop exit throttle map and the idle maps .
09-24-2011, 03:28 AM
#69
Here are a few I've found :
3D
31 12x16 Closed loop A
32 12x16 Closed loop B
2D
120 19x0 Closed loop Exit Throttle
277 8x0 Calc. Load IAT compensation
278 8x0 Calc. load Baro. compensation
Although all these extra maps are interesting and i have done some experimenting with them . I have yet to alter any of them to the point where i thought that knowing where they are was important to the tune.
With perhaps the exception of the closed loop exit throttle map and the idle maps .
3D
31 12x16 Closed loop A
32 12x16 Closed loop B
2D
120 19x0 Closed loop Exit Throttle
277 8x0 Calc. Load IAT compensation
278 8x0 Calc. load Baro. compensation
Although all these extra maps are interesting and i have done some experimenting with them . I have yet to alter any of them to the point where i thought that knowing where they are was important to the tune.
With perhaps the exception of the closed loop exit throttle map and the idle maps .
for maps 277 and 278 could you post the values? all of my maps seem to be at the same location as yours, but these seem a long way from the IAT calibration compared to most of the related maps.
Last edited by rotarenvy; 09-24-2011 at 03:32 AM.
09-25-2011, 04:20 AM
#73
+1
09-25-2011, 02:40 PM
#74
This table plays a role in injector staging, but I don't understand it completely yet.
1000 1500 2000 2500 3000 3500 4000 4500 5000 5500 6000 6500 7000 7500 8000 8500 9000
350 350 350 350 350 300 250 210 200 195 190 185 180 175 170 170 170
350 350 350 350 350 300 250 210 200 195 190 185 180 175 170 170 170
09-25-2011, 02:56 PM
#75
This is seems to be a load table for SSV and APV control, but not VDI which seems to be strictly RPM-based. The same subroutine also looks for a throttle position > 60, but I doubt you guys have the ability to edit that value.