×
INDI Library v1.8.6 Released (21 Aug 2020)

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

Avalon Driver Setup

1 year 9 months ago
NicD
Fresh Boarder
Fresh Boarder
Posts: 12
More
Avalon Driver Setup #33354
Awesome! Now it works. Thanks for the quick fix.

Un-/parking and slewing works like a charm. I will test centering, syncing, tracking and guiding next time we get clear skies. I had some issues with the focuser, though. It is an Avalon FOCS connected to AUX1 of the mount. Indi doesn't seem to read the position. It stays at 0 when it moves out, and then doesn't allow me to move back in. But I only tested it for 5 minutes. I'll try again later.

Nic

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

1 year 9 months ago
sterne-jaeger
Platinum Boarder
Platinum Boarder
Posts: 656
Karma: 6
More
Avalon Driver Setup #33355
Hi Nic,
the Avalon FOCS interface is at a very early stage. Since I do not own an Avalon FOCS, I cannot test and fix it yet. But I will try to contact the author of the focuser code.
- Wolfgang

TSA-120 + FSQ-85 + GSO 150/750 | Avalon Linear + M-zero | Moravian G2-8300 + ASI 1600mm pro | KStars/INDI on Raspberry Pi 4 with Raspbian 10
The following user(s) said Thank You NicD

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

1 year 9 months ago
NicD
Fresh Boarder
Fresh Boarder
Posts: 12
More
Avalon Driver Setup #33358
Hi Wolfgang,

That would be fantastic. You guys are awesome! Let me know if I can be of any assistance.

Nic

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

1 year 9 months ago
sterne-jaeger
Platinum Boarder
Platinum Boarder
Posts: 656
Karma: 6
More
Avalon Driver Setup #33360
Could you please post the corresponding log file? I should sit unter ~/.local/share/kstars/logs

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

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

1 year 9 months ago
NicD
Fresh Boarder
Fresh Boarder
Posts: 12
More
Avalon Driver Setup #33361
Sure, see attached. I set the output mode to "verbose" and activated "Mount" and "Focuser" output for both Ekos and the driver. Then I pressed some buttons (move out, move in, sync position, set absolute position, change focuser speed).
Attachments:

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

1 year 9 months ago
sterne-jaeger
Platinum Boarder
Platinum Boarder
Posts: 656
Karma: 6
More
Avalon Driver Setup #33362
In the logs there is a warning:
Focus mode is halt. Select slow or fast mode
At least from the source code it looks like the focuser speed is set to "Halt". Are the buttons available on the INDI panel to set it to "Slow" or "Fast"?

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

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

1 year 9 months ago
NicD
Fresh Boarder
Fresh Boarder
Posts: 12
More
Avalon Driver Setup #33364
The speed dial is numerical (see attached). It defaults to a value of 2. The controls are enabled. I can change the value, but it has no effect on the actual speed.
Attachments:

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

1 year 9 months ago
sterne-jaeger
Platinum Boarder
Platinum Boarder
Posts: 656
Karma: 6
More
Avalon Driver Setup #33372
Hm, without a working Avalon FOCS, it is difficult to drill the problem down. One option would be that you download the sources and debug it on your own.

If you want to do it, I can assist you in setting up a development environment.

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

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

1 year 9 months ago
NicD
Fresh Boarder
Fresh Boarder
Posts: 12
More
Avalon Driver Setup #33379

sterne-jaeger wrote: Hm, without a working Avalon FOCS, it is difficult to drill the problem down. One option would be that you download the sources and debug it on your own.


I see. But to be honest, I would not even know where to start with the debugging and what to look for. Would it help if I give you TeamViewer access to my mount-side PC? I already pulled the source code of indi and kstars from github and compiled it. Plus I can point a camera at the focuser, so you get a live stream of the movements. I will re-install the PC anyway, so I don't care if you mess it up. And I will disengage all clutches of the mount and focuser, so you can't do any damage when testing movements. What do you think?

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

1 year 9 months ago
sterne-jaeger
Platinum Boarder
Platinum Boarder
Posts: 656
Karma: 6
More
Avalon Driver Setup #33427
Hi Nic,
we could give it a try. I will send you a private message.

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

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

1 year 9 months ago
CanisUrsa
Fresh Boarder
Fresh Boarder
Posts: 15
More
Avalon Driver Setup #33434
Hi NICD,

I wrote the initial version of the focuser interface. Currently I don't have much free time but I will see what I can do.

I have a couple of questions:
- What is the firmware version you are using for StarGO?
- Are you commanding the motor to move through the interface or are you physically moving it?
- If you are commanding the motor to move through the interface is it actually moving? (I think it moves out but wont move in)

I suspect I know what is happening but I will get back to you.

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

1 year 9 months ago
CanisUrsa
Fresh Boarder
Fresh Boarder
Posts: 15
More
Avalon Driver Setup #33435
I think I know what is going on.

The mount has a periodic function to query status like RA/DEC and what not. The focuser also has one as well but it isn't being called. The reason you can extend the focuser and not retract is because position commands to positive values are allowed, all extension motions produce positive values when referenced to 0. However retraction motions require a negative position (compared to the current position) which means you cant retract because the current position is always 0. The problem will be resolved once the focuser's query function is called periodically.

I will see what I can do to fix this. I know the design has changed a bit since I last looked at the code. The main difficulty will be in preventing the focuser from trying to query status while the mount is doing the same thing. The simplist thing might be to call the focuser's periodic update function at the end of the mount's periodic update function.

Chris
The following user(s) said Thank You sterne-jaeger

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

Time to create page: 0.724 seconds