I experience similar irreproducible results. Sometimes it works flawlessly, sometimes it just doesn't get there. In most cases where it does not work, focusing on the wrong star is the problem. It selects a nebulous object, a double-star, or just a way too big star. So rescue method 1 for me is manual selection of a small star.
Subjectively I seem to have slightly better results with polynomial vs iterative method.
But I'm also recording my focuser position at various outdoor temperatures and find that the relationship is linear and very predictable. So for my setup, a drop in temperature of 1 degree celsius equals focuser in by approximately 80 steps. Important to keep circumstances similar (system must be in equilibrium with environment and dew heaters need to be in same position.
I do not let the focuser run unattended, and if I'm in a hurry, or experience issues, I just set the focuser where it theoretically should be with pretty good results.
Hmm, then I don’t know. Perhaps still something wrong with the scheduler. Keep in mind I only tested it with simulators.
Sent from my iPhone using Tapatalk
I have only tested with the simulators, but it slewed to the object and only then started to take pictures (I don’t use the guiding etc. options).
Did you see the scheduler pick up the coordinates of your target? I have found in the past that it is important to search for the target through the built in search function. Only then it adjust coordinates and speed to the object. Simply typing in the name of the target did not work for me.
Sent from my iPhone using Tapatalk
Just tried version 3.2.0 with the simulators, and it is working now!
Thank you so much Rob and Jasem, for resolving this so quickly!
After upgrading to version 3.1.1 for Mac (from 3.0), the scheduler does not seem to start. In the bottom right of the panel it says 'No jobs running' with the spinning sign behind it, suggesting that something is going on. However, no sequence is loaded in the capture module, no slewing to target happens, etc. Anyone any idea what I might be doing wrong here, or what could be going on? All jobs are scheduled to start ASAP, but even forcing it to start at a certain time did not work.
Attached a log-file that may be helpful. It reads somewhere 'Ekos communication status is 0, starting Ekos'. Could that point to the issue?
File Attachment:File Name: log_23-52-48.txt
File Size: 142 KB
You are absolutely right! There are indeed exactly 6 frames in the directory specified (three from the first sequence and three from the second sequence). This makes all sense now.
Glad nothing is wrong with the software, and just due to user error. I will uncheck the Remember Job Progress option going forward.
Thanks very much for your help solving this.
Thank you Wolfgang.
However, I never use the 'repeat for x runs', I always have 'Sequence Completion' selected.
Should I deselect 'Remember Job Progress' in the Preferences?
Thank you Wolfgang, for looking into this. I have attached the three capture sequence files I used (had to change extension to *.txt, or it would not upload). I'm afraid I did not save the scheduler job as a file (should probably start doing that...).
The three sequence files were executed in order, with selecting target M63, M44 and M63 respectively. In order to make sure they stay in order I typically assign a priority like 1, 10 and 15 or so to them.
Other settings of the scheduler were:
Tracking on, no focus, align or guide ticked. All Job constraint options unchecked. Selected shutdown procedures: warm CCD, Cap and Park Mount.
I just looked at the option 'remember job progress' and indeed that was selected. Can't remember I turned that on, so perhaps this was a default setting?
I've got logging on by default, but that only specifies some startup routines. Nothing in there about the actual imaging processes.
Once again, thank you very much already.
Best regards, Willem Jan.
Something strange happened last night when using the scheduler. I had three jobs on the list. First two went well. But from the third job, significantly less frames were taken than specified in the sequence-file. In the sequence file there was a series of 20/6/6/6/10 frames for various filters. However, the scheduler only took 10/3/3/3/10 frames. So most were halved, but not all. Looking at the time-stamps of the files, they were all taken in proper sequential order, no gaps, so I'm not missing files because they've been written wrongly. Seems like there is some logic/intelligence applied to the frame-reduction, but I can't see where or how and how to prevent this.
Usually when something goes wrong with the scheduler it's my own fault, having made a typo in the script or so, but I checked it hundred times, and the scripts all look fine. Any idea what could have gone wrong here and why th scheduler 'ate' some of my frames?
Using KStars 3.0.0 for Mac.
Thank you, Willem Jan.
If WiFi in the field is the bottleneck, perhaps this might help. I use an Amplifi router, creating it’s own network. It’s one of the few/only routers I know that is fed via usb-c. A simple Anker powerbank is enough to feed the router throughout the whole night. No ac power required. Dew/frost has so far not been a problem.
It gives very fast WiFi connections. 30Mb files from my asi1600 transfer in 3-4 seconds.
Sent from my iPhone using Tapatalk
Have you tried sync/offset to 0, with focuser all the way in? Remember, it’s an off-set, so I the focuser thinks it’s at 0 (set during calibration with the primalucelab software), and you set an offset in the INDI driver of 30,000, then entering an absolute position of 0 would make he focuser move outwards to 30,000. I had the same experience when my offset for whatever reason was always showing up as 76k..something, the maximum travel of my focuser. Synching it all to the 0-position has alsways worked reliably.
Looks like Jasem already has updated the driver, so that may be a much better solution.
Great that the Sesto Senso driver will be improved. In the meantime, NH, my workaround is as follows. I manually pull the focuser in all the way. Then I enter ‘0’ in Sync/offset and click ‘set’. This changes the absolute position of the focuser in Ekos to 0. Before you start your autofocusing routine, you then set the focuser to a value close to where you think you’ll be (in your case around 66000), and start the process. Works very well for me and gives me the reassurance that I have ‘calibrated’ my focuser each time.
Sent from my iPad using Tapatalk
You’re correct El Corazon, to point out the power usage. And this is where small telescope mounted PC’s can vary quite a bit. The Fitlet2 uses 7W (Linux, not sure about windows, might be more intensive) which is more than a RPi, which is probably closer to 2 or 3 W. But in the total scheme of things, 7W is very little. By comparison, putting the ASI1600 cooling on 75% takes 14W, or turn on one dew heater for a 130mm scope takes 10W, and the mount takes 13W. For my setup, I use about 40W, of which I could save 3 or 4 by going with a RPi. I am using a 400Wh battery, which lasts me 10h of observation time. Unfortunately there are few nights where I need the full battery.