FORUM DU LOGICIEL PRISM

I agree, and thank you for letting into the issue. This occurred on version 11.4.28.40 and also on the latest version that was released. I think I can explain why its happening, after version 11.2.3.21 a feature was introduced that would adjust the focus range as the session went on. For example, if...

The range for the focuser was: 13300 to 13450 On the prism version 11.4.28.40 during a focus run if Prism calcauted the focus to be outside the range I provided it will throw an error and stop the auto observation sequence. Imaging would contiune, but no guiding and unable to stop the sequence. When...

Good Evening Prism,
I see a recent version of PRISM was released on Feb 2, does that release resolve the focus error that stops automated observations.

Marcel

Good Morning PRISM, Our team recently installed the latest update on PRISM: 11.4.28.40 During a run the team received the following error message when auto observations were running the auto focus routine "Focuser movement out of range movement impossible". Our initial focus range is: 1330...

Log file is contained in the google drive link, and I have made it accessible

https://drive.google.com/drive/u/2/fold ... -bi-MIhuen

Good Evening, Tonight 11/12/24 our team noticed that during an automated observation of an exoplanet, the PRISM automated observation froze. The problem is similar to an issue we reported during flats processing when automated observations would just hang and not perform any additional functions. In...

Also, we have been running the updated config since Friday Oct 18 and we reviewed the auto_logs since and have detected no barycenter failures or out of focus stars.

Update: Barycenter Failure: I think we have managed to resolve this issue, we adjusted the end-stop of the focus range to be: 13510 vs 13583 when looking more closely at the V-curve we were more on the right side than was optimum. The next adjustment was to select: "Center Focus Auto" on t...

Good Morning PRISM, This is Prof. Mabson from Capitol Technology University, we recently added AAG Cloudwatcher into PRISM and noticed some interesting responses when in automated observations operations. Current Observatory Setup: Dome: NextDome, with Beaver controller Mount: Celestron CGX Scope: C...

I noticed an interesting error when using the auto observation feature on Prism V11. 4.17.36, that the focus range defined in the automated observation is not what gets used during a run. We have noticed on 4 runs that during the start of the run PRISM will use the correct focus range (14420 to 1471...