Type 2 in Z32 for R33 RB25DET pinouts - document
Moderator: Matt
Matt, I haven't made any changes to the consult routines.
I also experienced the same (consult) problem when making an ENT image of my own modified ROMs, but thought it was just me...
And since the ENT file seems to be encrypted I couldn't tell what was causing the problem
Maybe something in the software that does the ENT patching isn't quite right ?
-Eric
I also experienced the same (consult) problem when making an ENT image of my own modified ROMs, but thought it was just me...
And since the ENT file seems to be encrypted I couldn't tell what was causing the problem
Maybe something in the software that does the ENT patching isn't quite right ?
-Eric
When you are making an ENT file from inside Nistune it just copies the maps defined in the address files over the top of the ENT that you loaded previously
The current loaded BIN and the ENT must match the address file loaded using this process. If you have a BIN which causes issues, send it through and I can check it out
However when I did yours posted on this thread, I ran it directly through my patcher which searches for certain instruction sequences and then patches them over. It seemed to be successful but the patching has damaged something. I'll check that one out
The current loaded BIN and the ENT must match the address file loaded using this process. If you have a BIN which causes issues, send it through and I can check it out
However when I did yours posted on this thread, I ran it directly through my patcher which searches for certain instruction sequences and then patches them over. It seemed to be successful but the patching has damaged something. I'll check that one out
Re: Type 2 in Z32 for R33 RB25DET pinouts - document
Checking this out further tonight
FF FF EF => 10 Initialise ok
DO => F0, FF 16 => Version string ok, 30 => Terminate string
-DTA- reported
5A XX, A5 XX => Register checks okay until 5A 14 then gets FE FE (Error)
Followed by remainder version string again...
05 80 00 00 00 1F C0 00 E3 69 00 00 00 6D 9E 2D 44 54 41 2D
Looks like the version string terminate flag is not working with consult on this one
I reuse the existing consult memory addresses (0041,0042,0043) using the spare bits remaining for my own purposes in the patcher to set/clear flags
In particular set #02,cflag2reg (0042) to terminate the consult stream
Not sure here. Eric what part number are you using as a base for this code so I can compare the BIN files with/without your changes?
FF FF EF => 10 Initialise ok
DO => F0, FF 16 => Version string ok, 30 => Terminate string
-DTA- reported
5A XX, A5 XX => Register checks okay until 5A 14 then gets FE FE (Error)
Followed by remainder version string again...
05 80 00 00 00 1F C0 00 E3 69 00 00 00 6D 9E 2D 44 54 41 2D
Looks like the version string terminate flag is not working with consult on this one
I reuse the existing consult memory addresses (0041,0042,0043) using the spare bits remaining for my own purposes in the patcher to set/clear flags
In particular set #02,cflag2reg (0042) to terminate the consult stream
Not sure here. Eric what part number are you using as a base for this code so I can compare the BIN files with/without your changes?
Re: Type 2 in Z32 for R33 RB25DET pinouts - document
Have you guys swapped the injectors pins? It's not very easy, yet I feel that those should be swapped..
Does Z32 use sequential injection when at boost, or does it change to single batch like ca18det?
Does Z32 use sequential injection when at boost, or does it change to single batch like ca18det?
Re: Type 2 in Z32 for R33 RB25DET pinouts - document
Hey! Ignore my last post. I just compared RB25DET and Z32 pinouts:
http://www.allpinouts.org/index.php/199 ... _300ZX_ECU
http://www.gweeds.net/carpage2/RB25DET_ECR33_Pinout.pdf
and to me it seems that the injector pins ARE swapped already, they should be correct without any changes? If this really is the case, then Matt should update the document about these injector pins..
http://www.allpinouts.org/index.php/199 ... _300ZX_ECU
http://www.gweeds.net/carpage2/RB25DET_ECR33_Pinout.pdf
and to me it seems that the injector pins ARE swapped already, they should be correct without any changes? If this really is the case, then Matt should update the document about these injector pins..
Re: Type 2 in Z32 for R33 RB25DET pinouts - document
Hi!Zuikkis wrote:Hey! Ignore my last post. I just compared RB25DET and Z32 pinouts:
http://www.allpinouts.org/index.php/199 ... _300ZX_ECU
http://www.gweeds.net/carpage2/RB25DET_ECR33_Pinout.pdf
and to me it seems that the injector pins ARE swapped already, they should be correct without any changes? If this really is the case, then Matt should update the document about these injector pins..
Is there any point in this?
Would be nice to know if the the .pdf is final before I fire up my soldering station.
Cheers,
Andrew
Re: Type 2 in Z32 for R33 RB25DET pinouts - document
Base is a 47P10Matt wrote:Not sure here. Eric what part number are you using as a base for this code so I can compare the BIN files with/without your changes?
Re:
Peace wrote:I've putted such resistor but fule temperature is like 78 and DTC code always appear.
I've wired fuel temp pin to resistor and resistor to the ECU ground pin is it 2000 Ohms resisotr or 2K its something different?
And another thing. I thinck my knock sensors are bad now. Car always jumps to knock maps even without reaching half load. I've retard ignition 2 degres later and it anyway jumps to knock maps usually. I heard there is a solution of putting Resisor in place of knock sensor?
I have the same issue!
2.2K, 80C, DTC!
Re: Type 2 in Z32 for R33 RB25DET pinouts - document
Weird about the different resistor values for fuel temp. I've always used 1 to 2K on the bench and got 25 to 40 degrees.
I guess the obvious solution is to try changing the value of the resistor..
PL
I guess the obvious solution is to try changing the value of the resistor..
PL
Re: Type 2 in Z32 for R33 RB25DET pinouts - document
wondering if the fuel temp sender is different between various Z32 ECUs
Part numbers with your ECUs? I've mainly done the 40Pxx JDM ECUs here with this mod
Part numbers with your ECUs? I've mainly done the 40Pxx JDM ECUs here with this mod
Re: Type 2 in Z32 for R33 RB25DET pinouts - document
Hi!
I was thinking along the same line.
The Part Number is:
41P03 (was a refurbished unit .. )
I will connect a potentiometer and see what the ECU thinks the temperature is.
As said before I now have sliding values, ending up in 80C+
Would the strange fuel temp values affect what the ECU does?
I read in the Z32 the fuel pressure is upped.
Since I don't have this in my R33 it should not have any impact, should it?
I was thinking along the same line.
The Part Number is:
41P03 (was a refurbished unit .. )
I will connect a potentiometer and see what the ECU thinks the temperature is.
As said before I now have sliding values, ending up in 80C+
Would the strange fuel temp values affect what the ECU does?
I read in the Z32 the fuel pressure is upped.
Since I don't have this in my R33 it should not have any impact, should it?
Re: Type 2 in Z32 for R33 RB25DET pinouts - document
I know local guys who haven't bothered with the resistor for fuel temp and their cars do seem OK.
PL
PL
Re: Type 2 in Z32 for R33 RB25DET pinouts - document
the fueltemp (and coolant temp) sensor voltage output is checked at ECU-startup to be between 0.04V and 4.84V.
if it falls outside that range..because of a short (>5V) or not being connected (0V) it will generate a DTC and activate a tempsensor emulator (it will start to "guess" the temperature depending on how long the engine is running).
for the Z32 ECU, the fueltemp sensor is only used to switch the P-REG valve on/off at startup and only if fueltemp is >75C
nothing more, nothing less...the sensor's signal is not used for anything else.
-Eric
if it falls outside that range..because of a short (>5V) or not being connected (0V) it will generate a DTC and activate a tempsensor emulator (it will start to "guess" the temperature depending on how long the engine is running).
for the Z32 ECU, the fueltemp sensor is only used to switch the P-REG valve on/off at startup and only if fueltemp is >75C
nothing more, nothing less...the sensor's signal is not used for anything else.
-Eric
Re: Type 2 in Z32 for R33 RB25DET pinouts - document
Hi Eric,
Thanks for the explanation.
That explains the moving values for temperature.
I am just guessing here, but ->
If there is a 'short' shouldn't the voltage be 0 volt?
And if the sensor is not connected 5 volt?
GND
Thanks for the explanation.
That explains the moving values for temperature.
I am just guessing here, but ->
If there is a 'short' shouldn't the voltage be 0 volt?
And if the sensor is not connected 5 volt?
GND
Re: Type 2 in Z32 for R33 RB25DET pinouts - document
If there is a short to 0V or 5V, Nistune doesn't show the actual measured value, instead it shows this "emulated" temperature that starts from something like 20C and rises slowly to 80C..Torque wrote: If there is a 'short' shouldn't the voltage be 0 volt?
And if the sensor is not connected 5 volt?
Anyway, I think Eric is correct in that fuel temp only affects the P-REG valve, which is not present in RB25DET, anyway. Just disable the DTC and don't worry about it.