- Clean install of KStars357-2 on MacBook Pro Mojave
"Clean" means that I deleted the existing Application Support / Kstars and the 3 Preferences files
- Real Setup : Celestron, Microtouch focuser, 2 ZWO cameras, Maxdome
Only Celestron and focuser connected
Cameras : indi_asi_ccd crashed
My dome driver maxdomeII doesn't appear
- all simulators connected and KStars seems to work
"Thank you guys for testing, it really helps !!"
Rob, this is the LEAST we can do !
Thank you for your endeavours
Rob, it was "like the little dialog shown". KStars didn't crash but the little dialog shows again and again
The simulators also showed the same dialog
Thanks for your help with the Terminal but ... I restored already my disk from a backup
Hi Rob & Jasem,
KStars 357 seems to have produced a mess on my computer : I cannot run KStars 356 or 355 anymore. The app keeps bouncing on the dock.
A re-install of KStars 356 doesn't help
Any suggestions ?
I forgot to say that the "INDI Driver Reducer" is referring to my custom scope driver . In fact the driver is Celestron NexStar
Testing KStars 3.5.7 on MacBook Pro Mojave.
All INDI drivers crash (scope, dome, focuser, ASI cameras )
If I use a profile containing only the ASI cameras : crash again
I am unable to do this sort of thing !
I got also this bug on a fresh KStars installed on a new macOS disk.
Since INDI_sqm_weather v. 1.3 ( KStars 3.4.2) the driver seems to have issues.
Its size increased from 37 KB (v. 1.2) to 115 KB (v. 1.3) without changes in its interface.
I wonder why.
Thank you PDB for your comment on GPS : this was may be the real cause of my problem (on top of the FTDI / Prolific conflict)
I explain : I have a Celestron CGE Pro mount. Because that mount is not included in the Celestron list displayed by KStars, I chose "Celestron GPS" .
Somehow it worked but fairly frequently KStars crashed at the end of the session .
Because of your comments I replaced "Celestron GPS" by "Celestron NextStar" and this doesn't happen anymore.
Avocette, You are lucky.
I see that you are running Windows and I am running macOS.
May be the macOS version of KStars is the problem ?
I use a Unihedron SQM-LE device connected to KStars.
After a few minutes , it has a read overflow.
In order to test the origin of the overflow, I created a profile including only the SQM (+ a camera of course).
But the error was still there :
SQM : "[ERROR] Serial read error: Timeout error. "
SQM : "[ERROR] Serial read error: Read overflow. "
I use the latest version of KStars v.355 and an older one v.341. But the error was still there.
I attach the log.
(NOTE: when I use the udm app of Unihedron, I find no problem and the device works normally)