Brian McBride created a new topic ' plate solving issues' in the forum. 2 years ago

I'm having trouble using the new topic editor.  Is there any documentation anywhere?  I'm gonna try <code> and hope it doesn't screw up again.

I can use Ekos on my mac to plate solve and polar align.  I'm trying to switch to a Pi and plate solving is failing. 

I can point my 'scope' at the sky, plate solve with the Pi and have it fail, then immediately switch to mac without changing anything and the mac plate solve works.

To investigate this I've been trying to create a reproducible test case of an image that I can use load and slew to plate solve that will work on the mac but fails on the pi.  And load and slew is behaving in an unexpected way, even on the mac.

I have the same image , laptop-3, in 3 formats. 
  • a .fits file captured and stored by the ekos camera module
  • the matching .CR3 raw file (from the camera SD card) from which the .fits file was derived
  • a .fit file produced by using Siril to convert the .CR3 raw file from the camera to .fit format

Load and slew will solve the .CR3 file, the Siril produced .fit file but not the .fits file saved by the camera module.  Log file attached of load and slews of those three files in that order.

For the first two files 8 solvers with different fields of view are created.  "Solver # 2, Low 2.91094, High 11.3438 arcminwidth" succeeds. 

I'm guessing that 2.9x to 11.34xx is the range of field of view widths the solver will search.  The scope's fov width is about 10.3 degrees (200mm lens, full frame sensor) so that is what one would expect.

For the third file, only one solver is started with a scale range of "Scale range: 17.6923 to 26.5384 arcsec/pixel" which is wrong (if I've interpretted the log correctly).  And the single solver fails.

Presumably something in the fits header (attached) tells it to restrict the search.  I may have misconfigured something to cause an error in the fits header.  I know the scope aperture is wrong 74 instead of  50, but that doesn't seem like a likely cause.

Any thoughts on what might cause this behaviour?

 

Read More...