Jump to content
SAU Community

20/12/08 Willowbank Pre-test N Tune Session - 3 Hours


Recommended Posts

as said ive already pulled out due to other commitments, but maybe send PM's to every1 on on the list stating time needed to pay for this event incase they havent checked in events section. so somebody can fill my spot and i can be taken off the list please.

  • Replies 219
  • Created
  • Last Reply

Top Posters In This Topic

PLEASE PLEASE PLEASE use your FORUM NAME NOT your real name as reference, doesn't matter if you don't put drags after it, I can work it out from the amount paid, just PLEASE USE YOUR FORUM name, it is very difficult to work out who is who, and i'd hate to see someone miss out :(

Cheers, Anna :teehee:

All paid up. see you guys there!

Your/Business name: coaster david

Payment details

To Payee: coaster drag rego

Account BSB: 804050

Account Number: 30701728

Account Name: SKYLINES AUSTRALIA BANK ACC

Message/Reference: coaster drag rego

Amount: $48.00

updated list

1) Bunta - PAID

2) Wagamama - PAID

3) toddlls - PAID

4) Pear - PAID

5) DAS KAMU - PAID

6) and3_3

7) Shanef

8) Jayson

9) Fine Line

10) NA R33

11) Socko

12) Rhinorebel - PAID

13) Blitz_R33

14) Blitz_R33 (friend)

15) Strik3r

16) Lazy-Bastard

17) ToMMaH (MAYBE)

18) DiRTgarage (MAYBE)

19) trust33

20) 116.hks (MAYBE)

21) Col-GTSX PAID

22) si_ (MAYBE)

23) 85URK

24) 9krpm (MAYBE)

25) spilmer

26) Eug (MAYBE)

27) Hell Fire (MAYBE)

28) jase-r34 PAID

29) impact_blue - PAID

30) 2BNVS

31) wrxkilla (MAYBE)

32) TJ_R33 (MAYBE)

33) spoolup

34) slapper

35) coaster

36) SRB

37) Scadtional (MAYBE)

38) silver R33

39) jason

40) POQ123 PAID

Updated paid- 2 spots available

1) Bunta - PAID

2) Wagamama - PAID

3) toddlls - PAID

4) Pear - PAID

5) DAS KAMU - PAID

6) and3_3

7) Shanef

8) Jayson

9) Fine Line

10) NA R33

11) Socko

12) Rhinorebel - PAID

13) Blitz_R33

14) Blitz_R33 (friend)

15) Strik3r

16) Lazy-Bastard - PAID

17) ToMMaH (MAYBE)

18) DiRTgarage (MAYBE)

19) trust33

20)

21) Col-GTSX PAID

22) si_ (MAYBE)

23)

24) 9krpm (MAYBE)

25) spilmer - PAID

26) Eug (MAYBE)

27) Hell Fire - PAID

28) jase-r34 PAID

29) impact_blue - PAID

30) 2BNVS

31) wrxkilla - PAID

32) TJ_R33 (MAYBE)

33) spoolup

34) slapper

35) coaster-awaiting conf.

36) SRB

37) Scadtional (MAYBE)

38) silver R33

39) jason

40) POQ123 PAID

So hows it all looking? still looks to be alot unpaid. whats the deal if we dont get the numbers?

I may be able to get a few mates interested if we need and it means it gets the day to go ahead.

So hows it all looking? still looks to be alot unpaid. whats the deal if we dont get the numbers?

I may be able to get a few mates interested if we need and it means it gets the day to go ahead.

by all means mate get every one you can!

To any who have friends interested in attending this Drag day TestNTune pls feel free to ask them.

We will need to open this up to other clubs soon to fill the spots and aid the day in its go-ahead

It's a bit disappointing that we can't get the numbers we need guys. Seems theres a lot of people who won't put their money where their mouth is! :banana: lol

I just hope it goes ahead! I'm really looking forward to it!!

Yeah me too guys. I havent had mine on the strip and even tho it looks like i may end up running street tyres im still really keen.

I work at a servo for the next week so im hitting up anybody with a decent nissan that comes thru. Bad form on those who wont pay up!

I use a full face helmet,

The rule is Helmets must comply with Australian Standards

Helmets must show no sign of damage or scratches indicating an impact of any sort-if it does you will not be using that helmet

Seems theres a lot of people who won't put their money where their mouth is! :P lol

I'm sure they all have a note from their mum, or a lame arsed excuse about something being wrong with their car.....

:P

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