I think that the problem could arise from the fact that I run KStars (simulators) on two computers at the same time. And it might happen that they call the SQM-LE at the same time thus crashing the driver.
I will do more testings and I will report the results.
Read More...
I have a sky quality meter SQM-LE which is part of my KStars setting.
From time to time - KStars idles in the background - I ear clearly the fans of my computer which means that it uses suddenly a lot of power.
Effectively the app Activity Monitor shows the culprit : indi_sqm_weather.
And even two indi_sqm_weather drivers as can be seen in the attached doc.
In some occasions I saw even four( !) indi_sqm_weather drivers running at the same time.
I attach the log file.
Something is wrong with the driver or with the device ?
Read More...
JCJ wrote: While I am at it, I have been surprised that this USB 3 hub always connects my USB 3 cameras first, and not my USB 2 scope !
www.ebay.fr/itm/Sabrent-4-Port-Hub-USB-3...wqeVbuHKI:rk:12:pf:0
The link didn't appear in my reply ! The name of the hub is "Sabrent 4-Port Hub USB 3.0" with 4 independent switches
Read More...
While I am at it, I have been surprised that this USB 3 hub always connects my USB 3 cameras first, and not my USB 2 scope !
www.ebay.fr/itm/Sabrent-4-Port-Hub-USB-3...wqeVbuHKI:rk:12:pf:0
Read More...
I would like to add a point to this topic concerning the mixture of USB 2 and USB 3 devices connected to a same hub.
Remember to connect FIRST the USB 3 devices (cameras in my case) to the hub, and THEN the additional USB 2 devices (scope in my case).
The first device you plug in will configure the port, so always connect USB 3-capable hubs or devices first.
If you plug in a USB 2 hub first, all devices connected or "daisy-chained" to that hub will operate up to the maximum transfer rate of USB 2 speed (480 Mbps).
If you are on Apple, check connections with System Information (Apple () menu > About This Mac > System Report, then select : Hardware / USB, use ⌘R Refresh Information)
THEN power up the devices and start the astronomy software.
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...
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...