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.

sgl_imaging_challenge_banner_beauty_night_skies.thumb.jpg.2711ade15e31d01524e7dc52d15c4217.jpg

JBracegirdle

All Sky Plate Solver - Camera array data unsupported.

Recommended Posts

Good afternoon,

I'm still new to astronomy in general, my setup is explained in my previous post. I am trying to get plate solving working.

I can get results from Astrometry.net, and I can get All Sky Plate Solver to solve when given an image file, but I am trying to get it to work with my ZWO ASI224MC direct.

When I try "Click, Solve & Sync" I get an error "Camera array data unsupported."

I have my camera connected with ASCOM as ASI Camera (1). The Image Type options are Raw8, Raw16 and Y8. Raw16 is selected and seems to be the default. I have tried the others and they all produce the same error. I've tried it with and without MonoBin. Binning is set to 1 and Subframe to 100% (50% tried). Filter is blank.

I can connect to the camera in SharpCap via ASCOM (although it warns that it prefers native drivers). I've also tried the SharpCap native Plate solver with the astrometrics install from ASPS, it tries to solve takes a while, but can't find a solution. I also tried AstroTortilla, that reads from the camera but just returns "No solution in 0.0s". :(

I've tried a Google search for the ASPS error but it doesn't find anything. I have checked only one application has the ASCOM camera at once. Any suggestions would be appreciated.

Share this post


Link to post
Share on other sites

I've not really done any plate solving yet, but I think you need to enter camera and scope details so that the software can work out the fov. I think you have to download files which represents your setup fov for the software to compare.

I sure someone who knows better will come along soon!

Edited by Stargazer33

Share this post


Link to post
Share on other sites

you need to open settings in asps ,you need focal length of scope , camera microns , chip size etc  these give you the fov required to work out indexes required to download 

aspsCapture.JPG

asps2Capture.JPG

Edited by bottletopburly

Share this post


Link to post
Share on other sites

Thanks for your replies. I have the indexes and I have the focal length (with the focal reducer) from astrometry.net, solving doesn't seem to be the problem. It solves when given an image file, it just produces an error when it tries to capture an image from the camera via ASCOM.

What's extra weird is I can't find the the error it produces talked about on the Internet at all. I downloaded the program again, un-installed and re-installed it just in case the files had become corrupt, but it still produces the "Camera array data unsupported" error.

Share this post


Link to post
Share on other sites

so you entered sensor size and micron size and pressed button  retrieve from fits header choose a fits file image you have taken , that fills array and highlights indexes used in yellow ?

Edited by bottletopburly

Share this post


Link to post
Share on other sites

Yes that bit seems to work really well. I used the Index Installation Wizard and the Settings Assistant. Images from file solve fine. I like that you can press "Browse Solved Image" and see the image annotated and the celestial coordinates. It's just the camera connection that seems to be the problem.

SharpCap can see the camera and take images in native and ASCOM mode fine.

Share this post


Link to post
Share on other sites

May have misunderstood the issue, but you can't use ASPS to capture images.  It needs an image (jpeg or fits) captured by your imaging software.  This can either be used from within software (APT, for example) or loaded into ASPS running by itself.

  • Thanks 1

Share this post


Link to post
Share on other sites

Well if you can't use the camera to solve and it needs a file ASPS is working as expected. :) But what does the "Click, Solve & Sync" button do if not capture from camera? 

I have now got AstroTortilla working. It seems as though the Cygwin install file is out of date. I used the latest Cygwin setup-x86.exe and that installed but seemed to break Astrometry. I fixed Astrometry by copying it from the ASPS cope of Astrometry to the C:/Cygwin folder and AstroTortilla works now.

SharpCap, ASPS and AstroTortilla are all using the same astrometry files now.

SharpCap is working 100% (after setting sigma to 6) - 15 seconds.

AstroTortilla works 100% - 19 seconds.

ASPS works with a file but won't capture from camera - 25 seconds.

Share this post


Link to post
Share on other sites

Thanks for your perseverance, I think I've gone as far as I can with the simulators and I've gone from just ASPS working with a file to:

ShapCap working with the camera.

AstroTortilla working with a file or the camera.

ASPS still working with a file.

All 3 solvers now use the same base Astrometry files, so saving hard disk space. I'm happy with that, there is nothing I can't do with that setup. I'll try a near solve with ASPS when the clouds / storm Deirdre pass by. Thanks again for all your help.

Share this post


Link to post
Share on other sites

ASPS will blind solve but may take a while ? - there is no way to put in RA/DEC as far as I know  (only if the mount if connected or you do command line calls to ASPS) - the results are for results ?.  See 

ASPS uses Fits or JPG so make sure the output from the Ascom camera can produce Fits or JPG images.

if you take a couple of images (JPG or Fits or both)  that your camera (ASI224) has taken via the EXACT SAME Ascom camera as you tried to use in ASPS and see if they solve - you may have done this but i didn't see that you used the same Ascom settings. If they solve ok then its the Ascom interface not being used correctly by ASPS  - support does seem to be none existent now days ?

If they don't solve double check your settings including J200/JNow etc 

you can even try command line call to ASPS ?  see manual below

Maybe the manuals might help http://www.astrogb.com/downloads/ASPS_CmdLine.pdf    http://www.astrogb.com/downloads/ASPS_COM.pdf ?

  • Thanks 1

Share this post


Link to post
Share on other sites
1 hour ago, stash_old said:

ASPS uses Fits or JPG so make sure the output from the Ascom camera can produce Fits or JPG images.

 

Thanks that seems to explain what's happening. I think the ZWO ASCOM driver just produces a RAW output, so that's probably the reason it doesn't work. Considering all the plate solvers that do work and I'm not missing any features I'm happy. I do like ASPS's result viewer, thankfully it works with JPGs and FITS.

  • Thanks 1

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Cosmic Geoff
      Finally some clear skies on the 7th and I did not have to be anywhere else, so set up my EEVA rig to have a go at three comets, + M33 and M1.
      Rig = 102mm Startravel achro, SLT mount, permanent wooden tripod and ASI224MC camera.  This is not a 'designed' setup, just gear I owned already.
      With the aid of Precise GoTo, Platesolver2 and some live stacking in Sharpcap, I obtained images containing faint fuzzy blobs for the comets C/2017 T2 (PANSTARRS), C/2018 N2 (ASASSN) and C/260P McNaugt.
      Turning to M33 (which I have never seen before despite trying on a number of occasions including in rural Scotland), I got a stacked image of some faint nebulosity. Definitely something there but not spectacular.
      I had likewise never seen M1, but using the gear showed an unmistakable grey oval blob which became clearer with some stacking.
      Altogether a satisfactory night's work. Typical stacks were 5 x 6sec exposure.  Moon - gibbous. Semi-urban sky.
      Platesolver2 solves in about 1 second on a Dell Vostro laptop.
    • By Cosmic Geoff
      On 22 Oct I had a go at EEVA with the moons of Uranus, using my CPC800 and the ASI224MC (and flip mirror)
      The image with about 5 sec exposure looked exciting, with several little dots in a line around Uranus's overexposed blob.  But when I analysed it later I found that I had imaged several 13th mag. background stars, and noted Oberon as a definite ID and Ariel as possible.  The seeing was bad.
      The moons are clearly within the range of this setup, so I will try again sometime and see if I can secure a set of stackable images.  The Sharpcap live stacking wouldn't work on this occasion.
      I needed Calsky to identify and eliminate the background stars, but it unhelpfully notes the moons as 'beyond the range of amateur telescopes.'  The Sky & Telescope tool identified the moons.
    • By Oslet
      Sooo...I'm getting quote frustrated here. This spring I tested my HEQ5 with guiding. The synscan controller was connected to the computer trough the USB plug on the hand controller. This worked like a charm in my living room. On the new controllers you dont need the rs cable. But when I tried the whole thing with guide cameara for some live shooting, it just did not work. I get something wrong with the com port in decice manager, driver not working. I have tried 3 different drivers. The whole thing responded, connected and was guiding when i did a dummy test before the summer. So setup is pc-synscan via usb for pulse guiding. Can it be a problem with windows 10? What t h.... just happened? Where can I find a driver that works? And believe me it worked 5 months ago, argh. Thanks for any respons and support
    • By Cosmic Geoff
      Africano captured EVA style with 102mm f5 Startravel achromat, ASI224MC on SLT mount.   Field is angled around 45 deg to lat/long. Comet near bottom of frame next to TYC2285-216-1
      19 Sept around 22.30 BST

    • By Cosmic Geoff
      I have been plate solving some starfield images with All Sky Plate Solver and found that the solve time was measured in minutes. I presume that it shouldn't take that long and that the elderly PC is to blame.  (Intel Core 2, 6320, 1.86GHz x2, 2GB memory).
      Can anyone suggest a PC spec that will reduce the solve time to seconds? It seems time for an upgrade anyway, and I was thinking of getting a used business PC as they are available cheaply from re-sellers.  I'm typing this on another one that cost under £100.
       
×
×
  • Create New...

Important Information

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