# Code Interface Report for ADM_Integrated_Logic

### 목차

1. Introduction
2. Function Interfaces
   - Initialize Functions
   - Terminate Functions
   - Periodic Functions
   - Aperiodic Functions
3. Data Interfaces
   - Inports
   - Outports
   - Parameters
   - Internal data

## 1. Introduction [show]

The code generator produced a data code interface for the model. The code interface report summarizes the interface code for model callable entry-point functions and data interface elements, such as root-level inports and outports.

## 2. Function Interfaces [hide]

External code initiates execution of the generated code by calling entry-point functions generated for the model. The type of function code that the code generator produces for a model depends on the modeling style and periodic rates represented in the model. For more information, see Configure Generated C Function Interface for Model Entry-Point Functions

### 2.1 Initialize Functions

Initialize entry-point functions implement startup behavior. In a model, Initialize Function blocks represent startup behavior explicitly.

#### ADM_Integrated_Logic_initialize

Initialization entry point of generated code
`#include "ADM_Integrated_Logic.h" void ADM_Integrated_Logic_initialize(void)`

### 2.2 Terminate Functions

Terminate entry-point functions implement shutdown behavior. In a model, Terminate Function blocks represent shutdown behavior explicitly.

No terminate functions represented in model.

### 2.3 Periodic Functions

Periodic entry-point functions implement model behavior that occurs at a fixed sampling rate. For a rate-based model, the code generator produces a periodic entry-point function for each rate used in the model. In a function-call (export-function) model, Function Call Subsystem blocks that specify a sampling rate represent periodic functions.

#### ADM_Integrated_Logic_step

Output entry point of generated code. Must be called periodically, every 0.002 seconds.
`#include "ADM_Integrated_Logic.h" void ADM_Integrated_Logic_step(void)`

### 2.4 Aperiodic Functions

Aperiodic (asynchronous) entry-point functions implement component behavior occurring asynchronously. In a function-call (export-function) model, Function Call Subsystem blocks that do not specify a sampling rate represent aperiodic functions.

No aperiodic functions represented in model.

## 3. Data Interfaces [hide]

A data code interface maps model data interface elements, such as root-level inports and outports, to storage classes. A storage class specifies the appearance and placement of data elements in the generated code. Storage classes apply direct-access data communication. The list of storage classes available for mapping is determined by the Embedded Coder Dictionary that is associated with the model. You map model interface elements to storage classes in the model code mappings.

### 3.1 Inports

Inputs are variables that are generated in the code based on storage class specifications for model root-level input ports.

#### ADM_Integrated_Logic_U.GV_MCU_RPM

Input data for <Root>/GV_MCU_RPM
`struct { ... double GV_MCU_RPM; ... } ADM_Integrated_Logic_U;`

#### ADM_Integrated_Logic_U.GV_BrakeTorqueCommand

Input data for <Root>/GV_BrakeTorqueCommand
`struct { ... double GV_BrakeTorqueCommand; ... } ADM_Integrated_Logic_U;`

#### ADM_Integrated_Logic_U.GV_IMU_AX_Val

Input data for <Root>/GV_IMU_AX_Val
`struct { ... double GV_IMU_AX_Val; ... } ADM_Integrated_Logic_U;`

#### ADM_Integrated_Logic_U.GV_IMU_AY_Val

Input data for <Root>/GV_IMU_AY_Val
`struct { ... double GV_IMU_AY_Val; ... } ADM_Integrated_Logic_U;`

#### ADM_Integrated_Logic_U.GV_IMU_AZ_Val

Input data for <Root>/GV_IMU_AZ_Val
`struct { ... double GV_IMU_AZ_Val; ... } ADM_Integrated_Logic_U;`

#### ADM_Integrated_Logic_U.GV_IMU_PitchRtVal

Input data for <Root>/GV_IMU_PitchRtVal
`struct { ... double GV_IMU_PitchRtVal; ... } ADM_Integrated_Logic_U;`

#### ADM_Integrated_Logic_U.GV_Vx_Command

Input data for <Root>/GV_Vx_Command
`struct { ... double GV_Vx_Command; ... } ADM_Integrated_Logic_U;`

#### ADM_Integrated_Logic_U.GV_VCU_GearSelStat

Input data for <Root>/GV_VCU_GearSelStat
`struct { ... double GV_VCU_GearSelStat; ... } ADM_Integrated_Logic_U;`

#### ADM_Integrated_Logic_U.GV_MCU_EstTrq

Input data for <Root>/GV_MCU_EstTrq
`struct { ... double GV_MCU_EstTrq; ... } ADM_Integrated_Logic_U;`

#### ADM_Integrated_Logic_U.GV_Vx_Limit

Input data for <Root>/GV_Vx_Limit
`struct { ... double GV_Vx_Limit; ... } ADM_Integrated_Logic_U;`

#### ADM_Integrated_Logic_U.GV_Vx_Fbk

Input data for <Root>/GV_Vx_Fbk
`struct { ... double GV_Vx_Fbk; ... } ADM_Integrated_Logic_U;`

#### ADM_Integrated_Logic_U.GV_RWA_RackAngleCommand

Input data for <Root>/GV_RWA_RackAngleCommand
`struct { ... double GV_RWA_RackAngleCommand; ... } ADM_Integrated_Logic_U;`

#### ADM_Integrated_Logic_U.GV_RWS_RackAngleCommand

Input data for <Root>/GV_RWS_RackAngleCommand
`struct { ... double GV_RWS_RackAngleCommand; ... } ADM_Integrated_Logic_U;`

#### ADM_Integrated_Logic_U.GV_Drive_Mode

Input data for <Root>/GV_Drive_Mode
`struct { ... double GV_Drive_Mode; ... } ADM_Integrated_Logic_U;`

#### ADM_Integrated_Logic_U.GV_ACU_Fault_Flag

Input data for <Root>/GV_ACU_Fault_Flag
`struct { ... double GV_ACU_Fault_Flag; ... } ADM_Integrated_Logic_U;`

#### ADM_Integrated_Logic_U.GV_MCU_Actuator_Fault_Flag

Input data for <Root>/GV_MCU_Actuator_Fault_Flag
`struct { ... double GV_MCU_Actuator_Fault_Flag; ... } ADM_Integrated_Logic_U;`

#### ADM_Integrated_Logic_U.GV_IDB_ECU_Fault_Flag

Input data for <Root>/GV_IDB_ECU_Fault_Flag
`struct { ... double GV_IDB_ECU_Fault_Flag; ... } ADM_Integrated_Logic_U;`

#### ADM_Integrated_Logic_U.GV_RCU_ECU_Fault_Flag

Input data for <Root>/GV_RCU_ECU_Fault_Flag
`struct { ... double GV_RCU_ECU_Fault_Flag; ... } ADM_Integrated_Logic_U;`

#### ADM_Integrated_Logic_U.GV_RWA1_ECU_Fault_Flag

Input data for <Root>/GV_RWA1_ECU_Fault_Flag
`struct { ... double GV_RWA1_ECU_Fault_Flag; ... } ADM_Integrated_Logic_U;`

#### ADM_Integrated_Logic_U.GV_RWA2_ECU_Fault_Flag

Input data for <Root>/GV_RWA2_ECU_Fault_Flag
`struct { ... double GV_RWA2_ECU_Fault_Flag; ... } ADM_Integrated_Logic_U;`

#### ADM_Integrated_Logic_U.GV_RWA_Actuator_Fault

Input data for <Root>/GV_RWA_Actuator_Fault
`struct { ... double GV_RWA_Actuator_Fault; ... } ADM_Integrated_Logic_U;`

#### ADM_Integrated_Logic_U.GV_ACU_ECU_Fault_Flag

Input data for <Root>/GV_ACU_ECU_Fault_Flag
`struct { ... double GV_ACU_ECU_Fault_Flag; ... } ADM_Integrated_Logic_U;`

#### ADM_Integrated_Logic_U.GV_ACU_ECU_Fault_Flag1

Input data for <Root>/GV_ACU_ECU_Fault_Flag1
`struct { ... double GV_ACU_ECU_Fault_Flag1; ... } ADM_Integrated_Logic_U;`

#### ADM_Integrated_Logic_U.GV_ACU_ECU_Fault_Flag2

Input data for <Root>/GV_ACU_ECU_Fault_Flag2
`struct { ... double GV_ACU_ECU_Fault_Flag2; ... } ADM_Integrated_Logic_U;`

#### ADM_Integrated_Logic_U.GV_ACU_ECU_Fault_Flag3

Input data for <Root>/GV_ACU_ECU_Fault_Flag3
`struct { ... double GV_ACU_ECU_Fault_Flag3; ... } ADM_Integrated_Logic_U;`

### 3.2 Outports

Outputs are variables that are generated in the code based on storage class specifications for model root-level output ports.

#### ADM_Integrated_Logic_Y.GV_Brake_Command

Output data for <Root>/GV_Brake_Command
`struct { ... double GV_Brake_Command; ... } ADM_Integrated_Logic_Y;`

#### ADM_Integrated_Logic_Y.GV_Master_Rack_Angle_Cmd

Output data for <Root>/GV_Master_Rack_Angle_Cmd
`struct { ... double GV_Master_Rack_Angle_Cmd; ... } ADM_Integrated_Logic_Y;`

#### ADM_Integrated_Logic_Y.GV_Hill_Torque_Assist

Output data for <Root>/GV_Hill_Torque_Assist
`struct { ... double GV_Hill_Torque_Assist; ... } ADM_Integrated_Logic_Y;`

#### ADM_Integrated_Logic_Y.GV_Motor_Torque_Cmd

Output data for <Root>/GV_Motor_Torque_Cmd
`struct { ... double GV_Motor_Torque_Cmd; ... } ADM_Integrated_Logic_Y;`

#### ADM_Integrated_Logic_Y.Debug_HAC_FLAG

Output data for <Root>/Debug_HAC_FLAG
`struct { ... double Debug_HAC_FLAG; ... } ADM_Integrated_Logic_Y;`

#### ADM_Integrated_Logic_Y.Debug_HAC_RPM_Decision

Output data for <Root>/Debug_HAC_RPM_Decision
`struct { ... double Debug_HAC_RPM_Decision; ... } ADM_Integrated_Logic_Y;`

#### ADM_Integrated_Logic_Y.Debug_HAC_Pitch_angle

Output data for <Root>/Debug_HAC_Pitch_angle
`struct { ... double Debug_HAC_Pitch_angle; ... } ADM_Integrated_Logic_Y;`

#### ADM_Integrated_Logic_Y.Debug_HAC_Brake_Output

Output data for <Root>/Debug_HAC_Brake_Output
`struct { ... double Debug_HAC_Brake_Output; ... } ADM_Integrated_Logic_Y;`

#### ADM_Integrated_Logic_Y.Debug_CC_Brake_Output

Output data for <Root>/Debug_CC_Brake_Output
`struct { ... double Debug_CC_Brake_Output; ... } ADM_Integrated_Logic_Y;`

#### ADM_Integrated_Logic_Y.GV_RWS_RackAngleCmd1

Output data for <Root>/GV_RWS_RackAngleCmd1
`struct { ... double GV_RWS_RackAngleCmd1; ... } ADM_Integrated_Logic_Y;`

#### ADM_Integrated_Logic_Y.GV_Speed_Limit

Output data for <Root>/GV_Speed_Limit
`struct { ... double GV_Speed_Limit; ... } ADM_Integrated_Logic_Y;`

#### ADM_Integrated_Logic_Y.GV_Gear_Postion_Out

Output data for <Root>/GV_Gear_Postion_Out
`struct { ... double GV_Gear_Postion_Out; ... } ADM_Integrated_Logic_Y;`

#### ADM_Integrated_Logic_Y.Act_Fault_Exist

Output data for <Root>/Act_Fault_Exist
`struct { ... double Act_Fault_Exist; ... } ADM_Integrated_Logic_Y;`

#### ADM_Integrated_Logic_Y.Target_RWA_Out

Output data for <Root>/Target_RWA_Out
`struct { ... double Target_RWA_Out; ... } ADM_Integrated_Logic_Y;`

#### ADM_Integrated_Logic_Y.Target_IDB_Out

Output data for <Root>/Target_IDB_Out
`struct { ... double Target_IDB_Out; ... } ADM_Integrated_Logic_Y;`

#### ADM_Integrated_Logic_Y.Target_MCU_Out

Output data for <Root>/Target_MCU_Out
`struct { ... double Target_MCU_Out; ... } ADM_Integrated_Logic_Y;`

### 3.3 Parameters

Parameters are variables in the generated code that represent model parameters and model parameter arguments. The variable is generated based on a storage class specification and flagged to be tunable or not tunable while the model code executes in the target environment.

No interface or tunable parameters in the model.

### 3.4 Internal data

Internal data are variables in the generated code that represent signal data, blocks that have internal states, and data stores. The variable is generated based on a storage class specification and flagged to be measured or not measured while the model code executes in the target environment.

No global data stores or data stores with non-auto storage classes in the model.