MS3 pre-1.5 alpha 4 released

[muythaibxr]

I would probably try to make the thresholds a bit lower. The slow one matters more since that is the main thing keeping you out of idle.

Thanks for the tooltip reminder, those will be in the next alpha.

[nismoautoxr]

I'm getting the gist now and I'll say that this code is impressive. I slept on it and logged this mornings drive and did a few throttle snaps in neutral to get the big accel and decel number then some wfo pulls in 4th and then some decel from 6k down to 1k to get some numbers there on the map load kpa . I ended up with sd=-600 fd=3600 fa=10000 sa=1500 decel kpa threshold of 22kpa and a tpsthreshold of 2. I'm hunting a hardware,wiring or interference problem with my tps signal is why I went 2% there.

[muythaibxr]

What is it doing to make you call it impressive. It is funny because the code is maybe 20-30 lines to determine state, and I removed code and settings in the features that depend on it, and it works better than before.

[nismoautoxr]

I think it eliminated some potential traps but I have discovered some problems with CLIDLE and over run possibly. On my car it seems to not be referencing the initial duty cycle table. It's adding like 6% over what I have in the table. It works as expected when you set it to last known value. Over run doesn't seem to be respecting the rpm dot setting for fuel return below to 2000 rpm on my car. It comes in and out . I have a log of the idle situation but no of the overun.

[muythaibxr]

I have some fixes in IIRC that didn't make this alpha for idle. Post the log, I will look tonight to confirm that my changes fix the idle situation.

[nismoautoxr]

Here ya go . It responds to raising and lowering the initial values table but it just doesn't put the duty where its told to. I doubt you will see this in that log but crank to run taper seems to be broken too.

[muythaibxr]

I will look. Crank to run is working on my car, probably fixed at this point.

[nismoautoxr]

What my car seems to be doing is using the initial duty table values as the crank duty . When I change my initial values then my crank duty cycle follows that . Try it out and you will see its something screwball going on there .

[nismoautoxr]

Ok I figured out the issue with crank to run taper. it works fine when the clidle setting is last known value. If you try to use the initial value table then the crank to run taper is busted. it immediately dumps the duty down to the initial table lookup with no delay or taper. Here are the msqs and the logs showing this . I think its been broken for a while too.

EDIT : I attached the tune and I tried to attach the tune both ways but it wouldn't let me attach that man but the only change was that setting in clidle to use last known value or use the initial value table.

[muythaibxr]

will take a look when I can.

[nismoautoxr]

will take a look when I can.

Thank you Ken.

[KaPower]

I tested pre-1.5 Alpha 4 over the weekend. I tested vss% based traction control for the first time as well (jut installed a front & rear wheel speed sensors).

The logs show that boost duty cycle reactions are potentially not functioning as intended.

Boost duty cycle hit's 242% and boost 30.2 psi while in first gear after the launch.

Traction Control boost reaction was set @ -100%, @ 50% slip. After recognizing an the issue, I set the boost reaction curve to zero for a couple launches, and added 100%+ d/c for the last launch of the day (all logs are individual and available by request). Boost reaction set @ "0" seemed ok, not sure what happened on +100% launch, boost duty % did not look quite right. MLV does not have options to see traction boost duty reactions, all I could look at is the actually DC.

-Jason M

[jsmcortina]

That's a boost reduction curve is it not?

i.e. new boost = target boost - traction_boost_cut

So by specifying -100% you are adding to the duty cycle. (i.e. subtracting a negative number is the same as adding.)

EDIT: I got this wrong from memory.
The code adds on the boost change from traction.

James

[KaPower]

James, this was with the defualt setting. I assumed it was duty cycle % reduction. I.E. 100% of 40% duty = 0% or 50% 0f 40 = 20%.

My duty cycle changes based off throttle postition and RPM. I don't think I can tune to my wastegate spring under all conditions. Perhaps I could get close. How would a proposed method of tuning boost reduction work without risk of over boosting?

From Tuner Studio.

Sets the amount to change the boost duty by based on the amount of wheelspin multiplied by how long.

[jsmcortina]

I've tested this and confirmed that there is a bug, the boost duty is going negative and wrapping back to a positive number incorrectly.

This is resolved for the next alpha.

James

[KaPower]

Thank you for the quick response! I'am looking forward to testing the next Alpha.

[KaPower]

Not sure that this is an actual Megasquirt problem, but I figure it's worth mentioning. I've observed, when viewing the TPS signal on my datalogger (RaceCapture Pro mk2) via MS's Can Dash Board mode, a huge fluctuting value @ Idle (0%-6xxx%), and only while the car is running. I think at times my TPS value goes negative, and fluctuates a bit (not to stray off point, but - possible mechanical issue wih linkage or slop between the tps and throtle shaft, I know I need to look into this futher...). By calibratiing my min tps to always read a positive number, i.e. 2-3% @ full closed position with engine off, the datlogger seems to register TPS correctly. MAP, CLT, RPM all read correctly, from what I've observed.

-Jason M

[AbatelliCristian]

I attach log and msq.
If I use log cranck & cam I see correct cranck and cam.
If I use subaru 36-2-2vvt I dont see cam.

[nismoautoxr]

Not sure that this is an actual Megasquirt problem, but I figure it's worth mentioning. I've observed, when viewing the TPS signal on my datalogger (RaceCapture Pro mk2) via MS's Can Dash Board mode, a huge fluctuting value @ Idle (0%-6xxx%), and only while the car is running. I think at times my TPS value goes negative, and fluctuates a bit (not to stray off point, but - possible mechanical issue wih linkage or slop between the tps and throtle shaft, I know I need to look into this futher...). By calibratiing my min tps to always read a positive number, i.e. 2-3% @ full closed position with engine off, the datlogger seems to register TPS correctly. MAP, CLT, RPM all read correctly, from what I've observed.

-Jason M

May not have a thing to do with your issue but I was seeing some similar issues with mine and loosening the map sensor screws and nuts resolved my problems. cheers and good luck with it. I would notice mine the most when I was deceling.

[nuvolarossa]

EDIT: Loader updates to support older MS3s

A bit late...
this firmware loaded fine on a mid-2010 MS3/MS3x.
Checked also with miniterm and fw version is correct.