Jump to content
SAU Community

Recommended Posts

  • Replies 244
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Posted Images

Had a chance to test mine out today, with the help of Cubes and his laptop. :)

Had to setup the com port to recognize the usb adaptor supplied by the Datalogit people. After it was done, we had no problems with data transfer, or dropouts.

I need get a AFR meter on the car to fully utilise the software and cable :O

Also i can recommend people to get Dataloglab. It makes a hell of a difference to reading the logged data that we grabbed while cruising.

Edited by Bl4cK32

Whats the brand is your Serial->USB adaptor Bl4ck32?

EDIT: Girls... Post your datalogit logs. :O

The highest load (airflow hence power) peak we saw was

Bl4ck32's peaks at 17322, approx load point 17-18 - RB20DET Highflow ~15-16psi)

Mine peaks with a load of 14832, approx load point 16-17 (VG30DET TUrbo ~12psi tailing off to 10psi)

Edited by Cubes

This is the Serial to USB dongle the datalogit likes/uses.

http://www.ferret.com.au/articles/14/0c02f714.asp

I've had a little look around, it looks as if the dongle is only available in NZ.

Edited by Cubes

very handy it is. what ive been doing is setup the temp ign increase on the hand controller then load datalogit and run map watch with advanced knock and watch the avg / max values to see how it pans it and you can quickly work out what areas where you can afford more timing

i had a 20 minute datalogit session just lost as the laptop battery went flat and datalogit doesnt write/commit until the end :O

Why does the values from basic knock differ from advanced knock?

The basic knock values read higher, i.e one of the logs had a ping of 115 in basic yet it was only 60 in advanced. Both set to max.

Edited by Cubes

hmm that explains it then cos i was doing advanced knock watch and i saw a few rows of 100+ but the max the hand controller showed was 52. and i dont recall my tune knocking that much also. good thinkin 99. ive asked to join the usergoups so hopefully this stuff is covered in there

Why does the values from basic knock differ from advanced knock?

The basic knock values read higher, i.e one of the logs had a ping of 115 in basic yet it was only 60 in advanced. Both set to max.

It has always behaved that way. I remember asking the question and the answer from the programmers of the Datalogit was :

There should be no difference between Basic and Advanced Knock. The Basic and Advanced groups correspond to 2 different commands to get different groups of data out of the Power-FC.

Since the knock reading has a peak and hold effect between readings, there is a chance that either the Advanced otr the Basic knock will see a higher knock, but shouldn't happen consistently.

There is a chance that there is a bug in FC-Edit or actually in the Power-FC itself. What is your Power-FC type and version number?

There was also another input from a member who contributes regularly.

Unfortunately I do not know the exact reason why Basic knock shows higher values than Advanced knock. Here are some possibilities:

1)      Sampling rates are different

a.      One setup may be checking for knock values at a higher sampling frequency and that’s why it’s able to recorded some higher values

2)      On some applications, there are two knock sensors

a.      While it’s doubtful, that each sensor is tied to a different mode (one for advanced, one for basic) you never know what was going through the engineer’s mind that set up the system.

b.      If both modes sample at the same rate (thus #1 possibility is eliminated), it may be possible that one mode shows the peak value for one of the two sensors while the other mode shows an average value.

Whatever the case, it’s of little value to look at just a peak number from a knock sensor. You really need to look at the datalog in the chart screen and see the plot of knock sensor values. Remember, a knock sensor is nothing more than a specialized microphone that’s designed to listen for sounds in the frequency range of knock. As the engine rpm is increased it’s normal to see higher values from the knock sensor. Actual knock is going to look like a quick spike from the normal values. Thus, it’s going to show up whether you look at it in the Advanced or the Basic mode. 

You ears and a good stethoscope or HKS Knock amplifier with headphones is an even better way to listen for knock.

.

It has access to ignition correction values for air temp, water temp, voltage, etc...

Every Power FC has these correction tables, but they are not accessible with the hand controller. On the other hand, i have never touched mine, as they look pretty spot on with default values.

For example (for the GTR Datalogit), upto 50 degrees intake temp, it uses the normal values from the ignition map. From 50 to 60 C, it starts taking out 3 degrees, between 60 and 70 C, it takes another 2 degrees (up to 5 all up) from the ignition map. In short, if your intake temps were 70 C, it would run 5 degrees less ignition.

As i stated long time ago, the main advantage of the Datalogit as its name suggests, is to log data. Unlocked tuning parameters is just an added bonus.

Emre,

I'll go by the basic knock as that has consistently returned higher knock values with both Bl4ck32 and my R32 AP PowerFC.

With the PFC H/C plugged in at the same time the H/C has reported the same knock value as the datalogits basic knock.

It appears my and bl4ck32's knock sensors are working well.

General driving and cruising it basically sits on 1, give it a boot full and it will creep to 20-30 and that is it, if it goes higher then it will most definitely hit either 60ish or 100ish with quick spikes. It never holds an even 45+.

Edited by Cubes

I wanted to check the same thing, but while logging data, my hand controller freezes and doesn't display or hold any values.

On the other hand, while i had some high knock values under 'basic knock', there were no warning flashes coming from the dash.

Interestering...

When Bl4ck32 was using the laptop it was in advanced knock, i gunned it in third, dash light flashed and asked him if it went over 50 (I changed the max value before dash light flashes), he said no. :S

I've since pulled a few degree's out around 4000rpm, no more dash light flashing as there is no longer any det at that rpm. 5600rpm+ i've pulled a couple degree's out but I won't take the car there as its leaning out from then onwards.

Edited by Cubes

Interesting links....

http://www.rx7club.com/showthread.php?t=14...ght=Basic+Knock

http://www.rx7club.com/showthread.php?t=14...ght=Basic+Knock

Take the knock readings with a pinch of salt. Throw it on the dyno watch the exhaust and listen for ping. :)

Edited by Cubes

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



  • Latest Posts

    • I did end up getting it sorted, as GTSBoy said, there was a corroded connection and wire that needed to be replaced. I ended up taking out the light assembly, giving everything a good clean and re-soldered the old joints, and it came out good.
    • Wow, thanks for your help guys 🙏. I really appreciate it. Thanks @Rezz, if i fail finding any new or used, full or partial set of original Stage carpets i will come back to you for sure 😉 Explenation is right there, i just missed it 🤦‍♂️. Thanks for pointing out. @soviet_merlin in the meantime, I received a reply from nengun, and i quote: "Thanks for your message and interest in Nengun. KG4900 is for the full set of floor mats, while KG4911 is only the Driver's Floor Mat. FR, RH means Front Right Hand Side. All the Full Set options are now discontinued. However, the Driver's Floor Mat options are still available according to the latest information available to us. We do not know what the differences would be, but if you only want the one mat, we can certainly see what we can find out for you". Interesting. It seems they still have some "new old stock" that Duncan mentioned 🤔. I wonder if they can provide any photos......And i also just realized that amayama have G4900 sets. I'm tempted too. 
    • Any update on this one? did you manage to get it fixed?    i'm having the same issue with my r34 and i believe its to do with the smart entry (keyless) control module but cant be sure without forking out to get a replacement  
    • So this being my first contribution to the SAU forums, I'd like to present and show how I had to solve probably one of the most annoying fixes on any car I've owned: replacing a speedometer (or "speedo") sensor on my newly acquired Series 1 Stagea 260RS Autech Version. I'm simply documenting how I went about to fix this issue, and as I understand it is relatively rare to happen to this generation of cars, it is a gigantic PITA so I hope this helps serve as reference to anyone else who may encounter this issue. NOTE: Although I say this is meant for the 260RS, because the gearbox/drivetrain is shared with the R33 GTR with the 5-speed manual, the application should be exactly the same. Background So after driving my new-to-me Stagea for about 1500km, one night while driving home the speedometer and odometer suddenly stopped working. No clunking noise, no indication something was broken, the speedometer would just stop reading anything and the odometer stopped going up. This is a huge worry for me, because my car is relatively low mileage (only 45k km when purchased) so although I plan to own the car for a long time, a mismatched odometer reading would be hugely detrimental to resale should the day come to sell the car. Thankfully this only occurred a mile or two from home so it wasn't extremely significant. Also, the OCD part of me would be extremely irked if the numbers that showed on my dash doesn't match the actual ageing of the car. Diagnosing I had been in communication with the well renown GTR shop in the USA, U.P.garage up near University Point in Washington state. After some back and forth they said it could be one of two things: 1) The speedometer sensor that goes into the transfer case is broken 2) The actual cluster has a component that went kaput. They said this is common in older Nissan gauge clusters and that would indicate a rebuild is necessary. As I tried to figure out if it was problem #1, I resolved problem #2 by sending my cluster over to Relentless Motorsports in Dallas, TX, whom is local to me and does cluster and ECU rebuilds. He is a one man operation who meticulously replaces every chip, resistor, capacitor, and electronic component on the PCB's on a wide variety of classic and modern cars. His specialty is Lexus and Toyota, but he came highly recommended by Erik of U.P.garage since he does the rebuilds for them on GTR clusters.  For those that don't know, on R32 and R33 GTR gearboxes, the speedometer sensor is mounted in the transfer case and is purely an analog mini "generator" (opposite of an alternator essentially). Based on the speed the sensor spins it generates an AC sine wave voltage up to 5V, and sends that via two wires up to the cluster which then interprets it via the speedometer dial. The signal does NOT go to the ECU first, the wiring goes to the cluster first then the ECU after (or so I'm told).  Problems/Roadblocks I first removed the part from the car on the underside of the transfer case (drain your transfer case fluid/ATF first, guess who found out that the hard way?), and noted the transfer case fluid was EXTREMELY black, most likely never changed on my car. When attempting to turn the gears it felt extremely gritty, as if something was binding the shaft from rotating properly. I got absolutely no voltage reading out of the sensor no matter how fast I turned the shaft. After having to reflow the solder on my AFM sensors based on another SAU guide here, I attempted to disassemble the silicone seal on the back of the sensor to see what happened inside the sensor; turns out, it basically disintegrated itself. Wonderful. Not only had the electrical components destroyed themselves, the magnetic portion on what I thought was on the shaft also chipped and was broken. Solution So solution: find a spare part right? Wrong. Nissan has long discontinued the proper sensor part number 32702-21U19, and it is no longer obtainable either through Nissan NSA or Nissan Japan. I was SOL without proper speed or mileage readings unless I figured out a way to replace this sensor. After tons of Googling and searching on SAU, I found that there IS however a sensor that looks almost exactly like the R33/260RS one: a sensor meant for the R33/R34 GTT and GTS-T with the 5 speed manual. The part number was 25010-21U00, and the body, plug, and shaft all looked exactly the same. The gear was different at the end, but knowing the sensor's gear is held on with a circlip, I figured I could just order the part and swap the gears. Cue me ordering a new part from JustJap down in Kirrawee, NSW, then waiting almost 3 weeks for shipping and customs clearing. The part finally arrives and what did I find? The freaking shaft lengths don't match. $&%* I discussed with Erik how to proceed, and figuring that I basically destroyed the sensor trying to get the shaft out of the damaged sensor from my car. we deemed it too dangerous to try and attempt to swap shafts to the correct length. I had to find a local CNC machinist to help me cut and notch down the shaft. After tons of frantic calling on a Friday afternoon, I managed to get hold of someone and he said he'd be able to do it over half a week. I sent him photos and had him take measurements to match not only the correct length and notch fitment, but also a groove to machine out to hold the retentive circlip. And the end result? *chef's kiss* Perfect. Since I didn't have pliers with me when I picked up the items, I tested the old gear and circlip on. Perfect fit. After that it was simply swapping out the plug bracket to the new sensor, mount it on the transfer case, refill with ATF/Nissan Matic Fluid D, then test out function. Thankfully with the rebuilt cluster and the new sensor, both the speedometer and odometer and now working properly!   And there you have it. About 5-6 weeks of headaches wrapped up in a 15 minute photo essay. As I was told it is rare for sensors of this generation to die so dramatically, but you never know what could go wrong with a 25+ year old car. I HOPE that no one else has to go through this problem like I did, so with my take on a solution I hope it helps others who may encounter this issue in the future. For the TL;DR: 1) Sensor breaks. 2) Find a replacement GTT/GTS-T sensor. 3) Find a CNC machinist to have you cut it down to proper specs. 4) Reinstall then pray to the JDM gods.   Hope this guide/story helps anyone else encountering this problem!
    • So this being my first contribution to the SAU forums, I'd like to present and show how I had to solve probably one of the most annoying fixes on any car I've owned: replacing a speedometer (or "speedo") sensor on my newly acquired Series 1 Stagea 260RS Autech Version. I'm simply documenting how I went about to fix this issue, and as I understand it is relatively rare to happen to this generation of cars, it is a gigantic PITA so I hope this helps serve as reference to anyone else who may encounter this issue. NOTE: Although I say this is meant for the 260RS, because the gearbox/drivetrain is shared with the R33 GTR with the 5-speed manual, the application should be exactly the same. Background So after driving my new-to-me Stagea for about 1500km, one night while driving home the speedometer and odometer suddenly stopped working. No clunking noise, no indication something was broken, the speedometer would just stop reading anything and the odometer stopped going up. This is a huge worry for me, because my car is relatively low mileage (only 45k km when purchased) so although I plan to own the car for a long time, a mismatched odometer reading would be hugely detrimental to resale should the day come to sell the car. Thankfully this only occurred a mile or two from home so it wasn't extremely significant. Also, the OCD part of me would be extremely irked if the numbers that showed on my dash doesn't match the actual ageing of the car. Diagnosing I had been in communication with the well renown GTR shop in the USA, U.P.garage up near University Point in Washington state. After some back and forth they said it could be one of two things: 1) The speedometer sensor that goes into the transfer case is broken 2) The actual cluster has a component that went kaput. They said this is common in older Nissan gauge clusters and that would indicate a rebuild is necessary. As I tried to figure out if it was problem #1, I resolved problem #2 by sending my cluster over to Relentless Motorsports in Dallas, TX, whom is local to me and does cluster and ECU rebuilds. He is a one man operation who meticulously replaces every chip, resistor, capacitor, and electronic component on the PCB's on a wide variety of classic and modern cars. His specialty is Lexus and Toyota, but he came highly recommended by Erik of U.P.garage since he does the rebuilds for them on GTR clusters.  For those that don't know, on R32 and R33 GTR gearboxes, the speedometer sensor is mounted in the transfer case and is purely an analog mini "generator" (opposite of an alternator essentially). Based on the speed the sensor spins it generates an AC sine wave voltage up to 5V, and sends that via two wires up to the cluster which then interprets it via the speedometer dial. The signal does NOT go to the ECU first, the wiring goes to the cluster first then the ECU after (or so I'm told).  Problems/Roadblocks I first removed the part from the car on the underside of the transfer case (drain your transfer case fluid/ATF first, guess who found out that the hard way?), and noted the transfer case fluid was EXTREMELY black, most likely never changed on my car. When attempting to turn the gears it felt extremely gritty, as if shttps://imgur.com/6TQCG3xomething was binding the shaft from rotating properly. After having to reflow the solder on my AFM sensors based on another SAU guide here, I attempted to disassemble the silicone seal on the back of the sensor to see what happened inside the sensor; turns out, it basically disintegrated itself. Wonderful. Not only had the electrical components destroyed themselves, the magnetic portion on what I thought was on the shaft also chipped and was broken. Solution So solution: find a spare part right? Wrong. Nissan has long discontinued the proper sensor part number 32702-21U19, and it is no longer obtainable either through Nissan NSA or Nissan Japan. I was SOL without proper speed or mileage readings unless I figured out a way to replace this sensor. After tons of Googling and searching on SAU, I found that there IS however a sensor that looks almost exactly like the R33/260RS one: a sensor meant for the R33/R34 GTT and GTS-T with the 5 speed manual. The part number was 25010-21U00, and the body, plug, and shaft all looked exactly the same. The gear was different at the end, but knowing the sensor's gear is held on with a circlip, I figured I could just order the part and swap the gears. Cue me ordering a new part from JustJap down in Kirrawee, NSW, then waiting almost 3 weeks for shipping and customs clearing. The part finally arrives and what did I find? The freaking shaft lengths don't match. $&%* I discussed with Erik how to proceed, and figuring that I basically destroyed the sensor trying to get the shaft out of the damaged sensor from my car. we deemed it too dangerous to try and attempt to swap shafts to the correct length. I had to find a local CNC machinist to help me cut and notch down the shaft. After tons of frantic calling on a Friday afternoon, I managed to get hold of someone and he said he'd be able to do it over half a week. I sent him photos and had him take measurements to match not only the correct length and notch fitment, but also a groove to machine out to hold the retentive circlip. And the end result? *chef's kiss* Perfect. Since I didn't have pliers with me when I picked up the items, I tested the old gear and circlip on. Perfect fit. After that it was simply swapping out the plug bracket to the new sensor, mount it on the transfer case, refill with ATF/Nissan Matic Fluid D, then test out function. Thankfully with the rebuilt cluster and the new sensor, both the speedometer and odometer and now working properly!   And there you have it. About 5-6 weeks of headaches wrapped up in a 15 minute photo essay. As I was told it is rare for sensors of this generation to die so dramatically, but you never know what could go wrong with a 25+ year old car. I HOPE that no one else has to go through this problem like I did, so with my take on a solution I hope it helps others who may encounter this issue in the future. For the TL;DR: 1) Sensor breaks. 2) Find a replacement GTT/GTS-T sensor. 3) Find a CNC machinist to have you cut it down to proper specs. 4) Reinstall then pray to the JDM gods.   Hope this guide/story helps anyone else encountering this problem!
×
×
  • Create New...