MS3 pre-1.5 alpha 4 released

Post by **jsmcortina** » Fri Apr 08, 2016 6:47 am

To announce the release of "MS3 Pre 1.5 alpha 4"
Who should use this code?
Experienced users wanting to test the new features.

Who should not use this code?
New or casual users – please use the current release code instead – see the Downloads page linked above.

Main changes since the pre-1.5 alpha 3 firmware
(A number of these changes were made in parallel to the 1.4.x code stream.)
Bug fixes:
Make 'soft' config error behave as expected.
Launch control/nitrous checks launch-in, not launch on.

New / changed features:
Add Nissan QG15 from Dimitris. (untested)
SS1 can be calculated from VSS1 (shared input.) Possibly grainy calc currently.
Get 128 byte SDcard logs reading back in TS.
Add CBR600RR even fire 4-cyl variant of RC51.
Include GPS enable bit in byte 0x18 of SDcard logs.
Add automatic 11bit CAN acceptance filters.
Add automatic 29bit CAN acceptance filters.
Allow 29bit Megasquirt-CAN to be disabled.
Allow CAN receiving of 29bit messages.
Allow CAN baud rate to be changed to 250k or 1M.
Add CAN wideband support for AEM UEGO, ECOTRONS ALM, AEM 30-0300 'X' UEGO and Generic.
Re-add HE351 CAN broadcast option. (250k baud.)
Change LS1 sync to avoid checking cam near edges.
EDIT: Loader updates to support older MS3s

Minor / internal:
Extend config error space.
Make num_inj_pri a local variable.

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

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

Some more information on the dome feature is available is this temporary PDF: http://www.msextra.com/doc/pdf/Dome-sup ... -12-02.pdf

Upgrading users are advised to enable the "old baro calc" for backwards compatability.

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 2.6.x is REQUIRED.

Note that the firmware loader in TunerStudio 2.9.x does not yet work with this pre-1.5 firmware, please continue to use the included firmware loader.

subwoofer · Post by **subwoofer** » Mon Apr 11, 2016 12:57 am

Will the included firmware loader work on the older MS3s?

Post by **jsmcortina** » Mon Apr 11, 2016 1:31 am

subwoofer wrote:Will the included firmware loader work on the older MS3s?

That's the idea, yes.

James

subwoofer · Post by **subwoofer** » Mon Apr 11, 2016 2:18 am

I'll give it a shot one of the coming days then. I couldn't see it mentioned in the change log, hence the question.

juansh2385 · Post by **juansh2385** » Thu Apr 14, 2016 10:59 pm

Well I want to report that the loader worked like a charm. I have a question during the process of erasing the flash I notice some error message but the loader firmware loaded any way is this expected? the error say misalign .. can not remember the rest.

Ken I have question/suggestions regarding the engines states features.

For what purpose do you intend to use the slow/fast accel/deccel?

what do you define as slow acceleration?

I ask because am having a hard time setting the the slow setting low enough in order for the code to detect a slow constant acceleration of the engine with out affecting the Idle state.

To clarify do you expect the code to detect constant normal driving acceleration as slow accel?
if I select 20 rpm/sec the indicator detects normal slow acceleration but if am at idle with the air conditioner on when the compresor activates/deactivates it the change in rpm turns on/off the idle indicator and I think that is not the point at 350rpm/sec the drop from the air conditioner do not take me out of idle states but the code does not detect slow acceleration while driving normally.

Post by **muythaibxr** » Fri Apr 15, 2016 4:16 am

The slow decel state is really just there to help keep the code out of idle mode when it shouldn't be in idle mode. FYI I have it set to -500 on my car. I have some bug fixes coming around closed loop idle that will allow that setting to be set lower.

Right now nothing is directly tied to the "slow" states, but for example if you are "WOT" (not yet added) and "slow accel" you might want to pull timing after several seconds. This kind of feature will be possible with engine states.

juansh2385 · Post by **juansh2385** » Fri Apr 15, 2016 5:33 am

No problem i just giving you feed back of my setup.

idle indicator is on while on idle and cruise indicator is on while driving. slow acceleration indicator just blips if i take off from idle but during cruising (so this part is working as intender ) with the current set up i can not get the acceleration indicator to stay on while acceleration let say from 45 mph to 60 mph at the hi way.

Anything else that I should testo for now?

I think I can also report that the car is working normally on the code at least during the last 2 days

Post by **muythaibxr** » Fri Apr 15, 2016 11:42 am

IT sounds like some of the settings are not right, but at the moment since nothing is really tied to the acceleration parameters aside from keeping you out of one of the other states, there's not much else to test.

Ken

Sam280Z · Post by **Sam280Z** » Sat Apr 16, 2016 10:43 am

I just tried to install this firmware and have encountered strangeness - something to do with the CAN system.

I evidently have an early MS3 that the earlier "new" firmware loaders would not work on. The FW loader supplied with this release appears to work, although it does throw a few errors that it seems to resolve on its own. I'm also using the CANEGT module with LC1 EGO over serial.

The first time I loaded the firmware, I got the regular msq warnings common to an upgrade - but everything seemed to work; that is everything but the AFR gauge which was stuck at 7.4. I did find that the master CAN switch was off, so I turned it on. This had no effect on the AFR gauge. I also checked the RTC, and it had Jan 2000 as the MS3 time and I could not update the time. As far as I can tell, my CAN settings are all correct for my system and are what they were when it was functioning fine under the old firmware. I started the car and seemed to run fine with the exception of no AFR gauge.

In trying to get the AFR to work, I reloaded the firmware (twice now) and each time it seems to load with no problems. But now I am getting a config error: "can transceiver broken? wrong baud rate?" when I start TS. I have not changed the settings. The car will not start now.

Help? Ideas? Am I doing something stupid?

Configerror.msq

Edited to report actual incorrect AFR reading.

Post by **jsmcortina** » Sat Apr 16, 2016 11:35 am

Wait 15 seconds. The CAN transceiver config error is a "soft error" and normal operation resumes.

James

Sam280Z · Post by **Sam280Z** » Sat Apr 16, 2016 4:51 pm

Waiting 15 seconds addresses the reported error and allows the car to start only if TS is not connected when MS is switched on. AFR is still stuck at 7.4. I didn't check the RTC, but I can if it would help. It appears that CAN is not working at all for me.

racingmini_mtl · Post by **racingmini_mtl** » Sat Apr 16, 2016 6:09 pm

You might want to try my port scanner. This will scan the serial ports on your pc and check for all the CAN devices. Note that this is a Windows-only program.

Jean

arran · Post by **arran** » Sun Apr 17, 2016 12:10 am

Just updated to 1.5a4. The built in loader worked (the 1.5a3 firmware and loader would not work).

Initially the car would not start, even after a couple of power cycles. The EGT gauges were displaying 0. I left it for half an hour and then it started, and EGT were working.

Am having to re-tune the return to idle.

The crank to run taper does not seem to be working, msl attached

2016-04-17_16.26.07 crank to run.msl

Post by **muythaibxr** » Sun Apr 17, 2016 5:06 am

What did you update from?

arran · Post by **arran** » Sun Apr 17, 2016 5:27 am

Sorry, 1.4.1 b3

Haven't driven the car yet, but have been through a warm up cycle in the driveway working on the return to idle. Still working that out. It seems to be running the engine (13b rotary) well. Keen to try out the traction control, I tried it out on 1.4b3 briefly and it didn't seem to be doing anything. I noted that 1.4b5 and 1.5a4 mention something in the release notes about launch_on and launch_in mix up.

Post by **jsmcortina** » Sun Apr 17, 2016 6:16 am

arran wrote:Keen to try out the traction control, I tried it out on 1.4b3 briefly and it didn't seem to be doing anything. I noted that 1.4b5 and 1.5a4 mention something in the release notes about launch_on and launch_in mix up.

That's unrelated.

James

Sam280Z · Post by **Sam280Z** » Sun Apr 17, 2016 6:49 am

racingmini_mtl wrote:You might want to try my port scanner. This will scan the serial ports on your pc and check for all the CAN devices. Note that this is a Windows-only program.

Jean

Thanks! I ran it and got the following:

Port: COM4
No device detected

Port: COM1
MS3
CAN ID 00: MS3/Pro/Gold

Port: COM3
Unknown device

I'm going to go back to the release firmware and re-verify that everything was working as I remember.

Post by **jsmcortina** » Sun Apr 17, 2016 7:55 am

Sam280Z wrote:I'm going to go back to the release firmware and re-verify that everything was working as I remember.

Good plan.

James

racingmini_mtl · Post by **racingmini_mtl** » Sun Apr 17, 2016 8:09 am

The port scanner does confirm that there is a problem with the CAN bus communication but it can either be the firmware or the hardware. Go back to the previous firmware and run the port scanner again to see if you do see the CAN-EGT that way. You can also connect the CAN-EGT directly to the pc through the USB port and the port scanner should see it.

Jean

Sam280Z · Post by **Sam280Z** » Sun Apr 17, 2016 8:37 am

I went back to 1.3.4. I attempted to use the FW loader supplied with that release with the boot jumper on. It appeared to work, but when I opened TS, it would not see that firmware was loaded. Tried a couple of times to no avail. So I tried the loader supplied with the pre1.5a4. Now TS sees the firmware. The RTC appears to be working again, but the EGO is not - it only reads 7.3AFR now. (Although in the process of updating firmware definitions, it looked for a second like it was - TS was showing 19.9 AFR for a moment.)

Additionally, the CAN VSS, Gear, EGO dialog has values of 7 for the Remote CAN Id and Remote CAN Table under CAN VSS and gear selection. I have no VSS or gear CAN device, but there is nothing to de-select or turn that option off.

When I run the port scanner, I get:

Port COM4
No device detected

Port COM1
MS3
CAN ID 00: MS3/Pro/Gold

Port COM3
Unknown device

Megasquirt Support Forum (MSEXTRA)