https://wiki.deepskychile.com/api.php?action=feedcontributions&feedformat=atom&user=Cedric 2026-08-09T07:39:48Z User contributions MediaWiki 1.42.3 https://wiki.deepskychile.com/index.php?title=ACP_SafetyMonitor&diff=122 2025-12-04T11:53:11Z

<p>Cedric: </p> <hr /> <div>This page describes how to install and configure the Deep Sky Chile weather interface for ACP Observatory Control. <br /> This integration allows ACP to use roof state and weather data from your Deep Sky Chile observatory to determine whether observing conditions are safe.<br /> <br /> == Overview ==<br /> <br /> This collection of scripts was written by '''Bob Denny''' for Deep Sky Chile. <br /> It enables ACP to read the weather and roof state of your Deep Sky Chile observatory and map it to ACP’s internal '''Weather Safety Monitor'''.<br /> <br /> When the roof of your selected observatory is open, ACP will show weather as safe. <br /> When the roof is closed, ACP will show unsafe weather.<br /> <br /> == Download ==<br /> <br /> You will receive a ZIP file containing several scripts:<br /> <br /> * &lt;code&gt;DeepSkyChileWeather_obs1.wsc&lt;/code&gt; <br /> * &lt;code&gt;DeepSkyChileWeather_obs2.wsc&lt;/code&gt; <br /> * &lt;code&gt;DeepSkyChileWeather_obs3.wsc&lt;/code&gt; <br /> * (and others depending on the number of observatories)<br /> <br /> Select your observatory’s script — for example: <br /> '''Select the script corresponding to your observatory (obs1, obs2, obs3, etc.).'''<br /> <br /> == Installation ==<br /> <br /> You must install and register the &lt;code&gt;.wsc&lt;/code&gt; component so that ACP can load it.<br /> <br /> === 1. Copy the script ===<br /> <br /> Place the correct &lt;code&gt;DeepSkyChileWeather_obsX.wsc&lt;/code&gt; file in a suitable folder. <br /> The recommended location is:<br /> <br /> &lt;code&gt;C:\Program Files (x86)\ACP Obs Control\Weather Components&lt;/code&gt;<br /> <br /> Administration rights may be required.<br /> <br /> === 2. Register the component ===<br /> <br /> These steps assume a 64-bit Windows system with UAC enabled.<br /> <br /> # Locate: &lt;code&gt;C:\Windows\SysWOW64\cmd.exe&lt;/code&gt; <br /> # Right-click → '''Run as Administrator'''<br /> # In the admin command prompt, enter:<br /> <br /> &lt;code&gt;CD &quot;\Program Files (x86)\ACP Obs Control\Weather Components&quot;&lt;/code&gt;<br /> <br /> Then register the component:<br /> <br /> &lt;code&gt;regsvr32 DeepSkyChileWeather.wsc&lt;/code&gt;<br /> <br /> You should see a success message popup.<br /> <br /> Close the command window when done.<br /> <br /> == ACP Configuration ==<br /> <br /> # Open ACP.<br /> # Go to: '''Weather → Setup'''<br /> # Set:<br /> <br /> '''Object ID:''' &lt;code&gt;ACP.DSCWeather&lt;/code&gt;<br /> <br /> # Click: '''Setup Weather Server…'''<br /> <br /> If everything is correct, ACP will display a popup indicating the weather server is ready.<br /> <br /> Close ACP Preferences.<br /> <br /> == Connecting to the Weather Server ==<br /> <br /> In ACP:<br /> <br /> # Open the '''Weather''' menu.<br /> # Click '''Connect'''.<br /> <br /> If the roof of your selected Deep Sky Chile observatory is open, ACP should show:<br /> <br /> * Green **WEA** indicator <br /> * Weather status: **Safe**<br /> <br /> If the roof is closed or the API is unreachable, ACP will show unsafe weather.<br /> <br /> == Logs and Troubleshooting ==<br /> <br /> If something does not work:<br /> <br /> A detailed trace log is written to:<br /> <br /> &lt;code&gt;My Documents\ACP Astronomy\Logs\DSC_WeatherTrace.log&lt;/code&gt;<br /> <br /> Check this file for:<br /> <br /> * API connectivity issues <br /> * Wrong observatory script used <br /> * Communication timeouts <br /> * Invalid or missing data <br /> <br /> If ACP cannot retrieve data from the Deep Sky Chile weather API, weather will automatically be marked as '''unsafe'''.<br /> <br /> == Notes ==<br /> <br /> * Registration is required **only once** during installation. <br /> * If you change observatories, install the correct &lt;code&gt;.wsc&lt;/code&gt; file and re-register it. <br /> * Weather safety in ACP depends entirely on the data returned by the Deep Sky Chile servers.<br /> <br /> [[Category:User manuals]]</div>

Cedric https://wiki.deepskychile.com/index.php?title=ACP_SafetyMonitor&diff=121 2025-12-04T11:51:53Z

<p>Cedric: Created page with &quot;This page describes how to install and configure the Deep Sky Chile weather interface for ACP Observatory Control. This integration allows ACP to use roof state and weather data from your Deep Sky Chile observatory to determine whether observing conditions are safe. == Overview == This collection of scripts was written by &#039;&#039;&#039;Bob Denny&#039;&#039;&#039; for Deep Sky Chile. It enables ACP to read the weather and roof state of your Deep Sky Chile observatory and map it to ACP’s in...&quot;</p> <hr /> <div>This page describes how to install and configure the Deep Sky Chile weather interface for ACP Observatory Control. <br /> This integration allows ACP to use roof state and weather data from your Deep Sky Chile observatory to determine whether observing conditions are safe.<br /> <br /> == Overview ==<br /> <br /> This collection of scripts was written by '''Bob Denny''' for Deep Sky Chile. <br /> It enables ACP to read the weather and roof state of your Deep Sky Chile observatory and map it to ACP’s internal '''Weather Safety Monitor'''.<br /> <br /> When the roof of your selected observatory is open, ACP will show weather as safe. <br /> When the roof is closed, ACP will show unsafe weather.<br /> <br /> == Download ==<br /> <br /> You will receive a ZIP file containing several scripts:<br /> <br /> * &lt;code&gt;DeepSkyChileWeather_obs1.wsc&lt;/code&gt; <br /> * &lt;code&gt;DeepSkyChileWeather_obs2.wsc&lt;/code&gt; <br /> * &lt;code&gt;DeepSkyChileWeather_obs32.wsc&lt;/code&gt; <br /> * (and others depending on the number of observatories)<br /> <br /> Select your observatory’s script — for example: <br /> '''Select the script corresponding to your observatory (obs1, obs2, obs32, etc.).'''<br /> <br /> == Installation ==<br /> <br /> You must install and register the &lt;code&gt;.wsc&lt;/code&gt; component so that ACP can load it.<br /> <br /> === 1. Copy the script ===<br /> <br /> Place the correct &lt;code&gt;DeepSkyChileWeather_obsX.wsc&lt;/code&gt; file in a suitable folder. <br /> The recommended location is:<br /> <br /> &lt;code&gt;C:\Program Files (x86)\ACP Obs Control\Weather Components&lt;/code&gt;<br /> <br /> Administration rights may be required.<br /> <br /> === 2. Register the component ===<br /> <br /> These steps assume a 64-bit Windows system with UAC enabled.<br /> <br /> # Locate: &lt;code&gt;C:\Windows\SysWOW64\cmd.exe&lt;/code&gt; <br /> # Right-click → '''Run as Administrator'''<br /> # In the admin command prompt, enter:<br /> <br /> &lt;code&gt;CD &quot;\Program Files (x86)\ACP Obs Control\Weather Components&quot;&lt;/code&gt;<br /> <br /> Then register the component:<br /> <br /> &lt;code&gt;regsvr32 DeepSkyChileWeather.wsc&lt;/code&gt;<br /> <br /> You should see a success message popup.<br /> <br /> Close the command window when done.<br /> <br /> == ACP Configuration ==<br /> <br /> # Open ACP.<br /> # Go to: '''Weather → Setup'''<br /> # Set:<br /> <br /> '''Object ID:''' &lt;code&gt;ACP.DSCWeather&lt;/code&gt;<br /> <br /> # Click: '''Setup Weather Server…'''<br /> <br /> If everything is correct, ACP will display a popup indicating the weather server is ready.<br /> <br /> Close ACP Preferences.<br /> <br /> == Connecting to the Weather Server ==<br /> <br /> In ACP:<br /> <br /> # Open the '''Weather''' menu.<br /> # Click '''Connect'''.<br /> <br /> If the roof of your selected Deep Sky Chile observatory is open, ACP should show:<br /> <br /> * Green **WEA** indicator <br /> * Weather status: **Safe**<br /> <br /> If the roof is closed or the API is unreachable, ACP will show unsafe weather.<br /> <br /> == Logs and Troubleshooting ==<br /> <br /> If something does not work:<br /> <br /> A detailed trace log is written to:<br /> <br /> &lt;code&gt;My Documents\ACP Astronomy\Logs\DSC_WeatherTrace.log&lt;/code&gt;<br /> <br /> Check this file for:<br /> <br /> * API connectivity issues <br /> * Wrong observatory script used <br /> * Communication timeouts <br /> * Invalid or missing data <br /> <br /> If ACP cannot retrieve data from the Deep Sky Chile weather API, weather will automatically be marked as '''unsafe'''.<br /> <br /> == Notes ==<br /> <br /> * Registration is required **only once** during installation. <br /> * If you change observatories, install the correct &lt;code&gt;.wsc&lt;/code&gt; file and re-register it. <br /> * Weather safety in ACP depends entirely on the data returned by the Deep Sky Chile servers.<br /> <br /> [[Category:User manuals]]</div>

Cedric https://wiki.deepskychile.com/index.php?title=ASCOM_SafetyMonitor&diff=120 2025-12-04T11:48:40Z

<p>Cedric: </p> <hr /> <div>This page describes the '''Deep Sky Chile Safety Monitor''' ASCOM driver.<br /> <br /> It reads the roof state of a selected observatory via the Deep Sky Chile API and exposes it as the ASCOM &lt;code&gt;SafetyMonitor&lt;/code&gt; property &lt;code&gt;IsSafe&lt;/code&gt;.<br /> <br /> See also: [[ASCOM_ObservingConditions|Deep Sky Chile Observing Conditions (ASCOM driver)]]<br /> <br /> == Overview ==<br /> <br /> The '''Deep Sky Chile Safety Monitor''' is an ASCOM-compliant driver that exposes the '''safety status''' of Deep Sky Chile observatories.<br /> <br /> It converts the roof state into the standard ASCOM &lt;code&gt;IsSafe&lt;/code&gt; value:<br /> <br /> * '''Roof open''' → &lt;code&gt;IsSafe = True&lt;/code&gt; <br /> * '''Roof closed''' → &lt;code&gt;IsSafe = False&lt;/code&gt; <br /> <br /> This driver is intended for remote observatory automation systems that rely on an ASCOM SafetyMonitor to decide whether it is safe to operate equipment.<br /> <br /> == Features ==<br /> <br /> * ASCOM &lt;code&gt;SafetyMonitor&lt;/code&gt; implementation <br /> * Periodic polling of the Deep Sky Chile observatories API <br /> * Observatory selection via dropdown list <br /> * Roof-state-to-safety mapping <br /> * Stale-data protection <br /> * Optional trace logging <br /> * Configurable fail-safe mode<br /> <br /> == How it works ==<br /> <br /> The driver periodically queries the API endpoint:<br /> <br /> * &lt;code&gt;http://api.deepskychile.com/observatories&lt;/code&gt;<br /> <br /> On each poll it:<br /> <br /> # Retrieves the list of observatories from the API.<br /> # Identifies the '''selected observatory''' (configured in the Setup dialog).<br /> # Reads its &lt;code&gt;roofState&lt;/code&gt; value (typically &lt;code&gt;open&lt;/code&gt; or &lt;code&gt;closed&lt;/code&gt;).<br /> # Converts this into an ASCOM &lt;code&gt;IsSafe&lt;/code&gt; boolean:<br /> #* Roof open → safe <br /> #* Roof closed → unsafe<br /> # Applies stale-data protection logic.<br /> # Exposes &lt;code&gt;IsSafe&lt;/code&gt; to any ASCOM client application.<br /> <br /> == Requirements ==<br /> <br /> To use this driver you need:<br /> <br /> * A Windows PC <br /> * The '''ASCOM Platform 7.1 or later''' installed <br /> * An internet connection to reach the Deep Sky Chile API <br /> * Client software that supports ASCOM &lt;code&gt;SafetyMonitor&lt;/code&gt; devices (for example N.I.N.A., Voyager, etc.)<br /> <br /> == Installation ==<br /> <br /> # Download and run the driver installer from your Deep Sky Chile customer area.<br /> # The installer will:<br /> #* Copy the driver files to your system<br /> #* Register the COM driver with ASCOM<br /> #* Create the necessary ASCOM profile entries<br /> <br /> After installation, the driver appears in the ASCOM chooser as '''Deep Sky Chile Safety Monitor''' (or similar).<br /> <br /> == Configuration ==<br /> <br /> Open the '''Setup''' dialog from any ASCOM-compatible application (via the ASCOM chooser → '''Properties''' / '''Setup''').<br /> <br /> You can configure:<br /> <br /> '''API URL'''<br /> <br /> * Default: &lt;code&gt;http://api.deepskychile.com/observatories&lt;/code&gt; <br /> * Change this only if instructed by Deep Sky Chile.<br /> <br /> '''Observatory selection'''<br /> <br /> * A dropdown list shows the available observatories returned by the API. <br /> * Select your observatory from the list. The roof state of the selected observatory will determine the value of &lt;code&gt;IsSafe&lt;/code&gt;.<br /> <br /> '''Polling interval'''<br /> <br /> * Defines how often the driver polls the API. <br /> * Choose a value that balances responsiveness with network load.<br /> <br /> '''Stale-data multiplier'''<br /> <br /> * Protects against using outdated information. <br /> * If the data is older than &lt;code&gt;multiplier × polling interval&lt;/code&gt;, it can be treated as stale.<br /> <br /> '''Fail-safe mode'''<br /> <br /> * Defines the default &lt;code&gt;IsSafe&lt;/code&gt; value if:<br /> * The API is unreachable, or <br /> * Data is stale or invalid.<br /> * Typical setting:<br /> ** Fail-safe to '''unsafe''' (&lt;code&gt;IsSafe = False&lt;/code&gt;) for maximum safety.<br /> <br /> '''Trace logging'''<br /> <br /> * When enabled, the driver logs detailed operations and any errors.<br /> <br /> Trace logs are stored in:<br /> <br /> * &lt;code&gt;Documents\ASCOM\Logs&lt;/code&gt;<br /> <br /> == Usage with automation software ==<br /> <br /> Example workflow with N.I.N.A. or similar software:<br /> <br /> # Open the application.<br /> # For the '''Safety Monitor''' (or equivalent) device:<br /> #* Open the ASCOM chooser.<br /> #* Select '''Deep Sky Chile Safety Monitor'''.<br /> #* Click '''Properties''' / '''Setup''' to configure API URL, observatory, polling, etc.<br /> #* Connect to the driver.<br /> <br /> Once connected:<br /> <br /> * The application can read &lt;code&gt;IsSafe&lt;/code&gt; from the driver. <br /> * Roof open → &lt;code&gt;IsSafe = True&lt;/code&gt; → automation may start or continue imaging (depending on your rules). <br /> * Roof closed → &lt;code&gt;IsSafe = False&lt;/code&gt; → automation can park the mount, close sessions, etc.<br /> <br /> Always configure your automation software so that '''&lt;code&gt;IsSafe = False&lt;/code&gt; triggers protective actions'''.<br /> <br /> == Logging and troubleshooting ==<br /> <br /> If something does not work as expected:<br /> <br /> # Enable '''trace logging''' in the Setup dialog.<br /> # Reproduce the issue (connection error, wrong safety state, etc.).<br /> # Check the log files in:<br /> #* &lt;code&gt;Documents\ASCOM\Logs&lt;/code&gt;<br /> <br /> Things to verify:<br /> <br /> * Is the correct observatory selected in the Setup dialog? <br /> * Is the polling interval reasonable? <br /> * Is the fail-safe mode set to the desired behaviour if the API is down?<br /> <br /> == Uninstallation ==<br /> <br /> To uninstall the driver:<br /> <br /> # Open '''Windows Settings → Apps''' (or '''Control Panel → Programs and Features''').<br /> # Find '''Deep Sky Chile Safety Monitor''' in the list.<br /> # Click '''Uninstall'''.<br /> <br /> The uninstaller removes all related files and registry entries.<br /> <br /> == Support ==<br /> <br /> For help, contact:<br /> <br /> * '''Cédric Thomas''' <br /> * E-mail: &lt;code&gt;cedric@deepskychile.com&lt;/code&gt;<br /> <br /> == Disclaimer ==<br /> <br /> This driver depends entirely on the '''Deep Sky Chile API''' for the roof and safety information.<br /> <br /> It must not be your only safety measure. Always implement additional, independent safety systems (hardware interlocks, local weather sensors, etc.).<br /> <br /> <br /> [[Category:User manuals]]</div>

Cedric https://wiki.deepskychile.com/index.php?title=ASCOM_ObservingConditions&diff=119 2025-12-04T11:47:58Z

<p>Cedric: </p> <hr /> <div>This page describes the '''Deep Sky Chile Observing Conditions''' ASCOM driver.<br /> <br /> It exposes real-time weather and seeing data from the Deep Sky Chile site through the standard ASCOM &lt;code&gt;ObservingConditions&lt;/code&gt; interface, so that automation software (N.I.N.A., Voyager, SGP, etc.) can use it for monitoring and safety decisions.<br /> <br /> See also: [[ASCOM_SafetyMonitor|Deep Sky Chile Safety Monitor (ASCOM driver)]]<br /> <br /> == Overview ==<br /> <br /> The '''Deep Sky Chile Observing Conditions''' driver is an ASCOM-compliant driver that publishes:<br /> <br /> * Ambient and sky conditions (temperature, humidity, wind, rain…)<br /> * Seeing and sky quality<br /> * Cloud and rain status converted to standard ASCOM fields<br /> <br /> It retrieves meteorological data from the Deep Sky Chile API and maps it to ASCOM &lt;code&gt;ObservingConditions&lt;/code&gt; properties used by most automation software. <br /> This driver is intended for '''remote observatory automation''', to help you make safe decisions about starting, stopping and continuing imaging sessions.<br /> <br /> == Features ==<br /> <br /> '''Supported sensors'''<br /> <br /> * '''Temperature'''<br /> * '''Humidity'''<br /> * '''Dew point'''<br /> * '''Wind speed''' and '''wind gust'''<br /> * '''Seeing''' (star FWHM)<br /> * '''Sky quality''' (NSB)<br /> * '''Sky temperature'''<br /> * '''Cloud cover'''<br /> * '''Rain rate'''<br /> <br /> '''Other key features'''<br /> <br /> * Periodic polling of the Deep Sky Chile weather API<br /> * Conversion of raw values into standard ASCOM properties<br /> * Stale-data protection with a configurable time multiplier<br /> * Optional detailed trace logging for troubleshooting<br /> <br /> == How it works ==<br /> <br /> The driver periodically queries the Deep Sky Chile weather API (default endpoint):<br /> <br /> * &lt;code&gt;http://api.deepskychile.com/weather&lt;/code&gt;<br /> <br /> On each poll it:<br /> <br /> # Retrieves the JSON weather data over HTTP (TLS 1.2 secured)<br /> # Extracts the relevant sensor values (temperature, humidity, seeing, etc.)<br /> # Converts cloud and rain status into ASCOM-compatible percentage / rate values<br /> # Verifies that the data is not stale (based on the configured multiplier)<br /> # Exposes everything through the ASCOM &lt;code&gt;ObservingConditions&lt;/code&gt; interface<br /> <br /> == Requirements ==<br /> <br /> To use this driver you need:<br /> <br /> * A Windows PC <br /> * The '''ASCOM Platform 7.1 or later''' installed <br /> * An internet connection to reach the Deep Sky Chile API <br /> * Compatible client software (for example N.I.N.A., Voyager, SGP, …)<br /> <br /> == Installation ==<br /> <br /> # Download and run the driver installer from your Deep Sky Chile customer area.<br /> # The installer will:<br /> #* Copy the driver files to your system<br /> #* Register the COM driver with ASCOM<br /> #* Add the required ASCOM profile entries<br /> <br /> Once installed, the driver appears in the ASCOM chooser as '''Deep Sky Chile Observing Conditions''' (or similar).<br /> <br /> == Configuration ==<br /> <br /> You configure the driver via its '''Setup''' dialog, accessible from any ASCOM-compatible application.<br /> <br /> '''API URL endpoint'''<br /> <br /> * Default: &lt;code&gt;http://api.deepskychile.com/weather&lt;/code&gt; <br /> * Change this only if instructed by Deep Sky Chile.<br /> <br /> '''Polling interval (seconds)'''<br /> <br /> * Defines how often the driver queries the API. <br /> * Shorter intervals give fresher data but generate more network traffic.<br /> <br /> '''Stale data multiplier'''<br /> <br /> * Protects against using old data. <br /> * If the last update is older than &lt;code&gt;multiplier × polling interval&lt;/code&gt;, the driver can treat the data as stale.<br /> <br /> '''Trace logging'''<br /> <br /> * When enabled, the driver writes a detailed log of its activity.<br /> <br /> Trace logs are stored in:<br /> <br /> * &lt;code&gt;Documents\ASCOM\Logs&lt;/code&gt;<br /> <br /> == Usage with automation software ==<br /> <br /> A typical usage pattern:<br /> <br /> # Open your automation software (for example N.I.N.A., Voyager, SGP).<br /> # In the '''Weather''' (or equivalent) device selection:<br /> #* Open the ASCOM chooser.<br /> #* Select '''Deep Sky Chile Observing Conditions'''.<br /> #* Click '''Properties''' (or '''Setup''') to configure API URL, polling interval, etc.<br /> #* Confirm and connect.<br /> <br /> Once connected, your software can read:<br /> <br /> * Temperature, humidity, dew point <br /> * Wind speed and gusts <br /> * Cloud cover and rain rate <br /> * Seeing and sky quality <br /> * Sky temperature <br /> <br /> These values can then be used to drive safety limits, session start/stop rules and observing plans.<br /> <br /> == Logging and troubleshooting ==<br /> <br /> If you encounter issues:<br /> <br /> # Enable '''trace logging''' in the Setup dialog.<br /> # Reproduce the problem (for example connection error, missing data).<br /> # Check the latest log files in:<br /> #* &lt;code&gt;Documents\ASCOM\Logs&lt;/code&gt;<br /> <br /> Typical checks:<br /> <br /> * Is the API URL correct? <br /> * Is the polling interval reasonable (not too short or too long)? <br /> * Is the system time on the PC correct (for stale-data calculations)?<br /> <br /> == Uninstallation ==<br /> <br /> To remove the driver:<br /> <br /> # Open '''Windows Settings → Apps''' (or '''Control Panel → Programs and Features''').<br /> # Locate '''Deep Sky Chile Observing Conditions'''.<br /> # Click '''Uninstall'''.<br /> <br /> The uninstaller removes all installed files and related registry entries.<br /> <br /> == Support ==<br /> <br /> For help, contact:<br /> <br /> * '''Cédric Thomas''' <br /> * E-mail: &lt;code&gt;cedric@deepskychile.com&lt;/code&gt;<br /> <br /> == Disclaimer ==<br /> <br /> This driver relies entirely on the '''Deep Sky Chile API''' for its data.<br /> <br /> Always use redundant safety systems in remote observatories. This driver is intended as an information source and must not be your only line of defence.<br /> <br /> <br /> [[Category:User manuals]]</div>

Cedric https://wiki.deepskychile.com/index.php?title=ASCOM_SafetyMonitor&diff=118 2025-12-04T11:45:21Z

<p>Cedric: </p> <hr /> <div>This page describes the '''Deep Sky Chile Safety Monitor''' ASCOM driver.<br /> <br /> It reads the roof state of a selected observatory via the Deep Sky Chile API and exposes it as the ASCOM &lt;code&gt;SafetyMonitor&lt;/code&gt; property &lt;code&gt;IsSafe&lt;/code&gt;.<br /> <br /> See also: [[ASCOM_ObservingConditions|Deep Sky Chile Observing Conditions (ASCOM driver)]]<br /> <br /> == Overview ==<br /> <br /> The '''Deep Sky Chile Safety Monitor''' is an ASCOM-compliant driver that exposes the '''safety status''' of Deep Sky Chile observatories.<br /> <br /> It converts the roof state into the standard ASCOM &lt;code&gt;IsSafe&lt;/code&gt; value:<br /> <br /> * '''Roof open''' → &lt;code&gt;IsSafe = True&lt;/code&gt; <br /> * '''Roof closed''' → &lt;code&gt;IsSafe = False&lt;/code&gt; <br /> <br /> This driver is intended for remote observatory automation systems that rely on an ASCOM SafetyMonitor to decide whether it is safe to operate equipment.<br /> <br /> == Features ==<br /> <br /> * ASCOM &lt;code&gt;SafetyMonitor&lt;/code&gt; implementation <br /> * Periodic polling of the Deep Sky Chile observatories API <br /> * Observatory selection via dropdown list <br /> * Roof-state-to-safety mapping <br /> * Stale-data protection <br /> * Optional trace logging <br /> * Configurable fail-safe mode<br /> <br /> == How it works ==<br /> <br /> The driver periodically queries the API endpoint:<br /> <br /> * &lt;code&gt;http://api.deepskychile.com/observatories&lt;/code&gt;<br /> <br /> On each poll it:<br /> <br /> # Retrieves the list of observatories from the API.<br /> # Identifies the '''selected observatory''' (configured in the Setup dialog).<br /> # Reads its &lt;code&gt;roofState&lt;/code&gt; value (typically &lt;code&gt;open&lt;/code&gt; or &lt;code&gt;closed&lt;/code&gt;).<br /> # Converts this into an ASCOM &lt;code&gt;IsSafe&lt;/code&gt; boolean:<br /> #* Roof open → safe <br /> #* Roof closed → unsafe<br /> # Applies stale-data protection logic.<br /> # Exposes &lt;code&gt;IsSafe&lt;/code&gt; to any ASCOM client application.<br /> <br /> == Requirements ==<br /> <br /> To use this driver you need:<br /> <br /> * A Windows PC <br /> * The '''ASCOM Platform 7.1 or later''' installed <br /> * An internet connection to reach the Deep Sky Chile API <br /> * Client software that supports ASCOM &lt;code&gt;SafetyMonitor&lt;/code&gt; devices (for example N.I.N.A., Voyager, etc.)<br /> <br /> == Installation ==<br /> <br /> # Download and run the driver installer from your Deep Sky Chile customer area.<br /> # The installer will:<br /> #* Copy the driver files to your system<br /> #* Register the COM driver with ASCOM<br /> #* Create the necessary ASCOM profile entries<br /> <br /> After installation, the driver appears in the ASCOM chooser as '''Deep Sky Chile Safety Monitor''' (or similar).<br /> <br /> == Configuration ==<br /> <br /> Open the '''Setup''' dialog from any ASCOM-compatible application (via the ASCOM chooser → '''Properties''' / '''Setup''').<br /> <br /> You can configure:<br /> <br /> '''API URL'''<br /> <br /> * Default: &lt;code&gt;http://api.deepskychile.com/observatories&lt;/code&gt; <br /> * Change this only if instructed by Deep Sky Chile.<br /> <br /> '''Observatory selection'''<br /> <br /> * A dropdown list shows the available observatories returned by the API. <br /> * Select your observatory from the list. The roof state of the selected observatory will determine the value of &lt;code&gt;IsSafe&lt;/code&gt;.<br /> <br /> '''Polling interval'''<br /> <br /> * Defines how often the driver polls the API. <br /> * Choose a value that balances responsiveness with network load.<br /> <br /> '''Stale-data multiplier'''<br /> <br /> * Protects against using outdated information. <br /> * If the data is older than &lt;code&gt;multiplier × polling interval&lt;/code&gt;, it can be treated as stale.<br /> <br /> '''Fail-safe mode'''<br /> <br /> * Defines the default &lt;code&gt;IsSafe&lt;/code&gt; value if:<br /> * The API is unreachable, or <br /> * Data is stale or invalid.<br /> * Typical setting:<br /> ** Fail-safe to '''unsafe''' (&lt;code&gt;IsSafe = False&lt;/code&gt;) for maximum safety.<br /> <br /> '''Trace logging'''<br /> <br /> * When enabled, the driver logs detailed operations and any errors.<br /> <br /> Trace logs are stored in:<br /> <br /> * &lt;code&gt;Documents\ASCOM\Logs&lt;/code&gt;<br /> <br /> == Usage with automation software ==<br /> <br /> Example workflow with N.I.N.A. or similar software:<br /> <br /> # Open the application.<br /> # For the '''Safety Monitor''' (or equivalent) device:<br /> #* Open the ASCOM chooser.<br /> #* Select '''Deep Sky Chile Safety Monitor'''.<br /> #* Click '''Properties''' / '''Setup''' to configure API URL, observatory, polling, etc.<br /> #* Connect to the driver.<br /> <br /> Once connected:<br /> <br /> * The application can read &lt;code&gt;IsSafe&lt;/code&gt; from the driver. <br /> * Roof open → &lt;code&gt;IsSafe = True&lt;/code&gt; → automation may start or continue imaging (depending on your rules). <br /> * Roof closed → &lt;code&gt;IsSafe = False&lt;/code&gt; → automation can park the mount, close sessions, etc.<br /> <br /> Always configure your automation software so that '''&lt;code&gt;IsSafe = False&lt;/code&gt; triggers protective actions'''.<br /> <br /> == Logging and troubleshooting ==<br /> <br /> If something does not work as expected:<br /> <br /> # Enable '''trace logging''' in the Setup dialog.<br /> # Reproduce the issue (connection error, wrong safety state, etc.).<br /> # Check the log files in:<br /> #* &lt;code&gt;Documents\ASCOM\Logs&lt;/code&gt;<br /> <br /> Things to verify:<br /> <br /> * Can your PC reach the API URL in a web browser? <br /> * Is the correct observatory selected in the Setup dialog? <br /> * Is the polling interval reasonable? <br /> * Is the fail-safe mode set to the desired behaviour if the API is down?<br /> <br /> == Uninstallation ==<br /> <br /> To uninstall the driver:<br /> <br /> # Open '''Windows Settings → Apps''' (or '''Control Panel → Programs and Features''').<br /> # Find '''Deep Sky Chile Safety Monitor''' in the list.<br /> # Click '''Uninstall'''.<br /> <br /> The uninstaller removes all related files and registry entries.<br /> <br /> == Support ==<br /> <br /> For help, contact:<br /> <br /> * '''Cédric Thomas''' <br /> * E-mail: &lt;code&gt;cedric@deepskychile.com&lt;/code&gt;<br /> <br /> == Disclaimer ==<br /> <br /> This driver depends entirely on the '''Deep Sky Chile API''' for the roof and safety information.<br /> <br /> It must not be your only safety measure. Always implement additional, independent safety systems (hardware interlocks, local weather sensors, etc.).<br /> <br /> <br /> [[Category:User manuals]]</div>

Cedric https://wiki.deepskychile.com/index.php?title=ASCOM_SafetyMonitor&diff=117 2025-12-04T11:43:52Z

<p>Cedric: </p> <hr /> <div>This page describes the '''Deep Sky Chile Safety Monitor''' ASCOM driver.<br /> <br /> It reads the roof state of a selected observatory via the Deep Sky Chile API and exposes it as the ASCOM &lt;code&gt;SafetyMonitor&lt;/code&gt; property &lt;code&gt;IsSafe&lt;/code&gt;.<br /> <br /> See also: [[ASCOM_ObservingConditions|Deep Sky Chile Observing Conditions (ASCOM driver)]]<br /> <br /> == Overview ==<br /> <br /> The '''Deep Sky Chile Safety Monitor''' is an ASCOM-compliant driver that exposes the '''safety status''' of Deep Sky Chile observatories.<br /> <br /> It converts the roof state into the standard ASCOM &lt;code&gt;IsSafe&lt;/code&gt; value:<br /> <br /> * '''Roof open''' → &lt;code&gt;IsSafe = True&lt;/code&gt; <br /> * '''Roof closed''' → &lt;code&gt;IsSafe = False&lt;/code&gt; <br /> <br /> This driver is intended for remote observatory automation systems that rely on an ASCOM SafetyMonitor to decide whether it is safe to operate equipment.<br /> <br /> == Features ==<br /> <br /> * ASCOM &lt;code&gt;SafetyMonitor&lt;/code&gt; implementation <br /> * Periodic polling of the Deep Sky Chile observatories API <br /> * Observatory selection via dropdown list <br /> * Roof-state-to-safety mapping <br /> * Stale-data protection <br /> * Optional trace logging <br /> * Configurable fail-safe mode<br /> <br /> == How it works ==<br /> <br /> The driver periodically queries the API endpoint:<br /> <br /> * &lt;code&gt;http://api.deepskychile.com/observatories&lt;/code&gt;<br /> <br /> On each poll it:<br /> <br /> # Retrieves the list of observatories from the API.<br /> # Identifies the '''selected observatory''' (configured in the Setup dialog).<br /> # Reads its &lt;code&gt;roofState&lt;/code&gt; value (typically &lt;code&gt;open&lt;/code&gt; or &lt;code&gt;closed&lt;/code&gt;).<br /> # Converts this into an ASCOM &lt;code&gt;IsSafe&lt;/code&gt; boolean:<br /> #* Roof open → safe <br /> #* Roof closed → unsafe<br /> # Applies stale-data protection logic.<br /> # Exposes &lt;code&gt;IsSafe&lt;/code&gt; to any ASCOM client application.<br /> <br /> == Requirements ==<br /> <br /> To use this driver you need:<br /> <br /> * A Windows PC <br /> * The '''ASCOM Platform 7.1 or later''' installed <br /> * An internet connection to reach the Deep Sky Chile API <br /> * Client software that supports ASCOM &lt;code&gt;SafetyMonitor&lt;/code&gt; devices (for example N.I.N.A., Voyager, etc.)<br /> <br /> == Installation ==<br /> <br /> # Download and run the driver installer from your Deep Sky Chile customer area.<br /> # The installer will:<br /> #* Copy the driver files to your system<br /> #* Register the COM driver with ASCOM<br /> #* Create the necessary ASCOM profile entries<br /> <br /> After installation, the driver appears in the ASCOM chooser as '''Deep Sky Chile Safety Monitor''' (or similar).<br /> <br /> == Configuration ==<br /> <br /> Open the '''Setup''' dialog from any ASCOM-compatible application (via the ASCOM chooser → '''Properties''' / '''Setup''').<br /> <br /> You can configure:<br /> <br /> '''API URL'''<br /> <br /> * Default: &lt;code&gt;http://api.deepskychile.com/observatories&lt;/code&gt; <br /> * Change this only if instructed by Deep Sky Chile.<br /> <br /> '''Observatory selection'''<br /> <br /> * A dropdown list shows the available observatories returned by the API. <br /> * Select your observatory from the list. The roof state of the selected observatory will determine the value of &lt;code&gt;IsSafe&lt;/code&gt;.<br /> <br /> '''Polling interval'''<br /> <br /> * Defines how often the driver polls the API. <br /> * Choose a value that balances responsiveness with network load.<br /> <br /> '''Stale-data multiplier'''<br /> <br /> * Protects against using outdated information. <br /> * If the data is older than &lt;code&gt;multiplier × polling interval&lt;/code&gt;, it can be treated as stale.<br /> <br /> '''Fail-safe mode'''<br /> <br /> * Defines the default &lt;code&gt;IsSafe&lt;/code&gt; value if:<br /> * The API is unreachable, or <br /> * Data is stale or invalid.<br /> * Typical setting:<br /> ** Fail-safe to '''unsafe''' (&lt;code&gt;IsSafe = False&lt;/code&gt;) for maximum safety.<br /> <br /> '''Trace logging'''<br /> <br /> * When enabled, the driver logs detailed operations and any errors.<br /> <br /> Trace logs are stored in:<br /> <br /> * &lt;code&gt;Documents\ASCOM\Logs&lt;/code&gt;<br /> <br /> == Usage with automation software ==<br /> <br /> Example workflow with N.I.N.A. or similar software:<br /> <br /> # Open the application.<br /> # For the '''Safety Monitor''' (or equivalent) device:<br /> #* Open the ASCOM chooser.<br /> #* Select '''Deep Sky Chile Safety Monitor'''.<br /> #* Click '''Properties''' / '''Setup''' to configure API URL, observatory, polling, etc.<br /> #* Connect to the driver.<br /> <br /> Once connected:<br /> <br /> * The application can read &lt;code&gt;IsSafe&lt;/code&gt; from the driver. <br /> * Roof open → &lt;code&gt;IsSafe = True&lt;/code&gt; → automation may start or continue imaging (depending on your rules). <br /> * Roof closed → &lt;code&gt;IsSafe = False&lt;/code&gt; → automation can park the mount, close sessions, etc.<br /> <br /> Always configure your automation software so that '''&lt;code&gt;IsSafe = False&lt;/code&gt; triggers protective actions'''.<br /> <br /> == Logging and troubleshooting ==<br /> <br /> If something does not work as expected:<br /> <br /> # Enable '''trace logging''' in the Setup dialog.<br /> # Reproduce the issue (connection error, wrong safety state, etc.).<br /> # Check the log files in:<br /> #* &lt;code&gt;Documents\ASCOM\Logs&lt;/code&gt;<br /> <br /> Things to verify:<br /> <br /> * Can your PC reach the API URL in a web browser? <br /> * Is the correct observatory selected in the Setup dialog? <br /> * Is the polling interval reasonable? <br /> * Is the fail-safe mode set to the desired behaviour if the API is down?<br /> <br /> == Uninstallation ==<br /> <br /> To uninstall the driver:<br /> <br /> # Open '''Windows Settings → Apps''' (or '''Control Panel → Programs and Features''').<br /> # Find '''Deep Sky Chile Safety Monitor''' in the list.<br /> # Click '''Uninstall'''.<br /> <br /> The uninstaller removes all related files and registry entries.<br /> <br /> == Support ==<br /> <br /> For help, contact:<br /> <br /> * '''Cédric Thomas''' <br /> * E-mail: &lt;code&gt;cedric@deepskychile.com&lt;/code&gt;<br /> <br /> == Disclaimer ==<br /> <br /> This driver depends entirely on the '''Deep Sky Chile API''' for the roof and safety information.<br /> <br /> It must not be your only safety measure. Always implement additional, independent safety systems (hardware interlocks, local weather sensors, etc.) in any remote observatory.<br /> <br /> <br /> [[Category:User manuals]]</div>

Cedric https://wiki.deepskychile.com/index.php?title=ASCOM_SafetyMonitor&diff=116 2025-12-04T11:40:20Z

<p>Cedric: </p> <hr /> <div>This page describes the '''Deep Sky Chile Safety Monitor''' ASCOM driver.<br /> <br /> It reads the roof state of a selected observatory via the Deep Sky Chile API and exposes it as the ASCOM &lt;code&gt;SafetyMonitor&lt;/code&gt; property &lt;code&gt;IsSafe&lt;/code&gt;.<br /> <br /> See also: [[ASCOM_ObservingConditions|Deep Sky Chile Observing Conditions (ASCOM driver)]]<br /> <br /> == Overview ==<br /> <br /> The '''Deep Sky Chile Safety Monitor''' is an ASCOM-compliant driver that exposes the '''safety status''' of Deep Sky Chile observatories.<br /> <br /> It converts the roof state into the standard ASCOM &lt;code&gt;IsSafe&lt;/code&gt; value:<br /> <br /> * '''Roof open''' → &lt;code&gt;IsSafe = True&lt;/code&gt; <br /> * '''Roof closed''' → &lt;code&gt;IsSafe = False&lt;/code&gt; <br /> <br /> This driver is intended for remote observatory automation systems that rely on an ASCOM SafetyMonitor to decide whether it is safe to operate equipment.<br /> <br /> == Features ==<br /> <br /> * ASCOM &lt;code&gt;SafetyMonitor&lt;/code&gt; implementation <br /> * Periodic polling of the Deep Sky Chile observatories API <br /> * Observatory selection via dropdown list <br /> * Roof-state-to-safety mapping <br /> * Stale-data protection <br /> * Optional trace logging <br /> * Configurable fail-safe mode<br /> <br /> == How it works ==<br /> <br /> The driver periodically queries the API endpoint:<br /> <br /> * &lt;code&gt;http://api.deepskychile.com/observatories&lt;/code&gt;<br /> <br /> On each poll it:<br /> <br /> # Retrieves the list of observatories from the API.<br /> # Identifies the '''selected observatory''' (configured in the Setup dialog).<br /> # Reads its &lt;code&gt;roofState&lt;/code&gt; value (typically &lt;code&gt;open&lt;/code&gt; or &lt;code&gt;closed&lt;/code&gt;).<br /> # Converts this into an ASCOM &lt;code&gt;IsSafe&lt;/code&gt; boolean:<br /> #* Roof open → safe <br /> #* Roof closed → unsafe<br /> # Applies stale-data protection logic.<br /> # Exposes &lt;code&gt;IsSafe&lt;/code&gt; to any ASCOM client application.<br /> <br /> == Requirements ==<br /> <br /> To use this driver you need:<br /> <br /> * A Windows PC <br /> * The '''ASCOM Platform 7.1 or later''' installed <br /> * An internet connection to reach the Deep Sky Chile API <br /> * Client software that supports ASCOM &lt;code&gt;SafetyMonitor&lt;/code&gt; devices (for example N.I.N.A., Voyager, etc.)<br /> <br /> == Installation ==<br /> <br /> # Download and run the driver installer from your Deep Sky Chile customer area.<br /> # The installer will:<br /> #* Copy the driver files to your system<br /> #* Register the COM driver with ASCOM<br /> #* Create the necessary ASCOM profile entries<br /> <br /> After installation, the driver appears in the ASCOM chooser as '''Deep Sky Chile Safety Monitor''' (or similar).<br /> <br /> == Configuration ==<br /> <br /> Open the '''Setup''' dialog from any ASCOM-compatible application (via the ASCOM chooser → '''Properties''' / '''Setup''').<br /> <br /> You can configure:<br /> <br /> '''API URL'''<br /> <br /> * Default: &lt;code&gt;http://api.deepskychile.com/observatories&lt;/code&gt; <br /> * Change this only if instructed by Deep Sky Chile.<br /> <br /> '''Observatory selection'''<br /> <br /> * A dropdown list shows the available observatories returned by the API. <br /> * Select the observatory whose roof state should control &lt;code&gt;IsSafe&lt;/code&gt;.<br /> <br /> '''Polling interval'''<br /> <br /> * Defines how often the driver polls the API. <br /> * Choose a value that balances responsiveness with network load.<br /> <br /> '''Stale-data multiplier'''<br /> <br /> * Protects against using outdated information. <br /> * If the data is older than &lt;code&gt;multiplier × polling interval&lt;/code&gt;, it can be treated as stale.<br /> <br /> '''Fail-safe mode'''<br /> <br /> * Defines the default &lt;code&gt;IsSafe&lt;/code&gt; value if:<br /> * The API is unreachable, or <br /> * Data is stale or invalid.<br /> * Typical setting:<br /> ** Fail-safe to '''unsafe''' (&lt;code&gt;IsSafe = False&lt;/code&gt;) for maximum safety.<br /> <br /> '''Trace logging'''<br /> <br /> * When enabled, the driver logs detailed operations and any errors.<br /> <br /> Trace logs are stored in:<br /> <br /> * &lt;code&gt;Documents\ASCOM\Logs&lt;/code&gt;<br /> <br /> == Usage with automation software ==<br /> <br /> Example workflow with N.I.N.A. or similar software:<br /> <br /> # Open the application.<br /> # For the '''Safety Monitor''' (or equivalent) device:<br /> #* Open the ASCOM chooser.<br /> #* Select '''Deep Sky Chile Safety Monitor'''.<br /> #* Click '''Properties''' / '''Setup''' to configure API URL, observatory, polling, etc.<br /> #* Connect to the driver.<br /> <br /> Once connected:<br /> <br /> * The application can read &lt;code&gt;IsSafe&lt;/code&gt; from the driver. <br /> * Roof open → &lt;code&gt;IsSafe = True&lt;/code&gt; → automation may start or continue imaging (depending on your rules). <br /> * Roof closed → &lt;code&gt;IsSafe = False&lt;/code&gt; → automation can park the mount, close sessions, etc.<br /> <br /> Always configure your automation software so that '''&lt;code&gt;IsSafe = False&lt;/code&gt; triggers protective actions'''.<br /> <br /> == Logging and troubleshooting ==<br /> <br /> If something does not work as expected:<br /> <br /> # Enable '''trace logging''' in the Setup dialog.<br /> # Reproduce the issue (connection error, wrong safety state, etc.).<br /> # Check the log files in:<br /> #* &lt;code&gt;Documents\ASCOM\Logs&lt;/code&gt;<br /> <br /> Things to verify:<br /> <br /> * Can your PC reach the API URL in a web browser? <br /> * Is the correct observatory selected in the Setup dialog? <br /> * Is the polling interval reasonable? <br /> * Is the fail-safe mode set to the desired behaviour if the API is down?<br /> <br /> == Uninstallation ==<br /> <br /> To uninstall the driver:<br /> <br /> # Open '''Windows Settings → Apps''' (or '''Control Panel → Programs and Features''').<br /> # Find '''Deep Sky Chile Safety Monitor''' in the list.<br /> # Click '''Uninstall'''.<br /> <br /> The uninstaller removes all related files and registry entries.<br /> <br /> == Support ==<br /> <br /> For help, contact:<br /> <br /> * '''Cédric Thomas''' <br /> * E-mail: &lt;code&gt;cedric@deepskychile.com&lt;/code&gt;<br /> <br /> == Disclaimer ==<br /> <br /> This driver depends entirely on the '''Deep Sky Chile API''' for the roof and safety information.<br /> <br /> It must not be your only safety measure. Always implement additional, independent safety systems (hardware interlocks, local weather sensors, etc.) in any remote observatory.<br /> <br /> <br /> [[Category:User manuals]]</div>

Cedric https://wiki.deepskychile.com/index.php?title=ASCOM_ObservingConditions&diff=115 2025-12-04T11:39:52Z

<p>Cedric: </p> <hr /> <div>This page describes the '''Deep Sky Chile Observing Conditions''' ASCOM driver.<br /> <br /> It exposes real-time weather and seeing data from the Deep Sky Chile site through the standard ASCOM &lt;code&gt;ObservingConditions&lt;/code&gt; interface, so that automation software (N.I.N.A., Voyager, SGP, etc.) can use it for monitoring and safety decisions.<br /> <br /> See also: [[ASCOM_SafetyMonitor|Deep Sky Chile Safety Monitor (ASCOM driver)]]<br /> <br /> == Overview ==<br /> <br /> The '''Deep Sky Chile Observing Conditions''' driver is an ASCOM-compliant driver that publishes:<br /> <br /> * Ambient and sky conditions (temperature, humidity, wind, rain…)<br /> * Seeing and sky quality<br /> * Cloud and rain status converted to standard ASCOM fields<br /> <br /> It retrieves meteorological data from the Deep Sky Chile API and maps it to ASCOM &lt;code&gt;ObservingConditions&lt;/code&gt; properties used by most automation software. <br /> This driver is intended for '''remote observatory automation''', to help you make safe decisions about starting, stopping and continuing imaging sessions.<br /> <br /> == Features ==<br /> <br /> '''Supported sensors'''<br /> <br /> * '''Temperature'''<br /> * '''Humidity'''<br /> * '''Dew point'''<br /> * '''Wind speed''' and '''wind gust'''<br /> * '''Seeing''' (star FWHM)<br /> * '''Sky quality''' (NSB)<br /> * '''Sky temperature'''<br /> * '''Cloud cover'''<br /> * '''Rain rate'''<br /> <br /> '''Other key features'''<br /> <br /> * Periodic polling of the Deep Sky Chile weather API<br /> * Conversion of raw values into standard ASCOM properties<br /> * Stale-data protection with a configurable time multiplier<br /> * Optional detailed trace logging for troubleshooting<br /> <br /> == How it works ==<br /> <br /> The driver periodically queries the Deep Sky Chile weather API (default endpoint):<br /> <br /> * &lt;code&gt;http://api.deepskychile.com/weather&lt;/code&gt;<br /> <br /> On each poll it:<br /> <br /> # Retrieves the JSON weather data over HTTP (TLS 1.2 secured)<br /> # Extracts the relevant sensor values (temperature, humidity, seeing, etc.)<br /> # Converts cloud and rain status into ASCOM-compatible percentage / rate values<br /> # Verifies that the data is not stale (based on the configured multiplier)<br /> # Exposes everything through the ASCOM &lt;code&gt;ObservingConditions&lt;/code&gt; interface<br /> <br /> == Requirements ==<br /> <br /> To use this driver you need:<br /> <br /> * A Windows PC <br /> * The '''ASCOM Platform 7.1 or later''' installed <br /> * An internet connection to reach the Deep Sky Chile API <br /> * Compatible client software (for example N.I.N.A., Voyager, SGP, …)<br /> <br /> == Installation ==<br /> <br /> # Download and run the driver installer from your Deep Sky Chile customer area.<br /> # The installer will:<br /> #* Copy the driver files to your system<br /> #* Register the COM driver with ASCOM<br /> #* Add the required ASCOM profile entries<br /> <br /> Once installed, the driver appears in the ASCOM chooser as '''Deep Sky Chile Observing Conditions''' (or similar).<br /> <br /> == Configuration ==<br /> <br /> You configure the driver via its '''Setup''' dialog, accessible from any ASCOM-compatible application.<br /> <br /> '''API URL endpoint'''<br /> <br /> * Default: &lt;code&gt;http://api.deepskychile.com/weather&lt;/code&gt; <br /> * Change this only if instructed by Deep Sky Chile.<br /> <br /> '''Polling interval (seconds)'''<br /> <br /> * Defines how often the driver queries the API. <br /> * Shorter intervals give fresher data but generate more network traffic.<br /> <br /> '''Stale data multiplier'''<br /> <br /> * Protects against using old data. <br /> * If the last update is older than &lt;code&gt;multiplier × polling interval&lt;/code&gt;, the driver can treat the data as stale.<br /> <br /> '''Trace logging'''<br /> <br /> * When enabled, the driver writes a detailed log of its activity.<br /> <br /> Trace logs are stored in:<br /> <br /> * &lt;code&gt;Documents\ASCOM\Logs&lt;/code&gt;<br /> <br /> == Usage with automation software ==<br /> <br /> A typical usage pattern:<br /> <br /> # Open your automation software (for example N.I.N.A., Voyager, SGP).<br /> # In the '''Observing Conditions''' (or equivalent) device selection:<br /> #* Open the ASCOM chooser.<br /> #* Select '''Deep Sky Chile Observing Conditions'''.<br /> #* Click '''Properties''' (or '''Setup''') to configure API URL, polling interval, etc.<br /> #* Confirm and connect.<br /> <br /> Once connected, your software can read:<br /> <br /> * Temperature, humidity, dew point <br /> * Wind speed and gusts <br /> * Cloud cover and rain rate <br /> * Seeing and sky quality <br /> * Sky temperature <br /> <br /> These values can then be used to drive safety limits, session start/stop rules and observing plans.<br /> <br /> == Logging and troubleshooting ==<br /> <br /> If you encounter issues:<br /> <br /> # Enable '''trace logging''' in the Setup dialog.<br /> # Reproduce the problem (for example connection error, missing data).<br /> # Check the latest log files in:<br /> #* &lt;code&gt;Documents\ASCOM\Logs&lt;/code&gt;<br /> <br /> Typical checks:<br /> <br /> * Can the PC reach the API URL in a web browser? <br /> * Is the API URL correct? <br /> * Is the polling interval reasonable (not too short or too long)? <br /> * Is the system time on the PC correct (for stale-data calculations)?<br /> <br /> == Uninstallation ==<br /> <br /> To remove the driver:<br /> <br /> # Open '''Windows Settings → Apps''' (or '''Control Panel → Programs and Features''').<br /> # Locate '''Deep Sky Chile Observing Conditions'''.<br /> # Click '''Uninstall'''.<br /> <br /> The uninstaller removes all installed files and related registry entries.<br /> <br /> == Support ==<br /> <br /> For help, contact:<br /> <br /> * '''Cédric Thomas''' <br /> * E-mail: &lt;code&gt;cedric@deepskychile.com&lt;/code&gt;<br /> <br /> == Disclaimer ==<br /> <br /> This driver relies entirely on the '''Deep Sky Chile API''' for its data.<br /> <br /> Always use redundant safety systems in remote observatories. This driver is intended as an information source and must not be your only line of defence.<br /> <br /> <br /> [[Category:User manuals]]</div>

Cedric https://wiki.deepskychile.com/index.php?title=ASCOM_SafetyMonitor&diff=114 2025-12-04T11:33:18Z

<p>Cedric: </p> <hr /> <div>====== Deep Sky Chile Safety Monitor (ASCOM Driver) ======<br /> <br /> ===== Overview =====<br /> The **Deep Sky Chile Safety Monitor** is an ASCOM-compliant driver that exposes the **safety status** of Deep Sky Chile observatories.<br /> <br /> It reads the roof state of a selected observatory via the Deep Sky Chile API and converts it into the standard ASCOM ''SafetyMonitor'' ''IsSafe'' value.<br /> <br /> Mapping:<br /> <br /> * **Roof open** → ''IsSafe = True''<br /> * **Roof closed** → ''IsSafe = False''<br /> <br /> This driver is intended for remote observatory automation systems that rely on an ASCOM SafetyMonitor to decide whether it is safe to operate equipment.<br /> <br /> ===== Features =====<br /> * ASCOM ''SafetyMonitor'' implementation<br /> * Periodic polling of the Deep Sky Chile observatories API<br /> * Observatory selection via dropdown list<br /> * Roof state-to-safety mapping<br /> * Stale data protection<br /> * Optional trace logging<br /> * Configurable fail-safe mode<br /> <br /> ===== How it Works =====<br /> The driver periodically queries the API endpoint:<br /> <br /> * ''http://api.deepskychile.com/observatories''<br /> <br /> On each poll it:<br /> <br /> - Retrieves the list of observatories from the API.<br /> - Identifies the **selected observatory** (configured in the Setup dialog).<br /> - Reads its ''roofState'' value (typically ''open'' or ''closed'').<br /> - Converts this into an ASCOM ''IsSafe'' boolean:<br /> * Roof open → safe<br /> * Roof closed → unsafe<br /> - Applies stale data protection logic.<br /> - Exposes ''IsSafe'' to any ASCOM client application.<br /> <br /> ===== Requirements =====<br /> To use this driver you need:<br /> <br /> * A Windows PC<br /> * The **ASCOM Platform 7.1 or later** installed<br /> * An internet connection to reach the Deep Sky Chile API<br /> * Client software that supports ASCOM ''SafetyMonitor'' devices (e.g. N.I.N.A., Voyager, etc.)<br /> <br /> ===== Installation =====<br /> - Download and run the driver installer.<br /> - The installer will:<br /> * Copy the driver files to your system<br /> * Register the COM driver with ASCOM<br /> * Create the necessary ASCOM profile entries<br /> <br /> After installation, the driver appears in the ASCOM chooser as **Deep Sky Chile Safety Monitor** (or similar).<br /> <br /> ===== Configuration =====<br /> Open the **Setup** dialog from any ASCOM-compatible application (via the ASCOM chooser → **Properties** / **Setup**).<br /> <br /> You can configure:<br /> <br /> * **API URL**<br /> * Default: ''http://api.deepskychile.com/observatories''<br /> * Change this only if instructed by Deep Sky Chile.<br /> <br /> * **Observatory selection**<br /> * A dropdown list shows the available observatories returned by the API.<br /> * Select the observatory whose roof state should control ''IsSafe''.<br /> <br /> * **Polling interval**<br /> * Defines how often the driver polls the API.<br /> * Choose a value that balances responsiveness with network load.<br /> <br /> * **Stale data multiplier**<br /> * Protects against using outdated information.<br /> * If the data is older than ''multiplier × polling interval'', it can be treated as stale.<br /> <br /> * **Fail-safe mode**<br /> * Defines the default ''IsSafe'' value in case:<br /> - The API is unreachable, or<br /> - Data is stale or invalid.<br /> * Typical configuration:<br /> * Fail-safe to **unsafe** (''IsSafe = False'') for maximum safety.<br /> <br /> * **Trace logging**<br /> * When enabled, the driver logs detailed operations and any errors.<br /> <br /> Trace logs are stored in:<br /> <br /> * ''Documents\ASCOM\Logs''<br /> <br /> ===== Usage with Automation Software =====<br /> Example workflow with N.I.N.A. or similar software:<br /> <br /> - Open the application.<br /> - For the **Safety Monitor** (or equivalent) device:<br /> * Open the ASCOM chooser.<br /> * Select **Deep Sky Chile Safety Monitor**.<br /> * Click **Properties** / **Setup** to configure API URL, observatory, polling, etc.<br /> * Connect to the driver.<br /> <br /> From that point:<br /> <br /> * The application can read ''IsSafe'' from the driver.<br /> * Roof open → ''IsSafe = True'' → automation may start or continue imaging (depending on your rules).<br /> * Roof closed → ''IsSafe = False'' → automation can park the mount, close sessions, etc.<br /> <br /> Always configure your automation software so that **''IsSafe = False'' triggers protective actions.**<br /> <br /> ===== Logging and Troubleshooting =====<br /> If something does not work as expected:<br /> <br /> - Enable **trace logging** in the Setup dialog.<br /> - Reproduce the issue (connection error, wrong safety state, etc.).<br /> - Check the log files in:<br /> * ''Documents\ASCOM\Logs''<br /> <br /> Things to verify:<br /> <br /> * Can your PC reach the API URL in a web browser?<br /> * Is the correct observatory selected in the Setup dialog?<br /> * Is the polling interval reasonable?<br /> * Is the fail-safe mode set to the desired behaviour if the API is down?<br /> <br /> ===== Uninstallation =====<br /> To uninstall the driver:<br /> <br /> - Open **Windows Settings** → **Apps** (or **Control Panel** → **Programs and Features**).<br /> - Find **Deep Sky Chile Safety Monitor** in the list.<br /> - Click **Uninstall**.<br /> <br /> The uninstaller removes all related files and registry entries.<br /> <br /> ===== Support =====<br /> For help, contact:<br /> <br /> * **Cédric Thomas**<br /> * E-mail: ''cedric@deepskychile.com''<br /> <br /> ===== Disclaimer =====<br /> This driver depends entirely on the **Deep Sky Chile API** for the roof and safety information.<br /> <br /> It must not be your only safety measure. Always implement additional, independent safety systems (hardware interlocks, local weather sensors, etc.) in any remote observatory.<br /> <br /> [[Category:User manuals]]</div>

Cedric https://wiki.deepskychile.com/index.php?title=ASCOM_ObservingConditions&diff=113 2025-12-04T11:33:05Z

<p>Cedric: </p> <hr /> <div>====== Deep Sky Chile Observing Conditions (ASCOM Driver) ======<br /> <br /> ===== Overview =====<br /> The **Deep Sky Chile Observing Conditions** driver is an ASCOM-compliant driver that exposes real-time weather and seeing data from the Deep Sky Chile site.<br /> <br /> It retrieves meteorological data from the Deep Sky Chile API and maps it to the standard ASCOM ''ObservingConditions'' properties used by most automation software (N.I.N.A., Voyager, SGP, etc.).<br /> <br /> This driver is designed for **remote observatory automation**, to help you monitor environmental conditions and make safe decisions about imaging sessions.<br /> <br /> ===== Features =====<br /> Supported sensors include:<br /> <br /> * **Temperature**<br /> * **Humidity**<br /> * **Dew Point**<br /> * **Wind Speed** and **Wind Gust**<br /> * **Seeing** (Star FWHM)<br /> * **Sky Quality** (NSB)<br /> * **Sky Temperature**<br /> * **Cloud Cover**<br /> * **Rain Rate**<br /> <br /> Other key features:<br /> <br /> * Periodic polling of the Deep Sky Chile weather API<br /> * Conversion of raw values into standard ASCOM properties<br /> * Stale data protection with a configurable time multiplier<br /> * Optional detailed trace logging for troubleshooting<br /> <br /> ===== How it Works =====<br /> The driver periodically queries the Deep Sky Chile weather API (default endpoint):<br /> <br /> * ''http://api.deepskychile.com/weather''<br /> <br /> On each poll it:<br /> <br /> - Retrieves the JSON weather data over HTTP (TLS 1.2 secured)<br /> - Extracts the relevant sensor values (temperature, humidity, seeing, etc.)<br /> - Converts cloud and rain status into ASCOM-compatible percentage / rate values<br /> - Verifies that the data is not stale (based on the configured multiplier)<br /> - Exposes everything through the ASCOM ''ObservingConditions'' interface<br /> <br /> ===== Requirements =====<br /> To use this driver you need:<br /> <br /> * A Windows PC<br /> * The **ASCOM Platform 7.1 or later** installed<br /> * An internet connection to reach the Deep Sky Chile API<br /> * Compatible client software (e.g. N.I.N.A., Voyager, SGP, …)<br /> <br /> ===== Installation =====<br /> - Download and run the driver installer.<br /> - The installer will:<br /> * Copy the driver files to your system<br /> * Register the COM driver with ASCOM<br /> * Add the required ASCOM profile entries<br /> <br /> Once installed, the driver will appear in the ASCOM chooser as **Deep Sky Chile Observing Conditions** (or similar).<br /> <br /> ===== Configuration =====<br /> You configure the driver via its **Setup** dialog, accessible from any ASCOM-compatible application:<br /> <br /> * **API URL endpoint**<br /> * Default: ''http://api.deepskychile.com/weather''<br /> * Change this only if instructed by Deep Sky Chile.<br /> <br /> * **Polling interval (seconds)**<br /> * Defines how often the driver queries the API.<br /> * Shorter intervals give fresher data but generate more network traffic.<br /> <br /> * **Stale data multiplier**<br /> * Protects against using old data.<br /> * If the last update is older than ''multiplier × polling interval'', the driver can treat the data as stale.<br /> <br /> * **Trace logging (enable/disable)**<br /> * When enabled, the driver writes a detailed log of its activity.<br /> <br /> Trace logs are stored in:<br /> <br /> * ''Documents\ASCOM\Logs''<br /> <br /> ===== Usage with Automation Software =====<br /> Typical usage pattern:<br /> <br /> - Open your automation software (e.g. N.I.N.A., Voyager, SGP).<br /> - In the **Observing Conditions** (or equivalent) device selection:<br /> * Open the ASCOM chooser.<br /> * Select **Deep Sky Chile Observing Conditions**.<br /> * Click **Properties** (or **Setup**) to configure API URL, polling interval, etc.<br /> * Confirm and connect.<br /> <br /> Once connected, your software will be able to read:<br /> <br /> * Temperature, humidity, dew point<br /> * Wind speed and gusts<br /> * Cloud cover, rain rate<br /> * Seeing and sky quality<br /> * Sky temperature<br /> <br /> These values can then be used to drive safety limits, session start/stop rules, and observing plans.<br /> <br /> ===== Logging and Troubleshooting =====<br /> If you encounter issues:<br /> <br /> - Enable **trace logging** in the Setup dialog.<br /> - Reproduce the problem (e.g. connection error, missing data).<br /> - Check the latest log files in:<br /> * ''Documents\ASCOM\Logs''<br /> <br /> Typical checks:<br /> <br /> * Can the PC reach the API URL in a web browser?<br /> * Is the API URL correct?<br /> * Is the polling interval reasonable (not too short/long)?<br /> * Is the system time on the PC correct (for stale data calculations)?<br /> <br /> ===== Uninstallation =====<br /> To remove the driver:<br /> <br /> - Open **Windows Settings** → **Apps** (or **Control Panel** → **Programs and Features**).<br /> - Locate **Deep Sky Chile Observing Conditions**.<br /> - Click **Uninstall**.<br /> <br /> The uninstaller removes all installed files and related registry entries.<br /> <br /> ===== Support =====<br /> For help, contact:<br /> <br /> * **Cédric Thomas**<br /> * E-mail: ''cedric@deepskychile.com''<br /> <br /> ===== Disclaimer =====<br /> This driver relies entirely on the **Deep Sky Chile API** for its data.<br /> <br /> Always use redundant safety systems in remote observatories. This driver is intended as an information source and must not be your only line of defense.<br /> <br /> [[Category:User manuals]]</div>

Cedric https://wiki.deepskychile.com/index.php?title=ASCOM_SafetyMonitor&diff=112 2025-12-04T11:31:33Z

<p>Cedric: </p> <hr /> <div>====== Deep Sky Chile Safety Monitor (ASCOM Driver) ======<br /> <br /> ===== Overview =====<br /> The **Deep Sky Chile Safety Monitor** is an ASCOM-compliant driver that exposes the **safety status** of Deep Sky Chile observatories.<br /> <br /> It reads the roof state of a selected observatory via the Deep Sky Chile API and converts it into the standard ASCOM ''SafetyMonitor'' ''IsSafe'' value.<br /> <br /> Mapping:<br /> <br /> * **Roof open** → ''IsSafe = True''<br /> * **Roof closed** → ''IsSafe = False''<br /> <br /> This driver is intended for remote observatory automation systems that rely on an ASCOM SafetyMonitor to decide whether it is safe to operate equipment.<br /> <br /> ===== Features =====<br /> * ASCOM ''SafetyMonitor'' implementation<br /> * Periodic polling of the Deep Sky Chile observatories API<br /> * Observatory selection via dropdown list<br /> * Roof state-to-safety mapping<br /> * Stale data protection<br /> * Optional trace logging<br /> * Configurable fail-safe mode<br /> <br /> ===== How it Works =====<br /> The driver periodically queries the API endpoint:<br /> <br /> * ''http://api.deepskychile.com/observatories''<br /> <br /> On each poll it:<br /> <br /> - Retrieves the list of observatories from the API.<br /> - Identifies the **selected observatory** (configured in the Setup dialog).<br /> - Reads its ''roofState'' value (typically ''open'' or ''closed'').<br /> - Converts this into an ASCOM ''IsSafe'' boolean:<br /> * Roof open → safe<br /> * Roof closed → unsafe<br /> - Applies stale data protection logic.<br /> - Exposes ''IsSafe'' to any ASCOM client application.<br /> <br /> ===== Requirements =====<br /> To use this driver you need:<br /> <br /> * A Windows PC<br /> * The **ASCOM Platform 7.1 or later** installed<br /> * An internet connection to reach the Deep Sky Chile API<br /> * Client software that supports ASCOM ''SafetyMonitor'' devices (e.g. N.I.N.A., Voyager, etc.)<br /> <br /> ===== Installation =====<br /> - Download and run the driver installer.<br /> - The installer will:<br /> * Copy the driver files to your system<br /> * Register the COM driver with ASCOM<br /> * Create the necessary ASCOM profile entries<br /> <br /> After installation, the driver appears in the ASCOM chooser as **Deep Sky Chile Safety Monitor** (or similar).<br /> <br /> ===== Configuration =====<br /> Open the **Setup** dialog from any ASCOM-compatible application (via the ASCOM chooser → **Properties** / **Setup**).<br /> <br /> You can configure:<br /> <br /> * **API URL**<br /> * Default: ''http://api.deepskychile.com/observatories''<br /> * Change this only if instructed by Deep Sky Chile.<br /> <br /> * **Observatory selection**<br /> * A dropdown list shows the available observatories returned by the API.<br /> * Select the observatory whose roof state should control ''IsSafe''.<br /> <br /> * **Polling interval**<br /> * Defines how often the driver polls the API.<br /> * Choose a value that balances responsiveness with network load.<br /> <br /> * **Stale data multiplier**<br /> * Protects against using outdated information.<br /> * If the data is older than ''multiplier × polling interval'', it can be treated as stale.<br /> <br /> * **Fail-safe mode**<br /> * Defines the default ''IsSafe'' value in case:<br /> - The API is unreachable, or<br /> - Data is stale or invalid.<br /> * Typical configuration:<br /> * Fail-safe to **unsafe** (''IsSafe = False'') for maximum safety.<br /> <br /> * **Trace logging**<br /> * When enabled, the driver logs detailed operations and any errors.<br /> <br /> Trace logs are stored in:<br /> <br /> * ''Documents\ASCOM\Logs''<br /> <br /> ===== Usage with Automation Software =====<br /> Example workflow with N.I.N.A. or similar software:<br /> <br /> - Open the application.<br /> - For the **Safety Monitor** (or equivalent) device:<br /> * Open the ASCOM chooser.<br /> * Select **Deep Sky Chile Safety Monitor**.<br /> * Click **Properties** / **Setup** to configure API URL, observatory, polling, etc.<br /> * Connect to the driver.<br /> <br /> From that point:<br /> <br /> * The application can read ''IsSafe'' from the driver.<br /> * Roof open → ''IsSafe = True'' → automation may start or continue imaging (depending on your rules).<br /> * Roof closed → ''IsSafe = False'' → automation can park the mount, close sessions, etc.<br /> <br /> Always configure your automation software so that **''IsSafe = False'' triggers protective actions.**<br /> <br /> ===== Logging and Troubleshooting =====<br /> If something does not work as expected:<br /> <br /> - Enable **trace logging** in the Setup dialog.<br /> - Reproduce the issue (connection error, wrong safety state, etc.).<br /> - Check the log files in:<br /> * ''Documents\ASCOM\Logs''<br /> <br /> Things to verify:<br /> <br /> * Can your PC reach the API URL in a web browser?<br /> * Is the correct observatory selected in the Setup dialog?<br /> * Is the polling interval reasonable?<br /> * Is the fail-safe mode set to the desired behaviour if the API is down?<br /> <br /> ===== Uninstallation =====<br /> To uninstall the driver:<br /> <br /> - Open **Windows Settings** → **Apps** (or **Control Panel** → **Programs and Features**).<br /> - Find **Deep Sky Chile Safety Monitor** in the list.<br /> - Click **Uninstall**.<br /> <br /> The uninstaller removes all related files and registry entries.<br /> <br /> ===== Support =====<br /> For help, contact:<br /> <br /> * **Cédric Thomas**<br /> * E-mail: ''cedric@deepskychile.com''<br /> <br /> ===== Disclaimer =====<br /> This driver depends entirely on the **Deep Sky Chile API** for the roof and safety information.<br /> <br /> It must not be your only safety measure. Always implement additional, independent safety systems (hardware interlocks, local weather sensors, etc.) in any remote observatory.</div>

Cedric https://wiki.deepskychile.com/index.php?title=ASCOM_SafetyMonitor&diff=111 2025-12-04T11:29:55Z

<p>Cedric: Created page with &quot;====== Deep Sky Chile Safety Monitor (ASCOM Driver) ====== ===== Overview ===== The **Deep Sky Chile Safety Monitor** is an ASCOM-compliant driver that exposes the **safety status** of Deep Sky Chile observatories. It reads the roof state of a selected observatory via the Deep Sky Chile API and converts it into the standard ASCOM &#039;&#039;SafetyMonitor&#039;&#039; &#039;&#039;IsSafe&#039;&#039; value. Mapping: * **Roof open** → &#039;&#039;IsSafe = True&#039;&#039; * **Roof closed** → &#039;&#039;IsSafe = False&#039;&#039; This driv...&quot;</p> <hr /> <div>====== Deep Sky Chile Safety Monitor (ASCOM Driver) ======<br /> <br /> ===== Overview =====<br /> The **Deep Sky Chile Safety Monitor** is an ASCOM-compliant driver that exposes the **safety status** of Deep Sky Chile observatories.<br /> <br /> It reads the roof state of a selected observatory via the Deep Sky Chile API and converts it into the standard ASCOM ''SafetyMonitor'' ''IsSafe'' value.<br /> <br /> Mapping:<br /> <br /> * **Roof open** → ''IsSafe = True''<br /> * **Roof closed** → ''IsSafe = False''<br /> <br /> This driver is intended for remote observatory automation systems that rely on an ASCOM SafetyMonitor to decide whether it is safe to operate equipment.<br /> <br /> ===== Features =====<br /> * ASCOM ''SafetyMonitor'' implementation<br /> * Periodic polling of the Deep Sky Chile observatories API<br /> * Observatory selection via dropdown list<br /> * Roof state-to-safety mapping<br /> * Stale data protection<br /> * Optional trace logging<br /> * Configurable fail-safe mode<br /> <br /> ===== How it Works =====<br /> The driver periodically queries the API endpoint:<br /> <br /> * ''http://api.deepskychile.com/observatories''<br /> <br /> On each poll it:<br /> <br /> - Retrieves the list of observatories from the API.<br /> - Identifies the **selected observatory** (configured in the Setup dialog).<br /> - Reads its ''roofState'' value (typically ''open'' or ''closed'').<br /> - Converts this into an ASCOM ''IsSafe'' boolean:<br /> * Roof open → safe<br /> * Roof closed → unsafe<br /> - Applies stale data protection logic.<br /> - Exposes ''IsSafe'' to any ASCOM client application.<br /> <br /> ===== Requirements =====<br /> To use this driver you need:<br /> <br /> * A Windows PC<br /> * The **ASCOM Platform** installed<br /> * An internet connection to reach the Deep Sky Chile API<br /> * Client software that supports ASCOM ''SafetyMonitor'' devices (e.g. N.I.N.A., Voyager, etc.)<br /> <br /> ===== Installation =====<br /> - Download and run the driver installer.<br /> - The installer will:<br /> * Copy the driver files to your system<br /> * Register the COM driver with ASCOM<br /> * Create the necessary ASCOM profile entries<br /> <br /> After installation, the driver appears in the ASCOM chooser as **Deep Sky Chile Safety Monitor** (or similar).<br /> <br /> ===== Configuration =====<br /> Open the **Setup** dialog from any ASCOM-compatible application (via the ASCOM chooser → **Properties** / **Setup**).<br /> <br /> You can configure:<br /> <br /> * **API URL**<br /> * Default: ''http://api.deepskychile.com/observatories''<br /> * Change this only if instructed by Deep Sky Chile.<br /> <br /> * **Observatory selection**<br /> * A dropdown list shows the available observatories returned by the API.<br /> * Select the observatory whose roof state should control ''IsSafe''.<br /> <br /> * **Polling interval**<br /> * Defines how often the driver polls the API.<br /> * Choose a value that balances responsiveness with network load.<br /> <br /> * **Stale data multiplier**<br /> * Protects against using outdated information.<br /> * If the data is older than ''multiplier × polling interval'', it can be treated as stale.<br /> <br /> * **Fail-safe mode**<br /> * Defines the default ''IsSafe'' value in case:<br /> - The API is unreachable, or<br /> - Data is stale or invalid.<br /> * Typical configuration:<br /> * Fail-safe to **unsafe** (''IsSafe = False'') for maximum safety.<br /> <br /> * **Trace logging**<br /> * When enabled, the driver logs detailed operations and any errors.<br /> <br /> Trace logs are stored in:<br /> <br /> * ''Documents\ASCOM\Logs''<br /> <br /> ===== Usage with Automation Software =====<br /> Example workflow with N.I.N.A. or similar software:<br /> <br /> - Open the application.<br /> - For the **Safety Monitor** (or equivalent) device:<br /> * Open the ASCOM chooser.<br /> * Select **Deep Sky Chile Safety Monitor**.<br /> * Click **Properties** / **Setup** to configure API URL, observatory, polling, etc.<br /> * Connect to the driver.<br /> <br /> From that point:<br /> <br /> * The application can read ''IsSafe'' from the driver.<br /> * Roof open → ''IsSafe = True'' → automation may start or continue imaging (depending on your rules).<br /> * Roof closed → ''IsSafe = False'' → automation can park the mount, close sessions, etc.<br /> <br /> Always configure your automation software so that **''IsSafe = False'' triggers protective actions.**<br /> <br /> ===== Logging and Troubleshooting =====<br /> If something does not work as expected:<br /> <br /> - Enable **trace logging** in the Setup dialog.<br /> - Reproduce the issue (connection error, wrong safety state, etc.).<br /> - Check the log files in:<br /> * ''Documents\ASCOM\Logs''<br /> <br /> Things to verify:<br /> <br /> * Can your PC reach the API URL in a web browser?<br /> * Is the correct observatory selected in the Setup dialog?<br /> * Is the polling interval reasonable?<br /> * Is the fail-safe mode set to the desired behaviour if the API is down?<br /> <br /> ===== Uninstallation =====<br /> To uninstall the driver:<br /> <br /> - Open **Windows Settings** → **Apps** (or **Control Panel** → **Programs and Features**).<br /> - Find **Deep Sky Chile Safety Monitor** in the list.<br /> - Click **Uninstall**.<br /> <br /> The uninstaller removes all related files and registry entries.<br /> <br /> ===== Support =====<br /> For help, contact:<br /> <br /> * **Cédric Thomas**<br /> * E-mail: ''cedric@deepskychile.com''<br /> <br /> ===== Disclaimer =====<br /> This driver depends entirely on the **Deep Sky Chile API** for the roof and safety information.<br /> <br /> It must not be your only safety measure. Always implement additional, independent safety systems (hardware interlocks, local weather sensors, etc.) in any remote observatory.</div>

Cedric https://wiki.deepskychile.com/index.php?title=ASCOM_ObservingConditions&diff=110 2025-12-04T11:28:46Z

<p>Cedric: </p> <hr /> <div>====== Deep Sky Chile Observing Conditions (ASCOM Driver) ======<br /> <br /> ===== Overview =====<br /> The **Deep Sky Chile Observing Conditions** driver is an ASCOM-compliant driver that exposes real-time weather and seeing data from the Deep Sky Chile site.<br /> <br /> It retrieves meteorological data from the Deep Sky Chile API and maps it to the standard ASCOM ''ObservingConditions'' properties used by most automation software (N.I.N.A., Voyager, SGP, etc.).<br /> <br /> This driver is designed for **remote observatory automation**, to help you monitor environmental conditions and make safe decisions about imaging sessions.<br /> <br /> ===== Features =====<br /> Supported sensors include:<br /> <br /> * **Temperature**<br /> * **Humidity**<br /> * **Dew Point**<br /> * **Wind Speed** and **Wind Gust**<br /> * **Seeing** (Star FWHM)<br /> * **Sky Quality** (NSB)<br /> * **Sky Temperature**<br /> * **Cloud Cover**<br /> * **Rain Rate**<br /> <br /> Other key features:<br /> <br /> * Periodic polling of the Deep Sky Chile weather API<br /> * Conversion of raw values into standard ASCOM properties<br /> * Stale data protection with a configurable time multiplier<br /> * Optional detailed trace logging for troubleshooting<br /> <br /> ===== How it Works =====<br /> The driver periodically queries the Deep Sky Chile weather API (default endpoint):<br /> <br /> * ''http://api.deepskychile.com/weather''<br /> <br /> On each poll it:<br /> <br /> - Retrieves the JSON weather data over HTTP (TLS 1.2 secured)<br /> - Extracts the relevant sensor values (temperature, humidity, seeing, etc.)<br /> - Converts cloud and rain status into ASCOM-compatible percentage / rate values<br /> - Verifies that the data is not stale (based on the configured multiplier)<br /> - Exposes everything through the ASCOM ''ObservingConditions'' interface<br /> <br /> ===== Requirements =====<br /> To use this driver you need:<br /> <br /> * A Windows PC<br /> * The **ASCOM Platform** installed<br /> * An internet connection to reach the Deep Sky Chile API<br /> * Compatible client software (e.g. N.I.N.A., Voyager, SGP, …)<br /> <br /> ===== Installation =====<br /> - Download and run the driver installer.<br /> - The installer will:<br /> * Copy the driver files to your system<br /> * Register the COM driver with ASCOM<br /> * Add the required ASCOM profile entries<br /> <br /> Once installed, the driver will appear in the ASCOM chooser as **Deep Sky Chile Observing Conditions** (or similar).<br /> <br /> ===== Configuration =====<br /> You configure the driver via its **Setup** dialog, accessible from any ASCOM-compatible application:<br /> <br /> * **API URL endpoint**<br /> * Default: ''http://api.deepskychile.com/weather''<br /> * Change this only if instructed by Deep Sky Chile.<br /> <br /> * **Polling interval (seconds)**<br /> * Defines how often the driver queries the API.<br /> * Shorter intervals give fresher data but generate more network traffic.<br /> <br /> * **Stale data multiplier**<br /> * Protects against using old data.<br /> * If the last update is older than ''multiplier × polling interval'', the driver can treat the data as stale.<br /> <br /> * **Trace logging (enable/disable)**<br /> * When enabled, the driver writes a detailed log of its activity.<br /> <br /> Trace logs are stored in:<br /> <br /> * ''Documents\ASCOM\Logs''<br /> <br /> ===== Usage with Automation Software =====<br /> Typical usage pattern:<br /> <br /> - Open your automation software (e.g. N.I.N.A., Voyager, SGP).<br /> - In the **Observing Conditions** (or equivalent) device selection:<br /> * Open the ASCOM chooser.<br /> * Select **Deep Sky Chile Observing Conditions**.<br /> * Click **Properties** (or **Setup**) to configure API URL, polling interval, etc.<br /> * Confirm and connect.<br /> <br /> Once connected, your software will be able to read:<br /> <br /> * Temperature, humidity, dew point<br /> * Wind speed and gusts<br /> * Cloud cover, rain rate<br /> * Seeing and sky quality<br /> * Sky temperature<br /> <br /> These values can then be used to drive safety limits, session start/stop rules, and observing plans.<br /> <br /> ===== Logging and Troubleshooting =====<br /> If you encounter issues:<br /> <br /> - Enable **trace logging** in the Setup dialog.<br /> - Reproduce the problem (e.g. connection error, missing data).<br /> - Check the latest log files in:<br /> * ''Documents\ASCOM\Logs''<br /> <br /> Typical checks:<br /> <br /> * Can the PC reach the API URL in a web browser?<br /> * Is the API URL correct?<br /> * Is the polling interval reasonable (not too short/long)?<br /> * Is the system time on the PC correct (for stale data calculations)?<br /> <br /> ===== Uninstallation =====<br /> To remove the driver:<br /> <br /> - Open **Windows Settings** → **Apps** (or **Control Panel** → **Programs and Features**).<br /> - Locate **Deep Sky Chile Observing Conditions**.<br /> - Click **Uninstall**.<br /> <br /> The uninstaller removes all installed files and related registry entries.<br /> <br /> ===== Support =====<br /> For help, contact:<br /> <br /> * **Cédric Thomas**<br /> * E-mail: ''cedric@deepskychile.com''<br /> <br /> ===== Disclaimer =====<br /> This driver relies entirely on the **Deep Sky Chile API** for its data.<br /> <br /> Always use redundant safety systems in remote observatories. This driver is intended as an information source and must not be your only line of defense.</div>

Cedric https://wiki.deepskychile.com/index.php?title=ASCOM_ObservingConditions&diff=109 2025-12-04T11:26:41Z

<p>Cedric: </p> <hr /> <div>====== Deep Sky Chile Observing Conditions Driver ======<br /> <br /> ===== Description =====<br /> [cite_start]The **Deep Sky Chile Observing Conditions** driver is an ASCOM-compliant driver that exposes weather and seeing data from the Deep Sky Chile site[cite: 1]. [cite_start]It retrieves real-time meteorological data from the Deep Sky Chile API and maps it to standard ASCOM ObservingConditions properties[cite: 2].<br /> <br /> [cite_start]This driver is intended for remote observatory automation systems (like N.I.N.A., Voyager, SGP) to monitor environmental conditions[cite: 3].<br /> <br /> ^ Attribute ^ Detail ^<br /> | **Version** | [cite_start]1.0.0 [cite: 1] |<br /> | **Author** | [cite_start]Cédric Thomas [cite: 1] |<br /> | **Compliance** | [cite_start]ASCOM ObservingConditions [cite: 1] |<br /> <br /> ===== Supported Sensors =====<br /> [cite_start]The driver supports the following sensors[cite: 3]:<br /> * Temperature, Humidity, Dew Point<br /> * Wind Speed &amp; Wind Gust<br /> * Seeing (StarFWHM)<br /> * Sky Quality (NSB)<br /> * Sky Temperature<br /> * Cloud Cover &amp; Rain Rate<br /> <br /> ===== How it works =====<br /> [cite_start]The driver periodically queries the API (default: http://api.deepskychile.com/weather)[cite: 4].<br /> <br /> [cite_start]It then performs the following steps[cite: 5]:<br /> - Retrieves the JSON data via HTTP (TLS 1.2 secured)<br /> - Extracts sensor values (Temp, Hum, Seeing, etc.)<br /> - Converts cloud/rain status into percentage/rate<br /> - Supports stale data protection (configurable multiplier)<br /> - Provides detailed trace logging<br /> <br /> ===== Configuration =====<br /> [cite_start]Open the driver’s Setup dialog from any ASCOM application[cite: 5].<br /> <br /> [cite_start]You may configure the following[cite: 6]:<br /> * API URL Endpoint<br /> * Polling interval (seconds)<br /> * Stale data multiplier<br /> * Trace logging (Enable/Disable)<br /> <br /> Trace logs are stored in:<br /> [cite_start]''Documents\ASCOM\Logs'' [cite: 6]<br /> <br /> ===== Installation =====<br /> Run the installer. [cite_start]It will[cite: 7]:<br /> * Copy driver files<br /> * Register the COM driver<br /> * Add ASCOM profile entries<br /> <br /> ===== Uninstallation =====<br /> Use Windows Add/Remove Programs. [cite_start]The uninstaller removes all files and registry entries[cite: 8].<br /> <br /> ===== Support =====<br /> For help, contact:<br /> Cédric Thomas<br /> [cite_start]cedric@deepskychile.com [cite: 8]<br /> <br /> ===== Disclaimer =====<br /> This driver relies entirely on the Deep Sky Chile API. [cite_start]**Always use redundant safety systems in remote observatory operations.** [cite: 9]</div>

Cedric https://wiki.deepskychile.com/index.php?title=ASCOM_ObservingConditions&diff=108 2025-12-04T11:24:58Z

<p>Cedric: </p> <hr /> <div>= Deep Sky Chile Observing Conditions Driver =<br /> <br /> == Overview ==<br /> The '''Deep Sky Chile Observing Conditions''' driver is an ASCOM-compliant driver that exposes weather and seeing data from the Deep Sky Chile site. It retrieves real-time meteorological data from the Deep Sky Chile API and maps it to standard ASCOM ObservingConditions properties. This driver is intended for remote observatory automation systems (like N.I.N.A., Voyager, SGP) to monitor environmental conditions. {| class=&quot;wikitable&quot;<br /> ! Property<br /> ! Value<br /> |-<br /> | '''Version'''<br /> | 1.0.0 |-<br /> | '''Author'''<br /> | Cédric Thomas |}<br /> <br /> == Supported Sensors ==<br /> The driver supports the following sensors: * Temperature, Humidity, Dew Point<br /> * Wind Speed &amp; Wind Gust<br /> * Seeing (StarFWHM)<br /> * Sky Quality (NSB)<br /> * Sky Temperature<br /> * Cloud Cover &amp; Rain Rate<br /> <br /> == Operation Logic ==<br /> The driver periodically queries the API (default: &lt;code&gt;http://api.deepskychile.com/weather&lt;/code&gt;). It then performs the following operations: # Retrieves the JSON data via HTTP (TLS 1.2 secured)<br /> # Extracts sensor values (Temp, Hum, Seeing, etc.)<br /> # Converts cloud/rain status into percentage/rate<br /> # Supports stale data protection (configurable multiplier)<br /> # Provides detailed trace logging<br /> <br /> <br /> <br /> [Image of API data flow diagram]<br /> <br /> <br /> == Configuration ==<br /> Open the driver’s Setup dialog from any ASCOM application to configure the following: * API URL Endpoint<br /> * Polling interval (seconds)<br /> * Stale data multiplier<br /> * Trace logging (Enable/Disable)<br /> <br /> === Logging ===<br /> Trace logs are stored in: : &lt;code&gt;Documents\ASCOM\Logs&lt;/code&gt;<br /> <br /> == Installation ==<br /> Run the installer to: * Copy driver files<br /> * Register the COM driver<br /> * Add ASCOM profile entries<br /> <br /> == Uninstallation ==<br /> Use Windows Add/Remove Programs. The uninstaller removes all files and registry entries. == Support ==<br /> For help, contact: : Cédric Thomas (cedric@deepskychile.com)<br /> <br /> == Disclaimer ==<br /> This driver relies entirely on the Deep Sky Chile API. Always use redundant safety systems in remote observatory operations. ```<br /> <br /> ***<br /> <br /> ### Page 2: Deep Sky Chile Safety Monitor Driver<br /> <br /> ```mediawiki<br /> = Deep Sky Chile Safety Monitor =<br /> <br /> == Overview ==<br /> The '''Deep Sky Chile Safety Monitor''' is an ASCOM-compliant driver that exposes the safety status of Deep Sky Chile observatories. It retrieves the ''roofState'' (&quot;open&quot; or &quot;closed&quot;) from the Deep Sky Chile API and converts it into an ASCOM SafetyMonitor ''IsSafe'' value. This driver is intended for remote observatory automation systems that rely on ASCOM SafetyMonitor devices. {| class=&quot;wikitable&quot;<br /> ! Property<br /> ! Value<br /> |-<br /> | '''Version'''<br /> | 1.2.0 |-<br /> | '''Author'''<br /> | Cédric Thomas |}<br /> <br /> == Safety Logic ==<br /> The driver maps the roof state to the ASCOM safety status: * '''Roof open''' → Safe = True<br /> * '''Roof closed''' → Safe = False<br /> <br /> == Operation Logic ==<br /> The driver periodically queries the API at: : &lt;code&gt;http://api.deepskychile.com/observatories&lt;/code&gt;<br /> <br /> It then performs the following steps: # Identifies the selected observatory<br /> # Reads its roofState<br /> # Converts this into ASCOM IsSafe<br /> # Supports stale data protection<br /> # Provides optional trace logging<br /> <br /> == Configuration ==<br /> Open the driver’s Setup dialog from any ASCOM application to configure: * API URL<br /> * Observatory selection (dropdown list)<br /> * Polling interval<br /> * Stale data multiplier<br /> * Fail-safe mode<br /> * Trace logging<br /> <br /> === Logging ===<br /> Trace logs are stored in: : &lt;code&gt;Documents\ASCOM\Logs&lt;/code&gt;<br /> <br /> == Installation ==<br /> Run the installer to: * Copy driver files<br /> * Register the COM driver<br /> * Add ASCOM profile entries<br /> <br /> == Uninstallation ==<br /> Use Windows Add/Remove Programs. The uninstaller removes all files and registry entries. == Support ==<br /> For help, contact: : Cédric Thomas (cedric@deepskychile.com)<br /> <br /> == Disclaimer ==<br /> This driver relies entirely on the Deep Sky Chile API. Always use redundant safety systems in remote observatory operations. ```<br /> <br /> ### Next Step<br /> Would you like me to generate a summary email to Cédric Thomas notifying him that the documentation has been drafted?</div>

Cedric https://wiki.deepskychile.com/index.php?title=ASCOM_ObservingConditions&diff=107 2025-12-04T11:23:17Z

<p>Cedric: </p> <hr /> <div>= Deep Sky Chile Observing Conditions Driver =<br /> <br /> == Overview ==<br /> [cite_start]The **Deep Sky Chile Observing Conditions** driver is an ASCOM-compliant driver that exposes weather and seeing data from the Deep Sky Chile site &lt;ref&gt;[cite: 1]&lt;/ref&gt;. [cite_start]It retrieves real-time meteorological data from the Deep Sky Chile API and maps it to standard ASCOM ObservingConditions properties &lt;ref&gt;[cite: 2]&lt;/ref&gt;. [cite_start]This driver is intended for remote observatory automation systems (like N.I.N.A., Voyager, SGP) to monitor environmental conditions &lt;ref&gt;[cite: 3]&lt;/ref&gt;.<br /> <br /> {| class=&quot;wikitable&quot;<br /> ! Property<br /> ! Value<br /> |-<br /> | '''Version'''<br /> | [cite_start]1.0.0 &lt;ref&gt;[cite: 1]&lt;/ref&gt;<br /> |-<br /> | '''Author'''<br /> | [cite_start]Cédric Thomas &lt;ref&gt;[cite: 1]&lt;/ref&gt;<br /> |}<br /> <br /> == Supported Sensors ==<br /> [cite_start]The driver supports the following sensors &lt;ref&gt;[cite: 3]&lt;/ref&gt;:<br /> * Temperature, Humidity, Dew Point<br /> * Wind Speed &amp; Wind Gust<br /> * Seeing (StarFWHM)<br /> * Sky Quality (NSB)<br /> * Sky Temperature<br /> * Cloud Cover &amp; Rain Rate<br /> <br /> == How it works ==<br /> [cite_start]The driver periodically queries the API (default: &lt;code&gt;http://api.deepskychile.com/weather&lt;/code&gt;) &lt;ref&gt;[cite: 4]&lt;/ref&gt;.<br /> <br /> <br /> <br /> [Image of API data flow diagram]<br /> <br /> <br /> [cite_start]It performs the following logic &lt;ref&gt;[cite: 5]&lt;/ref&gt;:<br /> # Retrieves the JSON data via HTTP (TLS 1.2 secured).<br /> # Extracts sensor values (Temp, Hum, Seeing, etc.).<br /> # Converts cloud/rain status into percentage/rate.<br /> # Supports stale data protection (configurable multiplier).<br /> # Provides detailed trace logging.<br /> <br /> == Configuration ==<br /> [cite_start]Configuration is handled via the driver’s Setup dialog from any ASCOM application &lt;ref&gt;[cite: 5]&lt;/ref&gt;.<br /> <br /> === Settings ===<br /> [cite_start]You may configure the following parameters &lt;ref&gt;[cite: 6]&lt;/ref&gt;:<br /> * API URL Endpoint<br /> * Polling interval (seconds)<br /> * Stale data multiplier<br /> * Trace logging (Enable/Disable)<br /> <br /> === Logging ===<br /> [cite_start]Trace logs are stored in &lt;ref&gt;[cite: 6]&lt;/ref&gt;:<br /> : &lt;code&gt;Documents\ASCOM\Logs&lt;/code&gt;<br /> <br /> == Installation and Uninstallation ==<br /> ; Installation<br /> [cite_start]Run the installer to copy driver files, register the COM driver, and add ASCOM profile entries &lt;ref&gt;[cite: 7]&lt;/ref&gt;.<br /> <br /> ; Uninstallation<br /> Use Windows Add/Remove Programs. [cite_start]The uninstaller removes all files and registry entries &lt;ref&gt;[cite: 8]&lt;/ref&gt;.<br /> <br /> == Disclaimer ==<br /> This driver relies entirely on the Deep Sky Chile API. [cite_start]Always use redundant safety systems in remote observatory operations &lt;ref&gt;[cite: 9]&lt;/ref&gt;.<br /> <br /> == Support ==<br /> [cite_start]For help, contact Cédric Thomas at &lt;code&gt;cedric@deepskychile.com&lt;/code&gt; &lt;ref&gt;[cite: 8]&lt;/ref&gt;.<br /> <br /> == References ==<br /> &lt;references /&gt;</div>

Cedric https://wiki.deepskychile.com/index.php?title=ASCOM_ObservingConditions&diff=106 2025-12-04T11:21:22Z

<p>Cedric: Created page with &quot;= Deep Sky Chile Observing Conditions Driver = == Overview == [cite_start]The **Deep Sky Chile Observing Conditions** driver is an ASCOM-compliant driver designed to expose weather and seeing data from the Deep Sky Chile site[cite: 1]. [cite_start]It is intended for use with remote observatory automation systems, such as N.I.N.A., Voyager, or SGP, allowing them to monitor environmental conditions effectively[cite: 3]. {| class=&quot;wikitable&quot; ! Attribute ! Detail |- | &#039;&#039;&#039;V...&quot;</p> <hr /> <div>= Deep Sky Chile Observing Conditions Driver =<br /> <br /> == Overview ==<br /> [cite_start]The **Deep Sky Chile Observing Conditions** driver is an ASCOM-compliant driver designed to expose weather and seeing data from the Deep Sky Chile site[cite: 1]. [cite_start]It is intended for use with remote observatory automation systems, such as N.I.N.A., Voyager, or SGP, allowing them to monitor environmental conditions effectively[cite: 3].<br /> <br /> {| class=&quot;wikitable&quot;<br /> ! Attribute<br /> ! Detail<br /> |-<br /> | '''Version'''<br /> | [cite_start]1.0.0 [cite: 1]<br /> |-<br /> | '''Author'''<br /> | [cite_start]Cédric Thomas [cite: 1]<br /> |-<br /> | '''Compliance'''<br /> | [cite_start]ASCOM ObservingConditions [cite: 2]<br /> |}<br /> <br /> == Functionality ==<br /> [cite_start]The driver retrieves real-time meteorological data from the Deep Sky Chile API and maps it to standard ASCOM ObservingConditions properties[cite: 2].<br /> <br /> <br /> === Supported Sensors ===<br /> [cite_start]The driver supports the following environmental readings[cite: 3]:<br /> * Temperature, Humidity, and Dew Point<br /> * Wind Speed and Wind Gust<br /> * Seeing (StarFWHM)<br /> * Sky Quality (NSB)<br /> * Sky Temperature<br /> * Cloud Cover and Rain Rate<br /> <br /> === Operation Logic ===<br /> [cite_start]The driver operates by periodically querying the API (default endpoint: `http://api.deepskychile.com/weather`)[cite: 4]. [cite_start]The operational workflow is as follows[cite: 5]:<br /> # Retrieves JSON data via HTTP (secured with TLS 1.2).<br /> # Extracts specific sensor values (Temp, Hum, Seeing, etc.).<br /> # Converts cloud and rain status into percentage or rate formats.<br /> # Applies stale data protection using a configurable multiplier.<br /> # Generates detailed trace logs.<br /> <br /> == Configuration ==<br /> Configuration is managed via the driver’s Setup dialog, accessible from any ASCOM application. [cite_start]Users can configure the following settings[cite: 6]:<br /> * **API URL Endpoint**<br /> * **Polling interval** (in seconds)<br /> * **Stale data multiplier**<br /> * **Trace logging** (Enable/Disable)<br /> <br /> <br /> === Logging ===<br /> [cite_start]Trace logs are generated to assist with troubleshooting and are stored in the following directory[cite: 6]:<br /> : &lt;code&gt;Documents\ASCOM\Logs&lt;/code&gt;<br /> <br /> == Installation and Removal ==<br /> ; Installation<br /> [cite_start]Running the installer performs the following actions[cite: 7]:<br /> * Copies the necessary driver files.<br /> * Registers the COM driver.<br /> * Adds the required ASCOM profile entries.<br /> <br /> ; Uninstallation<br /> To remove the driver, use the Windows Add/Remove Programs feature. [cite_start]The uninstaller will remove all files and registry entries associated with the driver[cite: 8].<br /> <br /> == Safety and Disclaimer ==<br /> [cite_start]This driver relies entirely on the Deep Sky Chile API[cite: 9]. [cite_start]It is strongly recommended to always use redundant safety systems in remote observatory operations[cite: 9].<br /> <br /> == Support ==<br /> [cite_start]For assistance, please contact Cédric Thomas at `cedric@deepskychile.com`[cite: 8].</div>

Cedric https://wiki.deepskychile.com/index.php?title=Accessing_Your_Power_Manager&diff=92 2024-11-27T21:22:35Z

<p>Cedric: </p> <hr /> <div>== How to Access Your Power Manager Page ==<br /> <br /> Accessing your Power Manager no longer requires connecting to the Raspberry Pi, and soon this method will no longer be available. Follow these simple steps to access your power device (e.g., IPPower or IPX) directly from your Customer Dashboard.<br /> <br /> === 1. Log in to Your Customer Dashboard ===<br /> Start by opening your Customer Dashboard at [https://clients.deepskychile.com](https://clients.deepskychile.com) and log in with your credentials.<br /> <br /> [[File:login.png|center|width=400px]]<br /> <br /> <br /> Once logged in, navigate to '''Tools''' → '''My Systems'''.<br /> <br /> [[File:tools-my_systems.png|center|400px]] <br /> <br /> === 2. Open the Power Manager ===<br /> In the '''My Systems''' section, locate your system and click on it. You will see an option labeled '''Open Power Manager'''. Click on this link to access your Power Manager Page.<br /> <br /> [[File:my_system_power.png|center|width=400px]]<br /> <br /> If you do not see the link in this menu please contact us for assistance. If you have previously entered your Power Manager credentials in the system settings, they will be displayed directly below the '''Open Power Manager''' link for easy reference.<br /> <br /> === 3. Forgot Your Credentials? ===<br /> If you do not see your credentials or have forgotten them please contact us for assistance. Whenever you change your credentials, please remember to update them: scroll down to the '''Edit My System''' section in the same interface. Here, you can update or retrieve your credentials for future use.<br /> <br /> By following these steps, you can quickly and easily manage your power device.<br /> <br /> [[Category:User manuals]]</div>

Cedric https://wiki.deepskychile.com/index.php?title=Accessing_Your_Power_Manager&diff=91 2024-11-27T21:21:29Z

<p>Cedric: </p> <hr /> <div>== How to Access Your Power Manager Page ==<br /> <br /> Accessing your Power Manager no longer requires connecting to the Raspberry Pi, and soon this method will no longer be available. Follow these simple steps to access your power device (e.g., IPPower or IPX) directly from your Customer Dashboard.<br /> <br /> === 1. Log in to Your Customer Dashboard ===<br /> Start by opening your Customer Dashboard at [https://clients.deepskychile.com](https://clients.deepskychile.com) and log in with your credentials.<br /> <br /> [[File:login.png|center|width=400px]]<br /> <br /> <br /> Once logged in, navigate to '''Tools''' → '''My Systems'''.<br /> <br /> [[File:tools-my_systems.png|center|400px]] <br /> <br /> === 2. Open the Power Manager ===<br /> In the '''My Systems''' section, locate your system and click on it. You will see an option labeled '''Open Power Manager'''. Click on this link to access your Power Manager Page.<br /> <br /> [[File:my_system_power.png|center|width=400px]]<br /> <br /> If you do not see the link in this menu please reach out for assistance. If you have previously entered your Power Manager credentials in the system settings, they will be displayed directly below the '''Open Power Manager''' link for easy reference.<br /> <br /> === 3. Forgot Your Credentials? ===<br /> If you do not see your credentials or have forgotten them please contact us for assistance. Whenever you change your credentials, please remember to update them: scroll down to the '''Edit My System''' section in the same interface. Here, you can update or retrieve your credentials for future use.<br /> <br /> By following these steps, you can quickly and easily manage your power device.<br /> <br /> [[Category:User manuals]]</div>

Cedric https://wiki.deepskychile.com/index.php?title=Lost_Connection_to_Equipment&diff=90 2024-11-27T21:18:51Z

<p>Cedric: </p> <hr /> <div>== Troubleshooting Connectivity Issues ==<br /> <br /> If you're experiencing connectivity issues while trying to connect to the computer controlling your telescope in Chile, please follow the steps below to troubleshoot the problem before reaching out to Deep Sky Chile for assistance.<br /> <br /> === 1. Connect to the Customer Platform ===<br /> Begin by opening your customer platform at [https://clients.deepskychile.com](https://clients.deepskychile.com) and log in with your credentials.<br /> <br /> [[File:login.png|center|width=400px]]<br /> <br /> <br /> Navigate to '''Tools''' → '''My Systems'''.<br /> <br /> [[File:tools-my_systems.png|center|width=400px]]<br /> <br /> <br /> Here, you can view the status of your system. The color of the system's indicator will tell you its current state:<br /> <br /> * '''Green''': System is online.<br /> * '''Red''': System is offline.<br /> * '''Black''': System is not yet installed.<br /> <br /> [[File:mysystems.png|center|width=400px]]<br /> <br /> <br /> If your system is online, proceed to '''Step 2'''. If it is offline, click on your system, and select '''Reboot my System's Router''' from the menu. Once confirmed, your system's router will reboot. Wait for '''2 minutes''' then refresh the page. If the system turns green after this period, the issue was likely related to the router, and you should be able to reconnect. If the system remains red, contact us for further assistance.<br /> <br /> <br /> [[File:my_system_reboot.png|center|width=400px]]<br /> <br /> <br /> == Access Your Power Device ==<br /> <br /> If your system is online (as described in the previous step), you can attempt to reboot your main imaging computer. To do this:<br /> <br /> # Click on your system and select '''Open Power Manager''' from the menu.<br /> # This will open your Power Manager interface (e.g., IPPower, IPX, or similar).<br /> # In the Power Manager page, locate and execute the power cycle command for your main computer.<br /> <br /> <br /> <br /> [[File:my_system_power.png|center|width=400px]]<br /> <br /> <br /> By following these steps, you should be able to restore connectivity to your telescope control system. If the issue persists, please contact Deep Sky Chile support for further assistance.<br /> <br /> <br /> [[Category:User manuals]]</div>

Cedric https://wiki.deepskychile.com/index.php?title=Lost_Connection_to_Equipment&diff=89 2024-11-27T21:18:35Z

<p>Cedric: </p> <hr /> <div>== Troubleshooting Connectivity Issues ==<br /> <br /> If you're experiencing connectivity issues while trying to connect to the computer controlling your telescope in Chile, please follow the steps below to troubleshoot the problem before reaching out to Deep Sky Chile for assistance.<br /> <br /> === 1. Connect to the Customer Platform ===<br /> Begin by opening your customer platform at [https://clients.deepskychile.com](https://clients.deepskychile.com) and log in with your credentials.<br /> <br /> [[File:login.png|center|width=400px]]<br /> <br /> <br /> Navigate to '''Tools''' → '''My Systems'''.<br /> <br /> [[File:tools-my_systems.png|center|width=400px]]<br /> <br /> <br /> Here, you can view the status of your system. The color of the system's indicator will tell you its current state:<br /> <br /> * '''Green''': System is online.<br /> * '''Red''': System is offline.<br /> * '''Black''': System is not yet installed.<br /> <br /> [[File:mysystems.png|center|width=400px]]<br /> <br /> <br /> If your system is online, proceed to '''Step 2'''. If it is offline, click on your system, and select '''Reboot my System's Router''' from the menu. Once confirmed, your system's router will reboot. Wait for '''3 minutes''' then refresh the page. If the system turns green after this period, the issue was likely related to the router, and you should be able to reconnect. If the system remains red, contact us for further assistance.<br /> <br /> <br /> [[File:my_system_reboot.png|center|width=400px]]<br /> <br /> <br /> == Access Your Power Device ==<br /> <br /> If your system is online (as described in the previous step), you can attempt to reboot your main imaging computer. To do this:<br /> <br /> # Click on your system and select '''Open Power Manager''' from the menu.<br /> # This will open your Power Manager interface (e.g., IPPower, IPX, or similar).<br /> # In the Power Manager page, locate and execute the power cycle command for your main computer.<br /> <br /> <br /> <br /> [[File:my_system_power.png|center|width=400px]]<br /> <br /> <br /> By following these steps, you should be able to restore connectivity to your telescope control system. If the issue persists, please contact Deep Sky Chile support for further assistance.<br /> <br /> <br /> [[Category:User manuals]]</div>

Cedric https://wiki.deepskychile.com/index.php?title=Lost_Connection_to_Equipment&diff=88 2024-11-27T21:17:49Z

<p>Cedric: </p> <hr /> <div>== Troubleshooting Connectivity Issues ==<br /> <br /> If you're experiencing connectivity issues while trying to connect to the computer controlling your telescope in Chile, please follow the steps below to troubleshoot the problem before reaching out to Deep Sky Chile for assistance.<br /> <br /> === 1. Connect to the Customer Platform ===<br /> Begin by opening your customer platform at [https://clients.deepskychile.com](https://clients.deepskychile.com) and log in with your credentials.<br /> <br /> [[File:login.png|center|width=400px]]<br /> <br /> <br /> Navigate to '''Tools''' → '''My Systems'''.<br /> <br /> [[File:tools-my_systems.png|center|width=400px]]<br /> <br /> <br /> Here, you can view the status of your system. The color of the system's indicator will tell you its current state:<br /> <br /> * '''Green''': System is online.<br /> * '''Red''': System is offline.<br /> * '''Black''': System is not yet installed.<br /> <br /> [[File:mysystems.png|center|width=400px]]<br /> <br /> <br /> If your system is online, proceed to '''Step 2'''. If it is offline, click on your system, and select '''Reboot my System's Router''' from the menu. Once confirmed, your system's router will reboot. Wait for '''2 minutes''' then refresh the page. If the system turns green after this period, the issue was likely related to the router, and you should be able to reconnect. If the system remains red, contact us for further assistance.<br /> <br /> <br /> [[File:my_system_reboot.png|center|width=400px]]<br /> <br /> <br /> == Access Your Power Device ==<br /> <br /> If your system is online (as described in the previous step), you can attempt to reboot your main imaging computer. To do this:<br /> <br /> # Click on your system and select '''Open Power Manager''' from the menu.<br /> # This will open your Power Manager interface (e.g., IPPower, IPX, or similar).<br /> # In the Power Manager page, locate and execute the power cycle command for your main computer.<br /> <br /> <br /> <br /> [[File:my_system_power.png|center|width=400px]]<br /> <br /> <br /> By following these steps, you should be able to restore connectivity to your telescope control system. If the issue persists, please contact Deep Sky Chile support for further assistance.<br /> <br /> <br /> [[Category:User manuals]]</div>

Cedric https://wiki.deepskychile.com/index.php?title=Lost_Connection_to_Equipment&diff=87 2024-11-27T21:17:13Z

<p>Cedric: </p> <hr /> <div>== Troubleshooting Connectivity Issues ==<br /> <br /> If you're experiencing connectivity issues while trying to connect to the computer controlling your telescope in Chile, please follow the steps below to troubleshoot the problem before reaching out to Deep Sky Chile for assistance.<br /> <br /> === 1. Connect to the Customer Platform ===<br /> Begin by opening your customer platform at [https://clients.deepskychile.com](https://clients.deepskychile.com) and log in with your credentials.<br /> <br /> [[File:login.png|center|width=400px]]<br /> <br /> <br /> Navigate to '''Tools''' → '''My Systems'''.<br /> <br /> [[File:tools-my_systems.png|center|width=400px]]<br /> <br /> <br /> Here, you can view the status of your system. The color of the system's indicator will tell you its current state:<br /> <br /> * '''Green''': System is online.<br /> * '''Red''': System is offline.<br /> * '''Black''': System is not yet installed.<br /> <br /> [[File:mysystems.png|center|width=400px]]<br /> <br /> <br /> If your system is online, proceed to '''Step 2'''. If it is offline, click on your system, and select '''Reboot my System's Router''' from the menu. Once confirmed, your system's router will reboot. Wait for '''2 minutes''' before attempting to reconnect. If the system turns green after this period, the issue was likely related to the router, and you should be able to reconnect. If the system remains red, contact us for further assistance.<br /> <br /> <br /> [[File:my_system_reboot.png|center|width=400px]]<br /> <br /> <br /> == Access Your Power Device ==<br /> <br /> If your system is online (as described in the previous step), you can attempt to reboot your main imaging computer. To do this:<br /> <br /> # Click on your system and select '''Open Power Manager''' from the menu.<br /> # This will open your Power Manager interface (e.g., IPPower, IPX, or similar).<br /> # In the Power Manager page, locate and execute the power cycle command for your main computer.<br /> <br /> <br /> <br /> [[File:my_system_power.png|center|width=400px]]<br /> <br /> <br /> By following these steps, you should be able to restore connectivity to your telescope control system. If the issue persists, please contact Deep Sky Chile support for further assistance.<br /> <br /> <br /> [[Category:User manuals]]</div>

Cedric https://wiki.deepskychile.com/index.php?title=Lost_Connection_to_Equipment&diff=86 2024-11-27T21:15:11Z

<p>Cedric: </p> <hr /> <div>== Troubleshooting Connectivity Issues ==<br /> <br /> If you're experiencing connectivity issues while trying to connect to the computer controlling your telescope in Chile, please follow the steps below to troubleshoot the problem before reaching out to Deep Sky Chile for assistance.<br /> <br /> === 1. Connect to the Customer Platform ===<br /> Begin by opening your customer platform at [https://clients.deepskychile.com](https://clients.deepskychile.com) and log in with your credentials.<br /> <br /> [[File:login.png|center|width=400px]]<br /> <br /> <br /> Navigate to '''Tools''' → '''My Systems'''.<br /> <br /> [[File:tools-my_systems.png|center|width=400px]]<br /> <br /> <br /> Here, you can view the status of your system. The color of the system's indicator will tell you its current state:<br /> <br /> * '''Green''': System is online.<br /> * '''Red''': System is offline.<br /> * '''Black''': System is not yet installed.<br /> <br /> [[File:mysystems.png|center|width=400px]]<br /> <br /> <br /> If your system is online, proceed to '''Step 2'''. If it is offline, click on your system, and select '''Reboot my System's Router''' from the menu. Once confirmed, your system's router will reboot. Wait for '''5 minutes''' before attempting to reconnect. If the system turns green after this period, the issue was likely related to the router, and you should be able to reconnect. If the system remains red, contact us for further assistance.<br /> <br /> <br /> [[File:my_system_reboot.png|center|width=400px]]<br /> <br /> <br /> == Access Your Power Device ==<br /> <br /> If your system is online (as described in the previous step), you can attempt to reboot your main imaging computer. To do this:<br /> <br /> # Click on your system and select '''Open Power Manager''' from the menu.<br /> # This will open your Power Manager interface (e.g., IPPower, IPX, or similar).<br /> # In the Power Manager page, locate and execute the power cycle command for your main computer.<br /> <br /> <br /> <br /> [[File:my_system_power.png|center|width=400px]]<br /> <br /> <br /> By following these steps, you should be able to restore connectivity to your telescope control system. If the issue persists, please contact Deep Sky Chile support for further assistance.<br /> <br /> <br /> [[Category:User manuals]]</div>

Cedric https://wiki.deepskychile.com/index.php?title=Accessing_Your_Power_Manager&diff=85 2024-11-27T21:12:33Z

<p>Cedric: </p> <hr /> <div>== How to Access Your Power Manager Page ==<br /> <br /> Accessing your Power Manager no longer requires connecting to the Raspberry Pi, and soon this method will no longer be available. Follow these simple steps to access your power device (e.g., IPPower or IPX) directly from your Customer Dashboard.<br /> <br /> === 1. Log in to Your Customer Dashboard ===<br /> Start by opening your Customer Dashboard at [https://clients.deepskychile.com](https://clients.deepskychile.com) and log in with your credentials.<br /> <br /> [[File:login.png|center|width=400px]]<br /> <br /> <br /> Once logged in, navigate to '''Tools''' → '''My Systems'''.<br /> <br /> [[File:tools-my_systems.png|center|400px]] <br /> <br /> === 2. Open the Power Manager ===<br /> In the '''My Systems''' section, locate your system and click on it. You will see an option labeled '''Open Power Manager'''. Click on this link to access your Power Manager Page.<br /> <br /> [[File:my_system_power.png|center|width=400px]]<br /> <br /> If you do not see the link in this menu please reach out for assistance. If you have previously entered your Power Manager credentials in the system settings, they will be displayed directly below the '''Open Power Manager''' link for easy reference.<br /> <br /> === 3. Forgot Your Credentials? ===<br /> If you do not see your credentials or have forgotten them please reach out for assistance. Whener you change your credentials, please remember to update them: scroll down to the '''Edit My System''' section in the same interface. Here, you can update or retrieve your credentials for future use.<br /> <br /> By following these steps, you can quickly and easily manage your power device.<br /> <br /> [[Category:User manuals]]</div>

Cedric https://wiki.deepskychile.com/index.php?title=Accessing_Your_Power_Manager&diff=84 2024-11-27T21:04:50Z

<p>Cedric: </p> <hr /> <div>== How to Access Your Power Manager Page ==<br /> <br /> Accessing your Power Manager no longer requires connecting to the Raspberry Pi, and soon this method will no longer be available. Follow these simple steps to access your power device (e.g., IPPower or IPX) directly from your Customer Dashboard, from anywhere.<br /> <br /> === 1. Log in to Your Customer Dashboard ===<br /> Start by opening your Customer Dashboard at [https://clients.deepskychile.com](https://clients.deepskychile.com) and log in with your credentials.<br /> <br /> [[File:login.png|center|width=400px]]<br /> <br /> <br /> Once logged in, navigate to '''Tools''' → '''My Systems'''.<br /> <br /> [[File:tools-my_systems.png|center|400px]] <br /> <br /> === 2. Open the Power Manager ===<br /> In the '''My Systems''' section, locate your system and click on it. You will see an option labeled '''Open Power Manager'''. Click on this link to access your Power Manager Page.<br /> <br /> [[File:my_system_power.png|center|width=400px]]<br /> <br /> If you do not see the link in this menu please reach out for assistance. If you have previously entered your Power Manager credentials in the system settings, they will be displayed directly below the '''Open Power Manager''' link for easy reference.<br /> <br /> === 3. Forgot Your Credentials? ===<br /> If you do not see your credentials or have forgotten them please reach out for assistance. Whener you change your credentials, please remember to update them: scroll down to the '''Edit My System''' section in the same interface. Here, you can update or retrieve your credentials for future use.<br /> <br /> By following these steps, you can quickly and easily manage your power device.<br /> <br /> [[Category:User manuals]]</div>

Cedric https://wiki.deepskychile.com/index.php?title=Accessing_Your_Power_Manager&diff=83 2024-11-27T21:03:05Z

<p>Cedric: </p> <hr /> <div>== How to Access Your Power Manager Page ==<br /> <br /> Accessing your Power Manager no longer requires connecting to the Raspberry Pi, and soon this method will no longer be available. Follow these simple steps to access your power device (e.g., IPPower or IPX) directly from your Customer Dashboard, from anywhere.<br /> <br /> === 1. Log in to Your Customer Dashboard ===<br /> Start by opening your Customer Dashboard at [https://clients.deepskychile.com](https://clients.deepskychile.com) and log in with your credentials.<br /> <br /> [[File:login.png|center|width=400px]]<br /> <br /> <br /> Once logged in, navigate to '''Tools''' → '''My Systems'''.<br /> <br /> [[File:tools-my_systems.png|center|400px]] <br /> <br /> === 2. Open the Power Manager ===<br /> In the '''My Systems''' section, locate your system and click on it. You will see an option labeled '''Open Power Manager'''. Click on this link to access your Power Manager Page.<br /> <br /> [[File:my_system_power.png|center|width=400px]]<br /> <br /> If you do not see the link in this menu please reach out for assistance. If you have previously entered your Power Manager credentials in the system settings, they will be displayed directly below the '''Open Power Manager''' link for easy reference.<br /> <br /> === 3. Forgot Your Credentials? ===<br /> If you do not see your credentials or have forgotten them please reach out for assistance. Whener you change your credentials, please remember to update them: scroll down to the '''Edit My System''' section in the same interface. Here, you can update or retrieve your credentials for future use.<br /> <br /> By following these steps, you can quickly and easily manage your power device. without needing to connect to the Raspberry Pi.<br /> <br /> [[Category:User manuals]]</div>

Cedric https://wiki.deepskychile.com/index.php?title=Accessing_Your_Power_Manager&diff=82 2024-11-27T20:59:12Z

<p>Cedric: </p> <hr /> <div>== How to Access Your Power Manager Page ==<br /> <br /> Accessing your Power Manager no longer requires connecting to the Raspberry Pi, and soon this method will no longer be available. Follow these simple steps to access your power device (e.g., IPPower or IPX) directly from your Customer Dashboard, from anywhere.<br /> <br /> === 1. Log in to Your Customer Dashboard ===<br /> Start by opening your Customer Dashboard at [https://clients.deepskychile.com](https://clients.deepskychile.com) and log in with your credentials.<br /> <br /> [[File:login.png|center|width=400px]]<br /> <br /> Once logged in, navigate to '''Tools''' → '''My Systems'''.<br /> <br /> [[File:tools-my_systems.png|center|400px]] <br /> <br /> === 2. Open the Power Manager ===<br /> In the '''My Systems''' section, locate your system and click on it. You will see an option labeled '''Open Power Manager'''. Click on this link to access your Power Manager Page.<br /> <br /> [[File:mysystems.png|center|width=400px]]<br /> <br /> If you have previously entered your Power Manager credentials in the system settings, they will be displayed directly below the '''Open Power Manager''' link for easy reference.<br /> <br /> === 3. Forgot Your Credentials? ===<br /> If you do not see your credentials or have forgotten them please reach out for assistance. Whener you change your credentials, please remember to update them: scroll down to the '''Edit My System''' section in the same interface. Here, you can update or retrieve your credentials for future use.<br /> <br /> [[File:my_system_power.png|center|width=400px]]<br /> <br /> By following these steps, you can quickly and easily manage your power device. without needing to connect to the Raspberry Pi.<br /> <br /> [[Category:User manuals]]</div>

Cedric https://wiki.deepskychile.com/index.php?title=Lost_Connection_to_Equipment&diff=81 2024-11-27T20:56:58Z

<p>Cedric: </p> <hr /> <div>== Troubleshooting Connectivity Issues ==<br /> <br /> If you're experiencing connectivity issues while trying to connect to the computer controlling your telescope in Chile, please follow the steps below to troubleshoot the problem before reaching out to Deep Sky Chile for assistance.<br /> <br /> === 1. Connect to the Customer Platform ===<br /> Begin by opening your customer platform at [https://clients.deepskychile.com](https://clients.deepskychile.com) and log in with your credentials.<br /> <br /> [[File:login.png|center|width=400px]]<br /> <br /> <br /> Navigate to '''Tools''' → '''My Systems'''.<br /> <br /> [[File:tools-my_systems.png|center|width=400px]]<br /> <br /> <br /> Here, you can view the status of your system. The color of the system's indicator will tell you its current state:<br /> <br /> * '''Green''': System is online.<br /> * '''Red''': System is offline.<br /> * '''Black''': System is not yet installed.<br /> <br /> [[File:mysystems.png|center|width=400px]]<br /> <br /> <br /> If your system is online, proceed to '''Step 2'''. If it is offline, click on your system, and select '''Reboot my System's Router''' from the menu. Once confirmed, the router will reboot. Wait for '''5 minutes''' before attempting to reconnect. If the system turns green after this period, the issue was likely related to the router, and you should be able to reconnect. If the system remains red, contact us for further assistance.<br /> <br /> <br /> [[File:my_system_reboot.png|center|width=400px]]<br /> <br /> <br /> == Access Your Power Device ==<br /> <br /> If your system is online (as described in the previous step), you can attempt to reboot your main imaging computer. To do this:<br /> <br /> # Click on your system and select '''Open Power Manager''' from the menu.<br /> # This will open your Power Manager interface (e.g., IPPower, IPX, or similar).<br /> # In the Power Manager page, locate and execute the power cycle command for your main computer.<br /> <br /> <br /> <br /> [[File:my_system_power.png|center|width=400px]]<br /> <br /> <br /> By following these steps, you should be able to restore connectivity to your telescope control system. If the issue persists, please contact Deep Sky Chile support for further assistance.<br /> <br /> <br /> [[Category:User manuals]]</div>

Cedric https://wiki.deepskychile.com/index.php?title=Lost_Connection_to_Equipment&diff=80 2024-11-27T20:52:38Z

<p>Cedric: </p> <hr /> <div>== Troubleshooting Connectivity Issues ==<br /> <br /> If you're experiencing connectivity issues while trying to connect to the computer controlling your telescope in Chile, please follow the steps below to troubleshoot the problem before reaching out to Deep Sky Chile for assistance.<br /> <br /> === 1. Connect to the Customer Platform ===<br /> Begin by opening your customer platform at [https://clients.deepskychile.com](https://clients.deepskychile.com) and log in with your credentials.<br /> <br /> [[File:login.png|center|width=400px]]<br /> <br /> <br /> Navigate to '''Tools''' → '''My Systems'''.<br /> <br /> [[File:tools-my_systems.png|center|width=400px]]<br /> <br /> <br /> Here, you can view the status of your system. The color of the system's indicator will tell you its current state:<br /> <br /> * '''Green''': System is online.<br /> * '''Red''': System is offline.<br /> * '''Black''': System is not yet installed.<br /> <br /> [[File:mysystems.png|center|width=400px]]<br /> <br /> <br /> If your system is online, proceed to '''Step 2'''. If it is offline, click on your system, and select '''Reboot my System's Router''' from the menu. Once confirmed, the router will reboot. Wait for '''5 minutes''' before attempting to reconnect. If the system turns green after this period, the issue was likely related to the router, and you should be able to reconnect. If the system remains red, contact us for further assistance.<br /> <br /> <br /> [[File:my_system_reboot.png|center|width=400px]]<br /> <br /> <br /> === 2. Access Power Devices ===<br /> If your system is online (see previous step) you may try to reboot your main imaging computer. Click on your system, and select '''Open Power Manager''' from the menu. Your Power Manager (IPPower, IPX...) page should open. From there you should be able to power cycle your main computer.<br /> <br /> <br /> [[File:my_system_power.png|center|width=400px]]<br /> <br /> <br /> By following these steps, you should be able to restore connectivity to your telescope control system. If the issue persists, please contact Deep Sky Chile support for further assistance.<br /> <br /> <br /> [[Category:User manuals]]</div>

Cedric https://wiki.deepskychile.com/index.php?title=File:My_system_power.png&diff=79 2024-11-27T20:42:49Z

<p>Cedric: </p> <hr /> <div></div>

Cedric https://wiki.deepskychile.com/index.php?title=File:My_system_reboot.png&diff=78 2024-11-27T20:42:25Z

<p>Cedric: </p> <hr /> <div></div>

Cedric https://wiki.deepskychile.com/index.php?title=Accessing_Your_Power_Manager&diff=77 2024-11-27T20:34:44Z

<p>Cedric: /* Accessing Your Power Manager Page */</p> <hr /> <div>== How To Access Your Power Manager Page ==<br /> <br /> It is no longer necessary to connect to the Raspberry Pi to access your Power Manager. Follow these simple steps to access your power device from anywhere, such as IPPower or IPX, directly from your Customer Dashboard.<br /> <br /> === 1. Log in to Your Customer Dashboard ===<br /> Start by opening your Customer Dashboard at [https://clients.deepskychile.com](https://clients.deepskychile.com) and log in with your credentials.<br /> <br /> [[File:login.png|center|width=400px]]<br /> <br /> Once logged in, navigate to '''Tools''' → '''My Systems'''.<br /> <br /> [[File:tools-my_systems.png|center|400px]] <br /> <br /> === 2. Open the Power Manager ===<br /> In the '''My Systems''' section, locate your system and click on it. You will see an option labeled '''Open Power Manager'''. Click on this link to access your Power Manager Page.<br /> <br /> [[File:mysystems.png|center|width=400px]]<br /> <br /> If you have previously entered your Power Manager credentials in the system settings, they will be displayed directly below the '''Open Power Manager''' link for easy reference.<br /> <br /> === 3. Forgot Your Credentials? ===<br /> If you do not see your credentials or have forgotten them please reach out for assistance. Whener you change your credentials, please remember to update them: scroll down to the '''Edit My System''' section in the same interface. Here, you can update or retrieve your credentials for future use.<br /> <br /> [[File:mysystems-menu.png|center|width=400px]]<br /> <br /> By following these steps, you can quickly and easily manage your power device. without needing to connect to the Raspberry Pi.<br /> <br /> [[Category:User manuals]]</div>

Cedric https://wiki.deepskychile.com/index.php?title=Accessing_Your_Power_Manager&diff=76 2024-11-27T20:33:44Z

<p>Cedric: </p> <hr /> <div>== Accessing Your Power Manager Page ==<br /> <br /> It is no longer necessary to connect to the Raspberry Pi to access your Power Manager. Follow these simple steps to access your power device from anywhere, such as IPPower or IPX, directly from your Customer Dashboard.<br /> <br /> === 1. Log in to Your Customer Dashboard ===<br /> Start by opening your Customer Dashboard at [https://clients.deepskychile.com](https://clients.deepskychile.com) and log in with your credentials.<br /> <br /> [[File:login.png|center|width=400px]]<br /> <br /> Once logged in, navigate to '''Tools''' → '''My Systems'''.<br /> <br /> [[File:tools-my_systems.png|center|400px]] <br /> <br /> === 2. Open the Power Manager ===<br /> In the '''My Systems''' section, locate your system and click on it. You will see an option labeled '''Open Power Manager'''. Click on this link to access your Power Manager Page.<br /> <br /> [[File:mysystems.png|center|width=400px]]<br /> <br /> If you have previously entered your Power Manager credentials in the system settings, they will be displayed directly below the '''Open Power Manager''' link for easy reference.<br /> <br /> === 3. Forgot Your Credentials? ===<br /> If you do not see your credentials or have forgotten them please reach out for assistance. Whener you change your credentials, please remember to update them: scroll down to the '''Edit My System''' section in the same interface. Here, you can update or retrieve your credentials for future use.<br /> <br /> [[File:mysystems-menu.png|center|width=400px]]<br /> <br /> By following these steps, you can quickly and easily manage your power device. without needing to connect to the Raspberry Pi.<br /> <br /> [[Category:User manuals]]</div>

Cedric https://wiki.deepskychile.com/index.php?title=Accessing_Your_Power_Manager&diff=75 2024-11-27T20:30:21Z

<p>Cedric: Created page with &quot;== Accessing Your Power Manager Page == It is no longer necessary to connect to the Raspberry Pi to access your Power Manager. Follow these simple steps to access your power device from anywhere, such as IPPower or IPX, directly from your Customer Dashboard. === 1. Log in to Your Customer Dashboard === Start by opening your Customer Dashboard at [https://clients.deepskychile.com](https://clients.deepskychile.com) and log in with your credentials. File:login.png|cent...&quot;</p> <hr /> <div>== Accessing Your Power Manager Page ==<br /> <br /> It is no longer necessary to connect to the Raspberry Pi to access your Power Manager. Follow these simple steps to access your power device from anywhere, such as IPPower or IPX, directly from your Customer Dashboard.<br /> <br /> === 1. Log in to Your Customer Dashboard ===<br /> Start by opening your Customer Dashboard at [https://clients.deepskychile.com](https://clients.deepskychile.com) and log in with your credentials.<br /> <br /> [[File:login.png|center|400px]] <br /> <br /> Once logged in, navigate to '''Tools''' → '''My Systems'''.<br /> <br /> [[File:tools-my_systems.png|center|400px]] <br /> <br /> === 2. Open the Power Manager ===<br /> In the '''My Systems''' section, locate your system and click on it. You will see an option labeled '''Open Power Manager'''. Click on this link to access your Power Manager Page.<br /> <br /> [[File:open-power-manager.png|center|400px]] <br /> <br /> If you have previously entered your Power Manager credentials in the system settings, they will be displayed directly below the '''Open Power Manager''' link for easy reference.<br /> <br /> === 3. Forgot Your Credentials? ===<br /> If you do not see your credentials or have forgotten them please reach out for assistance. Whener you change your credentials, please remember to update them: scroll down to the '''Edit My System''' section in the same interface. Here, you can update or retrieve your credentials for future use.<br /> <br /> [[File:edit-my-system.png|center|400px]] <br /> <br /> By following these steps, you can quickly and easily manage your power device. without needing to connect to the Raspberry Pi.<br /> <br /> [[Category:User manuals]]</div>

Cedric https://wiki.deepskychile.com/index.php?title=Lost_Connection_to_Equipment&diff=74 2024-11-27T19:56:25Z

<p>Cedric: </p> <hr /> <div>== Troubleshooting Connectivity Issues ==<br /> <br /> If you're experiencing connectivity issues while trying to connect to the computer controlling your telescope in Chile, please follow the steps below to troubleshoot the problem before reaching out to Deep Sky Chile for assistance.<br /> <br /> === 1. Connect to the Customer Platform ===<br /> Begin by opening your customer platform at [https://clients.deepskychile.com](https://clients.deepskychile.com) and log in with your credentials.<br /> <br /> [[File:login.png|center|width=400px]]<br /> <br /> <br /> Navigate to '''Tools''' → '''My Systems'''.<br /> <br /> [[File:tools-my_systems.png|center|width=400px]]<br /> <br /> <br /> Here, you can view the status of your system. The color of the system's indicator will tell you its current state:<br /> <br /> * '''Green''': System is online.<br /> * '''Red''': System is offline.<br /> * '''Black''': System is not yet installed.<br /> <br /> [[File:mysystems.png|center|width=400px]]<br /> <br /> <br /> If your system is online, proceed to '''Step 2'''. If it is offline, click on your system, and select '''Reboot my System's Router''' from the menu. Once confirmed, the router will reboot. Wait for '''5 minutes''' before attempting to reconnect. If the system turns green after this period, the issue was likely related to the router, and you should be able to reconnect. If the system remains red, contact us for further assistance.<br /> <br /> [[File:mysystems-menu.png|center|width=400px]]<br /> <br /> <br /> === 2. Connect to the Raspberry Pi (RPi) ===<br /> The Raspberry Pi (RPi) is a dedicated 24/7 server installed on your network by Deep Sky Chile. If you cannot connect to your imaging computer, attempt to connect to the Raspberry Pi instead.<br /> <br /> Use '''AnyDesk''' or '''TeamViewer''' to establish a connection. You can find the necessary credentials in the '''My Systems''' section of your customer platform. Click on your system, and select your preferred connection method. The default password is '''DSChileRemote''' (please do not change this password).<br /> <br /> [[File:rpi.jpg|center|width=400px]]<br /> <br /> === 3. Access Power Devices ===<br /> Once connected to your Raspberry Pi, you can manage power for devices such as IPPower, IPX, or similar. To reboot your main imaging computer, open a web browser (e.g., Chromium) and enter the URL for your power management device (e.g., http://192.168.1.3).<br /> <br /> <br /> [[File:chromium.png|center|width=400px]]<br /> <br /> <br /> By following these steps, you should be able to restore connectivity to your telescope control system. If the issue persists, please contact Deep Sky Chile support for further assistance.<br /> <br /> <br /> [[Category:User manuals]]</div>

Cedric https://wiki.deepskychile.com/index.php?title=Lost_Connection_to_Equipment&diff=65 2024-11-15T16:15:37Z

<p>Cedric: </p> <hr /> <div>== Troubleshooting Connectivity Issues ==<br /> <br /> If you're experiencing connectivity issues while trying to connect to the computer controlling your telescope in Chile, please follow the steps below to troubleshoot the problem before reaching out to Deep Sky Chile for assistance.<br /> <br /> === 1. Connect to the Customer Platform ===<br /> Begin by opening your customer platform at [https://clients.deepskychile.com](https://clients.deepskychile.com) and log in with your credentials.<br /> <br /> [[File:login.png|center|width=400px]]<br /> <br /> <br /> Navigate to '''Tools''' → '''My Systems'''.<br /> <br /> [[File:tools-my_systems.png|center|width=400px]]<br /> <br /> <br /> Here, you can view the status of your system. The color of the system's indicator will tell you its current state:<br /> <br /> * '''Green''': System is online.<br /> * '''Red''': System is offline.<br /> * '''Black''': System is not yet installed.<br /> <br /> [[File:mysystems.png|center|width=400px]]<br /> <br /> <br /> If your system is online, proceed to '''Step 2'''. If it is offline, click on your system, and select '''Reboot my System''' from the menu. Once confirmed, the router will reboot. Wait for '''5 minutes''' before attempting to reconnect. If the system turns green after this period, the issue was likely related to the router, and you should be able to reconnect. If the system remains red, contact us for further assistance.<br /> <br /> [[File:mysystems-menu.png|center|width=400px]]<br /> <br /> <br /> === 2. Connect to the Raspberry Pi (RPi) ===<br /> The Raspberry Pi (RPi) is a dedicated 24/7 server installed on your network by Deep Sky Chile. If you cannot connect to your imaging computer, attempt to connect to the Raspberry Pi instead.<br /> <br /> Use '''AnyDesk''' or '''TeamViewer''' to establish a connection. You can find the necessary credentials in the '''My Systems''' section of your customer platform. Click on your system, and select your preferred connection method. The default password is '''DSChileRemote''' (please do not change this password).<br /> <br /> [[File:rpi.jpg|center|width=400px]]<br /> <br /> === 3. Access Power Devices ===<br /> Once connected to your Raspberry Pi, you can manage power for devices such as IPPower, IPX, or similar. To reboot your main imaging computer, open a web browser (e.g., Chromium) and enter the URL for your power management device (e.g., http://192.168.1.3).<br /> <br /> <br /> [[File:chromium.png|center|width=400px]]<br /> <br /> <br /> By following these steps, you should be able to restore connectivity to your telescope control system. If the issue persists, please contact Deep Sky Chile support for further assistance.<br /> <br /> <br /> [[Category:User manuals]]</div>

Cedric https://wiki.deepskychile.com/index.php?title=Lost_Connection_to_Equipment&diff=63 2024-11-15T16:03:11Z

<p>Cedric: </p> <hr /> <div>== Troubleshooting Connectivity Issues ==<br /> <br /> If you're encountering connectivity issues while trying to connect to the computer controlling your telescope in Chile, follow the steps below to resolve the issue.<br /> <br /> === 1. Connect to the Customer Platform ===<br /> Begin by opening your customer platform at [https://clients.deepskychile.com](https://clients.deepskychile.com) and log in with your credentials.<br /> <br /> [[File:login.png|center|width=400px]]<br /> <br /> <br /> Navigate to '''Tools''' → '''My Systems'''.<br /> <br /> [[File:tools-my_systems.png|thumb|center|width=400px]]<br /> <br /> <br /> Here, you can view the status of your system. The color of the system's indicator will tell you its current state:<br /> <br /> * '''Green''': System is online.<br /> * '''Red''': System is offline.<br /> * '''Black''': System is not yet installed.<br /> <br /> [[File:mysystems.png|center|width=400px]]<br /> <br /> <br /> If your system is online, proceed to '''Step 2'''. If it is offline, click on your system, and select '''Reboot my System''' from the menu. Once confirmed, the router will reboot. Wait for '''5 minutes''' before attempting to reconnect. If the system turns green after this period, the issue was likely related to the router, and you should be able to reconnect. If the system remains red, contact us for further assistance.<br /> <br /> [[File:mysystems-menu.png|center|width=400px]]<br /> <br /> <br /> === 2. Connect to the Raspberry Pi (RPi) ===<br /> The Raspberry Pi (RPi) is a dedicated 24/7 server installed on your network by Deep Sky Chile. If you cannot connect to your imaging computer, attempt to connect to the Raspberry Pi instead.<br /> <br /> Use '''AnyDesk''' or '''TeamViewer''' to establish a connection. You can find the necessary credentials in the '''My Systems''' section of your customer platform. Click on your system, and select your preferred connection method. The default password is '''DSChileRemote''' (please do not change this password).<br /> <br /> [[File:rpi.jpg|center|width=400px]]<br /> <br /> === 3. Access Power Devices ===<br /> Once connected to your Raspberry Pi, you can manage power for devices such as IPPower, IPX, or similar. To reboot your main imaging computer, open a web browser (e.g., Chromium) and enter the URL for your power management device (e.g., http://192.168.1.3).<br /> <br /> <br /> [[File:chromium.png|center|width=400px]]<br /> <br /> <br /> By following these steps, you should be able to restore connectivity to your telescope control system. If the issue persists, please contact Deep Sky Chile support for further assistance.<br /> <br /> <br /> [[Category:User manuals]]</div>

Cedric https://wiki.deepskychile.com/index.php?title=Lost_Connection_to_Equipment&diff=62 2024-11-15T15:58:16Z

<p>Cedric: </p> <hr /> <div>== Troubleshooting Connectivity Issues ==<br /> <br /> If you're experiencing connectivity issues when trying to connect to the computer controlling your telescope in Chile, please follow these steps to try and resolve the issue:<br /> <br /> === 1. Connect to Your Customer's Platform ===<br /> Open your customer's platform at [https://clients.deepskychile.com https://clients.deepskychile.com] using your credentials. <br /> <br /> [[File:login.png|center|width=400px|]] <br /> <br /> <br /> Then, browse to '''Tools''' → '''My Systems'''. <br /> [[File:tools-my_systems.png|thumb|center|width=400px|]]<br /> <br /> <br /> From there, you should be able to see the system states. The color of your system represents its state:<br /> <br /> * '''Green''': Your system is online.<br /> * '''Red''': Your system is offline.<br /> * '''Black''': Your system is not yet installed.<br /> <br /> [[File:mysystems.png|center|width=400px|]]<br /> <br /> <br /> If your system is online, proceed to step 2. If it is offline, click on your system. A menu will open. Choose '''Reboot my System'''. Once confirmed, your router will reboot. Please be patient and wait for 5 minutes. Do not attempt to reconnect during this time. If your system becomes green after 5 minutes, the issue was router-related, and you should be able to connect to your equipment as usual. If it remains red, please contact us for further assistance.<br /> <br /> [[File:mysystems-menu.png|center|width=400px|]]<br /> <br /> <br /> === 2. Connect to Your Raspberry Pi (RPi) ===<br /> A Raspberry Pi is a mini computer acting as a 24/7 server. It is always ON. At Deep Sky Chile, we install a Raspberry Pi on every customer's network. If you cannot connect to your imaging computer, first try to connect to your Raspberry Pi. Use Anydesk or TeamViewer to connect to your Raspberry Pi.<br /> <br /> [[File:rpi.jpg|center|width=400px|]]<br /> <br /> <br /> You can find the necessary credentials in your customer platform at [https://clients.deepskychile.com https://clients.deepskychile.com], under '''Tools''' → '''My Systems'''. Click on your system, and a menu will open. Click on your preferred connection method. The default password is always '''DSChileRemote'''. Please do not change this password.<br /> <br /> [[File:mysystems-menu.png|center|width=400px|]]<br /> <br /> <br /> === 3. Access Power Devices ===<br /> Once connected to your Raspberry Pi, you can control your IPPower, IPX, or similar devices to power on or reboot your main imaging computer. Open Chromium or any other web browser and enter the correct URL for your power management device (e.g., http://192.168.1.3) to power the desired equipment.<br /> <br /> [[File:chromium.png|center|width=400px|]]<br /> <br /> <br /> Following these steps should help restore connectivity to your telescope control system. If you continue to experience issues, please contact Deep Sky Chile support for further assistance.<br /> <br /> [[Category:User manuals]]</div>

Cedric https://wiki.deepskychile.com/index.php?title=File:Chromium.png&diff=61 2024-11-15T15:55:23Z

<p>Cedric: </p> <hr /> <div></div>

Cedric https://wiki.deepskychile.com/index.php?title=Lost_Connection_to_Equipment&diff=60 2024-11-15T15:47:36Z

<p>Cedric: </p> <hr /> <div>== Troubleshooting Connectivity Issues ==<br /> <br /> If you're experiencing connectivity issues when trying to connect to the computer controlling your telescope in Chile, please follow these steps to try and resolve the issue:<br /> <br /> === 1. Connect to Your Customer's Platform ===<br /> Open your customer's platform at [https://clients.deepskychile.com https://clients.deepskychile.com] using your credentials. <br /> <br /> [[File:login.png|center|width=400px|]] <br /> <br /> Then, browse to '''Tools''' → '''My Systems'''. <br /> [[File:tools-my_systems.png|thumb|center|width=400px|]]<br /> <br /> From there, you should be able to see the system states. The color of your system represents its state:<br /> <br /> * '''Green''': Your system is online.<br /> * '''Red''': Your system is offline.<br /> * '''Black''': Your system is not yet installed.<br /> <br /> [[File:mysystems.png|center|width=400px|]]<br /> <br /> If your system is online, proceed to step 2. If it is offline, click on your system. A menu will open. Choose '''Reboot my System'''. Once confirmed, your router will reboot. Please be patient and wait for 5 minutes. Do not attempt to reconnect during this time. If your system becomes green after 5 minutes, the issue was router-related, and you should be able to connect to your equipment as usual. If it remains red, please contact us for further assistance.<br /> <br /> [[File:mysystems-menu.png|center|width=400px|]]<br /> <br /> === 2. Connect to Your Raspberry Pi (RPi) ===<br /> A Raspberry Pi is a mini computer acting as a 24/7 server. It is always ON. At Deep Sky Chile, we install a Raspberry Pi on every customer's network. If you cannot connect to your imaging computer, first try to connect to your Raspberry Pi. Use Anydesk or TeamViewer to connect to your Raspberry Pi.<br /> <br /> [[File:rpi.jpg|center|width=400px|]]<br /> <br /> You can find the necessary credentials in your customer platform at [https://clients.deepskychile.com https://clients.deepskychile.com], under '''Tools''' → '''My Systems'''. Click on your system, and a menu will open. Click on your preferred connection method. The default password is always '''DSChileRemote'''. Please do not change this password.<br /> <br /> [[File:mysystems-menu.png|center|width=400px|]]<br /> <br /> === 3. Access Power Devices ===<br /> Once connected to your Raspberry Pi, you can control your IPPower, IPX, or similar devices to power on or reboot your main imaging computer. Open Chromium or any other web browser and enter the correct URL for your power management device (e.g., http://192.168.1.3) to power the desired equipment.<br /> <br /> Following these steps should help restore connectivity to your telescope control system. If you continue to experience issues, please contact Deep Sky Chile support for further assistance.<br /> <br /> [[Category:User manuals]]</div>

Cedric https://wiki.deepskychile.com/index.php?title=File:Rpi.jpg&diff=59 2024-11-15T15:45:03Z

<p>Cedric: </p> <hr /> <div></div>

Cedric https://wiki.deepskychile.com/index.php?title=File:Login.png&diff=58 2024-11-15T15:41:06Z

<p>Cedric: </p> <hr /> <div></div>

Cedric https://wiki.deepskychile.com/index.php?title=Lost_Connection_to_Equipment&diff=57 2024-11-15T15:39:57Z

<p>Cedric: </p> <hr /> <div>== Troubleshooting Connectivity Issues ==<br /> <br /> If you're experiencing connectivity issues when trying to connect to the computer controlling your telescope in Chile, please follow these steps to try and resolve the issue:<br /> <br /> === 1. Connect to Your Customer's Platform ===<br /> Open your customer's platform at [https://clients.deepskychile.com https://clients.deepskychile.com] using your credentials. Then, browse to '''Tools''' → '''My Systems'''. <br /> <br /> [[File:tools-my_systems.png|thumb|center|width=400px|]]<br /> <br /> From there, you should be able to see the system states. The color of your system represents its state:<br /> <br /> * '''Green''': Your system is online.<br /> * '''Red''': Your system is offline.<br /> * '''Black''': Your system is not yet installed.<br /> <br /> [[File:mysystems.png|center|width=400px|]]<br /> <br /> If your system is online, proceed to step 2. If it is offline, click on your system. A menu will open. Choose '''Reboot my System'''. Once confirmed, your router will reboot. Please be patient and wait for 5 minutes. Do not attempt to reconnect during this time. If your system becomes green after 5 minutes, the issue was router-related, and you should be able to connect to your equipment as usual. If it remains red, please contact us for further assistance.<br /> <br /> [[File:mysystems-menu.png|center|width=400px|]]<br /> <br /> === 2. Connect to Your Raspberry Pi (RPi) ===<br /> A Raspberry Pi is a mini computer acting as a 24/7 server. It is always ON. At Deep Sky Chile, we install a Raspberry Pi on every customer's network. If you cannot connect to your imaging computer, first try to connect to your Raspberry Pi. Use Anydesk or TeamViewer to connect to your Raspberry Pi. <br /> <br /> You can find the necessary credentials in your customer platform at [https://clients.deepskychile.com https://clients.deepskychile.com], under '''Tools''' → '''My Systems'''. Click on your system, and a menu will open. Choose your preferred connection method. The default password is always '''DSChileRemote'''. Please do not change this password.<br /> <br /> === 3. Access Power Devices ===<br /> Once connected to your Raspberry Pi, you can control your IPPower, IPX, or similar devices to power on or reboot your main imaging computer. Open Chromium or any other web browser and enter the correct URL for your power management device (e.g., http://192.168.1.3) to power the desired equipment.<br /> <br /> Following these steps should help restore connectivity to your telescope control system. If you continue to experience issues, please contact Deep Sky Chile support for further assistance.<br /> <br /> [[Category:User manuals]]</div>

Cedric https://wiki.deepskychile.com/index.php?title=File:Mysystems-menu.png&diff=56 2024-11-15T15:38:37Z

<p>Cedric: </p> <hr /> <div></div>

Cedric https://wiki.deepskychile.com/index.php?title=File:Mysystems.png&diff=55 2024-11-15T15:33:19Z

<p>Cedric: </p> <hr /> <div></div>

Cedric https://wiki.deepskychile.com/index.php?title=Lost_Connection_to_Equipment&diff=54 2024-11-15T15:27:07Z

<p>Cedric: </p> <hr /> <div>== Troubleshooting Connectivity Issues ==<br /> <br /> If you're experiencing connectivity issues when trying to connect to the computer controlling your telescope in Chile, please follow these steps to try and resolve the issue:<br /> <br /> === 1. Connect to Your Customer's Platform ===<br /> Open your customer's platform at [https://clients.deepskychile.com https://clients.deepskychile.com] using your credentials. Then, browse to '''Tools''' → '''My Systems'''. <br /> <br /> [[File:tools-my_systems.png|thumb|center|width=400px|]]<br /> <br /> From there, you should be able to see the system states. The color of your system represents its state:<br /> <br /> * '''Green''': Your system is online.<br /> * '''Red''': Your system is offline.<br /> * '''Black''': Your system is not yet installed.<br /> <br /> [[File:My_systems.png|thumb|center|width=400px|]]<br /> <br /> If your system is online, proceed to step 2. If it is offline, click on your system. A menu will open. Choose '''Reboot my System'''. Once confirmed, your router will reboot. Please be patient and wait for 5 minutes. Do not attempt to reconnect during this time. If your system becomes green after 5 minutes, the issue was router-related, and you should be able to connect to your equipment as usual. If it remains red, please contact us for further assistance.<br /> <br /> === 2. Connect to Your Raspberry Pi (RPi) ===<br /> A Raspberry Pi is a mini computer acting as a 24/7 server. It is always ON. At Deep Sky Chile, we install a Raspberry Pi on every customer's network. If you cannot connect to your imaging computer, first try to connect to your Raspberry Pi. Use Anydesk or TeamViewer to connect to your Raspberry Pi. <br /> <br /> You can find the necessary credentials in your customer platform at [https://clients.deepskychile.com https://clients.deepskychile.com], under '''Tools''' → '''My Systems'''. Click on your system, and a menu will open. Choose your preferred connection method. The default password is always '''DSChileRemote'''. Please do not change this password.<br /> <br /> === 3. Access Power Devices ===<br /> Once connected to your Raspberry Pi, you can control your IPPower, IPX, or similar devices to power on or reboot your main imaging computer. Open Chromium or any other web browser and enter the correct URL for your power management device (e.g., http://192.168.1.3) to power the desired equipment.<br /> <br /> Following these steps should help restore connectivity to your telescope control system. If you continue to experience issues, please contact Deep Sky Chile support for further assistance.<br /> <br /> [[Category:User manuals]]</div>

Cedric https://wiki.deepskychile.com/index.php?title=Lost_Connection_to_Equipment&diff=53 2024-11-15T15:25:36Z

<p>Cedric: </p> <hr /> <div>== Troubleshooting Connectivity Issues ==<br /> <br /> If you're experiencing connectivity issues when trying to connect to the computer controlling your telescope in Chile, please follow these steps to try and resolve the issue:<br /> <br /> === 1. Connect to Your Customer's Platform ===<br /> Open your customer's platform at [https://clients.deepskychile.com https://clients.deepskychile.com] using your credentials. Then, browse to '''Tools''' → '''My Systems'''. <br /> <br /> [[File:tools-my_systems.png|thumb|center|width=400px|]]<br /> <br /> From there, you should be able to see the system states. The color of your system represents its state:<br /> <br /> * '''Green''': Your system is online.<br /> * '''Red''': Your system is offline.<br /> * '''Black''': Your system is not yet installed.<br /> <br /> [[File:my_systems.png|thumb|center|width=400px|]]<br /> <br /> If your system is online, proceed to step 2. If it is offline, click on your system. A menu will open. Choose '''Reboot my System'''. Once confirmed, your router will reboot. Please be patient and wait for 5 minutes. Do not attempt to reconnect during this time. If your system becomes green after 5 minutes, the issue was router-related, and you should be able to connect to your equipment as usual. If it remains red, please contact us for further assistance.<br /> <br /> === 2. Connect to Your Raspberry Pi (RPi) ===<br /> A Raspberry Pi is a mini computer acting as a 24/7 server. It is always ON. At Deep Sky Chile, we install a Raspberry Pi on every customer's network. If you cannot connect to your imaging computer, first try to connect to your Raspberry Pi. Use Anydesk or TeamViewer to connect to your Raspberry Pi. <br /> <br /> You can find the necessary credentials in your customer platform at [https://clients.deepskychile.com https://clients.deepskychile.com], under '''Tools''' → '''My Systems'''. Click on your system, and a menu will open. Choose your preferred connection method. The default password is always '''DSChileRemote'''. Please do not change this password.<br /> <br /> === 3. Access Power Devices ===<br /> Once connected to your Raspberry Pi, you can control your IPPower, IPX, or similar devices to power on or reboot your main imaging computer. Open Chromium or any other web browser and enter the correct URL for your power management device (e.g., http://192.168.1.3) to power the desired equipment.<br /> <br /> Following these steps should help restore connectivity to your telescope control system. If you continue to experience issues, please contact Deep Sky Chile support for further assistance.<br /> <br /> [[Category:User manuals]]</div>

Cedric https://wiki.deepskychile.com/index.php?title=File:My_systems.png&diff=52 2024-11-15T15:23:27Z

<p>Cedric: </p> <hr /> <div></div>

Cedric https://wiki.deepskychile.com/index.php?title=Lost_Connection_to_Equipment&diff=51 2024-11-15T15:21:41Z

<p>Cedric: </p> <hr /> <div>== Troubleshooting Connectivity Issues ==<br /> <br /> If you're experiencing connectivity issues when trying to connect to the computer controlling your telescope in Chile, please follow these steps to try and resolve the issue:<br /> <br /> === 1. Connect to Your Customer's Platform ===<br /> Open your customer's platform at [https://clients.deepskychile.com https://clients.deepskychile.com] using your credentials. Then, browse to '''Tools''' → '''My Systems'''. <br /> <br /> [[File:tools-my_systems.png|thumb|center|width=400px|Your system status overview]]<br /> <br /> From there, you should be able to see the system states. The color of your system represents its state:<br /> <br /> * '''Green''': Your system is online.<br /> * '''Red''': Your system is offline.<br /> * '''Black''': Your system is not yet installed.<br /> <br /> If your system is online, proceed to step 2. If it is offline, click on your system. A menu will open. Choose '''Reboot my System'''. Once confirmed, your router will reboot. Please be patient and wait for 5 minutes. Do not attempt to reconnect during this time. If your system becomes green after 5 minutes, the issue was router-related, and you should be able to connect to your equipment as usual. If it remains red, please contact us for further assistance.<br /> <br /> === 2. Connect to Your Raspberry Pi (RPi) ===<br /> A Raspberry Pi is a mini computer acting as a 24/7 server. It is always ON. At Deep Sky Chile, we install a Raspberry Pi on every customer's network. If you cannot connect to your imaging computer, first try to connect to your Raspberry Pi. Use Anydesk or TeamViewer to connect to your Raspberry Pi. <br /> <br /> You can find the necessary credentials in your customer platform at [https://clients.deepskychile.com https://clients.deepskychile.com], under '''Tools''' → '''My Systems'''. Click on your system, and a menu will open. Choose your preferred connection method. The default password is always '''DSChileRemote'''. Please do not change this password.<br /> <br /> === 3. Access Power Devices ===<br /> Once connected to your Raspberry Pi, you can control your IPPower, IPX, or similar devices to power on or reboot your main imaging computer. Open Chromium or any other web browser and enter the correct URL for your power management device (e.g., http://192.168.1.3) to power the desired equipment.<br /> <br /> Following these steps should help restore connectivity to your telescope control system. If you continue to experience issues, please contact Deep Sky Chile support for further assistance.<br /> <br /> [[Category:User manuals]]</div>

Cedric