Increasing wrong character timeout to 30 to fix 'no annoucement' error. #12
+3
−3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I had a sketch reporting 'No announcement from Artemis bootloader'. This occurs when either 1) no chr(127) is received or 2) too many non-chr(127) characters are received. The sketch I was working on transmits a ton of serial data at 115200 constantly. After the Artemis is reset, the python script has more than 10 bytes sitting in the buffer. 30 seems to work well. With a 0.1s timeout, this is 3s total. Increasing to 50 seems overkill.