×

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

Pretty much all developers hate GIT when they start working with it, then slowly comes in terms with its power. So everything is sorted out, thanks. Can you double check the code, is everything there?
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 #44430
The topic has been locked.
  • Posts: 19
  • Thank you received: 3
Hi everyone,

This is my first post.
I read carefully most of the threads on this forum since few months. In fact since I installed a RPi3b+, running Stellarmate as server for my astronomy equipment. I learn a lot and most of the time, I find answers to my questions. thanks to all for that.
I just received a "myFocuser Pro2" from Robert Brown in New Zeeland and I would like to test it, first via Kstars/Indi device manager and then, directly via ekos.
My problem is that I do not find the driver in the list of the focusers, even after having updated Indi... Probably I missed something :(

Thanks for your help,

Pierre-Yves
Pierre-Yves
SW 200/1000, SW 72ED, EOS-100D, ASI-178MC, HEQ5-Pro (Rowan belt kit),
MyFP2ProM/v305 focuser, Joystick 8BitDo-N30, GPS dongle
Rpi4-2Mb/Stellarmate 1.5.6 server, Dell Inspiron 13.3/Linux Mint 19.3
Kstars/Ekos 3.5.2
1 year 11 months ago #44431
The topic has been locked.
Hello Pierre-Yves,

Welcome to INDI forum. The focuser is not yet available in the stable release. It should be within a couple of weeks with the next stable release of INDI.
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 #44443
The topic has been locked.
  • Posts: 19
  • Thank you received: 3
Ok Jasem, thanks for your feedback. I was misled by the indi web page regarding this focuser that suggests that the driver is available.
Pierre-Yves
Pierre-Yves
SW 200/1000, SW 72ED, EOS-100D, ASI-178MC, HEQ5-Pro (Rowan belt kit),
MyFP2ProM/v305 focuser, Joystick 8BitDo-N30, GPS dongle
Rpi4-2Mb/Stellarmate 1.5.6 server, Dell Inspiron 13.3/Linux Mint 19.3
Kstars/Ekos 3.5.2
1 year 11 months ago #44444
The topic has been locked.
It is available in the INDI Nightly Builds.

The documentation says it is available INDI Library >= v1.8.2

Current stable INDI version is v1.8.1
Jasem Mutlaq
Support INDI & Ekos; Get StellarMate Astrophotography Gadget.
How to Submit Logs when you have problems?
Add your observatory info
Last edit: 1 year 11 months ago by Jasem Mutlaq.
1 year 11 months ago #44447
The topic has been locked.
  • Posts: 19
  • Thank you received: 3
Sorry, I did'nt pay attention to the Indi release numbering.
Thanks Jasem.
Pierre-Yves
SW 200/1000, SW 72ED, EOS-100D, ASI-178MC, HEQ5-Pro (Rowan belt kit),
MyFP2ProM/v305 focuser, Joystick 8BitDo-N30, GPS dongle
Rpi4-2Mb/Stellarmate 1.5.6 server, Dell Inspiron 13.3/Linux Mint 19.3
Kstars/Ekos 3.5.2
1 year 11 months ago #44448
The topic has been locked.
  • Posts: 77
  • Thank you received: 14
I've double checked the code and it looks like everything is as intended. Tested too!
The following user(s) said Thank You: Acapulco Rolf
1 year 11 months ago #44521
The topic has been locked.
  • Posts: 52
  • Thank you received: 15
Thanks Alan

About to run some sanity test on the latest MyFP2 indi driver build (version 3) against the v2.91 focuser firmware

Before I run any tests, I took a quick look at the MyFP2 indi driver source code on git

You mentioned that:

" I will then make the base firmware check equal to or greater than 291."

It looks like the minimum firmware version check is as follows:



Is this as intended?
1 year 11 months ago #44533
Attachments:
The topic has been locked.
  • Posts: 52
  • Thank you received: 15
Ah, I see the issue now

The commit for myfocuserpro2.h on your git fork
github.com/ajt68/indi/tree/master/drivers/focuser

is ahead of the commit on
github.com/indilib/indi/tree/master/drivers/focuser
1 year 11 months ago #44534
The topic has been locked.
  • Posts: 77
  • Thank you received: 14
OK lets regroup, my last commit is not what was intended!!!

I did a merge and believed I made the correct changes, then committed and did a pull, at which time I was told I was up to date. So I assumed because my changes were correct at my end, then that is what was committed.

I have just realised this is not the case, and the only change was the version number!!!??? This was discovered whilst setting up an AstroBerry, and pulling the latest nightly, I noticed my changes were not there.

So I have two file on my development end, that need to be committed via a pull request?
I guess the steps are
1. Create a commit (should I do some sort of sync first, and if so what should I do?).
2. Create a Pull Request at the head end, and associate the above commit?

I won't do anything until I get some feedback, as this is how I started getting in this mess, and can't understand why only the version number was committed?

TIA.
Last edit: 1 year 11 months ago by Alan Townshend.
1 year 11 months ago #44544
The topic has been locked.
  • Posts: 77
  • Thank you received: 14
So no feedback on what to do so I have just tried another commit and pull request and again a conflict, but I think I have now pushed/pulled the code I intended (version 0.4)
The following user(s) said Thank You: Acapulco Rolf
1 year 11 months ago #44652
The topic has been locked.
  • Posts: 52
  • Thank you received: 15
Nice one Alan

I see your (v 0.4) commits from yesterday on your git fork to the following code files:

myfocuserpro2.h
myfocuserpro2.cpp


Just waiting for these to be reflected in the main branch now

Perhaps Jasem can support on that


Last edit: 1 year 11 months ago by Acapulco Rolf.
1 year 11 months ago #44671
Attachments:
The topic has been locked.
Time to create page: 1.117 seconds