×
INDI Library v1.8.1 Released (09 Sep 2019)

Monthly maintenance release INDI v1.8.1

myFocuserPro or myFocuserPro2 and INDI

1 month 2 weeks ago 1 month 2 weeks ago by Acapulco Rolf.
Acapulco Rolf
Senior Boarder
Senior Boarder
Posts: 41
Karma: 2
More
myFocuserPro or myFocuserPro2 and INDI #44758
Thanks Alan and Robert and Jasem

Gave version 4 of the MyFP2 indi driver a sanity test run last night

Not the best night for it with the clouds rolling in, but gave it a shot

Video below of a focuser test on Caph.
Clouds made a mess of the V curve, but otherwise a good outcome




One observation, not confined to version 4 of the indi driver, but seems to be an issue on versions 1,2,3 and 4:

The focuser "Absolute Position" and "Max Position" fields do not always show the current values
both on the focuser settings page and also on the indi focuser page

See highlighted fields in the screen captures below for reference

Seems somewhat inconsistent as the two values do sometimes persist after a closing then re-opening
the indi/ekos windows but the values do not always seem to survive a full shutdown/restart of indi






Focused on Caph


Focuser firmware version 291
Attachments:

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

1 month 2 weeks ago
ajt68
Senior Boarder
Senior Boarder
Posts: 75
Karma: 1
More
myFocuserPro or myFocuserPro2 and INDI #44848
I had a proper play last night, though still quite cloudy, and could not get the issue with losing absolute and maximum position. Even powering everything down and starting again, all values were retained as expected.
Could you try with a completely fresh install, and again see if you can come up with a sequence that will reproduce the error you are seeing?

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

1 month 2 weeks ago
Acapulco Rolf
Senior Boarder
Senior Boarder
Posts: 41
Karma: 2
More
myFocuserPro or myFocuserPro2 and INDI #44860
Thanks Alan

I should point out that I observe the same issue with the kstars/indi Windows build (Windows 10) as well as directly with the kstars/indi build on Stellarmate on the Raspberry Pi

Shutting down the client windows and opening them up again will sometimes *not* show a value in the fields (hi-lighted in red in my screen captures) then for the same session shutting down
the client windows and stopping/re-starting indi will sometimes show a value in the field.

I observe that shutting down kstars completely and then restarting is another way that I'm able to reproduce the issue (sometimes)

I've not yet worked out the exact pattern/scenario to reproduce this consistently but I'll stick with it until I do.

A fresh install is a good idea. I have a vanilla build of Stellarmate on another SD card which I can bring into play.

I'll see about starting from that sd card then fetch the nightly build and then see if I can reproduce the issue

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

1 month 2 weeks ago
roberto
Junior Boarder
Junior Boarder
Posts: 29
More
myFocuserPro or myFocuserPro2 and INDI #44867
I think that the only way you might to the bottom of this is if the serial log files are looked at,
Thant would determine if it is a serial timeout issue, a serial timing issue on connect, or if it is a problem in either the firmware or higher up the chain.

Regards
Robert
The following user(s) said Thank You Acapulco Rolf

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

1 month 2 weeks ago 1 month 2 weeks ago by Acapulco Rolf.
Acapulco Rolf
Senior Boarder
Senior Boarder
Posts: 41
Karma: 2
More
myFocuserPro or myFocuserPro2 and INDI #44869
Thanks Rob

I'm now able to reproduce the issue consistently


Steps to reproduce the issue:

I'll walk through the steps to reproduce the issue based on Stellarmate as that's the build I use

1. Start up the Stellarmate Web Manager
stellarmate.local:8624

2. Start the INDI server
All devices defined in the equipment profile will start-up as expected

3. Open Kstars
4. From the Kstars "Tools" menu select "Ekos"
5. "Start" Ekos from the "Ekos Profile - KStars" GUI
In my case, I have it set in my equipmemt profile to "auto connect" all devices

6. Click "Connect" to connect all devices defined in the equipment profile
7. Once the "INDI Control Panel - Kstars" screen opens then navigate to the MyFocuserPro2 page

Note the values shown in "Absolute Position" and "Max Position" fields
e.g. In my case see the first screen capture below

Note the empty fields for Absolute Position and Max Position

8. Close the "INDI Control Panel - Kstars" screen
9. Click "Disconnect" to disconnect all devices
10. Stop Ekos
11. Close Kstars


Follow steps 3 through 7 again
Now note that this time once you get to step 7, the Absolute Position and Max Position fields are now populated as expected
e.g. In my case see the second screen capture below

12. Close all screens and disconnect devices
13. Stop the indi server via the Stellarmate web manager
stellarmate.local:8624


Repeat the steps 1 through 7 to reproduce the issue again

If you don't use Stellarmate, substitute steps 1,2 and 13 for the equivalent steps for your set-up

Abs and Max fields not populated




Abs and Max fields populated


Attachments:

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

1 month 2 weeks ago
ajt68
Senior Boarder
Senior Boarder
Posts: 75
Karma: 1
More
myFocuserPro or myFocuserPro2 and INDI #44884
I think we may have a misunderstanding here. Your first picture clearly shows the abs and max fields are filled in. The zeros are in the set fields, what ever value you choose to put in those fields and then click set will either move the focuser to the new position, or update the max field.

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

1 month 2 weeks ago 1 month 2 weeks ago by Acapulco Rolf.
Acapulco Rolf
Senior Boarder
Senior Boarder
Posts: 41
Karma: 2
More
myFocuserPro or myFocuserPro2 and INDI #44889
Thanks Alan

What causes the behaviour with the fields "to the right" getting populated/non-populated given the steps followed ?
NB: Nothing was manually changed when walking through those steps yet the fields "to the right" got set to zero and then subsequently got populated without any intervention

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

1 month 2 weeks ago 1 month 2 weeks ago by ajt68.
ajt68
Senior Boarder
Senior Boarder
Posts: 75
Karma: 1
More
myFocuserPro or myFocuserPro2 and INDI #44890
All I can say is that it is not driven from the driver. At the end of the day is it a bug or an annoyance, either way it is unexpected behaviour. Maybe ask the question in a separate thread, is there a gui forum?

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

1 month 2 weeks ago
pyb
Fresh Boarder
Fresh Boarder
Posts: 11
More
myFocuserPro or myFocuserPro2 and INDI #44894
Hi,

It seems to me this behaviour is frequent in other drivers and cannot be regarded as a bug nor an annoyance. In my opinion, there is no clear interest having this box filled out, as the value is already set in the left one at the connection.

Great thanks to the developer(s). I hope this driver will be included soon in the stable indi library.

BR, Pierre-Yves

Pierre-Yves
SW 200/1000, Evostar 72ED, EOS-100D, HEQ5-Pro (Rowan belt kit),
MyFP2ProM/v2.91 focuser, Joystick 8BitDo-N30,
Rpi3B+/Stellarmate 1.4.5 server, Dell Inspiron 13.3/Linux Mint 19.2

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

1 month 2 weeks ago 1 month 2 weeks ago by Acapulco Rolf.
Acapulco Rolf
Senior Boarder
Senior Boarder
Posts: 41
Karma: 2
More
myFocuserPro or myFocuserPro2 and INDI #44899
Hi Pierre-Yves

I wasn't aware that this behaviour was frequent in other drivers too. Good to know

I've logged it as an issue on the INDI github page

Thanks to Alan for the driver and also thanks to Rob :)

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

1 month 2 weeks ago
knro
Administrator
Administrator
Posts: 7391
Karma: 51
myFocuserPro or myFocuserPro2 and INDI #44904
Ok, here is what causes this behavior. If all drivers, you have updateProperties() function. In this function, we define or delete properties based on whether we are connecting or disconnecting.

If the properties are initialized _before_ we define them, then both the right and left fields in KStars would be equal. I just took a look at the driver code, and made changes so that values are read before we define them. I pushed the changes to master, please compile and retest.

Jasem Mutlaq
Support INDI & Ekos; Get StellarMate Astrophotography Gadget.
How to Submit Logs when you have problems?
Add your observatory info
The following user(s) said Thank You Acapulco Rolf

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

1 month 2 weeks ago
Acapulco Rolf
Senior Boarder
Senior Boarder
Posts: 41
Karma: 2
More
myFocuserPro or myFocuserPro2 and INDI #44916
Thanks Jasem
I've compiled the latest build with the v 0,5 MyFP2 changes and all appears to be well

I'm no longer able to reproduce the issue

Nice one

Thanks Alan, Rob and Jasem

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

Time to create page: 1.357 seconds