search

Short-bus / pilomar

RaspberryPi based miniature observatory
https://shortbus.blog/
GNU General Public License v3.0
63 stars 14 forks source link

After a very long observation run the extending the trajectory got stuck with an out of date trajectory cache. #20

Closed Short-bus closed 11 months ago

Short-bus commented 11 months ago

Observation had been running 12+ hours, at a point where the telescope had to move very rapidly, the trajectory segments get very short. Eventually they became shorter than the time it takes to update on the microcontroller. At this point the software got stuck in a loop where it continually passed the last calculated trajectory segment from the cache. As a secondary issue, the ReadyToObserve flag did not get reset, so the camerahandler continued taking images even though the telescope was nolonger on target.

Short-bus commented 11 months ago

Modified pilomar.py to check for an out of date cache value. It will recalculate a fresh trajectory segment if this happens. Still need to check why the ReadyToObserve flag did not get reset to pause the camerahandler.

Short-bus commented 11 months ago

ReadyToObserve issue can be related to issue 19 [https://github.com/Short-bus/pilomar/issues/19] The motorcontroller code should report 'off target' if the trajectory is out of date. I think currently it just continues in a straight line until it receives a new trajectory. So Fixing the out of date cache error will probably prevent this problem arising anyway.

Short-bus commented 11 months ago

Next version released has the cache fix in place. The 'off target' issue will be fixed separately when issue 19 is addressed.