¿ªÔÆÌåÓý

  1. Losmandy_users
  2. Messages
Expanded Topics Messages Polls
Date
Re: TCP connection

 

i'm not sure how we got from TCP and Indi discussion to this, but absolutely give it a try and love to hear the results


On Wed, May 27, 2020 at 5:31 PM Jamie Amendolagine <jamie.amendolagine@...> wrote:
Seems like this may be the same issue as Magnus found in another post. I'm going to try the beta firmware as that seems to fix it.



--
Brian?



Brian Valente
portfolio

Re: TCP connection

 

Seems like this may be the same issue as Magnus found in another post. I'm going to try the beta firmware as that seems to fix it.
Re: TCP connection

 

Oh, is that a setting in the handset?
Re: TCP connection

 
Edited

i was referring to something else - "stop guiding when slew detected"
?
PHD can send guiding commands and they do not interfere with slewing. or i should say they don't interfere under normal circumstances.?

?
?

On Wed, May 27, 2020 at 12:24 PM Jamie Amendolagine <jamie.amendolagine@...> wrote:
I'm guiding with PHD2, and do have the option set to not send guide commands, but from the log they are being sent.?

?

?


?
--
Brian?
?
?
?
Brian Valente
portfolio

Re: TCP connection

 

I'm guiding with PHD2, and do have the option set to not send guide commands, but from the log they are being sent.?
Re: TCP connection

 

Re: TCP connection

 

What are you using to guide?

Usually guiding is unknown to the mount, and it's really up to the guide software to stop guiding on slew (there's an option for that in PHD) but i would not expect guiding on or off to impact ability to slew

On Wed, May 27, 2020 at 11:51 AM Jamie Amendolagine <jamie.amendolagine@...> wrote:
I'm going to get a reduced log of the successful slew and post that here. Next I'll post both to the indi forum. I haven't narrowed down which condition triggers it. I'm wondering now though if I should explicitly stop guiding before slewing and see if that helps. Would you expect timed guide commands that happen during a slew to cause any issue??

Jamie?



--
Brian?



Brian Valente
portfolio

Re: TCP connection

 

OK so here's the log of the successful slew. I'll post to the indi forum and add the link here.?

Jamie
Re: TCP connection

 

I'm going to get a reduced log of the successful slew and post that here. Next I'll post both to the indi forum. I haven't narrowed down which condition triggers it. I'm wondering now though if I should explicitly stop guiding before slewing and see if that helps. Would you expect timed guide commands that happen during a slew to cause any issue??

Jamie?
Re: TCP connection

 

>>>2020-05-27T06:42:20: Driver indi_lx200gemini: queuing responsible for <newNumberVector device='Losmandy Gemini' name='TELESCOPE_TIMED_GUIDE_WE'>


sounds like it's an Indi driver issue. have you tried posting to the indi forum?

have you been able to determine conditions in which slewing works and slewing does not work?



On Wed, May 27, 2020 at 11:24 AM Jamie Amendolagine <jamie.amendolagine@...> wrote:
I should try and be accurate instead of funny. I'm really not sure I understand the limits very well, but it was definitely not anywhere close to hitting anything, and it seemed to be in a safe pointing position where it had been before. I'm not sure of the details though.?

Looking closer at that log, there does seem to be a difference between the successful slew, and the failed one. The successful one is getting a progress report regularly about once every second:

2020-05-27T06:42:05: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini EQUATORIAL_EOD_COORD Busy
2020-05-27T06:42:06: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini EQUATORIAL_EOD_COORD Busy
2020-05-27T06:42:07: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini EQUATORIAL_EOD_COORD Busy
...

And the failed one has all sorts of things going on, including timed guides (I'm pretty sure that I set phd2 to not guide during slews). It only get's it's "EQUATORIAL_EOD_COORD Busy" message a few times then goes to?EQUATORIAL_EOD_COORD Idle
2020-05-27T06:42:20: Driver indi_lx200gemini: queuing responsible for <newNumberVector device='Losmandy Gemini' name='TELESCOPE_TIMED_GUIDE_WE'>

I've managed to trim down the log of the failed slew to a reasonable size, and attached it.?



--
Brian?



Brian Valente
portfolio

Re: TCP connection

 

I should try and be accurate instead of funny. I'm really not sure I understand the limits very well, but it was definitely not anywhere close to hitting anything, and it seemed to be in a safe pointing position where it had been before. I'm not sure of the details though.?

Looking closer at that log, there does seem to be a difference between the successful slew, and the failed one. The successful one is getting a progress report regularly about once every second:

2020-05-27T06:42:05: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini EQUATORIAL_EOD_COORD Busy
2020-05-27T06:42:06: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini EQUATORIAL_EOD_COORD Busy
2020-05-27T06:42:07: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini EQUATORIAL_EOD_COORD Busy
...

And the failed one has all sorts of things going on, including timed guides (I'm pretty sure that I set phd2 to not guide during slews). It only get's it's "EQUATORIAL_EOD_COORD Busy" message a few times then goes to?EQUATORIAL_EOD_COORD Idle
2020-05-27T06:42:20: Driver indi_lx200gemini: queuing responsible for <newNumberVector device='Losmandy Gemini' name='TELESCOPE_TIMED_GUIDE_WE'>

I've managed to trim down the log of the failed slew to a reasonable size, and attached it.?
Re: Strage issue

 

Hi Magnus

There was a beta release of firmware put out to address this. You can search the forums here for it, or if you can't find it please drop me a line

On Wed, May 27, 2020 at 10:29 AM Magnus Larsson <magnus@...> wrote:
Hi guys!

So here is "Mr. Strange problems" with a really strange problem.

What happens is this: at times the mount simply "runs away" (well,
doesn't leave the back yard, but slews to a very strange position). THis
has happened quite a lot lately, probably because I've been extensively
observing variable stars and that includes a lot of slews and
alignments. So in some detail:

Slew to a star. Alingment (plate solve). Adjustment something like 10"
in RA. Mount starts a wild slew, ends up some 5 hours Hour Angle away,
or gets stuck in the safety limit.

So I thought this was Indi/Ekos related, because that is the system I
work with. We've been extensively testing and exploring, and today were
able to repeatedly reproduce the error. It seems to happen when there is
a slew in RA of around 10".

So to eliminate things here, we decided to switch to windows and test it
there. That's why I asked before about how to enter coordinates in
Gemini.net.

Now, my experience of Gemini.net is not altogether solid. It seems to
not react sometimes (???). However, when it does, I can easily reproduce
the error there. THat is: a slew in about 10" in RA at least at times
causes a slew far away.

So: can anyone else reproduce this? IN that case, it must be a bug in
the Gemini software, rather than in Indi drivers. If not, it might be
something in my particular Gemini 2.

Just to be clear: I've worked extensively with the Indi developers on
this, so it does exist, but is obviously something that happens quite
rarely, during regular use of the mount. I think I have produced it more
often by running more than 20 jobs each night for some time.

And: of course my alignment accepts more than 10" off target. But this
happens when the RA part is about 10" - the Dec might be more. That's
our current hypothesis, at least.

Anyone recognizes anything from this?Or can reproduce? If you try to
slew 10" i RA, particularly on the eastern part of the sky (don't know
if that matters but there is where I've found it), can you reproduce a
"wild slew"?


Details: this happened last night, at 23:46. Target was IX Lyr:

1. Slew to RA 18:29:41, Dec 32:15:39.

2. Plate solve.

3. Then a differential slew to 18:29:30 and 32:11:47.

4. Ending up far far away.


I can probably produce a video of it in a few days.

Magnus







--
Brian?



Brian Valente
portfolio

Strage issue

 

Hi guys!

So here is "Mr. Strange problems" with a really strange problem.

What happens is this: at times the mount simply "runs away" (well, doesn't leave the back yard, but slews to a very strange position). THis has happened quite a lot lately, probably because I've been extensively observing variable stars and that includes a lot of slews and alignments. So in some detail:

Slew to a star. Alingment (plate solve). Adjustment something like 10" in RA. Mount starts a wild slew, ends up some 5 hours Hour Angle away, or gets stuck in the safety limit.

So I thought this was Indi/Ekos related, because that is the system I work with. We've been extensively testing and exploring, and today were able to repeatedly reproduce the error. It seems to happen when there is a slew in RA of around 10".

So to eliminate things here, we decided to switch to windows and test it there. That's why I asked before about how to enter coordinates in Gemini.net.

Now, my experience of Gemini.net is not altogether solid. It seems to not react sometimes (???). However, when it does, I can easily reproduce the error there. THat is: a slew in about 10" in RA at least at times causes a slew far away.

So: can anyone else reproduce this? IN that case, it must be a bug in the Gemini software, rather than in Indi drivers. If not, it might be something in my particular Gemini 2.

Just to be clear: I've worked extensively with the Indi developers on this, so it does exist, but is obviously something that happens quite rarely, during regular use of the mount. I think I have produced it more often by running more than 20 jobs each night for some time.

And: of course my alignment accepts more than 10" off target. But this happens when the RA part is about 10" - the Dec might be more. That's our current hypothesis, at least.

Anyone recognizes anything from this?Or can reproduce? If you try to slew 10" i RA, particularly on the eastern part of the sky (don't know if that matters but there is where I've found it), can you reproduce a "wild slew"?


Details: this happened last night, at 23:46. Target was IX Lyr:

1. Slew to RA 18:29:41, Dec 32:15:39.

2. Plate solve.

3. Then a differential slew to 18:29:30 and 32:11:47.

4. Ending up far far away.


I can probably produce a video of it in a few days.

Magnus
Re: TCP connection

 

>>> At some point the mount gives the beep! warning that it's going to hit an iceberg, but strangely the telescope is pointing straight up at the sky, where there is definitely no iceberg

assuming what you mean is RA was nearly horizontal, you could very well be hitting your east or west mount limit

On Wed, May 27, 2020 at 9:43 AM Jamie Amendolagine <jamie.amendolagine@...> wrote:
So what happened last night was roughly the same. I spent some time doing imaging, everything working just hunky dory. I then do a few slews and things go haywire again. After maybe the third slew the mount just stops before reaching the target, and SF just sits there waiting for the slew to complete and it never does. I end up hitting the "stop" button on SF, and that seems to go fine. I then try another slew, and it does the same thing. At some point the mount gives the beep! warning that it's going to hit an iceberg, but strangely the telescope is pointing straight up at the sky, where there is definitely no iceberg.? Looking at the log, I don't see anything different from a successful slew, and one where it just stops, other than an "abort!" message that I'm going to guess happened when I hit the "stop" button. So I'm not sure what went wrong really, but it appears to not be on the SF <-> Indi-server side. It appears to be somewhere between the driver and the mount, and I'm not seeing that level of detail, at least not in my filtered logs. I guess I can try and clip out the complete log between successful and failed slews...

Gory details below:
---------

OK, so doing this cuts the file size quite a bit, only looking at 10 million lines of log!

tail -n 10000000 /log.txt | grep Losmandy > logSnip.txt

I'm not sure what the exact meaning of the log messages are so I'm going to guess :P

This looks like a successful slew:
L115: 2020-05-27T06:41:40: Driver indi_lx200gemini: read message Losmandy Gemini? ?'[INFO] Slewing to RA: 15:40:08 - DEC: 36:34:18'
L509: 2020-05-27T06:42:15: Driver indi_lx200gemini: read message Losmandy Gemini? ?'[INFO] Slew is complete. Tracking...'

This looks like the first failed slew, I'm guessing that this is where things go wrong:
L555: 2020-05-27T06:42:20: Driver indi_lx200gemini: read message Losmandy Gemini? ?'[INFO] Slewing to RA: 16:42:24 - DEC: 36:25:22'

This appears to be the where I hit stop in SF:
L673: 2020-05-27T06:42:27: Client 11: read newSwitchVector Losmandy Gemini TELESCOPE_ABORT_MOTION?
?
There are several slew commands that happen after like here:?
L724: 2020-05-27T06:42:30: Driver indi_lx200gemini: read message Losmandy Gemini? ?'[INFO] Slewing to RA: 16:42:24 - DEC: 36:25:22'

First error, maybe when I turn off the mount:
2020-05-27T06:43:11: Driver indi_lx200gemini: read message Losmandy Gemini? ?'[ERROR] Error reading RA/DEC.'
?
Unfortunately I don't see any errors before this, and the first failed slew does not look all that different from the successful slew other than it never get's a??'[INFO] Slew is complete. Tracking...'
------------------------------------------
Trying to break it down a bit more, here's a filter of driver messages "indi_lx200gemini"
Last successful slew:
2020-05-27T06:42:04: Driver indi_lx200gemini: read message Losmandy Gemini? ?'[INFO] Slewing to RA: 15:40:08 - DEC: 36:34:18'
2020-05-27T06:42:04: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini TARGET_EOD_COORD Idle
2020-05-27T06:42:04: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini EQUATORIAL_EOD_COORD Busy
2020-05-27T06:42:05: Driver indi_lx200gemini: read setSwitchVector Losmandy Gemini TELESCOPE_TRACK_STATE Idle
2020-05-27T06:42:05: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini EQUATORIAL_EOD_COORD Busy
2020-05-27T06:42:06: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini EQUATORIAL_EOD_COORD Busy
2020-05-27T06:42:07: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini EQUATORIAL_EOD_COORD Busy
2020-05-27T06:42:08: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini EQUATORIAL_EOD_COORD Busy
2020-05-27T06:42:09: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini EQUATORIAL_EOD_COORD Busy
2020-05-27T06:42:10: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini EQUATORIAL_EOD_COORD Busy
2020-05-27T06:42:11: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini EQUATORIAL_EOD_COORD Busy
2020-05-27T06:42:12: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini EQUATORIAL_EOD_COORD Busy
2020-05-27T06:42:13: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini EQUATORIAL_EOD_COORD Busy
2020-05-27T06:42:14: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini EQUATORIAL_EOD_COORD Busy
2020-05-27T06:42:15: Driver indi_lx200gemini: read setSwitchVector Losmandy Gemini TELESCOPE_SLEW_RATE Ok
2020-05-27T06:42:15: Driver indi_lx200gemini: read message Losmandy Gemini? ?'[INFO] Slew is complete. Tracking...'

First unsuccessful slew:
2020-05-27T06:42:20: Driver indi_lx200gemini: read message Losmandy Gemini? ?'[INFO] Slewing to RA: 16:42:24 - DEC: 36:25:22'
2020-05-27T06:42:20: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini TARGET_EOD_COORD Idle
2020-05-27T06:42:20: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini EQUATORIAL_EOD_COORD Busy
2020-05-27T06:42:20: Driver indi_lx200gemini: queuing responsible for <newNumberVector device='Losmandy Gemini' name='TELESCOPE_TIMED_GUIDE_WE'>
2020-05-27T06:42:20: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini TELESCOPE_TIMED_GUIDE_WE Busy
2020-05-27T06:42:20: Driver indi_lx200gemini: read setSwitchVector Losmandy Gemini TELESCOPE_TRACK_STATE Idle
2020-05-27T06:42:20: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini EQUATORIAL_EOD_COORD Busy
2020-05-27T06:42:21: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini EQUATORIAL_EOD_COORD Busy
2020-05-27T06:42:22: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini EQUATORIAL_EOD_COORD Idle
2020-05-27T06:42:22: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini TELESCOPE_TIMED_GUIDE_WE Idle
2020-05-27T06:42:22: Driver indi_lx200gemini: queuing responsible for <newNumberVector device='Losmandy Gemini' name='TELESCOPE_TIMED_GUIDE_NS'>
2020-05-27T06:42:22: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini TELESCOPE_TIMED_GUIDE_NS Busy
2020-05-27T06:42:23: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini EQUATORIAL_EOD_COORD Idle
2020-05-27T06:42:23: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini TELESCOPE_TIMED_GUIDE_NS Idle
2020-05-27T06:42:24: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini EQUATORIAL_EOD_COORD Idle
2020-05-27T06:42:27: Driver indi_lx200gemini: queuing responsible for <newSwitchVector device='Losmandy Gemini' name='TELESCOPE_ABORT_MOTION'>
2020-05-27T06:42:27: Driver indi_lx200gemini: read setSwitchVector Losmandy Gemini TELESCOPE_ABORT_MOTION Ok
2020-05-27T06:42:28: Driver indi_lx200gemini: read setSwitchVector Losmandy Gemini TELESCOPE_TRACK_STATE Busy
2020-05-27T06:42:28: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini EQUATORIAL_EOD_COORD Ok
2020-05-27T06:42:30: Driver indi_lx200gemini: queuing responsible for <newSwitchVector device='Losmandy Gemini' name='ON_COORD_SET'>
2020-05-27T06:42:30: Driver indi_lx200gemini: queuing responsible for <newNumberVector device='Losmandy Gemini' name='EQUATORIAL_EOD_COORD'>
2020-05-27T06:42:30: Driver indi_lx200gemini: read setSwitchVector Losmandy Gemini ON_COORD_SET Ok
2020-05-27T06:42:30: Driver indi_lx200gemini: read message Losmandy Gemini? ?'[INFO] Slewing to RA: 16:42:24 - DEC: 36:25:22'
2020-05-27T06:42:30: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini TARGET_EOD_COORD Idle
2020-05-27T06:42:30: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini EQUATORIAL_EOD_COORD Busy
2020-05-27T06:42:31: Driver indi_lx200gemini: read setSwitchVector Losmandy Gemini TELESCOPE_TRACK_STATE Idle
2020-05-27T06:42:31: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini EQUATORIAL_EOD_COORD Busy
2020-05-27T06:42:32: Driver indi_lx200gemini: queuing responsible for <newNumberVector device='Losmandy Gemini' name='TELESCOPE_TIMED_GUIDE_WE'>
2020-05-27T06:42:32: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini EQUATORIAL_EOD_COORD Busy
2020-05-27T06:42:32: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini TELESCOPE_TIMED_GUIDE_WE Busy
2020-05-27T06:42:33: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini EQUATORIAL_EOD_COORD Busy
2020-05-27T06:42:34: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini EQUATORIAL_EOD_COORD Busy
2020-05-27T06:42:35: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini TELESCOPE_TIMED_GUIDE_WE Idle
2020-05-27T06:42:35: Driver indi_lx200gemini: queuing responsible for <newNumberVector device='Losmandy Gemini' name='TELESCOPE_TIMED_GUIDE_NS'>
2020-05-27T06:42:35: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini TELESCOPE_TIMED_GUIDE_NS Busy
2020-05-27T06:42:35: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini EQUATORIAL_EOD_COORD Busy
2020-05-27T06:42:36: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini EQUATORIAL_EOD_COORD Busy
2020-05-27T06:42:36: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini TELESCOPE_TIMED_GUIDE_NS Idle
2020-05-27T06:42:37: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini EQUATORIAL_EOD_COORD Busy
2020-05-27T06:42:38: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini EQUATORIAL_EOD_COORD Busy
2020-05-27T06:42:39: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini EQUATORIAL_EOD_COORD Busy
2020-05-27T06:42:40: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini EQUATORIAL_EOD_COORD Busy
2020-05-27T06:42:41: Driver indi_lx200gemini: queuing responsible for <newNumberVector device='Losmandy Gemini' name='TELESCOPE_TIMED_GUIDE_WE'>
2020-05-27T06:42:41: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini TELESCOPE_TIMED_GUIDE_WE Busy
2020-05-27T06:42:41: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini EQUATORIAL_EOD_COORD Busy
2020-05-27T06:42:42: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini EQUATORIAL_EOD_COORD Busy
2020-05-27T06:42:43: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini TELESCOPE_TIMED_GUIDE_WE Idle
2020-05-27T06:42:43: Driver indi_lx200gemini: queuing responsible for <newNumberVector device='Losmandy Gemini' name='TELESCOPE_TIMED_GUIDE_NS'>
2020-05-27T06:42:43: Driver indi_lx200gemini: queuing responsible for <newSwitchVector device='Losmandy Gemini' name='TELESCOPE_ABORT_MOTION'>
2020-05-27T06:42:43: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini TELESCOPE_TIMED_GUIDE_NS Busy
2020-05-27T06:42:43: Driver indi_lx200gemini: read message Losmandy Gemini? ?'[INFO] Guide aborted.'
2020-05-27T06:42:43: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini TELESCOPE_TIMED_GUIDE_NS Idle
2020-05-27T06:42:43: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini TELESCOPE_TIMED_GUIDE_WE Idle
2020-05-27T06:42:43: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini EQUATORIAL_EOD_COORD Idle
2020-05-27T06:42:43: Driver indi_lx200gemini: read message Losmandy Gemini? ?'[INFO] Slew/Track aborted.'





--
Brian?



Brian Valente
portfolio

Re: TCP connection

 

So what happened last night was roughly the same. I spent some time doing imaging, everything working just hunky dory. I then do a few slews and things go haywire again. After maybe the third slew the mount just stops before reaching the target, and SF just sits there waiting for the slew to complete and it never does. I end up hitting the "stop" button on SF, and that seems to go fine. I then try another slew, and it does the same thing. At some point the mount gives the beep! warning that it's going to hit an iceberg, but strangely the telescope is pointing straight up at the sky, where there is definitely no iceberg.? Looking at the log, I don't see anything different from a successful slew, and one where it just stops, other than an "abort!" message that I'm going to guess happened when I hit the "stop" button. So I'm not sure what went wrong really, but it appears to not be on the SF <-> Indi-server side. It appears to be somewhere between the driver and the mount, and I'm not seeing that level of detail, at least not in my filtered logs. I guess I can try and clip out the complete log between successful and failed slews...

Gory details below:
---------

OK, so doing this cuts the file size quite a bit, only looking at 10 million lines of log!

tail -n 10000000 /log.txt | grep Losmandy > logSnip.txt

I'm not sure what the exact meaning of the log messages are so I'm going to guess :P

This looks like a successful slew:
L115: 2020-05-27T06:41:40: Driver indi_lx200gemini: read message Losmandy Gemini? ?'[INFO] Slewing to RA: 15:40:08 - DEC: 36:34:18'
L509: 2020-05-27T06:42:15: Driver indi_lx200gemini: read message Losmandy Gemini? ?'[INFO] Slew is complete. Tracking...'

This looks like the first failed slew, I'm guessing that this is where things go wrong:
L555: 2020-05-27T06:42:20: Driver indi_lx200gemini: read message Losmandy Gemini? ?'[INFO] Slewing to RA: 16:42:24 - DEC: 36:25:22'

This appears to be the where I hit stop in SF:
L673: 2020-05-27T06:42:27: Client 11: read newSwitchVector Losmandy Gemini TELESCOPE_ABORT_MOTION?
?
There are several slew commands that happen after like here:?
L724: 2020-05-27T06:42:30: Driver indi_lx200gemini: read message Losmandy Gemini? ?'[INFO] Slewing to RA: 16:42:24 - DEC: 36:25:22'

First error, maybe when I turn off the mount:
2020-05-27T06:43:11: Driver indi_lx200gemini: read message Losmandy Gemini? ?'[ERROR] Error reading RA/DEC.'
?
Unfortunately I don't see any errors before this, and the first failed slew does not look all that different from the successful slew other than it never get's a??'[INFO] Slew is complete. Tracking...'
------------------------------------------
Trying to break it down a bit more, here's a filter of driver messages "indi_lx200gemini"
Last successful slew:
2020-05-27T06:42:04: Driver indi_lx200gemini: read message Losmandy Gemini? ?'[INFO] Slewing to RA: 15:40:08 - DEC: 36:34:18'
2020-05-27T06:42:04: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini TARGET_EOD_COORD Idle
2020-05-27T06:42:04: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini EQUATORIAL_EOD_COORD Busy
2020-05-27T06:42:05: Driver indi_lx200gemini: read setSwitchVector Losmandy Gemini TELESCOPE_TRACK_STATE Idle
2020-05-27T06:42:05: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini EQUATORIAL_EOD_COORD Busy
2020-05-27T06:42:06: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini EQUATORIAL_EOD_COORD Busy
2020-05-27T06:42:07: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini EQUATORIAL_EOD_COORD Busy
2020-05-27T06:42:08: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini EQUATORIAL_EOD_COORD Busy
2020-05-27T06:42:09: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini EQUATORIAL_EOD_COORD Busy
2020-05-27T06:42:10: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini EQUATORIAL_EOD_COORD Busy
2020-05-27T06:42:11: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini EQUATORIAL_EOD_COORD Busy
2020-05-27T06:42:12: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini EQUATORIAL_EOD_COORD Busy
2020-05-27T06:42:13: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini EQUATORIAL_EOD_COORD Busy
2020-05-27T06:42:14: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini EQUATORIAL_EOD_COORD Busy
2020-05-27T06:42:15: Driver indi_lx200gemini: read setSwitchVector Losmandy Gemini TELESCOPE_SLEW_RATE Ok
2020-05-27T06:42:15: Driver indi_lx200gemini: read message Losmandy Gemini? ?'[INFO] Slew is complete. Tracking...'

First unsuccessful slew:
2020-05-27T06:42:20: Driver indi_lx200gemini: read message Losmandy Gemini? ?'[INFO] Slewing to RA: 16:42:24 - DEC: 36:25:22'
2020-05-27T06:42:20: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini TARGET_EOD_COORD Idle
2020-05-27T06:42:20: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini EQUATORIAL_EOD_COORD Busy
2020-05-27T06:42:20: Driver indi_lx200gemini: queuing responsible for <newNumberVector device='Losmandy Gemini' name='TELESCOPE_TIMED_GUIDE_WE'>
2020-05-27T06:42:20: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini TELESCOPE_TIMED_GUIDE_WE Busy
2020-05-27T06:42:20: Driver indi_lx200gemini: read setSwitchVector Losmandy Gemini TELESCOPE_TRACK_STATE Idle
2020-05-27T06:42:20: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini EQUATORIAL_EOD_COORD Busy
2020-05-27T06:42:21: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini EQUATORIAL_EOD_COORD Busy
2020-05-27T06:42:22: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini EQUATORIAL_EOD_COORD Idle
2020-05-27T06:42:22: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini TELESCOPE_TIMED_GUIDE_WE Idle
2020-05-27T06:42:22: Driver indi_lx200gemini: queuing responsible for <newNumberVector device='Losmandy Gemini' name='TELESCOPE_TIMED_GUIDE_NS'>
2020-05-27T06:42:22: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini TELESCOPE_TIMED_GUIDE_NS Busy
2020-05-27T06:42:23: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini EQUATORIAL_EOD_COORD Idle
2020-05-27T06:42:23: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini TELESCOPE_TIMED_GUIDE_NS Idle
2020-05-27T06:42:24: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini EQUATORIAL_EOD_COORD Idle
2020-05-27T06:42:27: Driver indi_lx200gemini: queuing responsible for <newSwitchVector device='Losmandy Gemini' name='TELESCOPE_ABORT_MOTION'>
2020-05-27T06:42:27: Driver indi_lx200gemini: read setSwitchVector Losmandy Gemini TELESCOPE_ABORT_MOTION Ok
2020-05-27T06:42:28: Driver indi_lx200gemini: read setSwitchVector Losmandy Gemini TELESCOPE_TRACK_STATE Busy
2020-05-27T06:42:28: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini EQUATORIAL_EOD_COORD Ok
2020-05-27T06:42:30: Driver indi_lx200gemini: queuing responsible for <newSwitchVector device='Losmandy Gemini' name='ON_COORD_SET'>
2020-05-27T06:42:30: Driver indi_lx200gemini: queuing responsible for <newNumberVector device='Losmandy Gemini' name='EQUATORIAL_EOD_COORD'>
2020-05-27T06:42:30: Driver indi_lx200gemini: read setSwitchVector Losmandy Gemini ON_COORD_SET Ok
2020-05-27T06:42:30: Driver indi_lx200gemini: read message Losmandy Gemini? ?'[INFO] Slewing to RA: 16:42:24 - DEC: 36:25:22'
2020-05-27T06:42:30: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini TARGET_EOD_COORD Idle
2020-05-27T06:42:30: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini EQUATORIAL_EOD_COORD Busy
2020-05-27T06:42:31: Driver indi_lx200gemini: read setSwitchVector Losmandy Gemini TELESCOPE_TRACK_STATE Idle
2020-05-27T06:42:31: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini EQUATORIAL_EOD_COORD Busy
2020-05-27T06:42:32: Driver indi_lx200gemini: queuing responsible for <newNumberVector device='Losmandy Gemini' name='TELESCOPE_TIMED_GUIDE_WE'>
2020-05-27T06:42:32: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini EQUATORIAL_EOD_COORD Busy
2020-05-27T06:42:32: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini TELESCOPE_TIMED_GUIDE_WE Busy
2020-05-27T06:42:33: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini EQUATORIAL_EOD_COORD Busy
2020-05-27T06:42:34: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini EQUATORIAL_EOD_COORD Busy
2020-05-27T06:42:35: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini TELESCOPE_TIMED_GUIDE_WE Idle
2020-05-27T06:42:35: Driver indi_lx200gemini: queuing responsible for <newNumberVector device='Losmandy Gemini' name='TELESCOPE_TIMED_GUIDE_NS'>
2020-05-27T06:42:35: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini TELESCOPE_TIMED_GUIDE_NS Busy
2020-05-27T06:42:35: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini EQUATORIAL_EOD_COORD Busy
2020-05-27T06:42:36: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini EQUATORIAL_EOD_COORD Busy
2020-05-27T06:42:36: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini TELESCOPE_TIMED_GUIDE_NS Idle
2020-05-27T06:42:37: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini EQUATORIAL_EOD_COORD Busy
2020-05-27T06:42:38: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini EQUATORIAL_EOD_COORD Busy
2020-05-27T06:42:39: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini EQUATORIAL_EOD_COORD Busy
2020-05-27T06:42:40: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini EQUATORIAL_EOD_COORD Busy
2020-05-27T06:42:41: Driver indi_lx200gemini: queuing responsible for <newNumberVector device='Losmandy Gemini' name='TELESCOPE_TIMED_GUIDE_WE'>
2020-05-27T06:42:41: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini TELESCOPE_TIMED_GUIDE_WE Busy
2020-05-27T06:42:41: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini EQUATORIAL_EOD_COORD Busy
2020-05-27T06:42:42: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini EQUATORIAL_EOD_COORD Busy
2020-05-27T06:42:43: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini TELESCOPE_TIMED_GUIDE_WE Idle
2020-05-27T06:42:43: Driver indi_lx200gemini: queuing responsible for <newNumberVector device='Losmandy Gemini' name='TELESCOPE_TIMED_GUIDE_NS'>
2020-05-27T06:42:43: Driver indi_lx200gemini: queuing responsible for <newSwitchVector device='Losmandy Gemini' name='TELESCOPE_ABORT_MOTION'>
2020-05-27T06:42:43: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini TELESCOPE_TIMED_GUIDE_NS Busy
2020-05-27T06:42:43: Driver indi_lx200gemini: read message Losmandy Gemini? ?'[INFO] Guide aborted.'
2020-05-27T06:42:43: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini TELESCOPE_TIMED_GUIDE_NS Idle
2020-05-27T06:42:43: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini TELESCOPE_TIMED_GUIDE_WE Idle
2020-05-27T06:42:43: Driver indi_lx200gemini: read setNumberVector Losmandy Gemini EQUATORIAL_EOD_COORD Idle
2020-05-27T06:42:43: Driver indi_lx200gemini: read message Losmandy Gemini? ?'[INFO] Slew/Track aborted.'
Re: TCP connection

 

OK, I caught it in the act with verbose logging last night. And wow that logging is quite verbose. 35G log file! Luckily it happened at the end so I can hopefully snip it down quite a bit. This is an indi log file so I'm going to cross post it to the indi forum to see what they can find. I'll take a shot at trying to understand what is going on and post it here later today.?

Jamie
Re: How to slew to coordinates with gemini.net

 

¿ªÔÆÌåÓý

Thanks! :)

Magnus

Den 2020-05-27 kl. 17:14, skrev Brian Valente:

Function->object and coordinates

On Wed, May 27, 2020 at 7:48 AM Magnus Larsson <magnus@...> wrote:
Hi!

I use Indi/ekos, but I'd need to test something by slewing to
coordinates in windows, with . However, I cannot find out how
to type in coordinates to slew to. Anyone can guide me on that?

Magnus






--
Brian?



Brian Valente
portfolio

Re: How to slew to coordinates with gemini.net

 

Function->object and coordinates


On Wed, May 27, 2020 at 7:48 AM Magnus Larsson <magnus@...> wrote:
Hi!

I use Indi/ekos, but I'd need to test something by slewing to
coordinates in windows, with . However, I cannot find out how
to type in coordinates to slew to. Anyone can guide me on that?

Magnus






--
Brian?



Brian Valente
portfolio

How to slew to coordinates with gemini.net

 

Hi!

I use Indi/ekos, but I'd need to test something by slewing to coordinates in windows, with gemini.net. However, I cannot find out how to type in coordinates to slew to. Anyone can guide me on that?

Magnus
Re: Cold Start unresponsive

 
Edited

Glad to help Erik you¡¯re the one fixing it not me. ?A notch in your skills! ? All I do is kinda look at it from basics being mostly the problems.?

I have had a HC misbehave like you had and this was one of the things I tried to fix it.....which helped a lot! But it could have been me as I took it apart and re-assembled and maybe I tightened the screws too much? ?


I wouldn¡¯t be surprised if this effect some HCs in cold ?weather ....contracting. ?Yes plastic etc have different temp coefficients but it¡¯s possible given tight mfgr tolerances.?
--
Brendan
17241 - 17260 of 83716