MS3 pre-1.6 alpha 1 firmware available
10-25-2022, 03:47 PM
#2
Junior Member
Join Date: Jun 2017
Location: Pittsburgh
Posts: 46
Total Cats: 2
I gave this firmware a whirl a few weeks back, as I was super intrigued by the MAP based RPM limiter on launch. Do not flash this firmware. (05, ms3x diy).
There is a bug which grays out the internal knock module. But even working past this (as mentioned by the devs in the mse forums) my knock control was always triggering... With my thresholds set to 100% and my knock reading being ~9% (on all cyls), knock retard would fire straight to max. At one point it pulled more timing (-8 when I set the maximum to -5 if I recall) than I had configured to allow it - got it on video even.
Additionally at idle/below the min RPM limit, it would pull timing then give it back so fast it doesn't show (much) on a USB datalog, but it fires a programmable output I use (CEL on knock retard above 0).
Super curious to hear what the cause of this is, sounds like an interesting bug.
There is a bug which grays out the internal knock module. But even working past this (as mentioned by the devs in the mse forums) my knock control was always triggering... With my thresholds set to 100% and my knock reading being ~9% (on all cyls), knock retard would fire straight to max. At one point it pulled more timing (-8 when I set the maximum to -5 if I recall) than I had configured to allow it - got it on video even.
Additionally at idle/below the min RPM limit, it would pull timing then give it back so fast it doesn't show (much) on a USB datalog, but it fires a programmable output I use (CEL on knock retard above 0).
Super curious to hear what the cause of this is, sounds like an interesting bug.
Reply
0
0
10-26-2022, 06:32 PM
#3
Newb
Join Date: Dec 2011
Posts: 29
Total Cats: 6
I had a similar issue with spurious knock control activations - I logged an issue at msextra in the 1.6 alpha1 development thread.
Knock was activating when the logs showed I was well below the set knock threshold and the amount of knock retard hit up to 24 degrees when my max setting was 6.
I was getting pretty strong power drops due to the knock retard and the power delivery smoothed out once I disabled knock control.
No one else has reported having an issue with knock yet and I'm waiting for a response from the developers. I'm glad to see it wasn't just me and you are also seeing something odd.
Knock was activating when the logs showed I was well below the set knock threshold and the amount of knock retard hit up to 24 degrees when my max setting was 6.
I was getting pretty strong power drops due to the knock retard and the power delivery smoothed out once I disabled knock control.
No one else has reported having an issue with knock yet and I'm waiting for a response from the developers. I'm glad to see it wasn't just me and you are also seeing something odd.
Reply
0
0
10-27-2022, 01:02 PM
#4
Newb
Join Date: Dec 2011
Posts: 29
Total Cats: 6
Additionally at idle/below the min RPM limit, it would pull timing then give it back so fast it doesn't show (much) on a USB datalog, but it fires a programmable output I use (CEL on knock retard above 0).
Super curious to hear what the cause of this is, sounds like an interesting bug.
Super curious to hear what the cause of this is, sounds like an interesting bug.
If you get an opportunity, you should add your experience to the 1.6 alpha1 thread as well.
Reply
1
1
Thread
Thread Starter
Forum
Replies
Last Post
