MS3 pre-1.1 alpha 17 released

[jsmcortina]

Main changes since alpha16
New initial value table for CL idle.
PWM idle voltage compensation curve added.
Water inj wasn't showing "power cycle required" in TS.
Subaru 6/7 fix from MS2/Extra.
New experimental "accel-pump" style AE.
Various ini changes to use new(ish) TS features.
Basic Trigger sparkcut revlimiter fix.
Serial errors weren't using newserial response codes for error messages. Remove them from ms3_conferr.s
Allow MAP sampling window to span trigger and report impossible settings.

As usual, be sure to use the latest beta TunerStudio. 1.19 or higher is required ( http://www.efianalytics.com/TunerStudio/beta/ )

The zip is available to download at : http://www.msextra.com/doc/ms3/files/al ... lpha17.zip

The new-AE has had limited testing. Free-revving testing seemed good using the provided tpsdot settings on my Cortina, but out on the road it wasn't quite so happy. This is an experimental feature intended to offer a simpler standard accel enrichment (if it can be made to work.) It is modelled on the accel-pump of a carburettor and only squirt fuel while tps (or map) are changing.

James

[elaw]

Main changes since alpha16
PWM idle voltage compensation curve added.

Thank you!

[muythaibxr]

A quick note on the new CL idle table feature:

To use it, all increases in load must be fed forward. This means using fan control, AC idleup, and voltage compensation to make sure all loads are fed forward and compensated for.

IF you have an ECU-controlled alternator (using it with a circuit to control it like on early 2000's miatas), this feature is unlikely to work for you. I have alternator control with feedforward in the works for the next alpha to account for this.

Ken

[muythaibxr]

One other issue:

With new AE, the engine map accel/decel bits will still trigger when set to 100% TPS AE, and the engine TPS accel/decel bits will still trigger when set to 0% TPS AE.

This does not actually affect the final AE value injected.

This is also already fixed in our CVS repository, and the fix will be in alpha 18.

Ken

[ragepower]

A quick note on the new CL idle table feature:

To use it, all increases in load must be fed forward. This means using fan control, AC idleup, and voltage compensation to make sure all loads are fed forward and compensated for.

IF you have an ECU-controlled alternator (using it with a circuit to control it like on early 2000's miatas), this feature is unlikely to work for you. I have alternator control with feedforward in the works for the next alpha to account for this.

Ken

That is for the CL idle activated by VSS issue you talked about?

[muythaibxr]

No that's been in since 1.0 I believe. This is the table-based initial value.

Ken

[bubba2533]

Is the new AE an option?

I just want to make sure I can use my AE settings from alpha 15.

Thanks,
Branden

[93white3400z]

Is the new AE an option?

I just want to make sure I can use my AE settings from alpha 15.

Thanks,
Branden

Yes

[djp0623]

This version worked fine for me. I loaded it last night and did a little over 100 miles. I like the taper option in seconds. No problems to report

[Keithg]

I finally updated from alpha 10 today. I was waiting to make sure that the new Serial bugs were mostly worked out as I have been *very* busy.

The only issue I noted was that it would *not* burn initially. I then fired up TS to make sure it would use the USBSerial port and work with Alpha 10. That worked then I shut down TS then tried a burn and it all went fine. I did not use BT Serial to burn, but want to try it again. I did this a while back and was able to get it to burn but it took a long time. Any thoughts about if speed may be improved with the new program loader?

The only other issue was the new knock windowing output (I do not yet know what this is for) was using the same port I was using for tach out. I turned that off and it loaded the Alpha 10 MSQ and started right up. I did not drive it, but I feel it will be 'just fine'. Now I just need to catch up with the changes. It looks like my oddball spark dwell still works fine which was the one thing I was concerned about.

Also the new TS (Beta 19) works nicely with my BT Serial for tuning under Linux. I'll make sure to pass kudos to Phil on that on the TS forum. I know he has been working on that recently and it looks like it is much better about disconnect/reconnect.

KeithG

[jsmcortina]

The only issue I noted was that it would *not* burn initially. I then fired up TS to make sure it would use the USBSerial port and work with Alpha 10. That worked then I shut down TS then tried a burn and it all went fine. I did not use BT Serial to burn, but want to try it again. I did this a while back and was able to get it to burn but it took a long time. Any thoughts about if speed may be improved with the new program loader?

When you say "burn" are you meaning "load firmware"?
What was happening initially ?
Are you seeing speed issues with the firmware loader?

James

[Keithg]

The only issue I noted was that it would *not* burn initially. I then fired up TS to make sure it would use the USBSerial port and work with Alpha 10. That worked then I shut down TS then tried a burn and it all went fine. I did not use BT Serial to burn, but want to try it again. I did this a while back and was able to get it to burn but it took a long time. Any thoughts about if speed may be improved with the new program loader?

When you say "burn" are you meaning "load firmware"?
What was happening initially ?
Are you seeing speed issues with the firmware loader?

James

yes, I meant loading the firmware. I really do not know what was going on. I tried 2 x and it did not get a response from the wakeup command. I looked in the /dev directory and found the /dev/ttyUSB0. I then ran ts on the usb serial and it connected and worked. Then I tried again and it loaded.

Keith
Pretty baffled as well. I got it loaded, though.

[AbatelliCristian]

I have problem with fili INI. When update tuner studio I see this message "Invalid row in ini file"

[jsmcortina]

I have problem with fili INI. When update tuner studio I see this message "Invalid row in ini file"

Which particular row? and have you updated TS to 1.19 as directed?

James

[Keithg]

Don't know if this is firmware or logging related. I captured a data log using Phil's Shadow Logger this morning. I had some 'lost sync' events in the log, but no drivability issues on the drive in. Is it possible that these are serial glitches?

I got a call during the logging and it had a number of errors during the call (dropped packets?) - Lost sync on 2 events Reason 102 and 137. My guess is that this is a phone/logger issue.

It had one other error about 5min 32 sec into the drive - Lost Sync Reason 65. I have no idea about thsi one. I was creeping along on the way to work and felt nothing odd during the drive here either.

Keith

[jsmcortina]

Not easy to see which is count or reason when they are the same colour. The lost sync count goes up in ones, and only goes back to zero if there's a reset.
However, in your log there it looks like count goes from zero to a large number and then back to zero, that looks like false data.

If that is what you are seeing, the please post the info for Phil to review as it would likely indicate data corruption within the phone app (I think?)

James

[AbatelliCristian]

I have update TS and is all ok.... Thanks

[hassmaschine]

Not easy to see which is count or reason when they are the same colour. The lost sync count goes up in ones, and only goes back to zero if there's a reset.
However, in your log there it looks like count goes from zero to a large number and then back to zero, that looks like false data.

If that is what you are seeing, the please post the info for Phil to review as it would likely indicate data corruption within the phone app (I think?)

James

having used shadowlogger for a bit, that looks like comms dropouts to me.

[ranster]

Loaded and briefly tested. so far so good
New initial value table for CL idle works as published and now working with VSS activation is just great! (i would grey out the daspot adder in TS as i do not see a purpose for it anymore)

Great job! thanks

[Keithg]

Loaded and briefly tested. so far so good
New initial value table for CL idle works as published and now working with VSS activation is just great! (i would grey out the daspot adder in TS as i do not see a purpose for it anymore)

Great job! thanks

Where is this documented. I am also running CL idle and would like to test this new feature and would like to read up on it.

Keith