Speed Density 2.0 (3D VE Tables, Baro)
Newbie
Joined: Dec 2012
Posts: 18
Likes: 0
From: Portland, OR
Well, they should be 1:1, but it's actually used for as a scaler to figure out what kind of load is comparable to a particular voltage for your sensor input. This means if you put the peak at 500 when it should be 370, you're telling the ECU that at 3.5 bar, it should be a load well below the 350 peak.
If I've done my calcs correctly, I think if you've changed the settings like you have, then you would read a load around 148 at 2 bar. What do you see for load at idle?
10isace, I don't have the VE Calibration window you're showing. You may have a later version?
If I've done my calcs correctly, I think if you've changed the settings like you have, then you would read a load around 148 at 2 bar. What do you see for load at idle?
10isace, I don't have the VE Calibration window you're showing. You may have a later version?
Last edited by Architechnik; Feb 15, 2013 at 03:25 PM.
Well, they should be 1:1, but it's actually used for as a scaler to figure out what kind of load is comparable to a particular voltage for your sensor input. This means if you put the peak at 500 when it should be 370, you're telling the ECU that at 3.5 bar, it should be a load well below the 350 peak.
If I've done my calcs correctly, I think if you've changed the settings like you have, then you would read a load around 148 at 2 bar. What do you see for load at idle?
10isace, I don't have the VE Calibration window you're showing. You may have a later version?
If I've done my calcs correctly, I think if you've changed the settings like you have, then you would read a load around 148 at 2 bar. What do you see for load at idle?
10isace, I don't have the VE Calibration window you're showing. You may have a later version?
I don't see idle on this ROM. It I have to modulate the throttle to keep it from dying. It's incredibly lean around 21 AFR.
BTW, I tried your Excel sheet and it looks good. That's fairly close to what I came up with after logging VE for a couple of days on MAF.
The Calibration table is carried over from the 2D SD ROM.
Newbie
Joined: Dec 2012
Posts: 18
Likes: 0
From: Portland, OR
I'm glad the spreadsheet came in handy. I wasn't talking about those two tables being 1:1, though. Like I said, I don't have the VE and Calibration Table.
The Map to kPa and kPa to Load should both be 1:1 after setting the correct sensor in the Map to kPa settings (ctrl+m). I'm guessing the calibration table is really just the output of the calcs done by setting the other tables.
The Map to kPa and kPa to Load should both be 1:1 after setting the correct sensor in the Map to kPa settings (ctrl+m). I'm guessing the calibration table is really just the output of the calcs done by setting the other tables.
I also noticed the 9653 SD 2.0 doesn't carry over the old SD ROM. Is that right? The xml for 2.0 says to inherit the TephraMod-96530706-v7.
The 914172715 ROM inherits the TephraMod-914171715-v7 ROM and that ROM inherits the TephraMOD-94170715-v7.
The 914172715 ROM inherits the TephraMod-914171715-v7 ROM and that ROM inherits the TephraMOD-94170715-v7.
I'm glad the spreadsheet came in handy. I wasn't talking about those two tables being 1:1, though. Like I said, I don't have the VE and Calibration Table.
The Map to kPa and kPa to Load should both be 1:1 after setting the correct sensor in the Map to kPa settings (ctrl+m). I'm guessing the calibration table is really just the output of the calcs done by setting the other tables.
The Map to kPa and kPa to Load should both be 1:1 after setting the correct sensor in the Map to kPa settings (ctrl+m). I'm guessing the calibration table is really just the output of the calcs done by setting the other tables.
Are you running the 9417 SD 2.0 ROM? Are you not inheriting the 2D 9417 ROM? Care to post up your XMLs for both?
Newbie
Joined: Dec 2012
Posts: 18
Likes: 0
From: Portland, OR
I'm actually running the 9653 on a 1g DSM. The 9417 doesn't have the right trigger sequence for the crank sensor, while the 9653 has the same trigger sequence as the 1ga CAS combined unit. Other than that, they should be nearly identical.
If you're having trouble getting it to recognize the right XML, try copying just the files you want to use to a different directory and then change the location settings in ECUFlash. That should force it to use the correct definition, assuming there is one specific to that ROM.
If you're having trouble getting it to recognize the right XML, try copying just the files you want to use to a different directory and then change the location settings in ECUFlash. That should force it to use the correct definition, assuming there is one specific to that ROM.
Newbie
Joined: Dec 2012
Posts: 18
Likes: 0
From: Portland, OR
The first one posted was correct: http://i198.photobucket.com/albums/a...ps927d0117.png
Evolving Member
Joined: Nov 2008
Posts: 424
Likes: 3
From: Russia, Moscow
OH! I feel much better now, as I'm not the only one with that problem!!!
I'm definately going to try 9417 SD 2.0 rom. So I have several questions, hope somebody can answer me:
- If I want to use Fuel Temp pin as MAT input, I put 0x03 in "SD Convert IAT to MAT (0x03 -> 0x0E)" ? Should I make any other changes?
- Do I need to make any changes in "MAP sensor" section of the rom? I have EDM Evo 8 that doesnt have MAP sensor in stock...
I'm definately going to try 9417 SD 2.0 rom. So I have several questions, hope somebody can answer me:
- If I want to use Fuel Temp pin as MAT input, I put 0x03 in "SD Convert IAT to MAT (0x03 -> 0x0E)" ? Should I make any other changes?
- Do I need to make any changes in "MAP sensor" section of the rom? I have EDM Evo 8 that doesnt have MAP sensor in stock...
Anyone?
Last edited by Biggy VIII; Feb 16, 2013 at 05:02 AM.
I've just been through the 94170715 and 94172715 XML files you sent me and they are identical to mine. This points to either; a bug in the binary TephraMOD-94172715.bin that we both downloaded and used, or a problem with our understanding of how to set it up.
I'm not making any progress with either of the 3D ROM's (96534706 or 94172715) at this point and without further input from the community I don't have the time to use trial and error to figure out what I'm doing wrong. Both 96534706 and 94172715 ROMS go lean on tip in on my 2005 USDM VIII and don't seem to respond to tuning 3D VE.
Can anyone suggest how to troubleshoot this step by step please?
OH! I feel much better now, as I'm not the only one with that problem!!!
I'm definately going to try 9417 SD 2.0 rom. So I have several questions, hope somebody can answer me:
- If I want to use Fuel Temp pin as MAT input, I put 0x03 in "SD Convert IAT to MAT (0x03 -> 0x0E)" ? Should I make any other changes?
- Do I need to make any changes in "MAP sensor" section of the rom? I have EDM Evo 8 that doesnt have MAP sensor in stock...
I'm definately going to try 9417 SD 2.0 rom. So I have several questions, hope somebody can answer me:
- If I want to use Fuel Temp pin as MAT input, I put 0x03 in "SD Convert IAT to MAT (0x03 -> 0x0E)" ? Should I make any other changes?
- Do I need to make any changes in "MAP sensor" section of the rom? I have EDM Evo 8 that doesnt have MAP sensor in stock...
Using your scaling values seemed to help with one issue, but this patch still is giving me lots of load problems. It's reporting way too low of a load at all times, even with high VE values. As a test I put 100% VE in the table at anything above idle, and I hit 14 psi and load still only reported a max of 115, where of course since kPa to Load is set 1:1, and so is Map Sensor kPa, so I should be seeing closer to 190 load at that boost level (approx 190 kPa boost).
I'm also having to use WAY too low of an injector scaling value to get the car to about where it should be fuel trims wise at light load. Typical Actual engine VE will typically be below 60% at idle, and there's no way I'd be able to get the car to run down there. It runs perfect with the older 31706 2D SD stuff.
This is why I usually stick to standalones.. It's fun playing with patches though but I really don't like skewing/bandaiding data to get the car to run properly. I should be able to input an accurate injector scaling value, accurate MAP sensor data, and realistic VE values and have the load match actual load (kPa) and have actual AFR match target AFR.
Beau
I'm also having to use WAY too low of an injector scaling value to get the car to about where it should be fuel trims wise at light load. Typical Actual engine VE will typically be below 60% at idle, and there's no way I'd be able to get the car to run down there. It runs perfect with the older 31706 2D SD stuff.
This is why I usually stick to standalones.. It's fun playing with patches though but I really don't like skewing/bandaiding data to get the car to run properly. I should be able to input an accurate injector scaling value, accurate MAP sensor data, and realistic VE values and have the load match actual load (kPa) and have actual AFR match target AFR.
Beau
JAMIE - Can you share the base binaries you are using for 96534706 and 94172715 so I can compare (filediff) them with the ones we are downloading from post #1?
