The current bug has been solved in kstars v. 2.9.8
Thank you !

Read More...

I'm not an expert but I think that once the INDI driver for the Microtouch focuser has been fixed it should work correctly with all apps using it : AstroImager, KStars / Ekos ... Wait until the next release.

In the mean time the driver works as long that you keep the tick count in the range 0 - 32767. Easy to do.

Read More...

Hi suvowner,

1/ You'll find the MicroTouch Focus 1.1 for OS X here : www.stark-labs.com/downloads.html
This is however a very simple piece of software with which you'll not be able to do much.
The built-in driver is not an INDI driver as far as I know.

2/ Concerning TheSkyX sold by Software Bisque for $349.00 (TheSkyX alone, and then you'll have to buy all adds-on ending for around $1000) , I would really not recommend it to you because it's a simple robbery. Bisque has invented the MILKY WAY to get yearly money from its customers : you'll have to pay an extra $100.00 every year to get the software updates.
That a joke if you consider the extremely poor support. But a good business for Bisque.
Now, if you have extra bucks....

3/ The MicroTouch focuser is beautifully supported by KStars / Ekos through its INDI driver. There was still a minor bug which has just been corrected by Jasem. Enjoy.

Regards,

Read More...

OK, I opened an issue on the INDI github.
github.com/indilib/indi/issues/672
Regards,

Read More...

Eric,

This is true that I had the same focuser connection problem in March 2018 ( bugs.kde.org/show_bug.cgi?id=392148 ) and it got solved "by itself" through an unknown way. And now the problem comes back again ... through an unknown way .

My observatory is not Andromède but I published it as My Igloo in Laval (but I'm unable to give you a link to it).

I checked that the baud rate is 19200.

But You found the bug :
"Unless unless unless it is the position issue that goes over 32768 ticks? The Handshake function is managing a signed 16-bit, while the GetPosition function is managing a 32-bit. Could you try to move the focuser manually until its reported position is under that value before connecting?"
If I set the focuser manually below or equal 32767 : the focuser connects (see attachment)
If I set it above 32767 : the focuser doesn't connect.

There is definitely a bug in the INDI driver due to a integer/longint definition.

A big bravo for having found the bug !

Read More...

Bingo ! On a brand new macOS disk, I get exactly the same error : the Microtouch focuser can't connect.
It seems now to me that the fault is on the INDI driver side.

Read More...

No problem, Eric.

When KStars is not running and I run "lsof /dev/cu.SLAB_USBtoUART" in the Terminal, I get this :
iMac27:~ JCJ$ lsof /dev/cu.SLAB_USBtoUART
and when KStars is running, I get this :
iMac27:~ JCJ$ lsof /dev/cu.SLAB_USBtoUART
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
indi_micr 2285 JCJ 3u CHR 21,7 0t4 709 /dev/cu.SLAB_USBtoUART

I am trying to reinstall KStars on a brand new macOS X to see if I can connect.
If I can't, then the INDI driver is faulty.
What do you bet ?

Regards,

Read More...

I did write my comment on each step after your query.
On Step 2 : The port name was the correct one originally
On Step 6 + 7 : There was a red button on Step 6, and an error was reported on Step 7

After a restart, nothing changed and the problem was still there.

In the KStars Preferences I clicked on the "Restore default" button but this didn't solve anything.

Read More...

TallFurryMan wrote: The command says that the port is used by the Microtouch driver. Indeed. I wonder if it is the same issue as I have on my Moonlite.

Could you try the following:
1. Disable the auto search feature
It was/is disabled

2. Set the correct port name
Port name was/is correct : /dev/cu.SLAB_USBtoUART

3. Save the configuration
Saved

4. Disconnect and stop INDI from Ekos
OK

5. Start and connect INDI from Ekos
OK

6. Check the Microtouch panel console, it should only display the first communication error (that is, no autosearch).
OK : 2018-07-31T14:59:19: [INFO] Error retreiving data from Microtouch, please ensure Microtouch controller is powered and the port is correct.

Connect button should have a red light.
OK : red light

7. Click connect in the INDI panel.
Here is the status bar content IN RED : 2018-07-31T15:00:44: [ERROR] Failed to connect to port (/dev/cu.SLAB_USBtoUART). Error: Port failure Error: Resource busy. Check if device is connected to this port.
See attached screenshot

Proceed with these steps, and tell me what you configure at step 2 and what you observe on steps 6 and 7.

-Eric

In Terminal the output is this :
MacBookProJCJ:~ JCJ$ lsof /dev/cu.SLAB_USBtoUART
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
indi_micr 668 JCJ 3u CHR 21,11 0t4 673 /dev/cu.SLAB_USBtoUART
MacBookProJCJ:~ JCJ$

In KStars v.2.9.7 I just created a profile containing only the Microtouch focuser and a CCD.
The focuser is directly connected to the computer.

******* Here is what is reported in the status bar :
2018-07-31T13:15:21: [ERROR] Failed to connect to port (/dev/cu.SLAB_USBtoUART). Error: Port failure Error: Resource busy. Check if device is connected to this port.
2018-07-31T13:15:07: [INFO] Error retreiving data from Microtouch, please ensure Microtouch controller is powered and the port is correct.

******* Attached log file "log_15-12-51"

Thanks for your help

Read More...

Thanks Eric, but it doesn't seem to work in Terminal (and in my hands).
The idea is good : some process keeps the port for itself preventing KStars to access it.

Read More...

Since a few days, my Microtouch focuser refuses to connect to all softwares using the INDI protocol (KStars, INDI Control Panel, AstroLive).
Conversely other softwares not using the INDI protocol (TheSkyX, Nebulosity4, MicroTouch Focus 1.1) still connect perfectly.
Thus the connection problem I'm encountering is not a faulty setup.
The reported INDI error says : "Error: Port failure Error: Resource busy. Check if device is connected to this port"
I am using KStars v. 2.9.7 on a Mac and before everything was working fine on the usual port /dev/cu.SLAB_USBtoUART.
Any idea ?

Read More...

There is a shutter problem with the INDI MaxDome II driver.
For example, the app AstroTelescope of CloudMakers keeps saying "Shutter error" and the dome rotation simply doesn’t work.
It seems to me that the MaxDome II driver is waiting for a response of a second MaxDome board which takes care of the shutter opening.
I have only one MaxDome board to take care of the dome rotation and I open the dome shutters manually.
Also, the INDI Control Panel shows two red buttons - meaning that it is not happy : "Ticks per Turn", "Shutter Operation Azimuth".
Also the dome measurements and the Ticks per Turn are not accepted by the INDI Control Panel of CloudMakers probably because it is busy with the shutter error.
Any idea ? Thank you.

Read More...