SIST EN 15430-1:2008
(Main)Winter and road service area maintenance equipments - Data acquisition and transmission - Part 1: In vehicle data acquisition
Winter and road service area maintenance equipments - Data acquisition and transmission - Part 1: In vehicle data acquisition
This European Standard specifies a standardized protocol for downloading data from the equipment control box to an in vehicle board computer to ensure interchangeability between a vehicle and different equipments that the same vehicle can carry.
It specifies the interface connection as well as variables, records and reports which permit standardized protocol to cover applications with the greatest possible variety of equipments for performing winter maintenance and road service area maintenance.
Winterdienst- und Straßenbetriebsdienstausstattung - Datenerfassung und -übertragung - Teil 1: Datenerfassung im Fahrzeug
Dieses Europäische Norm legt ein genormtes Protokoll für das Übertragen von Betriebsdaten von der Anbau-Gerätesteuerung (Steuergerät) zu einem im Fahrzeug befindlichen Bord-Computer fest, um die Kompatibilität zwischen dem Fahrzeug und den verschiedenen Anbau-Geräten, die an diesem Fahrzeug betrieben werden können, sicherzustellen.
Diese Norm legt sowohl Schnittstellen (Anschlüsse) fest, wie auch Variablen, Datensätze und Meldungen, die es in dem genormten Protokoll ermöglichen eine größtmögliche Vielfalt bei Anwendungen von Anbau-Geräten beim Straßenbetriebs- und Winterdienst abzudecken.
Matériels de viabilité hivernale et d'entretien des dépendances routieres - Acquisition et transmission des données - Partie 1: Acquisition des données véhiculaires
Oprema za vzdrževalna dela zimske službe in službe za vzdrževanje cest - Zajem in prenos podatkov - 1. del: Zajem podatkov v vozilu
General Information
Relations
Standards Content (Sample)
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Winter and road service area maintenance equipments - Data acquisition and transmission - Part 1: In vehicle data acquisitionOprema za vzdrževalna dela zimske službe in službe za vzdrževanje cest - Zajem in prenos podatkov - 1. del: Zajem podatkov v voziluMatériels de viabilité hivernale et d'entretien des dépendances routieres - Acquisition et transmission des données - Partie 1: Acquisition des données véhiculairesWinterdienst- und Straßenbetriebsdienstausstattung - Datenerfassung und -übertragung - Teil 1: Datenerfassung im FahrzeugTa slovenski standard je istoveten z:EN 15430-1:2007SIST EN 15430-1:2008en,de43.16035.240.60ICS:SLOVENSKI
STANDARDSIST EN 15430-1:200801-marec-2008
EUROPEAN STANDARDNORME EUROPÉENNEEUROPÄISCHE NORMEN 15430-1December 2007ICS 43.160; 35.240.60 English VersionWinter and road service area maintenance equipments - Dataacquisition and transmission - Part 1: In vehicle data acquisitionMatériels de viabilité hivernale et d'entretien desdépendances routières - Acquisition et transmission desdonnées - Partie 1 : Acquisition des données véhiculairesWinterdienst- und Straßenbetriebsdienstausstattung -Datenerfassung und -übertragung - Teil 1: Datenerfassungim FahrzeugThis European Standard was approved by CEN on 21 October 2007.CEN members are bound to comply with the CEN/CENELEC Internal Regulations which stipulate the conditions for giving this EuropeanStandard the status of a national standard without any alteration. Up-to-date lists and bibliographical references concerning such nationalstandards may be obtained on application to the CEN Management Centre or to any CEN member.This European Standard exists in three official versions (English, French, German). A version in any other language made by translationunder the responsibility of a CEN member into its own language and notified to the CEN Management Centre has the same status as theofficial versions.CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Cyprus, Czech Republic, Denmark, Estonia, Finland,France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal,Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland and United Kingdom.EUROPEAN COMMITTEE FOR STANDARDIZATIONCOMITÉ EUROPÉEN DE NORMALISATIONEUROPÄISCHES KOMITEE FÜR NORMUNGManagement Centre: rue de Stassart, 36
B-1050 Brussels© 2007 CENAll rights of exploitation in any form and by any means reservedworldwide for CEN national Members.Ref. No. EN 15430-1:2007: E
EN 15430-1:2007 (E)
2 ContentsForeword.3 Introduction.4 1 Scope.6 2 Normative references.6 3 Terms and abbreviations.6 4 Communication between vehicle/equipment and board-computer.6 4.1 General.6 4.2 Communication through RS232.7 4.2.1 RS232 interface on vehicle/equipment “Data transmission handler”.7 4.2.2 RS232 interface on “Board-computer”.7 4.2.3 Communication protocol.8 5 Definitions of variables, records and report.12 5.1 General.12 5.2 Variable types.12 5.3 Recommended SLOTs for variable definitions.15 5.4 Definition of variables.18 5.4.1 General.18 5.4.2 General variables.18 5.4.3 General geographic position system variables.20 5.4.4 General vehicle and route variables.21 5.4.5 General road weather and road condition variables.21 5.4.6 Plough / Broom variables.22 5.4.7 Snow blower or cutter variables.23 5.4.8 Spreader / sprayer variables.23 5.4.9 Grass or branch cutting machine variables.26 5.4.10 Sweeper variables.27 5.4.11 Safety post cleaning machine variables.28 5.4.12 Boat plants cutter variables.29 5.5 Definition of records.29 5.5.1 General.29 5.5.2 Time synchronisation record (record code 0).30 5.5.3 Standard header record (record code 1).31 5.5.4 Standard footer record (record code 2).32 5.5.5 Trigger conditions for record code 3 and higher.32 5.5.6 Geographic position data record (record code 3).33 5.5.7 Vehicle and route data record (record code 4).34 5.5.8 Weather and road condition data record (record code 5).35 5.5.9 Snowplough / broom data record (record code 6 / 7).36 5.5.10 Spreader / sprayer data record (record code 8).37 5.5.11 Snow blower / cutter data record (record code 9).39 5.5.12 Grass / branch cutter data record (record code 10).40 5.5.13 Sweeper data record (record code 11).42 5.5.14 Safety post cleaning machine data record (record code 12).43 5.5.15 Boat plants cutter data record (record code 13).44 5.5.16 Free definable data record (record code 10000 and higher).44 5.6 Report definition.45 Bibliography.47
EN 15430-1:2007 (E) 3
Foreword This document (EN 15430-1:2007) has been prepared by CEN/TC 337/WG 3 "Interface between tools and vehicle", the secretariat of which is held by UNI-CUNA, under the direction of Technical Committee CEN/TC 337 "Winter maintenance and road service area maintenance equipment", the secretariat of which is held by AFNOR. This European Standard shall be given the status of a national standard, either by publication of an identical text or by endorsement, at the latest by June 2008, and conflicting national standards shall be withdrawn at the latest by June 2008. According to the CEN/CENELEC Internal Regulations, the national standards organizations of the following countries are bound to implement this European Standard : Austria, Belgium, Bulgaria, Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland and United Kingdom.
EN 15430-1:2007 (E)
4 Introduction This protocol is meant to be used for data acquisition in fleet management applications in the field of municipal vehicles. The purpose of the protocol is to define how data of a vehicle or equipment is generated, stored and transferred to a board-computer system in the vehicle and from the board-computer to the software application in the office (refer to Figure 1). On the equipment or vehicle the data is generated by a “Data generator”. This data is stored, if present, into a buffer-memory. The “Data transmission handler” will send the data present in the buffer-memory to the “Board-computer” or “Data Acquisition System”. The buffer-memory is there to ensure that data does not get lost in case there is no transmission possible. The size or type of the buffer is not defined in this proposal. If there is no buffer or the buffer is too small to store new data, data will get lost. To synchronise time-stamps of the vehicle/equipment with the Board-computer, a special record for time synchronisation is defined. In this part the data acquisition and communication from vehicle/equipment to the Board-computer is defined.
Figure 1 – Architecture
In general, the data is a semi-colon (“;”) separated ASCII text for separation of record codes and values of variables. CR+LF is used for separation of records (one record is one line of text).
EN 15430-1:2007 (E) 5 Examples of an on-board system configuration
Figure 2 – Diagram of possible connections
EN 15430-1:2007 (E)
6 1 Scope This European Standard specifies a standardized protocol for downloading data from the equipment control box to an in-vehicle board computer to ensure interchangeability between a vehicle and different equipments that the same vehicle can carry. It specifies the interface connection as well as variables, records and reports which permit standardized protocol to cover applications with the greatest possible variety of equipments for performing winter maintenance and road service area maintenance. 2 Normative references ISO 8859-1, Information technology - 8-bit single-byte coded graphic character sets - Part 1: Latin alphabet No. 1 NMEA 0183, Interface Standard TIA-232-F, Interface between data terminal equipment and data circuit-terminating equipment employing serial binary data interchange (RS232) SAE J1939/71, Recommended practice for serial control and communications vehicle network - Vehicle application layer 3 Terms and abbreviations ACK Acknowledge (ASCII control code 06h) ASCII American national Standard Code for Information Interchange Bps Bits per second CRC-16 Cyclic Redundancy Code with 16 bits CR Carriage Return (ASCII control code 0Dh) EOT End Of Transmission (ASCII control code 04h) h Number before h is in hexadecimal notation IEEE Institute of Electrical and Electronics Engineers LF Line Feed (ASCII control code 0Ah) NAK Negative acknowledge (ASCII control code 15h) SOH Start Of Header (ASCII control code 01h) TBD To Be Defined ↵ CR + LF (carriage return + line feed) 4 Communication between vehicle/equipment and board-computer 4.1 General The data exchange between vehicle/equipment “Data transmission handler” and the “Board-computer” must follow at least one of the communication standards described in the present document version or future release. Until
EN 15430-1:2007 (E) 7 now, only the RS232 standard (TIA-232-F) is defined as a communication standard so that means that at the present a compliant EN 15430
“Data transmission handler”
has to supply a RS232 interface , if in the future other standard interfaces will be defined
(e.g. CAN BUS, USB .) a compliant EN 15430 future “Data transmission handler” will have to supply at least one of the communication standard until that time is defined. 4.2 Communication through RS232 4.2.1 RS232 interface on vehicle/equipment “Data transmission handler” • Connector: SUB-D 9p female o Pin 2 = Transmit Data
o Pin 3 = Receive Data o Pin 5 = Signal Ground • Baud rate: 1 200 Bps.115 200 Bps, default 9 600 Bps. Rate can be programmable (optional) Remark: the baud rate must be sufficient for a worst case amount of data to be send with retries. • Data bits: 8 • Stop bits: 1 • Parity: No • Data format: according to ISO 8859-1 (ASCII) • Handshaking: by software with ACK, NAK ASCII control codes, refer to 4.2.3 • Transmission control by SOH and EOT ASCII control codes, refer to 4.2.3 • Data validity check: CRC-16/CCITT, refer to 4.2.3
4.2.2 RS232 interface on “Board-computer” • Connector: SUB-D 9p male o Pin 2 = Receive Data o Pin 3 = Transmit Data o Pin 5 = Signal Ground • Baud rate: 1 200 Bps.115 200 Bps, default 9 600 Bps. Rate must be programmable or automatically detected (autobaud) • Data bits: 8 • Stop bits: 1 • Parity: No • Data format: according to ISO 8859-1 (ASCII) • Handshaking: by software with ACK, NAK ASCII control codes, refer to 4.2.3
EN 15430-1:2007 (E)
8 • Transmission control by SOH and EOT ASCII control codes, refer to 4.2.3 • Data validity check: CRC-16/CCITT, refer to 4.2.3
4.2.3 Communication protocol Transmission of a record In this definition a message to be communicated consists of one record. Records are terminated by CR+LF (a record is one line of text). In general, a message is sent by the sender (e.g. the “Data transmission handler” of a spreader) and received by the receiver (e.g. the Board-computer). After power up, communication is always started by the vehicle/equipment “Data transmission handler” sending its first message (this is the time synchronisation record). Refer to Figure 4 for flow charts of the sender and receiver algorithms. The receiver will check the validity of a message by testing if the CRC-16 value corresponds to the data in the message received. If the data is valid, the receiver sends an ACK. The sender can now send a new message. If the data is invalid, the receiver sends a NAK. Then, the sender will try to send the same message again for a maximum of 2 times. If the message still fails, the message is considered to be lost. Preferably, a notification is given to the user (operator) that data has been lost by the sender and/or the receiver. Remark: The receiver sends an ACK or a NAK as a single character without other data. The ACK or NAK refers to the latest message sent by the sender. To avoid record synchronisation problems between sender and receiver, the sender must ignore any ACK or NAK received during the transmission of a message until the last byte is sent (EOT character). Also, the receiver is not allowed to send an ACK or NAK during the reception of a message until the last byte is received (EOT character). Calculation of the CRC-16 value The CRC value is calculated according to the ITU1 definition. The CRC value is calculated over all record bytes, starting with the record code, ending with CR+LF. The polynomial used is x16 + x12 + x5 + x0 = 11021h (i.e. XOR mask 1021 h) and initial value FFFFh. The value is written in ASCII characters in hexadecimal code with capitals (0.9, A.F). Sender without receiving options for handshaking For old vehicle/equipment “Data transmission handlers”, it may be impossible to receive data. In this case the sender cannot respond to an ACK or NAK, i.e. there is no handshaking feature. Hence, the sender will send a new message. This may cause in the result that data gets lost, e.g. in case the Board-computer was not started up yet or if transmission failed. It is up to the user to handle this problem (for example to connect power supply such that power-up is always at the same time for sender and transmitter). Synchronisation of communication To synchronise communication between sender and receiver, a message always starts with an SOH and ends with an EOT. If the receiver is not synchronised yet but the sender is already transmitting a message (e.g. when the Board-computer starts up while the spreader “Data transmission handler” is sending), all data before the first SOH will be ignored. If the receiver is synchronised but detects an SOH before an EOT, the previous, unfinished message is ignored. Time synchronisation between sender and receiver In general, the sender system time and the receiver system time are not equal. To synchronise messages to the system clock of the receiver, a time synchronisation record is introduced. This Time Sync record (refer to 5.5.2) contains the actual system time of the sender at the start of record transmission (with a maximum error of ± 0,5 s).
1
International Telecommunication Union.
EN 15430-1:2007 (E) 9 The receiver must record its system time at the moment of reception of a message. In case of the reception of a Time Sync record, the receiver can calculate the difference between its own system clock and the system clock of the sender. Now, the receiver can time-synchronise every message received from the sender and thereby synchronise this data to other data generated by other sources. The board computer must contain a real time clock which runs even if the board computer has no power. The electronic system on the vehicle/equipment must have a real time clock which runs even when this system has no power, or, a software clock must be implemented made which starts at date 1-1-2000 and time 00:00:00 and is updated every second. A Time Sync record, is sent by the sender • as the first message starting the communication, • after 10 s if the receiver does not respond to a message with an ACK or a NAK; after a successful transmission of this record, the latest message before the time synchronisation record is transmitted again, • if the system clock of the sender is adjusted, reset or set to any value which would cause a jump in time.
Loss of data Data will get lost in case of • “Data transmission handler” without handshaking feature which is sending while reliable communication is not possible, • overflow of the buffer-memory, • 2 unsuccessful retransmissions after a NAK. In case the “Data transmission handler” supports handshaking, it is mandatory sending the header record as the first record of a report (note: the Time Sync record is not part of the report). i.e. the header record may not get lost. Example of a message is shown in graphical form:
Example in ASCII:
Example in hexadecimal notation:
Start (1 byte) Data (codes + values, “;” separated) (x bytes) CR+LF (2 bytes) CRC-16 (4 bytes) End (1 byte) SOH 1;10;1602048;0441021;5;Abc;Equip1;;; 3230 EOT CR LF 01 313B31303B313630323034383B303434313032313B353B4162633B4571756970313B3B3B 33 32 33 300D 0A 04
EN 15430-1:2007 (E)
10
Communication example:
Figure 3 – Flow diagram
EN 15430-1:2007 (E) 11
Sender algorithm:
Receiver algorithm:
Figure 4 - Flow chart
EN 15430-1:2007 (E)
12 5 Definitions of variables, records and report 5.1 General A report is a file of records which in general is used to describe one ride. A report starts with a header record, one or more status records of the vehicle/equipment(s) and a footer record. A record is a structure of coherent variables in a predefined order. A member of a record is called a “field”. Table 1 - Application or equipment types Equipment Source ref.nr. Remark Board computer 1
Vehicle 2 On board vehicle electronic generating data Snow plough or broom 3 It is assumed that if there is more than one snow-plough, the data is generated by one source only. Snow blower or cutter 4
Spreader or sprayer 5 Remark: this equipment could also generate the data for example for a snow plough, however, the source reference number stays 5 (as the spreader is the data generator). Road weather and road condition information system 6
Grass or branch cutting machine 7
Sweeper 8
Safety post cleaning machine 9
Boat plants cutter 10 Used for cutting plants in canals or rivers Other 11 To be used for any equipment not defined 5.2 Variable types All variables defined, have to comply to one of the following variable types. The column “Format” shows how a variable is represented in one or more examples. A full stop is defined as a decimal separator. Data ranges are defined in the same way as SAE J1939/71 defines them:
EN 15430-1:2007 (E) 13 Table 2 - Ranges Range Name 1 byte 2 bytes 4 bytes ASCII 0 to 250 0 to 64 255 0 to 4211081215 1 to 254 Valid Signal 00h to FAh 0000h to FAFFh 00000000h to FAFFFFFFh 01h to FEh 251 64256 to 64 511 4211081216 to 4227858431 Parameter specific indicator FBh FB00h to FBFFh FBxxxxxxh None 252 to 253 64512 to 65 023 4227858432 to 4261412863 Reserved range for future indicator bits FCh to FDh FC00h to FDFFh FC000000h to FDFFFFFFh None 254 65 024 to 65 279 4261412864 to 4278190079 0 Error indicator FEh FExxh FExxxxxxh 00h 255 65280 to 65 535 4278190080 to 4294967294255 255 Not available or not requested FFh FFxxh FFxxxxxxh FFh Table 3 - Basic variable types Type Range Length Format Remark BOOLEAN 0, 1 2 Bits 00 = Value is 0, no errors 01 = Value is 1, no errors 10 = Error 11 = not available Definition taken from SAE J1939 CHAR -125.+125 1 byte 0.250, Offset -125 254 = Error 255 = not available Definition taken from SAE J1939 UNSIGNED CHAR 0.250 1 byte 0.250, Offset 0 254 = Error 255 = not available Definition taken from SAE J1939 SIGNED SHORT -32 127.+ 32 127 2 bytes 0.64255, Offset 32768 65024.65279 = Error 65280.65535 = not available Definition taken from SAE J1939 UNSIGNED SHORT 0.64255 2 bytes 0.64255, Offset 0 65024.65279 = Error 65280.65535 = not available Definition taken from SAE J1939 SIGNED LONG - 2105540608 .
+2105540608 4 bytes 0 to 4211081215,
Offset -2105540608, 4261412864 to 4278190079 = Error, 4278190080 to 4294967295 = not Definition taken from SAE J1939
EN 15430-1:2007 (E)
14 Type Range Length Format Remark available UNSIGNED LONG 0.4211081215 4 bytes 0 to 4211081215,
Offset -2105540608, 4261412864 to 4278190079 = Error, 4278190080 to 4294967295 = not available Definition taken from SAE J1939 BASIC_DATE 1.31,75 day 1.12 month 1985.2235 year 3 bytes 0,25 day/bit, 0 day offset 1 month/bit, 0 month offs. 1 year/bit, +1985 offset Definition taken from SAE J1939 Remarks: day = 0 is forbidden day = 1,2,3,4 are first day of month day = 5,6,7,8 are second day of month. month = 0 is forbidden year = 0 is 1985, year = 1 is 1986, . BASIC_TIME 0.23 h 0.59 min 0.59,75 s 3 bytes 1 h/bit, 0 h offset 1 min/bit, 0 min offset 0,25 s/bit, 0 s offset Definition taken from SAE J1939 STRING_X
ASCII-characters (character set is ISO Latin I) The string length must be <=
X Allowed char values: 01h.FEh 00h = Error FFh = not available Definition taken from SAE J1939 SAEat1728 Any string with max. 255 characters. NOTE The STRING_X type has to follow these additional rules: • If a transmission handler returns a valid string field the first character may not be 00h or FFh.
The predefined string length has to be covered completely with valid characters.
• If the valid string content is shorter than the predefined length ( X characters), the rest of the predefined length has to be filled with FFh characters to indicate that these characters are not valid. • If a transmission handler cannot supply the string filed the first character has to be either 00h, when the contents are incorrect, or FFh, when the contents are not available. In these two special cases the string length may be only one character in size, although it is also allowed to fill the rest of the predefined string length with FFh characters.
EN 15430-1:2007 (E) 15 Table 4 - ISO LATIN I Character set definition
x0 x1 x2 x3 x4 x5 x6 x7 x8 x9 xA xB xC xD xExF 0x ------------------------------------------- Should not be displayed ------------------------------------------- 1x ----------------------------------------------------------------------------------------------------------------------- 2x SP ! " # $ % & ' ( ) * + , - . / 3x 0 1 2 3 4 5 6 7 8 9 : ; <
= >
? 4x @ A B C D E F G H I J K L M N O 5x P Q R S T U V W X Y Z [ \ ] ^ _ 6x ` a b c d e f g h i j k l m n o 7x p q r s t u v w x y z { | } ~
8x ------------------------------------------- Should not be displayed ------------------------------------------- 9x ----------------------------------------------------------------------------------------------------------------------- Ax NBSP ¡ ¢ £ ¤ ¥ ¦ § ¨ © ª « ¬ SHY ® ¯ Bx ° ± ² ³ ´ µ ¶ · ¸ ¹ º » ¼ ½ ¾ ¿ Cx À Á Â Ã Ä Å Æ Ç È É Ê Ë Ì Í Î Ï Dx Ð Ñ Ò Ó Ô Õ Ö × Ø Ù Ú Û Ü Ý Þ ß Ex à á â ã ä å æ ç è é ê ë ì í î ï Fx Ð ñ ò ó ô õ ö ÷ ø ù ú û ü ý þ ÿ 5.3 Recommended SLOTs for variable definitions This section is intended to define a set of recommended SLOTs (Scaling, Limit, Offset, and Transfer Function), which can be used when parameters are added to this standard. This permits data consistency is to be maintained as much as possible between parameters of a given type (temperature, pressure, speed, etc.). Each SLOT is intended to provide a range and resolution suitable for most parameters within a given type. When necessary, a different scaling factor or offset can be used. All SLOTs should be based on a power of 2 scaling from another SLOT. This will minimize the math required for any internal scaling and reduce the opportunity for misinterpreted values. Offsets should be selected preferably on the following basis: a) Offset = 0 b) Offset = 50% (equal ± range) If Parameter Size is 16 Bit or more, LSB is first, MSB is last. Table 5 - SLOT definitions Parameter Scaling (Resolution) Limits (Range) Offset Parameter Size SLOT-Name Angle/Direction 1 10-7 deg/bit -211 to 211,108122 deg - 211 32 Bit SAEad01 Angle/Direction 2 1/128 deg/bit -200 deg to 301 deg - 200 16 Bit SAEad04 Angle/Direction 3 1/128 deg/bit 0 deg to 502 deg 0 16 Bit SAEad05 Distance 1 0,125 km/bit 0 km to 526385151,9 km 0 32 Bit SAEds10 Distance 2 0,125 m/bit - 2500 to 5531,875 m - 2500 16 Bit SAEds06 Distance 3 0,001 m/bit 0 m to 4211081,215 m 0 32 Bit SAEds05 Distance 4 0,125 m/bit 0 m to 8031.875 m 0 16 Bit CENds01
EN 15430-1:2007 (E)
16 Parameter Scaling (Resolution) Limits (Range) Offset Parameter Size SLOT-Name Distance 5 5 m/bit 0
mto 21055406 km 0 32 Bit SAEds09 Distance 6 0,1 mm/bit 0 m to 6425.5 mm 0 16 Bit SAEds04 Economy 1/512 km/L per bit 0 m to 125.5 km/L 0 16 Bit SAEel01 Electrical Current 1 1 A/bit -125 A to 125 A -125 8 Bit SAEec02 Electrical Current 2 1 A/bit 0 A to 250 A 0 8 Bit SAEec03 Electrical Potential 0,05 V/bit 0 V to 3212.75 V 0 16 Bit SAEev01 Flow Rate 1 0,05 L/h per bit 0 L/h to 3212.75 L/h 0 16 Bit SAEful01 Flow Rate 2 0,05 L/h per bit 0 L/h to 21055406 L/h 0 32 Bit CENful01 Force 5 N/bit 0 N to 321275 N 0 16 Bit SAEfr01 Governor Gain 1/1280 %/rpm per bit 0 %/rpm to 0.19 %/rpm 0 8 Bit SAEgg01 Mass (cargo) 1 0,5 kg/bit 0 kg to 32127.5 kg 0 16 Bit SAEmc01 Mass (cargo) 2 2 kg/bit 0 kg to 128510 kg 0 16 Bit SAEmc02 Mass (cargo) 3 0,5 kg/bit 0 kg to 2105540608kg 0 32 Bit CENmc01 Percent 1 (Position/Level) 0,4%/bit 0 % to 100% 0 8 Bit SAEpc03 Percent 2 (Position/Level) 1%/bit -125 % to 125% -125 8 Bit SAEpc05 Percent 3 (Position/Le
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.