MVS-CAN通信协议-翻译版
CAN-Specification for MVS MS6.2 V33
controller翻译中文
Page 1 of 12
1.General Requirements (3)
1.1.Standards and Additional Specifications (3)
2.Construction of the CAN Bus (3)
3.Messages (3)
3.1.Baud Rate (3)
3.2. Configuration Parameter for CAN Identifier and Transmission Rates (3)
3.3Configuration Parameter to Enable Messages (4)
3.4 Monitoring of Receive Messages (4)
3.5Not Available or not Valid Data Bytes (4)
3.6List of Messages (4)
4.CAN Send Messages (5)
5.CAN Receive Messages (10)
Page 2 of 12
1. General Requirements
The CAN Bus (Controller Area Network) is a communication port to exchange data between diagnostic systems and other controllers.
MVS receives data for engine operation and sends diagnostic information, measured data and calculated data via the CAN Bus.
1.1. Standards and Additional Specifications
The CAN-Interface is based on following standards :
SAE-J1939/21 1994-07.
SAE-J1939/71 1996-05
DIN ISO 11898 August 1995
Additional Specifications:
List of MVS Error codes, Blink Codes
2. Construction of the CAN Bus
The can bus lines must be twisted pair.
The maximum length of the complete Bus should not exceed 40m.
The distance between two CAN Bus controllers must be min. 0,1m.
The CAN BUS wires should go directly from one controller to the next controller,
because separate lines from a controller to the can bus must be max. 0.3m (for max baud rates up to
1Mbaud).
The CAN Bus must be terminated with a resistor 121 1% min 0.5W at both ends of the CAN Bus. MVS has got an internal termination resistor. So it must be place at the end of the CAN Bus.
For special applications MVS controller without termination resistors are available.
3. Messages
3.1. Baud Rate
Baud rate: 250 K Bit/s
3.2. Configuration Parameter for CAN Identifier and Transmission Rates
The messages are corresponding to the standards see above.
Additional MVS specific proprietary messages are defined.
The transmit rates, the receive rates and the identifiers are specified in this document, but for special applications modifications may be necessary.
The following parameter are configuration parameters for the CAN messages:
1. Scan rates of the receive messages
Page 3 of 12
2. the identifiers are set to the values which are listed in the chapters of transmit and receive messages.
For special application like to MVS controllers on one CAN BUS the complete identifiers can be modified by configuration parameters.
3. The identifiers consist on:
The Priority of the message
The 2 Byte PDU which tells the receiver what message it is
The source address of the message. That is the node address of the sender.
It is the last byte of the identifier and normally set to zero for engine controllers.
3.3 Configuration Parameter to Enable Messages
It depends on the application which MVS CAN Bus messages are enabled.
MVS sends the CAN messages all the time.
The receive messages have access to the MVS engine control functions. Therefore for each receive message there is a configuration parameter to enable the receiving and the access to the MVS functionality. Enabled receive messages are monitored continuously.
3.4 Monitoring of Receive Messages
Each enabled receive message will be monitored. Three seconds (configuration parameter)
after start of the engine the time out monitoring will be started. If the receive message is missing longer than 5s (configuration parameter) then the message is in time out and a fault message will be generated.
3.5 Not Available or not Valid Data Bytes
If data of a messages are foreseen but not available or not used, then these data have to be marked as …not defined“ by setting value to FF in byte data and FFxx for 2byte data, as defined in the standard. Not valid data, i.e. recognized as defective by an diagnostic function, have to be set to the value FE or FExx.
3.6 List of Messages
The first column of the following lists contains the Message name, the repetition rate and the identifier. The second column explains the data bytes.
Example:
Name: Electronic Engine Controller Message 1
EEC1
Repetition rate: 10 ms
Identifier: 0C F0 04 00
Page 4 of 12
Page 5 of 12
4. CAN Send Messages
MVS MS6.2 P060.V33
Message Data Bytes
Electronic Engine Controller Message 1 EEC1 10 ms 0C F0 04 00 Byte 1: Status Bits 1 to 4 engine torque mode 0 = Idle governor active (default) 1 = Accelerator pedal active 2 = Cruise control active 3 = PTO governor active 4 = Road speed limitation active 5 = Brake c
ontrol active 6 = Transmission control 7 = Torque limitation is active 8 = High speed governor is active Bits 5 to 8 are not defined Byte 2: Requested engine torque in % related to Mdmax 1% / bit, Offset 125, range 0 to 100% Example 135 = 10% Byte 3: Engine torque related to Mdmax 1% / bit, Offset 125, range 0 to 100% Byte 4,5: Engine speed 0,125 rpm/ bit, range 0 to 8031 rpm Bytes 6, 7, 8 not defined Electronic Engine Controller Message 2 EEC2 50 ms 0C F0 03 00 Byte 1: Status Bit 1, 2 Idle throttle switch 00 = not idle and plausible 01 = idle and plausible 10 = not plausible ( error value) 11 = switch not available Bits 3, 4 status accelerator pedal Kick down switch 00 = not active, 01 = active, 10 = Error Bits 5,6,7,8 not defined Byte 2: Accelerator pedal 0,4 % / bit, range 0 to 100% Byte 3: Percent load at current speed Engine torque related to max engine torque at engine speed 1% / bit, range 0 to 125% Bytes 4, 5, 6, 7, 8 Not available

版权声明：本站内容均来自互联网，仅供演示用，请勿用于商业和其他非法用途。如果侵犯了您的权益请与我们联系QQ:729038198，我们将在24小时内删除。