MS3 pre-1.5.1 beta 6 firmware released

[jsmcortina]

To announce the release of "MS3 pre-1.5.1 beta 6" this fixes one bug in "MS3 pre-1.5.1 beta 5".

Who should use this code?
Users wanting to test the new features or as directed by tech support to workaround known issues in 'release' version.

Who should not use this code?
Unless directed by tech support, new or casual users should use the current release code instead – see the Downloads page linked above.

Main changes since pre-1.5.1 beta5 firmware
See the page for pre-1.5.1 beta5 for more recent changes too.

Bug fixes:
SDcard. A timeout during first init could cause an invalid baud rate to be used.

New / changed features:
-

Minor / internal:
-

The firmware zip is available from:
http://www.msextra.com/downloads/dev/ms3/1-5-1/beta-6/

Be sure to read the README.txt and RELEASE-NOTES.txt that are supplied in the zipfile.

Some of the ini changes will result in harmless warnings when loading MSQs from 1.4.x
Users upgrading from 1.2.x or earlier codes need to pay more attention.
TunerStudio 3.0.16.6 beta or later is REQUIRED.
TunerStudio 3.0.18.09 beta or later is recommended for reliable SDcard readback.

Go ahead and use the built-in firmware loader on the Tools menu of TunerStudio 3.0.x - you'll like it.

[Dennis_Zx7r]

Used beta6 instead of the experimental version you sent per eMail.
SDCard is working fine for me now.

[elaw]

I know there are a lot of links in this chain and the firmware might well not be the cause, but since this started when I updated the firmware I figured I'd post here first...

I'm running Shadowdash on an Android phone with auto-connect and auto-logging turned on. It's connecting via a bluetooth adapter on the MS RS-232 port.

With this firmware, SD will connect to the Megasquirt, start logging, and then disconnect after about a second. The cycle then repeats, seemingly indefinitely.

This is new with the beta 6 firmware... I was previously running pre-1.5.1 beta 3 with no trouble.

One thing I checked was the .ini file on the phone, I thought it might not have updated properly. It had today's date on it, but I replaced it with the ms3.ini from the firmware .zip and it had no effect on the problem.

[jsmcortina]

I'm not aware of anything that would cause that effect. If you have opportunity, please try intermediate and original firmwares and report your findings.

James

[elaw]

Okay I tried beta 6, 5, 4, and 3, in that order. The problem happens with all > 3, with 3 everything works fine.

I notice on the versions > 3, SD pops up a message saying "runtime data 519 bytes" or something like that. Did the data block size change from beta 3 to 4 and maybe SD has a problem with > 512 bytes? I tried twice with beta 3 and there's no message about runtime data size at all.

[jsmcortina]

The realtime data size hasn't changed, so I don't know what's going on??
I double checked the ms3.ini and the block size directive is still showing as 512.

James

[VcrMiata]

WRT the issue with Shadowdash - I also have been having the same issue with not being able to connect for more than a second using EFI bluetooth adapter.
This has been happening for at least the last 2 beta releases.

I was using ShadowDash 1.5.02 - I moved back to 1.3 and had the same problem there, so I moved back to 1.5.02.
I thought it was me only issue with my tablet (Samsung Tab S2) because Tuner Studio on Windows connects fine and I haven't seen a similar issue reported in the "Other tuning /logging software" forum.

Anyone else?

Tony

[jsmcortina]

It would be worth posting on that sub-forum to see if others have the issue. I don't have a Shadow Dash install to test on.

I re-checked the code and don't see anything obvious.

James

[elaw]

Yeah, I did that. For anyone interested, the thread is here: http://www.msextra.com/forums/viewtopic ... 33&t=67101

[krisr]

This beta worked for me and resurrected my SD Card! It's early days yet but what appeared to be a temperamental SD card wrote 4 logs without issue after burning B6 and managed to retrieve them via Tunerstudio successfully

I did have an issue with the loader_macos file. When it ran the eraser it bombed out with some error. Only way I could recover the ECU was to fire up my Windows 10 VM on the Mac and run the windows loader. Didn't capture any logs though, just that it didn't work for me.

[elaw]

It would be worth posting on that sub-forum to see if others have the issue. I don't have a Shadow Dash install to test on.

I re-checked the code and don't see anything obvious.

James

Hey just to close the loop on this: I posted in the other forum, Phil responded that the .ini files for the newer betas were formerly not on the server but he had put them there. I tried connecting with SD again and all is now well. I'm thinking that when I manually copied the .ini file to the phone, either I put it in the wrong place or it got overwritten somehow.

[ms3rx7]

I have been having major issues with my ms3pro and I believe I've narrowed it down to engine states. I have had periodical occurrences since i believe beta 4 where under high load the ms3 will actually shut off. When the ms3 shuts off it obviously stops logging which makes things difficult to diagnose, but I have noticed a pattern. Every time the ms3 shuts off, the datalogs indicate the "engine accelerating slowly" state goes haywire right before the log ends. I have a value of 200 in my engine states for acceleration, but i've had it as low as 90 and as high as 500 and the results are similar. Although not immune, the higher I make that value the less likely the ms3 shuts off and visa versa the lower the value the more likely. With a value of 500, more times than not, it just hesitates. When it does this, the PW momentarily drop to zero shortly to recover where it left off causing a pretty gnarly rotary backfire. I've been unable to observe any sync losses under this condition where the ecu does not shut off and is still logging when the PW drops to zero. I do not have any definitive proof that this engine states feature is the cause, but it is suspect. Perhaps someone can view my datalog and msq and find something I'm missing as I'm no guru.

I am running a 12v hall effect sensor and 36-1 trigger wheel.

i have many datalogs, if more are needed let me know.

[jsmcortina]

I was driving and racing on beta6 over the weekend using an MS3X and an MS3-Pro Ultimate, I didn't observe anything like this.

What I do notice from your log that seems a bit odd, is right at the end you open the throttle but the engine doesn't react? i.e. you go from 50% throttle to 100% throttle but RPMs don't climb any faster and MAP doesn't climb any faster. This seems a little odd, unless the throttles are very large and 50% was already effectively wide open?

James

[ms3rx7]

I'm really at a loss, but I now have additional information. I first noticed this happen when I had the staged injection table open which may be key as I don't think most of us use this feature when testing these betas. it seemed like anytime the dot climbed to the top of the kpa row in the staged injection table it would cause this entire phenomenon we're discussing. Upon further investigation it appears the Ms3 is NOT actually shutting off even though it stops logging and tuner studio goes offline. I made the point today when the ecu cut out to intentionally not cycle the power while coasting and instead I rolled to a complete stop with the engine dead. What I observed was my wide-band went full rich immediately after I lost power instead of full lean like i initially thought and my E fan was on and stayed on even though "allow fan when engine off" is set to NO. Once I cycled the power, the Efan turned off as it should with engine not running and the engine had to be flood cleared to start. This to me indicates that I am probably losing spark to all 4 coils at once when the ecu trips up but apparently not fuel in addition to the rest of the symptoms i mentioned.

[LSXCutty]

Using Beta 6 on a MS3-Pro Using duel fuel tables Flex, Dome Control, Water Meth, Traction Control, Launch. Everything seems to be working great for the past 300 or so miles

[ms3rx7]

I am going to reinstall the firmware and rebuild my tune from scratch. Perhaps the tune itself got corrupted. I keep on getting write to controller error dialogs for no apparent reason. Also it seems like a lot of the time when I open a dialog even without changing any settings, the burn icon is red when I know nothing has changed or been tampered with. I am starting to think the Ms3Pro is defective but I have no way to test it. or is there a way to run diagnostics?

[jsmcortina]

I am going to reinstall the firmware and rebuild my tune from scratch. Perhaps the tune itself got corrupted. I keep on getting write to controller error dialogs for no apparent reason. Also it seems like a lot of the time when I open a dialog even without changing any settings, the burn icon is red when I know nothing has changed or been tampered with. I am starting to think the Ms3Pro is defective but I have no way to test it. or is there a way to run diagnostics?

Were you getting these messages with earlier firmware? I'm not seeing those problems, but _perhaps_ there is a firmware issue?

Your first step is to roll back to the last known-good working firmware and confirm that everything is back to normal.

James

[64bit]

@jsmcortina

I know MS3 takes a bit of priority, but will there ever be a firmware update to the Micro Transmission Control?

[ms3rx7]

I spent the last day messing with this issue. first thing i did was create a new project then reflash beta 6 without loading a tune then disconnected my laptop to sit in the recliner.. there I recreated my tune from scratch. I then hooked up my laptop and clicked "use tunerstudio settings" through the difference report. no errors came up until I power cycled the ecu afterwards then i got the error dialog box shown in attachments. the computer still acted up at high load.

I then installed firmware 1.4.1 with a known working tune and the problem was still there. However i was able to see a sync loss #2 which is a missing tooth error i believe. The prblem is i don't know if this sync loss was the cause or the effect of the issues i've been having. Seeing how I have a 36-1 12v hall effect wired into shielded ckp+ I did not expect to see this as i believe it to be a rock solid noise insensitive setup. I am using the kit from fullfunction engineering and it utilizes the same crankshaft position sensor sold by diy autotune https://www.diyautotune.com/product/hal ... on-sensor/ the gap is in spec and i have maybe 2000 miles on the sensor. Can these sensor even fail? I think my next step is to order a replacement sensor, but if a new sensor doesn't fix it, is there a way to improve upon that setup? a diode, capacitor, etc etc?

[jsmcortina]

As you are getting the same issue with 1.4.1 firmware, you are probably best to start a new topic with MSQ, datalog and tooth log. You may want to contact your supplier and link to that new topic.

James