Jump to content
SAU Community

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.

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

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

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

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.

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.

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

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.

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.

  • 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?

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

    • Forgot to include this but this is the mid section of my steering rack that looks like it has a thread/can be turned with that notch mentioned in the post:
    • Hey everyone, Wanted to pick some brains about this issue I'm having with rebuilding my 33 rack (PN is 49001-19U05). All of the tutorials/videos I've seen online are either R34 or S Chassis racks which seem to be pretty straightforward to disassemble but this process doesnt carry over to my rack. Few of the key differences that I've noted The pinion shaft on the other racks bolt on with 3 torx bolts: Whereas my rack bolts on with 2 allen head bolts: These changes are pretty inconsequential but the main difference is how you pull the actual rack out of the housing. The other skyline/s chassis racks can be taken out by tapping the rack out of the body with a socket and it just slides right out. I'm unable to do that with my rack because there's a hard stop at the end that doesn't let the seal/shaft be tapped out. Can also see a difference in the other end of the rack where mine has a notch that looks like you're able to use a big wrench to unthread 2 halves of the rack whereas the other racks are just kinda set in with a punch. My rack: Other racks: TLDR; Wanted to know if anyone has rebuilt this specific model of steering rack for the R33 and if there were any steps to getting it done easier or if I should just give this to a professional to get done. Sorry if this post is a bit messy, first one I've done.
    • I would just put EBC back on the "I would not use their stuff" pile and move on.
    • Can I suggest you try EBC directly again and link them to as many competitor catalogues as you can to show their listing is incorrect, eg https://dba.com.au/product/front-4000-series-hd-brake-rotor-dba42304/ If you have access to an R33 GTST VIN and your VIN, you could also use a Nissan Parts lookup like Amayama to show them the part number is different between 33 GTST and 34 GTT which may get their attention
    • So i got reply from EBC and they just this site where you can clearly see those 296mm fronts on R34 GTT. I send them photos and "quotes" that 296mm are not for 34 GTT and they are too small. But it will be very hard to return them cuz nobody here knows 100% and they just copy those EBC catalogue :-D https://ebcbrakesdirect.com/automotive/nissan/skyline-r34
×
×
  • Create New...