I found an excellent video on YouTube by AstroBlender that goes through his image train and backfocus calculation on a Celestron EdgeHD 9.25. His setup is very close to mine and he suggested the ASI174mm for the guide scope to better match the prism in the a Celestron OAG. I just wish it wasn't so expensive.

My ASI120MM mini just can't see much with the OAG and is not practical for guiding.


I didn't even think about trying the simulator! Thanks for taking the time. I guess I'm going have to look for things that are in a region with a lot of stars, or get a different camera. Could be an excuse for another astrophotography technology purchase!

I was using the ZWO ASI462MC for planetary imaging and I thought I would give it a try on some deep space objects. That's how I ended up there.


It's been cloudy here and probably remain so for the next couple of days. When it clears up I will share a FITS file from the Align module.


Thanks Jasem and Marc:

I reviewed the documentation you linked me to and reviewed my Astrometry FITS files. I'm going to give another try when the weather improves. It's clear that with my FOV I need to have sharp stars and enough of them to make it work. Might need to move to another camera with a wider FOV.


I have used Stellarmate successfully with my Skywatcher 100ED scope but now I'm trying to setup my Celestron Edge HD9.25 with Stellarmate.


  • Celestron EdgeHD 9.25
  • Skywatcher EQ6R mount
  • Celestron .7 Focal Reducer
  • Celestron SCT motorized focuser
  • Celestron OAG with ASI120MM for guiding
  • ASI462MC primary imager
  • ASI filter drawer
Everything connects successfully and I can control everything. The issue I am having is with stellarsolver. It fails whenever I attempt to align to a target. First thing I checked was to make sure I had the telescope setup correctly. The Celestron EdgeHD 9.25 has a focal length of 2350mm and an aperture of 235m. With the .7 focal reducer the focal length is 1645mm. The ASI462 appears to be setup correctly (checked all the parameters in EKOS). Calculating the FOV I get 11.73' x 6.64' and in the align module I see 11.7' x 6.6' for FOV and F/ is 7. Since it's an F10 scope, the focal reducer would make it F7 I believe. So, I think that is correct.

The error message solver failed ... there is not enough stars, check FOV...etc.

I'm hoping someone can suggest other things I should check. or other information I can provide that could help debug this issue.


Peter Greis replied to the topic 'Best FW for INDI compatibility?' in the forum. 2 years ago

Currently using the ZWO EFW with 5 2"filters. I recently added it to my configuration and it just worked. Although, I'm currently using a OSC for imaging, I have added a Optolong CLS-CCD filter and the L-extreme filter. The other filter is a Sybony dark filter for taking darks. Everything works smoothly and it's easy to select filters while you are imaging. Obviously with a mono camera you'll have different filters.


After running upgrade on the Pi4, I can confirm that now both the Pegasus Power Box Advanced (PPBA) and the Focus Cube II successfully connect.


UPDATE:  If I remove the focuser from the configuration, the Powerbox Advanced will connect. As was mentioned in the link ouioui01  provided, the port name is  truncated and that truncated name is saved, so it looks like it has to rescan to get the correct port name.

If I add the Pegasus focuser back in, then both the Powerbox Advanced and Focus Cube II will not connect.

Very frustrating.


Since upgrading to latest drivers (Indilib V1.9.0), I can no longer connect to the Pegasus PPBA and the Pegasus Focuser. These connected fine in the previous iteration. Error message is similar on both:

2021-04-26T02:14:34: [ERROR] Failed to connect to port (). Error: Port failure Error: No such file or directory. Check if device is connected to this port.

Port selected for Pegasus PPBA : /dev/serial/by-id/usb-Pegasus_Astro_PPBADV_revA_PPBA5A606G-if00-port0
Port selected for Pegasus DFMC :/dev/serial/by-id/usb-Pegasus_Astro_FocusCube_2_PA5EJ9N6-if00-port0

 Am I missing something that I need to do?


Peter Greis replied to the topic 'Ekos windows' in the forum. 3 years ago


Thanks so much for the tip! Worked!!



Peter Greis created a new topic ' Ekos windows' in the forum. 3 years ago

I moved the horizontal bar at the bottom of the Ekos window

that shows the notifications and the two buttons (options and clear) and I can't seem to get them back.

I can either look at the Ekos tab details I select or I can see the entire list of notifications and the buttons for that tab. There seems to be no point at which I can move the horizontal bar and get both.

Is there a way to adjust the bar so you can see both parts?


Peter Greis replied to the topic 'New User - A speed question' in the forum. 4 years ago


You're right. I attached the wrong screen grab. I have been using the copy of Astrometry on the Raspberry Pi. This speeds up the solve by about 10 sec. In looking at the timestamps in the logs, most of the time taken up in solving is uploading the image back to my laptop. Still not sure why remote solving would cause Indiserver to upload a captured image, when I'm solving on the Pi.?


I just received my Raspberry Pi4, so I'll be upgrading so I'm sure local solving will be faster. I had not considered using an SSD. Something I need to look into. Also, as I mentioned above, most of the elapsed time for an alignment iteration is taken up with uploading the image from my camera to my Windows laptop running KStars/Ekos. Still not sure why the software does that, when solving is done entirely on the Pi. If it didn't do that it would be a lot faster.

Thanks to both of you for offering good suggestions and ideas.