I had big imaging plans for October : (
Need to get a back-up camera for cases like this...
Just checked the camera with ASIStudio under Windows.
Nope... Didn't work.
This was a bit of a coincidence.
I just completed a 21-hour project and decided to upgrade to the latest SM/KStars.
Upgraded. All devices were recognized. I set up optical trains and was ready to shoot tonight.
However, ASI2600 wouldn't capture and time out with an "ASIGetExpStatus failed. Restarting exposure..." message.
ASI120MM was working fine.
Changed cables. Reverted back to previous version. Tried with another RPI.
Tried with everything disconnected but the camera.
No.. still didn't work.
I guess it's dead. After 18 months of flawless operation.
It's still under warranty. Already contacted the vendor.
Sorry. Just wanted to share my pain...
Big plus from me!
SM/KStars/Ekos have been pretty reliable for me for about four years now.
One happy user here.
I also installed a fresh SM 1.7.2 64bit.
Same two problems:
-- Desktop Resolution doesn't work. I don't need it though since I was able to change the resolution in the Dashboard.
-- Network / Bluetooth icons are duplicated and flickering.
I ran into this just a couple of days ago too
Internal guider does not reuse calibration despite the fact that "Store and reuse..." option is selected.
I am not 100% sure but think it did work before.
Am I missing a check mark somewhere?
The "Store and reuse..." option didn't work right for any of my mounts until recently.
Now it works just fine with HEQ5.
Wanted to try with RST-135 but it recalibrates every time the guiding is stopped/restarted.
I complained about this a little while ago.
After I upgraded from 32-bit Stellarmate to 64-bit I was no longer able to access the shared folders on RPI (I had Pictures, Videos and Logs).
Changed permissions - didn't help.
Today I figured this out.
On 32-bit SM those folders resided in /media/stellarmate/Elements/
On 64-bit they are in /home/pi/
Edited smb.conf accordingly - now everything works.
Just reporting. Might help someone.
So, what is your conclusion?
IFAIK, both iPolar and IGuider do work under ASCOM.
iPolar works under INDI. iGuider doesn't work under INDI.
My CEM40G doesn't have USB3 hub. Only USB2.
iPolar and iGuider connect to it internally.
There's one USB external input which works.
INDI/Ekos do recognize both cameras but iGuider doesn't work properly.
My two cents.
Sadly, iGuider is not currently supported.
Jasem was experimenting with it recently and said that it might never be supported.
As far as I understand, iOptron never released an INDI driver for it.
Found "Override high DPI" option in Windows.
I upgraded my 1920x1200 monitor to 3840x2160.
Windows OS scaling is set to 150%.
On this Windows 10 PC/monitor I am running a KStars client connecting to RPI server.
Pretty much all applications are scaled nicely and look good but KStars.
KStars/Ekos windows are just too large and don't look good.
They are totally usable though.
Is there any way to scale KStars windows/dialogs down some? Say to 75% ?
P.S. I ran a session tonight with all latest updates. Not a single problem.
Subject:iOptron iGuider functionality
Ticket reference number:YQVC-001953
I also installed TeamViewer on my StellarMate.
I am able to connect to it from my desktop.
Will submit a ticket with TV details.
Thank you, Jasem.
Yes, I remember.
I did install TeamViewer on my Windows PC.
Wiling to test.
I have zero experience with TeamViewer, though.
I am using my Windows PC INDI client to connect to a remote RPI server.