I have been unable to fix this issue. I have reset the mount to factory defaults. It has auto-meridian flip set as a default.
I rebuilt my Linux machine and installed the latest version of KStars 3.5.2 2021-03-01 and tested. Meridian flip worked, once, then would not work again. When it reaches the meridian + 0.1 it states "Meridian Flip Planned". No further captures take place and it just sits there and does nothing.
However I have found that if I uncheck the Meridian Flip if HA>0.1 before a run and then check it again then it will meridian flip during the run - hence the title of my topic.

I see from the changelog that there were a number of changes made around the meridian flip part. Is it possible that something has gone awry>



Thanks for all the replies everybody. It has given me a lot of food for thought. I do suspect the DST issue but will also try to issue a factory reset to the mount. I’m not sure if the HEQ5 Pro remembers much as I recall when operating it via the hand controller after it initialised you had to enter some more basic parameters. Years since I used the handset.


OK it is worth a shot :) thanks. Now where is that hand controller? wink.png 


No I don't use the hand controller. Not used it for years.


Just some more info for you all. I had it at 0.1 hours and it worked great for months. I still had it at 0.1 hours and it stopped working hence why I decreased it to 0.01 hours. I did that yesterday in my initial daylight test at which point it worked fine so kept it like that for the night run.



File Attachment:

File Name: 2021-04-03.zip
File Size: 6,465 KB

Over the last few days I have noticed that Meridian flip is not working. My setup is Raspberry PI4 running Astroberry version 2.0.3 which I run as a server at the telescope.The equipment at the telescope end is
  • Skywatcher HEQ5Pro so using EQMOD for that
  • 2 ZWO cameras one for capture the other for guiding
  • Lakeside focuser
  • ZWO filter wheel
  • PHD2 for guiding
I am remote controlling the PI with Ubuntu Mate which is running inside the house. KStars/EKOS runs fine with this setup and has worked flawlessly for months. I always ensure I keep everything up to date and have a spare PI that I use from time to time too.
I first noticed an issue with meridian flipping 29/03/2021 whilst tracking the sun and had to force a flip. Then when using the scope to image an Ha area in Cepheus I noticed again it did not flip. I have flip set to 0.01 hours after meridian. It seemed to sit there for ages doing nothing apart from stating "Waiting for flip". Again I forced it to flip and continued with its scheduled jobs.
Yesterday I tried flip during the daytime and it worked ok but this time I had mount and indi logs enabled. Last night I tried for my target again and found that it was stuck at the same point. I reinitiated the flip manually at around 03:45 at which point it captured 2 subs before the clouds finally set in and I had to abort it completely.
I attach the logs for your perusal. This log also contains the good test flips during the day as well as the "failed" one. 


Terry McKnight replied to the topic 'IOptron CEM70' in the forum. 6 months ago

So according to this post it isn’t supported. Oh well :(

27 Oct 2020 09:08
iGuider support for iOptron CEM70g

Category: Mounts

It's not yet supported. IOptron will send me one so I can try out soon.


Terry McKnight created a new topic ' IOptron CEM70' in the forum. 6 months ago

I’m looking at an addition to my existing rig and see the IOptron CEM70 with a larger capacity which will suit my needs. I believe the CEM60 works ok on Astroberry but anybody using the CEM70 on it? Same driver maybe?


My ZWO ASI120MM is actually the mini version with USB2 only. I've seen a few issues posted on various forums related to the ZWO ASI120MM-S . I wonder if you are seeing the same problems with your 120MC-S?


Hi Tom. No I've not noticed any issues with skipping frames with the 120MM. I have it set as 8 bit though. I had to do that in Windoze days too.


I updated my Astroberry from 2.02 to 2.03 upgrading Kstars at the same time and ran into the problem with my ASI cameras (and ASI EFW) not showing up when I launch KStars/EKOS from the PI4 or from the INDI WebManager
My hardware version is:
Hardware : BCM2835
Revision : c03111
Serial : 100000004632cd93
Model : Raspberry Pi 4 Model B Rev 1.1

lsusb would no longer show anything from the command line - zip
usb-devices was the same. However sudo lsusb or sudo usb-devices did work.

Anyway I did run sudo rpi-update e1050e94821a70b2e4c72b318d6c6c968552e9a2 and reboot. ASI devices now recognised again and everything shows up ok in lsusb

astroberry@astroberry:~ $ lsusb
Bus 002 Device 005: ID 03c3:183e
Bus 002 Device 004: ID 045b:0210 Hitachi, Ltd
Bus 002 Device 003: ID 045b:0210 Hitachi, Ltd
Bus 002 Device 002: ID 05e3:0616 Genesys Logic, Inc. hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 0403:6001 Future Technology Devices International, Ltd FT232 Serial (UART) IC
Bus 001 Device 010: ID 03c3:120c
Bus 001 Device 009: ID 03c3:1f01
Bus 001 Device 008: ID 04b4:6572 Cypress Semiconductor Corp.
Bus 001 Device 007: ID 0403:6001 Future Technology Devices International, Ltd FT232 Serial (UART) IC
Bus 001 Device 006: ID 045b:0209 Hitachi, Ltd
Bus 001 Device 005: ID 045b:0209 Hitachi, Ltd
Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

For reference I am running the following hardware

ZWO ASI 183MM, ASI120MM, ASI 5 position filter wheel (the latter 2 connected to the integral hub on the 183) and Lakeside focuser connected to a powered USB3 hub on the mount. This runs down an active USB3 cable to the PI4 straight into the USB3 socket.
The EQMOD cable runs direct from the HEQ5Pro to the PI4 USB2 socket. So two USB cables running to the PI and a relatively simple setup.

I am controlling the PI4 via 1G Ethernet connection so no wireless involved. I also have a bug with Windows KStars which I've already reported to Jasem.


I have found that the Lakeside Driver crashes if you specify an initial step size greater than 999

So essentially don't enter a large step in the Step box (shown as 0 in this picture) otherwise it crashes.

I am using KStars 3.4.0 on a Raspberry Pi4. The firmware version of the Lakeside controller is V1.3.0


I am using a Pi4 with all the latest updates to today 01/02/2020 and my ZWO ASI120MM works ok.
However my ZWO ASI183MC-PRO, although recognised, when I try to connect to it using oacapture or CCDciel crashes both applications.

I'm not sure where the crash logs are as /var/logs/messages does not contain any log of the crash. Happy to submit logs if you can tell me where they are.