Fan on, "Not Connected", 3 lights.
 

Hey guys, so I was street tuning the other day. Had the car on, tuner studio open, and connected. I hit the "undo" button on the AFR table. The car died. Tried to start it, no issue cranking, but it's not starting. When I turn the car to the "on" position, I get three red lights on the PNP (so would appear functional) but no connection to the laptop AND the fan is always on.

Since I can't communicate with the PNP am I SOL? I tried two different connectors and neither got any connection from the PNP, but they both work on my other microcontrollers.

edit: using a Mac. And I had to use the stock ECU to bring the car home, so I don't think it's an issue with the engine or related components.

its possible the firmware got corrupted? this an old MS1 PNP? try to reflash the firmware, and reload your tune.

edit: okay the tool doesn't mention it, nor the manual page I was reading. But here (https://www.diyautotune.com/support/...ding-firmware/) it mentions the boot jumper. Doing that I was able to communicate and flash the firmware. Will update as I keep going. -- Alright so the firmware was updated, so the tune needs to be "retuned/updated" as well. Car is acting quite a bit different with the same tune (q.q backwards compatibility). Side note: why the hell did the firmware get corrupt. Guess they're writing directly to the memory instead of a buffer with a final byte signal.

Seems like the firmware upgrade on a MSPNP2 (M9093) still needs to connect to the device via the firmware?

```
Debug message Level:
1: Normal
2: More detail
3: + serial comms
4: + the s19 file as parsed
Selection (default: 1): 3

Do you want to scan your serial ports automatically? (y/n default y)y

Trying: /dev/tty.Bluetooth-Incoming-Port ..#Opening comm port /dev/tty.Bluetooth-Incoming-Port
TX: 51
Sent Q and got 0 bytes back.
TX: 0d
Sent 0d and got 0 bytes back #Closing comm port
Trying: /dev/tty.usbserial-A5001tUr ..#Opening comm port /dev/tty.usbserial-A5001tUr
TX: 51
Sent Q and got 0 bytes back.
TX: 0d
#Closing comm portbytes back

WARNING!!!

No valid ports or ECUs found. Cannot load firmware without communications.

Common problems:
- Something is hogging the serial port.
e.g. TunerStudio, modem or mobile phone cable software.
Be sure to close/exit those applications.
- USB-serial cable on high COM port number, use Device Manager to re-assign
it to say COM1.
- ECU not powered up, be sure there is fused power applied. Use a mains
adapter or vehicle battery. PP9 batteries are too feeble.
- Serial cable not connected correctly
- Software driver problems

Check the above. Do you want to try probing again? (y/n default = y)
```

What firmware did you upgrade from? The 3.3.0 and later code added error checking and other features to protect the firmware.

It's also possible that you could have set a combination of settings that (1) the firmware doesn't have a good way to resolve, and (2) the code team didn't anticipate somebody would do. An example I ran into on one firmware version was where somebody had enabled missing tooth wheel mode, then set the number of trigger wheel base teeth to two teeth, and set the number of missing teeth to two as well. So he was saying there was a zero tooth trigger wheel. Crashed the firmware.

I can take a look at my restore points to tell you the previous firmware, but I believe it was a 3.3.x (to 3.4.2)

I hit "undo" on the AFR table in Tuner Studio, seems like it must have burnt that to the MS. I didn't have incorporate AFR table or anything, so wasn't expecting a burn. I guess Tuner Studio decided "undo" included a burn and still sends the AFR table incase MS needs it. Since it was writing the tune, it's possible that the corrupt data caused the tune to become something like case 2, but one AFR cell was all that changed (and to an acceptable value since it was already running that value). I guess the only way to truly prevent something like that is if the MS has two banks for tunes so it can write one tune and the last bit a "switch table" bit, but I assume that would run the cost up there a bit and require a redesign lol.

My frustration as a customer is that Tuner Studio on Mac has quite a good amount of bugs (as a User I shouldn't get NPE dialogs). And this would be the 3rd time that my MS tune got corrupted, previous times it was tuning idle in the garage. Would be nice if there was a way to say "blip the throttle before tuning", which the only way would be the IAC I guess. I will say I'm new to this so these might be "learning pains" but hey, a product with no learning pains is better than one with :P (if it can be eliminated). And thank you both for being here on the forum to help people with these pains. Can't wait dial in my tune (and eventually a turbo, once I've convinced myself that I have the skill for that part of the build).

Edit: also, Matt, if you could pass along that the firmware upgrader should mention something about the boot pin? I know Tuner Studio has a dialog for it, so there must be a way to tell. Or just have it like the static "did you" for the spark wires. That was frustrating since as a PNP user I didn't know anything about the boot pin / inside of the case.

Usually you don't need to use the boot pin, unless the tune is really corrupted or you accidentally changed the serial data rate.

I'd recommend contacting the TunerStudio team at support@efianalytics.com directly about apparent Mac bugs. Phil Tobin, the guy who wrote TunerStudio, uses a Mac pretty often himself.