| Summary: | kstars [ERROR] Object below elevation limit | ||
|---|---|---|---|
| Product: | [Applications] kstars | Reporter: | Mirco Massone <ghigomatto> |
| Component: | general | Assignee: | Jasem Mutlaq <mutlaqja> |
| Status: | RESOLVED FIXED | ||
| Severity: | grave | CC: | ghigomatto |
| Priority: | NOR | ||
| Version First Reported In: | 3.0.0 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: |
error image print screen
TIME_dATA_AFTER_CONNECT_SCOPE LOG_CONNECTING_SCOPE ATTEMPT_GUIDE_FROM_CAPELLA_TO_MIRFAK_LOG_CONSOLLE ATTEMPT_GUIDE_FROM_CAPELLA_TO_MIRFAK_SCREEN error log from ekos interface |
||
Did you perform 2 or 3 star alignment on your mount before connecting to KStars? (In reply to Jasem Mutlaq from comment #1) > Did you perform 2 or 3 star alignment on your mount before connecting to > KStars? First of all thank you for your kind reply. I had already aligned the telescope from home, as on this occasion. The initial setup was done with alignment using the north and the terrestrial horizon. The so-called simple training is manual. It's what I've been using since I've got the telescope, and it always seems to work very well. The only aspect on which I have some doubt is the fact that at the beginning of this procedure the GPS takes a while to detect its position. In fact, this setup I do from inside the house, right next to a very large window. In the past, in doing so, it has always worked well. I put in the past a video on youtube, a little tutorial on how to use kstars to chase the celestial objects. The tutorial is at this link: https://www.youtube.com/watch?v=zS1QB0Ekok0&t=114s And my desire was to do the same things again without meeting the frustrating problem of not being able to drive the telescope. My next step will be to redo this attempt outdoors. But I fear there is the same problem. I ask this question: is it possible that the audiostar console has the buffer battery discharged? Can it be a valid hypothesis? I say this because it happened to me for some time to find the telescope, once lit, always with a wrong initial setup. (Eg "cord wrap function" enabled previously I find it disabled when the telescope is switched on). Please, help me !!! I'm not sure, but GPS is not required, so you can skip this on the hand-controller. Just perform a 2 or 3 star alignment, then you're good to go. The message you received is when the telescope is not aligned OR when the location/time information is not correct. Go to INDI Control Panel, and check "Site Settings". Send screenshot of the date/time/location there. Everything appears to be correct? The process of two-star alignment is the standard for this telescope, and, net of initial corrections due, to put the celestial object in the center of the field of view, alignment activity always ends successfully. I noticed that the error appears as soon as I try to point an object, and accidentally, the error reports, a little earlier, the Universal date, exactly one hour behind my time zone. Unfortunately, however, I verify that kstars regularly records my local date and time. But then it would seem to always refer to UT, universal time of Greenwich. I'm now mounting the telescope again, to re-check when you've suggested. So I can send some photos of what happens to me, and also the log, which I have made verbose and regularly recorded on file. As soon as I have all the material I send it to you here. This is the log recorded when the error came out yesterday: 2018-12-30T18: 20: 35: [WARNING] Could not process mount date and time:: GCT00: 00: 00 2018-12-30T18: 20: 35: [WARNING] Failed to get site latitude from device. 2018-12-30T18: 20: 35: [ERROR] Failed to get tracking frequency from device. 2018-12-30T18: 20: 35: [ERROR] Failed to retrieve time format from device. In the error message, however, the date was correct, but the time was exactly one hour behind. I wait impatiently, for now thank you. Created attachment 117209 [details]
TIME_dATA_AFTER_CONNECT_SCOPE
Created attachment 117210 [details]
LOG_CONNECTING_SCOPE
Created attachment 117211 [details]
ATTEMPT_GUIDE_FROM_CAPELLA_TO_MIRFAK_LOG_CONSOLLE
Created attachment 117212 [details]
ATTEMPT_GUIDE_FROM_CAPELLA_TO_MIRFAK_SCREEN
There is definitely problem with communicating with the mount. Please follow the guide here to submit the Mount logs: https://www.indilib.org/support/logs-submission.html Created attachment 117287 [details]
error log from ekos interface
Please, can you help me?
Finally I came to the head of the problem. I had to re-buy a crimping tool to redo the AUDIOSTAR plug. Once the cable (connection) was restored, the telescope worked on the first one. The fact is that I did not realize that the clamp I had was not suitable for the purpose, and did not accurately fix the plug rj11. Resolved, remaking the cable, but with the right clamp. Thank you for the patience you have shown me. |
Created attachment 117077 [details] error image print screen I'm Ubuntu xfce 18.04 LTS user. I'm using this kernel: Linux ghost 4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux I'm using kstars application for pilot my LX90 ACF 10" SCOPE (with GPS INTEGRATED) I connect my scope after regular setup, and regular alignement. I start kstars app after the scope is successfully aligned. I apply chmod 777 /dev/ttyUSB0 to scope linux device. I activate indi panel for pilot my scope and activate tracking into application via cable. As soon as I try to point an object, even if I circumpulate, the application replies that it is too low. The error appears next to the universal date, not the local one! I verified that the Audiostar controller was regularly set as the date and time, and it is. The error is extremely frustrating, and there is no way to avoid it. Communication between telescope and PC is safe and verified. At the moment it is impossible for me to point an object with kstars and verify that the telescope actually follows it. At the moment the telescope remains where it was after the initial setup. Please solve this dramatic bug! Thank you.