Apex AFC Neo: Confirmed Programming Bug - Karman Function Doesn't Work - Page 3 - 3000GT/Stealth International Message Center

Dark-Hawk · 05-17-2008, 01:45 PM

I would imagine they're trying to get a bugfix released pretty quickly; it's a rather major bug.

Mike94TT · 05-17-2008, 01:49 PM

Wow, no wonder when I was using the Neo I could never get it right, especially over 4,000 rpm. This would also explain why it would run into the 13's AFR randomly above 5k. At least I now know I'm not retarded. I've still got it in the car, except I just use it to take up space below my radio and watch my throttle position.

q2418130103p · 05-17-2008, 04:16 PM

Quote:

Originally Posted by HYPERSONIC007

this sucks, I didnt hear anything about this and I planned on installing a 13g with 450's in the next 2 weeks. What should I do?

Install the turbos (and possible even install in the injectors and just turn the base pressure down) and wait to install the neo until there is a solution.

q2418130103p · 05-17-2008, 04:18 PM

I find this whole thing to be very bizzare.... this device only serves one purpose and that is to modify airflow signals... if any of you produced this device wouldnt you have tested the output using a scope about a million times before sending it to the public....

especially when its a device that would damage an engine.....

erikgross · 05-17-2008, 05:23 PM

Quote:

Originally Posted by HYPERSONIC007

this sucks, I didnt hear anything about this and I planned on installing a 13g with 450's in the next 2 weeks. What should I do?

I have a similar set up right now. I have 450cc injectors and DR-500s. I'd either wait to install the 450s (and limit yourself to 10psi of boost for now) or plan to run reduced fuel pressure with the 450's until new firmware for the Neo is released.

erikgross · 05-17-2008, 05:33 PM

Quote:

Originally Posted by q2418130103p

I find this whole thing to be very bizzare.... this device only serves one purpose and that is to modify airflow signals... if any of you produced this device wouldnt you have tested the output using a scope about a million times before sending it to the public....

especially when its a device that would damage an engine.....

One would think....

However, there are other types of airflow sensors (hot wire, flapper, etc.) that don't use a frequency-based signal. It seems that those features work ok.

There's no question that someone in their verification team really dropped the ball on this one. The feature works well on the SAFCII, so it's not that they're not capable of making a quality device. That the problem was not obvious and required a frequency data logger to isolate made things even worse. I imagine they're pretty freaked out right now, and all indications are that they're pushing a fix through as fast as possible.

A couple of notes:
1) It probably won't do any good to flood the Apex USA office with e-mails at this point - they know about the problem and are trying to fix it. I doubt you'll get any faster results by bombarding them with questions. I will absolutely let everyone know when I have the updated version in my hands and have verified that it works.

2) For those looking to sell their Neos for one reason or another, please take that to the classifieds - I'd like to keep this thread reasonably useful for people trying to understand what's going on.

maTT · 05-17-2008, 10:09 PM

Quote:

Originally Posted by HYPERSONIC007
this sucks, I didnt hear anything about this and I planned on installing a 13g with 450's in the next 2 weeks. What should I do?

Pick up a used SAFCII and use that for the time being. Then sell it once the NEO is fixed. Or keep it and sell the NEO!

Kibwe Walker · 06-09-2008, 07:13 PM

Wonder what version I have, guess I am subscribed for when there is a reflash available.

erikgross · 06-09-2008, 07:20 PM

Quote:

Originally Posted by Kibwe Walker

Wonder what version I have, guess I am subscribed for when there is a reflash available.

The version number is listed in one of the menus - I don't have mine with me at the moment, but I think it's on the "etc." menu.

Regardless, all the versions currently in the field are busted - it doesn't matter which one you have right now. Once a fix is released, then it will matter which firmware you have.

UPDATE: latest word is they're getting pretty close to a fix. It seems reasonable to hope that a new firmware may be available by the end of the month. It's no fun waiting this long for a fix, but if they're taking some extra time to do some real validation of the device before sending it out, I'm all for that ;-)

3K94GT · 06-09-2008, 07:57 PM

subscribed for a reflash release date