8.15.2 Read for relative time binary change events; Relative time not supported (revision 3.1r1, subset level 3)

Device under test: Step Function I/O dnp3 outstation

11:01:27.765 Running procedure: 8.15.2
11:01:27.766 This procedure is enabled because the following options:
11:01:27.766 - supports.binaryInput == true
11:01:27.766 - supports.binaryInputChangeEvents == true
11:01:27.766 - supports.binaryInputEventReads == true
11:01:27.766 step: 1
11:01:27.766 - Generate 1 Binary Input Change Event(s)
11:01:27.766 [PLG] Updated BI 0: value=true, flags=81, timestamp=1793185287766 (UNSYNCHRONIZED_TIME)
11:01:27.766 The plugin reports the DUT's clock unsynchronized
11:01:27.766 step: 2
11:01:27.766 - Read(0x01) fir: 1 fin: 1 con: 0 uns: 0 seq: 0x01
11:01:27.766 - g2v3, All Objects
11:01:27.767 --A-> Read(0x01) fir: 1 fin: 1 con: 0 uns: 0 seq: 0x01
11:01:27.767 g2v3, All Objects
11:01:27.767 --T-> fir: 1 fin: 1 seq: 0
11:01:27.767 --L-> master: 1 pri: 1 fcb: 0 fcv: 0 func: UNCONFIRMED_USER_DATA(0x04) 0xC4 length: 11 dest: 1024 src: 1
11:01:27.767 --P-> 05 64 0B C4 00 04 01 00 CA 8A
11:01:27.767 C0 C1 01 02 03 06 3E C6
11:01:27.767 step: 3
11:01:27.767 - Read a single fragment response w/ sequence(0x01)
11:01:27.767 - Verify that the response holds every Binary Input event generated
11:01:27.767 - If the events carry timestamps, verify that the gaps between them match the gaps between when the events were generated, to the Device Profile's resolution
11:01:27.767 - Verify that an application layer confirmation is requested.
11:01:27.767 - Verify that the events are reported as 3.1r1's rules for event reporting require, for a read of g2v3, by the state of the DUT's clock when it recorded them, where the procedure or the plugin knows it
11:01:27.767 - Verify that the flags behave as the note on flags in Section 2 requires (Note 5 in 2.7, Note 6 in 3.1r1).
11:01:27.767 - Confirm each response that asks for a confirmation
11:01:27.767 <-P-- 05 64 1E 44 01 00 00 04 C8 BD
11:01:27.767 C0 E1 81 90 00 33 02 07 01 56 0E 2C 82 A1 01 02 6E 0B
11:01:27.767 03 28 01 00 00 00 81 00 00 9A 2A
11:01:27.767 <-L-- master: 0 pri: 1 fcb: 0 fcv: 0 func: UNCONFIRMED_USER_DATA(0x04) 0x44 length: 30 dest: 1 src: 1024
11:01:27.767 <-T-- fir: 1 fin: 1 seq: 0
11:01:27.768 <-A-- Response(0x81) fir: 1 fin: 1 con: 1 uns: 0 seq: 0x01 IIN(DeviceRestart, NeedTime)
11:01:27.768 g51v2, 1-Byte Count, count: 1
11:01:27.768 time: 1793185287766
11:01:27.768 g2v3, 2-Byte Count and Index, count: 1
11:01:27.768 [0] - flags: 0x81 cto: 0
11:01:27.768 --A-> Confirm(0x00) fir: 1 fin: 1 con: 0 uns: 0 seq: 0x01
11:01:27.768 --T-> fir: 1 fin: 1 seq: 0
11:01:27.768 --L-> master: 1 pri: 1 fcb: 0 fcv: 0 func: UNCONFIRMED_USER_DATA(0x04) 0xC4 length: 8 dest: 1024 src: 1
11:01:27.768 --P-> 05 64 08 C4 00 04 01 00 9A 19
11:01:27.768 C0 C1 00 7D 3D
11:01:27.768 [PLG] Verified 1 binary input point event(s)
11:01:27.768 step: 4
11:01:27.768 - If the response has no binary input events with relative time, no further 8.15 tests apply: 8.15.3 runs only where the DUT records events with time and doesn't reject the read
11:01:27.768 Passed procedure: 8.15.2