Jump to content
SAU Community

Haltech E6K Or Nistune For A Rb20


Bsa
 Share

Recommended Posts

Therre was a ca/sr ecu that changed between sequential and batch, but considering the rb20 ecu only has 2 injector drivers it is batch only. No sure about ignition tho.

Pretty sure ignition is because you have 6 ignitors, if it was batch they would save money and use 2 or 3.

Link to comment
Share on other sites

  • Replies 63
  • Created
  • Last Reply

Top Posters In This Topic

Not enough memory I guess the extra timing calculations would require alot more code CPU used has limited outputs

Im actually a programmer and one of my job was writing software for old processors, namely the same cpu used in these early boards. The code for writing to 2 outputs vs 6 and doing sequential vs batch is basically identical, the cpu still runs fast enough to process that many events. I can't see the CPU being the limiting factor, would have been something else but f**ked if I know what.

Link to comment
Share on other sites

Funny enough I'm a programmer aswell yeah there wouldn't be a heap of extra code there is a bit of room available then again I've never worked on these chips they are probably faster than I give them credit for

Link to comment
Share on other sites

You guys dont have a clue.

You realise in going to the haltech you will be batch firing injectors and coils! The std ECU is fully sequential on both. It will do everything about 100times better than the haltech ever will.

http://www.fueltech....pdfs/HalE6K.pdf
8 injector drivers as standard equipment
There is a reason haltech doesn't support the earlier ECU's anymore is beacuse they are shit.
You dont think it has something to do with the fact that the e6k is near on 10 yrs old now and used old technology, how many companies do you know of that keep producing things for 10yr old hardware when there goal is to always develop newer technology? Edited by W0rp3D
Link to comment
Share on other sites

A bunch of programmers here haha.

Not a lot of additional code would be required to implement fully sequential injection/ignition. You basically just need slightly more sophisticated CAS decoder subroutine and cylinder counter and assign calculated outputs to different output ports based on that counter (using it as either input variable or index on inj/ign subroutine call). It's just one more routine and a couple of additional RAM values.

Those old CPU's are not very fast, but fast enough to handle engine management (some of early factory ECU's have hardware cap of 8000 rpm - been tested by Nistune developers, don't remember if RB20 is one of them). The only reason for not using fully sequential management I can think of is CPU may not have enough output ports.

Link to comment
Share on other sites

Multiplexing can be a bit tricky in real-time applications like engine management. Requires some cleverly arranged synchronization.

On the other hand, it depends on how exactly CAS/load-calc-output data flow is implemented.

By the way I'm pretty sure I've read somewhere that R32 RB26 uses fully sequential management.

Link to comment
Share on other sites

Neo motors use 16-bit processor, different family and higher performance. R34's use Mitsubishi 7700 processors, earlier Skyline ECUs use some kind of Motorola 8-bit clone manufactured by JECS, if I'm not mistaken.

EDIT: I mean I'm agreeing with you :) I'm just explaining why full seq. mode is easier for later ECUs

Edited by Legionnaire
Link to comment
Share on other sites

Neo motors use 16-bit processor, different family and higher performance. R34's use Mitsubishi 7700 processors, earlier Skyline ECUs use some kind of Motorola 8-bit clone manufactured by JECS, if I'm not mistaken.

Yep, much newer processor with more features.

Link to comment
Share on other sites

Not necessarily so. The CPU itself may be the same/similar, but its peripheral devices can be very different - it's an ECU architecture thing. E.g. RB26 ECU may incorporate multiplexing/decoding logic you were talking about.

Sure, it is all speculation only. The best way to do it is to open ECU case and take a look what's in there. And assembly code would be handy also.

But I seriously think they are all sequential, otherwise they would use crank sync trigger instead of CAS.

By the way 16-bit processors are seriously faster than 8-bit in this particular case because all AFM values and load calculations use 16-bit arithmetic.

Link to comment
Share on other sites

  • 4 weeks later...

Hey I was wondering what ecu would be better for my setup mods are

Td06h-20g 8cm housing

550 injectors

3 inch exhaust

35 mm turbosmart external wastegate 17 psi

Stainless high mount

32 gtr cooler

I know nistune will be cheaper but lets put price aside on this one

so which one did you go with?

Link to comment
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
 Share




  • Similar Content

  • Latest Posts

    • Opened up the cluster to inspect the gauge itself for signs of damage and it looks good. Got curious since that needle doesn't go back to a "neutral" position by itself (it stays in the same position when ignition is off. so I manually moved it to 1/2. Connected it back, turned on the ignition and the needle started moving up! Not sure what's up with that but before that the needle was way down below empty like fully south west. There's always a chance that the needle moved slightly the first time I tried and I didn't notice because of how slowly it moves and how far it was from the markings. I don't know if the current needle position is accurate so I'll fill it up and see where that brings it. I guess I'll try to adjust it manually if it doesn't get to F. Looks like the needle position is relative and not absolute? Thanks all for your help and patience!
    • You're confusing two different responders and more than one issue. The stock Neo ECU boost sensor is used by the ECU for protection purposes. It is essentially only an overboost sensor. It is not used for determining engine load for fuelling or ignition purposes. That task falls solely to the AFM. Any aftermarket ECU that either has an onboard MAP sensor or a plug in one, will use the MAP sensor as the primary load sensor. Or I should perhaps say "can", rather than "will", because some of them have the option of using other primary load sensors. That MAP sensor is not for the same function as the stock Neo boost sensor. The reason I recommended against a plug and play ECU is that they are intended to run a particular engine and usually in the car that the particular engine came in. So, if you have a transplanted engine in a different car, with some parts of the original missing (such as the boost sensor, for example) and therefore likely non-standardness of the loom and its insertion into the car's loom, then it is very likely that you will run into the same problems with needing to fix up wiring to make it work that you would with the stock ECU. And, if doing so for the stock ECU is enough of an obstacle that you start considering a standalone plugin as a solution, it should become clear that the plugin is quite possibly not the solution you'd hope it to be. It would just lead to more of the same type of problem solving work to get it going. In the above paragraph and in my earlier post, the lack of the boost sensor is not critical. It was just used as an example of something that we knew you did not have right, such that the stock ECU would not work. I took that as an indicator of a reasonable probability that there were other related problems hiding there.
    • I can think of two places in my city of <1.5million population that specialise in automotive instrument repairs.Unless you're out in the wilds of Quebec, you have 3 major Canadian and 3 major US cities within the same distance as the single nearest city to mine. Surely there is somewhere you could send it.
    • I never cared for twins but whenever these conversations came up, I always presumed the higher number represented a larger turbo. Learn something new everyday. 
    • Interesting, I've never seen a failure like that before but with the age of these cars and the general questionable-ness of all kinds of parts these days you can't rule anything out I suppose. Boost leak testing the boost control system would've revealed this though.
×
×
  • Create New...