There was a firmware change on allowing multiple outstanding match operations on the extender in this later release. Waiting for confirmation from Belgium on whether I can post the details.

With regard to Paul's issue. This firmware change was a side-effect that exposed a real bug in his scripting.

s.match(command + '\r',500); was indeed sending command and then waiting a default 250ms (undocumented timeout???) for a string of '500'.

The problem was that the extender was expecting to match on a string of "500" which will never be sent. The code should have issued something like:

s.match(command + '\r',\r',500);

When the timeout was occurring, match operation was not raising a timeout exception but rather attempting to call 'onError' on the serial object (which was not assigned).

Belgium has suggested:

s.match(command + '\r','\r', 0); for an immediate operation and no wait for completion.

If the 500 ms synchronous wait is required, I suggest:

s.match(command + '\r','\r',500);