Nistune Forums

My problem doesnt seem to be affecting the consult or logging functions. Other than the actual data changing in the bin I dont notice any problems.

Matt, I've been playing around with the rev7 bin and doing some dyno tuning. I noticed today that there are two areas in the bin that have changed from the basecode that I programmed on the nvram chip. The first is 3F26+3F27. They are normally 01 96 but in the current read I get 13 E0. The second se...

Yes, hot glue it. I think matt instructs everyone to hotglue it in the install manual.

Try doing a download through the romulator and then compare teh downloaded bin to a known clean bin with the same base code. Post it here if you like and I can check it against my 88ss_nt.bin file with Hexworkshop. Other than that maybe theres a hardware issue or something?

I've had some similar connection issues pop up at times but they've always been solved by shutting off the car, letting the ecu shutdown completely, and then turning the car/ecu back on. I'm guessing by all the steps you've tried that you have done this at some point already. I think the next step w...

A friend of mine is working on chipping an 84. So far he has pulled a little information off of each 24 pin chip. The plan is to follow the 87 ecu instructions and modify the ecu to take the 28 pin chip. My question is what bin file would we need to use. It doesnt seem like the stuff he's got off th...

Ram trace failed with both the serial consult connector and blazt cable when it worked. It says something about a checksum error and disconnects. The timing issue may well be an offset. It typically reads about 50 btdc at idle in both Nistune and Nissan Datascan. The FSM reports a stock timing value...

Ok, I guess you didnt fix the Blazt cable issue? I tried it again after having some success and I couldnt get it to work again. It came up with a timeout error when trying to connect. Let me know if you want the log. Anyway, I have another home built serial type consult adapter that I wired up and i...

I see you fixed the Blazt consult problem. It seems to be working well with the 450sx. I noticed the timing value is incorrect but its also incorrect in nissan datascan. When I went to do a ram trace to find the correct timing value address I got a checksum error and got disconnected. I'll probably ...

Any news on this? I'm probably going to start playing around with the the 450sx again shortly.

The mV table of the vqmap doesnt look right. It should be multiples of .08v right? Seems like its something else.

Well I guess what i'm asking is whats the resolution at the a/d converter. If its only .08v then there really isnt any way to do interpolation on the vqmap.

You're basing that off the vqmap right? The vqmap could use interpolation just like the fuel or ignition maps to provide for better resolution.

What's the resolution at which that the ecu reads the afm input voltage? .008v?

So the sr20s require a special bored to do anything?

Let me know when something is ready. We have access to a ka24de that we can use to test and we are also interested in getting into tuning the sr20s. I'll get the boss to fork over some money for a board or two.