MS3 pre-1.5 alpha 2 and 3 released

[DeadStiff]

The new firmware seemed to load on my ms3 no problems. It just did not complete the part of the TS upgrade process where it applies the tune. When i did it manually it gave me a few warnings which all seemed reasonable. I used the beta a version. Reading the various posts there does seem to be an issue with earlier ms3s, i think mine is a later version.

The problem is that TS is using the older loader and 1.5 requires a new loader, even if you have a newer MS3.

[jsmcortina]

I don't believe v3 TS will load 1.5 code correctly.

This is correct. Phil and I have discussed it and we are waiting until the standalone firmware loader is solid with pre-1.5 before Phil applies those changes to the TS firmware loader. There's little point in Phil applying the current loader changes when they are not yet proven.

James

[arran]

The recommendation would therefore be to reapply 1.5 alpha 3 with the standard loader included with the firmware download? Given I have used the incorrect method via TS V3, is it likely I will now run into issues? Are there additional switches/commands I need to use with the traditional loader?

Thanks,
Arran

[arran]

1.5 alpha 3 loader failed. First time since I have been a Megasquirt user that I have had a problem loading firmware. ECU was dead in the water. Fortunately after a power cycle I was able to reconnect. 1.5 update failed a second time. Debug level3 screen cap attached.
I have gone back to 1.4 beta 4. At least the TS 3 beta seemed to load 1.5. I had the engine states menu so it did seem to load

ms3 1.5 firmware fail.JPG

[jsmcortina]

As I said before, the first load may work, but subsequent loads (of different pre-1.5 firmware versions) will fail as the current TS loader (and older standalone loader) does not know how to erase all required flash pages.

Did you try with the updated loader I posted a link to?

James

[arran]

No, I used the packaged loader.
Just repeated with the loaders located here:
http://www.msextra.com/doc/files/
I used the win32 version

Failed again, see screen cap. Rolled back again to 1.4.1 b4

ms3 1.5 firmware fail_2.JPG

[juansh2385]

Those look exactly like te message I posted after using the patch loader that James uploaded.

Any news? I really wish to try 1.5.

James I not sure if it posible but I have access to a bdm cable. I know that the monitor is not available to the public in order to stop ilegal copy/use of the ms3 firmware but,

Is it posible to write a program to install the new monitor but as a requirement to work the old monitor must be installed in the processor or something in that line of thought?

I know it is probably easiest said than done but I just throwing ideas out there.

[tpsretard2]

i just tryed this morning. i get exactly the same error as above

[Sam280Z]

I'm getting a similar message. My MS3 was purchased from diyautotune in September of 2011.

I originally attempted to use the new TS firmware loader feature to load alpha3. I incorrectly thought that it used the loader supplied with the firmware. It appeared to work as James has indicated.

I then read that TS uses an incorrect loader for this version. I then tried the loader supplied with the firmware and got an error. I then saw that James had posted a different loader separate from the firmware. When I attempt to use it, I get this:

pre1.5 error2.png

https://drive.google.com/file/d/0BwzTtn ... cslist_api

I've gone back to pre1.4beta1 which appears to be working fine.

If there's anything I can do to help resolve this issue, let me know. My car is currently out of commission anyway, so I can even send the ms3 off if it's needed for testing.

Sam

[jsmcortina]

Yes, this is a known issue. No new bug reports needed.

James

[subwoofer]

Any progress on the new loader for old MS3s, James? I'm dying to try it out, but it won't load...

[jsmcortina]

I've been working on it and hope to have something to release soon once I've tested some more on the three operating systems.

James

[Speedy_G]

Do you have more informations about the DBW Idling Function?

I see only a option for maximum additional Throttle Target.

But for example: Where is the rpm target setup?


Maybe you could upload the source code ?

[jsmcortina]

But for example: Where is the rpm target setup?

In the idle control system.

Maybe you could upload the source code ?

Not yet no.

James

[Speedy_G]

But for example: Where is the rpm target setup?

In the idle control system.


James

So which table or curve exactly?

Because the "Closed-Loop Idle Target Curve" is only activated when i active the "idle rpm timing correction".
So it seems like it has nothing to do with the DBW. And there is no other target setup.

[jsmcortina]

Use the normal closed-loop idle RPM target curve.

James

[Speedy_G]

okay just to be clear:

I have to set the "Idle RPM Timing correction" to "ON", so that i activate the "closed-loop idle RPM target curve." Because without this the target curve is deactivated, no matter if i active DBW idle control in the testmode menue.
But then the "Idle rpm timing correction curve" gets also activated and i have to set all points (rpm delta/ ignition delta) to zero, so that this system doesn't interfere with the DBW Idle control?

And then it seems to be some kind of "hardcoded" PID-Control Loop? Because there is no option to set any PID Parameters for DBW Idle control

[jsmcortina]

The DBW system is being used in lieu of an idle valve. So set up closed loop idle like normal as if there was an idle valve.

James

[Speedy_G]

Okay then i have to set it to "PWM Valve (2 or 3 wire)" to get the target curve activated

But:

1) I have to select an output port. But all of those are already used for other functions, as i dont use a idle valve.
And i think it makes no sense to select a port, when a valve isnt used or wired at all.

2) What happens to all those "Closed-Loop Idle Valve Settings".
Is all that stuff ignored?

3) I guess the "Closed-Loop Idle PID Gains" are not ignored, and those PID Parameters (in case of "Advanced Tuning Mode") are used??

4) What happens while cranking? Is the DBW Idle just deactivated?
If yes .. for how long? Is this crank to run taper active?

So at the moment its not very clear which settings are active.

Or will this be changed in newer firmwares? As it seems inconvenient.

Maybe its possible to add a option "DBW" for Idle Valve Type.
Then all the unused settings are greyed out and only settings are visible, which are actually used.
And of course no port is controlled. As i think nobody is going to use a Idle Valve when DBW Idle Control is activated.

Couldn't the most stuff of this be done with a different TunerStudio ini and only some minor changes to the firmware?
I mean for example all the PID parameters could be stored in the same memory variable.

I added two pictures into the attachement to make i clear.

[Speedy_G]

Can't you upload the source code, when you dont answer questions or explain the idle function??