New firmware for APv2 is pretty bad

[soul.survivor]

Since I've updated my v2 AP to the new firmware rev I've noticed a few things that make me uneasy. I am unable to find the previous firmware to roll back to.

1. System Error pops up often when flashing a new map on the first try. I am able to back out and try again. Second try has worked but how long until it doesn't?

2. AP decides it doesn't want to log at times. It initializes but displays -- for the PID being output to the screen and creates invalid log files with NA size. This makes me sad because wasted gas on WOT logging runs and wasted time.

When is the fixed firmware/ATR coming?

One other thing: If I were in charge of the update server I would stop it from trying to push out a non-working version of ATR and buggy firmware. I'd also check to see if anyone is running buggy firmware and downgrade them to the previous non-buggy version. That would be the responsible thing to do considering we're talking about people's engines/ECUs here and problems can be disastrous. My problems aren't engine-killing, ECU-bricking serious as of yet but with buggy software you never know.

[mzr0818]

Originally Posted by soul.survivor Since I've updated my v2 AP to the new firmware rev I've noticed a few things that make me uneasy. I am unable to find the previous firmware to roll back to. 1. System Error pops up often when flashing a new map on the first try. I am able to back out and try again. Second try has worked but how long until it doesn't? 2. AP decides it doesn't want to log at times. It initializes but displays -- for the PID being output to the screen and creates invalid log files with NA size. This makes me sad because wasted gas on WOT logging runs and wasted time. When is the fixed firmware/ATR coming?

+

I have had the logging problems as well. I have ended up taking 4-5 logs just to make sure I get 2 good logs.

[MonstaSpeed6]

I am also having logging issues where it states: logging "--". Then come to send data logs and it says file size NA. I have even rolled it back, but it still won't log, right at 3k.

I've found starting the log at 2800rpm or so allows it to log. Weird.

[mzr0818]

Originally Posted by MonstaSpeed6 I am also having logging issues where it states: logging "--". Then come to send data logs and it says file size NA. I have even rolled it back, but it still won't log, right at 3k. I've found starting the log at 2800rpm or so allows it to log. Weird.

I'll have to try this... I usually start right at 3k as well.

[Cevaes_64]

Get a V3

[soul.survivor]

Originally Posted by Cevaes_64 Get a V3

You gotta be joking. Even if I had a use for a v3, I just got this one in June. No way am I dropping another $325 on something I don't need that probably has worse issues than this one.

[Quigs]

I'm glad I read all these threads so I can make sure to not update until the problem is resolved haha.

Hope Cobb makes a fix soon.

[DVM17]

This is just their plan....... make the v2's glitch out randomly.... cause mass chaos and have those people order the v3......



lol I keed I keed

[xI Leveler Ix]

The V3 has more issues than the V2 has. I wont get one for at least another year, till all the bugs are fixed.

[Cevaes_64]

Get a v1 then lawl, I dont even own a v3 I have the v2

Sent from my SPH-L900 using Tapatalk 2

[cabrone]

super sweet. just started the install and it says "Do not disconnect" fml.

[Neubreed]

been seeing the same issues here aswell. any word on a fix. @Cobb Tuning;

[illegal shishkebab]

FFFFF, i just updated

[mzr0818]

Logging at 2800 worked for me on the log issue

[Dizzy Turbo]

I have all those issues. Just updated to newest firmware and resaved maps, now they are locked to my ap and cannot be flashed. @Cobb Tuning;

[rtabagaboy]

Originally Posted by Dizzy Turbo I have all those issues. Just updated to newest firmware and resaved maps, now they are locked to my ap and cannot be flashed. @Cobb Tuning;

This. I am trying to get my emissions tested today and I cannot flash my shit back to running 14.7 AFR. Pissing me off some ya know. I hope Cobb can fix this soon and reply in this thread. I can't flash anything new.

[soul.survivor]

Logging is working for me intermittently even starting at 3k. Still getting system error when I hit the button to start flashing. Also had an issue where it errored out after flashing - before clearing dtcs and went back to the main menu.

[Todd98SE]

Build a new non E85 map to get me through a few days until I can finish my stockout, in the process I updated AP and AccessTuner..............it wont let me flash any maps but the one i'm already running. Guess I'll have to take it very easy since I'm out of E85.

[Dizzy Turbo]

You have to re request atr and download it. I can at least save, edit, and flash maps now
@Todd98SE; @rtabagaboy;

[killer-ms3]

Ive experienced the log glitch too, I start around 2500-2600

[Lex]

Hey guys, post up the FW version so that everyone is kept in the look and prevents the update until it is resolved.