It’s possible to go through error stack with SGETERR command and see all the function stack which generate the error. Moreover there is a RealTimeLog with increasing verbosity levels. Both error stack and log file can be retrieved through API calls.

A command can’t be aborted, but every time a failure occour, drivers recover FR2.0 to the initial status.