Looks like it was a connection issue because of bad contact on USB port and mistake in our team. When we checked if it's connected by
I used the ZWO ASI 1600MC-Cool camera as usual for a few months, but suddenly (about a month ago) it lost the connection.
Now every time I try to connect to it, Kstars show me a pop-up:
No ASI cameras detected. Power on?
Bus 001 Device 008: ID 04b4:6572 Cypress Semiconductor Corp.
Description: Ubuntu 16.04.5 LTS Release: 16.04 Codename: xenial
Not sure that power can create a problem, but I will double check this as well.
Ok, I see, so I need to:
1. Set more precise time and a scope location
2. Correct the park position of the mount manually to match the default park position in Kstars
I thought that Kstars doesn't have default park point. I mean looks like there is some kind of a stepper position, which translated in Kstars as "position towards NCP".
But I expected that the first sync on NPC would overwrite this point. So I make the park position a stepper position when RA and DE Steps are both set to 10000000, so I can easily reset park position at this point, knowing, that this position is pointing to NCP. Looks like I was wrong.
But I still can't understand, can't I really manually set this default park position? It's just a wrong model of my mount in Kstars/INDI. Is it possible to set that "this" stepper position positioned towards NCP? Is there a model of my mount that is by default identify (when no alignment has been made at all) that some stepper position of the mount pointing to specific place in the sky?
Yes, I know it. My mount is properly aligned and in park position pointing exactly at the NCP. So the problem is only in Kstars or INDI. Why, if I drop all alignment points, and my mount is in the park position (pointing NCP), Kstars shows that my mount is pointing far away from NCP. Look at the attached picture: