Welcome, Guest
Username: Password: Remember me
25 Jul 2018
Glad to announce of release of INDI Library v1.7.4 on 2018-07-25. A few drivers were added in this release as we continue to improve & stabilize existing drivers.
Read More...

TOPIC: Avalon mzero Stargo with lx200 protocol

Avalon mzero Stargo with lx200 protocol 5 months 4 weeks ago #25206

Hm, strange. Mine worked that way.
There are no fix plans when I shift it to INDI. Currently I am collaborating with CanisUrsa who takes care of the focuser part. When the focuser and the telescope are working on my repository it might be the right time to announce it for beta-testing and shift it to INDI.

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

Avalon mzero Stargo with lx200 protocol 5 months 3 weeks ago #25232

  • kengs
  • kengs's Avatar
  • Offline
  • Expert Boarder
  • Expert Boarder
  • Posts: 118
  • Karma: 2
  • Thank you received: 25
After another look the mount control is working fine. I did have a long delay before the first move and after that it worked well. Some operator error as well as I was holding down the buttons rather than toggling. I did get a timeout error early on but that may be due to holding down the button.
I see that the Telescope Simulator labels the slew speeds as Max/Find/Center/Guide rather than 1x/2x/3x/4x which is more accurate. Maybe that can be incorporated into the driver. Odd that the lx200_telescope driver does not do this by default.
If I make changes can I submit with a pull request? No issue if you prefer to keep it inhouse for now - just offering to help where I can.
Maybe Jasem can also advise on coding conventions. I tend to overload virtual methods to customize whereas the new driver seems to write a parallel method and invoke it. I prefer get/set terminology to the query... naming used.

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

Ubuntu 16.04 AMD64 VM, RPi3 Ubuntu Mate 16.04, Windows 10 AMD64, Ubuntu 16.04 AAEON UP Core
Avalon M-Uno, EQ6 Pro, Atik420, ASI1600MM-C, ASI120MM-S, DBK21AU04, ZWO EFW, Optec TCFSi
Vixen R150S, GSO RC8, ST80

Avalon mzero Stargo with lx200 protocol 5 months 3 weeks ago #25243

Hi Ken,
feel free to submit a pull request. Any help is warmly welcome!
Wolfgang

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

Avalon mzero Stargo with lx200 protocol 2 months 1 week ago #28380

  • kengs
  • kengs's Avatar
  • Offline
  • Expert Boarder
  • Expert Boarder
  • Posts: 118
  • Karma: 2
  • Thank you received: 25
I've been doing some testing recently while the skies are cloudy. With USB connection it seems quite stable but I then tried the Wifi connection. The driver got itself in a twist when it received a :Z1030 from the mount instead of its expected response. I think this is some sort of notification of LST. Possibly mixed with tracking rate as it also received one :Z1033 as well. I'm guessing the final digit signifies the tracking rate:0=Sidereal, 3=Terrestrial(no tracking)
I'll have a go at handling these if no one else has done that already.

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

Ubuntu 16.04 AMD64 VM, RPi3 Ubuntu Mate 16.04, Windows 10 AMD64, Ubuntu 16.04 AAEON UP Core
Avalon M-Uno, EQ6 Pro, Atik420, ASI1600MM-C, ASI120MM-S, DBK21AU04, ZWO EFW, Optec TCFSi
Vixen R150S, GSO RC8, ST80

Avalon mzero Stargo with lx200 protocol 2 months 1 week ago #28387

Hi Ken,
hm, that's a strange state. The first "0" represents the motors state showing that both RA and DEC motor are off. The "3" indicates sidereal tracking and the last digit is the motion speed, where "0" stands for "guide speed" and "3" for "slew speed".

In detail: the three last digits represent the motion status of the mount as :Z1<motorsState><trackingSpeedState><motionSpeed> with the following semantics:
motorsState:
// m = 0 both motors are OFF (no power)
// m = 1 RA motor OFF DEC motor ON
// m = 2 RA motor ON DEC motor OFF
// m = 3 both motors are ON

trackingSpeedState:
// t = 0 no tracking at all
// t = 1 tracking at moon speed
// t = 2 tracking at solar speed
// t = 3 tracking at sidereal speed (stars)

motionSpeed:
// s = 0 GUIDE speed
// s = 1 CENTERING speed
// s = 2 FINDING speed
// s = 3 SLEWING speed

- Wolfgang
The following user(s) said Thank You: kengs

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

Avalon mzero Stargo with lx200 protocol 2 months 6 days ago #28402

  • kengs
  • kengs's Avatar
  • Offline
  • Expert Boarder
  • Expert Boarder
  • Posts: 118
  • Karma: 2
  • Thank you received: 25
Do you think this is a notification to the mount or a response to a command? I guessed it was a notification because it appeared in the log between other command/response pairs. Looking at it a bit closer it could be an additional response to a :X3C#
I'll analyse a bit more to see what the pattern is...

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

Ubuntu 16.04 AMD64 VM, RPi3 Ubuntu Mate 16.04, Windows 10 AMD64, Ubuntu 16.04 AAEON UP Core
Avalon M-Uno, EQ6 Pro, Atik420, ASI1600MM-C, ASI120MM-S, DBK21AU04, ZWO EFW, Optec TCFSi
Vixen R150S, GSO RC8, ST80

Avalon mzero Stargo with lx200 protocol 2 months 6 days ago #28405

  • kengs
  • kengs's Avatar
  • Offline
  • Expert Boarder
  • Expert Boarder
  • Posts: 118
  • Karma: 2
  • Thank you received: 25
I think I see what’s happening. The X3C gets the Z1nnn response but also the LST as a separate response. On USB this arrives before the next command and gets flushed but on wifi it arrives after the flush. So there should be a flush after the first response is read.

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

Ubuntu 16.04 AMD64 VM, RPi3 Ubuntu Mate 16.04, Windows 10 AMD64, Ubuntu 16.04 AAEON UP Core
Avalon M-Uno, EQ6 Pro, Atik420, ASI1600MM-C, ASI120MM-S, DBK21AU04, ZWO EFW, Optec TCFSi
Vixen R150S, GSO RC8, ST80

Avalon mzero Stargo with lx200 protocol 2 months 6 days ago #28407

Right, Z1nnn is the response to the :X3C# command.

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

Avalon mzero Stargo with lx200 protocol 2 months 5 days ago #28425

  • kengs
  • kengs's Avatar
  • Offline
  • Expert Boarder
  • Expert Boarder
  • Posts: 118
  • Karma: 2
  • Thank you received: 25
I’ll start by putting in a trace to see what is initiating the LST response then put in an appropriate handler. When done I’ll raise a pull request.

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

Ubuntu 16.04 AMD64 VM, RPi3 Ubuntu Mate 16.04, Windows 10 AMD64, Ubuntu 16.04 AAEON UP Core
Avalon M-Uno, EQ6 Pro, Atik420, ASI1600MM-C, ASI120MM-S, DBK21AU04, ZWO EFW, Optec TCFSi
Vixen R150S, GSO RC8, ST80

Avalon mzero Stargo with lx200 protocol 2 months 5 days ago #28432

Have you already turned on logging to file? With debugging turned on for the Avalon driver, you could find the entire LX200 communication in the log file under ~/.local/share/kstars/logs

- Wolfgang

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

Last Edit: by sterne-jaeger.

Avalon mzero Stargo with lx200 protocol 2 months 4 days ago #28451

  • kengs
  • kengs's Avatar
  • Offline
  • Expert Boarder
  • Expert Boarder
  • Posts: 118
  • Karma: 2
  • Thank you received: 25
I had to enable logging from LX200driver as well so now I'm seeing what is happening. All is going ok until :X362# command which receives an additional :Z1nnn response (unless there is an unlogged command sent) and that throws out the rest of the stream. When I was snooping on the USB stream a while back I did see that some of the X36n commands get two responses. I'll see if I can flush the second response

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

Ubuntu 16.04 AMD64 VM, RPi3 Ubuntu Mate 16.04, Windows 10 AMD64, Ubuntu 16.04 AAEON UP Core
Avalon M-Uno, EQ6 Pro, Atik420, ASI1600MM-C, ASI120MM-S, DBK21AU04, ZWO EFW, Optec TCFSi
Vixen R150S, GSO RC8, ST80

Avalon mzero Stargo with lx200 protocol 2 months 4 days ago #28475

  • kengs
  • kengs's Avatar
  • Offline
  • Expert Boarder
  • Expert Boarder
  • Posts: 118
  • Karma: 2
  • Thank you received: 25
Made a great deal of progress but it took quite a bit of refactoring. As far as I could tell the issues were related to the commands/responses that went through the LX200driver code. Each time I migrated a function from there to the Stargo driver that command stopped being a problem. Its possibly a problem n the object code and maybe resolvable by rebuilding everything together but the code needed a bit of a cleanup anyway.
Attached are a before and after log. Due to some other problem the lat/lon coords fortuitously do not point to my home.
I haven't yet tested all the functions.
Attachments:

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

Ubuntu 16.04 AMD64 VM, RPi3 Ubuntu Mate 16.04, Windows 10 AMD64, Ubuntu 16.04 AAEON UP Core
Avalon M-Uno, EQ6 Pro, Atik420, ASI1600MM-C, ASI120MM-S, DBK21AU04, ZWO EFW, Optec TCFSi
Vixen R150S, GSO RC8, ST80
Time to create page: 0.235 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