Replies: 2 comments 2 replies
-
Probably should start by looking at the allsky.log file... my system shows that my system starts to process the end of night data at about 05:00 in the morning. I'd start there... The other thing you could try if you're comfortable with running command line instructions is to manually generate the start trail jpg file manually... here is a link to the Allsky docs for the star trail info You may need to look at is the BRIGHTNESS_THRESHOLD setting in the config.sh file, But if it was working before, I would start with looking at allsky.log file for errors first... the path to the log file location is: |
Beta Was this translation helpful? Give feedback.
-
I concur with @peng155. Are you not getting anything, or you're getting a startrails but it doesn't have trails? |
Beta Was this translation helpful? Give feedback.
-
As in the subject... I found that the star trails which have been generated without fail suddenly stopped being generated on 4/30. There are files up on the images location of time lapses, and keograms, but the star trails function has apparently failed since that date. I see keograms for each date since then with perfectly clear starry skies all night long. In fact on nights when the observatory was open and streaming to the world.
Where can I look to find what has gone wrong? I did not change anything and now the star trails are no longer being made since 4/30...
Thanks,
Marc
STLS
Beta Was this translation helpful? Give feedback.
All reactions