Results 1 to 8 of 8

Threaded View

  1. #1
    Join Date
    Nov 2005
    Location
    Virgil, NY
    Posts
    4,200

    Default AstroHaven Control

    Hi Bob,


    Anticipating that someday I'll be able to get my AstroHaven dome to respond automatically to weather events, in the meantime I've been running the ClarityII sensor and examining and comparing the BoltwoodFileTrace.log and corresponding BoltwoodFile.wsc code file (in your Weather Components folder), trying to tune the reported conditions to the actual conditions. I have a few questions and comments.


    I've attached five images: the Clarity app view, an ACP console view alerting a Very Windy condition, a snippet of the BoltwoodFile.wsc code, a portion of the trace log, and the whole trace log file corresponding (at the end) to this same alert.


    - Last, first. In the code file, I see at lines 635-638 the flags corresponding to clouds, wind, rain and daylight. These are parsed as bits(15-18). They are interpreted in the software correctly corrsponding to the Boltwood app. But up at line 605 the alert condition is bits(20) and not bits(19). Bits(19) would be the fifth number following the other four. This seems to be working correctly, too, so I'm don't know where my thinking has gone. I just wanted to point this out.


    - Near the top of the BoltwoodFile.wsc file, not shown here, is it necessary to keep DIAG_TRACE set to True? This has been helpful for setting up the initial conditions to provide alerts matching the real world, but when that's all sync'd up, can this trace file be disabled?


    - At line 206, in the SetupDialog(), the log file could be going to a Boltwood Systems folder in C/Program Files. In my setup the Boltwood software is installed in Program Files (x86). In any case wouldn't it be better for this to be in a location outside of the "system" folder structure (for example, in to DocRoots)? Just a thought.


    - When you issue an upgrade to ACP, are the Weather Component files typically rewritten, even if they've not been changed? I want to remove the conversion from Farenheit to Celsius and mph to kts. Personal preference. Wouldn't every Clarity user (other sensors too) set up the speed and temperature units to suit themselves - why do any conversion in the code at all? There is the "kt" in the SystemStatus weather annunciator, though...


    Thanks for considering all this. There's no big impact - I was just curious.
    Attached Images Attached Images
    Attached Files Attached Files
    Dick
    www.VirgilObservatory.us
    Pier-mounted Meade 12-inch SCT "classic"
    w. focal reducer to f/5.3 ~ FL 1630mm
    Optec TCF-S focuser
    SBIG CFW-8A and ST7-XME
    FOV ~ 15' x 10'
    H-alpha, BVRI, RGB & Clear filters
    MaxIm and, of course, ACP!
    AAVSO Code: BRIC

 

 

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. ASCOM AstroHaven driver
    By Dick Berg in forum Hardware/Software/Driver Topics Not Directly Related to Our Software
    Replies: 3
    Last Post: Jun 11, 2018, 15:07
  2. Astrohaven ASCOM driver?
    By Glenn Gaunt in forum Hardware/Software/Driver Topics Not Directly Related to Our Software
    Replies: 18
    Last Post: May 2, 2016, 16:28
  3. Experience With Astrohaven?
    By joshwalawender in forum Hardware/Software/Driver Topics Not Directly Related to Our Software
    Replies: 1
    Last Post: Sep 17, 2009, 12:38

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •