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.

stargazine_ep25_banner.thumb.jpg.9e57eee22cad68fd6b67a87befeaa79b.jpg

Icesheet

Members
  • Content Count

    284
  • Joined

  • Last visited

Community Reputation

112 Excellent

About Icesheet

  • Rank
    Star Forming

Profile Information

  • Location
    Bergen
  1. I think it's fantastic that this service is offered, and it would really give me peace of mind but I must say I'm surprised that there is nothing official supplied with the scope to confirm this. Not that I would expect a detailed optical report but even just a piece of paper with the serial number of the scope saying 'Bench tested by Es Reid' with one of those digitised signatures. I wouldn't think that's too much to ask?
  2. When did you email? I'm absolutely certain you will get a reply and will get the issue resolved one way or another. However, jumping to complaints of poor service and threats to return when you don't get a reply the same day is a bit extreme don't you think?
  3. Thanks Alan! Yes I’m guilty of it myself and it tends to be you try to push it when you don’t have the data to do it. Always good to have the input from others. One of the main ways to improve
  4. Ok, without going right back to the start this is my best attempt at it. Not even completely sure what I done!
  5. Thanks @Adreneline! Now that I look at yours and mine side by side I completely agree. I had probably been looking at it so much I couldn’t tell anymore. Actually I had this previous version that has a more neutral background (although I see there’s still a slight magenta tone) but I couldn’t get the ‘pop’ I wanted from the Galaxy so I must have pushed it too much trying to do that. You’ve got the best of both now. I’ll have a search around to see if I can do similar in PS
  6. M31 was one of my first images when I first caught the astrophotography bug and I hadn’t imaged it since. This one was shot with my Esprit 100 and a modded Canon 1000D (guided by an ASI1600 as I’ve been waiting months for my new guide cam!) 20x300’ lights 10 Darks, 30 bias, 30 flat Stacked in DSS and processed in PS I have been back and forth with the colour and saturation trying to find a balance between that and the noise. Had to stop somewhere so here it is. As always any constructive comments more than welcome At least I can say I have made an improvement from my first effort
  7. I'm looking to add an OSC camera alongside the ASI1600mm I already have. For various reasons, but also because I have the itch for something new again! I would like to use some of the OSC data I collect to compliment Ha or L data from the 1600 as well as imaging with it in it's own right. So what are the key factors I should be looking for to ensure the best pairing possible? Sensor size obviously. How important would pixel size be? For example would the the 4.6um of the ASI294MC pair well with the 3.6um of the ASI1600mm? What else I should be thinking about?
  8. I have about an hour of HA with it on an ASI1600 unguided (no calibration frames here). I know my spacing isn't right and it turns out I had some tracking issues so stars aren't perfect but with that considered I think it shows promise. I have noticed from some of the threads around on it that it does seem to display blue bloat. It's only really noticeable when you pixel peep or on really bright stars. Since for me this is primarily a back up lens and for really widefield it's a trade off I think I'll be happy to live with, and as Adam says it can be further corrected in processing. In any case the versatility and compact nature of it more than makes up for it for me. I've actually been using it mostly as a daytime spotter with a TV Pan 15mm and it's been excellent. Sharp, bright and contrasty. Only real downside is it doesn't handle glare well. I also plan to use it as a guide scope.
  9. Well, I've made some progress on this and mostly it is good news. I've only had an initial response from iOptron and since I only have about a week left for a return I decided to make use of some cloud free hours and load it up again. It didn't start out well. iPolar wouldn't connect and neither would the mount via USB. I double checked all drivers and everything was up to date. I was about to pack it in when I tried one more time. This time I held the USB cable firmly in place and it finally connected. I tested this with the mouse pointer problem too and it seems it is directly related to the connection. When I held it in place the mouse moved normally, when I let go the pointer went crazy again. Anyway, I managed to get polar aligned (turns out it wasn't that good) before Polaris clouded out. I slewed over to a clear part of the sky and put the mount on sidereal. For the first 5-10 secs it made the buzzing noise but then it suddenly stopped. I don't know why but it didn't come back for the rest of the night. I then set up the mount in PHD2, ran a calibration, guide assistant and let it track for about an hour. The results are attached, which suffice to say I'm very happy with. If the GA is to be believed my PE (~6arcsec P-P) is actually even better than the provided curve measured by encoder (~10arcsec P-P). Could there an error in the PHD2 guiding assistant? So there appears to be no mechanical issues and I may even have a better than average sample so now I really don't want to let it go. Having said that I can see myself getting fed up holding the USB in place when I need to polar align or have to do anything on the laptop. It also may rule out a remote session and what if the connection drops out in the middle of an imaging run. Is there any way I can secure the connection myself without having to send it away to get fixed? PHD2_GuideLog_2020-09-19_222040.txt
  10. Yes it had this on it (excuse the mess!). Balance was good. At least good enough anyway. Plus when it’s slewing it sounds fine. It only makes that noise when it’s tracking in sidereal. Actually the sound isn’t something I associate with something mechanical. It’s more like a buzzing with something electrical. Ive emailed iOptron and informed my dealer so fingers crossed.
  11. I'm using the 12v DC power supply that was delivered with the mount. Also, I am/ was using the USB B cable that was provided with the mount to connect to my laptop so that's not via the HC but straight from the laptop to a USB port on the mount. I did notice that the connection wasn't very secure right enough. The EQ6-R I had before had a similar USB port so I still had a cable from that. Tried that too. No success.
  12. I had my CEM40 mount out for the first time this evening and it quickly went downhill. I had downloaded all the drivers, ASCOM platform, iOptron commander etc and when I connected the mount to my laptop I got an error saying no iOptron product recognised. I then got an error message that the USB connection had failed. I had another USB-B cable so I tried that and got the no iOptron product recognised message again. I decided to try my ASIair Pro and this time I was able to connect to the mount but it made a strange noise when tracking. At first I thought this was related to the USB-B connection but the noise is apparent when tracking through the hand controller too. Furthermore, when I connected to iPolar it made my mouse pointer have a life of it's own (see attached videos). Can anyone suggest what the issue might be here? I'm praying this does not need to be sent back! Video_1.mov Video.mov
  13. As far as I’m aware it’s not been knocked but it must be tilt or something but then I’d expect it to affect more than just position 4. Ah well I guess it will need to come off and I’ll see. Fat fingers here I go
  14. Ok, no problem I’ll probably put it up on the sale section soon so you can let me know if it’s of interest
  15. I have an unused Sesto Senso autofocuser if you’re interested?
×
×
  • Create New...

Important Information

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