Actions
Feature #5831
closedwork around Falcon3 occasional lost of communication
Status:
Closed
Priority:
Urgent
Assignee:
Category:
-
Target version:
Start date:
06/02/2018
Due date:
% Done:
0%
Estimated time:
Deliverable:
Description
Falcon3 communication is still buggy. It gets some error that we catch and handled with imagedata = None. This is normally a fatal error and we should stop pause and wait for user to check hardware. However, it appears to recover fairly fast. To prevent lost of time while no one can make it continue, we will catch the error and abort the target and move on.
I do hope this is resolve by the manufacturer before 3.4 release.
Updated by Anchi Cheng over 5 years ago
- Status changed from Assigned to Closed
We have not encountered this error for a while now. Consider resolved by manufactor. Therefore, the pause for bad image is reactivated.
Updated by Anchi Cheng about 5 years ago
Falcon3 image server may also have a timeout error which means the image does not come back. It does recover from the error. We allow it to retry in 5714813a6
Actions