Welcome to the SR20 Community Forum - The Dash.
Register
SR20 forum logo

Thread: NEMU RealTime Boards

+ Reply To Thread
Posts: 111-120 of 176
2011-09-30 14:50:01
#111
Yes!
2011-09-30 16:58:55
#112
Want one.. What will be the introduction price for the package?
2011-09-30 19:40:43
#113
Goodness gracious, I got a good feeling it will be soon!!!!
2011-09-30 21:06:49
#114
will your boards be compatable with the vz-r 16ve ecu's?

... --- ...
2011-09-30 21:10:03
#115
Originally Posted by b12sr20ve
what if I have a 16ve ecu?


Originally Posted by dfddfd2
What part number?


Originally Posted by Cozzm0_AU
2N500 is the 16VE ecu, same deal (hardware wise) as the SR20VE ECU 5J000, no go. Unless you've been working on this quietly ?

Only option currently (and probably going to stay that way) for the VE ECU's is the Japanese daughterboards.


Originally Posted by dfddfd2
No, not yet anyway.


Originally Posted by happyharrysco1
will your boards be compatable with the vz-r 16ve ecu's?

... --- ...


Already covered... not yet, and i wouldn't expect it swiftly.
2011-10-01 07:54:22
#116
what is the problem with supporting these ecu's? hardware incompatability? or software? as their not obd2, I really want support for it and the jap daughterboard that tunes and runs on the knock maps isn't the best solution imo :/

... --- ...
2011-10-01 08:59:45
#117
Its hardware, they are a totally different ecu, totally different connection where the daughter board goes on the ecu, 64k file instead of 32k.

There are so many items in the bin file with it being so large, we have only scratched the surface and found the fuel/ig maps, and basic tuning info such as vvl, maf k value etc.

There is more than enough there to be able to make these daughter boards and ecu's run well, even turbo.

I have never had any issues with a car or engine not being able to run the knock control.
2011-10-01 09:22:27
#118
Originally Posted by happyharrysco1
what is the problem with supporting these ecu's? hardware incompatability? or software? as their not obd2, I really want support for it and the jap daughterboard that tunes and runs on the knock maps isn't the best solution imo :/

... --- ...


Tunercode doesn't have primary and knock maps, it has one map only and no knock control, so there's really not a big change there. << THIS INFORMATION IS INCORRECT, PLEASE IGNORE

As Evlnxr stated, there are vast physical hardware changes, that while with a bit of time spent on it a solution could be found. One issue is that its a far far far smaller market that offers very little extra/unique functionality compared with a DE ECU with tunercode/NEMU realtime board.
Last edited by Cozzm0_AU on 2011-10-01 at 21-26-57. Reason: i was corrected by Dave, felt it necessary to not remove my comment, but highlight the error
2011-10-01 09:25:30
#119
thanks for the info guys, and it sounds like tunercode/nemu isn't the solution for me either, obviously you guys never have problems with bad fuel if you have no fears of running without knock protection?

... --- ...
2011-10-01 09:29:44
#120
Originally Posted by happyharrysco1
thanks for the info guys, and it sounds like tunercode/nemu isn't the solution for me either, obviously you guys never have problems with bad fuel if you have no fears of running without knock protection?

... --- ...


Bad fuel isn't an issue here, but at the same time, if your tune is that close to the edge of knock, i wouldn't be relying on the OEM knock control system as it isn't fool proof (from both false positives and false negatives) and isn't really used at high throttle levels and high rpm as there is just far too much mechanical noise to distinguish knock.

As we all know, knock at high load will be very dangerous and likely do damage anyways, which would usually be outside of the knock flagged area.
+ Reply To Thread
  • [Type to search users.]
  • Quick Reply
    Thread Information
    There are currently ? users browsing this thread. (? members & ? guests)
    StubUserName

    Back to top