Jim S. replied to the topic 'Re:Ekos cannot guide using Nexstar Mount' in the forum. 4 days ago

mhammady wrote:

jws_indi wrote:

ChrisRowland wrote: You can't guide with a Nexstar mount that is mounted as alt Az. Lying to the system will not help because now the mount will not track correctly. If you look at what it's doing you will see that it isn't tracking properly.


Oops I posted the exact same thing below without seeing your post. Just here to steal thunder today :blush:


He could use a wedge...


Hi Chris, I definitely very interested in DYI wedge. I’m new to astrography, and want to slow down before spending another $1-1.5k on GEM. I still struggle with basic camera configuration and mount tracking. As soon as I can I will try this DYI wedge, and if was not successful I should just go and get GEM ;)


Thank you


Mohamed


Oh my, I am pretty sure you just insulted Chris... But its all good.

Your Welcome
Jim

Read More...

Jim S. replied to the topic 'Ekos cannot guide using Nexstar Mount' in the forum. 4 days ago

ChrisRowland wrote: You can't guide with a Nexstar mount that is mounted as alt Az. Lying to the system will not help because now the mount will not track correctly. If you look at what it's doing you will see that it isn't tracking properly.


Oops I posted the exact same thing below without seeing our post. Just here to steal thunder today :blush:


He could use a wedge... I do not recall if Celestron sells a wedge for this type of mount?!?!

Read More...

Jim S. replied to the topic 'Re:Ekos cannot guide using Nexstar Mount' in the forum. 4 days ago

mhammady wrote: Hi Chris,

I looked into the log and the following lines grabbed my attention.

<code>
[2020-05-16T20:28:48.009 EDT INFO ][ org.kde.kstars.indi] - Celestron NexStar : "[INFO] Mount is unparked. "
[2020-05-16T20:28:48.009 EDT INFO ][ org.kde.kstars.indi] - Celestron NexStar : "[INFO] Mount does not support guiding. Tracking mode must be set in handset to either EQ-North or EQ-South. "
[2020-05-16T20:28:48.015 EDT INFO ][ org.kde.kstars.indi] - Celestron NexStar : "[INFO] Mount UTC offset: -4.00. UTC time: 2020-05-17T00:28:45. DST: Off "
[2020-05-16T20:28:48.015 EDT INFO ][ org.kde.kstars.indi] - Setting UTC time from device: "Celestron NexStar" "Sun May 17 00:28:45 2020 GMT"
</code>

And in spite of this line, I can now see and use the mount as a destination for guide signal




Any idea whats going on? what I did wrong (or right)?


The NextStar mount is an Alt Az mount, inherently it will not track unless you place a 'wedge' between the tripod and the actual mount. After placing a wedge, you need to use your handset, look in setting or utilities to tell the mount that is is either a Northern Hemisphere or Southern Hemisphere Equatorial mount.

Cheers
Jim

Read More...

Jim S. replied to the topic 'Losmandy Slew goes haywire' in the forum. 4 days ago

amendolajamie wrote: Thanks for that link. That does seem to be the same issue. I have also discovered something tonight. From the logs of successful vs unsuccessful slew a difference that I noticed is that the failed slew has guide pulses happening after the slew is issued. I use PHD, and have checked the "don't guide while slewing" box, but somehow guide commands are still getting through. I tested the idea that the guide pulses are triggering this bad behavior, and was able to confirm it. I did almost a dozen slews around the sky with no problems. I then started guiding, and did a single slew, and it went haywire. It seems that the mount/gemini is supposed to handle this gracefully, but it does not. It also seems that phd2 is not supposed to be sending guide pulses if a slew was started.


I have not read any posts about PHD2 not suspending guiding during slew with any mounts. I am ignorant on this subject due to no experience with PHD2 and StellarMate as I use 'pulse' guiding.

Have you tried using pulse guiding and see if it does the same?

Cheers
Jim

Read More...

Jim S. replied to the topic 'Help understanding the log - what happened here?' in the forum. 4 days ago

ChrisRowland wrote: Are you really still a 'future G11 user'?


Yeah I can see where I might be seen as masochistic... Maybe I need to really think this one over? :huh:

Read More...

Jim S. replied to the topic 'Help understanding the log - what happened here?' in the forum. 6 days ago

ChrisRowland wrote: Yes, once we could extract a log showing the relevant information i.e. what commands were sent to the mount and what it did it was obvious. Absolutely nothng to do with Ekos. Everything to do with the mount.

The thing to remember is that correlation does not imply causation. Two things happening together need not be related.

None the less I think the Meridian flip enhancements should go. I am sick and tired of having to waste time defending them from random posts blaming them for everything except possibly bad weather.

Perhaps you should all start thinking before posting fake news.


For a future G11 user, this thread has enlightened me, I know it has been a pain for you and Jasem but it has been helpful to others !

Read More...

Jim S. replied to the topic 'Help understanding the log - what happened here?' in the forum. 6 days ago

mlarsson wrote: Hi all!

Latest news on this: after a long stretch of testing, that is, Jasem doing the testing and me mostly watching, we found out that this is indeed a mount issue. It is reproducible in windows. We found out how to systematically reproduce it and could do in win to.
And: it is actually a known issue (seemingly not well communicated though). THere is a beta firmware, and it seems to solve the issue!! (this far)

So thanks all for helping me out with this, and again, particularly to Chris for fixing that irritating side-of-pier issue that had nothing to do with this!!

One happy amateur over here!

Magnus


I am a future G11 user (as soon as I save a few more pennies :) ) Anyway I have read a few other posts on the Losmandy user group after following this post. Thank you all for the heads up Chris, Jasem and Magnus !

groups.io/g/Losmandy_users/topic/29574555#62167

groups.io/g/Losmandy_users/topic/32858271#63456

Read More...

Jim S. replied to the topic 'Losmandy Slew goes haywire' in the forum. 6 days ago

Sounds very much like what Magnus was seeing on his G11.

indilib.org/forum/general/6995-help-unde...t-happened-here.html

Read More...

Jim S. replied to the topic 'Gather gps data through gpsd daemon.' in the forum. 2 weeks ago

On Linux systems supporting udev, gpsd is normally started when a USB plugin event fires and is handed the name of the active device.

To see what devices are on the machine you can use $ lsdev

You can also run this at the command line $man gpsd

Which should output below, with some other information:

gpsd [-F control-socket] [-S listener-port] [-b] [-l] [-G] [-n] [-N] [-h] [-P pidfile] [-D debuglevel] [-V] [[source-name]...]

Typically Linux tries to assign a GPS device to /dev/ttyUSB0 or /dev/ttyS0

Have you tried the port manager within Ekos/Kstars to determine the port?

Jim

Read More...