Wrong sequence id after starting the simulation
dev-gb opened this issue · 0 comments
dev-gb commented
pdu_seq_id is reseted after sending a STC_run. This causes an error in the DCP-Slave implementation. The pdu_seq_id of DAT_input_output should be 326.
Log of the DCPTester:
2019-08-19 16:48:53 DEBUG Pdu was send with content=type_id=STC_run pdu_seq_id=325 receiver=1 start_time=1566226134
2019-08-19 16:48:53 DEBUG Pdu was received with content=type_id=RSP_ack sender=1 resp_seq_id=325
2019-08-19 16:48:53 DEBUG Pdu was received with content=type_id=NTF_state_changed sender=1 state_id=SYNCHRONIZING
2019-08-19 16:48:53 DEBUG Pdu was send with content=type_id=DAT_input_output pdu_seq_id=0 data_id=0 payload=00 00 00 00 ff ff ff ff ff ff ef ff