The Trace option that you mention is actually in the CloudWatcher ASCOM driver, all SGP is doing is starting the driver setup dialog.
In some way it's a shame that it works like this because it means that the erroneous unsafe events will be difficult to see.
It looks as if the unsafe messages were coming from the driver, even though they don't appear in the driver csv file. Maybe the time taken to write to the trace log is enough to stop something going wrong.
A possibility is that SGP will interpret any error in communicating with the safety device as an unsafe condition. Jared will know if that's the case.
