A3brGetState doesnt work properly at fast cycletimes

[sclaiborne]

From customer:

When using the A3brGetState fub, I needed to use a cycle time of at least 500 ms. Less than that interfered with other communications. The A3brControl requests would either return error Id 500 or never return done=true and just show busy=true forever.

I have not reproduced locally yet.

[Joshpolansky]

I wonder if the block is misconfigured. There is a cycleTime input (bad name) that determines how often to get an update. Each call is 3 requests, so it can easily be misused. We should probably add a check that the previous calls have finished before sending new requests.