Jump to content

sgl_imaging_challenge_2021_2.thumb.jpg.72789c04780d7659f5b63ea05534a956.jpg

cjdawson

Members
  • Content Count

    1,776
  • Joined

  • Last visited

Community Reputation

866 Excellent

3 Followers

About cjdawson

  • Rank
    Sub Dwarf

Contact Methods

  • Website URL
    http://cjdawson.com

Profile Information

  • Gender
    Male
  • Interests
    Astrophotography
  • Location
    Yorkshire UK

Recent Profile Visitors

5,518 profile views
  1. I use the 12v output to a cigar socket that comes with the Tracer battery. From there, I run power to Lynx Astro 4 channel dew controller, and 2 dew heaters (one for the guide scope and one for the main scope) The lynx astro output has 2*2.1mm 12v outputs. One I use for my ASIAir, the other is good for my EAF (in the post) and I have a splitter, so that I can run my ASI1600MM pro as well. If I upgrade to the AsiAir Pro, I can do away with the splitter. That's my setup. An alternative if you only USB Sockets is to get USB charger for a car, I've got one in my ca
  2. I attempted something similar to what you described and found that the 20K power bank didn't last nearly as long as I thought it would. The cold drains the batteries fast. I thought about insulating the power bank, and using one power bank for the mount and another for the heater, but then I got to thinking about it and realised that it was always going to be a problem. I also found that a dew heater that runs on 5V pulls huge amounts of power, and again will drain a battery fast. My solution was to forget the idea of running using 5v power banks that are not meant for the abuse that
  3. Hi @Priesters There is no concept of J2000 v JNow in the driver at all. So, I don't know what sharpcap is doing regarding conversions or where it is getting any idea that there is a difference from. There is a new release of the driver which I doubt will change anything in the accuract of platesolving. I have tried platesolving with Platesolve2 which I have working successfully, I'm also trying ASTAP. To date, I've platesolved with SGP, and have been a little dissapointed with it, the reason being that after the platesolve happens and the software issues a correction, it d
  4. I'd say a 40D or above. The 70D has wifi, whilst it sounds like a gimmick, for wide field, it opens an opportunity to do day to night timelapses using the "holy grail" technique, or even "Holy trinity" technique. Holy grail is where as the light levels drop, the exposure time is extended to capture more information, then once a certain level has been hit the ISO is bumped up to keep things going. The trinity also adds opening the aperture of the lens into the mix to even better results. I've got software for my iPhone called "Control my camera" that allows me to do this
  5. Thanks for the link. I suspected that SGP is doing a slew, after the plate solve, however the slew isn’t as accutate as using guide commands. What I’m thinking about is adding a feature to the driver that will find the current position of the scope, and if it’s below a given threshold distance, it’l use guide commands instead of doing a normal slew. This will allow the scope to work to greater accuracy, even though it’s doing repeated slew commands. I’ve got some more research to do on this before I start doing any coding, I suppose the biggest question that I have to overcome is figurin
  6. Ooo, that’s interesting. I’d love to know the details about that @michael8554 would you be able to find the link? I’m beginning to wonder if there’s something clever that I can do if the slew is for a small distance. I’m still thinking about this problem, and haven’t had a lot of time to work on it and don’t have access to my Lx-90 for the next couple of weeks.
  7. @jhart glad to hear that the driver is working great for you. I also have problems with getting platesolving perfect in SGP. I've got a project on the go to see if I can figure out what is going on and how to fix it. Hopefully I'll crack that at some point.
  8. Hi @pgoelz Got an update for you on this. Yep, I'm still working on things. 1. There is a bug in the driver when using an LX-200 classic. Which I've resolved with the help from an LX-200 Classic owner. 2. I think I've got an implementation of dynamic braking working in the driver now for the focuser. So would you be able to check this to see if it works? I don't have my Meade focuser plugged in at the moment. Here's a direct link to the development version of the driver, which should have these things resolved. https://www.dropbox.com/s/s4qzvpef6try
  9. Hiya. POTH - Plain Old Telescope Hub. iirc correctly that's what POTH stands for. And it's very old software, written in VB6 I believe. The device hub replacing POTH. I'm not sure of the details of exactly where things are with that at the moment. Something tells me that what you've seen with the installers is that the device hub might not be quite ready for prime time yet, so possible got pulled from the SP 1 install maybe. That's a guess so I could easily be wrong. As for adding support for dynamic breaking to the focuser implementation. I've not made much pr
  10. Hi Paul. Here's my initial responses.... 1. hmmm, that's something I'm going to have to look into. Not tried the device hub at all myself. I can't think of a reason why they'd be disabled. I might have to ask on the developer group what decides if those buttons are enabled or not. 2. focuser dynamic braking isn't implemented at this time. I'm using the old 5.0.4 driver as a source of information and it looks like this is a software feature. It's on to the todo list, but to be frank, I've found that the focuser has been very unreliable in hardware. 3. I'm going to have
  11. I released an update to the driver on 23-may which has an extra feature and if the driver fails to connect to the scope properly, it will put messages into the trace log. If you could try that one with trace logging on, it would be helpful to narrow down what is going on with that driver.
  12. Hi Douglas. Here's the response that I posted on my website to the same question.
  13. Hi @FrozenYack I created the driver using using my Meade LX-90 which also uses the Autostar, I did most of the work using the latest official firmware for it, I think it's 43Eg if I remember correctly. It's not really been change by meade in the last 10 or so years. I've also got an AudioStar handset, and have started using that in preference. That said it should not make any difference which of the two hand controllers you use, both work just fine. The EW being backwards seems a bit strange to me. Could that be a hemisphere setting related issue in your setup? I've
  14. I don't have the EQ3 Pro myself, it's something that I'm considering picking up at some point. That said, I'm very happy with my SA. There is also an alternative approach that you might want to consider as well. Rather than using a Tracer battery like I linked above.... Use several USB power packs, the internal battery in the DSLR and the AA's in the SA as well. This is a completely different way of thinking. Firstly, the SA documents says it'll run for several days from a set of AA's. You can get USB camera lens warmers - I have one that I have used and they work well.
  15. HI JudeHs I've got a Star Adventurer pro and use that for Deep Sky Imaging. Here's my setup that I'm using Mount: * Star Adventurer Pro (I'll call this SA For short) - https://www.firstlightoptics.com/skywatcher-star-adventurer/skywatcher-star-adventurer-astronomy-bundle.html * Sky-Watcher 3/8" Stainless Steel Tripod - https://www.firstlightoptics.com/skywatcher-star-adventurer/sky-watcher-38-stainless-steel-tripod.html Guide scope: * ZWO Mini Guide Scope - https://www.firstlightoptics.com/zwo-accessories/zwo-mini-guide-scope.html * ZWO
×
×
  • 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.