I know the image is easily solvable - the problem is that for some reason, ASTAP thought the target was centered. It started off centered by ASTAP just fine, but over time, the target drifted down. It was when I attempted to recenter the target that something went amiss, and what you see is the result.
Is there any reason for portrait mode? Not that I'm aware of. It's something that just seems to happen and I really have no idea why. I've gone back through several directories of images and sometimes they are all portrait, or all landscape, and sometimes they start off landscape and turn to portrait.
I just took a dark with "Capture and Solve". I hope it contains what you need: drive.google.com/file/d/13oM2uJ4b0j8x-tD...m0R/view?usp=sharing
It's cloudy here tonight so no imaging.
Under "Solver Options", the downsample was set to 2 and "Auto" is checked.
However, under ASTAP, binning was set to '2' - I've now changed it to '0'.
As for a FITs file - no such luck under /tmp. Is there another /tmp directory perhaps? Or perhaps I don't have a save feature enabled? Sorry, I hope I'm not sounding like a complete idiot.
I capture .NEF for imaging. I converted one to .jpg and uploaded it to astrometry.net. Here is a link to the results page: nova.astrometry.net/user_images/3731902#annotated
M16 started off dead-center and perfectly framed. However, some issue with dithering caused the image to drift downward, and when I attempted to recenter, it said it was within tolerance. M17 was far worse - right at the bottom edge of the screen.
Han - I did not know 0=automatic!
Stash - this is not the software, I'm sure.
Jerry - thanks for that! I think you nailed it as that is exactly the scenario.
Last night, I had quite a bit of success, but also an annoyance. ASTAP generally solved in seconds, and reslewed the scope to center the object, and I was very happy *except*:
ASTAP more or less centered Vega, but it also failed to solve once Vega came on screen. I told it to try again and this time it solved. But it never put Vega dead-center and instead left it a bit high.
ASTAP would not center M20 at all. Even when I changed the accuracy threshold to 10 arcsec, it placed M20 at the edge of the frame. As such, I was unable to image M20 - a good thing really - I needed to get more M16 data anyway. But it was odd nonetheless.
ASTAP centered M16. I set up for 100 60s shots w/dithering. Somewhere along the line, M16 drifted down in the images. I attempted to recenter but ASTAP said it was within tolerance.
I did NOT try any other platesolving.
Any idea what setting I might have wrong that would cause all this? Likely candidates?
Thanks a bunch and clear skies!
So, last night I had an opportunity to try ASTAP last night with pretty good results.
First go, with the scope in the park position (pointing north toward pole), I did a "Capture and Solve" with "do nothing" checked. ASTAP solved almost instantly!
Second go - slewed toward Vega and tried again. It solved, tried to move the scope, *FAILED*. I reduced the exposure time until it solved, but now it was stuck in a loop. I upped the exposure and noted star trails. "I don't think it's tracking," I said to my wife keeping me calm. Turned out my RA cable had popped out.
Third go - slewed toward Vega and tried again. Solved, slewed the scope. With Vega in view, it *FAILED*.
I clicked on "Capture and Solve" again - this time it solved, moved the scope, solved again, and now Vega was centered.
I now wanted to check my new knowledge re: PHD2, but first I had to change guide cam (I had swapped things around when using the Windows Stick).
After changing the guide cam from ASI120MM to SSAG, my Pi failed to boot. I tried several times and even with different uSD cards. NADA. @#$%! Turned out I may have lost my new powered USB3 hub - removing that from the link, the Pi came up and all was good, though I had lost quite a lot of time.
Main thing is ASTAP did seem to work nicely. Not sure what caused it to fail that one time - perhaps tonight I'll try again
Thanks very much for the detailed reply! I am currently using it in stand alone mode and have already done what you suggest, except my search angle was only 20 degrees. I've changed it to 180 but it didn't help with this particular frame.
The "calibrate prior solving" generates a warning about flat █ █ █ █ █ █ Warning, could not find a suitable flat for ""! De-classify flat filter or add correct flat. █ █ █ █ █ █ . I did try adding a flat manually and doing a simple stack of that plus an image, but that generated an actual error (something to do with Simple empty???).
Over the course of the afternoon, I've been trying with a variety of images and have been surprised at times. A couple of shots from my QHY cam (which is pretty noisy for what I was doing) solved. A couple more didn't. No shots of M16, whether from the QHY, my Nikon, or my wife's Canon, solved.
Unfortunately, it is cloudy now and predicted all through the night. Rain tomorrow. Clear skies supposedly on Saturday night - we'll see.
I copied over an old .NEF pic of M42 and it solved in 2.4 seconds! I tried the same with an old .NEF of M51 - failed. The difference I could see was the amount of vignetting - the M42 shot had none that I could see whereas the M51 shot was pretty apparent. I tried several other pics, all with substantial vignetting, and none of them solved. I can't help but wonder if that's the problem and if I were connected to my scope pointing at an object and able to capture much shorter image where vignetting would be far less pronounced if it would all suddenly work. Maybe?
I use the astrometry.net solver, but I've heard so many good things about ASTAP being so quick I wanted to give it a try.
I would like to try ASTAP. I have it installed in /opt/astap. I have G16 and G17 installed. I can bring up the program from the command line ./astap once in the subdirectory, and Ekos invokes it when I have it checked. But it cannot solve. Obviously, something is setup wrong.
I am using "simulators" at present and am trying to solve a pic I took earlier this month using my C8 w/6.3 focal reducer. Telescope should be 203mm, fl=1260mm. Guide scope is 30mm, fl=120mm. Camera is a Nikon D5100, 4.78u pixels, 4,928 × 3,264. All these parameters are plugged into the simulator.
When I click "Load and Solve", ASTAP opens a small window upper left of the screen, goes through the motions, then times out after 180 seconds without solution. Something is amiss.
Have I included enough info, or do I need logs for ASTAP, too? If so, where would the ASTAP logs be?
I've a similar problem re: wifi network/hotspot.
My old Pi4 running Astroberry 2.0.1 died suddenly, and today I received a replacement. I thought I could simply pull the uSD card from the defective one, plug it into the new one, and presto. But this Pi4 is not working the same as the old one. It apparently does not detect my internal network. So, it comes up in hotspot mode.
Funny enough, Stellarmate OS did exactly the same on the old Pi4, the primary reason I switched to Astroberry. Thoughts?
Reshot the darks and bias files and got this:
I tried M97 again last night without much success. I then turned attention to M51 and got a different result:
Initial (no flats/bias/darks):