My setup at the moment: Kstars-EKOS on my Linux virtual machine inside the house. Raspberry-Pi2 on wifi at the mount (AZ-EQ6) outside.

I'm able to connect all the devices correctly, they all work. However I may have a problem somewhere still. I tried a field-test just now and positioned the mount very roughly at Polaris (there were clouds at the time). I connected everything inside, all green, and told the mount to set the current position as its Park position. I didn't do any sync or solve (clouds), but I figured that wouldn't be necessary if my time-setting is correct (which I think it is, UTC+2 for the Netherlands) as well as my GPS coordinates. It was just a test so I didn't require any accuracy, just very roughly.

I connected the mount to Kstars and got a nice pointer at Polaris. Then I told the mount to slew to M31. It seemed to go to roughly the right position (I think), it stopped, but then did a so called "Iterative GoTo" and that went totally wrong, it just went waaaaaay off and I had to abort the slew using the software. I didn't properly confirm (I had to rush outside) but I thing Kstars also showed the pointer to go waaaay off, so the software knew about it. Where could this problem lie?

On other thing; telling the mount to then go back to its park position (remember I told the mount to save that at the beginning) and also that failed. It slewed back on RA, but DEC stayed put. Now, the motherboard of the mount was replaced just recently because an encoder connection on the old board was loose... maybe that has been installed wrong? I have no idea as I don't know what could cause this, any help is greatly appreciated!

Not sure, please enable "Debug" logging and post a link to the complete logging file. You need to enable debug logging before you do any slews. Follow instructions here for more details.

Woops, so sorry I didn't read that post first. Will do next time and come back here, thanks!

1 little question though; what does the Iterative GoTo really mean? If that is something that's been done after platesolving, then that might be what's going wrong. I didn't do any platesolving..

It has nothing to do with plate solving or Ekos, if after initial slew the target coordinates are not what is requested, it issues another GOTO to go there, that's all. Without the log file, I can't say much. I'm using EQMod as I write this and have no issues at all with slew/track from KStars.

Ok, just to double check. It might strengthen the feeling I have that my encoder is failing if it actually uses that to check the location. Anyway, the log should show something like that I guess so will come back with it.

Ok, I just tried using my setup again against a clear sky, only to discover my DSLR and INDI is causing problems now as well. My guider produced fine images.

Anyway, first things first, the iterative goto failure. I watched EKOS very carefully this time and what happens is that the crosshair goes to the target, stops, then jumps back to the NCP position and corrects for that offset (which ofcourse doesn't make sense). The debug log file wasn't in the tmp directory, even though it stated it was (maybe it was on the PI itself, will check next time), so I paste here the output of the EKOS console window:

2015-09-27T19:56:35: Telescope Aborted.
2015-09-27T19:56:34: StopDE() : calling DE StopWaitMotor
2015-09-27T19:56:34: StopRA() : calling RA StopWaitMotor
2015-09-27T19:56:34: IsDERunning() = true
2015-09-27T19:56:34: IsRARunning() = false
2015-09-27T19:56:32: IsDERunning() = true
2015-09-27T19:56:32: IsRARunning() = false
2015-09-27T19:56:31: IsDERunning() = true
2015-09-27T19:56:31: IsRARunning() = false
2015-09-27T19:56:30: IsDERunning() = true
2015-09-27T19:56:30: IsRARunning() = false
2015-09-27T19:56:29: SlewTo() : deltaRA = 1116 deltaDE = -582388
2015-09-27T19:56:29: Iterative goto (1): slew mount to RA increment = 1116, DE increment = -582388
2015-09-27T19:56:29: Iterative Goto (1): RA diff = 10.41 arcsecs DE diff = 81898.20 arcsecs
2015-09-27T19:56:29: IsDERunning() = false
2015-09-27T19:56:29: IsRARunning() = false
2015-09-27T19:56:28: IsRARunning() = true
2015-09-27T19:56:27: IsRARunning() = true
2015-09-27T19:56:26: IsRARunning() = true
2015-09-27T19:56:25: IsRARunning() = true
2015-09-27T19:56:24: IsRARunning() = true
2015-09-27T19:56:23: IsRARunning() = true
2015-09-27T19:56:22: IsRARunning() = true
2015-09-27T19:56:21: IsRARunning() = true
2015-09-27T19:56:20: IsRARunning() = true
2015-09-27T19:56:19: IsRARunning() = true
2015-09-27T19:56:18: Slewing to RA: 0:04:29 - DEC: 67:15:02
2015-09-27T19:56:18: SlewTo() : deltaRA = 882400 deltaDE = -582099
2015-09-27T19:56:18: Slewing mount: RA increment = 882400, DE increment = -582099
2015-09-27T19:56:18: StopDE() : calling DE StopWaitMotor
2015-09-27T19:56:18: StopRA() : calling RA StopWaitMotor
2015-09-27T19:56:18: Starting Goto RA=0.0746821 DE=67.2505 (current RA=2.37243 DE=89.9887)
2015-09-27T19:55:16: Session log file /tmp/indi_eqmod_telescope_2015-09-27T19:49:22.log
2015-09-27T19:55:14: Toggle Logging Level -- Driver Debug
2015-09-27T19:55:14: Toggle Logging Level -- Driver Debug
2015-09-27T19:55:13: Toggle Debug Level -- Driver Debug
2015-09-27T19:55:13: Toggle Debug Level -- Driver Debug
2015-09-27T19:55:10: Debug is enabled.
2015-09-27T19:54:59: Start Tracking (TRACK_SIDEREAL).
2015-09-27T19:50:01: updateLocation: long = 5.11667 lat = 52.1
2015-09-27T19:50:01: Setting UTC Time to 2015-09-27T19:49:27, Offset 2

Please be more specific.

There is the problem, DE Diff is too large. What mount are you using?

I first wanted to solve the GOTO problem, if my DSLR problem stays I'll open another topic, it was working last time.

Yes, the Dec value remains way too large, which is why I was suspecting my encoder to go haywire maybe. It seems to start out with a good value. My mount is the Skywatcher AZ-EQ6.

Thanks

I guess try it to see under EQMod windows to see if you get the same behavior. Try to go the same coordinates as well.

Ok, so that took a while to test (busy at work). I decided to take the entire setup (computer) out of the equation and use a handcontroller. Low and behold, same problem! Unfortunately I think I once again have a faulty mount.

On a positive note, I did get to know your software pretty well.