Spark plug #64 on an 8 bit little endian system? Kudos!
|
Originally Posted by Joe Perez
(Post 983151)
magical rings made from unicorn horn and pixie dust
MX-5 Miata Forum - View Single Post - Question about Turbos
Originally Posted by Braineack 2/11/13
I already knew that a turbo is an "impeller" that spins a "fan" that blows magical pixie dust with energy "harnessed" from the horns of unicorns into the motor to make power.
|
Originally Posted by timk
(Post 983209)
Spark plug #64 on an 8 bit little endian system? Kudos!
I honestly debated with that. At work, all of our SSI stuff is big endian, however it winds up displaying as though it were little endian when viewed on a logic analyzer, so the end result is the same (read from left to right.) On the other hand, most humans are accustomed to reading binary in big endian left-to-right when presented in print, and the clock on my shelf displays in this format as well. |
I don't know if this is still relevant to the current direction of the thread, or if it is precise enough for your intentions, but here is a spark map that I put together to emulate the OBD2 computer's indications on my 1997 1.8L California car: https://www.miataturbo.net/attachmen...spark_rev2-png
More background on it can be found at the original thread: https://www.miataturbo.net/megasquir...=tuning+octane |
/\ That's very interesting and still very relevant to this thread, thank you for posting.
|
What the heck is up with the -10 degrees of timing in the bottom left corner. The only time I've ever seen negative timing like that is when I was trying to get the formula car to idle below 4 grand with the shitty intake manifold that leaked like a sieve.
|
I don't think the car will even hit those areas at idle so probably doesn't matter?
|
it's just 10° After TDC. No biggie.
If we look at 750RPM (typical idle speed) and 10°BTDC (oem timing at idle), it takes 25° or 5.434ms for the flame front to reach 15°ATDC, or about 2mm into the downward stroke. 15°ATDC is an assumption of where the flame front is hitting for this comparison Since that time never changes we can figure that within the latency of 5.434ms for the spark to ignite the flame and hit the piston since at 500RPM the crank rotates one degree in 0.33333333 milliseconds. At 500RPM 5.434ms is about 16° of crank rotation. So if we spark at 10°ATDC, then the flame front has moved to ~26°ATDC. This should put the piston top maybe ~4mm into the downward stroke, so less power should be outputted at this time. if you figure at 6,000RPM it takes only 0.02777ms to move the crank 1°, you understand why we have to spark much sooner 35° vs. 10°. That's only 1.3885ms to get to 15°ATDC. I know I did this flame front math wrong, but you get the idea.This is possibly an effort to stabilize the motor if the RPMs drop that low. If you advanced the timing when the RPMs dropped, it would increase the power and increase ultimately bump up the idle speed. I dont believe the stock ECU uses timing control like my MS3Pro to help control idle speed, so I'm assuming it's a way to allow the idle valve ot have greater effect at low rpms. |
Originally Posted by jnshk
(Post 983605)
(map)
|
2 Attachment(s)
Huge jump in timing from 1000-1200 rpm, 25-42 kPa. That is probably not the static table in the ECU, but observations made, with AC and idle compensation included. Such a static table will cause severe idle instability.
https://www.miataturbo.net/attachmen...1&d=1361998303 |
Jason is correct. The table was compiled/interpolated based on observations of OBD2 polling, and around idle there was some compensation done to stabilize things between A/C off (low load) and A/C on (heavy load), which is also why it is scaled somewhat non-uniformly so that I could isolate some key areas around idle and cruise.
The stock computer calculates spark based on rpm and MAF load (I believe) and possibly a few other factors. Since the MS is configured differently, this was my best interpretation at emulating it in effectiveness. When I was testing it out, the readings synced up quite well between MS and OBD2. Note on the negative timing cells -- these cells were basically areas where the car was struggling to not stall. Braking to nearly 0mph with the transmission in gear and crawling along at low speed, high gear, throttle mashed open. |
2 Attachment(s)
Joe,
What are you seeing as far as knock with your knock sensor? The following is my table that I have been tuning out knock peaks by lowering timing. Mine is much more conservative now that I have a knock module. I need to check my hardware latency as it is set to 21 microseconds. https://www.miataturbo.net/attachmen...ine=1362504941 |
Originally Posted by djp0623
(Post 985773)
What are you seeing as far as knock with your knock sensor?
|
Originally Posted by Joe Perez
(Post 985774)
Knock sensor? Bah. A Jedi craves not such things.
Luddite :fawk: ;) |
he has a 1.6
doesn't even have a knock sensor. and he probably cares not about it enough to rig one up lol |
luddite is right. drag your ms paint white pre-paste image to a tiny rectangle and THEN paste your graph. we dont' care about 3/4 of the content of that bs.
|
Originally Posted by Joe Perez
(Post 985774)
Knock sensor? Bah. A Jedi craves not such things.
|
Originally Posted by y8s
(Post 985888)
luddite is right. drag your ms paint white pre-paste image to a tiny rectangle and THEN paste your graph. we dont' care about 3/4 of the content of that bs.
|
Although the knock peaks are responding to reducing the timing. I'm wondering if I'm tuning out peaks that represent negligible knock. Unfortunately there are no clearly defined knock thresholds that we have to follow.
What hardware latency are others running on the ms3x? |
1 Attachment(s)
Originally Posted by emilio700
(Post 985894)
This is not the flame front you are looking for.
https://www.miataturbo.net/attachmen...ine=1362505409 |
All times are GMT -4. The time now is 12:16 AM. |
© 2024 MH Sub I, LLC dba Internet Brands