Strange AP screen flashes, knock of 7, and other fun topics!

[writhen]

Background:

Bought AP summer 2010 and ran ots map, intake, race pipe and bpv for a couple days. I met Jmkc on here, straight up guy (not bashing him in this post at all, just need help), he offered to set me up with a map if I sent him logs. I don't know anything about tuning, so I came on here and found someone who could help.

This was last September, way before the current beta releases of APM and ATR. Map worked great, AP logged great, used DH as daily logger.


About 10 months later:
I hadn't updated APM or ATR since Sept due to moving and changing computers. Kept logging, but not updating firmware. All logs showed little to no knock.

2 days ago, I update to latest beta fw for both APM (1.6.4.2-2183) and ATR (1.8.6.0-2212 June 30 release) **NOT 1.8.6.0-2213 as stated in June 29 update on APM. All updates go smoothly.

I then go log my current "old" map one last time to send to Jmkc, open it up on my computer and see some weird ass stuff (See datalog18). Jmkc sends me a new map with updated tables to see if it solves the issue, I flash the map and log it (see datalog3).

The second I flash new map AP starts flashing like crazy (see linked video), showing me crazy knock numbers, but when I recheck with DH, no "knk retard". So I think hmm...maybe it's my 64 bit computer (even though cobb says 64 bit is A ok).

Reinstalled APM/ATR on 32bit laptop, synched ap, deleted new map, and reflashed old map that was working for 10 months. The flash goes fine, but AP screen still flashes like crazy and now the map that worked for 10 months ALSO shows exact same values of knock as the "new" map flash.

Going to try the "new" updated table map one more time, loaded onto AP off my 32 bit computer. After that I'm out of ideas.

Funny thing is AP only flashes when I go to monitor/log. Otherwise it works just like normal. DH also shows no knock, no idea why AP is.. Knock values constantly stay at 0, 1.4, 5.6, or 7 on AP, feels like something is definitely wrong with the device, except that it functions normally in all other situations (ecu connecting, computer connecting, flashing, etc)

PS: The power mods in my sig are lying in my living room. Got a little excited for the install coming up next month, guess it might not be happening now though. Currently car has all safety mods and intake/inlet, racepipe/catback, bpv.

I know the vid is shitty, best I could do since its dark here already.

‪video 2011 07 14 21 22 16‬‏ - YouTube

‪video 2011 07 14 21 22 16‬‏ - YouTube

[IMASA]

Did you resave your old map in the new ATR before you reflashed it? You have to do this after upgrading to the new ATR with faster datalogging and upgrading the AP firmware or else you'll get this problem.

[pearl_ms3]

ur post is so long i dont want to read it all. u missed a step on the new firmwire.
step 1 update to beta firmwire on the ap
step 2 update to beta firmwire on the ATR
step 3 open map in ATR and then save again. then reload to ap.

[writhen]

Didnt do it the first time, did it just now and glitch fixed I think. Thanks, i know the post was long anand annoying lol. Couldnt find anything when i searched.

[pearl_ms3]

only reason i knew is cuz it happened when we updated my buddies today. he didnt click check for beta updates on atr.

[JmkC]

That is a really long post

[2011speed]

I had similar issue when I used an old map on new firmware

[writhen]

Originally Posted by JmkC That is a really long post

Lol didn't know how long it was till I posted it. Pretty gigantic I'll admit.

Originally Posted by pearl_ms3 only reason i knew is cuz it happened when we updated my buddies today. he didnt click check for beta updates on atr.

Funny, I did that the first time. I guess the key is updating your old maps with new atr before loading any new maps.