Jump to content
SAU Community

Recommended Posts

Hi All,

Just in case you are interested detailed below are the new/additional locations that you can expect to find the ACT mobile Revenue collection offices :-). Speed cameras located at black spots, near schools and aged accommodation homes and at other sites where vulnerable citizens are exposed to danger are supportable from a road safety perspective, however other locations are purely revenue raising and should be identified as such.

I suppose with all the additional locations available below the ACT bottom line should become a little healthier in near future.

New Canberra SPEED CAMERA locations effective the 17th January

63 - Canberra Ave - Between Mildura Street and Monaro Highway

64 - Canberra Ave - Between Harman Naval Station and Newcastle Street

65 - Kings Avenue - Between Bowen Drive and Parkes Way

66 - William Hovell Drive - Between Bindubi Street and Coulter Drive

67 - William Hovell Drive - Between Coulter Drive and Drake Brockman

Drive

68 - Commonwealth Avenue - Between King Edward Terrace and London Circuit

69 - Gundaroo Drive - Between Burrowa Street and Gungahlin Drive

70 - Gundaroo Drive - Between Barton Highway and Nudurr Drive

71 - Bindubi Street - Between Banjalong Crescent and Cross Street

72 - Clift Crescent - Between Hemming Crescent and Rohan Street

73 - Cotter Road - Between Eucumbene Drive and Mount Stromlo Road

74 - Federal Highway - Between Antill Street and Majura Road

75 - Majura Road - Between Federal Highway and Fairbairn Avenue

76 - Ellenborough Street - Between Ginninderra Drive and Maribyrnong

Avenue

77 - Northbourne Avenue - Between Barton Highway and Stirling Avenue

78 - Southern Cross Drive - Between Coulter Drive and Kingsford Smith

Drive

79 - Southern Cross Drive - Between Kingsford Smith Drive and Spofforth

Street

80 - Sulwood Drive - Between Erindale Drive and Tuggeranong Parkway

81 - Coulter Drive - Between Belconnen Way and Lachlan Street

82 - Eastern Valley Way - Between Belconnen Way and College Street

83 - Haydon Drive - Between Belconnen Way and Ginninderra Drive

84 - Yamba Drive - Between Hindmarsh Drive and Wisdom Street

f**king barstards all they want is more money those greedy f**k stains

Link to comment
https://www.sau.com.au/forums/topic/102886-speed-cameras/
Share on other sites

i have not seen any results yet but i would really like to see if accidents have come down any significant number since the introduction of all these speed cameras... if anything i reckon in some cases accidents would go up with people shitting themselfs everytime they see one.

Link to comment
https://www.sau.com.au/forums/topic/102886-speed-cameras/#findComment-1889726
Share on other sites

Speed camera's in a blackspot like on the hume - I can almost understand that.

Otherwise, its just a revenue raiser. I honestly don't beleive that they are there for any other purpose. How can a fixed camera (aside from making people not speed in front of it) make our roads safer?

Link to comment
https://www.sau.com.au/forums/topic/102886-speed-cameras/#findComment-1890424
Share on other sites

clift cresent :S thats stupid imo

They will get heaps of ppl there. I always see a marked car with radar sitting on the side of the road between deamer and the shops (heading towards the shops). They sit rite at the school zone sign... You dont see em till your going past :P.

I spose it means 1 more cop could now be doing better things with his/her time.

Link to comment
https://www.sau.com.au/forums/topic/102886-speed-cameras/#findComment-1892345
Share on other sites

Yeh, normally people are doin 80km on Clift, and normally there is a cop waiting to catch you to make his quota for the night :P.

There is a bus driver living on that Clift that has gotten caught 5 times, but he is a dick and needs punishment.

Out of all the accidents I've had, none have been my fault. Three times i have not been moving and been hit into, twice i've been slowing down and hit into.

Of the five times hit, four times it has been someone over the age of 25. One time a old fart had been drunk and the police refused to come to arrest his ass, because no-one was injured. All occasions the other party has not been paying attention and If I had been speeding, would have avoided a accident!

Speed camera's won't solve the problem, but I think it will help. Main issue is driver training and awareness.

Edited by StinkyPoo
Link to comment
https://www.sau.com.au/forums/topic/102886-speed-cameras/#findComment-1892399
Share on other sites

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

    • Nah. For something like boost control I wouldn't start my design with PID. I'd go with something that originates in the fuzzy logic world and use an emergency function or similar concept. PID can and does work, but at its fundamental level it is not suited to quick action. I'd be reasonably sure that the Profecs et al all transitioned to a fuzzy algorithm back in the 90s. Keep in mind also that where and when I have previously talked about using a Profec, I'm usually talking about only doing an open loop system anyway. All this talk of PID and other algorithms only comes into play when you're talking closed loop boost control, and in the context of what the OP needs and wants, we're probably actually in the realm of open loop anyway. Closed loop boost control has always bothered me, because if you sense the process value (ie the boost measurement that you want to control) in the plenum (after the throttle), then boost control to achieve a target is only desirable at WOT. When you are not WOT, you do not want the the boost to be as high as it can be (ie 100% of target). That's why you do not have the throttle at WO. You're attempting to not go as fast as you can. If the process variable is measured upstream of the throttle (ie in an RB26 plenum, or the cold side pipework in others) then yeah, sure, run the boost controller closed loop to hit a target boost there, and then the throttle does what it is supposed to do. Just for utter clarity.... an old Profec B Spec II (or whatever it is called, and I've got one, and I never look at it, so I can't remember!) and similar might have a MAP sensor, and it might show you the actual boost in the plenum (when the MAP sensor is connected to the plenum) but it does not use that value to decide what it is doing to control the boost, except to control the gating effect (where it stops holding the gate closed on the boost ramp). It's not closed loop at all. Once the gate is released, it's just the solenoid flailing away at whatever duty cycle was configured when it was set up. I'm sure that there are many people who do not understand the above points and wonder wtf is going on.  
    • This has clearly gone off on quite a tangent but the suggestion was "go standalone because you probably aren't going to stop at just exhaust + a mild tune and manual boost controller", not "buy a standalone purely for a boost controller". If the scope does in fact stop creeping at an EBC then sure, buy an EVC7 or Profec or whatever else people like to run and stop there. And I have yet to see any kind of aftermarket boost control that is more complicated than a PID controller with some accounting for edge cases. Control system theory is an incredibly vast field yet somehow we always end up back at some variant of a PID controller, maybe with some work done to linearize things. I have done quite a lot, but I don't care to indulge in those pissing matches, hence posting primary sources. I deal with people quite frequently that scream and shout about how their opinion matters more because they've shipped more x or y, it doesn't change the reality of the data they're trying to disagree with. Arguing that the source material is wrong is an entirely separate point and while my experience obviously doesn't matter here I've rarely seen factory service manuals be incorrect about something. It's not some random poorly documented internal software tool that is constantly being patched to barely work. It's also not that hard to just read the Japanese and double check translations either. Especially in automotive parts most of it is loanwords anyways.
    • If you are keeping the current calipers you need to keep the current disc as the spacing of the caliper determines the disc diameter. Have you trial fitted the GTS brakes fit on a GTSt hub or is this forward planning? There could be differences in caliper mount spacing, backing plate and even hub shape that could cause an issue.
    • Hi there I have a r33 gts with 4 stud small brakes, I'm going to convert to 5 stud but keep the small brakes, what size rotor would I need?
    • First up, I wouldn't use PID straight up for boost control. There's also other control techniques that can be implemented. And as I said, and you keep missing the point. It's not the ONE thing, it's the wrapping it up together with everything else in the one system that starts to unravel the problem. It's why there are people who can work in a certain field as a generalist, IE a IT person, and then there are specialists. IE, an SQL database specialist. Sure the IT person can build and run a database, and it'll work, however theyll likely never be as good as a specialist.   So, as said, it's not as simple as you're thinking. And yes, there's a limit to the number of everything's in MCUs, and they run out far to freaking fast when you're designing a complex system, which means you have to make compromises. Add to that, you'll have a limited team working on it, so fixing / tweaking some features means some features are a higher priority than others. Add to that, someone might fix a problem around a certain unrelated feature, and that change due to other complexities in the system design, can now cause a new, unforseen bug in something else.   The whole thing is, as said, sometimes split systems can work as good, and if not better. Plus when there's no need to spend $4k on an all in one solution, to meet the needs of a $200 system, maybe don't just spout off things others have said / you've read. There's a lot of misinformation on the internet, including in translated service manuals, and data sheets. Going and doing, so that you know, is better than stating something you read. Stating something that has been read, is about as useful as an engineering graduate, as all they know is what they've read. And trust me, nearly every engineering graduate is useless in the real world. And add to that, if you don't know this stuff, and just have an opinion, maybe accept what people with experience are telling you as information, and don't keep reciting the exact same thing over and over in response.
×
×
  • Create New...