TS 3. 0. 10. 08 Corrupts MSQ MsI Extra Hr 11c2

[Gavin Lodewick]

Hi I have TS Ultra, and updated to 3.0.10.08 this update corrupts My MSQ When I make changes.

Running Ms I Extra Hr 11c2. I will put my old MSQ up.

[LT401Vette]

What gets corrupted?

[LT401Vette]

It think this line broke MS1....

- 2016-10-13 - Read only portion of page needed instead of full page on dialog open.

http://www.tunerstudio.com/index.php/do ... ngelogmenu


I'm glad you brought this to my attention before it got promoted to stable.

[Broke4speed]

This might be digging up an older thread (by a couple weeks), but I experienced the exact same thing, although with plain-Jane B&G fuel code, and Hi-Res 10C. I thought I blew up my processor (again) so I ordered a DIYautotune assembled unit to eliminate variables, haha.

[LT401Vette]

This might be digging up an older thread (by a couple weeks), but I experienced the exact same thing, although with plain-Jane B&G fuel code, and Hi-Res 10C. I thought I blew up my processor (again) so I ordered a DIYautotune assembled unit to eliminate variables, haha.

Yes it unfortunately effected all MS1 protocol ECU's.

[Broke4speed]

I have tried to make contact with the box since then, and the firmware uploader can't find it. I can connect to it with tunerstudio, but nothing reads properly. Is there a last-ditch way to upload the firmware? I've tried going back to the B&G fuel code, using the bootloader, not using the bootloader, but it just keeps erroring when I try. I'm not stressed, because I have a second MS1 now, but it would be cool to have two .

[LT401Vette]

You shouldn't need to reload the firmware. All TS corrupted was tun data.
You should be able to load an old msq and be good.

If you do re-load the firmware; The boot jumper should work fine. You can not use TunerStudio's firmware loader as it doesn't support MS1.

Are you using B&G MS1 firmware, not Extra?

[Broke4speed]

Ah ok, I'll try that.
I'm setting the car up on MSNS-extra (non HR for now), but flashed back to B&G to see if the problem was firmware related. I may be grappling with a separate issue too it seems, since my firmware comes up as '15' in project properties. I'll probably put this box aside for now, since I don't need it currently, and worry about it later.