Jump to content
SAU Community

Recommended Posts

Eagle Mountain Bike Park had been planned and is 95% finished. It is a purpose "built" park for mountain biking in SA. As they have "cracked down" on mountain biking as of late (and closed a lot of national parks to mountain bikers), a dedicated park is long overdue.

The development of South Australias first dedicated Mountain Bike Park is occurring within the site of an old quarry close to Eagle on the Hill and will provide a publicly accessible area in close proximity to Adelaide where people of all ages, fitness and skill levels can experience recreational and competition mountain bike riding on purpose built trails.

For more info on the park, click here.

The draft management plan is out; basically this is the oportunity for it to either go ahead, or go under. As with the car scene, there are a lot of people that want to "take us down". They just don't understand that a 1m wide trail is a 1m wide piece of cleared land, whether it be used by walkers, mountain bikers, horses, etc, and if the old Eagle Quarry wasn't converted to this MTB park, it would still just be a quarry - NOT revegetated land with some dirt trails through it. As a result, we need all of the support that we can get.

Long story short, if you are a mountain biker, you know of mountain bikers, you ever think you will be a mountain biker, or you just want to "help the cause" (hey, I always vote yes for "roadie" cycling events, skate parks, etc :( ), please give us a hand...

Well, Eagle feedback will close in 2 days now. (4pm Friday). For those slackers who haven't filled it out yet, attached is a form that has been filled out for you. Download it, fill out your name make any changes that you want and email it to:

[email protected]

For the government website, http://www.recsport.sa.gov.au/about-us/news.html

So there's no excuse, download it. Email it to all you slack mates. This is our last chance to help shape the park, if you don't chuck you're 2 cents in you can't whinge when it isn't what you want!

Please email it to as many people as you can. Lets get the numbers in before 4pm Friday.

Thanks

Travis

(PS. Thanks to another rider for doing up the form for me).

Thanks for your time. :(

Click here for the Eagle feedback template form.

Link to comment
https://www.sau.com.au/forums/topic/130615-calling-all-mountain-bikers/
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

    • My understanding is that UV tends to accelerate the aging process. If the car has been garaged, then you could probably get away with extending beyond 10 years. FWIW, in 2015, I had tyres on my 180B SSS that had a 3-digit code (2 for week, 1 for decade), ending in 0, so could have been more than 30 years old, but still worked fine. I did replaced them very quickly, though, once I discovered what the code meant!
    • But we haven't even gotten to the point of talking about stateless controllers or any of the good stuff yet!
    • You guys need to take this discussion to another thread if you want to continue it, most of the last 2 pages has nothing to do with OP's questions and situation
    • And this, is just ONE major issue for closed loop control, particularly using PID. One such issue that is created right here, is integrator wind up. But you know GTSBoy, "it's just a simple PID controller"...  
    • 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.  
×
×
  • Create New...