Jump to content
SAU Community

Recommended Posts

If u wanted to know stuff abt the car

No car has quite the same reputation as Nissan's Skyline GT-R. It's not officially sold in the United States, barely qualifies as compact, and is built with its steering wheel on the wrong side, but the all-wheel-drive, sequentially twin-turbocharged Skyline GT-R has managed to become a legend in America. That the producers of "2 Fast 2 Furious" ("2F2F") recognized that is at least somewhat encouraging--isn't it?

The Skylines used during filming were all R34s, a model introduced way back in 1998. Like other Skylines, the R34 is powered by a RB26DETT 2.6-liter, DOHC, 24-valve straight six sitting longitudinally in the engine bay that's force fed by twin turbos and rated at a laughingly low 280 hp. The R34's engine feeds a six-speed Getrag gearbox that in turn sends power to the ATTESA all-wheel-drive system, which electronically varies the torque split.

Super HICAS four-wheel steering is also aboard and includes an electronic feedback control system to ensure precise wheel positioning under extreme circumstances. But the big change for the R34 from previous Skylines was a stiffened body shell and fresh aerodynamic design. This car has carbon-fiber under-car diffusers and a new rear wing.

In fact, the Skyline R34 is such an effective piece of technology, it was too good for movie work. All-wheel-drive supercars are quick and amazing to drive, but they're absolutely nonchalant about their work. It takes a rear-quarter hit by an out-of-control country squire to get an R34's tail to swing out dramatically, and burnouts are tough in a car with more traction than a Caterpillar D9. So the 2F2F transportation department excised the front driveshaft and disabled the Skyline's four-wheel steering so it could misbehave like a regular car.

For its appearance on camera, the Skyline was encrusted within a C-West body kit, drenched in House of Kolor's platinum pearl paint and treated to a set of 19-inch HRE 446 polished wheels inside Toyo Proxes T1-S tires. Inside, the front passenger seat was ditched in favor of not one, not two, but three nitrous bottles--none of which are actually plumbed into the engine. Also thrown in is a Clarion head unit with LCD TV screen, a big JBL amp and Infinity speakers that actually seem to work. Of course, it also carries a bunch of blue neon and spits blue flame from its exhaust system.

As one of the two cars driven by too-pretty-for-a-guy hero Officer Brian O'Conner (Paul Walker), the Skyline, according to transportation coordinator Ted Moser, has 505 hp on tap and a hoarking 444 lb-ft of torque. In that "2F2F" alternate universe, that means this car rockets to 60 mph in just 4.1 seconds, consumes the quarter-mile in 12.1 seconds and has a top speed of 180 mph. Back on the actual planet Earth, the performance is still strong, but not quite as strong as fresher, intact R34s we've driven.

With Josh Jacquot doing his suave Paul Walker imitation, the Skyline, which is bone stock under the hood, groped its way through the quarter in 14.1 seconds at 101 mph--the third quickest car of the six included in this movie car test. With 22,254 km (13,797 miles) on its odometer, this car wasn't old, but it definitely had been beaten up pretty determinedly. Power output seemed down from other R34s, but a direct comparison is tough since the other R34s had the advantage of all-wheel-drive launches and didn't need a feathery throttle down the track. This car literally smoked its rear tires on every 1-2 upshift, which was cool to watch but certainly added time to each run. Its performance is also sabotaged by its big diameter wheels and the added heft of all the add-ons. The last stock R34 we drove hit 60 mph in just 5.07 seconds and crushed the quarter mile in 13.3 seconds at 103.7 mph.

The lack of AWD and 4WS knocked the movie Skyline's performance to 0.91g on the skidpad, although we expected worse. The missing front differentials made the car much easier to drift, which is of course, the point, and we have to admit the car looked great doing it.

As for the brakes, they remain stock all around, and the ABS is intact. From 60 mph, this car stopped in 127 ft. Again, not a terrible performance, but not exactly what we've come to expect from a Skyline GT-R.

Overall, the Skyline turned out to be one of the better running and better sorted of the six cars. The driver's seat is a Sparco Milano and the additional gauges are HKS products."It's not too bad," Josh reported after his quarter-mile runs. "Now we know how a rear-wheel-drive R34 performs."

2 Fast 2 Furious" Brian O'conner

1999 Nissan Skyline GT-R R34EngineEngine Code: RB26DETTType : In-line six, iron block, aluminum head, twin turbocharged and intercooledInternal Modifications: NoneExternal Modifications: K&N Ram Air system, HKS Titanium Exhaust, Turbonetic IntercoolerEngine Management Mods: NoneDrivetrainLayout: Front engine, all-wheel driveDrivetrain Modifications: Front driveshaft removed, Super HICAS disabledSuspension Front: JIC Magic shocks, Goldline springsRear : JIC Magic shocks, Goldline springsBrakesFront: Stop Tech brakesRear : Stop Tech brakesExteriorWheels: HRE 446Tires: Toyo 275/30ZR-19 (F/R) Performance AccelerationQuarter Mile Time: 14.1 sec.Quarter Mile Speed: 101.0 mph0-30 mph: 2.6 sec.0-60 mph: 6.0 sec.30-50 mph: 2.1 sec.50-70 mph: 2.9 sec.Handling Lateral Grip (200-ft skidpad): 0.91 gBraking60-0 stopping distance: 127 ft.Interior: Sparco harnesses, MOMO steering wheel, Clarion head unit with LCD TV screen, JBL amp, Infinity speakers

Link to comment
https://www.sau.com.au/forums/topic/200650-2f2f-skyline-r34/
Share on other sites

No car has quite the same reputation as Nissan's Skyline GT-R. It's not officially sold in the United States, barely qualifies as compact, and is built with its steering wheel on the wrong side,

As one of the two cars driven by too-pretty-for-a-guy hero Officer Brian O'Conner (Paul Walker),

:D:D huh? sounds like something a Frenchman would say...are you French? :)

The only good Fast and Furious was the original movie. 2F2F wasnt even about cars and Tokyo Drift was the lamest love story with a mix of Yakooza bullsh|t!

No way Fast and Furious sucked hard 2 Fast 2 Furious was the best, and Tokyo Drift is totally different from the 2nd one but i love the R34 :banana: from the movie.

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

    • 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.
    • 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. 
×
×
  • Create New...