Welcome, Guest
Username: Password: Remember me
14 Nov 2018
Glad to announce of release of INDI Library v1.7.5 on 2018-11-14. A few drivers were added in this release as we continue to improve & stabilize existing drivers.
Read More...
  • Page:
  • 1
  • 2

TOPIC: Requests/suggestions

Requests/suggestions 6 months 4 days ago #25942

  • pcxz
  • pcxz's Avatar Topic Author
  • Offline
  • Expert Boarder
  • Expert Boarder
  • Posts: 159
  • Thank you received: 10
Allow me to suggest some things that could, in my opinion, be useful.

1) Many times I do not remember to stop the tracking.
( would it be possible to auto stopping the tracking if move the telescope on another object? )

2) Would it be possible to add personal additions into the object database?
(so that it is possible to find them through the "search")

3) The scheduler has improved, but still receives the "invalid" error and stop all other ( when a modified session ends ) for example if added one in the repeats runs ... to repeat it scheduler.

In this case I came across this night.

However, I thank all the developers, for this wonderful software.
And excuse my poor english.

Please Log in or Create an account to join the conversation.

----
Celestron C8 Fastar XLT U.S.A. (Carbon tube), seeker 9x50 (used as a guide scope), Wedge, Meade DSI (used as a guide cam), Canon EOS 500D Full mod, Canon EOS 1000D, RaspBerryPI3 with remote management through EKOS.

Requests/suggestions 6 months 4 days ago #25944

I second that, 1) in particular.

Please Log in or Create an account to join the conversation.

Requests/suggestions 6 months 4 days ago #25945

  • xsnrg
  • xsnrg's Avatar
  • Offline
  • Gold Boarder
  • Gold Boarder
  • Posts: 237
  • Karma: 2
  • Thank you received: 50
If in 1) you mean guiding, not tracking, that would be nice, good suggestion. I believe it does stop tracking to slew already.
The following user(s) said Thank You: pcxz

Please Log in or Create an account to join the conversation.

12" pier with HDX110 using EQMod
ASI 1600 mono/color mains with ASI290MM in off-axis
ASI filter wheel
Moonlite focusers for the sharpening
AT115EDT and 8" Newt for the light
Fedora Linux, 100% INDI

Requests/suggestions 6 months 4 days ago #25946

  • pcxz
  • pcxz's Avatar Topic Author
  • Offline
  • Expert Boarder
  • Expert Boarder
  • Posts: 159
  • Thank you received: 10
Yes mean guiding. Thanks.

Please Log in or Create an account to join the conversation.

----
Celestron C8 Fastar XLT U.S.A. (Carbon tube), seeker 9x50 (used as a guide scope), Wedge, Meade DSI (used as a guide cam), Canon EOS 500D Full mod, Canon EOS 1000D, RaspBerryPI3 with remote management through EKOS.

Re:Requests/suggestions 6 months 4 days ago #25951

Could you elaborate on 3? I'd be interested in your version, .esl/.esq files and date/time to reproduce your problem. I believe the issue you refer to, that is, jobs being marked invalid when they pass their auto-scheduled startup time, should be fixed with the latest changes.

-Eric

Please Log in or Create an account to join the conversation.

HEQ5-Pro - Atik 314E - Orion ED80T - DMK21 on Orion 50mm
DIY 3D-printed Moonlite and FWheel RGB/LPR
KStars and indiserver on two Atom 1.6GHz 1GB RAM Linux, VPN remote access

Re:Requests/suggestions 6 months 3 days ago #25956

  • wvreeven
  • wvreeven's Avatar
  • Away
  • Platinum Boarder
  • Platinum Boarder
  • Posts: 425
  • Karma: 4
  • Thank you received: 98
Re 2) In KStars select Data -> Manually add new object
The following user(s) said Thank You: pcxz

Please Log in or Create an account to join the conversation.

Modded Canon EOS 700D with a WO ZS 71 ED on a SW HEQ5-Pro /
QHY9 CCD and filter wheel with an 8" RC on a SW EQ6-R

Re:Requests/suggestions 6 months 3 days ago #25964

  • pcxz
  • pcxz's Avatar Topic Author
  • Offline
  • Expert Boarder
  • Expert Boarder
  • Posts: 159
  • Thank you received: 10

TallFurryMan wrote: Could you elaborate on 3? I'd be interested in your version, .esl/.esq files and date/time to reproduce your problem. I believe the issue you refer to, that is, jobs being marked invalid when they pass their auto-scheduled startup time, should be fixed with the latest changes.

-Eric


Ok .I photograph three portions of the sky every night
the first evening works well, then I have to increase a "repeats runs" for start new session (otherwise the brand is completed and stops)
at this point, at end of first is marked as "invalid" and abort all.
Attachments:

Please Log in or Create an account to join the conversation.

----
Celestron C8 Fastar XLT U.S.A. (Carbon tube), seeker 9x50 (used as a guide scope), Wedge, Meade DSI (used as a guide cam), Canon EOS 500D Full mod, Canon EOS 1000D, RaspBerryPI3 with remote management through EKOS.

Re:Requests/suggestions 6 months 3 days ago #25968

Sorry I'll have to delay my analysis of your attached files, no bz2 tool on my phone (isn't that stupid for android!). From your description, I understand that:

1. Your jobs have fixed startup times "On YMD HMS" that include the date, and as such are considered "in the past" during the second night.

2. Your jobs are considered complete by the scheduler because the count of captures is achieved during the first run, and next jobs require additional repeats to continue processing.

For (1) the only workaround right now is to generate an .esl file with the right dates. You can generate a one-week long file, that should probably work (though I did not test over such a long interval). Perhaps there might be a way to tweak the culmination offset, but if you need specific time, that's a bit contrived. In any case that's not very practical unless planning is automated: that could be a feature to add next to the mosaic maker.

For (2) the behavior is the expected one. To work around the feature and achieve what you want, the most simple is to disable "Remember job progress" in the Ekos options. That will disregard capture storage and always run the sequence.

Tell me what you think.

-Eric
The following user(s) said Thank You: knro

Please Log in or Create an account to join the conversation.

HEQ5-Pro - Atik 314E - Orion ED80T - DMK21 on Orion 50mm
DIY 3D-printed Moonlite and FWheel RGB/LPR
KStars and indiserver on two Atom 1.6GHz 1GB RAM Linux, VPN remote access

Re:Requests/suggestions 6 months 1 day ago #25979

Regarding #1, the scheduler aborts guiding when it moves to the next target. If this doesn't happen now then a regression was introduced recently. Do you have logs to check?

Please Log in or Create an account to join the conversation.

Jasem Mutlaq
Support INDI & Ekos; Get StellarMate Astrophotography Gadget.
How to Submit Logs when you have problems?
Add your observatory info

Re:Requests/suggestions 6 months 1 day ago #25983

I think the scheduler will not abort guiding if the target is the same and guiding is ticked in the job pipeline. Probably not a regression?

Although I did not change that specific behavior, I did append two cases to that part of the code to fix issues arising in the job pipeline.

-Eric

Please Log in or Create an account to join the conversation.

HEQ5-Pro - Atik 314E - Orion ED80T - DMK21 on Orion 50mm
DIY 3D-printed Moonlite and FWheel RGB/LPR
KStars and indiserver on two Atom 1.6GHz 1GB RAM Linux, VPN remote access

Re:Requests/suggestions 6 months 1 day ago #25989

If you have a busy sequence queue and guiding is activated in the guide tab, then abort the sequence and slew to a new target the guider will remain active. Manually activated slewing, particularly after stopping the sequence queue, should stop guiding automatically IMO.

Downloading index files works for only half of the files listed. In my case the Tycho column works down to 4114. The files listed further down will provoke an error after download: "KAuth returned an error code: 8 Fehler im D-Bus-Hintergrundprogramm: Hilfsanwendung kann nicht kontaktiert werden. Verbindungsfehler: Not connected to D-Bus server."

Please Log in or Create an account to join the conversation.

Re:Requests/suggestions 6 months 1 day ago #25991

@pcxz I had a look at your .esl file. From what I see, you have three scheduler jobs each using their specific sequence file, and pointing to targets with different names. That means each scheduler job item will store its captures to different folders when it executes.

I assume this set of files is your starting point for an observation session, and that you update it prior to launching the scheduler.

If you don't want to bother with repeat counts, as I mentioned earlier, disable option "remember job progress".

Now about the invalid state, your three jobs are set to "asap", so there's no reason they should switch to "invalid", they should be rescheduled automatically. Unless you change them to start at a specific time before execution? I'll execute them with the simulator again when I can to check.

(maybe this should go to a specific topic)

-Eric

Please Log in or Create an account to join the conversation.

HEQ5-Pro - Atik 314E - Orion ED80T - DMK21 on Orion 50mm
DIY 3D-printed Moonlite and FWheel RGB/LPR
KStars and indiserver on two Atom 1.6GHz 1GB RAM Linux, VPN remote access
  • Page:
  • 1
  • 2
Time to create page: 0.168 seconds

Login

3rd Party

Choose from the numerous 3rd party INDI drivers to suit your needs!

Got Problem?

Check out the FAQ, the forum, and the bug tracking system to resolve any issues you might have!
You can also subscribe to INDI newsletter and development mailing lists to get the latest updates on INDI!


Gallery

Replica

Why INDI

Replica