MS3 pre-1.4 beta 12 released

[jsmcortina]

and what about the can com?

Native lambda is not reported by the Megasquirt, so you can't pull it directly over CAN.

Start a new topic and provide a lot more detail for your other question. As you are interfacing to a non-Megasquirt product you'll need to provide CAN analyser data to show what is or isn't happening.

James

[jsmcortina]

this code version does not seem to like V8 2 stroke
i have fully seq but keeps giving an error when cycling power

Do you have a timing diagram for your engine ? I'm not that familiar with how V8 two-strokes are phased.

There's a config error because the code wants to fire 8 discrete fuel/spark events in the 360 degree engine cycle. That's not possible with a 60 tooth crank wheel.

James

[sjf911]

That looks like a CAN issue. On my bench test setup (which is slightly different from a normal MS3-IOx setup), I do get that type of error just after loading a new firmware version to the MS3. I have to either keep the setup powered off for a while or short the CANH/CANL lines together (with the power off) for this error to go away. You should not have to do so but it's worth a try.

Once this initial issue has been cleared up from my setup, I have absolutely no issue with CAN comms and don't get the error. That goes for beta 11 and beta 12.

Jean

Thanks Jean, I tried letting it sit for hours with power off, didn't work, and then even with shorting the CAN wires together I still get the same error.

[racingmini_mtl]

Did you check if you have continuity between the CAN header on the IOx and JS6 and JS8 on the MS board? And does it go back to working if you go back to the old firmware?

Also you could try running the port scanner (if you haven't done so): http://forum.jbperf.com/viewtopic.php?f=2&t=1282.

Jean

[sjf911]

Thanks Jean, it does work if I go back to pre 1.4 beta 1. Port scanner shows MS3 and then multiple CAN channels. It doesn't identify the CAN inputs as IOx though.

[racingmini_mtl]

Thanks Jean, it does work if I go back to pre 1.4 beta 1. Port scanner shows MS3 and then multiple CAN channels. It doesn't identify the CAN inputs as IOx though.

What do you mean? Can you post a screen capture? Also, is that for both alpha 1 and beta 12?

If you're using an FTDI USB-serial adapter or the USB port on the MS3, you need to make sure you set the latency timer to 1 in the device manager (in your computer settings). I recently noticed that the port scanner gets confused if that is left to the default 16.

And it's also a good thing to change that setting because it will speed up a bunch of other things too.

Jean

[sjf911]

Thanks Jean, I couldn't find anywhere to change latency. I ran port check again on beta 12 and it showed this where first time it listed about 10 CAN devices without identifying IOx.
Also, when attempting to load the project last, it gave me a new conflict and warning. I could see in the background that previously TS wasn't seeing the sensor outputs from the IOx, now suddenly they are visible on the dash.

[jsmcortina]

Thanks Jean, I couldn't find anywhere to change latency

For FTDI devices, there's an additional box on the advanced port config panel. Similar to the one shown in the manual:
http://www.msextra.com/doc/pdf/html/Meg ... .3-18.html

So:
Portcheck finds the IOx. TunerStudio doesn't.
Correct?

That doesn't immediately sound like a firmware problem.

Please enable "Debug Log Comm" and try to connect. Then zip and attach your TunerStudioAppDebug.txt file.

James

[sjf911]

Thanks James, I found the latency. Attached is the appropriate log I hope. Also, TS has no trouble with the IOx pre1.4 alpha 1 when I revert to it.

[racingmini_mtl]

You have an old version of the IOx firmware. I haven't gone through the details of the debug file you posted but there might be some issues with TunerStudio and/or the MS3 firmware that expects some responses that that old version cannot give.

The solution would be to upgrade your IOx firmware. It is not a bad idea to do so in any case because it gives you a lot more features and there are some correction to the code also. The latest firmware is available here and, if you don't know, you can see how to upgrade here.

Jean

[sjf911]

My DOS skills left me 35 years ago. I was able to upgrade the firmware but how to I fix the MSQ? In the projectCfg folder I have 2 MSQ files CAN1_pcVariableValues and pcVariableValues.

[subwoofer]

Just checking in to say that no issues have surfaced with beta12 with MAF.

[sjf911]

Jean, this is what I am seeing:

[jsmcortina]

Update the ini file for the CAN device - that message shows that it doesn't match.

James

[sjf911]

Thanks for the help, updating the IOx solved the problem.

[ashford]

i have a quick question? if i turn on noise filtering for cam input, does that apply to all 4 cam position inputs i have or just what is on the ms3x cam in

[jsmcortina]

Agreed on the Coyote VVT3. Seems that I disabled the debugging data in the ini file. The next release (due shortly) will have that re-enabled and then I can take a look at what's going on.

James

[AbeFM]

Looking forward to the next release. I'll probably run it and try to add what I can.

[jsmcortina]

Looking forward to the next release.

It was released last week.

James

[AbeFM]

That's what I get for checking my email on the road. Thanks for the update!