The timer interval was not being applied to the first scanResponse, which was being sent immediately on receipt of the scanCommand - apparently before the Edison was ready.
If it misses that first scanResponse, the Edison does not receive any subsequent scanResponses. I believe it was a fluke that the Edison ever received a set of scanResponses.
The possibility remains that the simulator does send scanResponses too quickly, however, an interval of 80ms seemed to work during testing, so the interval was increased to 100ms for conservatism's sake.
The timer interval was not being applied to the first scanResponse, which was being sent immediately on receipt of the scanCommand - apparently before the Edison was ready. If it misses that first scanResponse, the Edison does not receive any subsequent scanResponses. I believe it was a fluke that the Edison ever received a set of scanResponses.
The possibility remains that the simulator does send scanResponses too quickly, however, an interval of 80ms seemed to work during testing, so the interval was increased to 100ms for conservatism's sake.
References #161.