Open Lagroxane opened 5 years ago
Sorry, I should have also added that this behaviour is in the beta and in 0.19.2 stable
I see in the log follow lines:
Exoplanets] Already updating... will not start again current update is complete. [Novae] already updating... will not start again current update is complete. [Exoplanets] Download error: While trying to access "https://freegeoip.stellarium.org/json/" the following error occured: "Connection timed out" [Novae] Download error: While trying to access "https://freegeoip.stellarium.org/json/" the following error occured: "Connection timed out" Failure getting IP-based location: "Connection timed out" [Exoplanets] Already updating... will not start again current update is complete. [Novae] already updating... will not start again current update is complete. Satellite has invalid orbit: "OSIRIS-3U" "43027" [Exoplanets] Already updating... will not start again current update is complete. [Novae] already updating... will not start again current update is complete. [Exoplanets] Already updating... will not start again current update is complete. [Novae] already updating... will not start again current update is complete. Error: unable to find Telescopeor EQUATORIAL_EOD_COORD property... Error: unable to find Telescopeor EQUATORIAL_EOD_COORD property... [Exoplanets] Already updating... will not start again current update is complete. [Novae] already updating... will not start again current update is complete. [Exoplanets] Already updating... will not start again current update is complete. [Novae] already updating... will not start again current update is complete. Error: unable to find Telescopeor EQUATORIAL_EOD_COORD property... [Exoplanets] Already updating... will not start again current update is complete. [Novae] already updating... will not start again current update is complete. [Exoplanets] Already updating... will not start again current update is complete.
This is very bad and seems like Stellarium cannot connect to network. Could you check network access operating from Stellarium (e.g. download star catalog) and Gatekeeper settings for Stellarium.
Hi Jasem,
it’s not blocked by the firewall and I’ve forgotten how to check the gatekeeper
c
On 31 Oct 2019, at 17:22, Alexander Wolf notifications@github.com wrote:
I see in the log follow lines:
Exoplanets] Already updating... will not start again current update is complete. [Novae] already updating... will not start again current update is complete. [Exoplanets] Download error: While trying to access "https://freegeoip.stellarium.org/json/ https://freegeoip.stellarium.org/json/" the following error occured: "Connection timed out" [Novae] Download error: While trying to access "https://freegeoip.stellarium.org/json/ https://freegeoip.stellarium.org/json/" the following error occured: "Connection timed out" Failure getting IP-based location: "Connection timed out" [Exoplanets] Already updating... will not start again current update is complete. [Novae] already updating... will not start again current update is complete. Satellite has invalid orbit: "OSIRIS-3U" "43027" [Exoplanets] Already updating... will not start again current update is complete. [Novae] already updating... will not start again current update is complete. [Exoplanets] Already updating... will not start again current update is complete. [Novae] already updating... will not start again current update is complete. Error: unable to find Telescopeor EQUATORIAL_EOD_COORD property... Error: unable to find Telescopeor EQUATORIAL_EOD_COORD property... [Exoplanets] Already updating... will not start again current update is complete. [Novae] already updating... will not start again current update is complete. [Exoplanets] Already updating... will not start again current update is complete. [Novae] already updating... will not start again current update is complete. Error: unable to find Telescopeor EQUATORIAL_EOD_COORD property... [Exoplanets] Already updating... will not start again current update is complete. [Novae] already updating... will not start again current update is complete. [Exoplanets] Already updating... will not start again current update is complete.
This is very bad and seems like Stellarium cannot connect to network. Could you check network access operating from Stellarium (e.g. download star catalog) and Gatekeeper settings for Stellarium.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Stellarium/stellarium/issues/825?email_source=notifications&email_token=AJGNUOICPICFW4PWNI36YL3QRMH4JA5CNFSM4JHNT4G2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECYSWDI#issuecomment-548481805, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJGNUONXWPYCUWI6LHACRBLQRMH4JANCNFSM4JHNT4GQ.
Hi Jasem,
I followed the instructions here
https://www.imore.com/how-open-apps-anywhere-macos-catalina-and-mojave https://www.imore.com/how-open-apps-anywhere-macos-catalina-and-mojave
I’ll send you the log in a moment
c
On 31 Oct 2019, at 17:22, Alexander Wolf notifications@github.com wrote:
I see in the log follow lines:
Exoplanets] Already updating... will not start again current update is complete. [Novae] already updating... will not start again current update is complete. [Exoplanets] Download error: While trying to access "https://freegeoip.stellarium.org/json/ https://freegeoip.stellarium.org/json/" the following error occured: "Connection timed out" [Novae] Download error: While trying to access "https://freegeoip.stellarium.org/json/ https://freegeoip.stellarium.org/json/" the following error occured: "Connection timed out" Failure getting IP-based location: "Connection timed out" [Exoplanets] Already updating... will not start again current update is complete. [Novae] already updating... will not start again current update is complete. Satellite has invalid orbit: "OSIRIS-3U" "43027" [Exoplanets] Already updating... will not start again current update is complete. [Novae] already updating... will not start again current update is complete. [Exoplanets] Already updating... will not start again current update is complete. [Novae] already updating... will not start again current update is complete. Error: unable to find Telescopeor EQUATORIAL_EOD_COORD property... Error: unable to find Telescopeor EQUATORIAL_EOD_COORD property... [Exoplanets] Already updating... will not start again current update is complete. [Novae] already updating... will not start again current update is complete. [Exoplanets] Already updating... will not start again current update is complete. [Novae] already updating... will not start again current update is complete. Error: unable to find Telescopeor EQUATORIAL_EOD_COORD property... [Exoplanets] Already updating... will not start again current update is complete. [Novae] already updating... will not start again current update is complete. [Exoplanets] Already updating... will not start again current update is complete.
This is very bad and seems like Stellarium cannot connect to network. Could you check network access operating from Stellarium (e.g. download star catalog) and Gatekeeper settings for Stellarium.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Stellarium/stellarium/issues/825?email_source=notifications&email_token=AJGNUOICPICFW4PWNI36YL3QRMH4JA5CNFSM4JHNT4G2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECYSWDI#issuecomment-548481805, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJGNUONXWPYCUWI6LHACRBLQRMH4JANCNFSM4JHNT4GQ.
After following the instructions at the link I sent you, this is the log
On 31 Oct 2019, at 17:22, Alexander Wolf notifications@github.com wrote:
I see in the log follow lines:
Exoplanets] Already updating... will not start again current update is complete. [Novae] already updating... will not start again current update is complete. [Exoplanets] Download error: While trying to access "https://freegeoip.stellarium.org/json/ https://freegeoip.stellarium.org/json/" the following error occured: "Connection timed out" [Novae] Download error: While trying to access "https://freegeoip.stellarium.org/json/ https://freegeoip.stellarium.org/json/" the following error occured: "Connection timed out" Failure getting IP-based location: "Connection timed out" [Exoplanets] Already updating... will not start again current update is complete. [Novae] already updating... will not start again current update is complete. Satellite has invalid orbit: "OSIRIS-3U" "43027" [Exoplanets] Already updating... will not start again current update is complete. [Novae] already updating... will not start again current update is complete. [Exoplanets] Already updating... will not start again current update is complete. [Novae] already updating... will not start again current update is complete. Error: unable to find Telescopeor EQUATORIAL_EOD_COORD property... Error: unable to find Telescopeor EQUATORIAL_EOD_COORD property... [Exoplanets] Already updating... will not start again current update is complete. [Novae] already updating... will not start again current update is complete. [Exoplanets] Already updating... will not start again current update is complete. [Novae] already updating... will not start again current update is complete. Error: unable to find Telescopeor EQUATORIAL_EOD_COORD property... [Exoplanets] Already updating... will not start again current update is complete. [Novae] already updating... will not start again current update is complete. [Exoplanets] Already updating... will not start again current update is complete.
This is very bad and seems like Stellarium cannot connect to network. Could you check network access operating from Stellarium (e.g. download star catalog) and Gatekeeper settings for Stellarium.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Stellarium/stellarium/issues/825?email_source=notifications&email_token=AJGNUOICPICFW4PWNI36YL3QRMH4JA5CNFSM4JHNT4G2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECYSWDI#issuecomment-548481805, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJGNUONXWPYCUWI6LHACRBLQRMH4JANCNFSM4JHNT4GQ.
Writing log file to: "/Users/collin/Library/Application Support/Stellarium/log.txt"
File search paths:
0 . "/Users/collin/Library/Application Support/Stellarium"
1 . "/Applications/Stellarium.app/Contents/Resources"
Config file is: "/Users/collin/Library/Application Support/Stellarium/config.ini"
Default surface format: QSurfaceFormat(version 2.0, options QFlags
No serious problems in log - please try connect to INDIGO server.
Hi,
After making the change to the gatekeeper - that was the first thing I did. 😀
It was no different I’m afraid
c
On 31 Oct 2019, at 20:40, Alexander Wolf notifications@github.com wrote:
No serious problems in log - please try connect to INDIGO server.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Stellarium/stellarium/issues/825?email_source=notifications&email_token=AJGNUOPKCTF4RV4WFM5IVEDQRM7FNA5CNFSM4JHNT4G2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECZFWFI#issuecomment-548559637, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJGNUOMXLX45HOD7ASCDDKTQRM7FNANCNFSM4JHNT4GQ.
I've install INDIGO Server and Control Panel on my linux and tried connect to Mount Simulator through Telescope Control Plugin - it works as expected and without problem. Possible problem is one: please unpark mount in Control Panel.
Hi,
I accept that. BUT
I was using a Mac ond not a simulated mount.
c
On 1 Nov 2019, at 16:27, Alexander Wolf notifications@github.com wrote:
I've install INDIGO Server and Control Panel on my linux and tried connect to Mount Simulator through Telescope Control Plugin - it works as expected and without problem. Possible problem is one: please unpark mount in Control Panel.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Stellarium/stellarium/issues/825?email_source=notifications&email_token=AJGNUOMH4X4ZUULCNF7RJLDQRRKGBA5CNFSM4JHNT4G2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEC3NKMY#issuecomment-548853043, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJGNUOMRFCR24OCZKTUW3B3QRRKGBANCNFSM4JHNT4GQ.
Probably you get more diagnostics by activating the "Log telescope driver..." in the TelescopeControl/Options plugin config dialog.
In any case please try switch MOUNT_PARK property to UNPARKED state for your real mount through INDIGO Control Panel. Is it a source of problem or not?
Hi,
I’ll give it a try.
Which file is the data logged to please ?
c
On 1 Nov 2019, at 16:39, Georg Zotti notifications@github.com wrote:
Probably you get more diagnostics by activating the "Log telescope driver..." in the TelescopeControl/Options plugin config dialog.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Stellarium/stellarium/issues/825?email_source=notifications&email_token=AJGNUOPEQQ3OAWKPXRM42EDQRRLUTA5CNFSM4JHNT4G2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEC3OPFI#issuecomment-548857749, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJGNUOMCJ52GNFCGG4ADRDTQRRLUTANCNFSM4JHNT4GQ.
Hi what I don’t understand is this. I had slewed the scope from astrotelesope. So by definition, wasn’t the mount unmarked ?
I could not then slew the mount from Stellarium.
c
On 1 Nov 2019, at 16:39, Georg Zotti notifications@github.com wrote:
Probably you get more diagnostics by activating the "Log telescope driver..." in the TelescopeControl/Options plugin config dialog.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Stellarium/stellarium/issues/825?email_source=notifications&email_token=AJGNUOPEQQ3OAWKPXRM42EDQRRLUTA5CNFSM4JHNT4G2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEC3OPFI#issuecomment-548857749, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJGNUOMCJ52GNFCGG4ADRDTQRRLUTANCNFSM4JHNT4GQ.
OK, step-by-step: 1) Run INDIGO Server 2) Run INDIGO Control Panel 3) Run Stellarium 4) Open the Control Panel of Telescope Control Plugin 5) Choose INDI driver 6) Get list of mounts and select your mount (Mount Simulator in my case) 7) Save settings and connect to new telescope 8) In INDIGO Control Panel switch Mount/Park property to Mount unparked state (see picture) 9) Use Slew Telescope To dialog in Stellarium as you want
Hi,
Thanks. I’ll try this now. Where are the driver messages logged please ?
c
On 1 Nov 2019, at 16:56, Alexander Wolf notifications@github.com wrote:
OK, step-by-step:
Run INDIGO Server Run INDIGO Control Panel Run Stellarium Open the Control Panel of Telescope Control Plugin Choose INDI driver Get list of mounts and select your mount (Mount Simulator in my case) Save settings and connect to new telescope In INDIGO Control Panel switch Mount/Park property to Mount unparked state (see picture) Use Slew Telescope To dialog in Stellarium as you want https://user-images.githubusercontent.com/88731/68041472-3b1d0e80-fd03-11e9-8e5e-dcaa0a7af3e3.png — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Stellarium/stellarium/issues/825?email_source=notifications&email_token=AJGNUOMGAXHWQBV5NGPVRJLQRRNVBA5CNFSM4JHNT4G2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEC3QTLA#issuecomment-548866476, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJGNUONWLAZJWLTTIOTESFLQRRNVBANCNFSM4JHNT4GQ.
Thanks. I’ll try this now. Where are the driver messages logged please ?
See Telescopes/Options tab on screenshot and User Data Directory to reading log from telescope
Hi,
Steps:
On 1 Nov 2019, at 16:56, Alexander Wolf notifications@github.com wrote:
OK, step-by-step:
Run INDIGO Server Run INDIGO Control Panel Run Stellarium Open the Control Panel of Telescope Control Plugin Choose INDI driver Get list of mounts and select your mount (Mount Simulator in my case) Save settings and connect to new telescope In INDIGO Control Panel switch Mount/Park property to Mount unparked state (see picture) Use Slew Telescope To dialog in Stellarium as you want https://user-images.githubusercontent.com/88731/68041472-3b1d0e80-fd03-11e9-8e5e-dcaa0a7af3e3.png — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Stellarium/stellarium/issues/825?email_source=notifications&email_token=AJGNUOMGAXHWQBV5NGPVRJLQRRNVBA5CNFSM4JHNT4G2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEC3QTLA#issuecomment-548866476, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJGNUONWLAZJWLTTIOTESFLQRRNVBANCNFSM4JHNT4GQ.
Writing log file to: "/Users/collin/Library/Application Support/Stellarium/log.txt"
File search paths:
0 . "/Users/collin/Library/Application Support/Stellarium"
1 . "/Applications/Stellarium.app/Contents/Resources"
Config file is: "/Users/collin/Library/Application Support/Stellarium/config.ini"
Default surface format: QSurfaceFormat(version 2.0, options QFlags
- OK
- There is no save option here. “Connect” button pressed. Status = “Connecting” 8.The mount is unmarked.
- No movement
From the log I see that point 6 is not complete. Please do follow steps: a) In Telescopes dialog select line with your mount and press button "Configure" b) In opened dialog press button "Refresh devices" and select your mount (Not Server!) c) Press button "OK"
For obvious technical reasons the steps a)-c) should be doing for every observing session.
Press button "Connect" (Step 7).
Yes Jasem - I did that
c
On 1 Nov 2019, at 17:01, Alexander Wolf notifications@github.com wrote:
Thanks. I’ll try this now. Where are the driver messages logged please ?
See Telescopes/Options tab on screenshot and User Data Directory to reading log from telescope
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Stellarium/stellarium/issues/825?email_source=notifications&email_token=AJGNUOKNCIWZG2S2TK4NHXLQRROH7A5CNFSM4JHNT4G2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEC3RCAQ#issuecomment-548868354, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJGNUOJD5L5Z2MP5KID7EQ3QRROH7ANCNFSM4JHNT4GQ.
Hi,
can I ask whom I am exchanging mails with ? Mails come to ma apparently from Jasem Mutlaq but the responses on Git appesr to come from Alex.
Who am I talking to ?
c
On 1 Nov 2019, at 17:47, Alexander Wolf notifications@github.com wrote:
OK There is no save option here. “Connect” button pressed. Status = “Connecting” 8.The mount is unmarked. No movement From the log I see that point 6 is not complete. Please do follow steps: a) In Telescopes dialog select line with your mount and press button "Configure" b) In opened dialog press button "Refresh devices" and select your mount (Not Server!) c) Press button "OK"
For obvious technical reasons the steps a)-c) should be doing for every observing session.
Press button "Connect" (Step 7).
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Stellarium/stellarium/issues/825?email_source=notifications&email_token=AJGNUOKPZNTNPEIL3VYTC4DQRRTUPA5CNFSM4JHNT4G2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEC3VFSA#issuecomment-548885192, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJGNUOOZ5CL64YQRCSWAUCDQRRTUPANCNFSM4JHNT4GQ.
Whoever is answering. I see you are addressing some Jasem, who is no member of Stellarium and who has not posted here on Stellarium. There is somebody of this name at KStars. Alex is answering most issues of Stellarium.
Hmm, interesting.
Maybe my mail db is corrupt :)
On 2 Nov 2019, at 20:42, Georg Zotti notifications@github.com wrote:
Whoever is answering. I see you are addressing some Jasem, who is no member of Stellarium and who has not posted here on Stellarium. There is somebody of this name at KStars. Alex is answering most issues of Stellarium.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Stellarium/stellarium/issues/825?email_source=notifications&email_token=AJGNUOO6ZJUKQ6MDN7T42Z3QRXQ33A5CNFSM4JHNT4G2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEC5EUAY#issuecomment-549079555, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJGNUONWSLMUKXEXUUDBPWLQRXQ33ANCNFSM4JHNT4GQ.
Any news?
Hi Alex,
Has the version changed ? I have 0.19.2.17327
c
On 10 Nov 2019, at 17:29, Alexander Wolf notifications@github.com wrote:
Any news?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Stellarium/stellarium/issues/825?email_source=notifications&email_token=AJGNUOPHAXATQELVZ2RZKTLQTBAGBA5CNFSM4JHNT4G2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDVCGPY#issuecomment-552215359, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJGNUOLQWRATLI7KLTH2YY3QTBAGBANCNFSM4JHNT4GQ.
Hi Alex, are you waitig for something from me ?
Regards,
c
Please check latest beta.
@Lagroxane any news?
I seem to be experiencing this issue too. Sometimes I can get my actual Nexstar Mount to connect if I add a Mount Simulator and connect to it shortly after starting the connection for Nexstar Mount. I feel like the information handshake from Indigo is dying halfway through, and starting the Mount Simulator retrieves the missing information.
Running 0.20.0 on Arch.
Also tested on 0.20.1, I've noticed the cheat I mentioned sometimes flips the connections (even though I used the Simulator to jumpstart my Nexstar, the connection labeled for Nexstar controls the Simulator, or vice versa).
Please check the fresh version (development snapshot) of Stellarium: https://github.com/Stellarium/stellarium-data/releases/tag/weekly-snapshot
I tried to set all this up again today, but I can't refresh the INDIGO server if it has Nexstar in the list. Anything else seems fine, but if it's in there it crashes.
As soon as you click refresh, it populates some entries but the whole program freezes then crashes.
My logs on Arch look the same as some posted above. However, on Fedora I get a nasty C++ error:
/usr/include/c++/11/bits/stl_vector.h:1045: std::vector<_Tp, _Alloc>::reference std::vector<_Tp, _Alloc>::operator[](std::vector<_Tp, _Alloc>::size_type) [with _Tp = INDI::BaseClient::BLOBMode*; _Alloc = std::allocator<INDI::BaseClient::BLOBMode*>; std::vector<_Tp, _Alloc>::reference = INDI::BaseClient::BLOBMode*&; std::vector<_Tp, _Alloc>::size_type = long unsigned int]: Assertion '__n < this->size()' failed.
I can't run the app images on either my Arch or Fedora system for some reason. I am running the official 0.21.2 release on both Arch and Fedora.
@Maxattax97 can you still reproduce this on latest stable (v23.3) ?
Indigo server provides a kind of superset of INDI. If it sees a legacy INDI client it falls back to support that protocol.
I have tried many configuration variations with the telescope plugin. When I hit "Connect" it sits there sayin "Connecting" apparently never getting connected. Log.txt shows it's done something as all the devices are listed. It has connected about 3 times out of 50 but would not issue a slew when I hit cmd+1. On the occasions that it has connected, if I issue a slew from another client, the stellarium scope position tracks to follow the slew. I have tested the INDIGO server with both Carte du Ciel and Kstars so I know the fall-back protocol is working fine. I have attached the current log and two screenshots log.txt You can see from the second screen shot that it knows where the scope is pointing. If I click on Dubhe it Identifies it as the scope (Mount)
I'm running a Macbook Pro with Catalina. INDIGO server is on a Raspberry Pi with up to date os (Buster) As I say - it's fine with Carte and Kstars. If you need anything more from me let me know (however that works)