Nick,
Attached is a screen-grab of the Pulsar settings I have set for use with a CloudWatcher-SOLO and ACP automation.
For daytime testing the CloudWatcher will normally be signalling “Unsafe”, depending on how you’ve configured the CLoudWatcher-SOLO trigger level for “Brightness”, and so if you manually open the shutter in daylight then after the “Delay” time set in the Pulsar configuration has elapsed the shutter will auto-close.
The same conditions will apply at night if any of the CloudWatcher safety thresholds are exceeded with the CloudWatcher-SOLO signalling “Unsafe” and you try and manually open the shutter then after the “Delay” time you configured in the Pulsar configuration has elapsed the shutter will auto-close.
Both the above statements apply when you have the direct hard-wired connection made between the pair of flying wires that exit the CLoudWatcher connecting cable (usually adjacent to the SOLO DB9 input socket) and the safety switch input connector on the bottom of the Pulsar control console.
If you are only using your observatory control application to open and close the shutter according to the CloudWatcher-SOLO’s ASCOM safety driver and don’t use the hardwired connection between the CLoudWatcher-SOLO and the Pulsar control console then in the Pulsar configuration, under Relay Settings, Polarity should be set to “NO” and nothing is plugged into the safety switch socket on the bottom of the Pulsar control console, but this is not a recommended operating setup because you are totally reliant on the observatory management application to tell the Pulsar dome controller to close the shutter and any issues with the management app, or Windows, might prevent that happening therefore it’s vital to use the provided hard-wired safety switch connection between the CloudWatcher-SOLO and the safety switch input on the bottom of the Pulsar control console as a minimum back-up provision in the event that your observatory management app’ or the PC has stopped responding.
HTH
