Special Issue (2003), S245–S253 Advances in Geometry ( de Gruyter 2003 Blocking sets in PG

在 System x 3100 上安装 Windows 2003 Server 中文版 (SAS型号)使用机型：System x 3100 M4 （2582）磁盘接口：SATA使用硬盘： 160GB * 2处理器：Intel XEON E3-1200/Core i3 2100/Pentium内存： 4 GB使用网卡：Dual Gigabit ports Intel 82574L一. 安装前的准备：1.安装前需要准备什么：检查并升级主板BIOS到最新版本需要一张有许可证的Windows 2003 Server光盘可支持的硬盘驱动器（请访问ServerProven网站/systems/info/x86servers/serverproven/compat/us/indexsp.html, 查看支持的选件及其部件号）需安装硬盘驱动，服务器整合C100 软RAID芯片，在驱动程序一览表中找此卡对应的驱动如果您需要安装IBM ServeRAID卡在IBM服务器里，您需要下面的卡、光盘、驱动及软盘：可支持的卡（请访问ServerProven网站,查看支持的选件及其部件号）2.下载C100 for Windows 2003驱动，并拷贝驱动文件至软盘Windows 2003非IBM x3100 M4 ServerProven OS,故IBM官方网站没有ServeRAID C100 for Windows 2003驱动程序下载, 我们可以上LSI官网下载2003驱动：/support/products/Pages/default.aspx3. 配置阵列1) 开机2) 按F1进入设置程序3) 进入System Settings 下 Devices and I/O Ports 子菜单将 Configure SATA as 值设为RAID(IDE/AHCI/RAID), 保存设置，重启4) 按F1再次进入SETUP程序，进入System Settings Storage 子菜单，选择LSI软RAID配置程序，如下图5) 第一项为控制器配置，第二项是阵列管理，第三项是硬盘管理，这里我们选择第二项6) 选择Create Configuation7) 选择RAID级别，8) 选择硬盘9) 保存阵列配置10) 查看刚刚配置的阵列信息二. 操作系统安装1.启动服务器，插入“Windows Server 2003 (32 bit) 安装光盘”到CDROM驱动器，用光盘引导系统。

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-0790SAE WEB ADDRESS Copyright 2002 Society of Automotive Engineers, Inc.TABLE OF CONTENTS1.Scope (4)2.References (4)2.1Applicable Publications (4)2.1.1SAE Publications (4)2.1.2ISO Documents (4)3.Definitions (4)4.Acronyms (5)5.Pass-Thru Concept (5)6.Pass-Thru System requirements (6)6.1PC requirements (6)6.2Software Requirements and Assumptions (6)6.3Connection to PC (6)6.4Connection to Vehicle (6)6.5Communication Protocols (6)6.5.1ISO 9141 (7)6.5.2ISO 14230-4 (KWP2000) (7)6.5.3SAE J1850 41.6 kbps PWM (pulse width modulation) (7)6.5.4SAE J1850 10.4 kbps VPW (variable pulse width) (7)6.5.5CAN (7)6.5.6ISO 15765-4 (CAN) (7)6.5.7SAE J2610 DaimlerChrysler SCI (7)6.6Programmable power supply (8)6.7Data Buffering (8)7.Win32 Application Programming Interface (8)7.1API Functions – Overview (8)7.2API Functions - Detailed Information (8)7.2.1PassThruConnect (8)7.2.2PassThruDisconnect (10)7.2.3PassThruReadMsgs (11)7.2.4PassThruWriteMsgs (12)7.2.5PassThruStartPeriodicMsg (13)7.2.6PassThruStopPeriodicMsg (14)7.2.7PassThruStartMsgFilter (14)7.2.8PassThruStopMsgFIlter (16)7.2.9PassThruSetProgrammingVoltage (17)7.2.10PassThruReadVersion (18)7.2.11PassThruGetLastError (19)7.2.12PassThruIoctl (19)7.3IOCTL Section (21)7.3.1GET_CONFIG (21)7.3.2SET_CONFIG (22)7.3.3READ_VBATT (25)7.3.4READ_PROG_VOLTAGE (26)7.3.5FIVE_BAUD_INIT (26)7.3.6FAST_INIT (26)7.3.7CLEAR_TX_BUFFER (27)7.3.8CLEAR_RX_BUFFER (27)7.3.9CLEAR_PERIODIC_MSGS (27)7.3.10CLEAR_MSG_FILTERS (27)7.3.11CLEAR_FUNCT_MSG_LOOKUP_TABLE (28)7.3.12ADD_TO_FUNCT_MSG_LOOKUP_TABLE (28)7.3.13DELETE_FROM_FUNCT_MSG_LOOKUP_TABLE (29)8.Message Structure (29)8.1 C / C++ Definition (29)8.2Elements (29)8.3Message Data Formats (30)8.3.1CAN Data Format (30)8.3.2ISO 15765-4 Data Format (30)8.3.3SAE J1850PWM Data Format (31)8.3.4SAE J1850VPW Data Format (31)8.3.5 ISO 9141 Data Format (32)8.3.6ISO 14230-4 Data Format (32)8.3.7SCI Data Format (32)8.4Message Flag and Status Definitions (33)8.4.1RxStatus (33)8.4.2TxFlags (33)9.DLL Installation and Registration (34)9.1Naming of Files (34)9.2Win32 Registration (34)9.2.1User Application Interaction with the Registry (36)9.2.2Attaching to the DLL from an application (37)10.Return Value Error Codes (37)Appendix A General ISO 15765-2 Flow Control Example (39)A.1Normal Addressing Used (39)A.2General Request Message Flow Example (39)A.3General Response Message Flow Example (40)Appendix B Message Filter Usage Example (42)B.1Filter Usage (42)B.2Transmission of a Multi-Frame Request Message (42)B.3Reception of a Multi-Frame Response Message (42)B.4Filter Configuration (42)B.4.1Request Message Transmission (44)B.4.2Response Message Reception (45)B.5ISO 15765-2 Extended Addressing Notes (46)1.Scope—This SAE Recommended Practice provides the framework to allow reprogramming softwareapplications from all vehicle manufacturers the flexibility to work with multiple vehicle data link interface tools from multiple tool suppliers. This system enables each vehicle manufacturer to control the programming sequence for electronic control units (ECU’s) in their vehicles, but allows a single set of programming hardware and vehicle interface to be used to program modules for all vehicle manufacturers.This document does not limit the hardware possibilities for the connection between the PC used for the software application and the tool (e.g., RS-232, RS-485, USB, Ethernet…). Tool suppliers are free to choose the hardware interface appropriate for their tool. The goal of this document is to ensure that reprogramming software from any vehicle manufacturer is compatible with hardware supplied by any tool manufacturer.The U.S. Environmental Protection Agency (EPA) and the California Air Resources Board (ARB) have proposed requirements for reprogramming vehicles for all manufacturers by the aftermarket repair industry.This document is intended to meet those proposed requirements for 2004 model year vehicles. Additional requirements for the 2005 model year may require revision of this document, most notably the inclusion of SAE J1939 for some heavy-duty vehicles. This document will be reviewed for possible revision after those regulations are finalized and requirements are better understood. Possible revisions include SAE J1939 specific software and an alternate vehicle connector, but the basic hardware of an SAE J2534 interface device is expected to remain unchanged.2.References2.1Applicable Publications—The following publications form a part of this specification to the extent specifiedherein. Unless otherwise indicated, the latest version of SAE 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 InterfaceSAE J1939—Truck and Bus Control and Communications Network (multiple parts apply)SAE J1962—Diagnostic ConnectorSAE J2610—DaimlerChrysler Information Report for Serial Data Communication Interface (SCI)2.1.2ISO D O CUMENTS—Available from ANSI, 25 west 43rd Street, New York, NY 10036-8002.ISO 7637-1:1990—Road vehicles—Electrical disturbance by conduction and coupling—Part 1: Passenger cars and light commercial vehicles with nominal 12 V supply voltageISO 9141:1989—Road vehicles—Diagnostic systems—Requirements for interchange of digital information ISO 9141-2:1994—Road vehicles—Diagnostic systems—CARB requirements for interchange of digital informationISO 11898:1993—Road vehicles—Interchange of digital information—Controller area network (CAN) for high speed communicationISO 14230-4:2000—Road vehicles—Diagnostic systems—Keyword protocol 2000—Part 4: Requirements for emission-related systemsISO/DIS15765-2—Road vehicles—Diagnostics on controller area networks (CAN)—Network layer servicesISO/DIS15765-4—Road vehicles—Diagnostics on controller area networks (CAN)—Requirements for emission-related systems3.Definitions3.1Registry—A mechanism within Win32 operating systems to handle hardware and software configurationinformation.4.AcronymsAPI Application Programming InterfaceASCII American Standard for Character Information InterchangeCAN Controller Area NetworkCRC Cyclic Redundancy CheckDLL Dynamic Link LibraryECU Electronic Control UnitIFR In-Frame ResponseIOCTL Input / Output ControlKWP Keyword ProtocolOEM Original Equipment ManufacturerPC Personal ComputerPWM Pulse Width ModulationSCI Serial Communications InterfaceSCP Standard Corporate ProtocolUSB Universal Serial BusVPW Variable Pulse Width5.Pass-Thru Concept—Programming application software supplied by the vehicle manufacturer will run on acommonly available generic PC. This application must have complete knowledge of the programming requirements for the control module to be programmed and will control the programming event. This includes the user interface, selection criteria for downloadable software and calibration files, the actual software and calibration data to be downloaded, the security mechanism to control access to the programming capability, and the actual programming steps and sequence required to program each individual control module in the vehicle.This document defines the following two interfaces for the SAE J2534 pass-thru device:a.Application program interface (API) between the programming application running on a PC and asoftware device driver for the pass-thru deviceb.Hardware interface between the pass-thru device and the vehicleAll programming applications shall utilize the common SAE J2534 API as the interface to the pass-thru device driver. The API contains a set of routines that may be used by the programming application to control the pass-thru device, and to control the communications between the pass-thru device and the vehicle. The pass-thru device will not interpret the message content, allowing any message strategy and message structure to be used that is understood by both the programming application and the ECU being programmed. Also, because the message will not be interpreted, the contents of the message cannot be used to control the operation of the interface. For example, if a message is sent to the ECU to go to high speed, a specific instruction must also be sent to the interface to go to high speed.The manufacturer of an SAE J2534 pass-thru device must supply both the device driver software and the pass-thru device hardware that communicates directly with the vehicle. The interface between the PC and the pass-thru device can be any technology chosen by the tool manufacturer, including RS-232, RS-485, USB, Ethernet, or any other current or future technology, including wireless technologies.The OEM programming application does not need to know the hardware connected to the PC, which gives the tool manufacturers the flexibility to use any commonly available interface to the PC. The pass-thru device does not need any knowledge of the vehicle or control module being programmed. This will allow all programming applications to work with all pass-thru devices to enable programming of all control modules for all vehicle manufacturers.Figure 1 shows the relationship between the various components required for pass-thru programming and responsibilities for each component:FIGURE 1—SAE J2534 OVERVIEW6.Pass-Thru System Requirements6.1PC Requirements—Generic PC running a Win32 Operating System (e.g., Windows 95/Windows 98/WindowsNT/Windows Millennium Edition, Windows 2000, Windows XP, …). The PC should be capable of connection to the Internet.6.2Software Requirements and Assumptions—Reprogramming applications can assume that the PC will beconnected to the Internet, although not all applications will require this. The OEM application is limited to a single thread for communication with the tool manufacturer DLL/API. Multiple protocols may be connected and communicated on sequentially (serialized) from the single application thread. This will prevent the unnecessary complexity of determining what message responses belong to which application thread.6.3Connection to PC—The interface between the PC and the pass-thru device shall be determined by themanufacturer of the pass-thru device. This can be RS-232, USB, Ethernet, IEEE1394, Bluetooth or any other connection that allows the pass-thru device to meet all other requirements of this document, including timing requirements. The tool manufacturer is also required to include the device driver that supports this connection so that the actual interface used is transparent to both the PC programming application and the vehicle.6.4Connection to Vehicle—The interface between the pass-thru device and the vehicle shall be an SAE J1962connector for serial data communications. The maximum cable length between the pass-thru device and the vehicle is five (5) meters. Vehicle manufacturers will need to supply information about necessary connections to any connector other than the SAE J1962 connector.6.5Communication Protocols—A fully compliant pass-thru interface shall support all communication protocolsas specified in this section. Additionally, the pass-thru device must support simultaneous communication of an ISO 9141 OR ISO 14230-4 protocol AND an SAE J1850 protocol AND a CAN or SCI based protocol during a single programming event. Note that only one type of SAE J1850 is required per programming event, as the two types of SAE J1850 are mutually exclusive on any given vehicle. As well, CAN and SCI are mutually exclusive on some vehicles as the same pins are used.The following communication protocols shall be supported:6.5.1ISO 9141—The following specifications clarify and, if in conflict with ISO 9141, override any relatedspecifications in ISO 9141:a.The maximum sink current to be supported by the interface is 100 mA.b.The range for all tests performed relative to ISO 7637-1 is –1.0 to +40.0 V.c.The minimum bus idle period before the interface shall transmit an address, shall be 300 ms.d.Support following baud rate with ±0.5% tolerance: 10400.e.Support following baud rates with ±2% tolerance: 9600, 9615, 10000, 10870, 11905, 12500, 13158,13889, 14706, and 15625.f.Support odd and even parity in addition to the default of no parity, with seven or eight data bits.Always one start bit and one stop bit.6.5.2ISO 14230-4 (KWP2000)—The ISO 14230-4 protocol is the same as the ISO 9141 protocol with thefollowing additions:a.The interface will handle the tester present message and 0x78 response code automatically (i.e.,without intervention from the PC).6.5.3SAE J1850 41.6 KBPS PWM (PULSE WIDTH MODULATIO N)—The following additional features of SAE J1850must be supported by the pass-thru device for 41.6 kbps PWM:a.Capable of high speed mode of 83.3 kbps.b.Recommend Ford approved SAE J1850PWM(SCP) physical layer6.5.4SAE J1850 10.4 KBPS VPW (VARIABLE PULSE WIDTH)—The following additional features of SAE J1850 mustbe supported by the pass-thru device for 10.4 kbps VPW:a.High speed mode of 41.6 kbpsb.4K block transfer6.5.5CAN—The following features of ISO 11898 must be supported by the pass-thru device:a.250 and 500 kbpsb.11 and 29 bit identifiersc.Support for 80% ± 2% and 68.5% ± 2% bit sample pointd.Pass-thru message interface (i.e., raw CAN frames with no flow control in the pass-thru device)6.5.6ISO 15765-4 (CAN)—The following features of ISO 15765-4 must be supported by the pass-thru device:a.250 and 500 kbpsb.11 and 29 bit identifiersc.Support for 80% ± 2% bit sample pointd.To maintain acceptable programming times, the transport layer flow control function, as defined in ISO15765-2, must be incorporated in the pass-thru device (see Appendix A). If the application does notuse the ISO 15765-2 transport layer flow control functionality, the CAN protocol will allow for anycustom transport layer.6.5.7SAE J2610 D AIMLER C HRYSLER SCI—Reference the SAE J2610 Information Report for a description of theSCI protocol.6.6Programmable Power Supply—The interface shall be capable of supplying between 5 and 20 volts to one ofthe following pins (6, 9, 11, 12, 13 or 14) on the SAE J1962 diagnostic connector, or to an auxiliary pin which would need to be connected to the vehicle via a cable that is unique to the vehicle. As well, short to ground capability on pin 15 is required. The following requirements shall be met by the power supply:a.Minimum 5 Vb.Maximum 20 Vc.Accuracy ±0.1 Vd.Maximum source current 200 mAe.Maximum sink current 300mA (only for SHORT_TO_GROUND option).f.Maximum 1 ms settling time (required for SCI protocol, reference SAE J2610 Information Report)g.Pin assignment software selectable6.7Data Buffering—The interface shall be capable of buffering a 4K byte transmit message as well as a 4K bytereceive message.7.Win32 Application Programming Interface7.1API Functions – Overview—To conform to this document a vendor supplied API implementation (DLL) mustsupport the functions included in Figure 2.FIGURE 2—SAE J2534 API FUNCTIONS7.2API Functions - Detailed Information7.2.1P ASS T HRU C ONNECT—This function is used to establish a logical connection with a protocol channel. Afterthis function is called, the value pointed to by pChannelID is used as the logical identifier for the connection.The DLL can use this function to initialize data structures and device drivers. If the function operates successfully, a value of STATUS_NOERROR is returned and a valid channel ID will be placed in <pChannelID>. All future interactions with the protocol channel will be done using the pChannelID. Note that all filters for the given protocol will be cleared with this function.7.2.1.1 C / C++ Prototypeextern “C” long WINAPI PassThruConnect(unsigned long ProtocolID,unsigned long Flags,unsigned long *pChannelID)7.2.1.2ParametersProtocolID Protocol ID.Flags Connection flags, normally set to zero.pChannelID Pointer to location for the channel ID that is assigned by the DLL.7.2.1.3Flag Values—See Figure 3.FIGURE 3—FLAG VALUES7.2.1.4ProtocolID Values—See Figure 4.FIGURE 4—PROTOCOL ID VALUES7.2.1.5Return Values—See Figure 5.FIGURE 5—RETURN VALUES7.2.2P ASS T HRU D ISCONNECT—This function is used to terminate a logical connection with a protocol channel. TheDLL can use this function to de-allocate data structures and deactivate any device drivers. If the function operates successfully, a value of STATUS_NOERROR is returned. After this call the Channel ID will no longer be valid.7.2.2.1 C / C++ Prototypeextern “C” long WINAPI PassThruDisconnect(unsigned long ChannelID)7.2.2.2ParametersChannelID The channel ID assigned by the PassThruConnect function.7.2.2.3Return Values—See Figure 6.FIGURE 6—RETURN VALUES7.2.3P ASS T HRU R EAD M SGS—This function reads messages from the receive buffer in the order they werereceived. If the function operates successfully, a value of STATUS_NOERROR is returned. Note that the ISO 15765-2 FirstFrame and TxDone indications will be returned as messages when calling this function.Also note that all messages and indications shall be read in the order that they occurred on the bus.7.2.3.1 C / C++ Prototypeextern “C” long WINAPI PassThruReadMsgs(unsigned long ChannelID,PASSTHRU_MSG *pMsg,unsigned long *pNumMsgs,unsigned long Timeout)7.2.3.2ParametersChannelID The channel ID assigned by the PassThruConnect function.pMsg Pointer to message structure(s).pNumMsgs Pointer to location where number of messages to read is specified. On return from the function this location will contain the actual number of messages read.Timeout Read timeout (in milliseconds). If a value of 0 is specified the function returns immediately.Otherwise, the API will not return until the Timeout has expired, an error has occurred, or thedesired number of messages have been read. If the number of messages requested havebeen read, the function shall not return ERR_TIMEOUT, even if the timeout value is zero. 7.2.3.3Return Values—See Figure 7.FIGURE 7—RETURN VALUES7.2.4P ASS T HRU W RITE M S GS—This function is used to send messages. The messages are placed in the bufferand sent in the order they were received. If the function operates successfully, a value of STATUS_NOERROR is returned. To perform blocking writes (i.e., the function does not return until message is successfully sent on the vehicle network or a timeout occurs), use the blocking flag in the TxFlags element of the message structure (Reference 8.4.2).7.2.4.1 C / C++ Prototypeextern “C” long WINAPI PassThruWriteMsgs(unsigned long ChannelID,PASSTHRU_MSG *pMsg,unsigned long *pNumMsgs,unsigned long Timeout)7.2.4.2ParametersChannelID The channel ID assigned by the PassThruConnect function.pMsg Pointer to message structure(s).pNumMsgs Pointer to the location where number of messages to write is specified. On return will contain the actual number of messages that were transmitted or placed in the transmitqueue.Timeout Write timeout (in milliseconds). If a value of 0 is specified the function returns immediately.Otherwise, the API will not return until the Timeout has expired, an error has occurred, or thedesired number of messages have been written. If the number of messages requested havebeen written, the function shall not return ERR_TIMEOUT, even if the timeout value is zero.7.2.4.3Return Values—See Figure 8.FIGURE 8—RETURN VALUES7.2.5P ASS T HRU S TART P ERIODIC M SG—This function starts sending a message at the specified interval. If thefunction operates successfully, a value of STATUS_NOERROR is returned. The maximum number of periodic messages is ten.7.2.5.1 C / C++ Prototypeextern “C” long WINAPI PassThruStartPeriodicMsg(unsigned long ChannelID,PASSTHRU_MSG *pMsg,unsigned long *pMsgID,unsigned long TimeInterval)7.2.5.2ParametersChannelID The channel ID assigned by the PassThruConnect function.pMsg Pointer to message structure.pMsgID Pointer to location for the message ID that is assigned by the DLL.TimeInterval Time interval between the start of successive transmissions of this message, in milliseconds. The valid range is 5-65535 milliseconds.7.2.5.3Return Values—See Figure 9.FIGURE 9—RETURN VALUES7.2.6P ASS T HRU S TOP P ERIODIC M SG—This function stops the process of sending a periodic message. If thefunction operates successfully, a value of STATUS_NOERROR is returned. After this call the MsgID will be invalid.7.2.6.1 C / C++ Prototypeextern “C” long WINAPI PassThruStopPeriodicMsg(unsigned long ChannelID,unsigned long MsgID)7.2.6.2ParametersChannelID The channel ID assigned by the PassThruConnect function.MsgID Message ID that is assigned by the PassThruStartPeriodicMsg function.7.2.6.3Return Values—See Figure 10.FIGURE 10—RETURN VALUES7.2.7P ASS T HRU S TART M SG F ILTER—This function starts filtering incoming messages. If the function operatessuccessfully, a value of STATUS_NOERROR is returned. The maximum number of message filters is ten.See Appendices A and B for a description of the use of these message filters for transmission and reception of multi-frame messages.7.2.7.1 C / C++ Prototypeextern “C” long WINAPI PassThruStartMsgFilter(unsigned long ChannelID,unsigned long FilterType,PASSTHRU_MSG *pMaskMsg,PASSTHRU_MSG *pPatternMsg,PASSTHRU_MSG *pFlowControlMsg,unsigned long *pMsgID)7.2.7.2ParametersChannelID The channel ID assigned by the PassThruConnect function.FilterType Designates:PASS_FILTER – allows matching messages into the receive queue.BLOCK_FILTER - keeps matching messages out of the receive queue.FLOW_CONTROL_FILTER – defines a filter and outgoing flow control messageto support the ISO 15765-2 flow control mechanism.pMaskMsg Designates a pointer to the mask message that will be applied to each incoming message (i.e., the mask message that will be ANDed to each incoming message) tomask any unimportant bits.The usage of the pMaskMsg allows for configuring a filter that passes thru multiple CANidentifiers. In case the filter allows for the reception of multiple CAN identifiers thenthose messages are only allowed to be SingleFrame messages, because only a singleFlowControl CAN identifier can be specified.pPatternMsg Designates a pointer to the pattern message that will be compared to the incoming message after the mask message has been applied. If the result matches this patternmessage and the FilterType is PASS_FILTER, then the incoming message will added tothe receive queue (otherwise it will be discarded). If the result matches this patternmessage and the FilterType is BLOCK_FILTER, then the incoming message will bediscarded (otherwise it will be added to the receive queue). Message bytes in thereceived message that are beyond the DataSize of the pattern message will be treatedas “don’t care”.pFlowControlMsg Designates a pointer to an ISO 15765-2 flow control message. This message will be sent out when the received message ANDed with the message pointed to by pMaskMsgmatches the message pointed to by pPatternMsg and the interface is receiving asegmented message. This message shall only contain the message ID (and extendedaddress byte if the ISO15765_EXT_ADDR flag is set). The interface will provide thePCI bytes when this message is transmitted. To modify the BS and STmin values thatare used by the interface, reference the IOCTL section. This pointer only applies to theFLOW_CONTROL_FILTER type and must be set to NULL when the FilterType isPASS_FILTER or BLOCK_FILTER.pMsgID Pointer to location for the message ID that is assigned by the DLL.7.2.7.3Filter Type Values—See Figure 11.FIGURE 11—FILTER TYPE VALUES7.2.7.4Return Values—See Figure 12.FIGURE 12—RETURN VALUES7.2.8P ASS T HRU S TOP M SG FI LTER—This function stops the process of filtering messages. If the function operatessuccessfully, a value of STATUS_NOERROR is returned. After this call the MsgID will be invalid.7.2.8.1 C / C++ Prototypeextern “C” long WINAPI PassThruStopMsgFilter(unsigned long ChannelID,unsigned long MsgID)7.2.8.2PrametersChannelID The channel ID assigned by the PassThruConnect function.MsgID Message ID that is assigned by the PassThruStartMsgFilter function.7.2.8.3Return Values—See Figure 13.FIGURE 13—RETURN VALUES7.2.9P ASS T HRU S ET P ROGRAMMING V OLTAG E—This function sets a programming voltage on a specific pin. If thefunction operates successfully, a value of STATUS_NOERROR is returned. It is up to the application programmer to insure that voltages are not applied to any pins incorrectly. This function cannot protect from incorrect usage (e.g., applying a voltage to pin 6 when it is being used for the CAN protocol). Note that for SCI protocol, the application would set the PinNumber, set the Voltage to VOLTAGE_OFF, and set SCI_TX_VOLTAGE in TxFlags of the message to pulse the programming voltage to 20 V DC.7.2.9.1 C / C++ Prototypeextern “C” long WINAPI PassThruSetProgrammingVoltage(unsigned long PinNumber,unsigned long Voltage)7.2.9.2ParametersPinNumber The pin on which the programming voltage will be set. Valid options are:0 – Auxiliary output pin (for non-SAE J1962 connectors)6 – Pin 6 on the SAE J1962 connector.9 – Pin 9 on the SAE J1962 connector.11 – Pin 11 on the SAE J1962 connector.12 – Pin 12 on the SAE J1962 connector.13 – Pin 13 on the SAE J1962 connector.14 – Pin 14 on the SAE J1962 connector.15 – Pin 15 on the SAE J1962 connector (short to ground only).Voltage The voltage (in millivolts) to be set. Valid values are:5000mV-20000mV (limited to 200mA with a resolution of ±100 millivolts for pins 0, 6, 9, 11,12, 13, and 14).VOLTAGE_OFF – To turn output off (disconnect).SHORT_TO_GROUND – Short pin to ground (pin 15 only).7.2.9.3Voltage Values—See Figure 14.FIGURE 14—VOLTAGE VALUES7.2.9.4Return Values—See Figure 15.FIGURE 15—RETURN VALUES7.2.10P ASS T HRU R EAD V ERSION—This function returns the version strings associated with the DLL. If the functionoperates successfully, a value of STATUS_NOERROR is returned. A buffer of at least eighty (80) characters must be allocated for each pointer by the application.7.2.10.1 C / C++ Prototypeextern “C” long WINAPI PassThruReadVersion(char*pFirmwareVersion,char*pDllVersion,char*pApiVersion)7.2.10.2ParameterspFirmwareVersion Pointer to Firmware version string in XX.YY format (e.g., 01.01). This string isdetermined by the interface vendor that supplies the device.pDllVersion Pointer to DLL version string in XX.YY format (e.g., 01.01). This string is determinedby the interface vendor that supplies the DLL.pApiVersion Pointer to API version string in XX.YY format. This string corresponds to the date ofthe balloted document.October 2001 Ballot = “01.01”December 2001 Ballot = “01.02”February 2002 Final = “02.02”7.2.10.3Return Values—See Figure 16.FIGURE 16—RETURN VALUES。

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.Copyright © 2003 SAE InternationalAll rights reserved. No part of this publication may be reproduced, stored in a retrieval system or transmitted, in any form or by any means, electronic, mechanical, photocopying,recording, or otherwise, without the prior written permission of SAE.TO PLACE A DOCUMENT ORDER:Tel: 877-606-7323 (inside USA and Canada)Tel: 724-776-4970 (outside USA)Fax: 724-776-0790Email: custsvc@SAE WEB ADDRESS: J1Borate Ester Based Brake Fluids1.Scope—This SAE Recommended Practice was prepared to provide engineers, designers, and manufacturersof motor vehicles with a set of minimum performance standards which covers the next level of performanceproperties above those of the present SAE J1703 brake fluid standard. These fluids are not intended for useunder arctic conditions or in braking systems requiring the use of mineral oil based hydraulic fluid.These fluids are designed for use in braking systems fitted with rubber cups and seals made from naturalrubber (NR), styrene-butadiene rubber (SBR), or a terpolymer of ethylene, propylene, and a diene (EPDM).These fluids are not designed to operate in a pumped or a clutch braking system, especially those hydraulicsystems requiring a mineral oil based fluid.2.References 2.1Applicable Publications—The following publications form a part of this specification to the extent specifiedherein. The latest issue of SAE publications shall apply.2.1.1SAE P UBLICATIONS —Available from SAE, 400 Commonwealth Drive, Warrendale, PA 15096-0001.SAE J527—Brazed Double Wall Low Carbon Steel TubingSAE J1703—Motor Vehicle Brake Fluid 2.1.2ASTM P UBLICATIONS —Available from ASTM, 100 Barr Harbor Drive, West Conshohocken, PA 19428-2959.ASTM D 91—Test Method for Precipitation Number of Lubricating OilsASTM D 395—T est Methods for Rubber Property—Compression SetASTM D 412—T est Methods for Rubber Properties in TensionASTM D 445—T est Method for Kinematic Viscosity of T ransparent and Opaque Liquids (and theCalculation of Dynamic Viscosity)ASTM D 664—T est Method for Neutralization Number of Potentiometric TitrationASTM D 746—T est Method for Brittleness Temperature of Plastics and Elastomers by ImpactASTM D 865—T est Method for Rubber—Deterioration by heating in Air (Test T ube Enclosure)ASTM D 1120—Method of Test for Boiling Point of Engine CoolantsASTM D 1209—Test Method for Color of Clear Liquids (Platinum-Cobalt Pigments)ASTM D 1364—Test Method for Water in Volatile Solvents (Fischer Reagent Titration Method)ASTM D 1415—Method of Test for International H ardness of Vulcanized Natural Rubber and SyntheticRubbersASTM D1613—T est Method for Acidity in Volatile Solvents and Chemical Intermediates Used in Paint, Varnish, Lacquer, and Related ProductsASTM D 2240—Method of T est for Indentation Hardness of Rubber and Plastics by Means of a Durometer ASTM D3182—Recommended Practice for Rubber-Materials, Equipment, and Procedures for Mixing Standard Compounds and Preparing Standard Vulcanized SheetsASTM D3185—Methods for Rubber-Evaluation of SBR (Styrene-Butadiene Rubber) including Mixtures with OilASTM E 1—Specification for ASTM ThermometersASTM E 145—Specification for Gravity-Convection and Forced-Ventilation Ovens2.2Related Publications—The following publications are provided for information purposes only and are not arequired part of this document.2.2.1ASTM P UBLICATIONS—Available from ASTM, 100 Barr Harbor Drive, West Conshohocken, PA 19428-2959.ASTM D 344—Method of Test for Relative Dry Hiding Power of PaintsASTM E 260—Standard Recommended Practice for General Gas Chromatography ProcedureASTM E 298—Evaluation of Benzoyl Peroxides3.Materials—The quality of the materials used shall be such that the resulting product will conform to therequirements of these specifications and ensure uniformity of performance.4.Requirements4.1Equilibrium Reflux Boiling Point (ERBP)—Brake fluid when tested by the procedure specified in5.1 shallhave an equilibrium reflux boiling point not less than 230 °C (446 °F).4.2Wet Equilibrium Reflux Boiling Point—Brake fluid when tested by the procedure specified in5.2 shall have awet equilibrium reflux boiling point not less than 155 °C (311 °F).4.3Viscosity—Brake fluid when tested by the procedure specified in5.3 shall have the following kinematicviscosities:4.3.1A T –40 °C (–40 °F)—Not more than 1800 mm2/s (1800 cSt)4.3.2A T 100 °C (212 °F)—Not less than 1.5 mm2/s (1.5 cSt)4.4pH Value—Brake fluid when tested by the procedure specified in5.4 shall have a pH value not less than 7.0and not more than 11.5.4.5Fluid Stability4.5.1H IGH-T EMPERATURE S TABILITY—When tested by the procedure specified in 5.5.1, the equilibrium refluxboiling point of the brake fluid shall not change by more than 5 °C (9 °F) increase or decrease.4.5.2C HEMICAL S TABILITY—When tested by the procedure specified in 5.5.2 the test fluid mixture shall show nochemical reversion as evidenced by a change in recorded temperature of more than 5 °C (9 °F) increase or decrease.-2-标准分享网 免费下载-3-4.6Corrosion—See T able 1.4.6.1D RY F LUID (AS RECEIVED )—Brake fluid, when tested by the procedure specified in5.6.1, shall not causecorrosion exceeding the limits shown in Table 1. The metal strip outside of the area where the strips are in contact shall neither be pitted nor roughened to an extent discernible to the naked eye, but staining or discoloration is permitted. The fluid at the end of the test shall show no jelling at 23 °C ± 5 °C (73.4 °F ±9°F). No crystalline-type deposit shall form and adhere to either the glass walls or the surface of the metal strips. The fluid shall not contain more than 0.10% sediment by volume.The rubber specimens at the end of the test shall show no disintegration, as evidenced by blisters or sloughing indicated by carbon black separation on the surface of the rubber cup.4.6.2B RAKE F LUID WITH WATER —The brake fluid containing water, when tested by the procedure specified in5.6.2,shall not cause corrosion exceeding the limits shown in Table 1. The metal strip outside of the area where the strips are in contact shall neither be pitted nor roughened to an extent discernible to the naked eye, but staining or discoloration is permitted. The fluid/water mixture at the end of the test shall show no jelling at 23°C ± 5 °C (73.4 °F ± 9 °F). No crystalline-type deposit shall form and adhere to either the glass walls or the surface of the metal strips. The fluid/water mixture shall not contain more than 0.10% sediment by volume. The fluid/water mixture shall have a pH of not less than 7.0 and not more than 11.5.The rubber test specimens at the end of the test shall show no disintegration, as evidenced by blisters or sloughing indicated by carbon black separation on the surface of the rubber cup. The hardness of the SBR cup shall not decrease by more than 15 IRHD and the hardness of the EPDM rubber specimen shall not decrease by more than 10 IRHD. The SBR rubber cup shall not decrease in volume and shall not increase in volume by more than 16%. The EPDM rubber specimen shall not decrease in volume and shall not increase in volume by more than 10%.4.7Fluidity and Appearance at Low Temperatures 4.7.1A T –40 °C (–40 °F)—When brake fluid is tested by the procedure specified in 5.7.1, the fluid shall show nostratification, sedimentation, or crystallization. Upon inversion of the sample bottle, the air bubble shall travel to the top of the fluid in not more than 10 s. Cloudiness is permissible, but on warming to room temperature 23 °C ± 5 °C (73.4 °F ± 9 °F), this fluid shall regain its original unformity, appearance, and clarity.4.7.2A T –50 °C (–58 °F)—When brake fluid is tested by the procedure specified in 5.7.2, the fluid shall show no stratification, sedimentation, or crystallization. Upon inversion of the sample bottle, the air bubble shall travel to the top of the fluid in not more than 35 s. Cloudiness is permissible, but on warming to room temperature 23 °C ± 5 °C (73.4 °F ± 9 °F), the fluid shall regain its original unformity, appearance , and clarity.TABLE 1—CORROSION TEST STRIPS AND WEIGHT CHANGESTest Strips (1)1.Obtainable from the Society of Automotive Engineers, 400 Common-wealth Drive, Warrendale, P A 15096-0001.RM Number Maximum PermissibleWeight Change(mg/cm 2 of surface area)Tinned Iron6A 0.2Steel70.2Aluminum80.1Cast Iron90.2Brass100.4Copper 110.44.8Water Tolerance4.8.1A T –40 °C (–40 °F)—When the humidified brake fluid is tested by the procedure specified in5.8.1, the blackcontrast lines on a hiding power chart shall be clearly discernible when viewed through the fluid in the centrifuge tube. The fluid shall show no stratification or sedimentation. Upon inversion of the centrifuge tube, the air bubble shall travel to the top of the fluid in not more than 10 s.4.8.2A T 60 °C (140 °F)—When brake fluid is tested by the procedure specified in5.8.2, the fluid shall show nostratification, and sedimentation shall not exceed 0.05% by volume after centrifuging when fluid is tested for qualification, or shall not exceed 0.15% by volume for a commercial packaged fluid.4.9Compatibility4.9.1A T –40 °C (–40 °F)—When brake fluid is tested by the procedure specified in5.9.1, the black contrast lineson a hiding power chart shall be clearly discernible when viewed through the fluid in the centrifuge tube. The fluid shall show no stratification or sedimentation.4.9.2A T 60 °C (140 °F)—When brake fluid is tested by the procedure specified in5.9.2, the fluid shall show nostratification, and sedimentation shall not exceed 0.05% by volume after centrifuging.4.10Resistance to Oxidation—When the humidified brake fluid is tested by the procedure specified in5.10, itshall not cause the metal strips outside the areas in contact with the tinfoil to be pitted or roughened to an extent discernible to the naked eye, but staining or discoloration is permitted. No more than a trace of gum shall be deposited on the test strips outside of the areas in contact with the tinfoil. The aluminum strips shall not change in mass by more than 0.05 mg/cm2 and the cast iron strips shall not change in mass by more than0.3 mg/cm2.4.11Effect on Rubber4.11.1Rubber brake cups (RM-3a) subjected to brake fluid as specified in5.11.1 shall show no increase inhardness, shall not decrease in hardness by more than 10 IRH D, and shall show no disintegration as evidenced by blisters or sloughing indicated by carbon black separation on the surface of the rubber cup.Volume increase shall not be less than 1% or greater than 16%.4.11.2Rubber brake cups (RM-3a) subjected to brake fluid as specified in5.11.2 shall show no increase inhardness, shall not decrease in hardness by more than 15 IRH D and shall show no disintegration as evidenced by blisters or sloughing indicated by carbon black separation on the surface of the rubber cup.Volume increase shall not be less than 1% or greater than 16%.4.11.3Rubber slab stock (RM-69) subjected to brake fluid, as specified in5.11.3, shall show no increase inhardness, shall not decrease in hardness by more than 10 IRH D, and shall show no disintegration as evidenced by blisters or sloughing indicated by carbon black separation on the surface of the test specimens.The test specimens shall not decrease in volume and the increase in volume shall not exceed 10%.4.11.4Rubber slab stock (RM-69) subjected to brake fluid, as specified in5.11.4, shall show no increase inhardness, shall not decrease in hardness by more than 15 IRH D, and shall show no disintegration as evidenced by blisters or sloughing indicated by carbon black separation on the surface of the test specimens.The test specimens shall not decrease in volume and the increase in volume shall not exceed 10%.-4-标准分享网 免费下载5.Test Procedures5.1Equilibrium Reflux Boiling Point—Determine the equilibrium reflux boiling point of the fluid by ASTM D 1120with the following exceptions:5.1.1 A PPARATUS5.1.1.1 4.4 Thermometer—ASTM E 1, 76 mm immersion, calibrated. Use ASTM 3C or 3F thermometer. Forfluids boiling below 300 °C, ASTM 2C or 2F thermometer may be used.5.1.1.2 4.5 Heat Source—Use a suitable variac-controlled 100 mL heating mantle designed to fit the flask, capableof supplying the heat required to conform to the specified heating and reflux rates. (Supplier: GLAS COL Apparatus Co., Terre Haute, IN. Serial number: 135464. 230 W, 135 V [max.])5.1.1.3Boiling Point Stones RM-755.1.1.4Preparation of Apparatus—6.4 Thoroughly clean and dry all glassware before use. Attach the flask to thecondenser. Place the mantle under the flask and support it with a suitable ring clamp and laboratory-type stand, holding the whole assembly in place by a clamp.NOTE—Place the whole assembly in an area free from drafts or other types of sudden temperature changes.5.1.2P ROCEDURE—7.1 When everything is in readiness, turn on the condenser water and apply heat to the flask atsuch a rate that the fluid is refluxing in 10 min ± 2 min at a rate in excess of 1 drop/s. Immediately adjust heat input to obtain a specified equilibrium reflux rate of 1 to 2 drops/s over the next 5 min ± 2 min period.Maintain a timed and constant equilibrium reflux rate of 1 to 2 drops/s for an additional 2 min; record the average value of four temperature readings taken at 30 s intervals as the equilibrium reflux boiling point.5.1.2.1Report the boiling point to the nearest degree Celsius. Duplicate runs which agree within 3 °C areacceptable for averaging (95% confidence level).5.2Wet Equilibrium Reflux Boiling Point—Humidify the fluid and determine the boiling point.5.2.1H UMIDIFICATION P ROCEDURE—Lubricate the ground-glass joint of a 250 mm ID bowl-form desiccator havingmatched tubulated glass cover and fitted with a No. 8 rubber stopper. Pour 450 mL ± 10 mL of distilled water into the dessicator and insert a perforated porcelain plate (Coors No. 60456 or equivalent). Immediately place one open RM-49 corrosion test jar containing 350 mL ± 5 mL of the test brake fluid into the dessicator.Place a second open RM-49 corrosion test jar containing 350 mL ± 5 mL of TEGME (triethylene glycol monomethyl ether, brake fluid grade - Appendix E) (RM-71) into the same desiccator. The water content of the TEGME control fluid at the start of exposure shall have been adjusted to 0.50% ± 0.05% by weight (Karl Fischer analysis or equivalent). Replace desiccator cover and insert at once into an ASTM E 145, Type II A, forced ventilation oven set at 50 °C ± 1 °C (122 °F ± 1.8 °F).Periodically, during oven humidification, remove the rubber stopper from the desiccator and, using a long needle hypodermic syringe, quickly sample the control fluid and determine its water content. When the water content of the control fluid has reached 3.70% ± 0.05% by weight, remove the dessicator from the oven and seal the test jar promptly using a screw-cap lid (RM-63). Allow the sealed jar to cool for 60 to 90 min at 23 °C ± 5 °C (73.4 °F ± 9 °F).5.2.2W ET E QUILIBRIUM R EFLUX B OILING P OINT—Humidify the fluid as described in 5.2.1 and determine the boilingpoint as described in 5.1.-5-5.3Viscosity—Determine the kinematic viscosity of the fluid by ASTM D 445.5.3.1Report the viscosity to the nearest mm2/s (centistoke). Duplicate runs which agree within 1.2% relative areacceptable for averaging (95% confidence level).5.4pH Value—Mix the fluid with an equal volume of an 50% ethanol/50% distilled water mixture neutralized to apH of 7. Determine the pH of the resulting solution electrometrically at 23 °C ± 5 °C (73.4 °F ± 9 °F) using a pH meter equipped with a calibrated full range (0 to 14) glass electrode and a calomel reference electrode, as specified in ASTM D 664.5.5Fluid Stability5.5.1H IGH T EMPERATURE S TABILITY—Heat a new sample of the original test brake fluid to a temperature of 185 °C± 2 °C (365 °F ± 3.6 °F) by the procedure specified in 5.1 and maintain at that temperature for 2 h. Then determine the boiling point of this brake fluid as specified in 5.1. The difference between this observed boiling point and that previously determined in 5.1 shall be considered as the change in boiling point of the brake fluid.5.5.2C HEMICAL S TABILITY—Mix 30 mL of brake fluid with 30 mL of SAE Compatibility Fluid described in AppendixB (RM-66-05). Determine the equilibrium reflux boiling point of this fluid mixture by use of the test apparatusspecified in 5.1, applying heat to the flask at such a rate that the fluid is refluxing in 10 min ± 2 min at a rate in excess of 1 drop/s. The reflux rate shall not exceed 5 drops/s. Record the maximum fluid temperature observed during the first minute after the fluid begins refluxing at a rate in excess of 1 drop/s. Over the next15 min ± 1 min, adjust and maintain the rate of reflux to 1 to 2 drops/s. Maintain a timed and constantequilibrium reflux rate of 1 to 2 drops/s for an additional 2 min; record the average value of four temperature readings taken at 30 s intervals as the final equilibrium reflux boiling point. Chemical reversion is evidenced by the decrease in temperature between the maximum fluid temperature recorded and the final equilibrium reflux boiling point.5.6Corrosion5.6.1D RY F LUID (AS RECEIVED)—Prepare two sets of strips from each of the metals listed in Table 1, each striphaving a surface area of 25 cm2 ± 5 cm2 (approximately 8 cm long, 1.3 cm wide, and not more than 0.6 cm thick). Drill a hole between 4 and 5 mm in diameter and about 6 mm from one end of each strip. With the exception of the tinned iron strips, clean the strips by abrading them on all surface areas with 320A (RM-29) or P400 waterproof carborundum paper and isopropanol or ethanol until all surface scratches, cuts, and pits are removed from the strips, using a new piece of carborundum paper for each different type of metal. Wash the strips, including the tinned iron, with isopropanol or ethanol and dry the strips with a clean lint-free cloth and place strips in a desiccator containing desiccant maintained at 23 °C ± 5 °C (73.4 °F ± 9 °F) for at least1 h.Handle the strips with clean forceps after polishing to avoid fingerprint contamination.Weigh each strip to the nearest 0.1 mg and assemble each set of strips on an uncoated steel bolt (RM-61) in the order tinned iron, steel, aluminum, cast iron, brass, and copper, so that the strips are in electrolytic contact. Bend the strips, other than cast iron, so that there is a separation of at least 3 mm between adjacent strips for a distance of about 6 cm from the free end of the strips. (Immerse strip assemblies in isopropanol or ethanol to eliminate fingerprints and then handle only with clean forceps.)Use two SBR cups (RM-3a) and two 25.4 mm x 25.4 mm (1 in x 1 in) EPDM rubber slab stock (RM-69) test specimens as described in Appendix C and Appendix D, respectively.-6-标准分享网 免费下载Obtain two straight-sided round glass jars, having a capacity of approximately 475 mL and inner dimensions of approximately 100 mm in height and 75 mm in diameter (RM-49). T o the RM-49 corrosion test jar, apply four wrappings of 19 mm (3/4 in) Teflon tape around the jar threads allowing a 3 mm (1/8 in) height above the top of the jar. Place one SBR cup (RM-3a) with lip edge facing up, in each of the two glass jars. Use only tinned steel lids vented with a hole 0.8 mm ± 0.1 mm in diameter (RM-64).Insert a metal strip assembly inside each cup with the bolted end in contact with the concavity of the cup and the free end extending upward in the jar. Place one EPDM rubber slab stock (RM-69) test specimen flat on the bottom of the test jar.Add 400 mL of fluid to cover the metal strip assembly in each jar. Tighten the lid and place the jars in an oven maintained at 100 °C ± 2 °C (212 °F ± 3.6 °F) for 120 h ± 2 h. Allow the jars to cool at 23 °C ± 5 °C(73.4 °F ± 9 °F) for 60 to 90 min. Immediately following the cooling period, remove the metal strips from thejars by use of a forceps, removing loose adhering sediment by agitation of the metal strip assembly in the fluid in the jar. Examine test strips and test jars for adhering crystalline deposit, disassemble the metal strips, removing adhering fluid by flushing with water, and clean individual strips by wiping with a cloth wetted with isopropanol or ethanol. Examine the strips for evidence of corrosion and pitting. Place strips in a desiccator containing a desiccant maintained at 23°C ± 5 °C (73.4 °F ± 9 °F) for at least 1 h. Weigh each strip to the nearest 0.1 mg.Determine the difference in weight of each metal strip and divide the difference by the total surface area of the metal strip measured in square centimeters. Average the measured quantities of the duplicates. In the event of a marginal pass on inspection, or of a failure in only one of the duplicates, another set of duplicate test samples shall be run. Both repeat samples must meet all the requirements of 4.6.Immediately following the cooling period, remove the rubber cups from the jars by use of a forceps, removing loose adhering sediment by agitation of the cup in the fluid in the jar.Rinse the rubber specimens in isopropanol or ethanol and air dry cups. Examine the rubber specimens for evidence of sloughing, blisters, and other forms of disintegration.Examine the fluid in the jars for jelling. Agitate the fluid in the jars to suspend and uniformly disperse sediment and transfer a 100 mL portion of this fluid to an ASTM cone-shaped centrifuge tube and determine percent sediment as described in 5.2 of ASTM D 91.Measure the pH value of the corrosion test fluid by the procedure specified in 5.4.5.6.2C ORROSION T EST ON B RAKE F LUID WITH W ATER—Same test procedure as 5.6.1 except the test is performedon a brake fluid containing 5% by volume water.Prepare two sets of strips from each of the metals listed in Table 1 (see Appendix A), each strip having a surface area of 25 cm2 ± 5 cm2 (approximately 8 cm long, 1.3 cm wide, and not more than 0.6 cm thick). Drilla hole between 4 and 5 mm in diameter and about 6 mm from one end of each strip. With the exception ofthe tinned iron strips, clean the strips by abrading them on all surface areas with 320A or P400 waterproof carborundum paper (RM-29) and isopropanol or ethanol until all surface scratches, cuts, and pits are removed from the strips, using a new piece of carborundum paper for each different type of metal. Wash the strips, including the tinned iron, with isopropanol or ethanol and dry the strips with a clean lint-free cloth and place strips in a desiccator containing desiccant maintained at 23 °C ± 5 °C (73.4 °F ± 9 °F) for at least 1 h.Handle the strips with clean forceps after polishing to avoid fingerprint contamination.-7-Weigh each strip to the nearest 0.1 mg and assemble each set of strips on an uncoated steel bolt (RM-61) in the order tinned iron, steel, aluminum, cast iron, brass, and copper, so that the strips are in electrolytic contact. Bend the strips, other than cast iron, so that there is a separation of at least 3 mm between adjacent strips for a distance of about 6 cm from the free end of the strips. (Immerse strip assemblies in isopropanol or ethanol to eliminate fingerprints and then handle only with clean forceps.)Use two SBR cups (RM-3a) and two 25.4 mm x 25.4 mm (1 in x 1 in) EPDM rubber slab stock (RM-69) test specimens as described in Appendix C and Appendix D, respectively.Determine the weight of the cups and rubber slab stock in air (m1) to the nearest 1 mg then determine the apparent weight of the cup and slab stock immersed in distilled water at room temperature (m2). Quickly dip each specimen in alcohol and then blot dry with filter paper free of lint and foreign matter. Measure the hardness of each specimen by the procedure specified in ASTM D 1415 using the Standards Tester.NOTE—ASTM D 2240 may be used for quality control and routine tests when a type A durometer is equipped with a fixture for keeping the plane of the pressure foot on the durometer parallel to the plane of the cup face during measurement.Obtain two straight-sided round glass jars, having a capacity of approximately 475 mL and inner dimensions of approximately 100 mm in height and 75 mm in diameter (RM-49). T o the RM-49 corrosion test jar, apply four wrappings of 19 mm (3/4 in) Teflon tape around the jar threads allowing a 3 mm (1/8 in) height above the top of the jar. Place one SBR cup (RM-3a) with lip edge facing up, in each of the two glass jars. Use only tinned steel lids vented with a hole 0.8 mm ± 0.1 mm in diameter (RM-64).Insert a metal strip assembly inside each cup with the bolted end in contact with the concavity of the cup and the free end extending upward in the jar. Place one EPDM rubber slab stock (RM-69) test specimen flat on the bottom of the test jar.Mix 760 mL of fluid with 40 mL of distilled water.Add 400 mL of the mixture to cover the metal strip assembly in each jar. Tighten the lid and place the jars in an oven maintained at 100 °C ± 2 °C (212 °F ± 3.6 °F) for 120 h ± 2 h. Allow the jars to cool at 23 °C ± 5 °C (73.4 °F ± 9 °F) for 60 to 90 min. Immediately following the cooling period, remove the metal strips from the jars by use of a forceps, removing loose adhering sediment by agitation of the metal strip assembly in the fluid in the jar. Examine test strips and test jars for adhering crystalline deposit, disassemble the metal strips, removing adhering fluid by flushing with water, and clean individual strips by wiping with a cloth wetted with isopropanol or ethanol. Examine the strips for evidence of corrosion and pitting. Place strips in a desiccator containing a desiccant maintained at 23 °C ± 5 °C (73.4 °F ± 9 °F) for at least 1 h. Weigh each strip to the nearest 0.1 mg.Determine the difference in weight of each metal strip and divide the difference by the total surface area of the metal strip measured in square centimeters. Average the measured quantities of the duplicates. In the event of a marginal pass on inspection, or of a failure in only one of the duplicates, another set of duplicate test samples shall be run. Both repeat samples must meet all the requirements of 4.6.Immediately following the cooling period, remove the rubber cups from the jars by use of a forceps, removing loose adhering sediment by agitation of the cup in the fluid in the jar.Rinse the rubber specimens in isopropanol or ethanol and air dry cups. Examine the rubber specimens for evidence of sloughing, blisters, and other forms of disintegration.Within 15 min after removal from the fluid, weigh each specimen in air (m3), again to the nearest milligram, then reweigh immersed in room temperature distilled water (m4) to determine the volume change after hot fluid immersion.-8-标准分享网 免费下载。

PACKAGING INFORMATIONOrderable DeviceStatus (1)Package Type Package Drawing Pins Package Qty Eco Plan (2)Lead/Ball FinishMSL Peak Temp (3)84128012A ACTIVE LCCC FK 201TBD POST-PLATE N /A for Pkg Type 8412801EA ACTIVE CDIP J 161TBD A42SNPB N /A for Pkg Type SN54HC151J ACTIVE CDIP J 161TBD A42SNPB N /A for Pkg Type SN74HC151D ACTIVE SOIC D 1640Green (RoHS &no Sb/Br)CU NIPDAU Level-1-260C-UNLIM SN74HC151DE4ACTIVE SOIC D 1640Green (RoHS &no Sb/Br)CU NIPDAU Level-1-260C-UNLIM SN74HC151DG4ACTIVE SOIC D 1640Green (RoHS &no Sb/Br)CU NIPDAU Level-1-260C-UNLIM SN74HC151DR ACTIVE SOIC D 162500Green (RoHS &no Sb/Br)CU NIPDAU Level-1-260C-UNLIM SN74HC151DRE4ACTIVE SOIC D 162500Green (RoHS &no Sb/Br)CU NIPDAU Level-1-260C-UNLIM SN74HC151DRG4ACTIVE SOIC D 162500Green (RoHS &no Sb/Br)CU NIPDAU Level-1-260C-UNLIM SN74HC151DT ACTIVE SOIC D 16250Green (RoHS &no Sb/Br)CU NIPDAU Level-1-260C-UNLIM SN74HC151DTE4ACTIVE SOIC D 16250Green (RoHS &no Sb/Br)CU NIPDAU Level-1-260C-UNLIM SN74HC151N ACTIVE PDIP N 1625Pb-Free (RoHS)CU NIPDAU N /A for Pkg Type SN74HC151NE4ACTIVE PDIP N 1625Pb-Free (RoHS)CU NIPDAU N /A for Pkg Type SN74HC151NSR ACTIVE SO NS 162000Green (RoHS &no Sb/Br)CU NIPDAU Level-1-260C-UNLIM SN74HC151NSRE4ACTIVE SO NS 162000Green (RoHS &no Sb/Br)CU NIPDAU Level-1-260C-UNLIM SN74HC151PW ACTIVE TSSOP PW 1690Green (RoHS &no Sb/Br)CU NIPDAU Level-1-260C-UNLIM SN74HC151PWE4ACTIVE TSSOP PW 1690Green (RoHS &no Sb/Br)CU NIPDAU Level-1-260C-UNLIM SN74HC151PWR ACTIVE TSSOP PW 162000Green (RoHS &no Sb/Br)CU NIPDAU Level-1-260C-UNLIM SN74HC151PWRE4ACTIVE TSSOP PW 162000Green (RoHS &no Sb/Br)CU NIPDAU Level-1-260C-UNLIM SN74HC151PWT ACTIVE TSSOP PW 16250Green (RoHS &no Sb/Br)CU NIPDAU Level-1-260C-UNLIM SN74HC151PWTE4ACTIVE TSSOP PW 16250Green (RoHS &no Sb/Br)CU NIPDAULevel-1-260C-UNLIMSNJ54HC151FK ACTIVE LCCC FK 201TBD POST-PLATE N /A for Pkg Type SNJ54HC151JACTIVECDIPJ161TBDA42SNPBN /A for Pkg Type(1)The marketing status values are defined as follows:ACTIVE:Product device recommended for new designs.LIFEBUY:TI has announced that the device will be discontinued,and a lifetime-buy period is in effect.NRND:Not recommended for new designs.Device is in production to support existing customers,but TI does not recommend using this part in a new design.PREVIEW:Device has been announced but is not in production.Samples may or may not be available.OBSOLETE:TI has discontinued the production of the device.6-Dec-2006(2)Eco Plan -The planned eco-friendly classification:Pb-Free (RoHS),Pb-Free (RoHS Exempt),or Green (RoHS &no Sb/Br)-please check /productcontent for the latest availability information and additional product content details.TBD:The Pb-Free/Green conversion plan has not been defined.Pb-Free (RoHS):TI's terms "Lead-Free"or "Pb-Free"mean semiconductor products that are compatible with the current RoHS requirements for all 6substances,including the requirement that lead not exceed 0.1%by weight in homogeneous materials.Where designed to be soldered at high temperatures,TI Pb-Free products are suitable for use in specified lead-free processes.Pb-Free (RoHS Exempt):This component has a RoHS exemption for either 1)lead-based flip-chip solder bumps used between the die and package,or 2)lead-based die adhesive used between the die and leadframe.The component is otherwise considered Pb-Free (RoHS compatible)as defined above.Green (RoHS &no Sb/Br):TI defines "Green"to mean Pb-Free (RoHS compatible),and free of Bromine (Br)and Antimony (Sb)based flame retardants (Br or Sb do not exceed 0.1%by weight in homogeneous material)(3)MSL,Peak Temp.--The Moisture Sensitivity Level rating according to the JEDEC industry standard classifications,and peak solder temperature.Important Information and Disclaimer:The information provided on this page represents TI's knowledge and belief as of the date that it is provided.TI bases its knowledge and belief on information provided by third parties,and makes no representation or warranty as to the accuracy of such information.Efforts are underway to better integrate information from third parties.TI has taken and continues to take reasonable steps to provide representative and accurate information but may not have conducted destructive testing or chemical analysis on incoming materials and chemicals.TI and TI suppliers consider certain information to be proprietary,and thus CAS numbers and other limited information may not be available for release.In no event shall TI's liability arising out of such information exceed the total purchase price of the TI part(s)at issue in this document sold by TI to Customer on an annualbasis.6-Dec-2006IMPORTANT NOTICETexas Instruments Incorporated and its subsidiaries (TI) reserve the right to make corrections, modifications, enhancements, improvements, and other changes to its products and services at any time and to discontinue any product or service without notice. Customers should obtain the latest relevant information before placing orders and should verify that such information is current and complete. All products are sold subject to TI’s terms and conditions of sale supplied at the time of order acknowledgment.TI warrants performance of its hardware products to the specifications applicable at the time of sale in accordance with TI’s standard warranty. T esting and other quality control techniques are used to the extent TI deems necessary to support this warranty. Except where mandated by government requirements, testing of all parameters of each product is not necessarily performed.TI assumes no liability for applications assistance or customer product design. Customers are responsible for their products and applications using TI components. T o minimize the risks associated with customer products and applications, customers should provide adequate design and operating safeguards.TI does not warrant or represent that any license, either express or implied, is granted under any TI patent right, copyright, mask work right, or other TI intellectual property right relating to any combination, machine, or process in which TI products or services are used. Information published by TI regarding third-party products or services does not constitute a license from TI to use such products or services or a warranty or endorsement thereof. Use of such information may require a license from a third party under the patents or other intellectual property of the third party, or a license from TI under the patents or other intellectual property of TI.Reproduction of information in TI data books or data sheets is permissible only if reproduction is without alteration and is accompanied by all associated warranties, conditions, limitations, and notices. Reproduction of this information with alteration is an unfair and deceptive business practice. TI is not responsible or liable for such altered documentation.Resale of TI products or services with statements different from or beyond the parameters stated by TI for that product or service voids all express and any implied warranties for the associated TI product or service and is an unfair and deceptive business practice. TI is not responsible or liable for any such statements. Following are URLs where you can obtain information on other Texas Instruments products and application solutions:Products ApplicationsAmplifiers Audio /audioData Converters Automotive /automotiveDSP Broadband /broadbandInterface Digital Control /digitalcontrolLogic Military /militaryPower Mgmt Optical Networking /opticalnetwork Microcontrollers Security /securityLow Power Wireless /lpw Telephony /telephonyVideo & Imaging /videoWireless /wirelessMailing Address:Texas InstrumentsPost Office Box 655303 Dallas, Texas 75265Copyright 2006, Texas Instruments Incorporated。

AGFA 5300 简略错误代码表供片盒模块MOD 01HC201000原因1：XS1没有连接到输入模块解决1：连接XS1到输入模块原因2：XS7没有连接到输入模块解决2：连接XS7到输入模块这个错误在显示器上显示为“E201000: XS1 not connected”注意：错码E201000 是通过在连接器XS1 电缆回路中检测到的，信号是通过电缆回路中的某一针没有被送到VILIS CPU板上，打印机假设，电缆是没有连接的。

HC201001原因：错误胶片格式解决：使用指定的胶片格式这个错误在显示器上显示为“W201001: Wrong film format specified”注意：打印机始终只能使用指定的格式胶片。

该错误代码告诉操作者，打印机使用不同规格的胶片与其指定使用规格相比较，胶片必须是打印机可使用的胶片规格。

HC201003原因1：XS1没有连接到输入模块解决1：连接XS1到输入模块原因2：XS7没有连接到输入模块解决2：连接XS7到输入模块原因3：供片盒的E-Label没有连接解决3：连接供片盒的E-Label这个错误在显示器上显示为“W201003: Elabel failure on input tray”注意：E-Label包含周围模块的信息，连续的数字或调节参数，损坏或开路的E-Label 会出现下列故障：·在没有备份的内置CF卡而内置CF卡损坏的情况下，在更换新的内置CF卡时周围模块的信息将会不能被读取，最坏的情况是打印机不能使用。

·纠正中心不能获得周围模块参数。

·在E-Label损坏后打印机是可以正常使用的。

HC201004原因：供片盒Inputtray over ruled (dmax 2.0)解决：替换胶片pack注意：供片盒模块没有读到有效的胶片包HC201005原因：供片盒故障解决：替换胶片pack这个错误在显示器上显示为“E201005: Upper Tray Disabled”HC201006原因：XS7没有连接到输入模块解决：连接XS7到输入模块这个错误在显示器上显示为“E201006: XS7 not connected”注意：错码E201006 是通过在连接器XS7 电缆回路中检测到的，信号是通过电缆回路中的某一针没有被送到VILIS CPU板上，打印机假设，电缆是没有连接的。

SURFACEVEHICLERECOMMENDED PRACTICESAE 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.Copyright © 2004 SAE InternationalAll rights reserved. No part of this publication may be reproduced, stored in a retrieval system or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior written permission of SAE.TO PLACE A DOCUMENT ORDER: Tel: 877-606-7323 (inside USA and Canada)Tel: 724-776-4970 (outside USA)SAE J2534-1 Revised DEC2004TABLE OF CONTENTS 1. Scope (5)2. References (5)2.1 Applicable Documents (5)2.1.1 SAE Publications (5)2.1.2 ISO Documents (6)3. Definitions (6)4. Acronyms (6)5. Pass-Thru C oncept (7)6. Pass-Thru System Requirements (8)6.1 P C Requirements (8)6.2 Software Requirements and Assumptions (8)6.3 Connection to PC (9)6.4 Connection to Vehicle............................................................................................................9 6.5 C ommunication Protocols (9)6.5.1 ISO 9141................................................................................................................................9 6.5.2 ISO 14230-4 (KWP2000).. (10)6.5.3 SAE J1850 41.6 kbps PWM (Pulse Width Modulation) (10)6.5.4 SAE J1850 10.4 kbps VPW (Variable Pulse Width) (10)6.5.5 C AN (11)6.5.6 ISO 15765-4 (CAN) (11)6.5.7 SAE J2610 DaimlerChrysler SCI (11)6.6 Simultaneous Communication on Multiple Protocols (11)6.7 Programmable Power Supply (12)6.8 Pin Usage (13)6.9 Data Buffering (14)6.10 Error Recovery (14)6.10.1 Device Not Connected (14)6.10.2 Bus Errors (14)7. Win32 Application Programming Interface (15)7.1 API Functions – Overview (15)7.2 API Functions - Detailed Information (15)7.2.1 PassThruOpen (15)7.2.1.1 C /C ++ Prototype (15)7.2.1.2 Parameters (16)7.2.1.3 Return Values (16)7.2.2 PassThru C lose (16)7.2.2.1 C /C ++ Prototype (16)7.2.2.2 Parameters (16)7.2.2.3 Return Values (17)7.2.3 PassThru C onnect (17)7.2.3.1 C /C ++ Prototype (17)7.2.3.2 Parameters (17)7.2.3.3 Flag Values (18)7.2.3.4 Protocal ID Values (19)SAE J2534-1 Revised DEC20047.2.3.5 Return Values (20)7.2.4 PassThruDisconnect............................................................................................................20 7.2.4.1 C /C ++ Prototype (20)7.2.4.2 Parameters (21)7.2.4.3 Return Values ......................................................................................................................21 7.2.5 PassThruReadMsgs. (21)7.2.5.1 C /C ++ Prototype (22)7.2.5.2 Parameters...........................................................................................................................22 7.2.5.3 Return Values . (23)7.2.6 PassThruWriteMsgs (23)7.2.6.1 C /C ++ Prototype ..................................................................................................................24 7.2.6.2 Parameters (24)7.2.6.3 Return Values (25)7.2.7 PassThruStartPeriodicMsg..................................................................................................26 7.2.7.1 C /C ++ Prototype (26)7.2.7.2 Parameters (26)7.2.7.3 Return Values ......................................................................................................................27 7.2.8 PassThruStopPeriodicMsg .. (27)7.2.8.1 C /C ++ Prototype (28)7.2.8.2 Parameters...........................................................................................................................28 7.2.8.3 Return Values . (28)7.2.9 PassThruStartMsgFilter.......................................................................................................28 7.2.9.1 C /C ++ Prototype (31)7.2.9.2 Parameters (31)7.2.9.3 Filter Types ..........................................................................................................................32 7.2.9.4 Return Values . (33)7.2.10 PassThruStopMsgFIlter (33)7.2.10.1 C /C ++ Prototype ..................................................................................................................33 7.2.10.2 Parameters (34)7.2.10.3 Return Values (34)7.2.11 PassThruSetProgrammingVoltage (34)7.2.11.1 C /C ++ Prototype (34)7.2.11.2 Parameters (35)7.2.11.3 Voltage Values (35)7.2.11.4 Return Values (35)7.2.12 PassThruReadVersion (36)7.2.12.1 C /C ++ Prototype (36)7.2.12.2 Parameters (36)7.2.12.3 Return Values (37)7.2.13 PassThruGetLastError (37)7.2.13.1 C /C ++ Prototype (37)7.2.13.2 Parameters (37)7.2.13.3 Return Values (37)7.2.14 PassThruIoctl (38)7.2.14.1 C /C ++ Prototype (38)7.2.14.2 Parameters (38)7.2.14.3 Ioctl ID Values (39)7.2.14.4 Return Values (39)7.3 IO C TL Section (40)7.3.1 GET_C ONFIG (41)7.3.2 SET_C ONFIG (42)SAE J2534-1 Revised DEC20047.3.3 READ_VBATT (46)7.3.4 READ_PROG_VOLTAGE....................................................................................................46 7.3.5 FIVE_BAUD_INIT . (47)7.3.6 FAST_INIT (47)7.3.7 C LEAR_TX_BUFFER (48)7.3.8 C LEAR_RX_BUFFER (48)7.3.9 C LEAR_PERIODI C _MSGS (49)7.3.10 C LEAR_MSG_FILTERS (49)7.3.11 C LEAR_FUN C T_MSG_LOOKUP_TABLE (49)7.3.12 ADD_TO_FUN C T_MSG_LOOKUP_TABLE (50)7.3.13 DELETE_FROM_FUN C T_MSG_LOOKUP_TABLE (50)8. Message Structure (51)8.1 C /C ++ Definition (51)8.2 Elements (51)8.3 Message Data Formats (52)8.4 Format Checks for Messages Passed to the API (53)8.5 Conventions for Returning Messages from the API (53)8.6 Conventions for Returning Indications from the API (53)8.7 Message Flag and Status Definitions..................................................................................54 8.7.1 RxStatus. (54)8.7.2 RxStatus Bits for Messaging Status and Error Indication....................................................55 8.7.3 TxFlags.................................................................................................................................56 9. DLL Installation and Registry...............................................................................................57 9.1 Naming of Files....................................................................................................................57 9.2 Win32 Registy. (57)9.2.1 User Application Interaction with the Registry (59)9.2.2 Attaching to the DLL from an application (60)9.2.2.1 Export Library Definition File (61)10. Return Value Error Codes (61)11. Notes (63)11.1 Marginal Indicia (63)Appendix A General ISO 15765-2 Flow Control Example (64)A.1 Flow Control Overview (64)A.1.1 Examples Overview (65)A.2 Transmitting a Segmented Message (66)A.2.1 C onversation Setup (66)A.2.2 Data Transmission (67)A.2.3 Verification (68)A.3 Transmitting an Unsegmented Message (69)A.3.1 Data Transmission (70)A.3.2 Verification (70)A.4 Receiving a Segmented Message (70)A.4.1 C onversation Setup (70)A.4.2 Reception Notification (70)A.4.3 Data Reception (71)A.5 Receiving and Unsegmented Messages (72)1.ScopeThis SAE Recommended Practice provides the framework to allow reprogramming software applications from all vehicle manufacturers the flexibility to work with multiple vehicle data link interface tools from multiple tool suppliers. This system enables each vehicle manufacturer to control the programming sequence for electronic control units (EC Us) in their vehicles, but allows a single set of programming hardware and vehicle interface to be used to program modules for all vehicle manufacturers.This document does not limit the hardware possibilities for the connection between the PC used for the software application and the tool (e.g., RS-232, RS-485, USB, Ethernet…). Tool suppliers are free to choose the hardware interface appropriate for their tool. The goal of this document is to ensure that reprogramming software from any vehicle manufacturer is compatible with hardware supplied by any tool manufacturer.U.S. Environmental Protection Agency (EPA) and the C alifornia Air Resources Board (ARB) "OBD service information" regulations include requirements for reprogramming emission-related control modules in vehicles for all manufacturers by the aftermarket repair industry. This document is intended to conform to those regulations for 2004 and later model year vehicles. For some vehicles, this interface can also be used to reprogram emission-related control modules in vehicles prior to the 2004 model year, and for non-emission related control modules. For other vehicles, this usage may require additional manufacturer specific capabilities to be added to a fully compliant interface. A second part to this document, SAE J2534-2, is planned to include expanded capabilities that tool suppliers can optionally include in an interface to allow programming of these additional non-mandated vehicle applications. In addition to reprogramming capability, this interface is planned for use in OBD compliance testing as defined in SAE J1699-3. SAE J2534-1 includes some capabilities that are not required for Pass-Thru Programming, but which enable use of this interface for those other purposes without placing a significant burden on the interface manufacturers.Additional requirements for future model years may require revision of this document, most notably the inclusion of SAE J1939 for some heavy-duty vehicles. This document will be reviewed for possible revision after those regulations are finalized and requirements are better understood. Possible revisions include SAE J1939 specific software and an alternate vehicle connector, but the basic hardware of an SAE J2534 interface device is expected to remain unchanged.2.References2.1Applicable PublicationsThe following publications form a part of this specification to the extent specified herein. Unless otherwise indicated, the latest version of SAE publications shall apply.2.1.1SAE P UBLICATIONSAvailable from SAE, 400 Commonwealth Drive, Warrendale, PA 15096-0001.SAE J1850—Class B Data Communications Network InterfaceSAE J1939—Truck and Bus Control and Communications Network (Multiple Parts Apply)SAE J1962—Diagnostic ConnectorSAE J2610—DaimlerChrysler Information Report for Serial Data Communication Interface (SCI)2.1.2 ISO D OCUMENTSAvailable from ANSI, 25 west 43rd Street, New York, NY 10036-8002.ISO 7637-1:1990—Road vehicles—Electrical disturbance by conduction and coupling—Part 1:Passenger cars and light commercial vehicles with nominal 12 V supply voltageISO 9141:1989—Road vehicles—Diagnostic systems—Requirements for interchange of digital informationISO 9141-2:1994—Road vehicles—Diagnostic systems—C ARB requirements for interchange of digitalinformationISO 11898:1993—Road vehicles—Interchange of digital information—Controller area network (CAN) forhigh speed communicationISO 14230-4:2000—Road vehicles—Diagnostic systems—Keyword protocol 2000—Part 4:Requirements for emission-related systemsISO/FDIS 15765-2—Road vehicles—Diagnostics on controller area networks (C AN)—Network layerservicesISO/FDIS 15765-4—Road vehicles—Diagnostics on controller area networks (C AN)—Requirements foremission-related systems3.Definitions 3.1 RegistryA mechanism within Win32 operating systems to handle hardware and software configuration information.4. AcronymsAPI Application Programming InterfaceASCII American Standard Code for Information InterchangeCAN Controller Area NetworkC R C C yclic Redundancy C heckDLL Dynamic Link LibraryECU Electronic Control UnitIFR In-Frame ResponseIOCTL Input / Output ControlKWP Keyword ProtocolOEM Original Equipment ManufacturerP C Personal C omputerPWM Pulse Width ModulationSCI Serial Communications InterfaceSCP Standard Corporate ProtocolUSB Universal Serial BusVPW Variable Pulse Width5.Pass-Thru ConceptProgramming application software supplied by the vehicle manufacturer will run on a commonly available generic PC. This application must have complete knowledge of the programming requirements for the control module to be programmed and will control the programming event. This includes the user interface, selection criteria for downloadable software and calibration files, the actual software and calibration data to be downloaded, the security mechanism to control access to the programming capability, and the actual programming steps and sequence required to program each individual control module in the vehicle. If additional procedures must be followed after the reprogramming event, such as clearing Diagnostic Trouble C odes (DTC), writing part numbers or variant coding information to the control module, or running additional setup procedures, the vehicle manufacturer must either include this in the PC application or include the necessary steps in the service information that references reprogramming.This document defines the following two interfaces for the SAE J2534 pass-thru device:a. Application program interface (API) between the programming application running on a PC and asoftware device driver for the pass-thru deviceb. Hardware interface between the pass-thru device and the vehicleThe manufacturer of an SAE J2534 pass-thru device shall supply connections to both the PC and the vehicle. In addition to the hardware, the interface manufacturer shall supply device driver software, and a Windows installation and setup application that will install the manufacturer's SAE J2534 DLL and other required files, and also update the Windows Registry. The interface between the PC and the pass-thru device can be any technology chosen by the tool manufacturer, including RS-232, RS-485, USB, Ethernet, or any other current or future technology, including wireless technologies.All programming applications shall utilize the common SAE J2534 API as the interface to the pass-thru device driver. The API contains a set of routines that may be used by the programming application to control the pass-thru device, and to control the communications between the pass-thru device and the vehicle. The pass-thru device will not interpret the message content, allowing any message strategy and message structure to be used that is understood by both the programming application and the ECU being programmed. Also, because the message will not be interpreted, the contents of the message cannot be used to control the operation of the interface. For example, if a message is sent to the ECU to go to high speed, a specific instruction must also be sent to the interface to go to high speed.The OEM programming application does not need to know the hardware connected to the PC, which gives the tool manufacturers the flexibility to use any commonly available interface to the PC. The pass-thru device does not need any knowledge of the vehicle or control module being programmed. This will allow all programming applications to work with all pass-thru devices to enable programming of all control modules for all vehicle manufacturers.The interface will not handle the tester present messages automatically. The OEM application is responsible to handle tester present messages.6.3Connection to PCThe interface between the PC and the pass-thru device shall be determined by the manufacturer of the pass-thru device. This can be RS-232, USB, Ethernet, IEEE1394, Bluetooth or any other connection that allows the pass-thru device to meet all other requirements of this document, including timing requirements. The tool manufacturer is also required to include the device driver that supports this connection so that the actual interface used is transparent to both the PC programming application and the vehicle.6.4Connection to VehicleThe interface between the pass-thru device and the vehicle shall be an SAE J1962 connector for serial data communications. The maximum cable length between the pass-thru device and the vehicle is five (5) meters. The interface shall include an insulated banana jack that accepts a standard 0.175" diameter banana plug as the auxiliary pin for connection of programming voltage to a vehicle specific connector on the vehicle.If powered from the vehicle, the interface shall:a. operate normally within a vehicle battery voltage range of 8.0 to 18.0 volts D.C.,b. survive a vehicle battery voltage of up to 24.0 volts D.C. for at least 10 minutes,c. survive, without damage to the interface, a reverse vehicle battery voltage of up to 24.0 volts D.C. forat least 10 minutes.6.5Communication ProtocolsThe following communication protocols shall be supported:6.5.1ISO9141The following specifications clarify and, if in conflict with ISO 9141, override any related specifications in ISO 9141:a. The maximum sink current to be supported by the interface is 100 mA.b. The range for all tests performed relative to ISO 7637-1 is –1.0 to +40.0 V.c. The default bus idle period before the interface shall transmit an address, shall be 300 ms.d. Support following baud rate with ±0.5% tolerance: 10400.e. Support following baud rate with ±1% tolerance: 10000.f. Support following baud rates with ±2% tolerance: 4800, 9600, 9615, 9800, 10870, 11905, 12500,13158, 13889, 14706, 15625, and 19200.g. Support other baud rates if the interface is capable of supporting the requested value within ±2%.h. The baud rate shall be set by the application, not determined by the SAE J2534 interface. Theinterface is not required to support baud rate detection based on the synchronization byte.i. Support odd and even parity in addition to the default of no parity, with seven or eight data bits.Always one start bit and one stop bit.j. Support for timer values that are less than or greater than those specified in ISO 9141 (see Figure 30 in Section 7.3.2).k. Support ability to disable automatic ISO 9141-2 / ISO 14230 checksum verification by the interface to allow vehicle manufacturer specific error detection.l. If the ISO 9141 checksum is verified by the interface, and the checksum is incorrect, the message will be discarded.m. Support both ISO 9141 5-baud initialization and ISO 14230 fast initialization.n. Interface shall not adjust timer parameters based on keyword values.6.5.2ISO14230-4(KWP2000)The ISO 14230 protocol has the same specifications as the ISO 9141 protocol as outlined in the previous section. In addition, the following specifications clarify and, if in conflict with ISO 14230, override any related specifications in ISO 14230:a. The pass-thru interface will not automatically handle tester present messages. The application needsto handle tester present messages when required.b. The pass-thru interface will not perform any special handling for the $78 response code. Anymessage received with a $78 response code will be passed from the interface to the application. The application is required to handle any special timing requirements based on receipt of this response code, including stopping any periodic messages.6.5.3SAE J185041.6 KBPS PWM(P ULSE W IDTH M ODULATION)The following additional features of SAE J1850 must be supported by the pass-thru device:a. Capable of 41.6 kbps and high speed mode of 83.3 kbps.b. Recommend Ford approved SAE J1850PWM (SCP) physical layer6.5.4SAE J185010.4 KBPS VPW(V ARIABLE P ULSE W IDTH)The following additional features of SAE J1850 must be supported by the pass-thru device:a. Capable of 10.4 kbps and high speed mode of 41.6 kbpsb. 4128 byte block transferc. Return to normal speed after a break indication6.5.5CANThe following features of ISO 11898 (CAN) must be supported by the pass-thru device:a. 125, 250, and 500 kbpsb. 11 and 29 bit identifiersc. Support for 80% ± 2% and 68.5% ± 2% bit sample pointd. Allow raw C AN messages. This protocol can be used to handle any custom C AN messagingprotocol, including custom flow control mechanisms.6.5.6ISO15765-4(CAN)The following features of ISO 15765-4 must be supported by the pass-thru device:a. 125, 250, and 500 kbpsb. 11 and 29 bit identifiersc. Support for 80% ± 2% bit sample pointd. To maintain acceptable programming times, the transport layer flow control function, as defined inISO 15765-2, must be incorporated in the pass-thru device (see Appendix A). If the application does not use the ISO 15765-2 transport layer flow control functionality, the CAN protocol will allow for any custom transport layer.e. Receive a multi-frame message with an ISO15765_BS of 0 and an ISO15765_STMIN of 0, asdefined in ISO 15765-2.f. No single frame or multi-frame messages can be received without matching a flow control filter. Nomulti-frame messages can be transmitted without matching a flow control filter.g. Periodic messages will not be suspended during transmission or reception of a multi-framesegmented message.6.5.7SAE J2610D AIMLER C HRYSLER SCIReference the SAE J2610 Information Report for a description of the SCI protocol.When in the half-duplex mode (when SCI_MODE of TxFlags is set to {1} Half-Duplex), every data byte sent is expected to be "echoed" by the controller. The next data byte shall not be sent until the echo byte has been received and verified. If the echoed byte received doesn't match the transmitted byte, or if after a period of T1 no response was received, the transmission will be terminated. Matching echoed bytes will not be placed in the receive message queue.6.6Simultaneous Communication On Multiple ProtocolsThe pass-thru device must be capable of supporting simultaneous communication on multiple protocols during a single programming event. Figure 2 indicates which combinations of protocols shall be supported. If SC I (SAE J2610) communication is not required during the programming event, the interface shall be capable of supporting one of the protocols from data link set 1, data link set 2, and data link set 3. If SC I (SAE J2610) communication is required during the programming event, the interface shall be capable of supporting one of the SCI protocols and one protocol from data link set 1.6.9Data BufferingThe interface/API shall be capable of receiving 8 simultaneous messages. For ISO 15765 these can be multi-frame messages. The interface/API shall be capable of buffering a maximum length (4128 byte) transmit message and a maximum length (4128 byte) receive message.6.10Error Recovery6.10.1D EVICE N OT C ONNECTEDIf the DLL returns ERR_DEVICE_NOT_CONNECTED from any function, that error shall continue to be returned by all functions, even if the device is reconnected. An application can recover from this error condition by closing the device (with PassThruC lose) and re-opening the device (with PassThruOpen, getting a new device ID).6.10.2B US E RRORSAll devices shall handle bus errors in a consistent manner. There are two error strategies: Retry and Drop.The Retry strategy will keep trying to send a packet until successful or stopped by the application. If loopback is on and the message is successfully sent after some number of retries, only one copy of the message shall be placed in the receive queue. Even if the hardware does not support retries, the firmware/software must retry the transmission. If the error condition persists, a blocking write will wait the specified timeout and return ERR_TIMEOUT. The DLL must return the number of successfully transmitted messages in pNumMsgs. The DLL shall not count the message being retried in pNumMsgs. After returning from the function, the device does not stop the retries. The only functions that will stop the retries are PassThruDisconnect (on that protocol), PassThruC lose, or PassThruIoctl (with an IoctllD of CLEAR_TX_BUFFER).Devices shall use the Retry strategy in the following scenarios:•All CAN errors, such as bus off, lack of acknowledgement, loss of arbitration, and no connection (lack of terminating resistor)•SAE J1850PWM or SAE J1850VPW bus fault (bus stuck passive) or loss of arbitration (bus stuck active)The Drop strategy will delete a message from the queue. The message can be dropped immediately on noticing an error or at the end of the transmission. PassThruWriteMsg shall treat dropped messages the same as successfully transmitted messages. However, if loopback is on, the message shall not be placed in the receive queue.Devices shall use the Drop strategy in the following scenarios:•If characters are echoed improperly in SCI•Corrupted ISO 9141 or ISO 14230 transmission•SAE J1850PWM lack of acknowledgement (Exception: The device must try sending the message 3 times before dropping)7.2.5.1 C / C++ Prototypeextern “C” long WINAPI PassThruReadMsgs(unsigned long ChannelID,*pMsg,PASSTHRU_MSGunsigned long *pNumMsgs,unsigned long Timeout)7.2.5.2ParametersChannelID The channel ID assigned by the PassThruConnect function.pMsg Pointer to message structure(s).pNumMsgs Pointer to location where number of messages to read is specified. On return from the function this location will contain the actual number of messages read.Timeout Read timeout (in milliseconds). If a value of 0 is specified the function retrieves up to pNumMsgs messages and returns immediately. Otherwise, the API will not return untilthe Timeout has expired, an error has occurred, or the desired number of messageshave been read. If the number of messages requested have been read, the functionshall not return ERR_TIMEOUT, even if the timeout value is zero.When using the ISO 15765-4 protocol, only SingleFrame messages can be transmitted without a matching flow control filter. Also, P I bytes are transparently added by the API. See PassThruStartMsgFilter and Appendix A for a discussion of flow control filters.7.2.6.1 C / C++ Prototypeextern “C” long WINAPI PassThruWriteMsgs(u nsigned long ChannelID,*pMsg,PASSTHRU_MSGunsigned long *pNumMsgs,unsigned long Timeout)7.2.6.2ParametersChannelID The channel ID assigned by the PassThruConnect function.pMsg Pointer to message structure(s).pNumMsgs Pointer to the location where number of messages to write is specified. On return will contain the actual number of messages that were transmitted (when Timeout is non-zero) or placed in the transmit queue (when Timeout is zero).Timeout Write timeout (in milliseconds). When a value of 0 is specified, the function queues as many of the specified messages as possible and returns immediately. When a valuegreater than 0 is specified, the function will block until the Timeout has expired, an errorhas occurred, or the desired number of messages have been transmitted on the vehiclenetwork. Even if the device can buffer only one packet at a time, this function shall beable to send an arbitrary number of packets if a Timeout value is supplied. Since thefunction returns early if all the messages have been sent, there is normally no penalty forhaving a large timeout (several seconds). If the number of messages requested havebeen written, the function shall not return ERR_TIMEOUT, even if the timeout value iszero.W hen an ERR_TIMEOUT is returned, only the number of messages that were sent onthe vehicle network is known. The number of messages queued is unknown. Applicationwriters should avoid this ambiguity by using a Timeout value large enough to work onslow devices and networks with arbitration delays.。

Applicability This Technical Note is intended to be used as an instruction guide onhow to use the on-line application that allows Software FeatureEnabling (SFE) codes to be generated and regenerated for repair forthe following products:•TB7000 Base Stations•TM8000 Mobiles•TM9000 APCO Digital Mobiles•TP9000 APCO Digital Portables•TB8000 Base Stations•TB9000.APCO Digital Base StationsThe Technical Note also details how to enable and disable features inthe products and aspects of board swapping.1.Background on SFE.What is an SFE? A S oftware F eature E nabling key code (formally known as a FeatureLicense Code (FLC)) that, once programmed into the product, turns on afeature that was not previously available to the user. This code is apurchasable item.Who can get an SFE?Currently only the Tait CSO’s can order SFE codes. In future, once the appropriate systems and IT applications are in place, customers may be able to order upgrades over the internet.How do I orderand SFE for myproduct?Please refer to TMS document TE0738 for ordering detailsCan I get access to the SFE code generator?Please refer to TMS document TE0738 for detailsTECHNICAL NOTE TN-822cHow to Use the SoftwareFeature Enabler Application28thSeptember 2005ing the SFE Generation ApplicationUser Instructions To obtain a SFE code, please follow the steps below:1)Go to the following web address./T8000_SFE/MainMenu_CSO.asp2)Please note that this is a Taitweb address. Unless you haveaccess to the Taitweb website the SFE website will not beshown.3)You will be prompted to enter in your generic TaitWeb logininformation before the title screen will be displayed.4)You will then be presented with the screen pictured below:5)Left click with your mouse onto the link titled “Purchase LicenseKeys”.6)You will now be presented with a screen asking you to enter in aserial number range or import a *.txt file (see picture below).Please select one of the options.Instructions (Cont)7)The next screen shown is the one pictured below. Please confirmthat the serial number range you have entered is correct for your needs. Once confirmed, please click on “Step 3: Select Features”.8)You will now be presented with a screen indicating whichfeatures can be enabled for the product type (only TM8000 and TB8000 series products allowed currently, APCO product in future).9)Using the mouse, click the “~” symbol. This will change from the“~” symbol to the words “Generate Key”. If the feature was already enabled on a particular serial number, the “Status” field will display “enabled”. If you click on the “~” key for a feature that was already enabled, the “~” will change to display the words “Regenerate Key”.10)Once all desired selections have been made, click on “Step 4:Generate Keys”.Instructions (cont)11)The next screen to be displayed is pictured below. This screen willdetail (in this order):Serial Number; Feature Number, SFE Code; Status. The status will be listed as “new” or “regenerated”.12)You now have the option to either print the information or e-mailit to an address. To e-mail, you must enter in a valid e-mail address into the field provided. Then click on “Email Key Files”13)At this stage, the SFE key generation process is complete. If yourequire to generate more SFE keys, click on “Step 1: Select Serial Numbers” to start the process again.14)If you have completed generating the keys you require, exit theapplication.What happens if an SFE feature is disabled?The only way that an SFE feature can purposefully be disabled is in the programming application using the SFE tool. When a feature is disabled, a disable key is generated. This key will always be able to be read and displayed until the feature is enabled again.However, to enable the feature again, the disable key needs to be provided to the SFE Administrator for your region. This key is then entered into the SFE database in association with the serial number of the radio. This effectively completes the cycle of disabling the feature. The entering in of the disable key into the database not only sets the feature to ‘Disabled” in the database, but also increments the database which in turn allows a new SFE key to be generated for the radio.How to Program the Key into my TB8000Instructions are always attached to the e-mail message that is sent with the SFE key file:TB8000:1.Connect and log on to the base station.2.Save the license files (and any others that you received for otherfeature sets or other base stations) to the Programming application’s license file folder (select Tools > Options to see which folder the Service Kit uses).3.IMPORTANT: If you received a ZIP file containing multiple licensefiles, you MUST unzip the contents of the ZIP file and save the individual license files into the correct folder.4.Go into Standby mode, and then select Tools > Software FeatureEnabler.5.Click the feature set to select it.6.Click Find License File. This searches the license file folder for alicense file for the current base station and the selected feature set. If the7.Programming Application finds one, it displays the license key (inthe feature set’s row and in the Feature License Key boxes), and increments the Seq column by 1.8.Click Enable. This enables the feature set. The license keyappears in the feature set’s row and the Seq column is incremented by 19.The feature has now been enabled in the product..How to Program the Key into my TM8000TM8000:To enable an optional feature1.Read the radio. See Reading a radio for more information.2.Select the Tools > Optional Features menu command.3.Click on the feature set that you want to enable in the Featuresbox.4.Obtain and enter a license key. Either:•Enter the code directly into the Feature License Key boxes.•Click the Find License File button, and double click a *.key file.5Click the Enable button6Close the dialog.7Enable relevant programmable settings. For example, to enable Tait high-speed data, select the Modem Enabled check box.3.SFE Disabling Process.How to disable a feature?-Simply click the “Disable” button.-The programmer will be prompted to ensure this is the desired action. Press OK-The radio product will be re-programmed at this stage and the feature disabled.-The status will change from “Enabled” to “Disabled”What do I do with the disable key?-Upon disabling of a key, a new code is generated within the radio. This is the SFE disable key. This key needs to be provided to Technical Support at the CSO along with the chassis serial number of the product.-Reason: If the feature is required to be turned on again in the future, the same SFE key used previously to turn the feature on can not be used (The “sequence” (see ‘Seq’ in the screen shot above) has incremented).-By providing the disable key to the SFE administrator, the key number can be entered into the database which in turn resets the “Status Field” in the SFE application from “Enabled” to “Disabled”.-This means that next time the feature is required, an SFE key will be generated that will match the sequence the radio is up to for that particular feature.CSO’s need to be very much aware of this requirement to prevent any possible confusion in the future.What about Product Demos?By receiving the SFE disable key, the TEL or CSO logistical staff can now issue a credit to the customer if the feature was only being usedfor demonstration purposes.4.Product Board Swap ProcessWhy does the SFE database need to be updated when a Board Swap is performed?With products such as the TM8000 and TB8000 series, it is becoming more and more apparent that board swapping will soon become the most economical repair for a product.However, along with this comes a need to have better traceability of what board is actually inside the product. The SFE requirement compounds this as the SFE key is based on the internal serial number of each individual board, not the chassis serial number.When a board is swapped, the SFE keys (if features are enabled) will need to be re-generated for the new boards, as the old keys will not function on a new board.What will happen if the database is not updated?If a board swap repair has been made to a customers radio unit, the customer will not notice any problem until they come to purchase an SFE key.The customer will quote the chassis serial number of the product they have in order to get the key generated. For this example, the chassis serial number is 12345678.When the product was built from the factory, the internal serial number was 3654321.However, it has now had a board swap performed and now contains a board with an internal serial number of 3232323.When the SFE board swap application is asked to generate a new SFE key for the customer radio, the application will generate an SFE key for serial number 3654321 and not 3232323.The end result is the SFE will not work for the customers’ radio.To remedy the problem will require a manual database search that will take time and cause delays for the customer and potential damage to Taits’ reputation.What does a Sub-Assembly Serial Number look like?On the TB7000, TM8000 and TM9000 series, the subassembly serial number is a 7 digit number that begins with the number 3 (e.g. 3xxxxxx). The location of the label has changed several times since production began (e.g. Bottom side PCB, top of the PA can) The intention is to have sub-assembly labels in one location. This location is on the bottom side, on the digital can. Some assemblies are already labelled this way (TM8100). An example of the TM8000/TM9000 label is shown below.TP9000 series hand portables have the sub-assembly serial number located on a label on topside digital can (previously located on the Front End can). The 7 digit sub assembly number begins with the 4 (e.g. 4xxxxxx)TB8000/TB9000 have a 7 digit subassembly number that begins with the number 2 (e.g. 2xxxxxx). There are many sub assembly numbers on a complete TB8000 or TB9000 product, however, the one of importance with regards to the “Board Swap” process is the onelocated on the topside of the digital board PCB.The Procedure1)Select the “Board Swap” option from the home page of the SFEapplication.NOTE: Access to this option will be limited to key technical support /repair personnel.2) Enter in the Chassis serial number of the radio into the fieldprovided, and press ‘continue’.3) The user will then be presented with a screen listing the chassisserial number, the current internal serial number and the current SFEfeatures that are enabled on that product (if any are enabled). Alsopresented is a field for the user to enter in the internal serial numberof the ‘replacement’ board sub-assembly. Once this has been done,press ‘continue’.The Procedure (cont)4) The application will then prompt the user asking whether to proceed with the ‘board swap’.5) There are two events that can occur from this point on.5a – If the product had SFE keys previously generated for it, the SFE Board Swap application will recognise this and prompt the user as to whether new SFE keys need to be re-generated for the new internal serial number by providing a “Generate Keys”option. This is followed by another confirmation of action screen.Once the ‘OK’ button in pressed, the user will then be presented with a page listing the SFE features and associated new SFE keys generated for the product. The user has the option to enter in an email address to send the key files to.The Procedure (cont)Alternatively:5b – If the product did not have any SFE keys previously generated for it, the SFE Board Swap application will recognise this and the board swap process would be complete at this point.Can a board that has been repaired be reused?Yes. When a board is removed from the chassis it was in, this action is recorded in the serial number database that the SFE Board Swap application uses. Any board taken out of circulation because it is faulty goes back into the “Unallocated” list of internal serial numbers. Therefore, if this board is repaired in future, it can be put into another radio as part of a board swap repair.Are there any safe guards to prevent error?Yes. Firstly, access to the Board Swap feature will be restricted and only those who have had adequate training will be allowed access. Secondly, the serial number tables used in the application are interrogated on each request for change to ensure that there is no serial number reuse where it is not allowed.For example – if someone enters an incorrect internal serial number for a board swap, the application will display a message stating:“Can’t do Board Swap – New Serial number is already used”.At this point, both the chassis serial number and the internal serial number of the board subassembly needs to be checked for accuracy.Are there any charges involved?No. The SFE features regenerated for a repaired radio are free of charge, as the customer has already paid for these features. There are safe guards in the system to ensure the Board Swap feature is notabused.Compliance Issues NoneCSO Instruction Please make sure that all sales, technical and logistical staff are aware ofthe processes that are required to be followed for ordering, freebies andrepairs.Please take particular note of the requirements with regards tothe SFE disable key.5.Issuing AuthorityName and Position of Issuing Officer Barry CratesTechnical Support Team Leader – Terminal ProductConfidentiality Confidential – This message or document contains proprietaryinformation intended only for the person(s) or organisation(s) to whomit is addressed. All Recipients are legally obliged to not disclose Taittechnological or business information to any persons or organisationswithout the written permission of Tait.Distribution Level Tait OnlyDocument History Original Release Dec 2003BLCAdded TM8000 SFE programminginformation10 March 2004BLCAdded more graphics for the TM8000and TB8000 SFE key programmingprocess31 March 2004BLCAdded disable process information8 April 2004BLCAdded Board Swap processesinformation and inserted the TMSdocument numbers.1 November 2004BLCAdded information on where to find theXSN numbers on the PCB’s24th June 2005BLCAdded information about what to do about product demonstrations and the SFE disable key(on page 9)28th September 2005BLC。