MS3 Basic error when selecting fields for SD card logging
 

https://cimg4.ibsrv.net/gimg/www.mia...c3eea05ec7.jpg

My car is a 93 with VVT swap running MS3Basic. Apparently my SD card logging feature by default only logs a few fields. When I try to add additional fields, this is the error message I get. Google isn't being helpful right now. Anyone know what's causing this msg ?

Thanks.

Too much data. Remove unnecessary channels from the log.

I gave him a list of 18 parameters to log for me. Is it not able to log 18 parameters? that's odd, because I've done way more before on other ms3's ( I think Sean has logged 20+ for me before)

That I don't know. I just know it's the same error I've gotten before that was remedied by removing channels. It looks like 55 bytes is the standard MS3 field size, maybe some of the calculations in the MS3 basic firmware take up more space than others?

You can upgrade the firmware to get more channels. It was in one of the changelogs.

Firmware 1.5+ allows way more channels.

Rev, have you moved to 1.5? If so, do you have a base map for reference for Engine States.... 1999 Miata? Or a screen shot of reference ES settings?

Related/unrelated, are you guys able to remove logged channels individually? I think there is a bug that makes it so you can't remove individual channels.

ahh, ok that's likely what it is. ok good to know, thank you

I don't think that's even possible. Each and every car has wildly different engine states settings based on rpmdot and how noisy it is/isn't. only way to make a "base" setting for that would be to set it really broad which really won't help much. IMO gotta dial in each car's ES every time.

Thanks all. I'll look into updating my firmware.

No, this would require that every single car we have tuned in the past for all the basemaps that have developed, return to base for a retune. This is not possible. Upgrade from 1.4.0 and work on the new settings.

Re-phrasing my question, because I'm slow on the uptake: Do you recommend I move to 1.5?

Have you used it some and seen no bugs that will give me issues?

I know you didn't ask me, but since you PM'd me the same question: I HAAAAAAATE engine states. On some cars it works fine, on some it's a total and complete nightmare. I cannot fathom why they implemented it. I see zero benefit from it
Other than that, no issues.

This will leave me not able to help others / contribute, as I remain on an old version. But I choose to be selfish here and just enjoy driving my car instead or re-tuning it.

Thanks.

For 90% of users out there, 1.5 has no real benefits over 1.4.

I agree with 18psi on this one, I see no benefit with the engine states system.

I use 1.5 on one car, 1.4.1 on all my others. Unless you like playing with all the latest and greatest. Stick with the 1.4 branch of code. I agree with the rest that engine states can be annoying to deal with. Once you get it tuned it, they can work nicely though.

Do you have a larger size selection available in the "log Data block size"? It's currently on 64 byte, and the error message seems to be suggesting that you need to select a larger size to allow more data. Not sure if it will work, but it might be worth a try.
Cheers,
Rusty

1.4.x only has 64 byte frames. There's an option to add audio but there's currently no hardware in place to do that.