260z project that needs some tuning help

[stew86MCSS396]

I appreciate your help, I haven't tried through the ALDL port, I'll try that today. I attached a past log if someone wants to take a look at it. This was a win zip file and it was the last log I sent to Affordable Fuel injection.

I recognized the way those log files save meaning you're probably using WinALDL as your datalogger. Nothing wrong with that if you know how to navigate around the data. Reading them as a text document presents some challenges interpreting it. Pennock Fiero site has a tool ALDLview that can somewhat present your data so it makes a little more sense. Hopefully your ALDL cable is a store bought one that can handle TPRT and not a 2 resistor home made one that'll only work with WinALDL. Couple of things that I noticed...MPH is flatlined at zero meaning do you have a functional VSS that is communicating to the ECM? Not sure what's going on with the knock sensor data with it's repeated reported pattern across the entire log.

Anyhoo gonna share couple of screen grabs 1. Your BLM datalog 2. Your BLM charted which helps in identifying where/what needs adjusting in the VE tables and 3. One of my BLM datalogs demonstrating what it can look like after tweaking your VE tables. While mine is not perfect, that's where you wanna be where the BLMs stay within a narrow band of 128 +-5.
BLM all over the place.jpgBLM charted.jpgBLM example after adjustments.jpg

[Larryz260]

There is no speed sensor, it didn't come in the kit. A knock didn't come on the kit so I'm not sure where it is getting the info from, but it does look very strange. I was using a WinALDL datalogger, but my old laptop crashed, and my new one didn't want to load the WinALDL program. I had my computer guy try to install it and windows 10 didn't cooperate. I'm going to try to get the cobra to except an XDF code from a 16144288 hopefully tonight. I'll let you know how it goes.
I like the way your data log looks; I have a store bought ALDL cable so it should work
Thanks

[stew86MCSS396]

Wow...I sorta get it or maybe don't now. Whatever AFI does is kinda beyond me. Apparently they turn off a whole bunch of stuff that is deemed, not needed. i.e. VSS, knock sensor, CEL etc If you open your log with a simple text editor, you can count about 17 parameters that winALDL is getting some kind of feedback. If I do the same with one my past project 1227747, there's a whopping 72 items that it list. Idk if it be worthwhile to try searching for a fuel only thread...which I can't seem to recall where I last read about. Well keep pushing along and hopefully we can get through this.

[Larryz260]

Thank you very much, I have a bunch of chips, do you think someone here could get the xdf out of it if I sent them one of the chips I have?

[1project2many]

Thank you very much, I have a bunch of chips, do you think someone here could get the xdf out of it if I sent them one of the chips I have?

For someone with an eprom burner it's generally not difficult to read a copy of the binary out of an existing chip.

Just out of curiousity, have you reached out to AFI to ask for a copy of what's on the chip? They might be willing to provide a binary file of your latest calibration along with the "mask ID" or "Broadcast code" for the original file. Getting either of those would help. Getting both would be huge.

[Larryz260]

Thanks for the reply, I don't have a burner and AFI is fairly protective of their stuff, but I will reach out to them and see if that is posable.
If I can't get anything from AFI what is the next step to get this ecm to work properly?