ConsecutiveFrameTimeoutError for first consecutive frame

[MaratSabitov]

I found that ConsecutiveFrameTimeoutError was not raised, although, the first consecutive frame was not received after first frame and flow control exchange:
S R
-----First Frame----->
<--- Flow Control----

Is that expected behaviour - that ConsecutiveFrameTimeoutError raises only if consecutive frame receieved with delay.
What if the first consecutive frame will not come at all?
I thought in this case ConsecutiveFrameTimeoutError should be raised.

[MaratSabitov]

Thanks for your quick answer.

Yeah, i saw this test.
And i mean that it should be raised even without incoming CF with index=1 ( line 246),
because stack received first frame, sent flow control and waits consecutive frame/frames, but it was not received on time.

In this case timer_rx_cf is already expired.
And this is checked in process_rx().
But the problem is that this method is called only if message received.
So, timer expired - but need incoming message to trigger the check and raise the exception.

So, I just have doubts that this is up to the standard (Network layer timing part),
that's why i am asking this question.

[pylessard]

Sorry I deleted my previous answer at the same time you typed yours.

You seems to be correct about this. I will fix.

[pylessard]

Fixed now. Will publish soon.
Github seems to have trouble, I am not sure if you get to see my comments.

Regards

[MaratSabitov]

Yeah, i see.
Yesterday i had some troubles with comments.
Thanks.

[pylessard]

This wasn't completely fixed.
Issue still exist and logged with #63