Jump to content
SAU Community

Recommended Posts

  • Replies 48
  • Created
  • Last Reply

Top Posters In This Topic

practice and race engines were the same spec, the race engine would be a fresh one for the 1000km race, vs Brock's well used practice engine... I doubt that was a disadvantage for Perkins! In fact Perkins top speed on Conrod was 277.9, Brocky 277.8 so how can you suggest Brock made up all his time down Conrod???

split time at Forest Elbow was a 1:30 for Brock and they originally said 30.9 for Perkins, but there was some confusion over it and they changed their minds to a 30 as well, probably because they were so convinced his smoother lap was going to be faster as they had been saying all the way through it. Maybe they just didn't want to be proven wrong on national television...

Meh, i dont know. They said LP was the quickest to Forrest Elbow, and i dont know any different...but i do expect that a race engine to be down in power and/or not rev'd as hard as a practice-quali engine. From memory the V8s in Grp A trim had a higher rev limit, higher compression ratio limit and more cam freedoms then they later enjoyed when they moved to the control formula?!?!? (Based on memory only)

I think you need to listen to it again. all that stuff in my previous post is what the commentators said. I didn't just make it up. eg:

commentators about Brock's split time: "fastest time at forest elbow, one minute thirty"

commentators about Perkins split time, after talking him up for the whole lap about how smooth he was and that's why he's going to be faster than Brocky's ragged lap: "split time to the elbow was a thirty point nine, so...<insert pregnant pause>... No a thirty! So quickest so far"

and what do you know, after doing identical speeds down Conrod (277.9 vs 277.8kph), Brock was 0.9 up at the finish line. I think the original 30.9 split for Perkins was correct, the commentators just couldn't accept it...

the identical terminal speeds say more about the equivalence of their engines than any theorising about which may have had more power...

Edited by hrd-hr30
I think you need to listen to it again. all that stuff in my previous post is what the commentators said. I didn't just make it up. eg:

commentators about Brock's split time: "fastest time at forest elbow, one minute thirty"

commentators about Perkins split time, after talking him up for the whole lap about how smooth he was and that's why he's going to be faster than Brocky's ragged lap: "split time to the elbow was a thirty point nine, so...<insert pregnant pause>... No a thirty! So quickest so far"

and what do you know, after doing identical speeds down Conrod (277.9 vs 277.8kph), Brock was 0.9 up at the finish line. I think the original 30.9 split for Perkins was correct, the commentators just couldn't accept it...

the identical terminal speeds say more about the equivalence of their engines than any theorising about which may have had more power...

Terminal speed accounts for nothing.

Its the highest average speed that results in better lap times. Just because they had near identical terminal speeds ignores which car was travelling fastest down Conrod for the longest. At higher speeds it takes a exponentional amount of hp to punch a hole through the air. Those cars could have been within 20hp of each other and still ended up with near identical terminal speeds because or wind resistence, gearing, etc.

Edited by juggernaut1

ffs, the cars are as near as is possible to being identical! same weight, same gearing, same wind resistance, same engine specs. they're both built to the same set of rules, by the same team!

are you suggesting that if one of those identical engines had 20bhp more, that's enough to accellerate an identically 1250kg Commodore fast enough to make up 0.9 of a second in the 19 seconds it takes to run down conrod alone???

I'm suggesting that identical terminal speeds and peak hp means nothing as to which car will produce faster lap times or a faster sector time even if the cars are "identical".

But your right.....your comment that "the commentators just couldn't accept it" sounds much more plausable. :cool:

Edited by juggernaut1

Have I got this right for how to corner?

Come up to the corner.

Brake in a straight line.

Clutch out.

Blip throttle.

Stop braking.

Clutch in and engage lower gear.

Should now be at corner turn in.

Turn wheel. :)

Flat on throttle until apex.

Slowly give it some gas and floor it on exit.

Rinse and repeat?

You shouldn't stop braking that early. If you're trail braking, you won't stop braking until you're practically at the apex.

Even if you're not trail braking, you should be braking during that gearchange (assuming its necessary). I'd swap the "engage lower gear" and "stop braking" points around.

Have I got this right for how to corner?

Come up to the corner.

Brake in a straight line.

Clutch out.

Blip throttle.

Stop braking.

Clutch in and engage lower gear.

Should now be at corner turn in.

Turn wheel. :D

Flat on throttle until apex.

Slowly give it some gas and floor it on exit.

Rinse and repeat?

Sequence is roughly like this.

At the start of the braking zone. Smash foot onto the brakes ie brake hard as you can without lockup early in the stop.

If you need to heel/toe down change do it as early as the road speed allows (ie don't buzz the motor) with the idea of being in the gear you need on corner exit before you turn in. You are still braking as hard as you can at this point.

Ease off the brakes as you turn the car in carrying a little brake pressure to the apex to keep the nose interested. (Mostly for GTR's as they are understeering cops)

Get on the gas as soon as you can and always bear in mind once on it it stay on it - don't stab at it. On some circuit set ups this may even happen before the apex of the corner.

The best advice is buy a book on track driving techniques that includes an explanation of tyre behaviour and chassis behaviour. There is a lot more to it than can be explained in one post let alone one chapter of a book.

Try amazon & pitstop for the books.

Edited by djr81

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

    • How complicated is PID boost control? To me it really doesn't seem that difficult. I'm not disputing the core assertion (specialization can be better than general purpose solutions), I'm just saying we're 30+ years removed from the days when transistor budgets were in the thousands and we had to hem and haw about whether there's enough ECC DRAM or enough clock cycles or the interrupt handler can respond fast enough to handle another task. I really struggle to see how a Greddy Profec or an HKS EVC7 or whatever else is somehow a far superior solution to what you get in a Haltech Nexus/Elite ECU. I don't see OEMs spending time on dedicated boost control modules in any car I've ever touched. Is there value to separating out a motor controller or engine controller vs an infotainment module? Of course, those are two completely different tasks with highly divergent requirements. The reason why I cite data sheets, service manuals, etc is because as you have clearly suggested I don't know what I'm doing, can't learn how to do anything correctly, and have never actually done anything myself. So when I do offer advice to people I like to use sources that are not just based off of taking my word for it and can be independently verified by others so it's not just my misinterpretation of a primary source.
    • That's awesome, well done! Love all these older Datsun / Nissans so rare now
    • As I said, there's trade offs to jamming EVERYTHING in. Timing, resources etc, being the huge ones. Calling out the factory ECU has nothing to do with it, as it doesn't do any form of fancy boost control. It's all open loop boost control. You mention the Haltech Nexus, that's effectively two separate devices jammed into one box. What you quote about it, is proof for that. So now you've lost flexibility as a product too...   A product designed to do one thing really well, will always beat other products doing multiple things. Also, I wouldn't knock COTS stuff, you'd be surprised how many things are using it, that you're probably totally in love with As for the SpaceX comment that we're working directly with them, it's about the type of stuff we're doing. We're doing design work, and breaking world firsts. If you can't understand that I have real world hands on experience, including in very modern tech, and actually understand this stuff, then to avoid useless debates where you just won't accept fact and experience, from here on, it seems you'd be be happy I (and possibly anyone with knowledge really) not reply to your questions, or input, no matter how much help you could be given to help you, or let you learn. It seems you're happy reading your data sheets, factory service manuals, and only want people to reinforce your thoughts and points of view. 
    • I don't really understand because clearly it's possible. The factory ECU is running on like a 4 MHz 16-bit processor. Modern GDI ECUs have like 200 MHz superscalar cores with floating point units too. The Haltech Nexus has two 240 MHz CPU cores. The Elite 2500 is a single 80 MHz core. Surely 20x the compute means adding some PID boost control logic isn't that complicated. I'm not saying clock speed is everything, but the requirements to add boost control to a port injection 6 cylinder ECU are really not that difficult. More I/O, more interrupt handlers, more working memory, etc isn't that crazy to figure out. SpaceX if anything shows just how far you can get arguably doing things the "wrong" way, ie x86 COTS running C++ on Linux. That is about as far away from the "correct" architecture as it gets for a real time system, but it works anyways. 
    • Holy hell! That is absolutely stunning! Great work!!!
×
×
  • Create New...