Hi Pete!

Based on your comments it looks like you know this but if it helps in any way, here is the language from the INDI driver page for iOptron mounts. I've generally set the EKOS MF at 2 degrees past and the mount's MF at 5 degrees - that difference more than covers the longest exposure I might expect to take.

FROM THE INDI DRIVER PAGE:
You have to let the mount track some time AFTER CROSSING MERIDIAN, otherwise MF is not going to happen. In iOptron driver, the Meridian Behaviour setting Flip or Stop does not matter here, since Meridian Flip will be triggered by the client (e.g. Ekos); but the Limit you set does matter. Basic rule is:

0 < Client Limit < Mount Limit

Example: set Client (e.g. Ekos) to trigger MF 3° after crossing the meridian, and set mount limit to 6° after crossing meridian. You must set the 6° in the iOptron INDI driver.
Ekos limit should be greater than 0, because Ekos and mount must exactly agree on which side on the meridian we are: allowing to track some degree after crossing it, relaxes the precision needed and accounts for small difference in models and approximations between Ekos and mount firmware.
Mount limit should be greater then Ekos limit, because some time is usually needed to complete the running capture when filp time occurs (should be: MOUNT LIMIT - EKOS LIMIT > LONGEST EXPOSURE PLANNED). And MOUNT LIMIT should be small enough to avoid the mount smashing your equipment on a tripod leg.

Pete, there is something strange in your log. The last slew went to 12h 36m 57s, but the meridian flip starts from the position 12h 17m 54s. Do you have an explanation why the mount position has changed?
- Wolfgang

This was while I was doing some testing inside. What might have happened was that I picked an object to track on and saw how long it would be until the MF happened. I didn't want to wait that long so I picked an object that would cause the MF to occur sooner. (I'm very impatient ).

--
iOptron GEM28, Redcat 51, Nikon D7500, WO Uniguide 32/120MM, ZWO ASI120MM Mini

I have had good success with the iOptron CEm25P and iOptron CEM120EC2. The only problem I still have with the CEM120 is that when I send the mount to the home position it stops sending “pier side” data so my dome gets confused and rotates to 090.

I’m not sure if this is a CEM120 problem or a Nexdome driver problem.

is that link updated? what about the hem27/armonic mount? is it compatible?

Fredrick, What parking problems did you have? I have an iOptron HEM27EC and occasionally when it gets the Park command from ekos, it will start rotatating East past the zero point. I don't know how far it would have gone since I was able to get to the power switch. I still haven't been able to find out what specific conditions cause that problem.

My iOptron CEM120 EC2 works well, but there is one ongoing issue that I can work around.
Each time that INDI is started the mount does not indicate if the mount pier-side is EASt or WEST. It just gives no info.
This means when I first start up, if I turn on dome slewing, the Nexdome rotates to 90 degrees.

Once I slew the scope to any position, the pier-side is given and the dome slews properly.

It just means my startup procedure requires that I slew the scope somewhere, anywhere, in order to generate a valid pier-side value.

Keith,

I have two iOptron mounts. One is the CEM120 EC2 and I don't use the hand controller at all (it's in a box somewhere) and I have not had problems in a while with getting the mount to properly respond when telling it to go to the Park position. I have set my Park position and Home position to the same position and that is what iOptron calls the Zero position.

I also have a CEM26-EC. For this mount I have to use the leave the hand controller connected since that's the only place I can connect the USB cable that allows EKOS/Indi to control the mount. In this case I've found that I need to set the Park position via the hand controller. I have tried setting the Park position solely from the Indi Control Panel but that hasn't worked for me. In the Indi Control Panel for the mount I've tried the usual things (Set Park as the Current Position for example). Then when I slew the mount away from Park and tell it to go back to Park it goes somewhere entirely different. If I set Park via the hand controller and then use Ekos/Indi to go to the Park position, it seems to work as expected.

I'm just guessing but when you've got two brains trying to control things (the hand controller and Ekos/Indi) there is more chance for conflicts. I hope iOptron will eventually migrate away from the requirement to have a hand controller connected (for some of their mounts) for those who would rather not use one.

With the HEM27EC mount, I think the handset is required since that is where the WiFi and processor are located. I would also like to get away from having a handset dangling off the mount, but I can also see why they would want to go that route since all of the brains are easier to replace.
.
One thing I would like to see them do is release an "AP" firmware version that is stripped down to just what we need. No databases, or goto-ing, ect. That would also open up room for other functions like hard RA/DEC limits for folks using a tripod with long scopes.
.
I'm starting to suspect that my problem was that one of the other parking positions other than 0/0 got loaded into the handset. I looked thru the iOptronV3 INDI driver and all it sends is a "park" command to the mount, so the handset then interprets where Park is. There are some functions in the INDI driver to send park positions, but I don't believe that I've ever used them.
.