


thats what sucks about 16x16 maps tho, you can only space the rpm's out so much before you lose resolution
I honestly don't mind 16x16. You don't really need THAT much resolution honestly. Just makes it more painful to retune everything.


I'm using a used OBD1 Calum R/T v1 that I bought used off the forum. It worked really well with my t25, but now I'm having trouble with the new setup lol. That U13 bin I got off the forum, I think it was somewhere in the ROM exchange section. I dunno if it would work or not, but it idled nice with the k value changed.
OBD1 Calum R/T v1 is the daughterboard chip. This chip works in USDM B13, USDM P10, JDM B13, U12, U13, W10 (if obd1), S13.... etc. etc. What I'm asking is for the ECU it self, look up the part number on the ECU. Take a picture of it and post it up.
If you use a U13 bin on a USDM ECU, your car wont run right. BIN file has two parts two it, one is tunable parameters like fuel maps, another is the actual ECU code. If you run the wrong ECU code the ECU wont read the tunable parameters right. Even between USDM ecu's there are slight code differences.
http://www.sr20-forum.com/tuning/45239-nissan-ecu-manufacture-part-nissan-part-number.html