Jump to content

Stargazers Lounge Uses Cookies

Like most websites, SGL uses cookies in order to deliver a secure, personalised service, to provide social media functions and to analyse our traffic. Continued use of SGL indicates your acceptance of our cookie policy.

sgl_imaging_challenge_banner_android_vs_ios_winners.thumb.jpg.803608cf7eedd5cfb31eedc3e3f357e9.jpg

chrisshillito

Members
  • Content Count

    1,386
  • Joined

  • Last visited

Community Reputation

280 Excellent

About chrisshillito

  • Rank
    Dark Matter

Contact Methods

  • AIM
    No Thanks
  • MSN
    No Thanks
  • ICQ
    No Thanks
  • Yahoo
    No Thanks
  • Jabber
    No Thanks
  • Skype
    No Thanks

Profile Information

  • Gender
    Not Telling
  • Interests
    None I wish to share.
  • Location
    Bucks.
  1. Ady is correct. All those folks who platesolve and say they don't align are only half right. Plate solving itself doesn't cange anything, but the act of synching, which is usually an integral part of the plate solve goto sequence, is what performs the alignment and is what allows the mount/driver to provide position correction. This is exactly the same as one star alignment except you can align closer to target and without being centred on a star. I guess the ease and convenience of the plate solve / goto process means many folks don't have to consider exactly what is happening behind the scenes, but if you platesolve and sync you are performing alignment. Chris
  2. The autopec feature in eqmod will store the raw pe data captured to file (it can do this even if you don't want to create/apply a correction curve). This can then be loaded into pecprep for analysis. Chris
  3. Eqmod will by default move in a way that keeps the counterweights downward. If moving to a park position that is counterweights up then the move is performed such that the dec movement is completed whilst in a counterweights down position so that any counterweights don movement only occurs in RA. There is a video tutorial on youtube that illustrates the eqmod movement strategies. Chris
  4. No that's not correct. The direction/guide software simply tells EQMOD where in astronomical terms it wants the mount to point. However astonomical coordinates mean nothing to the mount motor controller. It is EQMOD that has to work out how to safely move each axis motor to a position corresponds to the astronomical coordinates it was given. Moving 360 shouldn't happen - but if its happening then one possible explanation is an EQMOD bug.
  5. Yes, you can manually position (slew) the mount anywhere you like - you're in full control and if you crash into the pier/trip that's your own fault. Limits are essentialy there to protect an unattended mount tracking into he mount/tripod.
  6. Yes it will hit eventually. The problem was not that you had limits enabled, it was that you had left them the default (meridian). EQMOD RA limits are configurable. You could for instance slew off to your target so the dec axis gets positioned appropriately - then manually slew round in RA until the scope is about to hit and set the RA limit just that point. Then go back to your target, start imaging safe in the knowledge that EQMOD will track through the meridian but will stop tracking before any collision takes place.
  7. EQASCOM and EQMOD are the one and the same thing. EQMOD is the name of the community project that produced the EQMOD ASCOM Driver (EQASCOM). The EQMOD project has produced other software but by far the most widely used is the ASCOM driver which folks got into the habit of refering to as simply EQMOD. Whilst EQASCOM is at its core an ASCOM driver it also provides lots of other mount control functionality (Polar alignment tool, Sky model, gampead interface, GPS interface, PEC, Audio prompts etc.) that are not typical of other ASCOM mount drivers. If those features matter to you, and in all other respects the IOptron and EQ6r are matched, then the EQ6r may be a better choice. Chris.
  8. ASCOM drivers are what enable ASCOM capable software to (planetariums, guiding automation etc.) control specific hardware (mounts, cameras, focusers etc.). The uniqueness of each piece of hardware is abstracted into the driver allowing the the controlling software to use a common "language" when requesting services from the drivers. The drivers then interpret the ASCOM requests as mount specific commands. So, if you want to control your mount via ASCOM you will need a specific ASCOM driver written for your mount type. EQMOD is an ASCOM driver written specifically for skywatcher mounts.
  9. Start EQMOD using the toolbox applicaiton that installs with EQMOD. The toolbox, unlike a lot of other ASCOM applicaitons, will not immediately close down EQMOD if connection to the mount fails - allowing you to see the error message EQMOD is most likely displaying.
  10. Yes. Append on sync wil at a new point to your pointing model every time SGP syncs. This can be a pain when using plate solving at yo end up with clusters of closely grouped alignment points (where as alignment points really want to be space out). You have two options: 1. Stay with "append on sync" but set the proximity range filter so that only the last sync point added within a proxiity range is actually used by EQMOD (any other sync points within the proximity range are automatically deleted from the model). If you have a permanmently sited mount doing this allows you to have platesolving build up/refine that, as you visit different targets, will improve the accuracy of any "non platesolved" gotos you may subsequently make. 2. Change to "Dialogue Mode" (orginally this was the mode used for manual, dialog led alignment). With Dialogue mode any sync received by EQMOD only acts to shift its current point model to align with that sync point - no new points are added. This is the more traditional implementation of a sync. Each time a new sync is made the correction shifts in RA and DEC (shown as DxSA and DxSB in EQMOD) will be recalculated based only on the current sync/posiiton offset. Most folks just go the route od option 2 - probably beacuse this iswhat was settled upon by a consensus of opinion on the SGP support forum many years ago (but that's not to say there aren't folks sucessfully using option 1). Chris
  11. If you can't remeber to park then put some thought into how to setup a resynch encoders position (maybe some distant terrestrial object you can see with a reticule eyepeice or a physical indicator on the worm shaft (EQ6Pro have a flat on the end). All you then have to do do is create a custom park with the mount at the position and whenever you want to reysnc just move the mount there (manually or under EQMOD control), select the resync as you current park option and hit the resynch encoders button.
  12. If the files have been timestamped then that should be apparent in their filename. IF you're having trouble finding the files in widows explorer try changing the location they are stored (an AutoPEC config option) - Later windows version can be a bit fussy about giving folks direct access to the Program Files subdirectory that is the default.
  13. If you go onto the Periodic Error Correction tab of PECPRep you will see a plot of the "residual error" tha twould occur if using your filtered data to correct the actual data that was recorded. If you over filter the result can be a larger residual error. You don't have to get a perfectly repeatable trace on PECPreps Analysis - just aim for a curve that does a good job of fittig your raw data whilst ttaking out high frequency noise and non periodic elements. PECPRep will average the results of each cycle when it comes to build the single cycle PEC curve anyhow so any discrepenceiws in the individual cycles will be averaged out. Chris.
  14. Note that the options highlighed are not EQMOD AutoPEC - this is a low level interface to provide limited control of skywatcher's PPEC (on the mount's that support it)
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.