ABH-CAN Interface, PSM Function - GF54.21-S-3049TRA
Model 447
With Code ED5 (Parameterisable special module)
Except Code XM7 (MOPF II)
Model 448
With Code ED5 (Parameterisable special module)
Except Code XM7 (MOPF II)
The peripheral devices CAN corresponds to the body manufacturer CAN (CAN ABH). The abbreviation "ABH" continues to be used for diagnosis parameterization.
ISO = International Organization for Standardization.
Peripheral devices CAN, description
Peripheral devices CAN
The peripheral devices CAN is used to transmit and receive signals and messages in accordance with the database provided by Daimler AG.
They are divided into 3 specifications:
- Fleet management system (FMS I)
- ISO 11992
- Configurable messages, the peripheral devices CAN signals and their routing specification is described in "Signalrouting_ABHCAN_Sp_MPM_BR447.xls" as well as in the chapters "Peripheral devices CAN receive signals" and "Peripheral devices CAN transmit signals".
The peripheral devices CAN is woken up and held active through the "ABH_INPUT_COMM_ENABLE" input.
Signal identification number = Signal ID.
The following parameters can be configured through diagnosis:
| Parameter | Value range | Meaning |
|---|---|---|
| ABH-CAN active | "0" = No "1" = Yes |
Activate peripheral devices CAN module |
| ABH_INPUT_COMM_ENABLE | Signal ID | Switch communication on and off to match the assigned signal pool signal ID. |
| FMS messages enable | "0" = No "1" = Yes |
Activate specific messages of fleet management system |
| ISO messages enable | "0" = No "1" = Yes |
Activate ISO-11992-specific messages as well as the configurable message group |
| Hybrid messages enable | "0" = No "1" = Yes |
Activate message group Hybrid 1, 2 |
| ABH-CAN 125 kBaud | "0" = No "1" = Yes |
Baud rate of peripheral devices CAN. Only one of the 3 parameters may be switched on. If several are activated, the greatest baud rate is used. If no baud rate is selected, then 125 kBaud is used for sending. |
| ABH-CAN 250kBaud | "0" = No "1" = Yes |
|
| ABH-CAN 500kBaud | "0" = No "1" = Yes |
|
| GPM1H active | "0" = No "1" = Yes |
Activate configurable message |
| GPM1I active | "0" = No "1" = Yes |
Activate configurable message |
| GPM1J active | "0" = No "1" = Yes |
Activate configurable message |
| GPM1K active | "0" = No "1" = Yes |
Activate configurable message |
| HYBRID_1_OUT | "0" = No "1" = Yes |
Activate configurable message |
| HYBRID_2_OUT | "0" = No "1" = Yes |
Activate configurable message |
| Fuel Tank Size [in Liter] | 0...255 | Tank size in liter |
| Post run delay [in 0.1 s] | 0...65 535 | Run-on time after switch-off through the signal configured in ABH_INPUT_COMM_ENABLE |
The configurable messages can still be assigned signal IDs for transfer.
The reception signals are filed in the signal pool.
Peripheral devices CAN receive signals
Receive signals Rx
The signals of the receive messages read in the parameterizable special module (PSM) control unit (N26/16) by the peripheral devices CAN, are specified.
The received signals are specified under the following three messages:
- Fleet management system (FMS)
- ISO 11992
- Configurable messages
The signals continue to be processed and converted before they are stored in the signal pool.
Processing takes place in accordance with the corresponding specifications.
"Signalrouting_ABHCAN_Sp_MPM_BR447.xls" contains the signal routing in which the signals, information and conversions are described in detail.
FMS Rx signals
In accordance with the FMS I standard, no signals are received from the PSM.
ISO 11992-Rx signals
The ISO 11992 Class contains the following messages and signals:
The signal routing and the associated information for the signals are described in "Signalrouting_ABH-CAN_Sp_MPM_BR447.xls".
- "ISO11992_GPM23"
- "ISO11992_GPM24"
- "ISO11992_GPM2A"
The following peripheral devices CAN signals are described under "ISO11992_GPM23":
The relevant signal pool signals are located in the right-hand column. These are listed under peripheral devices CAN signals in the description of the signal pool.
| Peripheral devices CAN signal | Signal pool signal |
|---|---|
| ReqEngineSpeed | Body_ReqEngineSpeed |
| ReqEngineSpeedLimit | Body_ReqEngineSpeedLimit |
| ReqEngineSpeedLowerLim | Body_ReqEngineSpeedLowerLim |
| ReqEngineSpeedUpperLim | Body_ReqEngineSpeedUpperLim |
| ReqEngineTorqueLimit | Body_ReqEngineTorqueLimit |
The following peripheral devices CAN signals are described under "ISO11992_GPM24":
The relevant signal pool signals are located in the right-hand column.
| Peripheral devices CAN signal | Signal pool signal |
|---|---|
| ClutchIndpdtPTOSwitch | Body_ClutchIndpdtPTOSwitch |
| EngineStartSwitch | Body_EngineStartSwitch |
| EngineStopSwitch | Body_EngineStopSwitch |
| FirstClutchDPdtPTOSwitch | Body_FirstClutchDpdtPTOSwitch |
| FirstEngineMtdPTOSwitch | Body_FirstEngineMtdPTOSwitch |
| OperatingPanelActive | Body_OperatingPanelActive |
| RefusePackerStepSwitch | Body_RefusePackerStepSwitch |
| StarterLockoutSwitch | Body_StarterLockoutSwitch |
The following peripheral devices CAN signals are described under "ISO11992_GPM2A":
The relevant signal pool signals are located in the right-hand column.
| Peripheral devices CAN signal | Signal pool signal |
|---|---|
| EngineSpeedControlStates | Body_EngineSpeedControl_Increase |
| Body_EngineSpeedControl_Decrease | |
| Body_EngineSpeedControl_Resume | |
| FixedEngineSpeed1 | ABH_FixedEngineSpeed1 |
| FixedEngineSpeed2 | ABH_FixedEngineSpeed2 |
| FixedEngineSpeed3 | ABH_FixedEngineSpeed3 |
| GoToNeutral | Body_GoToNeutral |
| PTOGovernorEngineSpeedModeSwitch | Body_PTOGovernorEngineSpeedModeSwitch |
| SpeedControlModeUpperLimit1 | ABH_SpeedControlModeUpperLimit1 |
| SpeedControlModeUpperLimit2 | ABH_SpeedControlModeUpperLimit1 |
| SpeedControlModeUpperLimit3 | ABH_SpeedControlModeUpperLimit1 |
| WarningBuzzer | Body_WarningBuzzer |
Configurable receiver signals
The received configurable messages are described below:
The signal routing and the associated information for the signals are described in "Signalrouting_ABH-CAN_Sp_MPM_BR447.xls".
- "GPM2H"
- "GPM2I"
- "GPM2J"
- "GPM2K"
- "HYBRID_1_IN"
- "HYBRID_2_IN"
The data content or data information is not specified in line with FMS and ISO 11992.
The peripheral devices CAN signals of the following messages (with message numbers) "GPM2H" (1), "GPM2I" (2), "GPM2J" (3), "GPM2K" (4), "HYBRID_1_IN" (5) and "HYBRID_2_IN" (6) and their signal pool signals are described below.
These are listed under peripheral devices CAN signals in the description of the signal pool.
Each message encompasses the following types; the data lengths are in parentheses:
- 8x bit (2 bit)
- 2x byte (8 bit)
- 2x word (16 bit)
The peripheral devices CAN signal is composed of:
- In<data length><message number>_<signal number>
The associated signal pool signal is composed of:
- Body_<message name>_In_<data length>_<signal number>
Peripheral devices CAN transmit signals
Transmit signals Tx
The signals of the transmit messages, written by the PSM control unit on the peripheral devices CAN, are specified. The transmitted signals are specified under the following three messages.
- Fleet management system (FMS)
- ISO 11992
- Configurable messages
The signals are first read in from the signal pool and then processed and converted before they are sent via the peripheral devices CAN.
Processing takes place in accordance with the corresponding specifications.
"Signalrouting_ABH-CAN_Sp_MPM_BR447.xls" includes the signal routing in which the signals, information and conversions are described in detail.
FMS Tx signals
In accordance with the FMS I standard, the following messages are sent:
The signal routing and the associated information for the signals are described in "Signalrouting_ABH-CAN_Sp_MPM_BR447.xls" and are described in the communication matrix.
- "BAM_CM", "BAM_DT"
- "CCVS"
- "DashDisplay"
- "EEC1"
- "EEC2"
- "EngineHoursRevolutions"
- "EngineTemperature"
- "FMSstandardinterface"
- "FuelConsumption"
- "HighResolutionVehicleDistance"
- "Service"
- "TCO1"
- "VehicleWeight"
Additional messages:
- "CombinationVehicleWeight"
- "HighResolutionFuelConsumption"
Unsupported message:
- Owing to its data size of more than 8 bytes, "VehicleIdentification" is sent via transport protocols (Broadcast Announce Management messages) in compliance with the specifications. It is also not part of the communications matrix.
ISO-11992-Tx signals
The transmit messages as per the ISO 11992 standard and their mapped signals and information are described below:
The signal routing and the associated information of the signals are described in "Signalrouting_ABH-CAN_Sp_MPM_BR447.xls" (see Attachment) and in the communication matrix.
- "ISO11992_EBS11"
- "ISO11992_EBS12"
- "ISO11992_GPM11"
- "ISO11992_GPM12"
- "ISO11992_GPM13"
- "ISO11992_GPM14"
- "ISO11992_GPM15"
- "ISO11992_GPM16"
- "ISO11992_RGE11"
Additional messages:
- "Lamps"
Configurable Tx signals
The configurable messages and their mapped signals and information are described below:
The signal routing and the associated information are described in "Signalrouting_ABHCAN_Sp_MPM_BR447.xls".
- "GPM1H"
- "GPM1I"
- "IGPM1J"
- "GPM1K"
- "HYBRID_1_OUT"
- "HYBRID_2_OUT"
The configurable transmit messages "GPM1H" (1), "GPM1I" (2), "GPM1J" (3), "GPM1K" (4), "HYBRID_1_OUT" (5), and "HYBRID_2_OUT" (6) are described below.
The signal pool signals are assigned through configuration of the function inputs.
Each message encompasses the following types; the data lengths are in parentheses:
- 8x bit (2 bit)
- 2x byte (8 bit)
- 2x word (16 bit)
The peripheral devices CAN signal is composed of:
- Aux<data length><message number>_<signal number>
The associated function input is composed of:
- Body_INPUT_<message name>_<data length>_<signal number>
| Parameterizable special module (PSM) control unit component description | GF54.21-S-5005TRA | ||
| Overview of system components for parameterizable special module (PSM) | GF54.21-S-9998TRA |