Hello,

I have make this test, and the ratio become YELLOW when the focuser start to move, and become GREEN when is at position.

But, maybe it's not the same problem, but if I make a double click on Focus In (or Out), the ratio become YELLOW, but never GREEN ... Have you the same thing ?

Hy,

I just want to know, if someone can try to make a double-Click on the focus-in ou out bouton

It's like my focuser don't understand the second command of focus, if it don't send the position at the end of the first.

Driver updated and works well within INDI/Ekos, check it out in tomorrow's update.

Hello,

Thank's for the update.

But I am sorry, I always have problems when I make an autofocus.

After some movement, the focuser freeze, the ratio is Yellow ... and after a few time I got the next message

Sorry, not really a good news.

But the bug with the double-click on 'in' and 'out' bouton is fixe.

Do you get these timeouts also when doing manual motion? Sometimes it could be as simple as changing the USB port or the USB cable.

Hello,

At the moment, I don't have a lot of time to solve my problem. But I have made some test ... with no good result.

Those timeout are in Auto mode ... In manual mode, It's juste the yellow ratio symptom that I replicated by double click (but that was before you fix it)

My configuration is the next,

PC - USB HUB - USB/Serial - ROBOFOCUS

- I change the RS232 Cable, I made a short one ... but no amelioration
- I remove the UBS/Serial cable, and the USB HUB, by pluging directly the Serial cable of the robofocus on my PC ... allways TTY error

I wonder if my Robofocus is sick ? In parallele I try to build this one
sourceforge.net/projects/arduinofocuscontrollerpro/

But I want to know if my robofocus is dying or not.

Thank's for the time you spend on my problem.

I had something similar last night. It was the first time I used Ekos under the sky.
Configuration is latest xubuntu with kde plasma installed, kstars + ekos
Scope is VMC200l, AZEQ6GT, ST8xme and robofocus.

When I click in the focus tab on "start focus", it gives the following log:
2016-07-07T01:15:55 Focusing outward...
2016-07-07T01:15:55 FITS received. HFR 3.49 @ 7070. Delta (53.5%)
2016-07-07T01:15:51 Capturing image...
2016-07-07T01:15:43 Capturing image...

Basically, he tries to move the focus outwards, but stalls. The start focus button stays greyed out and I can only click "stop" after 10 minutes with no life.
in focus log in the control panel I have all the debug on:

2016-07-06T23:28:47: TTY error detected: Timeout error
2016-07-06T23:28:32: Focuser is moving to position 7005
2016-07-06T23:28:32: TTY error detected: Timeout error
2016-07-06T23:28:17: Focuser is moving to position 7005
2016-07-06T23:28:17: Focuser is moving to position 7005
(he doesn't move to 7005)

But when I select here in control panel focus in or focus out button, he doesn't do anything.

However, I can set the new focuser position by typing in the ticks and then click "set" (under the focus tab). Then the focusser moves and i can focus from the pc. In the focus tab, the focus in or focus out doesn't work either.

I have the robofocus directly on the COM port of the laptop. Before, I didn't have trouble with focusmax on windows.

I had 1 success with the "start focus" working. He did a few pictures, but then I got a bunch of errors, the mount and camera crashed. Disconnecting/connecting didn't work, starting/stopping indi too. The only thing that could bring back life to my astro-setup was a hard reboot of the laptop.

Does anyone has tips?

Btw, is it possible to select a big subframe in which the program can search for a suitable star? The st8 has lots of bad pixels at the edge and he tries to focus on the pixel.

Can you control Robofocus from INDI control panel or does it produce TTY errors? i.e. test all the robofocus functions.

It produced tty errors sometimes, certainly when clicking "focus in" or "focus out". This in indi and ekos.
2016-07-06T23:28:47: TTY error detected: Timeout error

But even with the debug on I couldn't detect the real source of the errors.
The only function I could use was the "Set". This in Ekos (focus->focuserfield)"Ticks: xxx", then click "Set". And in Indi (control panel-> focuser -> options absolute position -> xxxx, click "Set"). Then the focuser moved.

Using the focuser simulator now. In ekos the "focus in" and "focus out" does show movement. The absolute position moves. In indi it doesn't move and no new entry in the log. Maybe a software issue with communication between components.

I updated code to contain more debug statements. So turn debug logging on and let's see what it tells us.

Is it enough to have done the "apt-get update; apt-get install kstars-bleeding indi-full;"? He updated some components.
I have selected everything in "control panel->robofocus->options->debug levels".
Still the same problem with timeouts.

yes, like here . After you test, attach the log file.