当前位置:文档之家› SAE J2610-2002 Serial Data Communication Interface

SAE J2610-2002 Serial Data Communication Interface

SAE J2610-2002 Serial Data Communication Interface
SAE J2610-2002 Serial Data Communication Interface

SAE Technical Standards Board Rules provide that: “This report is published by SAE to advance the state of technical and engineering sciences. The use of this report is entirely voluntary, and its applicability and suitability for any particular use, including any patent infringement arising therefrom, is the sole responsibility of the user.”

SAE reviews each technical report at least every five years at which time it may be reaffirmed, revised, or cancelled. SAE invites your written comments and suggestions.

TO PLACE A DOCUMENT ORDER: +1 (724) 776-4970 FAX: +1 (724) 776-0790

SAE WEB ADDRESS https://www.doczj.com/doc/e513482562.html,

Copyright 2002 Society of Automotive Engineers, Inc.

5Technical Overview (5)

5.1General (5)

5.2Communication Model (6)

6Physical Layer (6)

6.1Data Rate Specification (7)

6.1.1Initialization (7)

6.1.2Communication Modes (7)

6.2Signal Definition (7)

6.2.1Logic Levels (7)

6.2.2Idle Condition (7)

6.2.3Break Condition (8)

6.3Routing and Connectivity (8)

6.3.1Diagnostic Connector Configurations (8)

6.3.2Diagnostic Connector Terminations (9)

6.3.3Diagnostic Connector Multiplexing (11)

6.4Media Characteristics (11)

6.4.1Impedance (11)

6.4.2Interface Cable Considerations (11)

6.5ECU Receiver/Transmitter Reference Circuits (11)

6.5.1SCI Rx Line (11)

6.5.2SCI Tx Line (12)

7.Data Link Layer (13)

7.1Data Frame Definition (13)

7.1.1Length and Format (13)

7.2Inter-Frame Timing (13)

7.3Error Handling (15)

7.3.1Error Detection (15)

7.3.2Error Correction/Recovery (15)

8Message Application Layer (15)

8.1Message Frame Structure (15)

9.Reprogramming Requirements (16)

9.1Security (16)

9.2Block Transfer (16)

9.2.1Length and Format (16)

9.2.2Verification (16)

9.3Hardware Interlock (16)

9.4Flash Strobe (17)

9.4.1VPP Specification (17)

9.4.2SCI/VPP Multiplexing (17)

9.4.3Time Critical Events (18)

1.Scope

1.1Purpose—The purpose of this SAE Information Report is to specify the requirements necessary to fully define

the Serial Data Communication Interface (SCI) used in the reprogramming of emission-related powertrain Electronic Control Units (ECU) in DaimlerChrysler Corporation (Chrysler Group) vehicles. It is intended to satisfy new regulations proposed by the federal U.S. Environmental Protection Agency (EPA) and California Air Resource Board (CARB) regulatory agencies regarding “pass-thru programming” of all On-Board Diagnostic (OBD) compliant emission-related powertrain devices. These requirements are necessary to provide independent automotive service organizations and after-market scan tool suppliers the ability to reprogram emission-related powertrain ECUs for all manufacturers of automotive vehicles.

Specifically, this document details the SCI physical layer and SCI data link layer requirements necessary to establish communications between a diagnostic tester and an ECU. It further specifies additional requirements for the application of a flash strobe voltage multiplexed on the SCI communication link for purposes of ECU reprogramming. This document does not specify the content or meaning of the application messages or diagnostic protocol to be transmitted on the SCI communication link. It only defines a generic method to transfer data between a diagnostic tester and an ECU, regardless of application messaging structure.

This specification will be referenced from within SAE J2534 Pass-Thru Programming as a technical information report. In this regard, the inclusion of the SCI communication link is in addition to the approved OBD communication links previously specified in SAE J2534, and constitutes unique DaimlerChrysler Corporation (Chrysler Group) manufacturer-specific requirements.

1.2Applications—This document shall strictly apply to DaimlerChrysler Corporation vehicles developed and

manufactured exclusively by the former Chrysler Corporation, and for purposes of clarification, referred to herein as DaimlerChrysler Corporation (Chrysler Group). This document shall not apply to other DaimlerChrysler Corporation vehicles or subsidiaries, including products developed and manufactured by Mercedes-Benz, Smart, or Mitsubishi Motors Corporation. The SCI communication link defined herein shall apply to OBD vehicles retroactive to the 1994 model year.

1.3History—DaimlerChrysler Corporation (Chrysler Group) introduced flash technology into emission-related

powertrain ECUs beginning in the 1993 model year. Flash technology consisted of implementing reprogrammable memory devices into powertrain ECUs for purposes of updating software functionality and calibrations in the customer field (service environment), assembly plant (manufacturing environment), and vehicle development (engineering environment). Reprogramming events in the field require strict compliance to corporate guidelines based on the following criteria:

Vehicle performance / driveability

Vehicle safety

Vehicle emissions

Vehicle fuel economy

Customer satisfaction

The DaimlerChrysler Corporation (Chrysler Group) corporate flash strategy consists of incorporating proprietary standards and requirements into the flash process. These requirements involve the integration of multiple levels of protective security measures using software and hardware lockout techniques including additional safeguard mechanisms controlled via internal corporate processes and corporate test tools. New regulations will force a change in the current DaimlerChrysler Corporation (Chrysler Group) flash strategy and process.

2.References

2.1Applicable Publications—The following publications form a part of this specification to the extent specified

herein. Unless otherwise specified, the latest issue of publications shall apply.

2.1.1SAE P UBLICATIO NS—Available from SAE, 400 Commonwealth Drive, Warrendale, PA 15096-0001.

SAE J1850—Class B Data Communications Network Interface

SAE J1962—Diagnostic Connector

SAE J1979—E/E Diagnostic Test Modes

SAE J2190—Enhanced E/E Diagnostic Test Modes

SAE J2534—Pass-Thru Programming

2.1.2ISO P UBLICATIONS—Available from ANSI, 25 West 43rd Street, New York, NY 10036-8002.

ISO 9141-2—Road vehicles—Diagnostic systems—Part 2: CARB requirements for interchange of digital information

ISO 14230-4—Road vehicles—Keyword protocol 2000 for diagnostic systems—Part 4: Requirements for emission-related systems

ISO 15765-4—Road vehicles—Diagnostics on CAN—Part 4: Requirements for emission-related systems 2.2Related Publications—The following publications are provided for information purposes only and are not a

required part of this specification.

2.2.1C HRYSLER G ROUP P UBLICATIO NS—Available from DaimlerChrysler Corporation, Vehicle Diagnostics, CIMS

484-08-06, 800 Chrysler Drive, Auburn Hills, MI USA 48326-2757.

SCI Diagnostic Protocol for PCM Applications, DaimlerChrysler Corporation (Chrysler Group)

SAE J2190 Diagnostic Protocol for PCM Applications, DaimlerChrysler Corporation (Chrysler Group)

System and Method for Reprogramming Vehicle Computers, U.S. Patent No. 5,278,759, DaimlerChrysler Corporation (Chrysler Group)

2.2.2M OTOROLA, I NC., P UB LICATION—Available from Motorola Literature Distribution, P.O. Box 20912, Phoenix, AZ

USA 85036.

Queued Serial Module (QSM) Reference Manual, Motorola, Inc.

3.Definitions

3.1Bit—The contraction of binary digit representing the smallest unit of information. A bit can assume either a

logical high (e.g., mark) or logical low (e.g., space) value.

3.2Bit Time—The time required to serially transmit/receive one bit of data, which is equal to one cycle of the baud

frequency.

3.3Break—A character or symbol used to terminate bus communications and reset all nodes to a ready-to-

receive state.

3.4Character—A data byte contained in a data frame transmission.

3.5Frame—One complete transmission of information delineated by the start of frame (start bit) and end of frame

(stop bit) identifiers.

3.6Message—An orderly sequence of data frame transmissions having varying length.

3.7Full-Duplex—A communication system capable of simultaneous bi-directional communications.

3.8Half-Duplex—A communication system capable of bi-directional communications, but only in one direction at

a time.

3.9Mark—A state of a binary element indicating a logical high or “1” value (inverse of space).

3.10Space—A state of a binary element indicating a logical low or “0” value (inverse of mark).

3.11Start Bit—The first binary element transmitted in the asynchronous transmission of a data frame. It is used to

uniquely identify the beginning of a data frame transmission to synchronize the receiver to an active session.

3.12Stop Bit—The last binary element transmitted in the asynchronous transmission of a data frame. It is used to

uniquely identify the end of a data frame transmission to return the receiver to an idle condition.

4.Abbreviations and Acronyms

bps – bits per second

BRK – Break

CAN – Controller Area Network

CARB – California Air Resource Board

ECM – Engine Control Module

ECU – Electronic Control Unit

EPA – Environmental Protection Agency

ISO – International Standards Organization

LSB – Least Significant Bit

MSB – Most Significant Bit

NRZ – Non-Return-to-Zero

OBD – On-Board Diagnostic

PCM – Powertrain Control Module

PROM – Programmable Read Only Memory

RAM – Random Access Memory

ROM – Read Only Memory

Rx – Receive

SAE – Society of Automotive Engineers

SCI – Serial Communication Interface

TCM – Transmission Control Module

TTL – Transistor-Transistor Logic

Tx – Transmit

UART – Universal Asynchronous Receiver Transmitter

5.Technical Overview

5.1General—The Serial Data Communication Interface (SCI) is defined as a full-duplex, asynchronous, UART-

based serial interface for point-to-point communications between an off-board diagnostic tester and an on-board electronic control unit (ECU). The SCI communication link is required to support the diagnosis and reprogramming of emission-related powertrain devices for DaimlerChrysler Corporation (Chrysler Group) vehicles. It is implemented as a non-inverted 0 to 5 V DC asynchronous system requiring a 5 V DC idle high mode. SCI baud rates are software selectable for data transmission modes. SCI terminations at the diagnostic connector must be software selectable for multiplexing old and new SCI configurations. Additionally, the application of a flash strobe voltage multiplexed on the SCI communication link is required for reprogramming ECU memory devices.

The following points summarize the SCI communication link requirements:

a.Full-duplex, dual-wire interface using one Rx line and one Tx line

b.Non-inverted Transistor-Transistor Logic (TTL) voltage level operation using idle “high” mode

c.Non-Return-To-Zero (NRZ) bit-coding format using 10-bit data frame

d.Multiple data rates of 7812.5 bps, 62.5 Kbps, 125.0 Kbps

e.Flash strobe voltage (Vpp) using multiplexed 20 V DC source

5.2Communication Model—The SCI communication model characterizes the SCI communication behavior into

three conceptual layers: SCI Physical Layer, SCI Data Link Layer, and Message Application Layer. In this regard, SCI communications is accomplished through the conceptual layering of peer entities. Each peer entity forms a virtual communication link. The layers allow transmitted data bits to be grouped into data frames, data frames constructed into messages, and messages mapped into application-specific protocol functions.

This is illustrated in the SCI communication model in Figure 1:

FIGURE 1—SCI COMMUNICATION MODEL DEPICTING THE THREE CONCEPTUAL LAYERS

Note that the SCI communication model does not specify the content or meaning of the application messages or diagnostic protocol to be transmitted on this interface. It only defines a generic method to transfer data between a diagnostic tester and an ECU, regardless of application messaging structure.

6.Physical Layer—The SCI Physical Layer is responsible for transferring data bits between the diagnostic tester

and the ECU. The SCI Physical Layer defines the data transmission rates, electrical signals, physical media, routing, and connectivity to the vehicle.

6.1Data Rate Specification—The SCI communication link shall have a default data rate of 7812.5 bps. A

communication session between a diagnostic tester and an ECU shall always be initiated at the default data rate. A change in data rate can be negotiated once communications are established between the diagnostic tester and ECU. The ECU shall automatically track to the requested data rate following a command sequence from the diagnostic tester. The command sequence is initiated by transmitting a specific training character to the ECU. The ECU shall respond with an acknowledgement character following establishment of the proper data rate. For proper operation of serial communications, the diagnostic tester and ECU shall support the data rates as specified in Figure 2.

FIGURE 2—SCI COMMUNICATION MODES WITH AVAILABLE DATA RATES AND BIT TIMES The bit time is the time required to serially transmit/receive one bit of data. It is equal to one cycle of the baud frequency as determined by the selected data rate.

6.1.1I NITIALIZATION—An ECU shall always initialize to the default low-speed communication rate of 7812.5 bps

following an ECU power-on or reset condition.

6.1.2C OMMUNICATIO N M ODES—An ECU shall support the following communication modes of operation:

a.Low-Speed Mode—The low-speed mode shall be used for initializing a communication exchange or

diagnostic session between a diagnostic tester and an ECU.

b.High-Speed Mode—The high-speed mode(s) shall be used for establishing a data acquisition session

or flash reprogramming download session between a diagnostic tester and an ECU.

6.2Signal Definition—For proper operation of serial communications, the diagnostic tester and ECU shall

correctly determine each signal value as specified as follows.

6.2.1L O GIC L EVELS—A standard Non-Return-to-Zero (NRZ) bit-coding format shall be required using non-inverted

Transistor-Transistor Logic (TTL) voltage levels. The logic states of each binary element are defined as follows:

a.Logic “1” State: A logic “1” state (high) shall be equivalent to a voltage level greater than 4.0 V (i.e.,

80% of Vdd).

b.Logic “0” State:A logic “0” state (low) shall be equivalent to a voltage level less than 1.0 V (i.e., 20% of

Vdd).

The rise and fall times shall be less than 10% of the bit times specified by the data rate. The rise and fall times shall be defined as the time for the voltage to change from 20% to 80% of Vdd (rise time), and from 80% to 20% of Vdd (fall time). This implies that in the 7812.5 bps low-speed mode, the rise time from 1.0 V to 4.0 V shall be no longer than 12.8 microseconds. In the 62.5 Kbps and 125.0 Kbps high-speed modes, rise and fall times shall be no longer than 1.6 microseconds and 0.8 microseconds, respectively.

6.2.2I DLE C ONDITION—An idle condition shall be defined as 10 (or more) consecutive bit times at a logic “1” state.

Hence, the SCI communication link shall enter a “bus high” state when an idle condition is declared.

6.2.3B REAK C O NDITIO N—A break condition shall be defined as 10 (or more) consecutive bit times at a logic “0”

state (i.e., BRK character). The BRK character is used to terminate bus communications and reset all nodes to a ready-to-receive state. Hence, the SCI communication link shall enter a “bus low” state when a break condition is declared.

6.3Routing and Connectivity—Connectivity from the diagnostic tester to the vehicle shall be provided via the

SAE J1962 Diagnostic Connector. Physical routing from the diagnostic connector to each ECU shall be provided via an SCI receive/transmit communication link in accordance to the specifications as follows.

6.3.1D IAGNOSTIC C ONNECTOR C ONFIG URATIONS—The SAE J1962 Diagnostic Connector is an industry-standard

16-pin common connector configuration defined for use in automotive vehicles. The diagnostic connector provides the physical means by which access to the on-board vehicle communication network is accomplished. The specific assignment and functionality of a fixed set of connector terminals has been defined by SAE for common industry-standard use by all vehicle manufacturers. The remaining undefined connector terminals are allocated for manufacturer-specific use for unique applications.

A revision to the SAE J1962 Diagnostic Connector recommended practice was enacted due to new

regulations allowing provisions for the acceptance of a Controller Area Network (CAN) as a viable alternative On-Board Diagnostic (OBD) communication interface. Consequently, new SAE requirements redefined connector pins 6 and 14, previously designated as manufacturer-specific, as SAE-specific for the development and integration of CAN. DaimlerChrysler Corporation (Chrysler Group) had previously designated pins 6 and 14 as SCI receive lines for the engine ECU and transmission ECU, respectively.

Consequently, DaimlerChrysler Corporation (Chrysler Group) has defined two unique connector configurations for use in vehicle applications. Configuration 'A' shall be referred to as the 'old' configuration, and Configuration 'B' shall be referred to as the 'new' configuration. Each connector configuration is defined in the following sections.

a.Configuration 'A'—Configuration 'A' shall be used in DaimlerChrysler Corporation (Chrysler Group)

vehicles beginning in the 1994 model year through the 2001 model year, and shall gradually be

replaced beginning in the 2002 model year by Configuration 'B'. Physical routing to ECUs shall be

handled by providing a separate SCI receive line to each ECU. The engine ECU shall support an SCI

receive line terminated at pin 6, and the transmission ECU shall support an SCI receive line terminated

at pin 14. Both engine and transmission ECUs shall share a common SCI transmit line terminated at

pin 7 (wire-ORed together). SCI connections to pins 6 and 14 shall not electrically interfere with

ISO15765-4 CAN operation. Likewise, SCI connections to pin 7 shall not electrically interfere with

ISO9141-2 operations. Additionally, if a vehicle supports SAE J1979 legislative diagnostics via the

ISO 9141-2 K-line, the SCI transmit lines shall remain wire-ORed together for engine and transmission

communications as specified in Configuration 'A'.

b.Configuration 'B'—Configuration 'B' shall be used in selective DaimlerChrysler Corporation (Chrysler

Group) vehicles beginning in the 2002 model year, and shall eventually be used on all vehicle

applications exclusively. Physical routing to ECUs shall be handled by providing a separate pair of SCI

receive/transmit lines to each ECU. The engine ECU shall support an SCI receive/transmit pair

terminated at pins 12 and 7, respectively. The transmission ECU shall support an SCI receive/transmit

pair terminated at pins 9 and 15, respectively. In this regard, Configuration 'B' supports the

independent interrogation and flash reprogramming of engine and transmission ECUs via SCI

simultaneously. Additionally, SCI connections to pins 6 and 14 have been vacated to allow the

migration to CAN to proceed without exception. This also permits the co-existence of both SCI and

CAN vehicles using Configuration 'B', and supports full compliance to the SAE J1962 diagnostic

connector requirements per the latest SAE publication.

6.3.2D IAGNOSTIC C ONNECTOR T E RMINATIO NS—The SAE J1962 connector terminal assignments are defined in

Figure 3 for each DaimlerChrysler Corporation (Chrysler Group) vehicle configuration. SCI receive/transmit connections are depicted as gray-shaded assignments (viewed from the ECU perspective). Each configuration is shown compared against the SAE industry-standard reference.

FIGURE 3—TERMINAL ASSIGNMENTS AND FUNCTION FOR

SAE J1962 DIAGNOSTIC CONNECTOR CONFIGURATIONS

The SCI receive/transmit re-mapping from Configuration 'A' to Configuration 'B' is defined as follows:

a.Reroute pin 6 (Configuration 'A') to pin 12 (Configuration 'B') for Engine SCI Rx

b.Reroute pin 14 (Configuration 'A') to pin 9 (Configuration 'B') for Transmission SCI Rx

c.Vacate pin 6 and pin 14 for CAN-C (+) and CAN-C (-), respectively

d.Retain pin 7 (Configuration 'B') for Engine SCI Tx only

e.Separate and reroute pin 7 (Configuration 'A') to pin 15 (Configuration 'B') for Transmission SCI Tx

The routing for each diagnostic connector configuration is depicted graphically in Figures 4 and 5.

FIGURE 4—OLD CONFIGURATION 'A' DEPICTED WITH SINGLE SCI TX LINE SHARED PER PAIR OF EMISSION ECUS

FIGURE 5—NEW CONFIGURATION 'B' DEPICTED WITH INDEPENDENT SCI RX/TX LINES PER EACH EMISSION ECU

6.3.3D IAGNOSTIC C ONNECTOR M ULTIP LEXING—Multiplexing of the SAE J1962 diagnostic connector terminals shall

be required by the diagnostic tester to support the two vehicle configurations as follows:

a.Configuration 'A'—For Configuration 'A', connector pins 6 and 14 shall be multiplexed between SCI

functionality and ISO 15765-4 CAN functionality under software control. SCI connections to pins 6 and

14 shall not electrically interfere with ISO 15765-4 CAN operation. Both pins must transition

simultaneously between data link types when requested. When the SCI mode is selected by the tester,

both pins 6 and 14 must support SCI transmit with Vpp flash strobe function under software control.

The default settings for the SCI channel function are 7812.5 bps with flash strobe 'OFF'. Connector pin

7 shall function as either an SCI receiver, or an ISO 9141-2 bi-directional transceiver under software

control. SCI connections to pin 7 shall not electrically interfere with ISO 9141-2 operations, and shall

be able to be pulled to either vehicle battery or 5 V DC under programmable control.

b.Configuration 'B'—For Configuration 'B', connector pins 9 and 12 shall be configured for SCI

functionality. When the SCI mode is selected by the tester, both pins 9 and 12 must support SCI

transmit with Vpp flash strobe function under software control. Either connector pin transitions

independently with SCI mode enabled. The default settings for the SCI channel function are

7812.5bps with flash strobe 'OFF'. Connector pins 7 and 15 shall function as either an SCI receiver, or

an ISO 9141-2 transceiver under software control. SCI connections to pins 7 or 15 shall not electrically

interfere with ISO 9141-2 operations, and shall be able to be pulled to either vehicle battery or 5 V DC

under programmable control.

For additional details regarding the multiplexing of the Vpp flash strobe requirements during a flash reprogramming session, please refer to Section 9 “Reprogramming Requirements”.

6.4Media Characteristics—The SCI physical media shall be defined as a dual-wire, unshielded, twisted-pair

interface.

6.4.1I MPEDANCE—Impedance characteristics shall be dictated by the interface circuitry as specified in the ECU

receiver/transmitter reference circuits in 6.5.

6.4.2I NTERFACE C A BLE C ONSIDERATIO NS—The diagnostic tester interface cable shall not exceed a maximum of

5m in length.

The interface cable may be constructed using one of the following methods:

a.By using two jumper connectors in the interface cable, backward compatibility between Configuration

'A' and Configuration 'B' can be supported with minimal tester software overhead. This is

accomplished by shorting connector pins 6 and 12 together for engine ECU and connector pins 9 and

14 together for transmission ECU, and promotes a single interface cable usage for old vs. new

connector configurations. The same goal can be accomplished using a cable adapter with the jumpers

integrated into the adapter. However, the interface cable and/or adapter connector will constitute

special requirements for DaimlerChrysler Corporation (Chrysler Group) vehicles, and as such, may be

a less desirable solution. Additionally, this set-up cannot be used for CAN vehicles.

b.By not using any jumper connectors in the interface cable, tester detection of connector configuration

can be supported through software polling techniques. Several methods for ECU response detection

via connector pins 7 and 15 are possible. This approach allows a standard interface cable to be used

for all vehicles.

6.5ECU Receiver/Transmitter Reference Circuits—The following figures depict functionally equivalent SCI

receive and transmit circuits for an ECU.

6.5.1SCI R X L INE—The ECU receive circuit shall contain provisions to support SCI communications as well as

Vpp flash strobe requirements multiplexed on the same line by the diagnostic tester. A typical ECU receive circuit is shown illustrated in Figure 6.

FIGURE 6—REPRESENTATIVE ECU RECEIVER CIRCUIT WITH TYPICAL COMPONENT VALUES

6.5.2SCI T X L INE—The ECU transmit circuit shall contain an open-collector style circuit to drive a diagnostic tester

receive circuit such as the one illustrated in Figure 7. The tester must provide adequate pull-up resistance as

shown.

FIGURE 7—REPRESENTATIVE ECU TRANSMITTER CIRCUIT WITH TYPICAL COMPONENT VALUES

7.Data Link Layer—The SCI Data Link Layer is responsible for transferring data between the SCI Physical

Layer and the Message Application Layer. The SCI Data Link Layer defines the data frame elements, format, length, inter-frame timing, and error handling conditions.

7.1Data Frame Definition—Asynchronous data transmission implies that each data frame shall be transmitted

individually. This section defines the grouping of data bits that comprise an SCI data frame. A data frame is defined as one complete transmission of information delineated by the start of frame (start bit) and end of frame (stop bit) identifiers. These start and stop bits define the boundaries of a single data frame for the receiver to properly interpret.

7.1.1L E NG TH A ND F ORMAT—The data frame size shall be defined as ten (10) bits in length (i.e., one start bit, eight

data bits, and one stop bit with no parity). The format of the data frame shall be defined as follows:

a.One (1) Start Bit:One start bit with logic “0” (low) for one bit time duration. The start bit is defined as the

first binary element transmitted in the asynchronous transmission of a data frame. It is used to uniquely

identify the beginning of a data frame transmission to synchronize the receiver to an active session.

b.Eight (8) Data Bits:Eight data bits transmitted from Least Significant Bit (LSB) to Most Significant Bit

(MSB). The data bits comprise the byte or character value contained in the data frame bounded by the

start and stop bits.

c.One (1) Stop Bit:One stop bit with logic “1” (high) for one bit time duration. The stop bit is defined as

the last binary element transmitted in the asynchronous transmission of a data frame. It is used to

uniquely identify the end of a data frame transmission to return the receiver to an idle condition.

d.No Parity Bit:No parity bit in the default data fram

e. Therefore, no parity checking is available in the

transmitted data frame.

Figure 8 illustrates this pattern:

FIGURE 8—THIS EXAMPLE DEPICTS THE DATA FRAME TRANSMISSION OF CHARACTER $69

7.2Inter-Frame Timing—An SCI receiver shall be capable of receiving 255 consecutive data frames with zero (0)

inter-frame delay. Inter-frame delay is defined as the time between the end of one data frame and the start of the next data frame. Zero inter-frame delay implies that data is being transferred as fast as the data rate allows. If a diagnostic tester cannot receive a stream of 255 consecutive data frames with zero (0) inter-frame delay, then a slower data rate should be negotiated between the diagnostic tester and the ECU.

Although the SCI communication link is a full-duplex serial interface, in some communication sessions a half-duplex mode is required. Half-duplex mode implies that the SCI communication system is capable of bi-directional communications but only in one direction at a time. In the half-duplex mode, every data frame sent by the diagnostic tester is “echoed” by the ECU. The tester shall not send the next data frame until receiving the expected echo from the ECU. Upon receiving the echo, the tester shall assume the ECU is ready for the next sequential data frame. Although the ECU shall echo the appropriate data frame as intended, this shall not imply that the command sequence has been fully serviced by the ECU. An additional delay time may be

required by the ECU for processing the request before a command sequence has been completed. This half-duplex mode allows the timing sequence to be completely managed by the diagnostic tester. This strategy prevents data frame overruns from occurring, but also effectively limits the data throughput. That is, the diagnostic tester shall wait for the echoed response character before sending the next request. This is illustrated in Figure 9:

FIGURE 9—TWO-FRAME MESSAGE REQUEST/ACKNOWLEDGEMENT SEQUENCE WITH A TWO-FRAME MESSAGE RESPONSE DURING A DIAGNOSTIC SESSION

Additionally, multiple-frame command sequences may be sent to an ECU without echoing each character. In this case, a response shall occur within a given timeframe. Otherwise, a communication timeout event shall be declared, and the ECU shall disregard the entire command sequence. This is illustrated in Figure 10:

FIGURE 10—MULTIPLE-FRAME MESSAGE DOWNLOAD SEQUENCE WITH A MULTIPLE-FRAME ACKNOWLEDGEMENT DURING A REPROGRAMMING SESSION The following timing parameters in Figure 11 shall apply to all communication modes:

FIGURE 11—TIMING DELAY PARAMETERS LISTED AS A FUNCTION OF COMMUNICATION MODE

7.3Error Handling

7.3.1E RRO R D ETECTION—There are several distinct types of detectable SCI communication errors. A diagnostic

tester and ECU shall monitor for framing, overrun, and noise communication errors. The SCI “frame level”

communication errors are defined as follows:

a.Framing Error:A framing error is set when the SCI receiver detects a logic “0” where a stop bit (logic

“1”) should occur. A framing error results when the frame boundaries in the received bit stream are not

synchronized with the receiver bit counter. This is usually caused by mismatched data rates between

receiver and transmitter. Note that a BRK condition may set a framing error.

b.Overrun Error:An overrun error is set when the SCI receiver has not transferred data from its internal

receive buffer before new data arrives. Data transfer between ECU and tester is inhibited until this

receive buffer can be cleared. Previous data in the receive buffer is still valid, but all data received after

the overrun condition was declared is discarded.

The SCI “bt level” communication errors are defined as follows:

c.Noise Error:A noise error is set when the SCI receiver has detected noise on a valid start bit, stop bit,

or data bit. A noise error results when the sampled bit in the received bit stream assumes different

states or an indeterministic state based on a sampling frequency of the logic level. The sampling

frequency is determined by the SCI receiver.

7.3.2E RRO R C ORRECTION/R ECOVERY—If an SCI communication error is detected, the SCI receiver shall reject the

request, discard any message contents, and refrain from sending any response character. Possible recovery strategies include:

a.Wait for a communication session timeout

b.Request a retransmission of the previous data frame

c.Request a change in communication parameters (e.g., reduction in data rate)

In the high-speed mode, the ECU shall monitor for framing and overrun communication errors. If a framing or overrun error is detected, the ECU shall record the error event to accumulate the number of occurrences.

When a maximum number of ten (10) errors have been detected, the ECU shall reset the data rate to the default low-speed mode and clear the error accumulation counter to zero. The noise error is not tracked for frequency of occurrence in the high-speed mode.

In the low-speed mode, the ECU shall monitor for framing, overrun, and noise communication errors. If no communication errors are detected during a 100 milliseconds sampling period, re-establishment of the high-speed mode shall be allowed.

8.Message Application Layer—The Message Application Layer transforms SCI data frames received from the

Data Link Layer into application-specific messages. Additionally, the Message Application Layer maps application-specific messages back into data frames to be transferred by the Data Link Layer. The Message Application Layer can support many industry-standard or proprietary application-specific protocols.

Application-specific protocols that utilize the SCI communication link include the SCI Diagnostic Protocol for PCM Applications, and the SAE J2190 Diagnostic Protocol for PCM Applications as applied to the diagnosis of DaimlerChrysler Corporation (Chrysler Group) vehicles.

8.1Message Frame Structure—An SCI message frame shall be defined as an ordered collection of SCI data

frames. Since SCI is a dedicated point-to-point communication link, no message header is required for specifying the addressing format or error checking. This permits full usage of the communication bandwidth.

The message frame shall have the following free-form structure as shown in Figure 12:

Data bytes 1 to N shall comprise the message data area. The message data area may or may not contain error checking. The message length may vary depending on the application-specific protocol requirements.

FIGURE 12—ARBITRARY MESSAGE FRAME STRUCTURE FOR SUPPORT OF MULTIPLE PROTOCOLS 9.Reprogramming Requirements—The SCI communication link is utilized in the flash reprogramming of

emission-related powertrain devices. Additional requirements apply when reprogramming emission-related ECUs via the SCI communication link. To that end, this section defines the application of protective security mechanisms, hardware interlock requirements, and flash strobe requirements as applied to the reprogramming of emission-related ECUs.

9.1Security—The diagnostic tester shall secure the flash reprogramming process by retaining all required

reprogramming information off-board the vehicle (i.e., resident in the tester). The tester shall provide the ECU with the proper software routines, algorithms, and loaders containing the necessary instructions for download, checksum, erase, and program. These routines are only temporarily downloaded into volatile RAM on-board the ECU for the current diagnostic session. These functions shall only be allowed following the initialization of secured access to ECU boot-loader functions.

9.2Block Transfer—Data targeted for the reprogramming of a memory device shall be segmented into data

blocks for download into the ECU. The data block size, format, and integrity verification process shall be as defined below.

9.2.1L E NG TH A ND F ORMAT—The data block shall not exceed 4K bytes in length. The format of each block shall

minimally contain a header composed of the target memory address (defined as the absolute memory address location) followed by a block length identifier.

9.2.2V ERIFICATIO N—Data block verification can be performed using various procedures and methods. Most

commonly, a checksum is performed and verified from the data stream echoed by the ECU to the diagnostic tester. Data is downloaded into the ECU RAM by the tester, flashed into PROM, read from PROM, and compared to RAM on a per byte basis. It is then echoed back to the diagnostic tester. A final checksum of the entire program code shall be performed following completion of the flash process.

9.3Hardware Interlock—The hardware interlock shall be required to externally trigger the ECU into entering the

special boot-loader mode following hardware reset. This interlock enables a “flash-ready” mode not achievable through normal software control. It is used to enhance the secured process through the implementation of an additional protective safeguard. Since the vehicle is unable to generate the Vboot signal level required for initiating boot-loader mode, no boot-block functions can be inadvertently accessed. The hardware interlock is stimulated by the flash strobe voltage multiplexed on the ECU SCI receive line. Once the hardware interlock has been initiated, a hardware reset is required to permit the ECU to enter a “load-and-go” boot-loader mode to allow off-board routines to be downloaded and executed. The flash strobe signal is used as a comparative voltage on the Vboot control input for the ECU bootstrap software to detect. The hardware reset is

accomplished through cycling of the ignition key.

9.4Flash Strobe—The diagnostic tester shall be required to generate the external Vpp flash strobe voltage

necessary for erasing and programming on-board memory devices. The Vpp flash strobe voltage is needed to support the following four functions:

a.Initiating ECU boot-loader mode

b.Reading flash memory electronic signature (manufacturer and device codes)

c.Erasing flash memory

d.Programming flash memory

9.4.1V PP S PECIFICATIO N—The diagnostic tester shall generate the Vpp flash strobe voltage multiplexed on the

tester SCI transmit line. The requirements for the programmable power supply shall be defined as follows in Figure 13:

FIGURE 13—VPP FLASH STROBE ELECTRICAL PARAMETER VALUES

A switching power supply is recommended for use as the Vpp flash strobe (instead of a charge pump or

other device) in order to satisfy the fast stabilization time requirements.

9.4.2SCI/VPP M ULTIP LEXING—The diagnostic tester shall be capable of multiplexing signals between SCI data

communications and Vpp flash strobe. The diagnostic tester shall apply the flash strobe following download and execution of the erase routine. The flash strobe shall be applied for the entire duration of the erase event. After completion of the erase event, the tester shall download the programming routine to the ECU.

The first block of data to be programmed into the flash memory shall be transmitted to the ECU and saved into on-board RAM. Since the data needed to fully reprogram a flash memory device is larger than the available RAM resources in the ECU, the program code is segmented into data blocks or packets of specific length. Following a successful download of the first data block to the ECU, the diagnostic tester shall apply the flash strobe to the ECU. The ECU boot-loader routine shall have sufficient delay to allow the tester to generate the flash strobe voltage. This timing is dependent on the circuitry used to switch in the flash strobe signal. The programming routine previously downloaded and resident in on-board RAM writes the data into the flash memory space and echoes the programmed data back to the tester. Upon receiving all expected data, the tester shall power down the flash strobe signal thus allowing further transmission of data. This cycle continues until all blocks of data have been programmed. This repetitive process is depicted in Figure 14:

FIGURE 14—TESTER MULTIPLEXING OF THE SCI TX AND VPP FLASH STROBE

SIGNALS FOR A SINGLE DATA BLOCK TRANSFER EVENT

9.4.3T IME C RITICAL E VENTS—Time critical events are required to address timing and process constraints imposed

by certain request and response activities that necessitate some level of real-time intervention. Most notably, this is a requirement during the application and removal of the flash strobe voltage following the execution of the erase sequence or block download sequence for memory programming. The diagnostic tester should apply the flash strobe voltage within one character transmission of the last data byte of the block transfer.

The ECU shall allow a delay time for the settling and stabilization of the flash strobe voltage. This stabilization time (Ts) shall be measured from the reception of the last stop bit of the block transfer. If the flash strobe voltage has not stabilized within the allotted delay time, the ECU shall abort the reprogramming process. Following completion of the programming event, the tester shall remove the flash strobe so that SCI communications can recommence. This re-establishment of data communication allows further block transfers to occur.

PREPARED BY THE SAE VEHICLE E/E SYSTEMS DIAGNOSTIC STANDARDS COMMITTEE

Rationale—The purpose of this document is to specify the requirements necessary to fully define the Serial Data Communication Interface (SCI) used in the reprogramming of emission-related powertrain Electronic Control Units (ECU) in DaimlerChrysler Corporation (Chrysler Group) vehicles. It is intended to satisfy new regulations proposed by the federal U.S. Environmental Protection Agency (EPA) and California Air Resource Board (CARB) regulatory agencies regarding “pass-thru programming” of all On-Board Diagnostic (OBD) compliant emission-related powertrain devices. These requirements are intended to provide independent automotive service organizations and after-market test equipment suppliers the ability to reprogram emission-related powertrain ECUs for all manufacturers of automotive vehicles. These requirements are in addition to the approved OBD communication links previously specified and included in SAE J2534 Pass-Thru Programming, and constitute unique DaimlerChrysler Corporation (Chrysler Group) manufacturer-specific requirements. This specification will be referenced from within SAE J2534 as a technical information report.

Relationship of SAE Standard to ISO Standard—Not applicable.

Application—The purpose of this SAE Information Report is to specify the requirements necessary to fully define the Serial Data Communication Interface (SCI) used in the reprogramming of emission-related powertrain Electronic Control Units (ECU) in DaimlerChrysler Corporation (Chrysler Group) vehicles. It is intended to satisfy new regulations proposed by the federal U.S. Environmental Protection Agency (EPA) and California Air Resource Board (CARB) regulatory agencies regarding “pass-thru programming” of all On-Board Diagnostic (OBD) compliant emission-related powertrain devices. These requirements are necessary to provide independent automotive service organizations and after-market scan tool suppliers the ability to reprogram emission-related powertrain ECUs for all manufacturers of automotive vehicles.

Specifically, this document details the SCI physical layer and SCI data link layer requirements necessary to establish communications between a diagnostic tester and an ECU. It further specifies additional requirements for the application of a flash strobe voltage multiplexed on the SCI communication link for purposes of ECU reprogramming. This document does not specify the content or meaning of the application messages or diagnostic protocol to be transmitted on the SCI communication link. It only defines a generic method to transfer data between a diagnostic tester and an ECU, regardless of application messaging structure.

This specification will be referenced from within SAE J2534 Pass-Thru Programming as a technical information report. In this regard, the inclusion of the SCI communication link is in addition to the approved OBD communication links previously specified in SAE J2534, and constitutes unique DaimlerChrysler Corporation (Chrysler Group) manufacturer-specific requirements.

Reference Section

SAE J1850—Class B Data Communications Network Interface

SAE J1962—Diagnostic Connector

SAE J1979—E/E Diagnostic Test Modes

SAE J2190—Enhanced E/E Diagnostic Test Modes

SAE J2534—Pass-Thru Programming

ISO 9141-2—Road vehicles—Diagnostic systems—Part 2: CARB requirements for interchange of digital information

ISO 14230-4—Road vehicles—Keyword protocol 2000 for diagnostic systems—Part 4: Requirements for emission-related systems

ISO 15765-4—Road vehicles—Diagnostics on CAN—Part 4: Requirements for emission-related systems

Queued Serial Module (QSM) Reference Manual, Motorola, Inc.

SAE J2190 Diagnostic Protocol for PCM Applications, DaimlerChrysler Corporation (Chrysler Group)

SCI Diagnostic Protocol for PCM Applications, DaimlerChrysler Corporation (Chrysler Group)

System and Method for Reprogramming Vehicle Computers, U.S. Patent No. 5,278,759, DaimlerChrysler Corporation (Chrysler Group)

Developed by the SAE Vehicle E/E Systems Diagnostic Standards Committee

国际技术咨询服务合同 (中英文)

国际技术咨询服务合同(中英文) Technical Consultancy Service Contract 合同号:Contract No________________ 签订日期:Date of Signature:________________ 签订地点:Place of Signature:________________ 中国____________公司(以下简称委托方)为一方,______国______________ 公 司(以下简称为咨询方)为另一方,双方就_____________的技术咨询服务,授权双方代表按下列条款签订本合同。 This Contract is made and entered into through friendly negotiation by and between China____________________ (hereina fter referred to as “Client”), as one party, and____________________ (hereinafter referred to as“Consultant”),as the other party, concerning the technical consultancy service of__________, under the following terms and conditions: 第一条合同内容 Article 1 Contents of Technical Consultancy Service 1.1 委托方希望获得咨询方就_____提供的技术咨询服务,而咨询方愿意提供此项服务。 Whereas Client desires to obtain the technical consultancy service of from Consultant and Consultant has agreed to perform such services. 1.2 技术咨询服务范围详见本合同附件一。 The Scope of Technical Services is defined in Appendix 1. 1.3 技术咨询服务的进度安排详见本合同附件二。 The Time Schedule for the Services is shown in Appendix 2. 1.4 技术咨询服务的人员安排见本合同附件三。 The Manning Schedule is described in Appendix 3. 1.5 技术咨询服务自合同生效之日起_____个月内完成,将在_____个月内提交最终技术咨询报告,包括图纸、设计资料、各类规范和图片等。咨询方应免费通报委托方类似工程的最近发展和任何进展,以便委托方能改进该工程的设计。 Consultant shall complete the Services within__________months from the Effective Date of this Contract and furnish the final technical service report, including drawings, designing documents, all kinds of standards and photos, within____months. Consultant shall keep aware, free of charge, Client of the latest development of similar projects and any progress made in order to improve the designing of the project.

国际技术咨询服务合同范本 中英文对照版

编号:_____________ 国际技术咨询服务合同 委托方:___________________________ 咨询方:___________________________ 签订日期:_______年______月______日

中国________________________公司(以下简称委托方)为一方,_____国 __________________________ 公司(以下简称为咨询方)为另一方,双方就 _________________________的技术咨询服务,授权双方代表按下列条款签订本合同。 This Contract is made and entered into through friendly negotiation by and between China_________________________ (hereinafter referred to as “Client”), as one party, and__________________________ (hereinafter referred to as“Consultant”),as the other party, concerning the technical consultancy service of________________________, under the following terms and conditions: 第一条合同内容 Article 1 Contents of Technical Consultancy Service 1.1 委托方希望获得咨询方就___________________________提供的技术咨询服务,而咨询方愿意提供此项服务。 Whereas Client desires to obtain the technical consultancy service of from Consultant and Consultant has agreed to perform such services. 1.2 技术咨询服务范围详见本合同附件一。 The Scope of Technical Services is defined in Appendix 1. 1.3 技术咨询服务的进度安排详见本合同附件二。 The Time Schedule for the Services is shown in Appendix 2. 1.4 技术咨询服务的人员安排见本合同附件三。 The Manning Schedule is described in Appendix 3.

中英文咨询服务合同

竭诚为您提供优质文档/双击可除 中英文咨询服务合同 篇一:咨询协议,counsaltingservicecontract(英文版) consuLTIngseRVIceconTRAcT ThisAgreementismadebyandbetween:partyA: 【】,ancorporationhavingitsprincipalplaceofbusiness atItsbusinessLicenseno.【】;AnD partyb: 【】,ancorporationhavingitsprincipalplaceofbusiness atItsbusinessLicenseno.【】 “partyA”and“partyb”individuallyreferredtoasthe “party”andcollectivelyasthe“parties”, whereas (i)partyAisanindependentcompany(ii)partybis partyAandpartyb,intendingtobelegallybound,partyAent rustpartybtoprovidetheconsultingservice,andinconsid erationofthemutualpromisesandcovenantscontainedhere

in,agreeasfollows: 1.Itemofservice The“service”1) 2)…… 2.serviceperiod partybwillprovidetheservicetopartyAfrom【】to【】 3.priceandpaymentTerms 1)price:Thetotalservicefeeis 2)paymentTerm:partyAagreestopaytheamountofservicefe esforthe followingfixedterm:①within【】daysafterthesignaturedate,andpartybbegintoprovideth eservice,partyAshallpay【】%ofthetotalservicefee; ②within【】daysaftertheserviceundertheagreementhascompletelype rformed,partyAshallpay【】%ofthetotalservicefee; …… 3)Theservicefeeshallbepaidtothedesignatedbankaccoun tofpartyb,the

国际技术咨询服务合同(中英文版)

合同编号: 国际技术咨询服务合同(中英文 版) 签订地点: 签订日期:年月日

国际技术咨询服务合同(中英文版) 合同号:________________ 签订日期:________________ 签订地点:________________ 中国____________公司(以下简称委托方)为一方,______国 ______________ 公司(以下简称为咨询方)为另一方,双方就 _____________的技术咨询服务,授权双方代表按下列条款签订本合同。 第一条合同内容 1.1 委托方希望获得咨询方就_____提供的技术咨询服务,而咨询方愿意提供此项服务。 1.2 技术咨询服务范围详见本合同附件一。 1.3 技术咨询服务的进度安排详见本合同附件二。 1.4 技术咨询服务的人员安排见本合同附件三。 1.5 技术咨询服务自合同生效之日起_____个月内完成,将在 _____个月内提交最终技术咨询报告,包括图纸、设计资料、各类规范和图片等。咨询方应免费通报委托方类似工程的最近发展和任何进展,以便委托方能改进该工程的设计。 第二双方的责任和义务

2.1 委托方应向咨询方提供有关的资料、技术咨询报告、图纸和可能得到的信息并给予咨询方开展工作提供力所能及的协助,特别是委托方应在适当时候指定一名总代表以便能随时予以联系。 2.2 委托方应协助咨询方向有关机构取得护照签证、工作许可和咨询方要求的其它文件以使咨询方能进入委托方国家和本工程 的现场,但费用由咨询方负担。 2.3 除了合同附件三所列的技术人员外,咨询方还应提供足够数量的称职的技术人员来履行本合同规定的义务。咨询方应对其所雇的履行合同的技术人员负完全责任并使委托方免受其技术人 员因执行合同任务所引起的一切损害。 2.4 咨询方应根据咨询服务的内容和进度安排,按时提交咨询技术咨询报告及有关图纸资料。 2.5 咨询方应协助委托方的技术人员获得进入咨询方国家的签 证并负责安排食宿,食宿费用由委托方负担。咨询方应为委托方的技术人员提供办公室、必要的设施和交通便利。 2.6 咨询方对因执行其提供的咨询服务而给委托方和委托方工 作人员造成的人身损害和财产损失承担责任并予以赔偿,但这种损害或损失是由于咨询方人员在履行本合同的活动中的疏忽所 造成的。咨询方仅对本合同项下的工作负责。 2.7 咨询方对本合同的任何和所有责任都限定在咨询方因付出

技术服务合同范本,英文

篇一:各类合同_中英文样本(含15份)1 中英文版法律顾问服务合同 法律顾问服务合同 legal counseling agreement 聘请方: (下称甲方) consigner: 地址: address: 法定代表人: legal representative: 受聘方: consignee: (hereinafter referred to as “party b”) 地址:上海市淮海中路283号香港广场26楼 address:26/f,hongkang plaza 283 huaihai road shanghai 本合约由上列甲乙双方于中华人民共和国上海市订立。 this agreement is made and entered into by and between the two parties in shanghai, the people’s republic of china 鉴于: whereas: 甲方为促进业务发展,防范法律风险,决定聘请乙方为其常年法律顾问; party a want to promote its business and keep away law risks, decides to assign party b as its long-term law consultant. 乙方系一家在中国境内注册设立并经中国政府特许、可持续运营的劳动法律服务机构,经与甲方商洽,同意接受聘请,担任其常年法律顾问; 为此, now, therefore 甲乙双方本着相互信任、合作共赢的原则,经友好、充分之协商,就聘请合约的条款及内容达成如下协议: the two parties based on principle of trusting and win-win cooperating, after friendly and thorough negotionation, the parties agreed the following terms and conditions on the consigning. 第一条聘约期间 article one consignment periods 1.1 甲方聘请乙方作为常年法律顾问的期间为壹年,自________至_______;聘期届满后,本合约自动终止。 party a consign party b as it’s long-term law consultant, the consignment period is one year, from _____________ to ___________, the agreement will terminate after expiration. 1.2乙方指定________作为主要联系人,负责跟进和处理法律顾问事宜。如因甲方的工作内容需要或_____出差在外地,乙方可另行指派其他专业人员提供法律服务。 the party b assign lawyer______ as major coordinator, he willbe responsible for following and settling law consulting affairs. if the working assignment of party a requires or lawyer______ are out to other cities on business, party b can assign other professional lawyer to provide legal service.1.3本合约聘期届满后,若甲方

国际技术咨询服务合同中英文对照

国际技术咨询服务合同 国际技术咨询服务合同 合同号:________________ 签订日期:________________ 签订地点:________________ 中国____________公司(以下简称委托方)为一方,______国______________ 公司(以下简称为咨询方)为另一方,双方就_____________的技术咨询服务,授权双方代表按下列条款签订本合同。 第一条合同内容 1.1 委托方希望获得咨询方就_____提供的技术咨询服务,而咨询方愿意提供此项服务。1.2 技术咨询服务范围详见本合同附件一。 1.3 技术咨询服务的进度安排详见本合同附件二。 1.4 技术咨询服务的人员安排见本合同附件三。 1.5 技术咨询服务自合同生效之日起_____个月内完成,将在_____个月内提交最终技术咨询报告,包括图纸、设计资料、各类规范和图片等。咨询方应免费通报委托方类似工程的最近发展和任何进展,以便委托方能改进该工程的设计。 第二双方的责任和义务 2.1 委托方应向咨询方提供有关的资料、技术咨询报告、图纸和可能得到的信息并给予咨询方开展工作提供力所能及的协助,特别是委托方应在适当时候指定一名总代表以便能随时予以联系。 2.2 委托方应协助咨询方向有关机构取得护照签证、工作许可和咨询方要求的其它文件以使咨询方能进入委托方国家和本工程的现场,但费用由咨询方负担。 2.3 除了合同附件三所列的技术人员外,咨询方还应提供足够数量的称职的技术人员来履行本合同规定的义务。咨询方应对其所雇的履行合同的技术人员负完全责任并使委托方免受其技术人员因执行合同任务所引起的一切损害。 2.4 咨询方应根据咨询服务的内容和进度安排,按时提交咨询技术咨询报告及有关图纸资料。 2.5 咨询方应协助委托方的技术人员获得进入咨询方国家的签证并负责安排食宿,食宿费用由委托方负担。咨询方应为委托方的技术人员提供办公室、必要的设施和交通便利。 2.6 咨询方对因执行其提供的咨询服务而给委托方和委托方工作人员造成的人身损害和财产损失承担责任并予以赔偿,但这种损害或损失是由于咨询方人员在履行本合同的活动中的疏忽所造成的。咨询方仅对本合同项下的工作负责。 2.7 咨询方对本合同的任何和所有责任都限定在咨询方因付出专业服务而收到的合同总价之内,并将在本合同第7.3条规定的保证期满后解除。 第三条价格与支付 3.1 本合同总价为___________(币种)_______(大写:__________)。各分项的价格如下:分项一的合同价为________(币种)_______(大写:);分项二的合同价为________(币种)_______(大写:);分项三的合同价为________(币种)_______(大写:);分项四的合同价为________(币种)_______(大写:)。 3.2 本合同总价包括咨询方所提供的所有服务和技术费用,为固定不变价格,且不随通货膨胀的影响而波动。合同总价包括咨询方在其本国和委托方国家因履行本合同义务所发生的一切费用和支出和以各种方式寄送技术资料到委托方办公室所发生的费用。如发生本合同规定

国际项目咨询服务合同范本

国际项目咨询服务合同范本 篇一:国际项目咨询服务合同范本中英文合同号:________________ 签订日期:________________ 签订地点:________________ 中国____________公司(以下简称委托方)为一方,______国______________ 公司(以下简称为咨询方)为另一方,双方就_____________的项目咨询服务,授权双方代表按下列条款签订本合同。 第一条合同内容 1.1 委托方希望获得咨询方就_____提供的项目咨询服务,而咨询方愿意提供此项服务。 1.2 项目咨询服务范围详见本合同附件一。 1.3 项目咨询服务的进度安排详见本合同附件二。 1.4 项目咨询服务的人员安排见本合同附件三。 1.5 项目咨询服务自合同生效之日起_____个月内完成,将在_____个月内提交最终项目咨询报告,包括资料、各类案例和图片等。咨询方应免费通报委托方类似信息的最近发展和任何进展,以便委托方能改进该项目的资料。第二双方的责任和义务 2.1 委托方应向咨询方提供有关的资料、项目咨询报告、

图纸和可能得到的信息并给予咨询方开展工作提供力所能及的协助,特别是委托方应在适当时候指定一名总代表以便能随时予以联系。 2.2 委托方应协助咨询方向有关机构取得护照签证、工作许可和咨询方要求的其它文件以使咨询方能进入委托方国家和本工程的现场,但费用由咨询方负担。 2.3 除了合同附件三所列的项目人员外,咨询方还应提供足够数量的称职的项目人员来履行本合同规定的义务。咨询方应对其所雇的履行合同的项目人员负完全责任并使委托方免受其项目人员因执行合同任务所引起的一切损害。 2.4 咨询方应根据咨询服务的内容和进度安排,按时提交咨询项目咨询报告及有关图纸资料。 2.5 咨询方应协助委托方的项目人员获得进入咨询方国家的签证并负责安排食宿,食宿费用由委托方负担。咨询方应为委托方的项目人员提供办公室、必要的设施和交通便利。 2.6 咨询方对因执行其提供的咨询服务而给委托方和委托方工作人员造成的人身损害和财产损失承担责任并予以赔偿,但这种损害或损失是由于咨询方人员在履行本合同的活动中的疏忽所造成的。咨询 方仅对本合同项下的工作负责。

咨询服务合同范本doc

咨询服务合同范本 这篇关于咨询服务合同范本,是编辑为您整理的,希望对您有所帮助! 咨询服务合同范本 合同号:__ 本合同由委托咨询者为一方,××国际咨询公司为另一方,于19__年__月__日在中国××签订。 鉴于委托方意图从咨询者处得到完成××项目的咨询服务,且咨询者已向雇主表明其拥有进行这项服务所要求的专业技术、人员和技术资源,并同意提供服务,双方特同意按以下条款签订本合同: 1.定义 除非合同中另有说明,本合同的下列术语具有以下含义: a)“委托方”指×××; b)“咨询者”指×××; c)“适用法律”指在中华人民共和国内具有法律效力的法律和其它文件; d)“合同”指委托方和咨询者之间签订的合同; e)“外国货币”指任何非人民币的货币; f)“服务”指咨询者根据合同条款为完成本项目而进行的工作; g)“分包咨询者”指按合同条款规定分包部分服务的实

体。 2.合同的适用法律及使用语言 本合同及其条款的含义和解释以及合同双方的关系受中华人民共和国法律的制约。 本合同以中英文两种文字书写,但有关本合同的含义及解释以英语合同为准。 3.执行合同的地址 咨询服务将在中国××进行。 4.通知的发出 任何通知都应以英语书写。一方给另一方的通知应按对方随时用书面提供的地址寄出。如果没有收到另一方的地址改变通知,则按以下地址寄出: _____________________ _____________________ _____________________ _____________________ 任何由专人送去或已按以上地址邮寄、电传、传真、电报的通知都视为寄到。 5.税收 咨询者及其人员应自己交纳公司及个人所得税,交纳中

国际项目咨询服务合同范本中英文

国际项目咨询服务合同 合同号:________________ 签订日期:________________ 签订地点:________________ 中国____________公司(以下简称委托方)为一方,______国______________ 公司(以下简称为咨询方)为另一方,双方就_____________的项目咨询服务,授权双方代表按下列条款签订本合同。 第一条合同内容 1.1 委托方希望获得咨询方就_____提供的项目咨询服务,而咨询方愿意提供此项服务。 1.2 项目咨询服务范围详见本合同附件一。 1.3 项目咨询服务的进度安排详见本合同附件二。 1.4 项目咨询服务的人员安排见本合同附件三。 1.5 项目咨询服务自合同生效之日起_____个月内完成,将在_____个月内提交最终项目咨询报告,包括资料、各类案例和图片等。咨询方应免费通报委托方类似信息的最近发展和任何进展,以便委托方能改进该项目的资料。 第二双方的责任和义务 2.1 委托方应向咨询方提供有关的资料、项目咨询报告、图纸和可能得到的信息并给予咨询方开展工作提供力所能及的协助,特别是委托方应在适当时候指定一名总代表以便能随时予以联系。 2.2 委托方应协助咨询方向有关机构取得护照签证、工作许可和咨询方要求的其它文件以使咨询方能进入委托方国家和本工程的现场,但费用由咨询方负担。 2.3 除了合同附件三所列的项目人员外,咨询方还应提供足够数量的称职的项目人员来履行本合同规定的义务。咨询方应对其所雇的履行合同的项目人员负完全责任并使委托方免受其项目人员因执行合同任务所引起的一切损害。 2.4 咨询方应根据咨询服务的内容和进度安排,按时提交咨询项目咨询报告及有关图纸资料。 2.5 咨询方应协助委托方的项目人员获得进入咨询方国家的签证并负责安排食宿,食宿费用由委托方负担。咨询方应为委托方的项目人员提供办公室、必要的设施和交通便利。 2.6 咨询方对因执行其提供的咨询服务而给委托方和委托方工作人员造成的人身损害和财产损失承担责任并予以赔偿,但这种损害或损失是由于咨询方人员在履行本合同的活动中的疏忽所造成的。咨询方仅对本合同项下的工作负责。

国际技术咨询服务合同模板[中英合并版]

国际技术咨询服务合同 Technical Consultancy Service Contract 合同号: ________________________。 Contract No.:________________________. 签订日期: ____________________。 Date of Signature:____________________. 签订地点: ___________________。 Place of Signature:____________________. 中国________________________公司(以下简称委托方)为一方,_____国 __________________________ 公司(以下简称为咨询方)为另一方,双方就 _________________________的技术咨询服务,授权双方代表按下列条款签订本合同。 This Contract is made and entered into through friendly negotiation by and between China_________________________ (hereinafter referred to as “Client”), as one party, and__________________________ (hereinafter referred to as“Consultant”),as the other party, concerning the technical consultancy service of________________________, under the following terms and conditions: 第一条合同容 Article 1 Contents of Technical Consultancy Service 1.1 委托方希望获得咨询方就___________________________提供的技术咨询服务,而咨询方愿意提供此项服务。 Whereas Client desires to obtain the technical consultancy service of from Consultant and Consultant has agreed to perform such services. 1.2 技术咨询服务围详见本合同附件一。 The Scope of Technical Services is defined in Appendix 1. 1.3 技术咨询服务的进度安排详见本合同附件二。 The Time Schedule for the Services is shown in Appendix 2. 1.4 技术咨询服务的人员安排见本合同附件三。 The Manning Schedule is described in Appendix 3. 1.5 技术咨询服务自合同生效之日起_____个月完成,将在_____个月提交最终技术咨询报告,包括图纸、设计资料、各类规和图片等。咨询方应免费通报委托方

咨询协议,Counsalting Service Contract(英文版)

CONSULTING SERVICE CONTRACT This Agreement is made by and between: Party A :【】,an corporation having its principal place of business at 【】Its Business License No.【】; AND Party B :【】,an corporation having its principal place of business at 【】Its Business License No.【】 “Party A”and “Party B” individually referred to as the“Party” and collectively as the “Parties”, Whereas (i)Party A is an independent company (ii)Party B is Party A and Party B, intending to be legally bound, Party A entrust Party B to provide the consulting service, and in consideration of the mutual promises and covenants contained herein, agree as follows: 1.Item of service The “Service” herein referred to, is the . 1) 2)…… 2.Service Period Party B will provide the service to Party A from【】to【】 3.Price and Payment Terms 1)Price: The total service fee is【RMB/USD/HKD】XXXXXXXX (including/excluding tax) 2)Payment Term: Party A agrees to pay the amount of service fees for the following fixed term: ①Within 【】days after the signature date, and Party B begin to provide the service, Party A shall pay【RMB/USD/HKD】XXXXXXXX to Party B, 【】% of the total service fee; ② Within 【】days after the service under the agreement has completely performed, Party A shall pay【RMB/USD/HKD】XXXXXXXX to Party B, 【】% of the total service fee; ……

咨询服务协议范本 英文版

编号:_____________ AGREEMENT ON CONSULTING SERVICES Contractor:________________________ Client:___________________________ 签订日期:_______年______月______日

1. *** (hereafter called Contractor) agrees to provide the following products and services to the Iceberg *** (hereafter called Client): A. Information gathering: Contractor will review the following information compiled by Client: 1). information on attendance at past events 2). samples of past promotional pieces and any recent press coverage 3). samples of past membership flyers 4). financial information from the past three or four years Contractor will also inquire into the availability of any recent market studies on the *** area done by the city government or other groups working on the ***'s economic development. Contractor will also confer by phone with the part-time coordinator and two or three Client board members to get their view of the issues facing Client. B. Member survey: Contractor will design a one-page membership survey. Client will be responsible for duplicating the survey, sending it out to the membership and tallying the responses. C. Contractor will design a "community leader interview" format. Client's board members will call on community leaders and conduct interviews. Contractor will summarize the finding and merge them with the survey responses, giving Client a written report on how it is perceived by members and community, and what people think it should be doing.

国际项目咨询服务合同(中英文)

CONTRACT OF TECHNICAL CONSULTANCY SERVICE 合同号:Contract No. 签订日期:Date of Signature: 签订地点:Place of Signature:_ 中国_______公司(以下简称委托方)为一方,______国______ 公司(以下简称为咨询方)为另一方,双方就______的项目咨询服务,授权双方代表按下列条款签订本合同。 This Contract is made and entered into through friendly negotiation by and between China____(hereinafter referred to as “Client”), as one party, and____(hereinafter referred to as“Consultant”),as the other party, concerning the technical consultancy service of_____, under the following terms and conditions: 第一条合同内容Article 1 Contents of Technical Consultancy Service 1.1 委托方希望获得咨询方就_____提供的项目咨询服务,而咨询方愿意提供此项服务。 Whereas Client desires to obtain the technical consultancy service of from Consultant and Consultant has agreed to perform such services. 1.2 项目咨询服务范围详见本合同附件一。 The Scope of Technical Services is defined in Appendix 1. 1.3 项目咨询服务的进度安排详见本合同附件二。 The Time Schedule for the Services is shown in Appendix 2. 1.4 项目咨询服务的人员安排见本合同附件三。 The Manning Schedule is described in Appendix 3.

咨询费合同范本中英文

咨询费合同范本中英文 合同是当事人或当事两方之间设立、变更、终止民事关系的协议。依法成立的合同,受法律保护。下面就是整理的咨询费合同范本中英文,一起来看一下吧。 商务咨询费合同范本 甲方(委托方): 乙方(被委托方): 签订地点: 签订日期: 两方经平等协商一致签订本合同,以确认各方权利与义务并共同遵守,商务咨询费合同范本。 一、甲方委托乙方服务事项 甲方因融资万元事宜,委托乙方就融资方式、对象选择、操作办法、风险防范措施等事宜,委托乙方提供咨询服务。 二、乙方服务内容 1、帮助甲方联系或者寻找适合甲方融资需求的对象; 2、对甲方拟进行的融资方案进行可行性论证; 3、帮助或者代理甲方与潜在的融资对象进行初步的商业谈判或者协商; 4、根据融资意向两方的具体情况,为甲方拟定融资参考方案; 5、帮助或者指导甲方准备融资方案执行过程中所需的基本资料。

三、咨询服务费 就乙方提供的咨询服务,甲方向乙方支付的报酬为:甲方按实际取得融资额的 %向乙方支付服务费。服务费在融资通过审批并取得前一次性向乙方支付。 四、乙方服务期限 乙方收取甲方按本合同约定支付的服务费后,为甲方提供的服务至以下条件之一出现时止: ⑴甲方与合作对方实现成功合作,即甲方与合作对方主要合作合同签订;⑵甲方以书面形式通知乙方放弃融资计划;⑶甲方已经实际失去融资条件;⑷甲方三次以上放弃与乙方联系的客户进行实质性谈判,合同范本《商务咨询费合同范本》。 五、保密 为履行本合同,甲方向乙方提供的融资信息、关于主体与资信情况的信息,经甲方特别明示为保密信息的,乙方应承担保密责任,未经甲方书面许可不得擅自向第三人提供或者泄露,但为履行本合同所必需的除外。 六、风险承担 1、乙方为履行本合同向甲方提供的所有信息、资料、方案与措施等均供甲方参考,对甲方使用后可能产生的风险不承担任何责任。 2、乙方对帮助或者指导甲方所取得的合作对方的调查资料的真实性,对合作对象资信状况与承担责

咨询服务协议ConsultingAgreement-英文模板

AGREEEMENT FOR CONSULTING SERVICES CITY OF FARMINGTON HILLS THIS AGREEMENT, made and entered into the ________day of __________, 20, ____, by and between the CITY OF FARMINGTON HILLS, a Michigan Municipal Corporation, referred to as the CITY, and _______________________________________________________ with offices located at _____________________________________________________________ hereinafter called the CONSULTING ENGINEER. WITNESSETH: That, in consideration of the mutual covernants and agreements herein contained, the parties hereto do mutually agree as follows: A. CONSTRUCTION PROJECT: The construction project shall consist of B. REVIEW BY THE CITY: The City will require that reviews between the City and the Consultants take place in order that the City’s input can be an integral part of the project. This input may occur at various times during the design of said project. These reviews will consist, as a minimum, of a preliminary review which will follow the preliminary design by the consultant. The second review will take place no later than two weeks prior to the plans being made available to contractors for bidding purposes. The purpose of these reviews will be to allow the City and the consultants to discuss the actual design of the project. This will also allow the City input into the project that may have not been formally discussed in prior meetings. It is possible that this input could result in changes in the design of the project. These reviews must be conducted as the payment schedule is tied to these reviews. C. ENGINEERING SERVICES: The Consulting Engineer shall provide engineering services as follows: SECTION 1 – DESIGN PHASE a. PRELIMINARY:

相关主题
文本预览
相关文档 最新文档