Are you saying my mount model is reflected in KStars? When the mount slewed to Alnitak instead of M42 and plate solving said I was on target, I looked at KStars to see where it thought I was pointing and it indicated Alnitak. I selected M42 in KStars and told EQMod to slew to M42 and it wouldn't move there.

When it wouldn't move to M42, I went to the Flame Nebula in KStars and told EQMod to slew to it. The slew showed properly in KStars, staying on the east side, and plate solving showed I was very close to the target. It took about the usual amount of fine moves to get the mount centered on the target within the tolerance I had given.

I have attached the log from this particular session for additional information. I think the issue starts around line 439150, local time 21:21:30.

Uh, that sounds weird indeed.
Could it be that you had moved the KStars FOV (not the mount pointing) at some point after having slewed to M42, so that EKOS/the align module thought that was the target?
Also, if you look at the log, the messages from align only start around 21:34, so before there seems to not have been a try to actually do an alignment....
(Edit: and the coordinates refered to there are the ones of M42)

Look at line 146277 which shows the mount is on target for M42 at 19:27:54(+) local time. This was on the west side of the pier. I realigned at 19:52 (194825), 20:00 (276814) and 20:18 (311291). At 20:18, the accepted solution is about 2 minutes in declination from M42 (which isn't Alnitak either). I'm still confused....

2 arc minutes in declination away is very close after a meridian flip and if you mean 2 minutes of time then it's still only half a degree which is still not bad.

2 arc minutes puts the target outside my FOV.

It's more important to note that this was the plate-solved location that was meant to be M42. I guess I'll just chalk this up as an ongoing mystery.

Hey RDBeck!

I had the EXACT SAME SITUATION yesterday!

Since i had flip-problems all of the time i was awake yesterday at flip-time and decided to have a look, what happens.

So everything worked fine, mount flipped, went to the target from the other pierside and made a platesolve afterwards. And then it says "solver succesful" after 1 try , but stays WAY out of the desired location. Funny thing is that when working on "the other side" i can say go there or there, the mount moves but ALWAYS goes to the wrong point in the sky, saying solver succesful!
WTF
I can not understand this behaviour.
Cleared Mount model several times.

Conclusion ATM:

Platesolving works great when west pointing east.
Platesolving goes wild when east pointing west...

System not usable after the flip for me...

Ideas?

Niki

Hi Niki,
without logs it's not that easy. Could you please post the logs, I could take a look...

- Wolfgang

Sorry, i would like to but my logs are always way to large. The one of yesterday has 47mb...

ill try to host it somewhere...

Niki

OK, here you go.

Greetings, Niki

www.dropbox.com/sh/rgojajm3xaxatmb/AAAYH...oKmsE5Kkg_Bm8Da?dl=0

Hi Niki,
the meridian flip itself was running fine:
But after this, it looks like the scope moves. There is one warning in the log:
I'm not so familiar with EQ mounts. But if I get it right is, that you have a setting forcing the mount to stay on a certain pier side. This does not sound like a good idea for meridian flips.

- Wolfgang

Since my last post, I had two, IIRC, cases where the capture and slew of a target too close to the meridian would not point to the correct location. The location in KStars was where the scope was pointing, it just wasn't my target. I didn't post them at the time because I didn't have good notes to point someone else where to look for them in the logs (different nights and targets).

After I reset the mount and ensured it was working correctly (I don't recall what all I had wrong), automatic meridian flips have been working just fine. I'm using 1/2 hour past the meridian as my criterion.

Hi Wolfgang!

The first part of the Log you quoted says die erneute Ausrichtung blablabla wurde abgeschlossen. Thats right, the system "thinks" it is on the right point, but it is just NOT. Thats the funny thing.

The second thing you quoted, that i forced the mount to the other pier side was before that, when i tried to make the flip manually.
This would have worked besides that. The problem is happening after the flip.
The flip itself works flawless.

I´ll try it in German, maybe i have better words, i think you speak german Wolfgang?

Also folgendes problem passiert. Platesolve funktioniert eigentlich problemlos am Abend. Meine Objekte starten meist tief im Osten. Wen ich dann flippen muss, macht das system das problemlos.
Du musst dir das so vorstellen. Gestern hatte ich die Walgalaxie im Bild vor dem Flip. Fadenkreuz drauf, der "Rahmen" des Sensors nach dem Platesolve auch, alles normal.

Dann der Flip. Monti fährt das Objekt verkehrt an und ist relativ weit weg, ich hab das mal im Screenshot markiert wie weit in etwa das gestern war.

Also die Walgalaxie ist auf dem Screen da wo das Fadenkreuz ist. Der Rote Ring zeigt wo die Monti nach dem Flip hingefahren ist. Und da hat sie dann gemeint erneute Ausrichtung abgeschlossen.
Was ich dann natürlich gemacht hab, war mit der Maus auf die Walgalaxie zu klicken und dem System zu sagen "fahr da hin"
Und was macht das System? NICHTS! Es sagt sinngemäß. "Da bin ich doch schon"

Verstehst du wie ich das meine? Komplett unlogisch, ich kapiers nicht, vor allem warum VOR dem Flip alles hinhaut.

Die Zeit hab ich 3 mal gecheckt, die hat gepasst...

Werd jetzt mal alle Einstellungen der Montierung, bzw. des Platesolve löschen , mal sehen obs dann geht...
Aber jetzt ist erstmal schlechtwetter...

Grße
Niki