MS3 pre-1.5.1 beta 2 firmware released

Testing and development of Megasquirt 3

Moderators: jsmcortina, muythaibxr

MS3 pre-1.5.1 beta 2 firmware released

Postby jsmcortina » Wed May 10, 2017 2:05 am

To announce the release of "MS3 pre-1.5.1 beta 2" this fixes some bugs in "MS3 1.5.0 release" and adds support for new hardware.

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 beta1 firmware

Bug fixes:
AEM CAN EGO could rollover beyond 25.5AFR. Limit to 25.5.
Fix realtime baro port #define for MS3-Pro-evo

New / changed features:
-

Minor / internal:
Update "CAM sensor" tooltip for Nissan CAS case.
Simplify AEMX CAN receiving code.
Staging greying.
Sequenced batch-fire tooltip tweak.

TODO:
A small number of further changes are in testing and will be in next beta.

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

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.
I can supply, repair or upgrade Megasquirts in UK. http://www.jamesmurrayengineering.co.uk

My Success story: viewtopic.php?f=104&t=34277
MSEXTRA documentation at: http://www.msextra.com/doc/index.html
jsmcortina
Site Admin
 
Posts: 33901
Joined: Mon May 03, 2004 1:34 am
Location: Birmingham, UK

Re: MS3 pre-1.5.1 beta 2 firmware released

Postby David_G » Fri May 26, 2017 9:15 am

I tried the new code.

Seems to work fine apart from the Idle-valve issue during/after cranking which I still have (since the update from 1.5.0 to 1.5.1-beta1).
I'm not entirely sure if this is a problem with my tune or the firmware itself but after checking the datalogs over and over again I am quite convinced that this is firmware related.

I just can't understand the idle valve behaviour at all.
Why is the idle duty rapidly increasing by about 6% directly after 'cranking'-mode has ended? And why is it also rapidly decreasing by about 13% after a short time - causing the engine to stall? Where are those values coming from? The 'Cranking' value (from the 'Idle Cranking duty'-table) and the 'Run' value (from the 'CL Idle Initial values'-table) are clear to me but where do the values in between come from?

From time to time the engine starts as expected because the idle valve is NOT rapidly decreasing but instead entering CL-Idle (see Status6=48 in the datalog) which keeps the Idle Valve PWM up where it is supposed to be and then slowly tapering down. So the engine only stays alive if its entering CL-Idle about 0.8s after 'Cranking' has ended. However I have set a PID delay of 1s and RPMdot is much too high in the beginning which actually would have to prevent entering CL-Idle. But as said from time to time it still does (which is good because only the the engine stays alive). Are there different CL-Idle lockout criteria for 'AfterStart' compared to normal operation?

Please can someone explain what is going on and how I (or the developers) can fix this??
Attachments
2017-05-25_13.03.28_LOG0242_WarmStart(good and bad).msl
(939.13 KiB) Downloaded 11 times
Cranking good and bad.jpg
Cranking good and bad.jpg (212.35 KiB) Viewed 616 times
Bildschirmfoto 2017-05-26 um 18.20.34.jpg
Idle settings
Bildschirmfoto 2017-05-26 um 18.20.34.jpg (300.88 KiB) Viewed 616 times
David_G
Helpful MS/Extra'er
 
Posts: 78
Joined: Wed Apr 02, 2014 1:14 am

Re: MS3 pre-1.5.1 beta 2 firmware released

Postby arran » Tue May 30, 2017 4:39 am

Your Engine state values don't look right to me.
I just installed the same 1.5.1 b2 code last week and saw a similar problem on startup, the "idle cranking duty/steps" didn't work.
The problem is that the prior code was not working properly in other aspects which was masking incorrectly setup Engine States.

If you have not already, take a look through this thread:
viewtopic.php?f=125&t=65770

My settings are here, seems to work so far
engine states.JPG
engine states.JPG (76.13 KiB) Viewed 559 times
RX7 Series 2 13B Turbo. Megasquirt 3 with 3X Expander and V3 CPU. Firmware 1.4.1
Knock module, twin EGT, real time clock, WBO2, full sequential fuel and spark
http://web.aanet.com.au/arran
arran
Master MS/Extra'er
 
Posts: 581
Joined: Mon Oct 29, 2012 2:34 am
Location: Brisbane Australia

Re: MS3 pre-1.5.1 beta 2 firmware released

Postby David_G » Tue May 30, 2017 5:06 am

Hm you mean my fast accel/deccel thresholds?

I did a quick pull in second Gear, checked my datalogs for those and didn't touch them again after that because I could'nt think of a way how the FAST accel/deccel thresholds could have an influence on the cranking behaviour...
But thanks for showing me your values just to have an idea, I will have a closer look on those values!

Is there a better explanation somewhere what exactly the slow/fast accel/deccel thresholds have an influence on?
In TS, it only says "used by Closed-Loop Idle control, idle-VE and idle advance". But for what exactly?
David_G
Helpful MS/Extra'er
 
Posts: 78
Joined: Wed Apr 02, 2014 1:14 am

Re: MS3 pre-1.5.1 beta 2 firmware released

Postby arran » Tue May 30, 2017 5:27 pm

I was looking more at the slow figures, these are the ones that will be impacting you after start and closed loop behaviour.

I am aware of the tool tips and the 1.5 release version doco. There was mention on the forum a year or two ago that a flow chart style description of the idle pseudo code would be a good idea but I don't think anything came of it.

There does seem to be an undercurrent of Megasquirt users asking questions about how it is that idle is intended to work, I know from my perspective it is something that I have struggled to make work as well as I'd like over a number of years. The Engine states code seems to help greatly because it is simpler now though it is still a complex subject and questions on the forum which I'm sure irritates the devs would be reduced if there was just a little more detail available

David_G wrote:Hm you mean my fast accel/deccel threshold?

...............

Is there a better explanation somewhere what exactly the slow/fast accel/deccel thresholds have an influence on?
In TS, it only says "used by Closed-Loop Idle control, idle-VE and idle advance". But for what exactly?
RX7 Series 2 13B Turbo. Megasquirt 3 with 3X Expander and V3 CPU. Firmware 1.4.1
Knock module, twin EGT, real time clock, WBO2, full sequential fuel and spark
http://web.aanet.com.au/arran
arran
Master MS/Extra'er
 
Posts: 581
Joined: Mon Oct 29, 2012 2:34 am
Location: Brisbane Australia

Re: MS3 pre-1.5.1 beta 2 firmware released

Postby David_G » Mon Jun 05, 2017 1:41 am

Well, I overtook the slow figures from the 1.4.1 firmware because i figured, those must react to the same things (RPMdot threshold for engaging CL-Idle and PID disable RPMdot).
PID engagement works flawlessly once the engine is running. I am just having troubles with the afterstart-behaviour and can't figure out how to change it.

However I did try different settings with first making the slow-windows as small as possible which did not work out at all. Now i set the fast-values for first gear RPMdots and also widened up the slow-window a bit (see screenshot). Still with no improvement.
Also when checking my datalogs during cranking, my RPMdots do not really change no matter if the idle valve behaves normally so that the engine keeps on running or if the idle valve closes rapidly so that the engine stalls. If RPMdots stay the same, how can changing the RPMdot values help?

However I only got these cranking issues after updating from 1.5.0 to 1.5.1-beta, so it definitely has got to do something with the engine states.
Attachments
Bildschirmfoto 2017-06-05 um 10.21.36.jpg
current settings
Bildschirmfoto 2017-06-05 um 10.21.36.jpg (94.69 KiB) Viewed 445 times
David_G
Helpful MS/Extra'er
 
Posts: 78
Joined: Wed Apr 02, 2014 1:14 am

Re: MS3 pre-1.5.1 beta 2 firmware released

Postby R/TErnie » Mon Jun 19, 2017 12:35 pm

bump I have this same issue now.
R/TErnie
MS/Extra Newbie
 
Posts: 8
Joined: Fri Jun 02, 2017 3:25 pm


Return to MS3 Development

Who is online

Users browsing this forum: AbatelliCristian and 2 guests