Still there in 3.6.8. Moreover, scripts are not executed when sequence starts, even if related fields are filled-in by hand prior to start it.

Read More...

Yes: guiding speed is usually configurable in mount settings as a fraction of the tracking speed, defaulting to 0.5x. Assuming this default value, for example, guiding pulses towards east will slow down RA tracking to half speed, guiding pulses towards west will speed it up to 1.5 x tracking speed.

Read More...

Based on the screenshot, scope focal length is wrong: your input was 300, but the blind solver detected 2000!. So, what's the real focal length of your scope? One thing you must consider it that plate solve is normally "not blind", i.e. the solver is fed with approximate pointing data to speed-up the solve. Moreover, solving success it strongly related to the selection of correct index file, which, in turn, is related to FOV and so to sensor size and scope focal length. If this data is not correct, solver will fail.

Read More...

Backlash is not relevant for RA axis: during tracking and guiding, RA drive never reverses motion (it only slows down when correcting towards East), so any backlash, if present, can't produce any effect.

Read More...

Reading tooltip for "Save sequence HFR value to file", it says that if it's checked, HFR threshold value is constant (so it won't be updated, even if it's zero).

Actually in Astroberry repo I can see some arm64 packages. But if system is ready or not, I think only Radek can answer....

Read More...

Hi Willy,

SkySafari driver, AFAIK, is not meant to let an indi client interact with drivers, but to let SkySafari interact with drivers as it was an indi client itself. It's not clear how are you planning to use your mount: you want to drive an astrophotography session via Ekos? Or?

Read More...

Here too it is working. Seems to me that also "Auto update" can be left checked: if unit is "app", found that changing binning updates Low and High scales with the correct numbers.

Read More...

Hy, I'm very sorry I was working and haven't seen your msg until now. Reading on I discovered you found parameters to replicate it anyway Super!

Read More...

Not RaspberryPI-related only: here on a intel VM, 2GB ram configured, Ubuntu 20.04 and KStars 3.6.0 from ppa, same behaviour: all-simulators profile, three error assestment solves went perfect (4 sec exposure, less than 1 sec each), adjust plate solves (same refhresh 4 seconds, tried also with 6 seconds) all fail.