Sie sind auf Seite 1von 31

Page 1 of 31 APC IRMA IV IBIS Protocol Version 1.

00, 03/14/2006

APC IRMA IV IBIS Protocol Version 1.00 03/14/2006


Document History
Version 1.00, 03/14/2006 by Bernd Schubert: Initial document.

Page 2 of 31 APC IRMA IV IBIS Protocol Version 1.00, 03/14/2006

1
1.1

Introduction
Terms and Definitions

Within this document term on-board computer refers to all type of vehicle equipment connected to the same interface bus as IRMA analyzer(s) and capable of communicating by means of IBIS Protocol. Term IRMA analyzer refers to the following products: Product IRMA-A21S-2-IBIS IRMA-A21C-2-IBIS IRMA-A21C8-4-IBIS IRMA-A21S-2-RS485 IRMA-A21S-2-RS485.2 IRMA-A21C-2-RS485 IRMA-A21CL-3-51 Interface IBIS IBIS IBIS RS-485, 4-wire RS-485, 2-wire RS-485, 4-wire RS-232

List of products above were up-to-date at release date of this document. Updates of this product list may be done without corresponding update of this document.
1.1.1 Abbreviations

IBISIP UIRMAIP 1.2


1.2.1

IBIS Protocol for APC IRMA Universal IRMA Protocol

Applicable Documents
VDV Publications

VDV 300 Revision 01/92


1.2.2

Integrated On-Board Information System (IBIS)

Documents of iris company

iris UIRMAIP Version 1.06, 09/27/2004

Universal IRMA Protocol Specification (IRMA-A21-Kommunikationsprotokolle_ V1-06_Entwurf_27.09.2004_eng.pdf)

Versions and release dates of documents listed above were up-to-date at release date of this document. Updates of documents listed above may be published without corresponding update of this document. 1.3 Purpose

IBISIP was specified based upon VDV 300 to establish the following communication capabilities: Transfer of counting results from IRMA analyzer(s) to on-board computer. Transfer of status information from IRMA analyzer(s) to on-board computer. Query of configuration of IRMA analyzer(s) by on-board computer.

Page 3 of 31 APC IRMA IV IBIS Protocol Version 1.00, 03/14/2006

There is an IBISIP data record for switching to UIRMAIP. On IRMA analyzer RS-232 service interface (A21 connector C) default baud rate 38,400bps is used for UIRMAIP. This communication protocol is used for fast IRMA analyzer software updates controlled by IRMA service software suite IRMA-A21-Windows. It is also used for IRMA installation mode. Modular update of IRMA analyzer software is available if software supports runtime modularity. Term update recovery mode is related to repetition of modular software update after IRMA analyzer configuration data became invalid as result of disturbed software update. 1.4 General Specifications

IBIS protocol specified by recommendations VDV 300 is based upon master-slave principle. As a result IBISIP communication is always half-duplex. Small letter b is first character of all IBIS data records related to passenger counting. APC protocol specified by VDV 300 was extended by proprietary data records for full support of system IRMA IV.
1.4.1 Structure of IBIS Data Records

Term IBIS data record is used in recommendations VDV 300. It can be treated as a synonym for IBIS message. Character within IBIS data record is represented by 11 bits transmitted serially: 1 start bit 7 data bits 1 parity bit 2 stop bits ST Start bit b1 LSB b2 ST b1b7 P S b3 b4 b5 b6 b7 MSB P S Parity Stop bit bit S Stop bit

IBIS character format can be described by the usual abbreviation 7E2. Parity bit completes count of data bits to an even number (even parity). Examples: character b S CR 7 data bits + parity bit represented by 2-digit hexadecimal number 0xE2 0x53 0x8D

An IBIS data record is a sequence of characters of serial format described above. IBIS data record contains no information about number of characters. End of IBIS data record is indicated by format control character F. ASCII character CR (Carriage Return) is used for this purpose. Format control character F is followed by control character P which is always the last character of IBIS data record. Control character P can be treated as checksum of IBIS data record. Its ASCII code is calculated according to the following formula: P = NOT (CH1 XOR CH2 XOR ... XOR CHn)

Page 4 of 31 APC IRMA IV IBIS Protocol Version 1.00, 03/14/2006

Symbols CH1 ... CHn represent ASCII code of all characters preceeding P within data record. Format control character F is included in characters CH1 ... CHn. All IBISIP data records have one of the following structures: DI DRI DRA PL1 PLm F P Data identifier Data record identifier Data record address First byte of payload of IBIS data record Last byte of payload of IBIS data record Format control character Control character (term according to VDV 300)

(term according to VDV 300) (term according to VDV 300)

Call-up data record transmitted by on-board computer: CH1 CH2 CH3 CH4 ... CHn-1 CHn DI DRI DRA PL1 ... PLm F P b ... CR Minimum value of payload length m: 0 Maximum value of payload length m: 250 Response data record transmitted by IRMA analyzer including data record identifier: CH1 CH2 CH3 ... CHn-1 CHn DI DRI PL1 ... PLm F P b ... CR Minimum value of payload length m: 0 Maximum value of payload length m: 251 Response data record transmitted by IRMA analyzer without data record identifier: CH1 CH2 ... CHn-1 CHn DI PL1 ... PLm F P b ... CR Minimum value of payload length m: 1 Maximum value of payload length m: 252 Payload PL1PLm of response data record without data record identifier may consist of characters of type H only. Refer to section 1.4.2 for more information. Total length of IBISIP data record is always equal to n + 1. It is always smaller than 256. Example of call-up data record without payload: Hexadecimal number Hexadecimal number Character without parity bit with parity bit b 0x62 0xE2 V 0x56 0x56 1 0x31 0xB1 CR 0x0D 0x8D 0x77 0x77

Meaning within IBIS data record Data identifier Data record identifier Data record address Format control character Control character

Page 5 of 31 APC IRMA IV IBIS Protocol Version 1.00, 03/14/2006

Example of response data record including data record identifier: Hexadecimal number Hexadecimal number Character without parity bit with parity bit b 0x62 0xE2 F 0x46 0xC6 CR 0x0D 0x8D 0x56 0x56 Example of response data record without data record identifier: Hexadecimal number Hexadecimal number Character without parity bit with parity bit b 0x62 0xE2 0 0x30 0x30 CR 0x0D 0x8D 0x20 0xA0
1.4.2 IBISIP Character Sets

Meaning within IBIS data record Data identifier Data record identifier Format control character Control character

Meaning within IBIS data record Data identifier Data record address Format control character Control character

IBIS data records consist of ASCII characters represented by ISO 7-bit code. Agreed limited character set according to DIN 660033 is used (German reference version). Character Type Z H H64 C D I Usage Decimal digits Hexadecimal digits Addresses Text IRMA text Data record identifiers Accordance VDV 300 VDV 300 proprietary VDV 300 proprietary proprietary Range 09 0? (see below) 1p (ASCII codes $31$70) # (ASCII codes $20$23), / (ASCII codes $27$2F), 09, AZ / (ASCII codes $20$2F), 09, ?, AZ, _, az !/ (ASCII codes $21$2F), ?, AZ, az

Page 6 of 31 APC IRMA IV IBIS Protocol Version 1.00, 03/14/2006

Hexadecimal digits are used e. g. for data record addresses and representation of counting results. In contrast to the widely used representation by a character set consisting of decimal digits 09 and capital letters AF IBIS representation is based upon character set with continuous interval of ASCII codes. Refer to the following table: Hexadecimal Digit 0 1 2 3 4 5 6 7 8 9 A B C D E F
1.4.3

Decimal number 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15

Character 0 1 2 3 4 5 6 7 8 9 : ; < = > ?

ASCII code 0x30 0x31 0x32 0x33 0x34 0x35 0x36 0x37 0x38 0x39 0x3A 0x3B 0x3C 0x3D 0x3E 0x3F

IRMA Analyzer Address Assignment

Up to 16 IRMA analyzers supporting IBISIP may be connected to interace bus to which on-board computer is connected too. There are no restrictions regarding other devices to be connected to the same interface bus. Of course these devices must comply with VDV 300 too. All call-up data records transmitted by the on-board computer have to include data record address DRA. Call-up data records without address are not answered by IRMA analyzers. In other words: Third character of call-up data record received from on-board computer is always interpreted by IRMA analyzer as address. Unique IRMA analyzer device address has to be assigned to each IRMA analyzer connected to a certain interface bus. Typically IRMA service software A21_Assistant is used for this task. A21_Assistant is part of IRMA service software suite IRMA-A21-Windows. IRMA analyzer device address can be configured using input field Device Settings, Address of A21_Assistant. Permitted range for IRMA analyzer device address: 116

Query of counting results and of door status from IRMA analyzer(s) is part of IBISIP. Call-up data record addresses used for such queries will be interpreted as door addresses. Door addresses used for a certain interface bus must be unique. Door addresses are usually configured using IRMA service software A21_Assistant. Input fields Function Areas / Sensor Assignments, FA Address have to be used for this task. Typically abstract term function area may be treated as a synonym for door. Permitted range for IRMA analyzer door addresses: 164

Page 7 of 31 APC IRMA IV IBIS Protocol Version 1.00, 03/14/2006

1.4.4

Available Baud Rates

According to recommendations VDV 300 default IBISIP baud rate is 1200bps. At this baud rate the following assignments apply: Bit duration: Transmission time of 11-bit character: 0.833ms 9.167ms

Baud rates 2400bps, 4800bps, 9600bps, 19200bps and 38400bps are available options for APC IRMA IV supporting IBISIP. Typically IRMA service software A21_Assistant is used for configuration of IBISIP baud rate. Input field Com Settings, Baud Rate is assigned to this task. Presetting of customer-specific IBISIP baud rate in IRMA analyzer software is available on request. Setting for update recovery mode: Presetted (customer-specific) IBISIP baud rate.
1.4.5 Support of RS-485 2-Wire Communication

As already mentioned above IBIS protocol specified by recommendations VDV 300 is strictly halfduplex. This enables usage of IBISIP on RS-485 2-wire interfaces. Local echo at this interface can be easily detected and suppressed by all devices connected to the RS-485 bus. However there are two issues to be considered: Response data records transmitted by a certain IRMA analyzer are received by all other IRMA analyzers connected to the same RS-485 interface bus. Therefore no response data record may be equal to any call-up data record. This requirement is not fulfilled for data record pair IDS084, IDS184. Refer to section 2.3.1 for detailed specification. As a result this data record pair must not be used for RS-485 2-wire communication. Service software A21_Assistant offers drop down list titled Com Settings, Mode. String 2-Wire has to be selected for RS-485 2-wire communication. No response data record IDS184 is transmitted by IRMA analyzer software on reception of call-up data record IDS084 if this setting is made. RS-485 transmitter of on-board computer has to be deactivated after transmission of call-up data record. Usually this task is done by on-board computer software. Thus software runtime must be taken into account. Defined delay of transmission of response data record by IRMA analyzer software is necessary to avoid RS-485 transmitter contention. This transmission delay can be configured using input field Com Settings, Delay (ms) of service software A21_Assistant.

IRMA analyzer software default settings: Com Settings, Mode = 4-Wire Com Settings, Delay (ms) = 0 Presetting of customer-specific configuration in IRMA analyzer software is available on request. Settings for update recovery mode: Com Settings, Mode = 2-Wire Com Settings, Delay (ms) = 50

Page 8 of 31 APC IRMA IV IBIS Protocol Version 1.00, 03/14/2006

1.4.6

System Limitations due to IRMA Analyzer Software Architecture

Further limitations specified for system generation APC IRMA IV: No. of doors supported by one IRMA analyzer: 14 Total no. of IRMA sensors supported by one IRMA analyzer: 18 No. of doors per vehicle supported by APC IRMA IV: 164

Please note: Limitations listed above are given by software architecture. More closer limitations may apply as a result of hardware specifications.
1.4.7 Default Settings of IRMA Analyzer Software

There are three different designs of IRMA analyzer software supporting IBISIP: Maximum No. of Doors Supported 2 3 4 Default IRMA Door Addresses 1, 2 1, 2, 3 1, 2, 3, 4

Please note: Presetting of customer-specific door addresses is available on request. Using service software A21_Assistant no. of doors supported by IRMA analyzer may be configured between value 1 and maximum given by software design. Input field Number of Function Areas has to be used for this configuration.
1.4.8 Irrelevant and Invalid IBIS Data Records

All irrelevant and invalid IBIS data records are n o t answered by IRMA analyzer. IBIS call-up data record received from on-board computer is invalid if at least one of the following conditions applies: Length of data record exceeds maximum length of 255 including control character P. Control character P of IBIS data record is invalid.

IBIS call-up data record received from on-board computer is irrelevant if at least one of the following conditions applies: First character of data record is not equal to b. Second character of data record is not equal to one of the data record identifiers supported by IRMA analyzer software. Refer to section 2 for detailed information. Third character of data record is not equal to configured address. Depending on preceding data record identifier address is interpreted either as IRMA analyzer device address or as IRMA analyzer door address.

Page 9 of 31 APC IRMA IV IBIS Protocol Version 1.00, 03/14/2006

Description of IBISIP Data Records

In this section pairs of call-up data records and according response data records are described in detail. Designators beginning with capital letters DS are used for data records. These letters are an abbreviation for German word Datensatz which is the translation of term data record. Consequent numbers assigned by recommendations VDV 300 to certain types of data record are used to complete designators. Designators beginning with capital letters IDS are used for proprietary IBISIP data records not covered by recommendations VDV 300. Numbering introduced there is extended to proprietary IBISIP data records. Numbers beginning with 0 are assigned to call-up data records while numbers beginning with 1 are assigned to response data records. 2.1 DS082, DS181

Call-up data record DS082 transmitted by on-board computer: CH1 CH2 CH3 CH4 DI DRI DRA F P H64 b F CR This type of data record is specified by recommendations VDV 300 under consequent no. 082 (Movement started). In contrast to VDV 300 data record address is included. Data record address is interpreted as door address. Response data record DS181 transmitted by IRMA analyzer: CH1 CH2 CH3 DI DRI F P b F CR This type of data record is specified by recommendations VDV 300 under consequent no. 181 (Acknowledgement and identification). Identifier F represents system type Passenger counting. Actions on reception of call-up data record DS082: 1. Query of passenger counting results for addressed door is initialized by setting of door specific flag UpdateIBISCount. Setting of this flag is independent of door state. 2. IBIS status of addressed door is set to value 1 if all of the following conditions apply: - Addressed door is closed. - Counting at addressed door is finished, i. e. evaluation of according IRMA sensor signals is stopped. - There is no fault of any IRMA sensor assigned to addressed door. 3. Transmission of response data record DS181. IBISIP dependencies: Data records DS082 and DS181 are part of query of passenger counting results. Protocol flow chart specified for this task has to be considered. Refer to section 3.1 for details.

Page 10 of 31 APC IRMA IV IBIS Protocol Version 1.00, 03/14/2006

2.2

DS083, DS183

Call-up data record DS083 transmitted by on-board computer: CH1 CH2 CH3 CH4 DI DRI DRA F P H64 b E CR This type of data record is specified by recommendations VDV 300 under consequent no. 083 (Measurement result inquiry). In contrast to VDV 300 data record address is included. Data record address is interpreted as door address. Response data record DS183 transmitted by IRMA analyzer: CH1 CH2 CH3 CH4 CH5 CH6 DI PL1 PL2 PL3 PL4 F P H H H H b CR This type of data record is specified by recommendations VDV 300 under consequent no. 183. Specification of payload PL1PL4: Numbers of boarding and alighting passengers for addressed door stored in door specific IBIS transmission buffer. PL1, PL2: number of boarding passengers, high-order digit first, 0255 PL3, PL4: number of alighting passengers, high-order digit first, 0255 Example PL1PL4 = 0, 5, 1, :: number of boarding passengers = 5 number of alighting passengers = 26 Actions on reception of call-up data record DS083: 1. If door specific flag UpdateIBISCount is equal to value TRUE following actions are executed in the order of listing: - Current passenger counting results for addressed door are read from passenger counters and stored in door specific IBIS transmission buffer. - Passenger counters for addressed door are cleared. - Door specific flag UpdateIBISCount is set to value FALSE. If door specific flag UpdateIBISCount is equal to value FALSE none of these actions is executed. 2. IBIS status of addressed door is set to value 0 if all of the following conditions apply: - Addressed door is closed. - Counting at addressed door is finished, i. e. evaluation of according IRMA sensor signals is stopped. - Call-up data record DS082 was received prior to DS083 while addressed door was closed and counting was finished at this door. - There is no fault of any IRMA sensor assigned to addressed door. IBIS status of addressed door is set to value 2 if there is no fault of any IRMA sensor assigned to this door and at least one of the following conditions apply: - Addressed door is open. - Counting at addressed door is not finished, i. e. evaluation of according IRMA sensor signals is running. - Call-up data record DS082 was not received prior to DS083 and after last closing of addressed door as well as after last finishing of counting at this door. 3. Transmission of response data record DS183.

Page 11 of 31 APC IRMA IV IBIS Protocol Version 1.00, 03/14/2006

IBISIP dependencies: Data records DS083 and DS183 are part of query of passenger counting results. Protocol flow chart specified for this task has to be considered. Refer to section 3.1 for details. 2.3
2.3.1

IDS084, IDS184 and IDS0841, IDS1841


IDS084, IDS184

This pair of call-up data record and according response data record is applicable to 4-wire communication only. Call-up data record IDS084 transmitted by on-board computer: CH1 CH2 CH3 CH4 DI DRI DRA F P H64 b S CR This type of data record is not specified by recommendations VDV 300. Data record address is interpreted as door address. Response data record IDS184 transmitted by IRMA analyzer: CH1 CH2 CH3 CH4 DI DRI PL1 F P H b S CR This type of data record is not specified by recommendations VDV 300. Specification of payload PL1: PL1: IBIS status of addressed door. 0 = no fault, door closed, counting finished, call-up data record DS082 received after last finishing of counting and call-up data record DS083 received afterwards 1 = no fault, door closed, counting finished, call-up data record DS082 received after last finishing of counting but no call-up data record DS083 received afterwards 2 = no fault, door either open or counting not finished after door closing or no call-up data record DS082 received after last finishing of counting 3 = fault type defect 4 = fault type sabotaged, this status may be active only if door is closed and counting is finished after door closing Please note: Presence of IBIS status value 1 may serve as an indicator for availability of new counting results only after first reception of call-up data record DS082 following finishing of counting and door closing. The following cases cannot be distinguished by evaluation of IBIS status: - Door was open between two consecutive queries of counting results but no passenger boarded or alighted. - Door was not open between two consecutive queries of counting results. Actions on reception of call-up data record IDS084: Transmission of response data record IDS184 provided IRMA analyzer software is not configured for 2-wire communication. IBIS status transmitted depends on current state of query of passenger counting results for addressed door. Refer to sections 2.1, 2.2 and 3.1 for details. Refer to section 4 for more information about detection of IRMA faults.

Page 12 of 31 APC IRMA IV IBIS Protocol Version 1.00, 03/14/2006

IBISIP dependencies: IBIS status query using data records IDS084 and IDS184 may be done at any time independently on other IBISIP activities. Apart from triggering of response transmission reception of IDS084 does not influence IRMA analyzer software. However query of IBIS door status is strongly recommended to enable detection of APC IRMA faults. Refer to sections 3.1 and 4 for details.
2.3.2 IDS0841, IDS1841

This pair of call-up data record and according response data record is applicable to 2-wire communication and to 4-wire communication as well. Call-up data record IDS0841 transmitted by on-board computer: CH1 CH2 CH3 CH4 DI DRI DRA F P H64 b R CR This type of data record is not specified by recommendations VDV 300. Data record address is interpreted as door address. Response data record IDS1841 transmitted by IRMA analyzer: CH1 CH2 CH3 CH4 CH5 DI DRI PL1 PL2 F P H b R 0 CR This type of data record is not specified by recommendations VDV 300. Specification of payload PL2: PL2: IBIS status of addressed door, refer to section 2.3.1 for specification of IBIS status values. Actions on reception of call-up data record IDS0841: Transmission of response data record IDS184. IBIS status transmitted depends on current state of query of passenger counting results for addressed door. Refer to sections 2.1, 2.2 and 3.1 for details. Refer to section 4 for more information about detection of IRMA faults. IBISIP dependencies: IBIS status query using data records IDS0841 and IDS1841 may be done at any time independently on other IBISIP activities. Apart from triggering of response transmission reception of IDS0841 does not influence IRMA analyzer software. However query of IBIS door status is strongly recommended to enable detection of APC IRMA faults. Refer to sections 3.1 and 4 for details.

Page 13 of 31 APC IRMA IV IBIS Protocol Version 1.00, 03/14/2006

2.4

IDS085, IDS185

Call-up data record IDS085 transmitted by on-board computer: CH1 CH2 CH3 CH4 DI DRI DRA F P H64 b ? CR This type of data record is not specified by recommendations VDV 300. Data record address is interpreted as door address. Maximum number of sensors supported by IRMA analyzer software design is equal to 14: Response data record IDS185 transmitted by IRMA analyzer: CH1 CH2 CH3 CH4 CH5 CH6 CH7 DI DRI PL1 PL2 PL3 PL4 F P C C C C b ? CR This type of data record is not specified by recommendations VDV 300. Specification of payload PL1PL4: PL1: status of IRMA sensor 1 PL2: status of IRMA sensor 2 PL3: status of IRMA sensor 3 PL4: status of IRMA sensor 4 Maximum number of sensors supported by IRMA analyzer software design is equal to 58: Response data record IDS185 transmitted by IRMA analyzer: CH1 CH2 CH3 CH4 CH5 CH6 CH7 CH8 CH9 CH10 DI DRI PL1 PL2 PL3 PL4 PL5 PL6 PL7 PL8 C C C C C C C C b ? This type of data record is not specified by recommendations VDV 300. Specification of payload PL1PL8: PL1: status of IRMA sensor 1 PL2: status of IRMA sensor 2 PL3: status of IRMA sensor 3 PL4: status of IRMA sensor 4 PL5: status of IRMA sensor 5 PL6: status of IRMA sensor 6 PL7: status of IRMA sensor 7 PL8: status of IRMA sensor 8 Specification of sensor status values: - = IRMA sensor is not assigned to addressed door 0 = IRMA sensor is assigned to addressed door, no sensor fault 3 = IRMA sensor is assigned to addressed door, sensor fault type sensor defect 4 = IRMA sensor is assigned to addressed door, sensor fault type sensor sabotaged CH11 F CR

Page 14 of 31 APC IRMA IV IBIS Protocol Version 1.00, 03/14/2006

Relationship between IBIS status of door and according sensor status is as follows: Status of all sensors assigned to certain door are equal to 0: IBIS status of door is equal to 0, 1 or 2. Status of at least one sensor assigned to certain door is equal to 3: IBIS status of door is equal to 3. Status of at least one sensor assigned to certain door is equal to 4 and there is no sensor assigned to this door with status value 3: IBIS status of door is equal to 4.

Actions on reception of call-up data record IDS085: Transmission of response data record IDS185. Refer to section 4 for more information about detection of IRMA faults. IBISIP dependencies: Sensor status query using data records IDS085 and IDS185 may be done at any time independently on other IBISIP activities. Apart from triggering of response transmission reception of IDS085 does not influence IRMA analyzer software. 2.5
2.5.1

IDS086, DS181 and IDS0861, DS181


IDS086, DS181

Call-up data record IDS086 transmitted by on-board computer: CH1 CH2 CH3 CH4 DI DRI DRA F P H64 b s CR This type of data record is not specified by recommendations VDV 300. Data record address is interpreted as door address. Response data record DS181 transmitted by IRMA analyzer: CH1 CH2 CH3 DI DRI F P b F CR This type of data record is specified by recommendations VDV 300 under consequent no. 181 (Acknowledgement and identification). Identifier F represents system type Passenger counting. Actions on reception of call-up data record IDS086: 1. Sensor fault type sensor defect is cleared for all IRMA sensors assigned to addressed door. - Conditions causing fault type sensor defect continue to exist after fault clearing for certain sensor(s): Fault type sensor defect is reactivated for this sensor (these sensors) within 1s. - Conditions causing fault type sensor defect do not continue to exist after fault clearing for certain sensor(s): Fault type sensor sabotaged is activated for this sensor (these sensors) if according conditions apply. Otherwise sensor status no fault active is present. Refer to section 4 for more information about priority of IRMA faults and clearing of faults. 2. Transmission of response data record DS181.

Page 15 of 31 APC IRMA IV IBIS Protocol Version 1.00, 03/14/2006

IBISIP dependencies: Clearing of sensor fault type sensor defect using data records IDS086 and DS181 may be done at any time independently on other IBISIP activities. Of course there must be an useful coordination of query of sensor fault type sensor defect and its clearing. Refer to section 3.3 for more information.
2.5.2 IDS0861, DS181

Data record pair IDS0861, DS181 is supported by IRMA analyzer software for the sake of clarity of specification only. usage of bs in conjunction with bS usage of br in conjunction with bR

There is not any functional difference compared to data record pair IDS086, DS181. Call-up data record IDS0861 transmitted by on-board computer: CH1 CH2 CH3 CH4 DI DRI DRA F P H64 CR b r This type of data record is not specified by recommendations VDV 300. Data record address is interpreted as door address. Response data record DS181 transmitted by IRMA analyzer: CH1 CH2 CH3 DI DRI F P b F CR This type of data record is specified by recommendations VDV 300 under consequent no. 181 (Acknowledgement and identification). Identifier F represents system type Passenger counting. Actions on reception of call-up data record IDS0861: Same as for data record IDS086, refer to section 2.5.1. IBISIP dependencies: Same as for data records IDS086 and DS181, refer to section 2.5.1. 2.6 IDS087, IDS187

Reliable real-time information about door status (closed or open) is very important to achieve guaranteed counting precision of APC IRMA. In this context state open means that door is not closed completely. State of hardware door contact connected to IRMA analyzer door signal input is continously sampled by IRMA analyzer software. Sampling interval is equal to 100ms. Delay from start of door movement to change of door contact state must not exceed 200ms. IBIS status of addressed door depends on door status but it is influenced by several other factors too. Refer to sections 2.3.1 and 4 for detailed information. It is strongly recommended to use data record pair IDS087, IDS187 if door status has to be queried by on-board computer.

Page 16 of 31 APC IRMA IV IBIS Protocol Version 1.00, 03/14/2006

Call-up data record IDS087 transmitted by on-board computer: CH1 CH2 CH3 CH4 DI DRI DRA F P b W H64 CR This type of data record is not specified by recommendations VDV 300. Data record address is interpreted as door address. Response data record IDS187 transmitted by IRMA analyzer: CH1 CH2 CH3 DI PL1 F P H b CR This type of data record is not specified by recommendations VDV 300. Specification of payload PL1: PL1: status of addressed door. 0 = door open 1 = door closed Actions on reception of call-up data record IDS087: Transmission of response data record IDS187. IBISIP dependencies: Door status query using data records IDS087 and IDS187 may be done at any time independently on other IBISIP activities. Apart from triggering of response transmission reception of IDS087 does not influence IRMA analyzer software. 2.7 DS0801, DS1801

Call-up data record DS0801 transmitted by on-board computer: CH1 CH2 CH3 CH4 DI DRI DRA F P H64 b V CR This type of data record is specified by recommendations VDV 300 under consequent no. 0801 (Version inquiry). In contrast to VDV 300 data record address is included. Data record address is interpreted as door address. Response data record DS1801 transmitted by IRMA analyzer: CH1 CH2 CH3 ... CHn-1 CHn DI DRI PL1 ... PLm F P D D b V ... CR Minimum value of payload length m: 1 Maximum value of payload length m: 59 This type of data record is specified by recommendations VDV 300 under consequent no. 1801. In contrast to VDV 300 payload length is not fixed to value 6 and extended character type D is used instead of default character type C. Specification of payload PL1PLm: String representing name of IRMA analyzer software as stored in software name area of Flash EPROM sector 5.

Page 17 of 31 APC IRMA IV IBIS Protocol Version 1.00, 03/14/2006

Actions on reception of call-up data record DS0801: Transmission of response data record DS1801. IBISIP dependencies: Query of IRMA analyzer software name using data records DS0801 and DS1801 may be done at any time independently on other IBISIP activities. Apart from triggering of response transmission reception of DS0801 does not influence IRMA analyzer software. 2.8 IDS0802, IDS1802

Call-up data record IDS0802 transmitted by on-board computer: CH1 CH2 CH3 CH4 DI DRI DRA F P H64 b P CR This type of data record is not specified by recommendations VDV 300. Data record address is interpreted as door address. Response data record IDS1802 transmitted by IRMA analyzer: CH1 CH2 CH3 ... CHn-1 CHn DI DRI PL1 ... PLm F P D D b P ... CR Minimum value of payload length m: 14 Maximum value of payload length m: 28 This type of data record is not specified by recommendations VDV 300. Specification of payload PL1PLm: String representing important configuration data of IRMA analyzer. 1 or 2 character(s) representing IRMA analyzer device address, decimal digit(s), most significant digit first delimiter _ (underline) 2...15 characters representing IRMA door configuration, set of identifiers separated by delimiter - (hyphen), no. of identifiers equal to no. of doors supported by IRMA analyzer, each identifier consists of 2 or 3 characters 1st character and possibly 2nd character: representing configured door address, decimal digit(s), most significant digit first 2nd or 3rd character: representing configured logical polarity of door contact, N or P N: logical negative polarity of door contact P: logical positive polarity of door contact delimiter _ (underline) 1 character representing IRMA communication mode, R or H R: Com Settings, Mode = 4-Wire H: Com Settings, Mode = 2-Wire delimiter _ (underline) 7 characters representing device number of IRMA analyzer, 6 decimal digits, 3rd character is hyphen, example 23-1234, white space is used as delimiter for device number at IRMA analyzer name plate

Page 18 of 31 APC IRMA IV IBIS Protocol Version 1.00, 03/14/2006

Examples for payload PL1PLm: 1_1N_R_24-1957 IRMA analyzer with device number 24 1957 and device address 1 supports one door with door address 1 and logical negative polarity of door contact. IRMA analyzer software is configured for IBIS and RS-485 4-wire interfaces. 16_5P-7P-64P_H_22-0083 IRMA analyzer with device number 22 0083 and device address 16 supports three doors with door addresses 5, 7 and 64. Logical positive polarity is configured for all door contacts. IRMA analyzer software is configured for RS-485 2-wire interface.

Actions on reception of call-up data record IDS0802: Transmission of response data record IDS1802. IBISIP dependencies: Query of IRMA analyzer configuration data using data records IDS0802 and IDS1802 may be done at any time independently on other IBISIP activities. Apart from triggering of response transmission reception of IDS0802 does not influence IRMA analyzer software. 2.9 DS080, DS181

Data record pair DS080, DS181 is supported by IRMA analyzer software for the sake of accordance to recommendations to VDV 300 only. There is not any usage of these data records. Call-up data record DS080 transmitted by on-board computer: CH1 CH2 CH3 CH4 DI DRI DRA F P H64 b T CR This type of data record is specified by recommendations VDV 300 under consequent no. 080 (Prepare measurement (open door)). In contrast to VDV 300 data record address is included. Data record address is interpreted as door address. Response data record DS181 transmitted by IRMA analyzer: CH1 CH2 CH3 DI DRI F P b F CR This type of data record is specified by recommendations VDV 300 under consequent no. 181 (Acknowledgement and identification). Identifier F represents system type Passenger counting. Actions on reception of call-up data record DS080: Transmission of response data record DS181. IBISIP dependencies: Call-up data record DS080 may be transmitted at any time independently on other IBISIP activities. Apart from triggering of response transmission reception of DS080 does not influence IRMA analyzer software.

Page 19 of 31 APC IRMA IV IBIS Protocol Version 1.00, 03/14/2006

2.10

DS081, DS181

Data record pair DS081, DS181 is supported by IRMA analyzer software for the sake of accordance to recommendations to VDV 300 only. There is not any usage of these data records. Call-up data record DS081 transmitted by on-board computer: CH1 CH2 CH3 CH4 DI DRI DRA F P CR b M H64 This type of data record is specified by recommendations VDV 300 under consequent no. 080 (Carry out measurement (door has closed)). In contrast to VDV 300 data record address is included. Data record address is interpreted as door address. Response data record DS181 transmitted by IRMA analyzer: CH1 CH2 CH3 DI DRI F P b F CR This type of data record is specified by recommendations VDV 300 under consequent no. 181 (Acknowledgement and identification). Identifier F represents system type Passenger counting. Actions on reception of call-up data record DS081: Transmission of response data record DS181. IBISIP dependencies: Call-up data record DS081 may be transmitted at any time independently on other IBISIP activities. Apart from triggering of response transmission reception of DS081 does not influence IRMA analyzer software. 2.11 IDS0811, DS181

Call-up data record IDS0811 transmitted by on-board computer: CH1 CH2 CH3 CH4 DI DRI DRA F P H64 b Y CR This type of data record is not specified by recommendations VDV 300. Data record address is interpreted as door address. Response data record DS181 transmitted by IRMA analyzer: CH1 CH2 CH3 DI DRI F P b F CR This type of data record is specified by recommendations VDV 300 under consequent no. 181 (Acknowledgement and identification). Identifier F represents system type Passenger counting.

Page 20 of 31 APC IRMA IV IBIS Protocol Version 1.00, 03/14/2006

Actions on reception of call-up data record IDS0811: Clearing of passenger counting results stored in door specific IBIS transmission buffer. Both passenger counters and virtual passenger counters used for test function Simulation of Passenger Change are initialized. Addressed door is closed: Counter of boarding passengers = Virtual counter of boarding passengers = 0 Counter of alighting passengers = Virtual counter of alighting passengers = 0 Addressed door is open: Counter of boarding passengers = Virtual counter of boarding passengers = 100 Counter of alighting passengers = Virtual counter of alighting passengers = 0 Activation of test function Simulation of Passenger Change for addressed door. Transmission of response data record DS181. IBISIP dependencies: Data record pair IDS0811, DS181 is part of test function Simulation of Passenger Change. Protocol flow chart specified for this task has to be considered. Refer to section 3.2 for details. 2.12 IDS0812, DS181

Call-up data record IDS0812 transmitted by on-board computer: CH1 CH2 CH3 CH4 DI DRI DRA F P H64 b Z CR This type of data record is not specified by recommendations VDV 300. Data record address is interpreted as door address. Response data record DS181 transmitted by IRMA analyzer: CH1 CH2 CH3 DI DRI F P b F CR This type of data record is specified by recommendations VDV 300 under consequent no. 181 (Acknowledgement and identification). Identifier F represents system type Passenger counting. Actions on reception of call-up data record IDS0812: If test function Simulation of Passenger Change is active passenger counters for addressed door and passenger counting results stored in door specific IBIS transmission buffer are cleared. Deactivation of test function Simulation of Passenger Change for addressed door. Transmission of response data record DS181. IBISIP dependencies: Data record pair IDS0812, DS181 is part of test function Simulation of Passenger Change. Protocol flow chart specified for this task has to be considered. Refer to section 3.2 for details.

Page 21 of 31 APC IRMA IV IBIS Protocol Version 1.00, 03/14/2006

2.13

IDS0800

Call-up data record IDS0800 is used for switching to UIRMAIP. There is no response data record assigned to this call-up. Switching to UIRMAIP, default baud rate 38,400bps: Call-up data record IDS0800 transmitted by on-board computer: CH1 CH2 CH3 CH4 CH5 CH6 CH7 CH8 DI DRI DRA PL1 PL2 PL3 PL4 F P H64 b ! I R M A CR This type of data record is not specified by recommendations VDV 300. Data record address is interpreted as device address. Switching to UIRMAIP, required baud rate: Call-up data record IDS0800 transmitted by on-board computer: CH1 CH2 CH3 CH4 CH5 CH6 CH7 CH8 ... CHn-1 CHn DI DRI DRA PL1 PL2 PL3 PL4 PL5 ... PLm F P H64 Z Z b ! I R M A ... CR Minimum value of payload length m: 8 Maximum value of payload length m: 9 This type of data record is not specified by recommendations VDV 300. Data record address is interpreted as device address. Specification of payload PL5PLm: String representing baud rate to be used for UIRMAIP communication, 4 or 5 characters, decimal digits, most significant digit first, permitted baud rate values as specified in section 1.4.4. Actions on reception of call-up data record IDS0800: Reinitialization of asynchronous serial interface of IRMA analyzer (ASC0) for UIRMAIP communication. Activation of watchdog timer with timeout interval 1s. Watchdog timer is deactivated on reception of valid UIRMAIP message. Otherwise IBISIP communication is reestablished at ASC0 after expiration of timeout interval. IBISIP dependencies: IBISIP communication with addressed IRMA analyzer cannot be continued after reception of valid call-up data record IDS0800. IBISIP communication is reestablished on reception of appropriate UIRMAIP command message. Refer to document iris UIRMAIP for details.

Page 22 of 31 APC IRMA IV IBIS Protocol Version 1.00, 03/14/2006

3
3.1
3.1.1

IBISIP Flow Charts


Query of Passenger Counting Results
Query of Passenger Counting Results While Addressed Door is Closed

Query of passenger counting results is done by using data records DS082, DS181, DS083 and DS183. No other types of data records are necessary for this task. However query of IBIS status of door is strongly recommended to enable detection of APC IRMA faults. With respect to queries of passenger counting results there is complete independence among doors no matter if these doors are supported by the same IRMA analyzer or not. As a result queries of passenger counting results for different doors may be nested without restrictions. Additional call-up data records not mentioned in flow charts below may be transmitted by on-board computer at any time without disturbing query of passenger counting results: IDS084, IDS0841, IDS085, IDS087, DS0801, IDS0802, DS080, DS081 On the other hand the following types of call-up data records are not permitted for additional transmission within protocol sequence used for query of passenger counting results: IDS086, IDS0861, IDS0811, IDS0812, IDS0800 Passenger counting results are summed up if not queried by on-board computer between consecutive door open periods. On closing of door counting by IRMA analyzer software is not stopped immediately. Evaluation of sensor signals already sampled is continued until final counting results are determined. This period may be as long as 2s. Availability of final passenger counting results is indicated by IBIS status value 1 within certain IBISIP context. Refer to section 2.3.1 and to flow charts below for more information.

Page 23 of 31 APC IRMA IV IBIS Protocol Version 1.00, 03/14/2006

Default procedure compatible to IRMA III: According to recommendations VDV 300 call-up data record DS082 is transmitted by on-board computer if vehicle starts ride after closing of all doors. Usually 3-km/h criterion is used to trigger DS082 transmission. Of course on-board computer software has to ensure DS082 is not transmitted earlier than 2s after door closing. Query of IBIS status of door is strongly recommended for detection of APC IRMA faults and for verification of passenger counting results being final. Default flow chart: Point in Time 0 x x + 2s 1 2 Door Status open just closed closed closed closed Status of IRMA Analyzer Software counting counting counting finished counting finished counting finished On-Board Computer Call-Up IRMA Analyzer Response

DS082 IDS084 or IDS0841 DS083

DS181 IDS184 or IDS1841 DS183

Apart from minimum delay of 2s for DS082 transmission after door closing there are no other timing requirements for query of passenger counting results. Of course query must be finished with reception of valid response data record DS183 by on-board computer before reopening of door. Queried passenger counting results are valid if IBIS status of door queried within the same protocol sequence is equal to 1. They are invalid in all other cases: IBIS status of door = 0 or = 2: Probably malfunction of according door contact. On-site service required. IBIS status of door = 3: Probably malfunction of at least one cable connecting IRMA sensor(s) with IRMA analyzer. Possible malfunction of IRMA sensor or IRMA analyzer must be considered too. On-site service required. IBIS status of door = 4: Probably at least one IRMA sensor sabotaged. Typically sensor is masked by an opaque material. On-site service required.

Page 24 of 31 APC IRMA IV IBIS Protocol Version 1.00, 03/14/2006

Special flow chart, second query of passenger counting results after door closing: Status of Point in On-Board Computer IRMA Analyzer Door Status IRMA Analyzer Time Call-Up Response Software 0 open counting x just closed counting x + 2s closed counting finished DS082 DS181 1 closed counting finished IDS084 or IDS0841 IDS184 or IDS1841 2 closed counting finished DS083 DS183 3 closed counting finished DS082 DS181 4 closed counting finished IDS084 or IDS0841 IDS184 or IDS1841 5 closed counting finished DS083 DS183 Point in time 1: Response data record IDS184 or IDS1841 contains IBIS status of door equal to 1 provided that there is no malfunction of door contact and no IRMA fault. Point in time 2: Response data record DS183 contains passenger counting results for door open period finished at point in time x. Point in time 4: Response data record IDS184 or IDS1841 contains IBIS status of door equal to 1 provided that there is no malfunction of door contact and no IRMA fault. Point in time 5: Response data record DS183 contains passenger counting results equal to 0.

Page 25 of 31 APC IRMA IV IBIS Protocol Version 1.00, 03/14/2006

Special flow chart, repeated transmission of DS082 before transmission of DS083, repeated transmission of DS083 before transmission of DS082: Status of Point in On-Board Computer IRMA Analyzer Door Status IRMA Analyzer Time Call-Up Response Software 0 open counting x just closed counting x + 2s closed counting finished DS082 DS181 1 closed counting finished DS082 DS181 2 closed counting finished IDS084 or IDS0841 IDS184 or IDS1841 3 closed counting finished DS083 DS183 4 closed counting finished IDS084 or IDS0841 IDS184 or IDS1841 5 closed counting finished DS083 DS183 Point in time 2: Response data record IDS184 or IDS1841 contains IBIS status of door equal to 1 provided that there is no malfunction of door contact and no IRMA fault. Point in time 3: Response data record DS183 contains passenger counting results for door open period finished at point in time x. Point in time 4: Response data record IDS184 or IDS1841 contains IBIS status of door equal to 0 provided that there is no malfunction of door contact and no IRMA fault. Point in time 5: Response data record DS183 contains passenger counting results for door open period finished at point in time x.

Page 26 of 31 APC IRMA IV IBIS Protocol Version 1.00, 03/14/2006

3.1.2

Query of Passenger Counting Results Independently of Door State

In contrast to system generation IRMA III query of passenger counting results may be performed also if addressed door is open. As a result system generation IRMA IV is usable also in cases where closing of doors during riding cannot be guaranteed. Flow chart for single query of passenger counting results independently of door state: Status of Point in On-Board Computer IRMA Analyzer Door Status IRMA Analyzer Time Call-Up Response Software 1 any counting DS082 DS181 2 any counting IDS084 or IDS0841 IDS184 or IDS1841 3 any counting DS083 DS183 Protocol sequence shown above has to be repeated periodically. There is no strict requirement regarding repetition frequency but usage of value near 1Hz is recommended. Passenger counters are cleared on each query. Virtual counting interval is limited by two consecutive queries of passenger counting results. Numbers contained in response data record DS183 received by on-board computer at end of virtual counting interval are equal to counts of passengers boarded and alighted within this interval. IBIS status of door should be checked for being equal to 3 only. Status values 0, 1, 2 and 4 are useless in this context. Remarks: Depending on counting software slight degradation of counting precision may be caused by query of passenger counting results while addressed door is open. This effect is arising if counting software for IRMA sensor class DIST4 uses passenger counter decrements to handle complex situations. Of course there is an underflow protection for passenger counting results so desired decrement is not done if passenger counter is equal to 0. Due to continous query of passenger counting results independently of door state passenger counters are equal to 0 almost all the time. Contact company iris-GmbH to get more information if this matter is of interest.

Page 27 of 31 APC IRMA IV IBIS Protocol Version 1.00, 03/14/2006

3.2

Test Function "Simulation of Passenger Change"

Main usage of this test function is verification of part of on-board computer software related to APC IRMA. Passenger counters used for normal operation are used for test function Simulation of Passenger Change too. As a result simulated passenger counting results may be queried in the same manner as described in section 3.1. If test function is activated passenger counting results are not determined by evaluation of IRMA sensor signals but virtual counting triggered by opening of according door is performed. Additional virtual passenger counters are used for this purpose. With respect to test function Simulation of Passenger Change there is complete independence among doors no matter if these doors are supported by the same IRMA analyzer or not. As a result test function may be activated and used for any selection of doors while normal operation is continued at all other doors. Activation of test function Simulation of Passenger Change: Test function is activated for addressed door on reception of IDS0811 by IRMA analyzer supporting this door. Passenger counters are and virtual passenger counters initialized as described in section 2.11. Actions on door opening: 1. Virtual passenger counters are equal to 0: - Virtual counter of boarding passengers is set to 100, virtual counter of alighting passengers is set to 0. Virtual counter of boarding passengers is equal to 100, virtual counter of alighting passengers is equal to 0: - Virtual counter of boarding passengers is decreased by one , virtual counter of alighting passengers is increased by one. As long as test function is active sum of both counts is equal to 100. 2. Passenger counters are loaded with content of virtual passenger counters. Closing of door does not affect virtual passenger counters. Test function Simulation of Passenger Change activated while addressed door is closed: Passenger counting results Boarding Alighting activation of test function 0 0 st after 1 door opening 100 0 after 2nd door opening 99 1 rd after 3 door opening 98 2 after 99th door opening 2 98 after 100th door opening 1 99 st after 101 door opening 0 100 after 102nd door opening 100 0 rd after 103 door opening 99 1

Page 28 of 31 APC IRMA IV IBIS Protocol Version 1.00, 03/14/2006

Test function Simulation of Passenger Change activated while addressed door is open: Passenger counting results Boarding Alighting 100 0 activation of test function st 99 1 after 1 door reopening 98 2 after 2nd door reopening rd after 3 door reopening 2 98 th 1 99 after 99 door reopening 0 100 after 100th door reopening 100 0 after 101st door reopening 99 1 after 102nd door reopening rd 98 2 after 103 door reopening Deactivation of test function Simulation of Passenger Change: Hardware reset of IRMA analyzer (interruption of power supply for at least 1s). Software reset of IRMA analyzer caused by reception of according UIRMAIP message. Reception of call-up data record IDS0812 with appropriate door address. Remarks: Query of simulated passenger counting results may be conducted without transmission delay for DS082. It is not necessary to wait 2s after door closing to launch query sequence. Test function Simulation of Passenger Change is reinitialized on reception of call-up data record IDS0811 if it is already active.

Page 29 of 31 APC IRMA IV IBIS Protocol Version 1.00, 03/14/2006

3.3

Query and Clearing of IRMA fault type defect

Default procedure of query of passenger counting results as described in section 3.1.1. It is strongly recommended to extend this procedure by query of sensor status and clearing of IRMA fault type if necessary. Extended flow chart for query of passenger counting results: Status of Point in On-Board Computer Door Status IRMA Analyzer Time Call-Up Software 0 open counting X just closed counting x + 2s closed counting finished DS082 1 closed counting finished IDS084 or IDS0841 2 closed counting finished DS083 3 closed counting finished IDS085 4 closed counting finished IDS086 or IDS0861

IRMA Analyzer Response

DS181 IDS184 or IDS1841 DS183 IDS185 DS181

Apart from minimum delay of 2s for DS082 transmission after door closing there are no other timing requirements for query of passenger counting results. Of course query must be completely finished before reopening of door. Query is finished with reception of valid response data record DS181 by on-board computer following IDS086 or IDS0861 call-up. Transmission of call-up data record IDS086 or IDS0861 may be omitted if no IRMA fault type defect is indicated by response data record IDS184 or IDS1841.

Page 30 of 31 APC IRMA IV IBIS Protocol Version 1.00, 03/14/2006

Detection of IRMA faults

Different types of faults are specified for APC IRMA IV supporting IBISIP: defect and sabotaged. Specification of fault types strongly depends on APC IRMA hardware and software design. Specification of sensor fault types is not part of this document. Two different categories of status are used within IBISIP: IBIS status of door and sensor status. Refer to sections 2.3.1 and 2.4 for detailed information. Checking for sensor faults is done according to following table: Sensor fault type sensor defect At the end of start-up sequence Initial checking of IRMA analyzer software independently of door status Periodic checking concurrently Consecutive checking with sensor sampling if according door is open

Sensor fault type sensor sabotaged No initial checking On closing of according door

IBIS status of door is derived from current status of sensors assigned to this door at the end of startup sequence of IRMA analyzer software and on reception of call-up data records IDS084 and IDS0841. Rules for activation and deactivation of sensor faults: Fault type sensor defect has always priority over fault type sensor sabotaged. If conditions for both fault types are fulfilled at the same time, fault type of sensor in question is sensor defect. Activation of fault type sensor defect: At the end of start-up sequence of IRMA analyzer software fault type sensor defect can be activated independently of door status. Afterwards this fault type can be activated for any sensor supported by an IRMA analyzer only if door to which a certain sensor is assigned is open. Deactivation of fault type sensor defect: Fault type sensor defect can be deactivated by the following methods if cause for sensor fault does not longer exists: - Hardware reset of IRMA analyzer (interruption of power supply for at least 1s). - Software reset of IRMA analyzer caused by reception of according UIRMAIP message. - Temporary switching to installation mode using UIRMAIP. - Reception of either call-up data record IDS086 or IDS0861 addressed to door to which a certain sensor is assigned.

Page 31 of 31 APC IRMA IV IBIS Protocol Version 1.00, 03/14/2006

Activation of fault type sensor sabotaged: Fault type sensor sabotaged can be activated immediately after closing of door to which a certain sensor is assigned. Fault type sensor sabotaged is activated if all criteria for sensor sabotage were fulfilled during elapsed door open period. Deactivation of fault type sensor sabotaged: Fault type sensor sabotaged can be deactivated by the following methods if cause for sensor fault does not longer exists: - Hardware reset of IRMA analyzer (interruption of power supply for at least 1s). - Software reset of IRMA analyzer caused by reception of according UIRMAIP message. - Temporary switching to installation mode using UIRMAIP. - Fault type sensor sabotaged is deactivated on opening of door to which a certain sensor is assigned.

Rules listed above apply to values 3 (fault type defect) and 4 (fault type sabotaged) of IBIS status of door too. This is a result of relationship between IBIS status of door and according sensor status as specified in section 2.4.