Jump to content
SAU Community

Recommended Posts

HI everyone, 98 r33 gtr

First off when i got my car went on the net and found that u cut wire 52 i think it was it would remove the speed liminter, rite i did so and yes it worked untill i hit 240 well there abouts, so i joined the wires back up and later on i chipped the ecu and sure enough the limiter was raised to 240km/h again, you hit 6000rpm in 5th and the engine will just die and wont come back into life untill you raise your foot then put it down again. i thought fair enough i should stop being a cheap arse and just get a real ecu like a fc. But my mate has a r32 gtr and he just put in a mines ecu fully baged and sealed and his is doing the same thing has anyone got any ideas i have tried searching but cant find anything on this?

Link to comment
https://www.sau.com.au/forums/topic/220905-speed-cut-at-240kmh/
Share on other sites

yes well the one i chipped was a mines copy they claimed and was meant to remove it, but my mates was the real deal and the also claim to remove it, and for it to happin to both of us just wondering whats the g o

i dont think they can just edit the binary code and remove it, they can only probably set it to the max ceiling limit which would be like 240 or 255

it will be a short integer or something along those lines. as they can't just edit the binary code to say don't execute this part, they just edit the values it looks at, in this case they change it from 180 to the max it will support, so 240/250 sounds about right. a stand alone wont have a speed limit at all, but if you've cut the speed signal wire, then the stock ecu has no idea reference how fast the car is moving

i dont think they can just edit the binary code and remove it, they can only probably set it to the max ceiling limit which would be like 240 or 255

it will be a short integer or something along those lines. as they can't just edit the binary code to say don't execute this part, they just edit the values it looks at, in this case they change it from 180 to the max it will support, so 240/250 sounds about right. a stand alone wont have a speed limit at all, but if you've cut the speed signal wire, then the stock ecu has no idea reference how fast the car is moving

The value that the speed lifiter can be raised to is 512km/h

The value that the speed lifiter can be raised to is 512km/h

haha yeh i dont think im quite going to hit that limit, but the thing is its not like the speed limiter not the usual barb barb barb it just dies like a total ignition cut untill you take you foot off and the put it bak on again, i also reconected wire 52 and im sure other ppl out there have the same problem and go faster than 240 well i hope or its just our cars dont like us lol

oh and another point is that my mates speedo cable snaped a few weeks bak and it made no differance still did it, so it has to be a rev/gear thing that the computer is reading because with out the speedo cable there is no way it can tell the speed unless its something to do with the rpm and gear because like i said with out fail 7000rpm in 4th or 6000rmp in 5th same spot every time.

oh and another point is that my mates speedo cable snaped a few weeks bak and it made no differance still did it, so it has to be a rev/gear thing that the computer is reading because with out the speedo cable there is no way it can tell the speed unless its something to do with the rpm and gear because like i said with out fail 7000rpm in 4th or 6000rmp in 5th same spot every time.

mine does this too, and its not speed limiter as the speed sensor is rooted in the dash so it cant loop back too the ecu

oh and another point is that my mates speedo cable snaped a few weeks bak and it made no differance still did it, so it has to be a rev/gear thing that the computer is reading because with out the speedo cable there is no way it can tell the speed unless its something to do with the rpm and gear because like i said with out fail 7000rpm in 4th or 6000rmp in 5th same spot every time.

Speedo cable is meaningless. The ECU takes the speed from the ABS wheel speed sensors. The actual wire that feeds into the ECU is a mean average of the wheel speed sensors from some type of aggregate box (HICAS?) though.

Speedo cable is meaningless. The ECU takes the speed from the ABS wheel speed sensors. The actual wire that feeds into the ECU is a mean average of the wheel speed sensors from some type of aggregate box (HICAS?) though.

the speed sensor on the dash sends a speed signal to the

HICAS

power steer

ECU

isn't that right?

Yeh i have hurd that and something about cutting some circut track on the dash cluster but if it affects the hicas which is usless but its the power steering that might go funny because i think its progressive faster you go the hard it is or something

the speed sensor on the dash sends a speed signal to the

HICAS

power steer

ECU

isn't that right?

I didn't think so. I figured the hall effect setup on each wheel was used to feed the ECU, HICAS, ATESSA etc, but would be awesome to actually know concretely.

I didn't think so. I figured the hall effect setup on each wheel was used to feed the ECU, HICAS, ATESSA etc, but would be awesome to actually know concretely.

without the speed sensor on my dash the following happens;

speedometer works (its cable driven)

HICAS failed - so dicked it off

Power steering is locked into high speed mode, it actually starts the car in low speed and then kicks over after about 30 seconds or so.

ECU cannot detect speed signal to feed to consult

ALTESSA works

ABS works

not sure what happens with the sensor in as i am having problems finding one for an early model GTR r32

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