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

    • Can I suggest you try EBC directly again and link them to as many competitor catalogues as you can to show their listing is incorrect, eg https://dba.com.au/product/front-4000-series-hd-brake-rotor-dba42304/ If you have access to an R33 GTST VIN and your VIN, you could also use a Nissan Parts lookup like Amayama to show them the part number is different between 33 GTST and 34 GTT which may get their attention
    • So i got reply from EBC and they just this site where you can clearly see those 296mm fronts on R34 GTT. I send them photos and "quotes" that 296mm are not for 34 GTT and they are too small. But it will be very hard to return them cuz nobody here knows 100% and they just copy those EBC catalogue :-D https://ebcbrakesdirect.com/automotive/nissan/skyline-r34
    • Hi, is the HKS  Tower Bar still available ? negotiable ? 🤔
    • From there, it is really just test and assemble. Plug the adapter cables from the unit into the back of the screen, then the other side to the car harness. Don't forget all the other plugs too! Run the cables behind the unit and screw it back into place (4 screws) and you should now have 3 cables to run from the top screen to the android unit. I ran them along the DS of the other AV units in the gap between their backets and the console, and used some corrugated tubing on the sharp edges of the bracket so the wires were safe. Plug the centre console and lower screen in temporarily and turn the car to ACC, the AV should fire up as normal. Hold the back button for 3 sec and Android should appear on the top screen. You need to set the input to Aux for audio (more on that later). I put the unit under the AC duct in the centre console, with the wifi antenna on top of the AC duct near the shifter, the bluetooth antenna on the AC duct under the centre console The GPS unit on top of the DS to AC duct; they all seem to work OK there are are out of the way. Neat cable routing is a pain. For the drive recorder I mounted it near the rear view mirror and run the cable in the headlining, across the a pillar and then down the inside of the a pillar seal to the DS lower dash. From there it goes across and to one USB input for the unit. The second USB input is attached to the ECUtec OBD dongle and the 3rd goes to the USB bulkhead connected I added in the centre console. This is how the centre console looks "tidied" up Note I didn't install the provided speaker, didn't use the 2.5mm IPod in line or the piggyback loom for the Ipod or change any DIP switches; they seem to only be required if you need to use the Ipod input rather than the AUX input. That's it, install done, I'll follow up with a separate post on how the unit works, but in summary it retains all factory functions and inputs (so I still use my phone to the car for calls), reverse still works like factory etc.
    • Place the new daughterboard in the case and mount it using the 3 small black rivets provided, and reconnect the 3 factory ribbon cables to the new board Then, use the 3 piggyback cables from the daughterboard into the factory board on top (there are stand offs in the case to keep them apart. and remember to reconnect the antenna and rear cover fan wires. 1 screw to hold the motherboard in place. Before closing the case, make a hole in the sticker covering a hole in the case and run the cable for the android unit into the plug there. The video forgot this step, so did I, so will you probably. Then redo the 4 screws on back, 2 each top and bottom, 3 each side and put the 2 brackets back on.....all ready to go and not that tricky really.      
×
×
  • Create New...