Thank you for the response!

Today I have performed a simple test.
- I connected to the mount and unparked it.
- I slewed to the Saturn (far after transit). It works ok. The side of the pier was correct: east pointing west.
- I slewed to Pleyades (far before transit which is around 3 AM in my timezone). It works ok. The side of the pier was updated correctly to west pointing east. 
- I slewed to Andromeda Galaxy (transit in about 4 hours, around the midnight). The scope shouldn't change the side of the pier but it did. As I wrote before the meridian flip is scheduled after more than 12 hours (attached image), which indicates that the mount knows that it is on the wrong side of pier.
By the way I was unable to set the debug on - the driver instantly turned it of. The same behaviour was under AP GTOCP2 driver. Here is the log copied from the indi console:


2021-10-12T19:09:42: [INFO] Debug is disabled. 
2021-10-12T19:09:42: [INFO] Debug is enabled. 
2021-10-12T19:09:26: [ERROR] Error reading from device Timeout error (-4) 
2021-10-12T19:09:13: [ERROR] Error reading from device Timeout error (-4) 
2021-10-12T19:08:32: [ERROR] Error reading from device Timeout error (-4) 
2021-10-12T19:06:43: [ERROR] Error reading from device Timeout error (-4) 
2021-10-12T19:06:39: [ERROR] Error reading from device Timeout error (-4) 
2021-10-12T19:05:44: [INFO] Slew is complete. Tracking... 
2021-10-12T19:05:38: [ERROR] Error reading from device Timeout error (-4) 
2021-10-12T19:04:49: [INFO] Slewing to RA: 0:43:56 - DEC: 41:23:20 
2021-10-12T19:04:24: [INFO] Slew is complete. Tracking... 
2021-10-12T19:03:13: [INFO] Slewing to RA: 3:47:37 - DEC: 24:00:55 
2021-10-12T19:01:42: [INFO] Slew is complete. Tracking... 
2021-10-12T19:01:25: [ERROR] Error reading from device Timeout error (-4) 
2021-10-12T19:01:17: [ERROR] Error reading from device Timeout error (-4) 
2021-10-12T19:00:56: [INFO] Slewing to RA: 20:37:58 - DEC: -19:20:31 
2021-10-12T19:00:48: [ERROR] Error reading from device Timeout error (-4) 
2021-10-12T19:00:36: [ERROR] Error reading from device Timeout error (-4) 
2021-10-12T19:00:30: [INFO] Debug is disabled. 
2021-10-12T19:00:30: [INFO] Debug is enabled. 
2021-10-12T19:00:28: [INFO] Debug is disabled. 
2021-10-12T19:00:28: [INFO] Debug is enabled. 
2021-10-12T19:00:27: [INFO] Debug is disabled. 
2021-10-12T19:00:27: [INFO] Debug is enabled. 
2021-10-12T19:00:16: [INFO] Parking/Unparking aborted. 
2021-10-12T19:00:04: [INFO] Parking is in progress... 
2021-10-12T18:59:59: [INFO] Mount is unparked. 
2021-10-12T18:59:59: [INFO] Mount is unparked. 
2021-10-12T18:59:54: [WARNING] You must initialize the mount before parking. 
2021-10-12T18:59:50: [INFO] Telescope already unparked. 
2021-10-12T18:59:46: [WARNING] You must initialize the mount before parking. 
2021-10-12T18:59:31: [INFO] Time updated. 
2021-10-12T18:59:17: [INFO] Device configuration applied. 
2021-10-12T18:59:17: [INFO] Pulse guiding is enabled. 
2021-10-12T18:59:17: [INFO] Observer location updated: Latitude 50:02:21.4 (50.04) Longitude 19:55:36.3 (19.93) 
2021-10-12T18:59:17: [INFO] Site location updated to Lat 50:02:21 - Long 19:55:36 
2021-10-12T18:59:17: [INFO] Dome Policy set to: Dome ignored. Mount can park or unpark regardless of dome parking state. 
2021-10-12T18:59:17: [INFO] Loading device configuration... 
2021-10-12T18:59:17: [INFO] Please initialize the mount before issuing any command. 
2021-10-12T18:59:17: [INFO] AstroPhysics is online. 
 

Read More...

Hi All,

I have a strange problem with my mount (AstroPhysics) under INDI. When I try to point at the target which is 2 or 3hours before transit, the mount tries to place the telescope on the east side of the mount (not the west, I'm on the northern hemisphere), which typically causes a collision with the tripod. It is not a matter of time or location settings (I gave a GPS dongle and it works ok). It occurs on AP legacy and AP GTOCP2 drivers, and with Kstar and Cartes du Ciel (SkyCharts). So it looks like a problem with the driver or its settings. When I switch to Windows the slewing works ok, so it is not the problem of the hardware or the mount position stored in encoders neither. Interestingly, Ekos knows that it is on the wrong side because in the mount tab it says that the next flip will be after 14-15 hours. When the target is far from transit (eg. 5 hours) the mount slews ok. Do you have any idea what am I doing wrong, or what should I change with settings?
My setup is based on raspberry pi with astroberry.

Read More...