×
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.

myFocuserPro or myFocuserPro2 and INDI

7 months 1 week ago
roberto
Junior Boarder
Junior Boarder
Posts: 33
More
myFocuserPro or myFocuserPro2 and INDI #45062
Hi Alan
I think you have done more than your fair share so far!

Best wishes for a good game, lets hope the ref lets the game flow.
I'll cheer for my team, and you for yours. Here's to a cracker of a game.

Regards
Robert
The topic has been locked.
7 months 1 day ago
pyb
Fresh Boarder
Fresh Boarder
Posts: 15
More
myFocuserPro or myFocuserPro2 and INDI #45389
Hi Alan,

First, many thanks for the great job you are doing by developing this driver.

I am presently doing tests of a myFocuserPro2 connected to a RPI3B+/stellarmate 1.4.4 as server, the client being Kstars/Ekos on a laptop running Linux Mint (~ Ubuntu). The results are very good. I just would like to report a strange behaviour when playing with the joystick.
As I already use a joystick to manually move my HEQ5Pro mount, I thought to dedicate 3 of the free remaining buttons to also control the focuser. The buttons (in, out and abort) react reliably but the amount of steps when I push them, in or out, is "huge" and not constant, variyng roughly between 60 and 80 (~ 2 times my CFZ !). As it now stands, the joystick feature appears to be not really usable.

If I change from full step to 1/4 step mode, the number of step is multiplied by 4, which makes me to suspect the command sent is a time pulse and not a number of steps. Am I right ?

I didn't find any place in the INDI driver menus or Ekos/focus where to manage this parameter. Maybe the joystick support is a part of the driver development which is not yet finalised.

Thanks for bringing me some light.

Pierre-Yves

Pierre-Yves
SW 200/1000, SW 72ED, EOS-100D, ASI-178MC, HEQ5-Pro (Rowan belt kit),
MyFP2ProM/v2.92 focuser, Joystick 8BitDo-N30,
Rpi4/Stellarmate 1.5.2 server, Dell Inspiron 13.3/Linux Mint 19.3
The topic has been locked.
7 months 1 day ago
ajt68
Senior Boarder
Senior Boarder
Posts: 77
Karma: 1
More
myFocuserPro or myFocuserPro2 and INDI #45395
Th ejoystick support is implemented external to this driver, and probably does as you suggest, time based. You may want to raise this question in the general forum. I might take a look at the joystick code later, see if I can get a definitive answer.
The topic has been locked.
7 months 1 day ago
ajt68
Senior Boarder
Senior Boarder
Posts: 77
Karma: 1
More
myFocuserPro or myFocuserPro2 and INDI #45396
There is a MoveFocuser in the driver (I did not touch this function, assumed standard), but maybe able to do something in here. I think the options will be limited, based on number of steps/s or something similar, or perhaps divide whatever it is now by the inverse step mode (1, 2, 4, 8, 16....)

It is not something I have played with yet, but if I get time I will have a look this week.
The topic has been locked.
7 months 1 day ago
pyb
Fresh Boarder
Fresh Boarder
Posts: 15
More
myFocuserPro or myFocuserPro2 and INDI #45398
Thanks Alan for your reply.
I do not realize what that represents in terms of coding but the ideal would be to have something like in ekos/focuser, that is buttons with the possibility of choosing the number of steps.
This feature is not essential but could be convenient when observing at the eyepiece.
PY

Pierre-Yves
SW 200/1000, SW 72ED, EOS-100D, ASI-178MC, HEQ5-Pro (Rowan belt kit),
MyFP2ProM/v2.92 focuser, Joystick 8BitDo-N30,
Rpi4/Stellarmate 1.5.2 server, Dell Inspiron 13.3/Linux Mint 19.3
The topic has been locked.
7 months 1 day ago
ajt68
Senior Boarder
Senior Boarder
Posts: 77
Karma: 1
More
myFocuserPro or myFocuserPro2 and INDI #45400
I'll see what I can do, but you must remember Ekos and Indi are all about remote observing and automation.

When I built my myFocuserPro2 I added all the bells and whistles. The only feature left now is the temp sensor.

Disconnected the, display,in and out leds and In and out buttons! It is my intention to build another bare bone one that will fit in a very small footprint.
The topic has been locked.
7 months 5 hours ago 7 months 5 hours ago by ajt68.
ajt68
Senior Boarder
Senior Boarder
Posts: 77
Karma: 1
More
myFocuserPro or myFocuserPro2 and INDI #45451
I've managed to get debugging going with a joystick connected, and see that it is time based, it always seems to be 1s, and don't know where that is set? The other variable is the speed.

I could override this function, but with what? I think absolute position increments might work, but would be tiny, and only allowed one increment per second. The increments would be tiny because I think a maximum step size of 4 steps would be used, regardless of step mode. This is because I beleive ther are supposed to be about 10-12 steps at the focal point,(?) and so would give two or three presses at focus. My focuser at full step has 4900 steps full travel so

4900/4=1225s / 60 = 20 minutes, full travel!

Or perhaps speed 0 = 4 steps, speed 1= 20th full travel and speed 2=10th full travel? (if we went this way then we may as well have 1 step at speed 0, which might be a pain for the 1/16th 1/32nd step settings, but hey ho).

Any thoughts, anybody?


I'm going to code steps of 1,10 and 100 and see how it feels.
The topic has been locked.
7 months 5 hours ago
ajt68
Senior Boarder
Senior Boarder
Posts: 77
Karma: 1
More
myFocuserPro or myFocuserPro2 and INDI #45452
Having coded that, and then playing with the speed, it dawned on me that I could have just used the set relative step! I did also note that I could cause small fractions of steps, by feathering the joystick button, so I don't understand how that is working?
The topic has been locked.
7 months 3 hours ago
pyb
Fresh Boarder
Fresh Boarder
Posts: 15
More
myFocuserPro or myFocuserPro2 and INDI #45458
Hi Alan,
I appreciate your efforts to improve the joystick operation.
My feeling is that it should be nice if effectively you could use the set relative step. In that way each user could set a number of steps according to the gear reduction of his focuser system.
But maybe there is some drawbacks to implement this solution...
BR, Pierre-Yves

Pierre-Yves
SW 200/1000, SW 72ED, EOS-100D, ASI-178MC, HEQ5-Pro (Rowan belt kit),
MyFP2ProM/v2.92 focuser, Joystick 8BitDo-N30,
Rpi4/Stellarmate 1.5.2 server, Dell Inspiron 13.3/Linux Mint 19.3
The topic has been locked.
7 months 2 hours ago
ajt68
Senior Boarder
Senior Boarder
Posts: 77
Karma: 1
More
myFocuserPro or myFocuserPro2 and INDI #45463
Yes there does appear to be some draw backs, it does not seem that the relative steps step value is available in the derived class for the focuser. Even if it was it would need to be set each startup. I'm back to implementing a 1, 10, 100 movement based on speed, which does not take much effort to implement, and retains the setting between power cycles. Would this be better than the current solution, though I suspect the current solution is not behaving as expected.

I am thinking I will just leave as is for now, until someone explains how the in out joystick is intended to work.
The following user(s) said Thank You knro
The topic has been locked.
6 months 4 weeks ago
knro
Administrator
Administrator
Posts: 8000
Karma: 51
myFocuserPro or myFocuserPro2 and INDI #45473
You can find the implementation for Joystick button handling here: github.com/indilib/indi/blob/732c725eb17...indifocuser.cpp#L242

and the button defined here: github.com/indilib/indi/blob/732c725eb17.../indifocuser.cpp#L64

So in theory you add more buttons and you can change the behavior here. If the relative steps were set to say, a 100, then in theory pressing the button would move them by this much. Feel free to play around with the code in order to get the most desirable behavior keeping in mind that it should work for all kind of focusers (DC and steppers).

Jasem Mutlaq
Support INDI & Ekos; Get StellarMate Astrophotography Gadget.
How to Submit Logs when you have problems?
Add your observatory info
The topic has been locked.
6 months 4 weeks ago
ajt68
Senior Boarder
Senior Boarder
Posts: 77
Karma: 1
More
myFocuserPro or myFocuserPro2 and INDI #45490
Thanks for the heads up as to where in the code to look, and it looks to me like the code wold already do what we probably want. Unfortunately because this focuser has variable speed AND relative position, then the times move is used in preference the relative move.
From my point of view I would have thought relative move should have been first choice as it maintains accuracy of actual position.

My FocuserPro2 supports three speeds, so I assumed this means it is variable speed, but it is a stepper motor and not DC. Was this the intended purpose of variable speed or have I misunderstood? I don't see why a stepper motor would ever want to use a timed move as opposed to an abs/rel move.

I appreciate this is a global function, and so should not assume that everyone else would agree with my opinion, so how do we move forward on this?
The topic has been locked.
Time to create page: 0.672 seconds