Hi!

Thanks for the suggestion - I'll check it out!

Cheers

Read More...

Hi!

I finally managed (fingers crossed) to get my gear up and running. What I did was:

1. Mount FW upgrade which made my mount behave as expected
2. After struggling extensively with the internal guider, I tried PHD2 which worked immediately so I decided to stick to it

Thanks for your replies and suggestions.

Cheers

Read More...

Hi Wolfgang!

I think I can see progress now! I re-installed the firmware from my Avalon Win dir and the mount behaves in a more "civilized" manner now :) From some "indoor dry runs" the mount seems to have a better understanding of where it is pointing. As soon as the weather permits I'll take it for a test run and let you know about my findings.

Regarding the hand controller I find your answer very encouraging as I, sometimes, find the use of the HC preferable in the field and not only rely on the tablet/pc for all movements. I got the impression from Avalon that there are some "safety precautions" built in in the FW which restricts the movement somehow in situations when the HC is not connected to the StarGo Unit, please see this link:

www.avalon-instruments.com/support-2/tro...op-before-the-target

Again, many thanks for your help!

Read More...

Hi Gilles!

Thanks for your reply! I've removed the "keypad" from the configuration and entered your guide setings in Ekos. I'll try when the weather improves. I still assume that the proper way of using the mount would be:

1. polar align using the Ekos alignment module
2. goto a bright star, say Vega/Deneb/Altair, and then sync the mount

That should be the only steps necessary if I'm correct or have I missed something?

Cheers

Read More...

Hi!

I successfully use the Ekos PA routine in order to get a good polar alignment but then things go, well, not according to plan. Some background information:

OTA: TS Optics CF-APO 90mm F6 with 0.8 reducer
DSLR: EOS 600D
Guider: QHY5LII-M-6027e
GPS: Hat GPS card
Mount: Avalon Zero Obs WiFi, FW 6.5.6
Control stack: Raspberry Pi 4B, 64GB ssd, Astroberry 2.0.3 and using the Avalon StarGo IndiLib Driver

The GPS receives lat/long/time every 10s and updates Kstars/Ekos accordingly.

Ok, so I managed to get a good polar alignment using the alignment module now it's time to slew to, say, Vega in order to sync the alignment. I click Vega in Kstars and selects Avalon StarGo -> GoTo resulting in the mount slewing but definitely not to Vega. In fact it is waaay off! I get the feeling that the mount stops too early. I have the control box connected and uses it in order to finalize the slew and then select Avalon StarGo -> Sync. Hmmm, "Ok - this is odd" I think. Well now I hope the mount "knows" where it is so I try Altair and slews to Altair... NOT! The mount is (of course) confused leaving me, well, a little disappointed to say the least.

One more thing. I've also tried to get the mount and guider to "talk" to each other although the alignment is way off. When trying to calibrate I get a message something like "Not able to ... ... after 21 iterations" after trying to sort out the RA backlash. It doesn't get to the DEC part. Do I need to tweak the control parameters somehow? I've set the Guiding rate to 0.3 which renders P: 222.22

Now, let me start by telling you I'm definitely not a Kstars/Ekos/IndiLib wizard by any means but I thought I had understood at least some of the core concepts well enough. And, also, I have a deep respect and admiration for the IndiLib driver developers who create these drivers for us. I just hope somebody out there can point me in the right direction and telling me what I'm doing wrong.

Many thanks in advance!
 

Read More...

I'm a noob when it comes to using the alignment module in Ekos so please bare with me :)

First my equipment:
Scope: TS-Optics CF-APO 90mm F/6 with 0.8x corrector
Mount: Avalon Zero Obs WiFi
DSLR: Canon EOS 600D (prime focus)
Guider: QHY 5L II
GPS(D): Up and running and reporting valid Lat/Long and Time
Software: Astroberry with KStars 3.5.4 build 2021-07-15 running on a Raspberry Pi 4B with 64Gb SSD card
Astrometry Files: *ALL* mandatory and recommended, see below
When I registered the configuration above I registered the OTA as having an F-ratio of 432mm (540 * 0.8 from the corrector mentioned above). After that I went into the alignment module and let the module decide which astrometry files were needed and downloaded *all* of the mandatory and recommended files. All of the files were marked as green, i.o.w., marked
as available! Last night I spent roughly four hours to get the polar alignment procedure to work without any luck. The solver *always* failed to solve the first image downloaded from the DSLR! After looking in the log-files I could see that the solver was unable to solve for the picture taken and then a FITS-filename. The FoV was calculated by the alignment module
based on my aperture/F-ratio so I didn't add that myself. I used various exposure times from 2s up to the maximum 60s to no avail. I feel that I have seriously misunderstood *everything* related to the alignment module so I'd very much appreciate to be enlightened by some of you professionals out there :) Apart from this issue everything seems to work "as advertised".

My speculations about the problem is the FoV but, as I said I'm a complete noob!

Many thanks in advance - I'm struggling here!!!

Clear skies!
Peter

​​​​​​​Downloaded files based on calculated FoV (177'6'' * 118'8'')
index-4213 index-4113
index-4212 index-4112
index-4211 index-4111
index-4210 index-4110
index-4209 index-4109
index-4208 index-4108
index-4207 index-4107
index-4206

Read More...