When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
Nope, reloaded to 1.4.0 and nothing. The same situation. Car will fire up with some throttle and won't idle. It keeps running as it was before on 1.4.1 definitely ruff and makes the garage smell like half burned fuel. Yay.
I was in the hospital sick most of the day so haven't had a chance too mess with it. Don't worry, I'm not dying. I'm under veterans health care, yay socialized medicine and all its hurry up and wait glory.
As is sits the car should run
-LS coils (4 of them) set for sequential
-350cc sequential injection
-internal map sensor
-no turbo
My understanding from digging around the interwebz on a spotted cell phone connection is that tunerstudio should find the correct .ini file for the firmware number. The car does fire, run like crap, and the "sync" light icon is red and never flickers even though it runs and I get signals on the composite logger.
I will add that I got this message after the firmware update. I transferred the projects over to my desktop and got it to give me the error message from opening the last tune file. Currently looking at both tune with an old 1.2.4 firmware and the new. So far the idle control was turned off on the new and lets see what else we can find. Looking at this list of 84 erros I don't know where to find a lot of it.
I have nothing to add other than thank you for posting this.
I've got EXACTLY the same problem with my MS3-Basic. I'm also running 1.2.4 and any attempt to upgrade to 1.3.x or 1.4.x results in this same kind of chaos. All crank, no start. I gave up and just left it on 1.2.4 and haven't touched it since. If I'm feeling ambitious I'll put 1.4.0 on it and see if I can pull a log, but right now the car is pulled apart.
Solidarity, brother. In for win. I'd love to see this resolved.
There were quite a bit of code changes between 1.2.4 and 1.4.1. A lot of times it fills in values with rubbish, you should go page-by-page and make sure there's been no setting changes that would prevent a start or do something funky, or try a know good 1.4.1 map -- that will at least rule things out.
My Rev built MS3 works fine after the 4.1 update. none of my old files are any good anymore. After the update I started a new project, hooked it up to the car and saved the tune in the ecu as current.
only drawback is no older set points.
Solidarity, brother. In for win. I'd love to see this resolved.
No worries. Sorry if I never get this figured.
I just sat here and drank coffee and hate going through the tune files. Laptop running 1.2.4 firmware and the last tune I used with a running car and the desktop running the same file on 1.4.1 I then transferred it all back to my laptop. I realized I did the changes on 1.4.1 , but opening it in 1.4.0 shows no errors. Just went and test fired it. Only thing I found wonky was the idle control wasn't turned on. Now it tries to idle, the settings are odd and it hunts around, but it does try. It will start without throttle input now. However, it still shows that is doesn't have sync even thought the trigger logs look clean like the last one posted.
If you notice it is running, but the little red sync button is all angry.
Current trigger wheel is the 4 tooth factory one. It is the 949 damper with the 4 tooth wheel. I did not swap wheels yet cause I learned a long time ago to make as small a change as possible between tests. At least when possible.
Ah, I see noow. It was, and still is, set to the 99-05 option. If I recall correctly it was set that way the other day.
I just downloaded all the firmwares I could in between 1.2.3 and 1.4.1 and made new projects for each as well as loaded the tunes into each one, glanced at the error logs, and all I changed was the idle control I turned back on. A shot in the dark. I thought maybe if I go in baby steps through the levels of updates than maybe it would help. Yes I'm not software guy, but I'm at home sick and have the time. So here goes.
from 1.2.4 to 1.3.4 lots of errors and this is where the idle control got turned off.
from 1.3.4 to 1.4.0 there a was no error code going to 1.4.1 so screw adding more pics.
Muahaha! It raises from the dead like the cursed spawn it is to lay waste and destruction. Unless I try to fix a thing again. I never learn.
So for some reason it worked. I made a temp project for each firmware level and then loaded the tune from when it last worked. Then glanced through the menus and and out of all the iterations I only change the idle stuff. Basically rinse repeat at each option of firmware. Starting with a tune on 1.2.3 to 1.2.4 then save the tune and make a new project with the new saved 1.2.4 tune. Now adjust, save and make a new project at the next level. Bring in the tune let magic happen and re-save until you are at the level you want. Then once I made it to the desired level of Donkey Kong I connected to the ecu and made a new project and loaded my saved game from my cycle of projects earlier. For me I'm stopping tonight at 1.4.0 unless I feel better later and get frisky with 1.4.1
I have no idea why this worked. I make no claim to why. It worked and now to see what the interwebs and smarter than I peoples say.
Muahaha! It raises from the dead like the cursed spawn it is to lay waste and destruction. Unless I try to fix a thing again. I never learn.
So for some reason it worked. I made a temp project for each firmware level and then loaded the tune from when it last worked. Then glanced through the menus and and out of all the iterations I only change the idle stuff. Basically rinse repeat at each option of firmware. Starting with a tune on 1.2.3 to 1.2.4 then save the tune and make a new project with the new saved 1.2.4 tune. Now adjust, save and make a new project at the next level. Bring in the tune let magic happen and re-save until you are at the level you want. Then once I made it to the desired level of Donkey Kong I connected to the ecu and made a new project and loaded my saved game from my cycle of projects earlier. For me I'm stopping tonight at 1.4.0 unless I feel better later and get frisky with 1.4.1
I have no idea why this worked. I make no claim to why. It worked and now to see what the interwebs and smarter than I peoples say.
I'm not sure I quite followed you. Sounds like you made the projects twice,
But I think you did not. So instead of jumping from 1.2.3 to 1.4.0, you stepped through each FW revision. That worked better and gave a different result than going straight from 1.2.3 to 1.4.0, and fixing the idle. Is that what you're saying.
If so... Brain and Rev, is that what we should always do?
Sorta yeah. I opened tunerstudio and made a fake new project and loaded the tune. Tunerstudio popped some error codes and I fixed the idle turned off. Then I save the tune as a new name and made a new fake project with the next up firmware named something else. Then loaded the "fixed" tune to the next level firmware. repeat until at current level tune. I will say the gauges and stuff are different on the step by step firmware then on the big step update. Once again no idea why, but I know I don't want to go from Windows 95 strait to Windows 10. Figured maybe this was similar.
good, i was thinking doing something like that would solve the issue. This should pretty much always be standard practice when changing firmwares -- i almost always start a new project, and reload the tune file once it's been saved back out at the newer firmware.
What I find odd it the dashboard didn't change with the firmware up date. I didn't know it should so I never questioned it. Notice the firmware number at the top of the pics. The location changed on the new one that worked. I'm guessing in the list of stuff that went wonky the dashboard not changing would be a hint. No if I could stop having a lung infection I'd be happy.
12-10-2016, 03:04 PM
0
