Closed NogginBops closed 5 years ago
This looks like it is a little bit more complicated as the master could be resending it's request. If the slave is expecting a response there will be some error reading the response back. What really should be done it early filtering of messages based on their ID, and then just reading all data until there is a 3.5T gap. That way there is no need to keep track of the state of the buss. Just respond to the messages meant for the slave and ignore the rest.
Merged changes into snapshot
Oh! Sorry I never fixed my pull-request! Good that you fixed the problems with it 👍
Expected Behavior
The slave should detect that the master request is not destined to the slave. After this the slave should expect there to come a response on the serial line and read it. Otherwise should timeout and expect another request.
Actual Behavior
The slave detects that the message it not for it, and correctly ignores it. But the slave does not expect the response and thinks that this is supposed to be another request. This results in the slave not correctly reading the next request meant for it.
Steps to Reproduce the Problem
Specifications