Most of these groups have an 'Input', or inputs, to their task, and, ususlly a single 'output', sometimes with branches. When you split these thousands of parms into their perspective groups, it starts to become clearer. It makes it very confusing, when looking at 7,000+ paramaters inside an engine in this way, when instead, it needs to be looked at in terms of 'Groups'. Indeed what is going on in most of them these days, is instead of one big 'program', there is in fact multiple applications running at the same time (think of windows, and several desktop apps running side by side). I think where a lot of people get lost in these newer ECM's is that they do not look at them as a multitasking platform. The combustion manager is actually the application in the ecm that does all the work firing the cylinders, changing fueling and charge pressure rates, etc. The frac command is then sent, along with any derates (combustion changes in this case), to the all mighty combustion manager, where other factors of the engine are sent as well. From there it goes through some upper/lower limiting filters, gets changed based on exhaust temp, etc. The initial value plucked from any given table is based on the current speed (rpm) and fueling rate. It is derrived mainly by lookup tables, such as the 6 tables representing each cylinder. This value can be monitored inside calterm via paramater during a monitoring session.
The EGR inside the ecm of the CM871 is calculated using an overall FRAC value (measuring from 0.000000 - 1.000000).
0 kommentar(er)
