I think it is likely that it started the run by overwriting the same file and then after midnight the sequence started incrementing correctly.
Some additional clues that might help track this down.
I am unable to duplicate it with the simulators.
I have not seen it happen with darks or flats and they never start a sequence with 000 only 001.
I cannot be certain that it has anything to do with the 000 numbering, but it started at the same time, back early last year.
It happens with and without using the scheduler.
It seems to correct itself when midnight occurs.
If it is happening and you stop and start the capture sequence it seems to fix it for the current run.
Paul
Read More...
Jasem,
It appears randomly, however, it most often occurs when I have taken some images using the capture page and then remove an existing line or two and put some more lines in.
My original work around was to add a single capture and another line with the number I needed. It seems to reset the counter after doing this, although it would sometimes not work.
I have since added the time stamp, and last night it did the same thing again, where it started with a count of 010 and got stuck there until midnight local time when it started incrementing.
This started at the same time, just over a year ago, when the original count started at 000 instead of 001.
So, when I start a new capture run it begins at 000, but if it changes filters or starts a new capture run it always starts at 001, assuming there are not already images in the directory.
If I could reproduce this consistently, it would be easier.
Paul
Read More...
Peter,
I can guarantee it is happening with a version I built arounf 3 weeks ago, which is running 64 bit Buster.
I haven't yet got a fully working version on Bullseye, but believe I am close to succeeding.
Paul
Read More...
Yes, I do hope they resolve this soon, it has been over 12 months since I first reported it and it continues to be a major source of frustration.
indilib.org/forum/ekos/9913-image-counte...ages-to-be-lost.html
Paul
Read More...
Kurt,
It all depends on how you configure everything.
If you go to an object that is close to but East of the meridian the mount can determine whether to approach it from the East or West and therefore whether a flip is required.
You really need to understand how it all works together to understand how it will work.
Paul
Read More...
Unfortunately I spoke to soon, because under Bullseye I cannot get my QSI camera to operate, Kstars aborts as reported in the kstars bug reporting.
So, stuck using an older version for the moment.
Paul
Read More...
Jasem,
I was using Buster because previously INDI did not compile under Bullseye, but I can confirm that Bulleeye is now working so I will forget about Buster.
Bullseye seems to perform noticebly better that Buster so I am eager to move to it.
Paul
Read More...
Would anyone please assist with getting around this error, on Raspberry Pi OS 64bit Buster.
pi@HOM-DEV-BU64:~/Projects/build/kstars $ cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=RelWithDebInfo ~/Projects/kstars
CMake Error at CMakeLists.txt:70 (find_package):
Could not find a configuration file for package "ECM" that is compatible
with requested version "5.68.0".
The following configuration files were considered but not accepted:
/usr/share/ECM/cmake/ECMConfig.cmake, version: 5.54.0
-- Configuring incomplete, errors occurred!
See also "/home/pi/Projects/build/kstars/CMakeFiles/CMakeOutput.log".
See also "/home/pi/Projects/build/kstars/CMakeFiles/CMakeError.log".
Paul
Read More...
This not a new issue, it started just over twelve months ago and I have been using various workarounds since, but they often fail.
indilib.org/forum/ekos/9913-image-counte...ages-to-be-lost.html
Paul
Read More...
Tomm,
All the driver settings screens should have a save option under one of the tabs, have you used that?
Paul
Read More...
Jamie,
I am using the latest general release firmware for the Gemini 2 controller and if the error message is accurate then it seems to timeout when a non recognised command is received.
You may not be aware that they are currently testing a significant rewrite of the firmware that may have additional functionality.
I am wondering if there is a way to query the controller for a version so that you can implement functions based on the version.
Paul
Read More...
Jamie,
I am wondering if some of your changes have already made into the source and possibly changed the behaviour as per my recent post.
indilib.org/forum/mounts/11954-error-rea...timeout-error-4.html
If not, then I would say that it depends on how the Gemini controller behaves when confronted with commands it does not recognise.
Paul
Read More...