Code Interface Report for ADM_Integrated_Logic

Table of Contents

  1. Introduction
  2. Function Interfaces
  3. Data Interfaces

1. Introduction [show]

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 modelling 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

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.

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

Variables that are generated in the code based on storage class specifications for model root-level inports.

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_Operation_Mode

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

ADM_Integrated_Logic_U.GV_RC_RWA1_2_FAULT

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

ADM_Integrated_Logic_U.GV_RC_IDB_Fault

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

ADM_Integrated_Logic_U.GV_RC_MCU_Fault

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

ADM_Integrated_Logic_U.IDB_ECU_FAULT_FLAG

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

ADM_Integrated_Logic_U.RCU_ECU_FAULT_FLAG

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

ADM_Integrated_Logic_U.RWA_ECU_FAULT_FLAG

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

ADM_Integrated_Logic_U.RWA2_ECU_FAULT_FLAG

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

3.2 Outports

Variables that are generated in the code based on storage class specifications for model root-level outports.

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

Variables in the generated code that represent model parameters and model parameter arguments that are generated in the code 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/tunable parameters in model.

3.4 Internal data

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

No data stores in model; note that this report lists only data stores with non-auto default storage class and global data stores