adapnex::drivers::compulab::iotdin_imx8p::ADC8Driver

Name

Description

core::Task

Task represents a base class to implement schedulable application components. Tasks are combined via TaskGroup and executed by the scheduler according to the given scheduling parameters. See Application::CreateCyclicTaskGroup() and Application::CreateFreewheelingTaskGroup().

Name

Description

ADC8Driver [constructor]

Construct from string

PreUpdate [virtual]

Update [virtual]

Name

Description

I0

Analog Input I0 (values: 0..10V)

I1

Analog Input I1 (values: 0..10V)

I2

Analog Input I2 (values: 0..10V)

I3

Analog Input I3 (values: 0..10V)

I4

Analog Input I4 (values: 0..10V)

I5

Analog Input I5 (values: 0..10V)

I6

Analog Input I6 (values: 0..10V)

I7

Analog Input I7 (values: 0..10V)

Name

Description

PostUpdate [virtual]

The PostUpdate method provides an opportunity to do some processing after all Update() methods have been invoked each cycle. Drivers generally use this to update any outputs that might have been written to by other tasks.

PreUpdate [virtual]

The PreUpdate method provides an opportunity to do some processing before any Update() methods are invoked each cycle. Drivers generally use this step to update any inputs that might be consumed by other tasks.

Setup [virtual]

The Setup method is called once during the setup phase of the application after the setup() function has returned. Any remaining configuration or memory allocation that could not be handled in the constructor should occur here. The order in the Setup methods for each Task are called is dependent on the order in which the containing task groups are created followed by the order in which the tasks are added to their respective task groups. Drivers generally use this step to initialize any peripherals or devices, based on the previously defined configuration.

TearDown [virtual]

The TearDown method is called once during the shutdown phase of the application, after the final update cycle has completed. Tasks generally use this to drive outputs to a safe state, while drivers use it to flush those final values and release any peripherals or devices. The TearDown methods are called in reverse order relative to Setup(), so that a driver added before the tasks consuming its inputs and outputs tears down after them. See Application::Stop().

Update [virtual]

The Update method is called repeatedly after the setup phase and should contain the main processing step for most tasks. Therefore, the method has no default implementation and must be overridden by every derived class.