MS2-E based so bets are on that it will contain at least some significant parts of the old code and be in a similar style.8InchesFlacid wrote:Anyway, just curious what you all think... Does anyone have any idea what the code looks like?
Fred.
MS2-E based so bets are on that it will contain at least some significant parts of the old code and be in a similar style.8InchesFlacid wrote:Anyway, just curious what you all think... Does anyone have any idea what the code looks like?
Just another quick update on the ms3. Here is the planned software roadmap:
MS3 1.0 code:
The MS3 operates in 2 "modes." There is an "upgrade" mode which has the following characteristics:
-Direct plug-in swap for MS2 daughtercard
-Compatible with MS2 wiring
-Same single spark output
-Same injector outputs
-Compatible with MS2/Extra wiring
-Same six spark outputs
-Same injector outputs
-Same switch inputs
-USB connector (USB->serial)
-On-board SD device datalogging (per ignition/injection-event resolution)
There is also an "MS3X" mode:
-Uses expander board for more I/O
-8 channel sequential fuel
-8 channel coil-on-plug (logic level output)
-Trim tables for fuel and spark (6x6)
-Minimal on-board wiring 'mods' (no more wiring mess everywhere)
-Pre-defined outputs for certain features
-Individual injector parameters with opening-time curves
-Hardware PWM outputs for idle, boost, VVT, etc (only supported on PWM outputs via the expander board)...
Both "upgrade" mode and "standard" mode will support everything that ms2/extra supports. In addition, X-tau will be added to make upgrading from ms2-standard easier, and MAF support and fuel perturbation mode will be added as well from the ms2/standard code (although it may not look exactly the same). In addition, due to certain paging limitations in megatune, we will be requiring the use of Phil Tobin's TunerStudio. One point of interest is that due to the organization of RAM and flash, the burn-stumble from ms2/extra is now gone.
MS3 2.0 code:
-Angle clock will be used for timing ignition and fuel events (and other events)
-More accurate at scheduling events (especially in acceleration and deceleration, hoping for 0.1 degree accuracy to 16667 RPM based on a 1 microsecond tick rate on the XGATE)
-Essentially a clock that ticks in degrees instead of time... counts from 0 to 719.9 degrees in tenths of a degree
-Allows for the integration of post-2.0 model-based features (as many as we can add with a CPU of this speed)
-Will incorporate alpha-beta-gamma for predicting the number of microseconds per angle-tick
-Up to ten injector outputs (8 on MS3X, 2 on V3)
-Staged injection, water injection, methanol injection on spare injectors
-Up to 14 spark outputs (8 on MS3X, 6 on V3 board)
-Progressive nitrous control
-Anti-lag (becomes easy to do with the angle clock)
-Knock-windowing (becomes easy to do with the angle clock)
-Special Rotary engine mode with support for sequential-staged injection and FC, FD, Renesis, 3-rotor COP and 4-rotor COP modes
I'm sure there will be many more cool features that having an angle clock will make easier. I have attached a loose flow-chart (could change as I implement the angle clock) for how I plan on having the angle-clock work.
What's left to do before....
Beta?
-Complete work on the monitor
-Make sure all porting from MS2/extra I/O works, including all I/O (both upgrade mode and MS3X mode I/O)
-Make sure all porting from MS2/extra features work (regression testing of the whole firmware basically).
-Upgrade mode only
-Get SD-card datalogging working
-Choice between starting logging as soon as a card is plugged in and using a toggle switch to start it
-SD card must be formatted on PC
-Any existing log files will be skipped.
-All space on the device will be taken by pre-allocated files for logging speed purposes
-Pre-allocated files will be relatively small in order to make them easier to load in a log-viewer
-One of the v3's built-in LEDs can be repurposed to give datalogging status
Hardware Release?
All of the beta features plus full support for the MS3X expander board.
That's all I can come up with for now. Keep in mind that while we've had a few engines running, there is still a lot of work to do. Stay tuned for more info.
Ken
You must be thinking of Mazda engines and other modern designs that aren't old V8's and siamese A series engines ;-)8InchesFlacid wrote:I never really got what a "trim table" is.. So, you have a map, and it sucks, so you add a table to tweak what's in the table, instead of just fixing the table? This can't be right... because it's inane. :-)
There's actually not much to say on it because it's actually quite simple (in principle).Fred wrote:Jean, when are you going to do a write up on the logic behind your code? Keeping in mind that you own that code, of course.