Jump to content
SAU Community

Recommended Posts

Awesome! Is it fussy about what type of video files?

Also, how bright is the screen in the car when it brings up split times etc.? I took my brother's car out to Wakefield yesterday which had an Aim dash, and in the sunlight I couldn't see a thing!

It's been about 18mths since I've used both Dashware and the LT-Q6000 but you just import the video file from your gopro or contour then import the data file from the qstarz then sync them together in Dashware.

I can't remember how bright and clear the screen is as Wakefield Park you are driving into the sun down the main straight. It is a much more clear and easier to read screen than the old PerformanceBox units (which I also have).

Also, how does it work out where you are on the track when you add the video file? Have you found it to be accurate?

Just can't work out how the video and data logging lines up accurately without any data from the video file.

The Qstarz unit you have to set a start/finish and also splits on the unit or in Dashware when you edit it together (which is the biggest let down of the Qstarz).

The Performance box you can actually download configuration files from there website of popular tracks from around Australia and the World and load them into the PB and it will have perfectly set start/finish and splits.

The Qstarz has an internal battery which when fully charged should get you through 2 full trackdays. The PerformanceBox has no internal battery and needs a cigarette lighter socket (which I had to get installed in my little car).

Phunky_Monkey has been using my LT-Q6000 the past few weeks so maybe he will have some feedback and/or video's available from his weekend at Phillip Island :)

You also have to manually sync the video and GPS data. So be sure to set the clock on the gopro so you can easily match video file to GPS data set. In dash ware you the have to use a slider bar to line up the data.

If you aren't good with software then you should just pay for a more expensive unit that does it all. I'm pretty savvy but I know others find it difficult.

When I have my lt6000 mounted on the windscreen I have no problem seeing it. I keep it set in lap time but it uses splits to estimate how you are going. Better than best lap will have green background and worse has red background while giving you a stop watch style counter on screen.

I like the Qstarz unit because it seems like it would give instant easy to understand feedback on the track. Green means fast, Red means slow.

+/- 0.2 sec seems like a lot of a difference though, have you tested the times against a beacon timer?

And with the video syncing, do you basically set the time of day on the video file, sync it with the GPS unit and match them that way?

Yes 0.2 is against drag and lap timers. Think about it, if your GPS is polling 10 times per second that's 0.1 s per data point. Dashware and QStarz software seem to calc crossing the line differently. Most of the time it's pretty close to Natsoft but can be out up to 0.2 across different software packages.

If you want more accuracy you have to be willing to pay $100's more. Just part of the technology really.

And Jimmy, you still have to open both video and GPS files, pick a point on the track and sync them that way. It's a but if guess work to get it right. Think about it, you aren't starting the video and GPS capture at exactly the same time at the track so you have to do it manually on your computer in Dashware.

All just part of learning to deal with the Tech. I can get it down to about 10 minutes of fiddling now, but that's after lots and lots of practice.

here's the last session (5 laps) recorded on my 1hz iPhone lap timer app compared to the transponder timing at Lakeside, in Nev's Z at Lakeside last week (I had to park my car after the first session so I put the iPhone in Nev's Z) :

post-15659-0-37293400-1380065747_thumb.jpg

as you can see the errors on those last 5laps are 0.02, 0.01, 0.03, 0.01, and 0.05

If a 10hz GPS timer's accuracy is an order of magnitude worse, something's wrong!

I think it is mainly due to the software and approximate location of start/finish.

I'm not fussed. In the car time lets me know if I'm faster/slower. That's what really matters to me.

I haven't really tried to fine tune to match natsoft.

Just remembered that most of the inconsistency is introduced from Dashware side of the equasion. (I'm out of practice cause about 10 month since I've had a track day :( boo hooo! )

I "think" DashWare doesn't try to interpolate it's polling. So for instance, when I was doing the drags the times were up to 0.2 out. So it reads stoped then moving 0.1 seconds later but starts timeing from full stopped. Then likewise I think it stops the clock when you pass over the mark. Thus not really all that accurate.

The devices that have 1hz signal actually assume the time based on the maths of where the finish line should have been between GPS pulses and then linearly split up the time.

  • 2 weeks later...

Just got a RaceChrono Pro but have not used it yet. The main reason for that choice was it has a remote mount GPS so that the screen can be located anywhere without worrying about GPS signals. Looks like the screen will be mounted on the speedo face where the colour changes at least will be readily seen via peripheral vision. Link http://roostindustries.com/lap_timers.php

I still use external GPS and free Racechrono phone software - just moved to the modern Android version which now exports all data to the csv files (not just laps as per nokia version). Therefore makes it a easy to sync data to video at takeoff.

  • 3 months later...

Just to update I bought a Qstarz, but the dickhead who I bought it off sent me the wrong mount :(

For some reason I thought it would automatically detect what track I was at but it appears I need to download maps.

Which maps do you guys use? Is it easy enough to record your own map? Still don't know how to use this thing.

What qstarz did you buy, just the gps thingy? if so, you then need to download racechrono software on your phone and it will automatically search tracks if/when your near them(thats the feature of the racechrono software, not the gps unit).

If yours is the qstarz all in one(gps and lap timer) then im not sure... hopeful;ly someone will know.

What i would like to know... if your doing a hill climb where theres a start and finish line, how would you setup your racechrono for that?

I know you can tell it where the start and finish lines are, but that requires you to know exactly where they are... on hillclimbs i dont know! and if you set it while there at the start line(a bit hard as you have to move along pretty quickly), how would you set the finish line as you pass it at who knows what speeds?

  • 3 weeks later...

Pez have you tried recording the tracks yourself? You had it at the SMSP South track day, how'd it go?

My only concern with the shared tracks is how old they are. Not sure if Eastern Creek is still the same layout

If you record them yourself do NOT try to do the set up from the unit. I've never gotten that to work.

Bring a laptop and record the data of the session as straight GPS data record (e.g. do not select circuit). Import in the QRacing set up the track and then load it back into the unit.

That's the only way I've been able to set up tracks.

To properly set up a track you have to drive across the start/finish slowly and you just can't do that unless you have the track to yourself.

  • 2 weeks later...

To properly set up a track you have to drive across the start/finish slowly and you just can't do that unless you have the track to yourself.

I've found some are missing and some downloaded tracks sta/fin don't match either the line or natsoft timing beam. So it's good to be able to record your own tracks.

As for the start/finish points, just take the gps recorder out of the car.

Walk backwards/forward a few times perpendicular to the track at your chosen point.

Later review your track session edit the sta/fin and move to where the extrapolated walk line crosses the track

Job done

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



  • Similar Content

  • Latest Posts

    • 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!
    • perhaps i should have mentioned, I plugged the unit in before i handed over to the electronics repair shop to see what damaged had been caused and the unit worked (ac controls, rear demister etc) bar the lights behind the lcd. i would assume that the diode was only to control lighting and didnt harm anything else i got the unit back from the electronics repair shop and all is well (to a point). The lights are back on and ac controls are working. im still paranoid as i beleive the repairer just put in any zener diode he could find and admitted asking chatgpt if its compatible   i do however have another issue... sometimes when i turn the ignition on, the climate control unit now goes through a diagnostics procedure which normally occurs when you disconnect and reconnect but this may be due to the below   to top everything off, and feel free to shoot me as im just about to do it myself anyway, while i was checking the newly repaired board by plugging in the climate control unit bare without the housing, i believe i may have shorted it on the headunit surround. Climate control unit still works but now the keyless entry doesnt work along with the dome light not turning on when you open the door. to add to this tricky situation, when you start the car and remove the key ( i have a turbo timer so car remains on) the keyless entry works. the dome light also works when you switch to the on position. fuses were checked and all ok ive deduced that the short somehow has messed with the smart entry control module as that is what controls the keyless entry and dome light on door opening   you guys wouldnt happen to have any experience with that topic lmao... im only laughing as its all i can do right now my self diagnosed adhd always gets me in a situation as i have no patience and want to get everything done in shortest amount of time as possible often ignoring crucial steps such as disconnecting battery when stuffing around with electronics or even placing a simple rag over the metallic headunit surround when placing a live pcb board on top of it   FML
    • Bit of a pity we don't have good images of the back/front of the PCB ~ that said, I found a YT vid of a teardown to replace dicky clock switches, and got enough of a glimpse to realize this PCB is the front-end to a connected to what I'll call PCBA, and as such this is all digital on this PCB..ergo, battery voltage probably doesn't make an appearance here ; that is, I'd expect them to do something on PCBA wrt power conditioning for the adjustment/display/switch PCB.... ....given what's transpired..ie; some permutation of 12vdc on a 5vdc with or without correct polarity...would explain why the zener said "no" and exploded. The transistor Q5 (M33) is likely to be a digital switching transistor...that is, package has builtin bias resistors to ensure it saturates as soon as base threshold voltage is reached (minimal rise/fall time)....and wrt the question 'what else could've fried?' ....well, I know there's an MCU on this board (display, I/O at a guess), and you hope they isolated it from this scenario...I got my crayons out, it looks a bit like this...   ...not a lot to see, or rather, everything you'd like to see disappears down a via to the other side...base drive for the transistor comes from somewhere else, what this transistor is switching is somewhere else...but the zener circuit is exclusive to all this ~ it's providing a set voltage (current limited by the 1K3 resistor R19)...and disappears somewhere else down the via I marked V out ; if the errant voltage 'jumped' the diode in the millisecond before it exploded, whatever that V out via feeds may have seen a spike... ....I'll just imagine that Q5 was switched off at the time, thus no damage should've been done....but whatever that zener feeds has to be checked... HTH
×
×
  • Create New...