Interesting. My PN40 is officially only speced for 19V, but I run it on 12V all the time, without issues. After all there's nothing within such a computer that runs on 19V - that (most of the time) is only to guarantee a stable 12V when converted down. So I'd just try it with 12V. You might just need a strong enough PSU or large enough battery that doesn't drop below 12V, as an i7 might well need some power...
Read More...
Go to 'Scale & Position' and disable hinting ("Use Scale", "Use Position")
And/or try other "Option profiles" for the Stellarsolver
Read More...
If it doesn't find stars, check the setting of the stellarsolver profile. If it finds stars, but doesn't solve, check what you entered for the focal length of your telescope, and whether the camera pixel size is correct. The pointing of the mount should be good enough to be half-way close to where you want it to point.
If there's an uncertainty in either of those two, go to the options and disable hinting for scale and position. It will then do a complete blind solve, which can/will take longer, but should succeed eventually. Then you can use the scale/focal length determined there as default, and/or sync the mount to proper coordinates.
Oh, and verify that you have the needed index files for the FOV of your camera.
Read More...
Yes, I tried that lately. But when I switched to 2x2 bin it didn't find darks and disabled the option, which I forgot to re-enable when I switched back to 1x1....
I only found the setting in the SEP profile (star area), and a maximum HFR in the guide section. Did I overlook something?
Read More...
Well, if you intend to re-use the calibration, you definitely should do that one calibration for declination close to zero (celestial equator) and near the meridian (max. altitude). The guider then automatically scales the result to whatever location you are pointing at. This has always worked perfectly for me, both with PHD2 and now with the internal guider.
Calibrating at high declination (north or south) is suboptimal anyhow, because the RA movement of the star is reduced by a factor cos(DEC). This can easily make the guide star movement drown in noise, unless you use long (and many?) steps....
Read More...
Yeah, I'm guilty there - I still only run the sequences from the capture module... For my conditions here usually the temperature refocus and only-start-if-guideerror-below settings are enough to keep me running all night.
But the point was rather the hot pixel issue, as I'm quite sure that is what happened, as my mount has RA encoders that by themselves would never drift off that much. Maybe the guide section should also get a 'minimum HFR' setting? Or is something like that always active?
Read More...
Hy,
another issue that maybe you can comment on:
Two nights ago, when I had tested the new version, I had put my guide camera in 2x2 bin mode and forgot to set it back. During that session, I had some really weird (and bad) guiding errors. Guiding would be great, until suddenly it would start to oscillate:
Those excursions came back several times (roughly half an hour spaced), so I assumed there might be something with the belt of the RA axis.
It went away after the meridian flip.
Last night, I got a similar behavior right from the start. What I had noticed was that the jump/error was about 3 arc sec, which is the (binned) pixel size of the guide cam, and RA and DEC were basically in anti-phase... that really looked artificial to me.
I switched back to 1x1 binning, and the problem was gone.
Now I wonder if anything in the code could trigger such an error, or if maybe the binning algorithm is unstable somehow. Or do you have other ideas?
This is an ASI1600MM. I use multistar SEP/guide profile and GPG.
Pit
Read More...
Guess I was bitten by that, too, last night. Clouds at 1am, that went away again around 3am. Capture never aborted, but somehow the FOV had drifted half a degree, so the remaining 3h of (good quality) data were off-target 
Read More...
Just from curiosity: Is there a specific reason why you don't keep/re-use the calibration? At least during one night's session that should work.
(I'm using my guide calibration for months. My mount is fixed on a pier, though, and the OTA setup is also fixed, I just schlepp it out and put it on the mount. But as I said, as long as your mount has goto and supports pier side reporting one calibration per night should be enough...)
Read More...
Have you tried to enable verbose logging, and check the log for hints what it doesn't like?
Read More...
Thanks for your detailed analysis Hy!
I agree, changing it might cause even more head-scratching than in it's curent state (and lots of threads, e.g., on CN, confirm that...). Even more as the quasi-standard PHD2 uses guider pixels, too.
But the idea that additional info box doing the conversion for you I really like. 
Read More...