MOST总线规范3.0：引领汽车娱乐与安全的最新进展

4星 · 超过85%的资源需积分: 49 156 浏览量更新于2024-07-29 3 收藏 2.02MB PDF 举报

M.O.S.T. (Media Oriented Systems Transport) 是一个专为汽车电子系统设计的通信标准，由16家欧洲主要汽车制造商在2000年联合推出，旨在提供高效、低延迟的数据传输解决方案，以支持车内娱乐系统和安全功能。其核心特点是采用了塑料光纤作为传输介质，这使得它能在高温、振动和电磁干扰的汽车环境中稳定运行。版本3.0的MOST规范，被称为Rev.3.0E2，发布于2010年7月。这个更新可能包括了性能提升、新的功能集成、更严格的兼容性和安全性要求。作为一款局域网技术，MOST专注于短距离通信，如音频、视频、GPS导航系统和车载通信设备之间的连接，确保了信息的快速传输和多媒体应用的无缝协同。在车辆内部，MOST网络对于提升驾驶者体验和安全性至关重要。通过集成多媒体功能，如高级音响系统、车载显示屏以及实时交通信息，它增强了娱乐性能，同时也有助于实现诸如自动紧急刹车、盲点监测等高级驾驶辅助系统，从而提升行车安全。然而，版权和许可条款需明确指出，任何对MOST Cooperation网站或文档的使用都必须遵守版权法，且未经许可不得复制或以任何形式滥用。内容和责任声明表明，MOST Cooperation及其成员不对网站上的错误或遗漏负责，并有权随时进行更新，所有信息均按“原样”提供，不承担任何保证或担保。此外，他们不对链接到其网站的其他网站内容负责。 M.O.S.T. Rev.3.0规范不仅定义了汽车内部通信架构，还强调了知识产权保护和用户责任。对于汽车行业而言，它是推动智能化和互联驾驶的重要组成部分，为现代汽车提供了一个标准化的平台，确保了信息的高效传输和系统的互操作性。

Specification Document

Page 16

MOST

Specification

MOST Specification

Rev. 3.0 E2 07/2010

Change

Ref.

Section Changes

3V0E1_031 3.1.5.5

− Modified Figure 3-23 so that muting and demuting does not exclusively refer to

nchronous signals and changed the name of state NetInterface PowerOff to NetInterface

Off.

3V0E1_032 3.1.5.6.2.1

− Correction: NetBlock.ShutDown.ResultAck, not Result, is used to request the temperature

shutdown.

3V0E1_033 3.1.5.6.2.2

− Added footnote “The parameter SenderHandle of NetBlock.ShutDown.ResultAck is

ignored by the NetworkMaster.”

3V0E1_034 3.1.5.6.3

− Corrected formatting error where body text had become part of the heading.

3V0E1_035 3.2.2.1

− Added line for address 0x0000 in Table 3-17.

3V0E1_036 3.2.5.2.1

− Removed superfluous remark regarding the obligation to implement AMS.

− Removed “Length” after “OPType” of “DeviceID.FBlockID.InstID.FktID.OPType

(Parameter)” because the length is calculated and not explicitly transmitted.

− Added restrictions regarding the use of TelID 4.

− Added unnumbered heading “TelID, TelLen, and Data”.

− TelIDs greater than 4 have to be ignored.

3V0E1_037 3.2.6.1

− Modified Figure 3-32 so that the isochronous data

transport mechanisms are now called

“DiscreteFrame Isochronous”, “A/V Packetized Isochronous”, and “QoS IP”.

3V0E1_038 3.2.7.1

− Modified Figure 3-33 so that the isochronous data

transport mechanisms are now called

“DiscreteFrame Isochronous”, “A/V Packetized Isochronous”, and “QoS IP”.

3V0E1_039 3.2.7.2.1

− Removed requirement that sources and sinks are numbered in ascending order without

gaps.

3V0E1_040 3.2.9

− For timing constraints, the character “-” means “not defined”.

− Modified description of t

ShutDown

; the constraint also applies when setting the Shutdown

Flag.

− Made “Typ Value” of tWaitSuspend “System Integrator specific”.

− Modified description of t

ShutDownWait

so that it refers to the Shutdown Flag.

− Made “Typ Value” and “Max Value” of tSlaveShutdown “System Integrator specific”.

− Removed inequation for t

MPRdelay

− Changed “Max Value” of t

WaitForProperty

to 400.

− Made “Min Value” of tProcessingDefault1 “System Integrator specific”.

− Made “Min Value” and “Typ Value” of tCM_DeadlockPrev “System Integrator specific”.

− Modified most values for Ring Break Diagnosis.

− Corrected description of t

Diag_Slave_T1

To facilitate the identification of changes and corrections in this errata version, the paragraphs that

were changed substantially are marked with red vertical lines on both sides.

Specification Document

Page 17

MOST

Specification

MOST Specification

Rev. 3.0 E2 07/2010

Changes MOST Specification 2V5-00 to MOST Specification 3V0-00

Change

Ref.

Section Changes

3V0_001 General

− Specification structure modified to better distinguish between application layer and protocol

layer.

− Improved and unified the use of commonly used terms.

− Enforced clear distinction between the terms “protocol”, “message”, and “function”.

− Replaced occurrences of “physical address” with “node position address”.

− Corrected clerical errors.

3V0_002 Glossary

− Removed references to specific speed grades.

− Added entries for Notification, Notification Matrix, and OPType.

3V0_003 1.2

− Removed “MOST Hardware” from scope of the specification.

− Added remark that the specification is speed grade independent and not fully backward

compatible to existing speed grades MOST25/50 described in MOST Spec. Rev. 2.5.

− Moved distinction between ePhy and oPhy here.

3V0_004 1.3

− Updated MOST Framework diagram.

3V0_005 1.4

− Added Unicode, IEEE 802.3, ISO 8859, IEC 62106, ETSI EN 300401 and Shift JIS to list of

references.

3V0_006 1.5

− Removed distinction between MOST25 and MOST50. The specification is speed grade

independent.

− Removed note that the MOST Specification does not depend on any other MOST

Cooperation documents.

3V0_007 2.1.1

− New section outlining a few basic principles of MOST.

3V0_008 2.1.1.1

− Renamed to “Overview of Data Transport”

3V0_009 2.1.1.1.1

− Removed note on recommended data rate limit for the Control Channel.

− Removed partial description of Packet Data Channel because of redundancy.

3V0_010 2.1.1.1.2

− Made application scenario for streaming data more specific by mentioning time-

synchronized transmission.

3V0_011 2.1.1.1.3

− Added remark that the Packet Data Channel is secured by CRC and has ACK/NAK with

automatic retry.

3V0_012 2.1.2

− Stated more clearly that the section describes the logical model of a MOST device.

3V0_013

2.1.2.1

−

Moved function interface description to appendix because function interfaces are now

optional.

3V0_014 -

− Merged section “Managing Streaming/Packet Bandwidth” with “Bandwidth Management”

section.

3V0_015 2.1.2.1.1

− Added remark that a Controller can be associated with more than one Slave and vice

versa.

3V0_016 2.1.2.1.2

− Removed remark on using FBlock Shadows on the Controller side⎯implementation detail.

− Removed distinction between properties and methods because these are introduced later.

3V0_017 2.1.2.2

− For clearer distinction, methods and properties are called “categories”, not “classes”.

3V0_018 2.1.2.3

− Removed overly extensive description of RDS example scenario.

− Changed non-Ack OPTypes to OPTypes using Ack.

3V0_019 2.1.2.4

− Rephrased slightly misleading statement that properties represent limits.

3V0_020 2.1.2.5

− Added recommendation to change properties with Set instead of SetGet when using

notification to avoid two identical status messages.

− Removed definition example.

Specification Document

Page 18

MOST

Specification

MOST Specification

Rev. 3.0 E2 07/2010

Change

Ref.

Section Changes

3V0_021 -

− Moved “Function Interfaces” section to appendix because function interfaces are now

optional.

3V0_022 2.1.2.6

− Inserted consolidated list of address types, which includes Ethernet MAC address.

3V0_023 2.2

− Section renamed from “Protocol” to “Application Layer Protocol Specification”.

3V0_024 2.2.1

− Changed heading to “Application Messages in a MOST Network”

− Added Packet Data Channel as potential channel for transport of application messages.

Previously, only the Control Channel was mentioned.

3V0_025 2.2.2

− Added brief introductory description of properties and methods.

3V0_026 2.2.2.1

− Now using actual device names in the example instead of the generic terms Controller and

Slave.

− Added brief description of FBlock Shadow concept.

− Consolidated description to reduce emphasis on implementation details.

− Added note that a Status reply has the same functional address as the command, but a

different DeviceID.

− Removed overly implementation centric example.

− In addition to FBlockID and InstID, the FktID is required to make an address unique.

3V0_027 2.2.2.2

− Added introduction to the use of methods.

3V0_028 2.2.2.2.1

− Renamed from “Special Case Using Routing” to “Using Methods with SenderHandle”.

− Methods with SenderHandle are now the standard case.

− SenderHandle concept is now described before being used in the example.

− Added restriction that SenderHandle must not contain application relevant information.

− Replaced “Controller” and “Slave” with actual devices names used in the example.

3V0_029 2.2.2.2.2

− Renamed from “Standard Case” to “Using Methods Without SenderHandle”.

− Completely revised.

− Added note that methods without SenderHandle are deprecated.

3V0_030 -

− Removed redundant section “Application Protocol Basics”.

3V0_031 2.2.3

− Renamed to “Structure of MOST Messages”

− Removed “Length” from the structure because it is not transmitted as part of the message.

3V0_032 2.2.3.1

− Stated that the use of device address 0xFFFF is not available for communication directed

from Slave to Controller.

3V0_033 2.2.3.1.1

− Moved section here. Previously under the “DeviceID” section.

3V0_034 2.2.3.2

− “Errors … for FBlockID 0xFF should not be returned” becomes “must not be returned”.

− Removed name for FBlockID 0x00. Extended explanation.

− FBlockID 0xC8 becomes “Reserved for Compliance Testing”.

− Removed Secondary Node (FBlockID 0xFC), which is no longer covered by the

specification.

− Modified ranges from FBlockID 0xF0 to 0xFE.

− Added Tool FBlock (0x0E), AuxiliaryOutput FBlock (0x25), and AuxiliaryInputOutput FBlock

(0x29).

3V0_035 2.2.3.2.1

− Added section “Handling of Supplier Specific FBlocks” to improve document structure.

3V0_036 2.2.3.3.1

− Changed heading from “Responsibility” to “Uniqueness of Functional Addresses”

Specification Document

Page 19

MOST

Specification

MOST Specification

Rev. 3.0 E2 07/2010

Change

Ref.

Section Changes

3V0_037 2.2.3.4

− Merged “Mandatory” and “Extensions” ranges into the “Application” range.

− Added FBlockIDs and FunctionIDs ranges to table.

− The requirement “a controller must verify the identity of a device before using any

proprietary function of FBlock” is now a recommendation.

− Added FBlockInfo as example for obtaining the identity of a device.

3V0_038 2.2.3.5

− Reintroduced ErrorAck OPType for properties (in conjunction with ErrorCode 0x01…0x04).

− Added footnote that non-Ack OPTypes are deprecated.

− Added footnote that GetInterface and Interface are optional OPTypes.

− Added footnote that ErrorAck is required for properties to report syntax errors in conjuction

with illegal OPTypes.

3V0_039 2.2.3.5.1

− Added reference to AMS section for details on Data[0]…Data[n].

− More precise specification of ErrorCode 0x0C, ErrorInfo 0x01 and 0x07.

− Modified table entry for ErrorCode 0x20.

− Rephrased note so that it cannot be misread as entirely dismissing error handling.

− Slaves shall rely on ErrorCodes defined in MOST Specification. Added footnote that error

messages are not limited to single telegrams (except segmentation errors).

− No error reply for multicast messages (broadcast, groupcast, “all FBlocks”, “all instances”).

− Removed overly detailed description of the segmented message concept.

− Segmentation errors are no longer only directed from Slave to Controller

− Removed MOST25 specific Secondary Node error. ErrorCode 0x0A is now reserved.

− Removed Secondary Node branch from Figure 2-16.

−

Removed “Start Execution” action from Figure 2-16 because of potential conflicts in some

scenarios.

−

Removed redundant example for ErrorCode 0x07.

3V0_040 2.2.3.5.2

− Added note stating that non-Ack OPTypes are no longer recommended.

− Corrected description that correlated StartAck with ResultAck.

3V0_041 2.2.3.5.4

− Added remark that usage of Start and StartResult is no longer recommended.

− Changed diagrams to use Ack OPTypes instead of non-Ack OPTypes and moved them to

the corresponding section.

3V0_042 2.2.3.5.6

− Changed reference to Start OPType to StartAck because non-Ack OPTypes are no longer

recommended.

3V0_043 2.2.3.5.7

− Removed ambiguous remark on independence from Notification Matrix.

3V0_044 2.2.3.5.8

− OPTypes GetInterface and Interface are now optional. Added corresponding note.

3V0_045 2.2.3.5.9

− Added note that usage of Increment and Decrement is not recommended for multicast

messages.

3V0_046 2.2.3.5.10

− Added remark that usage of Abort is no longer recommended.

3V0_048 2.2.3.6

− Completely revised.

3V0_049 2.2.3.7

− Added remark that the system-specific maximum length is defined by the System

Integrator.

− Replaced remark about length not being transmitted directly with reference to AMS section.

3V0_050 2.2.3.8

− Removed limitation that messages are sent on the Control Channel only.

− Removed data field length description. Already contained in previous section.

− Removed recommendation to limit messages to single telegrams.

− Added note, stating that the exponent of a value is not transmitted over MOST with the

value.

Specification Document

Page 20

MOST

Specification

MOST Specification

Rev. 3.0 E2 07/2010

Change

Ref.

Section Changes

3V0_051 2.2.3.8.2

− Inserted BitField/Array example that was previously contained in the BitSet function class

description.

− Corrected minor error in example (wrong bit value).

3V0_052 2.2.3.8.10

− “Unicode, UTF8” was labeled as not being ASCII compatible; corrected.

3V0_053 2.2.3.8.11

− Added list of restrictions for the use of data type Stream.

3V0_054 2.2.3.8.11.1

− New section: Stream Cases.

3V0_055 2.2.3.8.11.2

− New section: Stream Signals.

3V0_056 2.2.3.8.12

− Added statement that the Length field includes the MediaType.

− Included examples.

3V0_057 2.2.3.8.13

− Added statement that short streams can be structured like streams.

3V0_058 2.2.4

− Emphasized that OPTypes GetInterface and Interface are optional.

− Removed note that Unicode is not ASCII compatible.

− Changed Channel Type table entries for ProcessingAck and ResultAck.

− Removed reference to MOST High over Control Channel, which is no longer supported.

3V0_059 2.2.4.1

− Updated overview: Container function class now supports Stream, Classified Stream and

Short Stream.

3V0_060 2.2.4.1.1

− Parameter “Boolean” becomes “Content”; the parameter name is no longer a type name.

− Corrected parameter type for function class Switch to be Boolean.

− Added footnote that Interface and GetInterface are optional OPTypes.

3V0_061 2.2.4.1.2

− Parameter “Number” becomes “Content”; the parameter name is no longer a type name.

− Added list of allowed data types and description.

− Added GByte, TByte, bit, bps, kbps, Mbps, Bps, kBps, and MBps to table of units.

− Added remark that units are based on the International System of Units (SI).

3V0_062 2.2.4.1.3

− Parameter “String” becomes “Content”; the parameter name is no longer a type name.

− Added allowed data type and description.

3V0_063 2.2.4.1.4

− Parameter “Pos” becomes “Content” to avoid confusion with Arrays.

− Corrected parameter type to be Enum.

− Removed Increment and Decrement OPTypes.

3V0_064 2.2.4.1.6

− Parameter “SetOfBits” becomes “Content” for reasons of consistency.

− Removed example of BitSet with Array, which is not supported by this function class.

3V0_065 2.2.4.1.7

− Parameter “Classified Stream” becomes “Content” for reasons of consistency.

− Container function class now supports Stream, Classified Stream and Short Stream.

− Added DataType parameter to Interface OPType.

3V0_066 2.2.4.2

− Changed description of Sequence Property to indicate that it contains single value which

can be treated as one property.

− Added function class Map to function class table.

− Added Unclassified Property to function class table.

− Added remark that all types except “Stream” can be used as parameters in Arrays,

Records and Sequences. Stream may be used as last element in Records or Sequences.

− Added remark that OPTypes are omitted in the interface description of function classes

with multiple parameters.

3V0_067 2.2.4.2.1

− Removed note about omission of OPTypes in function interfaces.

− Added statement that an Array must be the last parameter if used within a Record.

− Modified Figure 2-20 so that the Array is the last element.

剩余261页未读，继续阅读

ITSurfer

粉丝: 1
资源: 6

MOST总线规范3.0：引领汽车娱乐与安全的最新进展

基于MOST的互联网协议通信标准

MOST Specification V3.0

Audi A6 Most 总线

MOST总线协议详细讲解

MOST数据总线检修--MOST网络总线系统的检修.pptx

学习情境五 MOST总线系统的检修.docx

学习情境五 MOST总线系统的检修.pdf

汽车车身电控系统检修-MOST总线系统.pptx

用于汽车电子的CAN、LIN、MOST总线 基础知识

MOST总线规范：汽车多媒体系统的控制协议详解

最新资源

用于汽车电子的CAN、LIN、MOST总线基础知识