Peter Greis replied to the topic 'Best FW for INDI compatibility?' in the forum. 2 months 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.

Read More...

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.

Read More...

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.

Read More...

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?

Read More...

Peter Greis replied to the topic 'Ekos windows' in the forum. 9 months ago

Bart:

Thanks so much for the tip! Worked!!

Peter

Read More...

Peter Greis created a new topic ' Ekos windows' in the forum. 9 months 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?

Read More...

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

Hy:

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.?

Jo;

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.

Peter

Read More...

Peter Greis replied to the topic 'PNew User - A speed question' in the forum. 1 year ago

Paul:

I think I have everything set correctly. As you suggest, it's really making sure you're close to where you think it is. I have used the iOS app and the Wifi dongle to do a two star alignment on the EQ6R before running Kstars/Ekos to choose targets. Last night having carefully done that, I was able to get align to work in 2 iterations.

Peter

Read More...

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

Hy:

I've attached a screenshot of the Align module and solver options.

The bin option on the Align module is grayed out. Down sample is set to 2. So I'm consisting getting about 70-90 sec for a remote solver iteration. As you can see last night I was able to solve in two iterations. I still think the issue is the downloading of the image to my laptop running KStars/Ekos. Since it is solving the image remotely on the Pi, why does it download the image to my laptop? When I take an image sequence and capture the image remotely on my Pi, it only takes about 10 sec from completing the image capture before I can view the image on the Pi.

Thanks for hanging in with me to see what improvements I can make. So far everything else seems to be working ok.

Read More...

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

hy:

It's been awhile, but I have been testing and experimenting with your suggestions.

So here's what I have seen using the Alignment module:

It takes 1 sometimes up to 2 1/2 minutes from "exposure done" to "image received" using the online solver. It typically takes from 90 to 160 sec for the solver to complete:

[2020-08-02T22:47:12.246 Eastern Daylight Time INFO ][ org.kde.kstars.ekos.align] - "Capturing image..."
[2020-08-02T22:47:12.271 Eastern Daylight Time INFO ][ org.kde.kstars.indi] - Canon DSLR EOS 77D : "[INFO] Starting 15 seconds exposure. "
[2020-08-02T22:47:34.074 Eastern Daylight Time INFO ][ org.kde.kstars.indi] - Canon DSLR EOS 77D : "[INFO] Exposure done, downloading image... "
[2020-08-02T22:48:57.199 Eastern Daylight Time INFO ][ org.kde.kstars.ekos.align] - "Image received."
[2020-08-02T22:48:58.024 Eastern Daylight Time INFO ][ org.kde.kstars.ekos.align] - "Solver iteration #1"
[2020-08-02T22:48:58.575 Eastern Daylight Time INFO ][ org.kde.kstars.ekos.align] - "Uploading file..."
[2020-08-02T22:50:10.007 Eastern Daylight Time INFO ][ org.kde.kstars.ekos.align] - "Upload complete. Waiting for astrometry.net solver to complete..."
[2020-08-02T22:51:38.925 Eastern Daylight Time INFO ][ org.kde.kstars.ekos.align] - "Solver completed in 161 seconds."
[2020-08-02T22:51:38.991 Eastern Daylight Time INFO ][ org.kde.kstars.ekos.align] - "WCS information updated. Images captured from this point forward shall have valid WCS."
[2020-08-02T22:51:38.993 Eastern Daylight Time INFO ][ org.kde.kstars.ekos.align] - "Solution coordinates: RA (21h 01m 52s) DEC ( 68° 14' 28\") Telescope Coordinates: RA (21h 01m 52s) DEC ( 68° 14' 55\")"
[2020-08-02T22:51:38.993 Eastern Daylight Time INFO ][ org.kde.kstars.ekos.align] - "Target is within 00° 00' 26\" degrees of solution coordinates."

If i use astrometry on the Pi3, takes from 40 sec to over a min from "capturing image" to "image received" and 1 1/2 min to 2 min to solve:

[2020-08-02T23:52:11.655 Eastern Daylight Time INFO ][ org.kde.kstars.ekos.align] - "Capturing image..."
[2020-08-02T23:52:11.765 Eastern Daylight Time INFO ][ org.kde.kstars.indi] - Canon DSLR EOS 77D : "[INFO] Upload settings set to client only. "
[2020-08-02T23:52:11.768 Eastern Daylight Time INFO ][ org.kde.kstars.indi] - Canon DSLR EOS 77D : "[INFO] Starting 15 seconds exposure. "
[2020-08-02T23:52:33.359 Eastern Daylight Time INFO ][ org.kde.kstars.indi] - Canon DSLR EOS 77D : "[INFO] Exposure done, downloading image... "
[2020-08-02T23:53:11.049 Eastern Daylight Time INFO ][ org.kde.kstars.ekos.align] - "Image received."
[2020-08-02T23:53:11.052 Eastern Daylight Time INFO ][ org.kde.kstars.ekos.align] - "Solver iteration #1"
[2020-08-02T23:53:59.464 Eastern Daylight Time INFO ][ org.kde.kstars.ekos.align] - "Starting remote solver..."
[2020-08-02T23:53:59.641 Eastern Daylight Time INFO ][ org.kde.kstars.indi] - Astrometry : "[INFO] Astrometry solver is enabled. "
[2020-08-02T23:54:13.031 Eastern Daylight Time INFO ][ org.kde.kstars.indi] - Astrometry : "[INFO] Solving image... "
[2020-08-02T23:55:45.702 Eastern Daylight Time INFO ][ org.kde.kstars.ekos.align] - "Solver completed in 93 seconds."
[2020-08-02T23:55:45.728 Eastern Daylight Time INFO ][ org.kde.kstars.ekos.align] - "Solution coordinates: RA (21h 37m 45s) DEC ( 57° 28' 48\") Telescope Coordinates: RA (21h 36m 37s) DEC ( 57° 29' 21\")"
[2020-08-02T23:55:45.728 Eastern Daylight Time INFO ][ org.kde.kstars.ekos.align] - "Target is within 00° 16' 53\" degrees of solution coordinates."
[2020-08-02T23:55:45.743 Eastern Daylight Time INFO ][ org.kde.kstars.ekos.align] - "Syncing to RA (21h 37m 45s) DEC ( 57° 28' 48\")"

What I find interesting is that when I am capturing images in the CCD module locally to the Pi3, it takes only about 10 sec from image captured until I can view them on Pi3.

I was thinking that the difference is that the alignment module is sending a copy to Ekos running on my laptop as well as capturing it on the Pi, thereby making the process much longer. If I'm using Astrometry for solving on the Pi, why would it send an image to EKOS on laptop?

Thanks for all your help

Peter

Read More...

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

Hy

Cloudy skies, so I haven't had a chance to try it again and post my setup.

Peter

Read More...

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

Hy:

Thanks so much for your detailed and quick reply! As I mentioned, I'm using a Raspberry Pi3B while I wait for my Pi4. I have installed Astrometry on the Raspberry Pi and have tried using it for alignment and it works (occasionally I get solver timed out message), but slowly. I'm going to give ASTAP a try. Thanks for the tip. Based on your experience, I now see what's possible.

I'll post back with my results. One other question, are there some setup parameters that I should change for the mount (EQ6-R Pro) to improve the solving process (i.e.. less iterations).

Regards,

Peter

Read More...

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

While waiting for my Raspberry Pi4, I followed the suggestion to capture the pix from my DSLR directly on the Raspberry Pi3. Wow, big speed improvement and I can quickly look at the captured image using VNC on my lap to connect to the Pi and display the Canon CR2 file.

Now I just need to figure out how to speed up using Ekos Align.

After polar aligning the mount, I go from the parked home position and slew to the first alignment star (typically Vega). It just seems to take a long time from capture picture to the solution. The longest time seems to be from capturing image to starting the solver. I have tried running both the remote solver (with astrometry on the Raspberry Pi) and the online solver. It takes 1:30m to capture and image receive. Solving iteration takes about 100 sec. So with about 8 iterations to get to a solution, it takes awhile for the first star alignment.

I have the Raspberry Pi connected directly to the EQ6-R mount and controlling it with EQMOD. I was going to try and use the hand controller to do the initial alignment, but I have problems if both the hand controller and Raspberry Pi are connected to the mount. There seems to be some sort of conflict.

I'm curious if any other EQ6-R users have suggestions on speeding up alignment.

Read More...