Search the Community
Showing results for tags 'maximdl'.
Found 4 results
Hi, After 6 months of waiting for the new deep-sky camera to reach my observatory,I discovered I have a real problem. All this time, the system was used only several times, with the purpose to make some deep-sky images using a planetary camera (an ASI 174 mono - see the topic HERE ). Using the set-up for this kind of images, the usual way to acquire images was altered. At some point I discovered that is more easy and reliable to make a synchronization from TheSky6 and not from MaximDL, as usual. This is the history. Yesterday night and the night before, after installing my new CCD camera on the rig, I started to redo the adjustments in order to have a good alignment, a good focus and have some decent pictures to evaluate the camera. But at this point, I had a nasty surprise. I inserted some screen shots to understand better what I want to explain (and perhaps I will not do it well because of my English). When I pointed in The Sky to a star and sent the "slew" command, the cross-hair on TheSky6 show me that the telescope is pointing to that star. But looking to the small planetarium from MaximDL, I sow that the crosshair here is not pointing exactly to that star, but a little bit apart from it, which shouldn't happened... Trying to synchronize the scope in Maxim with the star position, the scope stopped to move in sidereal. Actually, he stop at all. Doing the same thing first time in Maxim and then in TheSky, an error message from TheSky appeared. After rebooting the computer and started again all the programs, same thing happens. Sometimes, when first syncronizing in Maxim and then in TheSky, the error does not appear but the crosshair is jumping apart from the star in one program when is pointing in the other one and other way around... i am desperate, because I do not understand what is happen. Could anyone to give me a hint, please? Had anyone a similar problem before? How can I erase the sky model from TheSky and put it back on the same alignment with the model from Maxim (which apparently work good stand alone in conjunction with EQMOD)?
Hi all! I'm embarking on the autoguiding path... Obviously not everything is going smoothly... So, I have the new QHY5LII Mono for guiding on a Celestron 8x50 finder scope. I had already tried capturing images with maxim, from my main scope with the reflex on it. That seemed to work alright. I installed the ASCOM platform, the drivers from the qhyccd.com site (system & ASCOM), and also EZPlanetary. Maxim connects to the cam alright, but all I can get from the camera is noise, black images, or white overexposed images. I tried all USB gates, reinstalled a few times the drivers... I tried to capture images in the Guide tab, in the Expose tab... I tried with PHD2 as well, but no luck there either: only overexposed white images, or, when decreasing exposure time, gray to black images, but no details of what I'm pointing at at all... Also, strangely, my reflex shows only noise.... Meanwhile, I've seen all kinds of flashing patterns from the red LED on the QHY5... from fixed to slow flashing, to intermittent, to very fast flashes... I'm sure I'm doing something very basic wrong.... Any ideas? I tried looking at previous threads on this, but had no luck trying what was written there... Thanks! Gerhard
Are you using the artemisHSC or the ASCOM driver.. what's the difference? Seems my first imaging run since April has been thwarted by Maxim breaking the Atik HSC driver. I've been getting an intermittent VBS "overflow CInt" error in ACP and looks like this is connected to a camera temp reporting issue from Maxim. V6.8 & below worked fine. But V6.9 isn't reporting the temp. I switched to the ASCOM driver & it seems to be happy but I'm wondering if there's any difference? I've always used the ArtemisHSC driver since V5. Any one know what/if there's a difference between the two? Not much I've seen on the Atik site so far and the Maxim forum seems to have gone quiet on it.