I could do it, but I not sure about compiling it? How about I extend a teamviewer invite to you??.... Bruce

I don't have (and use) teamviewer which seems to be a commercial product.
Maybe you could try to compile yourself:That should replace your current indi-eqmod version which should be in /usr (not in /usr/local). You may have to install dependencies (indi-devel, nova-devel..).
I may help further if you need.

Hi Jean-Luc,

I did compile the driver and made a quick test, it was a bit scary when my mount didn't stop when I expected but it seems that I maybe missed the xml-file when trying..?? I'll see if I get the time to give it a try later on..

Here you can take a look what happened.. pretty scary, but Abort worked, otherwise I would have forced to switch off the power.



My guess is that when the mount slows down first time it should change direction and also the next time it slows down.. but it's a bit hard to say because I only looked through webcam.
I'll have to go to my obsy tomorrow to get things right again, but no problem, I'm pretty sure it will work one day
Thank you so far!!
Br
/Markku

Thanks Maxer, it was a little bit risky to perform this test remotely, but we know that Abort is working in this situation.
Otherwise I've looked at the video and saw the problem arised in the 4th move: after checking the code I saw I have made a mistake (read a loop while for a loop until). So I inverted the stop condition here. I also changed some direction settings in the 2 next moves, but I'm quite confused about this (I believe the firmware sets the shortest path direction in some cases, well I hope). I put a new version here.
If you make further tests, can you activate driver debug and serial port debug and post the log file. The video is really useful.
Thanks again,
Jean-Luc.

A bit risky, but abort works so I'm fine with that.
So, here is results from second test..



And the log :
2016-02-17T11:18:03: Telescope Aborted.
2016-02-17T11:18:01: Autohome phase 5: Waiting for motors to stop
2016-02-17T11:17:59: Autohome phase 5: Waiting for motors to stop
2016-02-17T11:17:58: Autohome phase 5: Waiting for motors to stop
2016-02-17T11:17:57: Autohome phase 5: Waiting for motors to stop
2016-02-17T11:17:56: Autohome phase 5: Waiting for motors to stop
2016-02-17T11:17:55: Autohome phase 5: Waiting for motors to stop
2016-02-17T11:17:54: Autohome phase 5: Waiting for motors to stop
2016-02-17T11:17:53: Autohome phase 5: Waiting for motors to stop
2016-02-17T11:17:52: Autohome phase 5: Waiting for motors to stop
2016-02-17T11:17:51: Autohome phase 5: Waiting for motors to stop
2016-02-17T11:17:50: Autohome phase 5: Waiting for motors to stop
2016-02-17T11:17:49: Autohome phase 5: Waiting for motors to stop
2016-02-17T11:17:48: Autohome phase 5: Waiting for motors to stop
2016-02-17T11:17:47: Autohome phase 5: Waiting for motors to stop
2016-02-17T11:17:46: Autohome phase 5: Waiting for motors to stop
2016-02-17T11:17:45: Autohome phase 5: Moving back (10 deg.)
2016-02-17T11:17:45: Autohome phase 4: end
2016-02-17T11:17:43: Autohome phase 4: detected DE Home index: 24583, stopping motor
2016-02-17T11:17:43: Autohome phase 4: detected RA Home index: 24583, stopping motor
2016-02-17T11:17:41: Autohome phase 4: find the home position index
2016-02-17T11:17:41: Autohome phase 3: end
2016-02-17T11:17:40: Autohome phase 2: end
2016-02-17T11:17:39: Autohome phase 2: Waiting for motors to stop
2016-02-17T11:17:38: Autohome phase 2: Waiting for motors to stop
2016-02-17T11:17:37: Autohome phase 2: Waiting for motors to stop
2016-02-17T11:17:36: Autohome phase 2: start
2016-02-17T11:17:36: Autohome phase 1: end
2016-02-17T11:17:35: Autohome phase 1: Waiting for motors to stop
2016-02-17T11:17:34: Autohome phase 1: Waiting for motors to stop
2016-02-17T11:17:33: Autohome phase 1: Waiting for motors to stop
2016-02-17T11:17:31: Autohome phase 1: Waiting for motors to stop
2016-02-17T11:17:31: Starting Autohome.
2016-02-17T11:17:30: *** AutoHome NOT TESTED. Press PERFORM AGAIN TO CONFIRM. ***

Behaviour didn’t have changed a lot for some reason, it still wants to do a full circle and I can't just do that because the floor in in the way
I tried to start from 2 different positions, first from East of pier and then West of pier but the result was the same..??

Br.
/Markku

While clouds are rolling in I did some digging and came up with this, so I post it even if I think you already know all this..

If result from command ":q1000000" or ":q2000000" is anything else than 000000 or FFFFFF then the result shows encoder position of home-position.

After slewing slewing from West to East :
Result for :q1000000 WayToGoForAutohome 000000 SlewUpRA=True or FFFFFF SlewUpRA=False : =6F617F
Result for :q2000000 WayToGoForAutohome 000000 SlewUpDEC=True or FFFFFF SlewUpDEC=False : =4D1AAA
************************************
After slewing from East to West :
Result for :q1000000 WayToGoForAutohome 000000 SlewUpRA=True or FFFFFF SlewUpRA=False : =076980
Result for :q2000000 WayToGoForAutohome 000000 SlewUpDEC=True or FFFFFF SlewUpDEC=False : =B91DB9
*************************************
After slewing slewing from West to East again just RA :
Result for :q1000000 WayToGoForAutohome 000000 SlewUpRA=True or FFFFFF SlewUpRA=False : =FB177A
Result for :q2000000 WayToGoForAutohome 000000 SlewUpDEC=True or FFFFFF SlewUpDEC=False : =FFFFFF => Not moved..

Found another error in the driver code, I was using :q1010000/:q2010000 command in place of :q1000000/:q2000000.
By the way, in the code you sent from skywatcher (and that I try to mimic) they always use forward goto commands (:G100 or :G200) independently of the direction. When slewing they set the direction accordingly (:G131 or :G130). That's why I thought the firmware may change direction itself in goto mode. Unfortunately that's not what your test is showing up, so I reverted the direction in this negative goto phase. Well, I've just looked at the log which was sent a year ago, there are goto commands with backwards direction, so maybe this is just a mistake in the skywatcher code.
I will look deeply into the firmware anyway, one day.

Yess!!! It's working now.. great job!!



Yes, always forward, even with the HC,
Forgot to take the log but I got too exited when it worked
I do some more testing when stars comes out, for the moment I can't verify that it's pointing exactly same position as with the HC.
Thank you for a great job!
Br.
/Markku

That's nice, should be a lucky day. I will wait for you to make other tests before committing as there are different cases in the procedure. And also wait for the accuracy of the positioning.
Thanks for the feedback.
Jean-Luc.

Am I correct in understanding this. With the eq8, from a completely unknown position, this routine will correctly find the home postion ? the video shows it in action, but that is starting from a correct park position already. Will this do the same, if starting at an arbitrary and unknown position ?

I did some more testing later on and so far it does a better job than the HC to find homeposition, with HC in some cases it tries to do a full 360deg cycle to find home but with this routine I haven't got that problem yet, but I'm still waiting for some stars to measure the accuracy..