×
INDI Library v1.8.5 Released (19 Apr 2020)

April 2020 release of INDI Library v1.8.5 introduces new drivers while providing fixes and improvements to existing devices and core framework.

Avalon mzero Stargo with lx200 protocol

2 years 3 months ago 2 years 3 months ago by Jean-Jacques.
Jean-Jacques
Fresh Boarder
Fresh Boarder
Posts: 18
More
Topic Author
Avalon mzero Stargo with lx200 protocol #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.

2 years 3 months ago
sterne-jaeger
Platinum Boarder
Platinum Boarder
Posts: 573
Karma: 6
More
Avalon mzero Stargo with lx200 protocol #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

TSA-120 + FSQ-85 + GSO 150/750 | Avalon Linear + M-zero | Moravian G2-8300 + ASI 1600mm pro + ASI 294mc pro | KStars/INDI on Raspberry Pi 4 with Raspbian 10

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

2 years 3 months ago
sterne-jaeger
Platinum Boarder
Platinum Boarder
Posts: 573
Karma: 6
More
Avalon mzero Stargo with lx200 protocol #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

TSA-120 + FSQ-85 + GSO 150/750 | Avalon Linear + M-zero | Moravian G2-8300 + ASI 1600mm pro + ASI 294mc pro | KStars/INDI on Raspberry Pi 4 with Raspbian 10

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

2 years 3 months ago
knro
Administrator
Administrator
Posts: 8109
Karma: 51
Avalon mzero Stargo with lx200 protocol #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.

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

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

2 years 3 months ago
sterne-jaeger
Platinum Boarder
Platinum Boarder
Posts: 573
Karma: 6
More
Avalon mzero Stargo with lx200 protocol #25012
Thanks for the hint. I opened another thread here .

Wolfgang

TSA-120 + FSQ-85 + GSO 150/750 | Avalon Linear + M-zero | Moravian G2-8300 + ASI 1600mm pro + ASI 294mc pro | KStars/INDI on Raspberry Pi 4 with Raspbian 10

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

2 years 3 months ago
kengs
Expert Boarder
Expert Boarder
Posts: 153
Karma: 3
More
Avalon mzero Stargo with lx200 protocol #25043
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.

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

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

2 years 3 months ago
kengs
Expert Boarder
Expert Boarder
Posts: 153
Karma: 3
More
Avalon mzero Stargo with lx200 protocol #25047
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.

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

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

2 years 2 months ago
kengs
Expert Boarder
Expert Boarder
Posts: 153
Karma: 3
More
Avalon mzero Stargo with lx200 protocol #25189
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.

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

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

2 years 2 months ago
sterne-jaeger
Platinum Boarder
Platinum Boarder
Posts: 573
Karma: 6
More
Avalon mzero Stargo with lx200 protocol #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?

TSA-120 + FSQ-85 + GSO 150/750 | Avalon Linear + M-zero | Moravian G2-8300 + ASI 1600mm pro + ASI 294mc pro | KStars/INDI on Raspberry Pi 4 with Raspbian 10

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

2 years 2 months ago
kengs
Expert Boarder
Expert Boarder
Posts: 153
Karma: 3
More
Avalon mzero Stargo with lx200 protocol #25202
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?

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

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

2 years 2 months ago
sterne-jaeger
Platinum Boarder
Platinum Boarder
Posts: 573
Karma: 6
More
Avalon mzero Stargo with lx200 protocol #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.

TSA-120 + FSQ-85 + GSO 150/750 | Avalon Linear + M-zero | Moravian G2-8300 + ASI 1600mm pro + ASI 294mc pro | KStars/INDI on Raspberry Pi 4 with Raspbian 10

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

2 years 2 months ago
kengs
Expert Boarder
Expert Boarder
Posts: 153
Karma: 3
More
Avalon mzero Stargo with lx200 protocol #25232
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.

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

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

Time to create page: 0.428 seconds