I am trying to understand where the perimeter names are coming from and if they represent something such as their location in the bin. Here are a couple of examples...
{B0915} Low RPM VE Table (Single Fire)
{B0917} High RPM VE Table
{B0611} Spark ECT Correction
Need help understanding tune perimeter names
-
darkman5001
- Posts: 213
- Joined: Sat Dec 18, 2021 8:15 am
- cars: 2004 Suburban, 2001 Tahoe, 2002 Envoy, 2006 Envoy, 2003 Lincoln LS
- Location: New Jersey, USA
-
antus
- Site Admin
- Posts: 8250
- Joined: Sat Feb 28, 2009 8:34 pm
- cars: TX Gemini 2L Twincam
TX Gemini SR20 18psi
Datsun 1200 Ute
Subaru Blitzen '06 EZ30 4th gen, 3.0R Spec B - Contact:
Re: Need help understanding tune perimeter names
AFAIK Some of the first P01/P59 XDFs were created by editing tunes in efilive and then reading bins off the PCM and comparing what changed, where and by how much. The names line up with what efilive call them. It seems to be a good standard as you can use those numbers to cross reference / verify changes in efilive and other xdfs that use them.
Have you read the FAQ? For lots of information and links to significant threads see here: http://pcmhacking.net/forums/viewtopic.php?f=7&t=1396