Jump to content
SAU Community

Recommended Posts

straight back fro NY or a few days in LA?

the jetlag with NYC-> MEL is a real kicker!

Last week was Vegas > LA > MEL

slept like 12 hours on way back cos I was so wrecked so not too tired anymore. (Although slept through the f1 :()

got done by Mansfield HWP on sunday. business as usual for the senior constable. even had a stamp with his details so didnt have fill in information about the issuing officer. looked like the whole force was out on cars and bikes in surrounding metro areas though... what happens when the number of speeding fines being dished out drops and suddenly theyre not making back the OT theyre paying the force? will they just cut it or make more of an effort to raise money?

also, i tried googling but couldnt find it: the way they work out detected speed and alleged speed. is it % based or just a flat number? Because I saw they changed the rules so that speedos should never read less than the actual speed, but thought that 2km/h is hardly significant when on a 100km/h road.

Detected speed is what showed on the radar, i.e. the speed you were actually doing assuming accuracy of equipment. Alleged is detected speed minus 2km/h if a cop and 3km/h if a camera, giving benefit of doubt which covers equipment inaccuracy and the odd chance your speedo is reading low...this is the speed that you get charged based on.

Speedos from factory are usually generous because the opposite creates law suits.

Therefore if alleged speed is a couple km over the limit, fair to say your speedo was probably displaying ~7-8km/h over the limit, unless you have recalibrated your speedo or changed your tyre circumference to a bigger size, which will make you as fast as or faster than what the speedo is actually displaying.

From what I hear most cops don't bother with 5km/h detected over / flamin mongrel fines. You would have to be picked on for them to get you for a couple km/h over. Cameras are a different story of course...

Detected speed is what showed on the radar, i.e. the speed you were actually doing assuming accuracy of equipment. Alleged is detected speed minus 2km/h if a cop and 3km/h if a camera, giving benefit of doubt which covers equipment inaccuracy and the odd chance your speedo is reading low...this is the speed that you get charged based on.

Speedos from factory are usually generous because the opposite creates law suits.

Therefore if alleged speed is a couple km over the limit, fair to say your speedo was probably displaying ~7-8km/h over the limit, unless you have recalibrated your speedo or changed your tyre circumference to a bigger size, which will make you as fast as or faster than what the speedo is actually displaying.

From what I hear most cops don't bother with 5km/h detected over / flamin mongrel fines. You would have to be picked on for them to get you for a couple km/h over. Cameras are a different story of course...

There's been a push from the top that they start fining for a couple ks over

http://www.heraldsun.com.au/news/law-order/traffic-police-told-to-target-lowlevel-speeding-offenders/story-fni0fee2-1226807937959

I don't understand that bullshit excuse...if the margin for error is that tiny before you enter the "danger zone" (i.e. exactly 2km/h over the speed limit), to warrant low speed fines...then why not reduce speed limits another 5km/h? As they are clearly too high with such a small margin of error.

VicPol seems to think humans are robots, what with our impeccable ability to maintain exact speed whilst looking at the road and their superhuman ability to detect decibel readings with their ears and distort reality with their minds ala Matrix style.

Vicpol's behaving erratically lately.

Went past a hwp 10k over limit, they didn't do squat.

Other day on monash went past bike cop at 20k over, he didn't do squat as well.

Are officers defying Commissioner Hill's orders or it's 'too much paperwork' for them?

I'll see what comes in the letterbox later on...

Guest
This topic is now closed to further replies.



  • Similar Content

  • Latest Posts

    • 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...