Has your tune ever gone wacky when you don't burn any new tunes in???
04-24-2017, 12:52 PM
#1
Junior Member
Thread Starter
Join Date: Nov 2005
Location: Duluth, GA
Posts: 92
Total Cats: 0
Has your tune ever gone wacky when you don't burn any new tunes in???
Details: 1995 original 1.8 motor, 460cc RX-7 injectors, T3 turbo, Innovate LC-1 wideband
MSPNP - original MSPnP from DIYAutotune v1 with 029y4 firmware
I use ShadowDash on an Android phone as a dashboard and datalogger whenever I drive... And I've used it to burn new tune files to the ECU when I do VEanalyze on the laptop.
I have been driving this car a long time now, so I'm not tuning all the time anymore between driving sessions. Have a very stable tune that I run with all the time.
Anyone ever had this happen?
A few months ago, after driving several months on the same tune, I used the laptop and TunerStudio connceted to the ECU to work on the idle section as hornetball had written up. When I opened up the MSQ file, of course it asked to burn the tune to the ECU. I of course said yes because I was opening the same tune file that was burned into the ECU. But then all of a sudden, TS warns me that there are multiple differences between the file and the controller: one of which was the EGO sensor selection. The ECU thought I had a narrowband! How could that be? I told TS to reburn the tune to the ECU, and I didn't think that much of it after that. The car had been running totally fine up to that point. Had I never used the laptop TS I wouldn't have known the problem. Somehow the tune on the ECU had drifted to something else.
This past week, what was happening on my ShadowDash was that AFR's were going haywire! I mean like reading full lean 22.33 while crusing, or showing AFR in the 9's or full lean when idling, but the engine was operating as normal. Sometime it would even oscillate between 7 and 22 while cruising at 75mph on the highway. Thinking that something was going on with the LC-1 like grounding or something, I decided to just open up the laptop TunerStudio and see what was going on. This time there were no difference warnings, but of course it burned the file to the ECU when I opened the file. But then the laptop dashboard showed complete, normal behavior of the AFR number. So then I reconnected the ShadowDash on my phone and the AFR's were also acting normally.
Has anyone else noticed that the tune burned to the ECU seems to drift if never updated? Or do you just regularly burn tunes to it with TunerStudio?
MSPNP - original MSPnP from DIYAutotune v1 with 029y4 firmware
I use ShadowDash on an Android phone as a dashboard and datalogger whenever I drive... And I've used it to burn new tune files to the ECU when I do VEanalyze on the laptop.
I have been driving this car a long time now, so I'm not tuning all the time anymore between driving sessions. Have a very stable tune that I run with all the time.
Anyone ever had this happen?
A few months ago, after driving several months on the same tune, I used the laptop and TunerStudio connceted to the ECU to work on the idle section as hornetball had written up. When I opened up the MSQ file, of course it asked to burn the tune to the ECU. I of course said yes because I was opening the same tune file that was burned into the ECU. But then all of a sudden, TS warns me that there are multiple differences between the file and the controller: one of which was the EGO sensor selection. The ECU thought I had a narrowband! How could that be? I told TS to reburn the tune to the ECU, and I didn't think that much of it after that. The car had been running totally fine up to that point. Had I never used the laptop TS I wouldn't have known the problem. Somehow the tune on the ECU had drifted to something else.
This past week, what was happening on my ShadowDash was that AFR's were going haywire! I mean like reading full lean 22.33 while crusing, or showing AFR in the 9's or full lean when idling, but the engine was operating as normal. Sometime it would even oscillate between 7 and 22 while cruising at 75mph on the highway. Thinking that something was going on with the LC-1 like grounding or something, I decided to just open up the laptop TunerStudio and see what was going on. This time there were no difference warnings, but of course it burned the file to the ECU when I opened the file. But then the laptop dashboard showed complete, normal behavior of the AFR number. So then I reconnected the ShadowDash on my phone and the AFR's were also acting normally.
Has anyone else noticed that the tune burned to the ECU seems to drift if never updated? Or do you just regularly burn tunes to it with TunerStudio?
Reply
0
0
04-27-2017, 12:01 AM
#3
I have the same POS. That has happened to me, and I always used the controller settings, as I may have accidentally changed something in my project or forgot to save to ecu and turned my car off with autotune still on.
Maybe a dumb question, is your IAT working correct? I've noticed that caused those symptoms for me.
Did your map sensor lose calibration? It has over the past few years for me. You have to rewrite the code or solder in a new unit.
Here is the solution.
https://www.miataturbo.net/mspnp-55/...bration-54795/
Maybe a dumb question, is your IAT working correct? I've noticed that caused those symptoms for me.
Did your map sensor lose calibration? It has over the past few years for me. You have to rewrite the code or solder in a new unit.
Here is the solution.
https://www.miataturbo.net/mspnp-55/...bration-54795/
Reply
0
0
