Jump to content

sgl_imaging_challenge_2021_2.thumb.jpg.72789c04780d7659f5b63ea05534a956.jpg

symmetal

Members
  • Content Count

    1,437
  • Joined

  • Last visited

  • Days Won

    1

symmetal last won the day on December 21 2019

symmetal had the most liked content!

Community Reputation

1,022 Excellent

1 Follower

About symmetal

  • Rank
    Sub Dwarf

Profile Information

  • Location
    North Cornwall

Recent Profile Visitors

2,924 profile views
  1. The histogram is displaying the range from 1112 to 35399 and assuming the histogram is showing a linear display that makes the peak at around 28000 ADU which is fine. It's easiest to have the histogram showing the full range from 0 to 65535 to get a quick assessment of your ADU levels, rather than the min to max values of the image as you have. Alan
  2. The default setting in Firecapture is not to debayer when recording images as debayering, (to produce the colour image) takes significant processor time, particularly if you use higher quality debayer algorithms, so your capture frame rate will then drop significantly. So during recording the preview image is normally greyscale with the bayer grid pattern visible, and may also be lower quality if your capture PC is not high spec, to try to maintain the best capture frame rate. Use Autostackert to debayer the recorded mono image, and therefore create the colour image. Under the 'Color' men
  3. It's saying it can't find a config file, so what happens if you click continue. It may then create a default config file to work with. I'm assuming you've just installed the ascom driver. It's bad programming to create this error situation though. See if the config file actually exists where it's looking. Perhaps you need to install the Ascom driver using 'Run as 'Administrator' to overcome permission requirements for writing to C:\Program Data\ which is protected like C:\Program Files\ Alan
  4. The flats do show the same sort of patterning vlaiv. I would suspect a power supply issue. What is the source for the 5V USB supply for the 1600 as maybe it's struggling powering the guide camera as well, along with excessive interference noise on the 5V. Are you using a USB2 or USB3 cable to connect the 1600 to your computer. Try taking a flat without the guide camera connected to see if it's any different. Also try a different cable and/or computer to power the camera. Inserting a powered USB hub to supply the camera will also see if it's a power issue. I don't think the cooler 12V can
  5. Glad it's working now, at least with 2 programs. When I replied last night I didn't see the Eqmod screenshot you posted, (maybe you added it later), but the latitude displayed set off alarm bells. SGP gets all its location info from the scope, (Eqmod in this case), you can't set it in the program. CdC keeps its own location info and gets feedback from the scope for position display. NINA has an option to set location in the Telescope section of equipment. Whether it uses that for slewing purposes I'm not sure. Worth checking it's correct. Alan
  6. I think you meant to say the Alt should equal your latitude. As Merlin66 points out you seem to have the wrong location coords entered in Eqmod as your latitude is -27. Also for completeness the RA should show the RA at the meridian +/- 6 hours. This is because when viewing an object at the meridian the counterweight bar is always horizontal. The home position rotates the bar by 90 degrees (6 hrs) so it hangs down which is safer. Alan
  7. Dec should read +90:00:00 and Az should read 00:00:00 in the Northern hemishere default home position, (weights down and scope pointing North). If it doesn't then you've still got previous sync alignment points being applied. Expand the Eqmod window to show setup options and under 'Alignment/Sync' delete the sync alignment points by clicking the button to the left of the DxSA and DxSB readings. These should then read zero and your Dec and Az readings should also then be correct. You can also delete the 'Point Count' by clicking the button to its left too but I don't think this affects things i
  8. The phones GPS location should be fine, but if you want it accurately goto google maps, zoom in and right click over your house location. It will give your lat and long in decimal degrees as the first line of the popup info. You can convert that to DMS format here. Alan Edit: negative longtitude values as shown by google maps mean it's West of the Greenwich Meridian so you'd enter it as a positive DMS value but then add West.
  9. Just the same way as when you rotated the reticule through 180 degrees by rotating the RA axis, looking at a distant object during the day, to check the reticule was centre aligned on the RA axis. In this case, however, if you're polar aligned with the reticule centre over the NCP, when you rotate the RA axis, Polaris will rotate around the NCP following the line of the reticule circle as Polaris is around 45' away from the NCP. It may be worth mentioning that another reason for poor goto performance can be the mount clutches slipping if not done up tight enough, or grease has worked it w
  10. Your Mel Maz display indicates that the polar alignment is over 1 degree out in azimuth which is about two thirds the diameter of the polar alignment circle. The circle is about 1.5 degrees in diameter. As you say the polar clock doesn't have to set with 0 at the top as long as you judge where Polaris would be on a clock face, if you assume the 0 is at the top and 6 is at the bottom. You've done the 180 degree rotation test and the object in the centre didn't move so your polar scope reticule is correctly aligned with the centre of the mount RA axis. When you're accurately polar aligned y
  11. Betelgeuse is 22 degrees from Sirius and a one hour error in the time setting on your handset puts you off by 15 degrees so Dave's suggestion looks a likely answer. Alan Edit Assuming you're in the UK and your location is input correctly you need Time Zone set to 0, and Daylight Saving set to No which I assume your SynscanInit is displaying.
  12. Where's the fun in that. The cables may be out of stock too, like most other astro items at the moment. Alan
  13. Bryan, If you don't fancy soldering a D9 connector to the cut ethernet cable you can always use one of these adapters which have a wired RJ45 socket at one end wired to 8 D-type pins and a D9 shell. A standard ethernet cable then connects it to your Powerbox. You push the pins into the D9 shell in any combination you wish to make your adapter and then click-snap the shell into the casing. The cable colours are different to ethernet cable though so you have to check you have the right colours before pushing the pins home as once inserted you can't really remove them without a special tool. Any
  14. This is the wiring of the cable you need Bryan. It's unlikely the wires of the DB9 cable you currently have will fit into the RJ45 connector easily as they will be too thick. As the RJ45 cable shown uses standard ethernet T-568B pinout it would be easiest to cut one end off a network cable and solder a DB9 female connector in its place. The Ultimate powerbox V2 only has 4 wires on the RJ45 pins 3 to 6 and no 12V. The Ultimate powerbox V1 states it works with unipolar stepper motors. Most bipolar stepper motors can be connected to work in unipolar mode. The +12V is used for driving bi-pola
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. By using this site, you agree to our Terms of Use.