¿ªÔÆÌåÓý

  1. Losmandy_users
  2. Messages
Expanded Topics Messages Polls
Date
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
Re: G11 RA needle bearings

 

Frank?

FYI we do not recommend lithium grease

we use jet-lube mp-50 moly paste



On Tue, May 26, 2020 at 6:27 PM Frank <ffowsky@...> wrote:


Presently experimenting with:
Mobil 1 5w-30

Previously used:
Slick 50 One Grease
Multipurpose Grease Fortified with Slick 50 PTFE Chemistry
Not smooth in the cold.

Next:
Lucas Oil White Lithium Grease 8 oz. Tube

My 90's CG11 has very little use as indicated by little to no roller bearing rub marks on the shaft.




--
Brian?



Brian Valente
portfolio

Re: G11 RA needle bearings

 


Presently experimenting with:
Mobil 1 5w-30

Previously used:
Slick 50 One Grease
Multipurpose Grease Fortified with Slick 50 PTFE Chemistry
Not smooth in the cold.

Next:
Lucas Oil White Lithium Grease 8 oz. Tube

My 90's CG11 has very little use as indicated by little to no roller bearing rub marks on the shaft.
Re: Cold Start unresponsive

 

nice work Erik!


On Tue, May 26, 2020 at 6:10 PM Erik Brogger via <EBrogger=[email protected]> wrote:
OK, I re-calibrated and backed off the screws a little. It's responsive now!
Thanks!

Now its starting to cloud up for the rest of the week!



--
Brian?



Brian Valente
portfolio

Re: Cold Start unresponsive

 

OK, I re-calibrated and backed off the screws a little. It's responsive now!
Thanks!

Now its starting to cloud up for the rest of the week!
Re: Cold Start unresponsive

 

Dear Brendan,

You make a really interesting point about a too-tight surface to the HC, but I gotta say I'm a little nervous about even slightly unscrewing something (by a half-turn) on a brand new product. I could give it a try, if something like this has been part of your experience...!

-Erik
Re: Cold Start unresponsive

Sonny Edmonds
 

Well, I'm still weird.

I fell asleep in my chair.
Out back, trying to figure out what was going wrong, and even the mosquitoes weren't keeping me awake.
Which was bad for them. My blood is toxic.
They get after sucking on me.

20 years! Hope you are on the mend, Brendan!

We may not be able to visit you due to this virus thing, but we can inflict pain by making you laugh online. ;^)
--
SonnyE


(I suggest viewed in full screen)
Re: NGC max cables

Sonny Edmonds
 

Hi Jay,
I got curious and

It it anything like these??


--
SonnyE


(I suggest viewed in full screen)
Re: TCP connection

Sonny Edmonds
 


--
SonnyE


(I suggest viewed in full screen)
Re: TCP connection

 

>>> I don't sync or align from SF, just do goto's. I do a goto then plate solve with ekos.?

sorry I didn't realize ekos was in the mix, but same thing: you are syncing from an external app, so it's possible to get a bad sync there.

>>>SF kept the goto button greyed out showing that it never reached it's target. I restarted SF and had a repeat of this behavior. At some point it went haywire.

? Didn't complete the slew? This is starting to sound more like an ekos issue. the gemini will never slew and then not report done. it may be inaccurate, but it will finish.?



On Tue, May 26, 2020 at 12:14 PM Jamie Amendolagine <jamie.amendolagine@...> wrote:
I don't sync or align from SF, just do goto's. I do a goto then plate solve with ekos. One weird thing I noticed was that I did a goto and it did not go all the way to the target. SF kept the goto button greyed out showing that it never reached it's target. I restarted SF and had a repeat of this behavior. At some point it went haywire.



--
Brian?



Brian Valente
portfolio

NGC max cables

 

NGC Max digital setting circles were installed on my G11 and I need a new cable. ?Its a Y-cable with RJ45 splitting into two RJ12s (or RJ11-not sure). ? Has anyone installed this on their G11? ?Jim's Mobile no longer exists as a separate company and I'm not sure if they're made. ?Does anyone know of a cable company that ?might make or carry this.
Re: Progress deep sky imaging with a C14HD f/11 on a G11.

 

Nicely done. I actually had to get rings for my Edge11 because balancing DEC was impossible with FW, camera, Moonlite, auto focuser, and the reducer; not to mention dangerous. Your 14 incher looks like and snug.?
17241 - 17260 of 83705