I’m not sure if this is meaningful or just coincidence. I am also not 100% certain what you mean by “choked”. In the logs, the 11th bias frames appears to save to disk fine and then moves on to the next target because the target has an end time specified:
[2016-11-3 23:16:00] [DEBUG] [Sequence Thread] ---------> Save file took 5349ms
[2016-11-3 23:16:01] [DEBUG] [Sequence Thread] Target past specified end time, moving to next target...
All that said, there was an odd PHD2 error during the 11th frame that I do not currently have any good explanation for:
PHD will make several attempts to re-connect the camera.
Other than the obvious, I am not sure entirely what this means. How did the API guider camera become disconnected? Or if it didn’t why does PHD2 think that it did?