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

erikgross · 05-16-2008, 08:23 PM

Quote:

Originally Posted by GTO NEMESIS

Nice to know in advance that I could have issues!

There's no "could" about it

It's "will". It's completely busted for Karman mode at anything above 1000Hz. It's not perfect under 1000Hz, either. Seriously, don't use it until a fix is released. You'll only be chasing your tail. Look at my logs - the green line is the Neo output, and it's seriously screwed up. Not tryiing to be a jerk - just want to save you some frustration.

maTT · 05-16-2008, 08:39 PM

Quote:

any one wanna buy my neo? ill give you a good price

Yours was the first one we tuned and I think the only one that didn't have us pulling our hair out. OMG I've wasted so much time fucking with those things. Replaced dyno widebands thinking something was wrong etc... I finally stopped selling them to people about 8 months ago.

THANKS ERIK GROSS!!!!!

3KGT2NV · 05-16-2008, 08:43 PM

sweet that will double the price I have the only neo that works!!! let the bidding start.

I have noticed some wacky behavior with it but nothing drastic enough where It wouldnt stay at what I have it set at. Mainly just slight fluctuations as the temp changes and gets hoter in new york. But I am going EMS so it doesnt matter anymore for me.

91vr4n00maxima · 05-16-2008, 08:51 PM

Quote:

Originally Posted by 3KGT2NV

any one wanna buy my neo? ill give you a good price

100 shipped?

oddly enough i had no problems keeping a good tune with mine. 12.2-12.4 at WOT and 17 psi.

though now i think it was the afc and not the 99 ecu that was causing issues in ciancis car.

ray pampena · 05-17-2008, 08:02 AM

ive been telling you guys this for a loooong time. no one listens lol

q2418130103p · 05-17-2008, 10:10 AM

I assume that firmware version 1.103 is the latest, meaning every Neo made has the problem.

Or is the issue non existant in newer revisions?

erikgross · 05-17-2008, 12:38 PM

Quote:

Originally Posted by q2418130103p

I assume that firmware version 1.103 is the latest, meaning every Neo made has the problem.

Or is the issue non existant in newer revisions?

I've personally tested it with version 1.020 and 1.100. From what they've told me, v1.103 is the latest that they had in their US office as of early April. By firmware numbering conventions, v1.103 should not have major changes from v1.100. Since they've reproduced the problem in Japan at this point, I believe that the problem exists on 1.103, or whatever latest version they have overseas (if greater than v1.103). I have not personally tested it on anything greater than v1.100.

FYI, my Neo is now sitting on the desk of one of the guys at Apex Integration in Cali. All we need now is a new firmware revision and whatever equipment is needed to reflash it.

HYPERSONIC007 · 05-17-2008, 12:43 PM

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?

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

I had seen a ton of issues with them on 240's as well when they first came out. I chalked it up to installation/tuner error until I started seeing more and more issues popping up over here too! Glad to hear Apex is fixing the bug.

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?

If you have an AFC NEO you should wait until the fix is released and you can have your NEO flashed. If you have an AFC I/II you're fine.

HYPERSONIC007 · 05-17-2008, 01:25 PM

Yea, I wonder when they are going to offer a fix. This is terrible! I am currently a medical student with a limited time off this summer, and I had plans on getting this thing in. Now it seems like Im screwed! Anyone here have apexi tech contact information? I looked on thier website and found nothing....