GithubHelp home page GithubHelp logo

Comments (4)

NameOfTheDragon avatar NameOfTheDragon commented on September 3, 2024

With open vs. closed, the fail-safe condition must be to report that the dome is open, since a false closed indication could be disastrous. Therefore, the software uses the following definitions:

  1. The shutter is considered Closed if and only if the closed sensor is asserted (making electrical connection).
  2. Open is defined as not Closed.

This can sometimes lead to a situation where the shutter visually appears closed by electrically it cannot be verified, so the default fail-safe condition is to report Open.

It is possible that manually using the toggle switch to close the shutter beyond where the closed condition has been detected, could lead to it being reported as open.

The way to check this would be to examine the log file to see what the firmware is reporting. Please attach a log file that demonstrates the issue.

If you are using the ASCOM driver, then you can find log files in C:\users\your-username\logs. Ideally, delete all existing logs, reproduce the problem, record the time that the problem occurred as accurately as possible (so we can correlate it to the log file).

If you are not using the ASCOM driver, then if you can use a terminal emulator to capture output from the firmware, we can probably use that. We can't really troubleshoot issues based on logs from third party software.

Please attach your log file to this issue as a file attachment (do not copy and paste text from the log file).

from firmware.

w4sm avatar w4sm commented on September 3, 2024

I connected to the dome, started a shutter opening and let it run for a few seconds, stopped the shutter with the software when it was partially open, closed the shutter with the software. At that point the display properly indicated "closed." I then manually closed it about half an inch more. The display showed "open." I then disconnected. The magnetic switch should have stayed closed during and after my brief manual change.
TA.Nexdome.Server-2020-08-24-HEP-PC_Stacey Mills-HEP-PC.log
This is obviously NOT a major issue, but doessn't seem correct either. Log attached. Thanks!

from firmware.

w4sm avatar w4sm commented on September 3, 2024

Is there anything else I need to do?

from firmware.

NameOfTheDragon avatar NameOfTheDragon commented on September 3, 2024

Closed due to inactivity (issue is over a year old)

from firmware.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.