×

INDI Library v1.9.2 Released (14 Sep 2021)

Bimonthly Stable INDI Library release introduces new drivers and fixes for existing ones.

myFocuserPro or myFocuserPro2 and INDI

  • Posts: 52
  • Thank you received: 15
Update:

OK, figured out the problem

It appears that the focuser "Max Postion" value isn't being "recognised" on initial connection of the focuser device even though it appears to be set when looking at the value for "Max Position" in the ekos driver GUI

Forcing the value of "Max Position" after connecting the focuser by entering the value via the ekos GUI manually then solves the problem

Looks like this might be a candidate for a "quick fix" in the driver source code

As an aside, errors are being reported in the ekos GUI for each movement of the focuser but the actual focuser travel is not affected

@Paul: Thanks, regarding your build of the focus driver code.
Maybe one of the indilib devs will be able to maintain the code if you make it public and push it to github


1 year 11 months ago #43916
Attachments:
The topic has been locked.
  • Posts: 193
  • Thank you received: 24

My github for is out of sync and i don't want to spend more time getting that correct again. Had to struggle too much with github to get some earlier development in. (it keeps telling me my fork is 1 commit ahead , and I am not going to try and figure this out)
So no!

Paul
1 year 11 months ago #43923
The topic has been locked.
I asked Alan (the driver developer) to look into these issues and hopefully soon we can have a fix for these problems.

@PDB Hope you feel better soon. If you can just zip and attach the code in your reply, that would be more than sufficient. We all appreciate your contribution. Get well soon.
Jasem Mutlaq
Support INDI & Ekos; Get StellarMate Astrophotography Gadget.
How to Submit Logs when you have problems?
Add your observatory info
1 year 11 months ago #43926
The topic has been locked.
  • Posts: 52
  • Thank you received: 15
@knro, thank you.

By the way, is there an equivalent kstars for Windows OS nightly build?

The last kstars Windows build I have is v 3.3.6 which does not appear to present the new MyFocuserPro2 INDI driver in the equipment setup interface

1 year 11 months ago #43970
Attachments:
The topic has been locked.
  • Posts: 77
  • Thank you received: 14
Hi guys, apologies for not responding sooner, but I have just back from an astro camp.

Regarding the IsMoving error reported, I cannot reproduce using firmware 280, but the debug log looks like the returned value has been modified should be I00 or I01, but is returning I0 or I1. I could fix this is the source driver, but maybe it should be fixed in the focuser firmware? I don't mind either way.

Regarding loosing the max position, again I cannot reproduce in 280. Can you give me the least amount of steps to reproduce the issue?

Were they the only two problems?
1 year 11 months ago #44024
The topic has been locked.
  • Posts: 52
  • Thank you received: 15
Hi Alan

Hope you had clear skies at the astro event.

Steps to reproduce the "Max Position" issue below:
Connect focuser through the indi connection GUI
Attempt to move the focus either in or out using the ekos focuser GUI (be ready to abort the focuser travel)

Note that the focuser will continue to move well past the set number of steps
Abort the focus movement using the ekos GUI

On inspection, the ekos GUI appears to show that Max Position is set as it should be
In my use case, Max Position = 10000 (see my earlier screen capture)

Re-enter and set the Max Position value by entering the value for Max Position in the ekos GUI
Now set the focuser to travel in or out using the ekos GUI and observe that the issue no longer occurs; the focuser moves the defined number of steps without issue

I can reproduce this every time using the steps above

I took a quick look at the source code but could not immediately see where the issue might be.
If I could get around to setting up a debug environment, I might be able to trace the code and debug

About to pop out for a while, so can respond further later once I get back

MyFP2 firmware version: DRVHW203.290
Last edit: 1 year 11 months ago by Acapulco Rolf.
1 year 11 months ago #44026
The topic has been locked.
  • Posts: 102
  • Thank you received: 7
Hello Developers,
I have four myFocuserPro's in use, so I am very pleased to hear, that a dedicated driver is in development. Thanks.
I have found only one bug yet. The temperature sensor is not working at all.
Thomas
Thomas Jäger
www.starhopper.eu
Linux Mint19.2
300/1200mm, 200/1000mm & 200/618mm Newton, Esprit 100/550mm, C 9.25"
SBIG STL11000M C2, Moravian G2-8300, ZWO ASI183MM-C and ASI2600
1 year 11 months ago #44029
Attachments:
The topic has been locked.
  • Posts: 52
  • Thank you received: 15
Hi Thomas

That's interesting to hear about what you observe with the temperature sensor

For me, I'm seeing that the temperature sensor reports temperature readings back to the ekos GUi as expected

I take it that you're not seeing any temperature values being reported back to the ekos focuser GUI...

Out of interest, which MyFP2 firmware version are you on?

FWIW, I'm running firmware version: DRVHW203.290
1 year 11 months ago #44032
The topic has been locked.
  • Posts: 102
  • Thank you received: 7
Hallo Rolf,
I am running firmware ULN2....290 and for reporting this, I have used the INDI driver dialog.
If I flash my hardware with myFocuserProV1 and use the INDI Moonlite driver, the temperature is reported in the driver and to the clients like CCDCiel and EKOS. So I think, my hardware is ok.
Thomas
Thomas Jäger
www.starhopper.eu
Linux Mint19.2
300/1200mm, 200/1000mm & 200/618mm Newton, Esprit 100/550mm, C 9.25"
SBIG STL11000M C2, Moravian G2-8300, ZWO ASI183MM-C and ASI2600
1 year 11 months ago #44039
The topic has been locked.
  • Posts: 52
  • Thank you received: 15
Hi Thomas

So it appears that we're both running the same MyFP2 .290 firmware version yet we see different outcomes with Alan's indi focus driver for the temperature readout

Might be worth sharing your indi debug logs here for a deeper dive
FYI: I'm seeing logs in this location on my device : ~/.local/share/kstars/logs

For me, I'm able to see the temperature reported back to the ekos GUI

Last edit: 1 year 11 months ago by Acapulco Rolf.
1 year 11 months ago #44044
Attachments:
The topic has been locked.
  • Posts: 35
  • Thank you received: 3
Hi

Can I please ask that only the latest firmware be used, at present v290, as I will not go back and change the firmware on previous releases. But if there are
issues in 290 I will address them with haste.

On the note of ismoving, the current return value is either 0 or 1. In prior releases it could have been 00 or 01. the INDI driver should
test for both (as does the Windows App or ASCOM drivers).

In terms of the temperature, nothing changed in the firmware. Use the Windows app to confirm that the temperature is being correctly reported from the controller. If it is appearing in Windows App v2xxxx then it removes the controller and firmware out of the picture.

I am not supporting any changes in "firmware" to make the INDI driver go. That could have the potential to break a lot of other dependent things. So that is not an option.

Can I suggest that if you are experiencing errant behavior with maxsteps etc, can I suggest that you also try that same procedures with the Windows App and the v290 firmware. If the behavior is the same it points to an issue in the firmware that I can readily resolve. That way we would not end up chasing things around too much?

regards
Roberto
Author: myfocuserpro2
1 year 11 months ago #44051
The topic has been locked.
  • Posts: 52
  • Thank you received: 15
Thanks Rob

Update:

#1
Attached the MyFP2 focuser to a laptop running the MyFP2 Windows client (version 2.4.3.9)
MyFP2 firmware version: DRVHW203.290

Focus Position = 3207
Max Steps = 10000

clicked the {+100} focuser travel button
focuser moves +100 steps as expected

clicked the {-100} focuser travel button
focuser moves -100 steps as expected

Ran the above focus travel moves 3 times. Focuser moves as commanded


#2
Connect focuser through the indi connection GUI on a Raspberry Pi 4 running kstars/ekos under Stellarmate (StellarmateOS_1.4.3_rpi4.img)
kstars version: 3.3.7
Attempt to move the focus either in or out using the ekos focuser GUI (be ready to abort the focuser travel)

The focuser will continue to move well past the commanded number of steps
Abort the focus movement using the ekos GUI

On inspection, the ekos GUI appears to show that Max Position is set as it should be
In my use case, Max Position = 10000 (see my earlier screen capture)

Regardless, re-enter and set the Max Position value by entering the value for Max Position in the ekos GUI
Now set the focuser to travel in or out using the ekos GUI and observe that the issue no longer occurs; the focuser moves the defined number of steps without issue



Just as an FYI, after applying the manual workaround above, I had the focuser in service last night with ekos under the stars using Alan's indi driver in between the rain clouds
IIRC, I slewed over to Capella to use as a focus target

Ekos auto focus seems to perform as expected, so all's well on that front with the focuser achieving focus under automation.

Just need to get to the bottom of the "Max Position" issue

Will carry out further field tests as the weather improves










Validated the focus achieved via ekos with a subsequent Bhatinov mask test:
Last edit: 1 year 11 months ago by Acapulco Rolf.
1 year 11 months ago #44081
The topic has been locked.
Time to create page: 1.597 seconds