Jump to content
SAU Community

Recommended Posts

With all the reports of Skyline's being stolen left, right and centre, it's easy to lose track of where it is actually happening. I'm more of a visual person and had some time to kill, so I made a map of all the Skyline's that have been stolen in the past two years from reports on this forum. This map is just an indication of the areas where cars have been stolen in the past and may be served as a cautious warning/reminder for anybody living in or parking in those areas or surrounding suburbs. Take care of your cars and maybe invest in a decent GPS tracking system if you are really concerned!

Click on the image below (or this text) to see the map:

ScwoA.png

Link to comment
https://www.sau.com.au/forums/topic/413542-map-of-stolen-skylines-2011-2012/
Share on other sites

Good idea...but if you use the search function, you'll see there are already plenty of threads about the west/north suburbs and fun-filled activities you can do within them :P

Lovely thread but, cars can get stolen ANYWHERE, all you have to do is to buy a insurance. So you're covered when your car is stolen.

Simple really. No use in being paranoid.

Lovely thread but, cars can get stolen ANYWHERE, all you have to do is to buy a insurance. So you're covered when your car is stolen.

Simple really. No use in being paranoid.

Not that simple. Sure you might get your money within a month, but how long is it going to take to find that perfect car? After my first GTR got stolen i had to wait just over a year until one that had all the shit i wanted on it popped up. So i'd prefer it not to get stolen this time.

Not that simple. Sure you might get your money within a month, but how long is it going to take to find that perfect car? After my first GTR got stolen i had to wait just over a year until one that had all the shit i wanted on it popped up. So i'd prefer it not to get stolen this time.

I'd rather having insurance and searching forever for 'perfect' car than not having insurance at all...

That way I'm able to sleep at night knowing I'm covered.

That's just me, you can put security system to shame Fort Knox and someone will find a way to steal it, unfortunately it's the way it is nowdays.

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

    • Yeah, that's fine**. But the numbers you came up with are just wrong. Try it for yourself. Put in any voltage from the possible range and see what result you get. You get nonsense. ** When I say "fine", I mean, it's still shit. The very simple linear formula (slope & intercept) is shit for a sensor with a non-linear response. This is the curve, from your data above. Look at the CURVE! It's only really linear between about 30 and 90 °C. And if you used only that range to define a curve, it would be great. But you would go more and more wrong as you went to higher temps. And that is why the slope & intercept found when you use 50 and 150 as the end points is so bad halfway between those points. The real curve is a long way below the linear curve which just zips straight between the end points, like this one. You could probably use the same slope and a lower intercept, to move that straight line down, and spread the error out. But you would 5-10°C off in a lot of places. You'd need to say what temperature range you really wanted to be most right - say, 100 to 130, and plop the line closest to teh real curve in that region, which would make it quite wrong down at the lower temperatures. Let me just say that HPTuners are not being realistic in only allowing for a simple linear curve. 
    • I feel I should re-iterate. The above picture is the only option available in the software and the blurb from HP Tuners I quoted earlier is the only way to add data to it and that's the description they offer as to how to figure it out. The only fields available is the blank box after (Input/ ) and the box right before = Output. Those are the only numbers that can be entered.
    • No, your formula is arse backwards. Mine is totally different to yours, and is the one I said was bang on at 50 and 150. I'll put your data into Excel (actually it already is, chart it and fit a linear fit to it, aiming to make it evenly wrong across the whole span. But not now. Other things to do first.
    • God damnit. The only option I actually have in the software is the one that is screenshotted. I am glad that I at least got it right... for those two points. Would it actually change anything if I chose/used 80C and 120C as the two points instead? My brain wants to imagine the formula put into HPtuners would be the same equation, otherwise none of this makes sense to me, unless: 1) The formula you put into VCM Scanner/HPTuners is always linear 2) The two points/input pairs are only arbitrary to choose (as the documentation implies) IF the actual scaling of the sensor is linear. then 3) If the scaling is not linear, the two points you choose matter a great deal, because the formula will draw a line between those two points only.
    • Nah, that is hella wrong. If I do a simple linear between 150°C (0.407v) and 50°C (2.98v) I get the formula Temperature = -38.8651*voltage + 165.8181 It is perfectly correct at 50 and 150, but it is as much as 20° out in the region of 110°C, because the actual data is significantly non-linear there. It is no more than 4° out down at the lowest temperatures, but is is seriously shit almost everywhere. I cannot believe that the instruction is to do a 2 point linear fit. I would say the method I used previously would have to be better.
×
×
  • Create New...