uCANca

h1. Tour flows

As we have said, a flow is a [[magnitude]] (logical or physical) of interest in our system.

We can see a flow that is representing a digital input of the system: the ignition button of the car.

http://ucanca.gatatac.org/flows/34-in-but-ignition

{{iframe(http://ucanca.gatatac.org/flows/34-in-but-ignition,1024,400,yes)}}

In this web page we can see:

* Flow properties:

** Type (in this case is a DIO - digital input output -).

* SubSystem flows: the subsystems that are using the flow.  In this example we can read:

** The CU subsystem (CU is the abbreviation of ControlUnit in this project) is using it as an input located the first pin of its J3 connector.

** The CU_micro subsystem (it is actually the microcontroller inside the ControlUnit system) is using it as an input located in the pin 11 of its {{fn(PINOUT, microcontrollers do not have different connectors, we usually use a virtual PINOUT connector that groups all the inputs and outputs.  Sometimes we make a partition of the real pinout, f.i. FUNCTIONAL pins and MCUSUPPORT pins for functonal I/O and support I/O like the oscillator, the power or the ADC reference of a microcontroller) connector.

** The CU_micro_lights subsystem (actually a functional software module called LIGHTS inside the microcontroller software) is using it as pin {{fn(7,when dealing with software modules, this number is irrelevant)}} of its {{fn(DRE,Data Runtime Environment, another virtual connector that represents the pool of sofware variables shared by all the software modules as an internal bus)}} connector.