Welcome, Guest
Username: Password: Remember me
08 Apr 2018
INDI development team is happy to announce the release of INDI Library v1.7.0. This new exciting release builds on the maturity of INDI Library and comes with many new supported devices and fixes for existing drivers.
Read More...

TOPIC: Avalon mzero Stargo with lx200 protocol

Avalon mzero Stargo with lx200 protocol 1 month 2 days ago #24374

Wolfgang, How do you feel about grabbing the focuser code I wrote and adding it to your driver? I have decided to halt development of the Telescope/Focuser driver combo I was working on so we can focus on a single Avalon driver. If that sounds good to you I'll start trying to break your driver :evil:

Please Log in or Create an account to join the conversation.

Avalon mzero Stargo with lx200 protocol 1 month 2 days ago #24380

Warmly welcome, go ahead!

And maybe we should spend some effort in a proper modularization. Because one huge class implementing all StarGO features might not be the best idea. Currently we need to modifiy LXGeneric in order to be able to subclass it and need to stay within the core framework. Maybe we can convince Jasem to change this so that we are able to move our implementation to a proper 3rdparty driver.

Please Log in or Create an account to join the conversation.

Avalon mzero Stargo with lx200 protocol 1 month 2 days ago #24389

Hello Wolfgang, hello CanisUrsa,
You join your work to write one driver : VERY GOOD NEWS.
Can you add a function in your driver : PushCloud () :) Because it is very difficult to test and use your driver with cloud.
I am waiting the information for the new one, to know if it will be int the git space of Wolfgang or CanisUrsa.

Please Log in or Create an account to join the conversation.

Last Edit: by Jean-Jacques.

Avalon mzero Stargo with lx200 protocol 1 month 1 day ago #24417

Hi Jean-Jacques,
the PushCloud() is not the problem, I will take it into the product backlog. The invest in the physical device might be challenging - better you start saving money now :-)

Wolfgang

Please Log in or Create an account to join the conversation.

Avalon mzero Stargo with lx200 protocol 1 week 4 days ago #24998

Hi folks,
the first imaging session with the new driver went almost fine. The driver worked perfectly fine for hours and I could take ~25 subs. The downside: my kstars client crashed after the meridian flip, so half of the night the scope was running, but no images were taken :angry:

Stay tuned...
Wolfgang

Please Log in or Create an account to join the conversation.

Avalon mzero Stargo with lx200 protocol 1 week 4 days ago #25001

Sorry about that, that's terrible. Please always run KStars in GDB so that if there is a crash, we'll get useful backtrace back. You can run it like this:
gdb --ex run --args kstars

If it crashes, just go back to the console and type in bt to get the backtrace and share that. Also the logs would be useful, but the backtrace is more useful in cases of crash.

Please Log in or Create an account to join the conversation.

Jasem Mutlaq
Support INDI & Ekos; Get StellarMate Astrophotography Gadget.
How to Submit Logs when you have problems?
Add your observatory info

Avalon mzero Stargo with lx200 protocol 1 week 4 days ago #25012

Thanks for the hint. I opened another thread here .

Wolfgang

Please Log in or Create an account to join the conversation.

Avalon mzero Stargo with lx200 protocol 1 week 3 days ago #25043

  • kengs
  • kengs's Avatar
  • Offline
  • Senior Boarder
  • Senior Boarder
  • Posts: 73
  • Karma: 1
  • Thank you received: 13
Great to see this work taking place. I am keen to help out if I can. I've had to revert to Windows since getting my M-Uno

CanisUrsa wrote: I have the ability to set the tracking rates and slewing rates. I haven't figured out how to query what the currently selected tracking rate and slewing rate is. One status command you might be interested in is :X34# it will return something like m00# where the first 0 is for RA, second 0 is for DEC. The higher the number, the faster that axis is moving. m10# indicates RA tracking only while m54# would indicate a fast slew on RA, and slightly slower slew on DEC.

I don't think that is quite right. I've been chasing down an issue in the ASCOM driver where it fails to notify PHD2 when a guiding pulse is complete till very late. So in response to a guiding command Mg (followed by n/e/s/w for direction and nnnnn for duration in ms) e.g. Mge00678 a follow up X34 command returns m40 meaning the mount is guiding in RA. Once guiding is complete the X34 command returns m10. At least thats how it looks.

Please Log in or Create an account to join the conversation.

Ubuntu 16.04 AMD64, RPi3 Ubuntu Mate 16.04, Windows 8.1 AMD64
EQ6 Pro, Atik420, ASI1600MM-C, ASI120MM-S, DBK21AU04, ZWO EFW
Vixen R150S, GSO RC8, ST80

Avalon mzero Stargo with lx200 protocol 1 week 3 days ago #25047

  • kengs
  • kengs's Avatar
  • Offline
  • Senior Boarder
  • Senior Boarder
  • Posts: 73
  • Karma: 1
  • Thank you received: 13
Aha. Just saw Wolfgangs code where 4 means Moving at low speed to refine. That makes sense. In any case no problem for PHD2 as it only polls for IsGuiding on ASCOM mountsand even then it is apparently not reliable.

Please Log in or Create an account to join the conversation.

Ubuntu 16.04 AMD64, RPi3 Ubuntu Mate 16.04, Windows 8.1 AMD64
EQ6 Pro, Atik420, ASI1600MM-C, ASI120MM-S, DBK21AU04, ZWO EFW
Vixen R150S, GSO RC8, ST80

Avalon mzero Stargo with lx200 protocol 6 days 11 hours ago #25189

  • kengs
  • kengs's Avatar
  • Offline
  • Senior Boarder
  • Senior Boarder
  • Posts: 73
  • Karma: 1
  • Thank you received: 13
Looking into things a bit more. I see that the StarGo ASCOM driver sends guiding pulses as %05d format versus the lx200 default of %04d. Not sure if this is a problem for the mount or not.
Also noticed that using the mount control, slewing even at highest speed was slow. I need to look deeper into this as I thought the default behaviour was that the 4 speeds correspond to Guiding, Centering, Finding and Slewing at the speeds set for each of those.
At face value, the INDI driver fixes an issue I'm having on ASCOM whereby there is often a long wait after a guide pulse is sent before PHD2 is informed that guiding has completed. I believe this is a bug in the ASCOM driver.

Please Log in or Create an account to join the conversation.

Ubuntu 16.04 AMD64, RPi3 Ubuntu Mate 16.04, Windows 8.1 AMD64
EQ6 Pro, Atik420, ASI1600MM-C, ASI120MM-S, DBK21AU04, ZWO EFW
Vixen R150S, GSO RC8, ST80

Avalon mzero Stargo with lx200 protocol 6 days 8 hours ago #25193

For setting the 4 speeds please use the ASCOM client. I haven't implemented changing the speeds yet.
Concerning pulse guiding: same thing, maybe it works occasionally, but I did not change the behavior of the underlying lx200telescope implementation. Does pulse guiding work?

Please Log in or Create an account to join the conversation.

Avalon mzero Stargo with lx200 protocol 6 days 6 hours ago #25202

  • kengs
  • kengs's Avatar
  • Offline
  • Senior Boarder
  • Senior Boarder
  • Posts: 73
  • Karma: 1
  • Thank you received: 13
I did have them set from ASCOM but the Slew speed was still slow. I'm a developer too so I'll dive into the code. When do you think you'll move the code to a branch of INDI?

Please Log in or Create an account to join the conversation.

Ubuntu 16.04 AMD64, RPi3 Ubuntu Mate 16.04, Windows 8.1 AMD64
EQ6 Pro, Atik420, ASI1600MM-C, ASI120MM-S, DBK21AU04, ZWO EFW
Vixen R150S, GSO RC8, ST80
Time to create page: 0.126 seconds

Login



3rd Party

Choose from the numerous 3rd party INDI drivers to suit your needs!

Got Problem?

Check out the FAQ, the forum, and the bug tracking system to resolve any issues you might have!
You can also subscribe to INDI newsletter and development mailing lists to get the latest updates on INDI!


Gallery

Replica

Why INDI

Replica