-
-
Notifications
You must be signed in to change notification settings - Fork 82
ConsecutiveFrameTimeoutError for first consecutive frame #41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Thanks for your quick answer. Yeah, i saw this test. In this case timer_rx_cf is already expired. So, I just have doubts that this is up to the standard (Network layer timing part), |
Sorry I deleted my previous answer at the same time you typed yours. You seems to be correct about this. I will fix. |
Fixed now. Will publish soon. Regards |
Yeah, i see. |
This wasn't completely fixed. |
…flow control without waiting on next CAN msg.
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.
The text was updated successfully, but these errors were encountered: