SIST EN 15430-1:2015
(Main)Winter and road service area maintenance equipment – Data acquisition and transmission - Part 1: In vehicle data acquisition
Winter and road service area maintenance equipment – 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 equipment
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 equipment for performing winter
maintenance and road service area maintenance.
Winterdienst- und Straßenbetriebsdienstausstattung - Datenerfassung und -übertragung - Teil 1: Datenerfassung im Fahrzeug
Diese 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 routières - 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
Ta evropski standard določa standardiziran protokol za prenos podatkov od nadzorne omarice opreme do računalnika v vozilu za zagotavljanje izmenljivosti med vozilom in drugo opremo, ki je lahko nameščena v istem vozilu.
Določa povezavo vmesnika in spremenljivke, zapise ter poročila, ki omogočajo standardiziranemu protokolu obravnavanje aplikacij z največjim možnim naborom opreme za izvajanje vzdrževalnih del zimske službe in službe za vzdrževanje cest.
General Information
Relations
Standards Content (Sample)
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Oprema za vzdrževalna dela zimske službe in službe za vzdrževanje cest - Zajem in prenos podatkov - 1. del: Zajem podatkov v voziluWinterdienst- und Straßenbetriebsdienstausstattung - Datenerfassung und -übertragung - Teil 1: Datenerfassung im FahrzeugMatériels de viabilité hivernale et d'entretien des dépendances routières - Acquisition et transmission des données - Partie 1 : Acquisition des données véhiculairesWinter and road service area maintenance equipment – Data acquisition and transmission - Part 1: In vehicle data acquisition43.160Vozila za posebne nameneSpecial purpose vehicles35.240.60Uporabniške rešitve IT v transportu in trgoviniIT applications in transport and tradeICS:Ta slovenski standard je istoveten z:EN 15430-1:2015SIST EN 15430-1:2015en,fr,de01-oktober-2015SIST EN 15430-1:2015SLOVENSKI
STANDARDSIST EN 15430-1:2008+A1:20111DGRPHãþD
SIST EN 15430-1:2015
EUROPEAN STANDARD NORME EUROPÉENNE EUROPÄISCHE NORM
EN 15430-1
August 2015 ICS 35.240.60; 43.160 Supersedes EN 15430-1:2007+A1:2011English Version
Winter and road service area maintenance equipments - Data acquisition and transmission - Part 1: In-vehicle data acquisition Matériels de viabilité hivernale et d'entretien des dépendances routières - Acquisition et transmission des données - Partie 1 : Acquisition des données véhiculaires
Winterdienst- und Straßenbetriebsdienstausstattung - Datenerfassung und -übertragung - Teil 1: Datenerfassung im Fahrzeug This European Standard was approved by CEN on 28 May 2015.
CEN members are bound to comply with the CEN/CENELEC Internal Regulations which stipulate the conditions for giving this European Standard the status of a national standard without any alteration. Up-to-date lists and bibliographical references concerning such national standards may be obtained on application to the CEN-CENELEC 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 translation under the responsibility of a CEN member into its own language and notified to the CEN-CENELEC Management Centre has the same status as the official versions.
CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and United Kingdom.
EUROPEAN COMMITTEE FOR STANDARDIZATION
COMITÉ EUROPÉEN DE NORMALISATION EUROPÄISCHES KOMITEE FÜR NORMUNG
CEN-CENELEC Management Centre:
Avenue Marnix 17,
B-1000 Brussels © 2015 CEN All rights of exploitation in any form and by any means reserved worldwide for CEN national Members. Ref. No. EN 15430-1:2015 ESIST EN 15430-1:2015
EN 15430-1:2015 (E) 2 Contents Page
European foreword .3 Introduction .4 1 Scope .6 2 Normative references .6 3 Terms and abbreviations .6 4 Communication between vehicle/equipment and board-computer .7 4.1 General .7 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 Data integrity check . 12 5.3 Variable types . 13 5.4 Recommended SLOTs for variable definitions . 15 5.5 Definition of variables . 18 5.5.1 General . 18 5.5.2 General variables . 18 5.5.3 General geographic position system variables . 19 5.5.4 General vehicle and route variables . 19 5.5.5 General road weather and road condition variables . 20 5.5.6 Plough/Broom variables . 21 5.5.7 Snow blower or cutter variables . 21 5.5.8 Spreader/sprayer variables . 22 5.5.9 Grass or branch cutting machine variables . 24 5.5.10 Sweeper variables. 25 5.5.11 Safety post cleaning machine variables . 25 5.5.12 Boat plants cutter variables . 26 5.6 Definition of records . 26 5.6.1 General . 26 5.6.2 Time synchronisation record (record code 0) . 26 5.6.3 Standard header record (record code 1) . 27 5.6.4 Standard footer record (record code 2) . 27 5.6.5 Trigger conditions for record code 3 and higher . 27 5.6.6 Geographic position data record (record code 3) . 28 5.6.7 Vehicle and route data record (record code 4) . 29 5.6.8 Weather and road condition data record (record code 5) . 30 5.6.9 Snowplough/broom data record (record code 6/7) . 31 5.6.10 Spreader/sprayer data record (record code 8) . 32 5.6.11 Snow blower/cutter data record (record code 9) . 34 5.6.12 Grass/branch cutter data record (record code 10) . 35 5.6.13 Sweeper data record (record code 11) . 37 5.6.14 Safety post cleaning machine data record (record code 12) . 38 5.6.15 Boat plants cutter data record (record code 13) . 39 5.6.16 Free definable data record (record code 10000 and higher) . 40 5.7 Report definition . 42 Bibliography . 43
SIST EN 15430-1:2015
EN 15430-1:2015 (E) 3 European foreword This document (EN 15430-1:2015) has been prepared by Technical Committee CEN/TC 337 "Road operation equipment and products", the secretariat of which is held by AFNOR. This document supersedes EN 15430-1:2007+A1:2011. 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 February 2016, and conflicting national standards shall be withdrawn at the latest by February 2016. Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. CEN [and/or CENELEC] shall not be held responsible for identifying any or all such patent rights. The following changes haves been implemented in this new edition: — Modify variable no.127 in Table 12 by adding the sentence in bold: Spreader mode (0=Idle or Transport, 1=Spreading or Spraying, 2=Unload Hopper, 3=Spreading and Spraying, 4 = Spreading, 5 = Spraying) — Modify variable no.137 in Table 12 by adding the following remark: NOTE For spraying and spreading (SprMode=3), the value applies to the brine percentage of the spreading dosage only. According to the CEN/CENELEC Internal Regulations, the national standards organisations of the following countries are bound to implement this European Standard: Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and the United Kingdom. SIST EN 15430-1:2015
EN 15430-1:2015 (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). SIST EN 15430-1:2015
EN 15430-1:2015 (E) 5 Examples of an on-board system configuration.
Figure 2 — Diagram of possible connections SIST EN 15430-1:2015
EN 15430-1:2015 (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 equipment 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 equipment for performing winter maintenance and road service area maintenance. 2 Normative references The following documents, in whole or in part, are normatively referenced in this document and are indispensable for its application. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. ISO/IEC 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 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 CRC-32 Cyclic Redundancy Code with 32 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) SIST EN 15430-1:2015
EN 15430-1:2015 (E) 7 4 Communication between vehicle/equipment and board-computer 4.1 General The data exchange between vehicle/equipment “Data transmission handler” and the “Board-computer” shall follow at least one of the communication standards described in the present document version or future release. Until 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 — Pin 2 = Transmit Data — Pin 3 = Receive Data — 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 shall 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/IEC 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 — Pin 2 = Receive Data — Pin 3 = Transmit Data — Pin 5 = Signal Ground — Baud rate: 1 200 Bps.115 200 Bps, default 9 600 Bps. Rate shall be programmable or automatically detected (autobaud) — Data bits: 8 SIST EN 15430-1:2015
EN 15430-1:2015 (E) 8 — Stop bits: 1 — Parity: No — Data format: according to ISO/IEC 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.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. NOTE 1 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 has to 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). NOTE 2 Numerical values have to be transmitted with ASCII characters in decimal code. Calculation of the CRC-16 value. The CRC value is calculated according to the CCITT 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 1021h) and initial value FFFFh. NOTE 3 The value is written in ASCII characters in hexadecimal code with capitals (0.9,A.F). Calculation of the CRC-32 value. The CRC-32 value is calculated according to the CCITT definition. The CRC-32 value is calculated over all record bytes, starting with the record code, ending with CR+LF. The polynomial used is
x32 + x26 + x23 + x22 + x16 + x12 + x11 + x10 + x8 + x7 + x5 + x4 + x2 + x + 1 NOTE 4 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 SIST EN 15430-1:2015
EN 15430-1:2015 (E) 9 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). The receiver shall 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 shall contain a real time clock which runs even if the board computer has no power. The electronic system on the vehicle/equipment shall have a real time clock which runs even when this system has no power, or, a software clock shall be implemented 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: — a “Data transmission handler” without handshaking feature which is sending while reliable communication is not possible; — an 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: Start (1 byte) Data (codes + values, “;” separated) (x bytes) CR+LF (2 bytes) CRC-16 (2 bytes) End (1 byte) SOH 1;10;1602048;0461021;5;Abc;Equip1;;; CR LF 66D9 EOT SIST EN 15430-1:2015
EN 15430-1:2015 (E) 10 ASCII characters in hexadecimal notation: 01 31 3B 31 30 3B 31 36 30 32 30 34 38 3B 30 34 36 31 30 32 31 3B 35 3B 41 62 63 3B 45 71 75 69 70 31 3B 3B 3B 0D 0A 36 36 44 39 04 Communication example:
Figure 3 — Flow diagram SIST EN 15430-1:2015
EN 15430-1:2015 (E) 11 Sender algorithm: Receiver algorithm:
Figure 4 — Flow chart SIST EN 15430-1:2015
EN 15430-1:2015 (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 Data integrity check There are at least two methods required to assure integrity: a) Data have to be checked for manipulation of the contents themselves. b) Data have to be checked for completeness: Data have to be checked against any deletion of any parts of them. In the present standard these two requirements lead to the following methods of covering: — Data manipulation (a) is checked by CRC. — Data deletion (b) is checked by including the previously calculated CRC value into the new CRC value. In order to ensure data integrity two CRC variables (CRC_REC and CRC_STREAM) are defined for each record and generated by the board computer. CRC_REC contains the CRC-32 value calculated over all the data contents of the record itself and CRC_STREAM contains the CRC-32 value calculated over the CRC_STREAM of the preceding record and the current CRC_REC value. CRC_REC and CRC_STREAM are both optional and are not available in the Time synchronisation record (record code 0), Standard header record (record code 1) and Standard footer record (record code 2) (see 5.6). SIST EN 15430-1:2015
EN 15430-1:2015 (E) 13 5.3 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: Table 2 — Ranges Range Name 1 byte 2 bytes 4 bytes ASCII Valid Signal 0 to 250 0 to 64 255 0 to 4211081215 1 to 254 00h to FAh 0000h to FAFFh 00000000h to FAFFFFFFh 01h to FEh Parameter specific indicator 251 64256 to 64 511 4211081216 to 4227858431 None FBh FB00h to FBFFh FBxxxxxxh Reserved range for future indicator bits 252 to 253 64512 to 65 023 4227858432 to 4261412863 None FCh to FDh FC00h to FDFFh FC000000h to FDFFFFFFh Error indicator 254 65 024 to 65 279 4261412864 to 4278190079 0 FEh FExxh FExxxxxxh 00h Not available or not requested 255 65280 to 65 535 4278190080 to 4294967294255 255 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 available Definition taken from SAE J1939 SIST EN 15430-1:2015
EN 15430-1:2015 (E) 14 Type Range Length Format Remark 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 shall 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. SIST EN 15430-1:2015
EN 15430-1:2015 (E) 15 Table 4 — ISO LATIN I Character set definition
x0 x1 x2 x3 x4 x5 x6 x7 x8 x9 xA xB xC xD xE xF 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 -----------------------------------------------------------------------------
...
SLOVENSKI STANDARD
kSIST FprEN 15430-1:2015
01-marec-2015
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
Winter and road service area maintenance equipment – Data acquisition and
transmission - Part 1: In vehicle data acquisition
Winterdienst- und Straßenbetriebsdienstausstattung - Datenerfassung und -übertragung
- Teil 1: Datenerfassung im Fahrzeug
Matériels de viabilité hivernale et d'entretien des dépendances routières - Acquisition et
transmission des données - Partie 1 : Acquisition des données véhiculaires
Ta slovenski standard je istoveten z: FprEN 15430-1
ICS:
35.240.60 Uporabniške rešitve IT v IT applications in transport
transportu in trgovini and trade
43.160 Vozila za posebne namene Special purpose vehicles
kSIST FprEN 15430-1:2015 en,fr,de
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
---------------------- Page: 1 ----------------------
kSIST FprEN 15430-1:2015
---------------------- Page: 2 ----------------------
kSIST FprEN 15430-1:2015
EUROPEAN STANDARD
FINAL DRAFT
FprEN 15430-1
NORME EUROPÉENNE
EUROPÄISCHE NORM
November 2014
ICS 35.240.60; 43.160 Will supersede EN 15430-1:2007+A1:2011
English Version
Winter and road service area maintenance equipment - Data
acquisition and transmission - Part 1: In vehicle data acquisition
Winterdienst- und Straßenbetriebsdienstausstattung -
Datenerfassung und -übertragung - Teil 1: Datenerfassung
im Fahrzeug
This draft European Standard is submitted to CEN members for unique acceptance procedure. It has been drawn up by the Technical
Committee CEN/TC 337.
If this draft becomes a European Standard, CEN members are bound to comply with the CEN/CENELEC Internal Regulations which
stipulate the conditions for giving this European Standard the status of a national standard without any alteration.
This draft European Standard was established by CEN in three official versions (English, French, German). A version in any other language
made by translation under the responsibility of a CEN member into its own language and notified to the CEN-CENELEC Management
Centre has the same status as the official versions.
CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia,
Finland, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania,
Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and United
Kingdom.
Recipients of this draft are invited to submit, with their comments, notification of any relevant patent rights of which they are aware and to
provide supporting documentation.
Warning : This document is not a European Standard. It is distributed for review and comments. It is subject to change without notice and
shall not be referred to as a European Standard.
EUROPEAN COMMITTEE FOR STANDARDIZATION
COMITÉ EUROPÉEN DE NORMALISATION
EUROPÄISCHES KOMITEE FÜR NORMUNG
CEN-CENELEC Management Centre: Avenue Marnix 17, B-1000 Brussels
© 2014 CEN All rights of exploitation in any form and by any means reserved Ref. No. FprEN 15430-1:2014 E
worldwide for CEN national Members.
---------------------- Page: 3 ----------------------
kSIST FprEN 15430-1:2015
FprEN 15430-1:2014 (E)
Contents Page
Foreword .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 Data integrity check . 12
5.3 Variable types . 13
5.4 Recommended SLOTs for variable definitions . 15
5.5 Definition of variables . 17
5.5.1 General . 17
5.5.2 General variables . 17
5.5.3 General geographic position system variables . 18
5.5.4 General vehicle and route variables . 19
5.5.5 General road weather and road condition variables . 19
5.5.6 Plough/Broom variables . 20
5.5.7 Snow blower or cutter variables . 20
5.5.8 Spreader/sprayer variables . 21
5.5.9 Grass or branch cutting machine variables . 23
5.5.10 Sweeper variables. 24
5.5.11 Safety post cleaning machine variables . 24
5.5.12 Boat plants cutter variables . 25
5.6 Definition of records . 25
5.6.1 General . 25
5.6.2 Time synchronisation record (record code 0) . 25
5.6.3 Standard header record (record code 1) . 26
5.6.4 Standard footer record (record code 2) . 26
5.6.5 Trigger conditions for record code 3 and higher . 26
5.6.6 Geographic position data record (record code 3) . 27
5.6.7 Vehicle and route data record (record code 4) . 28
5.6.8 Weather and road condition data record (record code 5) . 29
5.6.9 Snowplough/broom data record (record code 6/7) . 30
5.6.10 Spreader/sprayer data record (record code 8) . 31
5.6.11 Snow blower/cutter data record (record code 9) . 33
5.6.12 Grass/branch cutter data record (record code 10) . 34
5.6.13 Sweeper data record (record code 11) . 36
5.6.14 Safety post cleaning machine data record (record code 12) . 37
5.6.15 Boat plants cutter data record (record code 13) . 38
5.6.16 Free definable data record (record code 10000 and higher) . 39
5.7 Report definition . 40
Bibliography . 41
2
---------------------- Page: 4 ----------------------
kSIST FprEN 15430-1:2015
FprEN 15430-1:2014 (E)
Foreword
This document (FprEN 15430-1:2014) has been prepared by Technical Committee CEN/TC 337 "Road
operation equipment and products", the secretariat of which is held by AFNOR.
This document is currently submitted to the Unique Acceptance procedure.
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent
rights. CEN [and/or CENELEC] shall not be held responsible for identifying any or all such patent rights.
This document supersedes EN 15430-1:2007+A1:2011.
The following changes haves been implemented in this new edition:
— Modify variable no.127 in Table 12 by adding the sentence in bold:
Spreader mode (0=Idle or Transport, 1=Spreading or Spraying, 2=Unload Hopper, 3=Spreading and
Spraying, 4 = Spreading, 5 = Spraying)
— Modify variable no.137 in Table 12 by adding the following remark:
NOTE For spraying and spreading (SprMode=3), the value applies to the brine percentage of the spreading dosage
only.
3
---------------------- Page: 5 ----------------------
kSIST FprEN 15430-1:2015
FprEN 15430-1:2014 (E)
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).
Examples of an on-board system configuration.
4
---------------------- Page: 6 ----------------------
kSIST FprEN 15430-1:2015
FprEN 15430-1:2014 (E)
Figure 2 — Diagram of possible connections
5
---------------------- Page: 7 ----------------------
kSIST FprEN 15430-1:2015
FprEN 15430-1:2014 (E)
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 equipment
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 equipment for performing winter
maintenance and road service area maintenance.
2 Normative references
The following referenced documents are indispensable for the application of this document. For dated
references, only the edition cited applies. For undated references, the latest edition of the referenced
document (including any amendments) applies.
ISO/IEC 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 06 )
h
ASCII American national Standard Code for Information Interchange
Bps Bits per second
CRC-16 Cyclic Redundancy Code with 16 bits
CRC-32 Cyclic Redundancy Code with 32 bits
CR Carriage Return (ASCII control code 0D )
h
EOT End Of Transmission (ASCII control code 04 )
h
Number before h is in hexadecimal notation
h
IEEE Institute of Electrical and Electronics Engineers
LF Line Feed (ASCII control code 0A )
h
NAK Negative acknowledge (ASCII control code 15 )
h
SOH Start Of Header (ASCII control code 01 )
h
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” shall
follow at least one of the communication standards described in the present document version or future
6
---------------------- Page: 8 ----------------------
kSIST FprEN 15430-1:2015
FprEN 15430-1:2014 (E)
release. Until 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
— Pin 2 = Transmit Data
— Pin 3 = Receive Data
— 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 shall 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/IEC 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
— Pin 2 = Receive Data
— Pin 3 = Transmit Data
— Pin 5 = Signal Ground
— Baud rate: 1 200 Bps.115 200 Bps, default 9 600 Bps. Rate shall be programmable or automatically
detected (autobaud)
— Data bits: 8
— Stop bits: 1
— Parity: No
— Data format: according to ISO/IEC 8859-1 (ASCII)
— Handshaking: by software with ACK, NAK ASCII control codes, refer to 4.2.3
7
---------------------- Page: 9 ----------------------
kSIST FprEN 15430-1:2015
FprEN 15430-1:2014 (E)
— 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.
NOTE 1 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
has to 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).
NOTE 2 Numerical values have to be transmitted with ASCII characters in decimal code.
Calculation of the CRC-16 value.
The CRC value is calculated according to the CCITT definition. The CRC value is calculated over all record
16 12 5 0
bytes, starting with the record code, ending with CR+LF. The polynomial used is x + x + x + x = 11021
h
(i.e. XOR mask 1021 ) and initial value FFFF .
h h
NOTE 3 The value is written in ASCII characters in hexadecimal code with capitals (0.9,A.F).
Calculation of the CRC-32 value.
The CRC-32 value is calculated according to the CCITT definition. The CRC-32 value is calculated over all
record bytes, starting with the record code, ending with CR+LF. The polynomial used is
32 26 23 22 16 12 11 10 8 7 5 4 2
x + x + x + x + x + x + x + x + x + x + x + x + x + x + 1
NOTE 4 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
8
---------------------- Page: 10 ----------------------
kSIST FprEN 15430-1:2015
FprEN 15430-1:2014 (E)
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). The receiver shall 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 shall
contain a real time clock which runs even if the board computer has no power. The electronic system on the
vehicle/equipment shall have a real time clock which runs even when this system has no power, or, a software
clock shall be implemented 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:
— a “Data transmission handler” without handshaking feature which is sending while reliable communication
is not possible;
— an 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:
Start Data (codes + values, “;” separated) (x bytes) CR+LF CRC-16 End
(1 byte) (2 bytes) (2 bytes) (1 byte)
SOH 1;10;1602048;0461021;5;Abc;Equip1;;; CR LF 66D9 EOT
ASCII characters in hexadecimal notation:
01 31 3B 31 30 3B 31 36 30 32 30 34 38 3B 30 34 36 31 0D 0A 36 36 44 39 04
30 32 31 3B 35 3B 41 62 63 3B 45 71 75 69 70 31 3B
3B 3B
Communication example:
9
---------------------- Page: 11 ----------------------
kSIST FprEN 15430-1:2015
FprEN 15430-1:2014 (E)
Figure 3 — Flow diagram
10
---------------------- Page: 12 ----------------------
kSIST FprEN 15430-1:2015
FprEN 15430-1:2014 (E)
Sender algorithm: Receiver algorithm:
Figure 4 — Flow chart
11
---------------------- Page: 13 ----------------------
kSIST FprEN 15430-1:2015
FprEN 15430-1:2014 (E)
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 6
condition information system
Grass or branch cutting 7
machine
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 Data integrity check
There are at least two methods required to assure integrity:
a) Data have to be checked for manipulation of the contents themselves.
b) Data have to be checked for completeness: Data have to be checked against any deletion of any parts of
them.
In the present standard these two requirements lead to the following methods of covering:
— Data manipulation (a) is checked by CRC.
— Data deletion (b) is checked by including the previously calculated CRC value into the new CRC value.
In order to ensure data integrity two CRC variables (CRC_REC and CRC_STREAM) are defined for each
record and generated by the board computer. CRC_REC contains the CRC-32 value calculated over all the
data contents of the record itself and CRC_STREAM contains the CRC-32 value calculated over the
CRC_STREAM of the preceding record and the current CRC_REC value. CRC_REC and CRC_STREAM are
both optional and are not available in the Time synchronisation record (record code 0), Standard header
record (record code 1) and Standard footer record (record code 2) (see 5.6).
12
---------------------- Page: 14 ----------------------
kSIST FprEN 15430-1:2015
FprEN 15430-1:2014 (E)
5.3 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:
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
None
indicator
FBh FB00h to FBFFh FBxxxxxxh
252 to 253 64512 to 65 023 4227858432 to 4261412863
Reserved range for
None
future indicator bits
FCh to FDh FC00h to FDFFh FC000000h to FDFFFFFFh
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
00 = Value is 0, no errors
01 = Value is 1, no errors Definition taken from
BOOLEAN 0, 1 2 Bits
10 = Error SAE J1939
11 = not available
0.250, Offset -125
Definition taken from
CHAR -125.+125 1 byte 254 = Error
SAE J1939
255 = not available
0.250, Offset 0
UNSIGNED Definition taken from
0.250 1 byte 254 = Error
CHAR SAE J1939
255 = not available
0.64255, Offset 32768
SIGNED
65024.65279 = Error Definition taken from
-32 127.+ 32 127 2 bytes
65280.65535 = not SAE J1939
SHORT
available
0.64255, Offset 0
UNSIGNED 65024.65279 = Error Definition taken from
0.64255 2 bytes
SHORT 65280.65535 = not SAE J1939
available
0 to 4211081215,
Offset -2105540608,
4261412864 to
- 2105540608 . Definition taken from
SIGNED LONG 4 bytes 4278190079 = Error,
+2105540608 SAE J1939
4278190080 to
4294967295 = not
available
0 to 4211081215,
Offset -2105540608,
UNSIGNED Definition taken from
4261412864 to
0.4211081215 4 bytes
LONG SAE J1939
4278190079 = Error,
4278190080 to
4294967295 = not
13
---------------------- Page: 15 ----------------------
kSIST FprEN 15430-1:2015
FprEN 15430-1:2014 (E)
Type Range Length Format Remark
available
Definition taken from
SAE J1939
Remarks:
day = 0 is forbidden
day = 1,2,3,4 are first
1.31,75 day 0,25 day/bit, 0 day offset
day of month
BASIC_DATE 1.12 month 3 bytes 1 month/bit, 0 month offs.
day = 5,6,7,8 are
1985.2235 year 1 year/bit, +1985 offset
second day of month
....
month = 0 is forbidden
year = 0 is 1985,
year = 1 is 1986,
...
0.23 h 1 h/bit, 0 h offset
Definition taken from
BASIC_TIME 0.59 min 3 bytes 1 min/bit, 0 min offset
SAE J1939
0.59,75 s 0,25 s/bit, 0 s offset
The Definition taken from
Allowed char values:
string SAE J1939
ASCII-characters 01h.FEh
STRING_X length SAEat1728
(character set is ISO Latin I) 00h = Error
shall be Any string with max.
FFh = not available
<= X 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
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.