I just took a look. It seems that there is some confusion in the code between the dawn offset you are setting, and another (old) parameter called "Pre-dawn" which is in the same options menu several rows above "dawn offset".

I'm not sure whether Pre-dawn is something that should be removed from the code or not, it predates me, but I'll think about it. In the mean time, I believe that if you set Pre-dawn to 0, you will get the performance you desire.

Hy

Read More...

For at least my focuser, and likely many others, the "position" that's tracked really means the position of the stepper motor that turns the mechanical focuser. It does not mean the position of the mechanical focuser. (I suppose it's possible to keep track of that with optical sensors etc, but that's likely not being done.) So, if you detach the clutch and manually turn the mechanical focuser, I believe you are right that INDI/Ekos and the focuser controller itself lose track of the mechanical focuser position. However, if you use a focuser controller's user interface to step the focuser, then I would hope that the focuser controller (and INDI/Ekos) could keep track.

Read More...

Interesting project. I have not attempted to use the scheduler for satellites, however I can say that the start and end times should correspond to the constraints set up for imaging. It likely is using a fixed RA/DEC coordinate, and tracking that across the sky. It is looking at other constraints you may have configured such as altitude and twilight. It is considering the imaging sequence you have chosen, eg how many exposures you requested and at what duration. The start time is sampled every minute or two and the end time is an estimate of how long the imaging might take, including focus times, download times, etc.

Read More...

> I assume this happens when INDI starts and connects to the focuser. Is there any logging of what it reports?

I assume most drivers will query the focus position regularly, e.g. every second. Mine does.

If you enable driver logging for your focuser, you'll probably see these values, though I suppose that depends on the driver.

Hy

Read More...

Many (perhaps most?) focusers report their position to the INDI driver, which in turn sends it to Ekos.
So, Ekos gets told the focuser position.

Internally, the focuser firmware will very likely do as you said: "record where it last was and imagine that it's still there".
Hy

Read More...

Hy Murveit replied to the topic 'Defining a schedule' in the forum. 1 month ago

Please send the log with verbose logging and all modules checked (and why not, also the .esl and .esq files).

There is decent documentation in the kstars handbook on using the scheduler, if you haven't checked it out--see
docs.kde.org/trunk5/en/kstars/kstars/kstars.pdf#scheduler

It's hard to tell what's wrong, but the "empty plan" is likely that your job was aborted for some reason (can't tell exactly why without log), and you have "aborted job management" set to "None" instead of having it retry right away or retry after some fixed time.

FWIW, I run the scheduler with the simulator all the time when writing/debugging software, so you might want to try and practice setting something up that way. (To take pictures with the simulator, you need gsc installed, and I don't know if that happens by default, but you can try and see if it works.)

Perhaps the issue is related to the fact that you're imaging near Polaris (e.g. I'm sure the guider would have issues there, are you using the guider?). Try some easier target further from the pole and see if you can get that going...

Anyway, we should be able to get this going, keep posting your progress.

Hy

Read More...

Hy Murveit replied to the topic 'Install "Obsolete" Driver' in the forum. 1 month ago

Steve,

Not sure about the old driver, you can likely compile and install it yourself, but let's see if we can get the V2 driver working for you ... I use it all the time (with my CP3, but I'm sure it was verified to be working with CP4 and CP5).

Can you connect to it with KStars/Ekos? If that shows an issue, can you send a full kstars log of your failed connections (make sure you have verbose logging on and logging for the mount driver checked). The usual issue for things like that it is trying to connect to the wrong port. E.g. if you are using a FTDI cable, you need to make sure you have the right /dev/ttyUSB0 or /dev/ttyUSB1 etc. If you are using ethernet with your CP4, I think there was some network protocol choice. If you don't get it working from that, can you also send screenshots of your INDI mount control tabs (e.g. Main Control and Connection)?

Mike Hanson at Astro-Physics has also verified all this works and can be a resource to help you.

Hy

Read More...

Hy Murveit replied to the topic 'Plate Solving Woes' in the forum. 1 month ago

Also, Jean-Luc, can you please point me to the part of the handbook that was misleading?
Here's one section (in English) I found (and there are a few others too), please let me know if you have suggested changes.
Hy



Read More...

Hy Murveit replied to the topic 'Plate Solving Woes' in the forum. 1 month ago

Jean Luc,

It is worth seeing if that now that you have the right scale, re-checking 'use scale' works. I assume it will work, and that it will significantly speed up your plate solves. Again, you should be able to do this debugging with the FITS Viewer's solver tool during the daytime, if you don't want to do it at night with the Align tab.

I'm not sure how scale originally gets screwed up though.
Hy

Read More...

I can't answer for PHD2, but for the Ekos internal guider, the stages are (1) increment RA, (2) decrement RA, (3) increment DEC, (4) decrement DEC.
It's probably similar for PHD2, however to be sure you can find out by just letting it calibrate and watching the mount's reported RA and DEC angles (e.g. in the Ekos mount tab).
That is, in the RA stages you should see the DEC stay the same and the RA change consistently in one direction when going out and the other when coming back in.

Read More...

Juergen,

What I do for that situation is set Capture's guide limit start setting.
This way, capture doesn't start until the guider corrects the drift. In fact your example is the reason that that parameter was implemented.

Note that I believe this parameter is a property of the capture sequence file (as opposed to a global parameter) so I believe that you'd need to load a sequence file, set the parameter, and then save your sequence file, so that the next time you loaded that sequence file the parameter would still be checked.

Hy



Read More...

Also, I imagine you should be looking on the machine that runs indiserver--that is, the machine that is physically connected to your cameras.
Hy

Read More...

  • Basic Information

  • Gender
    Male