CAN is a network aware protocol using as few as 4 wires although all implementations use 9 which when you are dealing with shielded signals is a major pain in the arse.
this leads to a various sample size for an event handler which shares the data model. As more signals are sent through the network each cpu has to keep up with the message size so each sensor gets tuned from a networking perspective
Networks can be taped. They can be injected. If an external controller detects on the network something is missing it can inject a calculated signal, detect if it sent a signal in error and stop doing that for a while and externally log the sensor before it tells you you should look into something on the car.
4 wires are TX and RX signals
CAN interface is impractical in its implementation
if you output tap the RX and validate against your local code to know when to fire. remote attached networked sensors that only alert the event handlers which run on two bluetooth attached iPads that elect which one is in charge. The two iPads are running native app or broken if necissary. They display
EMS Studio as the dash and ensure all of the necessary signals are present even if the remote sensor isn't present.
engine at predefined rpm shifts from 24x signal to 3x signal for performance reasons and that signal takes too long to process normally. This remote sensor can be queried by sending a request signal across the network to provide signal for a duration.
local validation code on the output device uses CAN decipering signals across those 4 wires.
GM DIS is first example on car already using the technology by pre processing the7x signal and converign it to 3x off board
what better place to put input signals like slap shifters that say lets upshift and we want it to happen asap.
event logger is waiting for any signal of the slap shift telling the `car` to do something unique like any good event handler deals with
Transmission control happens externally with a harness to the transmission which signals the network of a query interface to find the neutral safety switch status
lets say we want our event handler to detect throttle platee at 0 since this is a major event for the system
we need to bypass air since thats how I sit in trtaffic mostly on the brake. Idle air control through the existing valve is valuable. MAP, TPS, and TACH can be interpreted that we're idling but there is no reason to send these signals everywhere at every chance so we tune the network, and data logging usage by allowing for small documents to transmit.
need to add event handler for throttle plate position by time interval and time interval acceration
This type of logic lives at a higher level than the firmware. The entire design is to be able to tune event handlers for known conditions. I currently have an evap leak that I ought to fix, but a check engine light is a bit extreme for this.
normal cpu not utilized determining based off existing tables or at the oscellation. Event handlers become the slimed down versions of code.
gemsets or versions of the modules become available to each external controller.