×

INDI Library v2.0.6 is Released (02 Feb 2024)

Bi-monthly release with minor bug fixes and improvements

[SOLVED] Some problems with my RoboFocus

  • Posts: 38
  • Thank you received: 2
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.
8 years 1 month ago #6885

Please Log in or Create an account to join the conversation.

  • Posts: 41
  • Thank you received: 6
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.
7 years 8 months ago #9181

Please Log in or Create an account to join the conversation.

Can you control Robofocus from INDI control panel or does it produce TTY errors? i.e. test all the robofocus functions.
7 years 8 months ago #9185

Please Log in or Create an account to join the conversation.

  • Posts: 41
  • Thank you received: 6
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.
7 years 8 months ago #9188

Please Log in or Create an account to join the conversation.

I updated code to contain more debug statements. So turn debug logging on and let's see what it tells us.
7 years 8 months ago #9194

Please Log in or Create an account to join the conversation.

  • Posts: 41
  • Thank you received: 6

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.
7 years 8 months ago #9218

Please Log in or Create an account to join the conversation.

yes, like here . After you test, attach the log file.
7 years 8 months ago #9224

Please Log in or Create an account to join the conversation.

  • Posts: 38
  • Thank you received: 2
Hello,

I always had this problem.

I update Indi/Ekos/Kstars by the PPA.

See some logs, from the robofocus tab, I remove some line in double ... if it can help ...
2016-07-10T14:37:04: ReadUntilComplete with timeout 15 
2016-07-10T14:37:03: Bogus position: FD005444 
2016-07-10T14:37:03: TTY error detected: Timeout error 
2016-07-10T14:36:48: ReadUntilComplete with timeout 15 
2016-07-10T14:36:47: Bogus position: FD005444 
2016-07-10T14:36:47: TTY error detected: Timeout error 
2016-07-10T14:36:32: ReadUntilComplete with timeout 15 
2016-07-10T14:36:31: Bogus position: FD005444 
2016-07-10T14:36:31: TTY error detected: Timeout error 
2016-07-10T14:36:16: ReadUntilComplete with timeout 15 
2016-07-10T14:36:15: Bogus position: FD005444 
2016-07-10T14:36:15: TTY error detected: Timeout error 
2016-07-10T14:36:00: ReadUntilComplete with timeout 15 
2016-07-10T14:35:59: Bogus position: FD005444 
2016-07-10T14:35:59: TTY error detected: Timeout error 
2016-07-10T14:35:44: ReadUntilComplete with timeout 15 
2016-07-10T14:35:43: Bogus position: FD005444 
2016-07-10T14:35:43: TTY error detected: Timeout error 
2016-07-10T14:35:28: ReadUntilComplete with timeout 15 
2016-07-10T14:35:27: Bogus position: FD005444 
2016-07-10T14:35:27: TTY error detected: Timeout error 
2016-07-10T14:35:12: ReadUntilComplete with timeout 15 
2016-07-10T14:35:11: Bogus position: FD005444 
2016-07-10T14:35:11: TTY error detected: Timeout error 
2016-07-10T14:34:56: ReadUntilComplete with timeout 15 
2016-07-10T14:34:55: Bogus position: FD005444 
2016-07-10T14:34:55: TTY error detected: Timeout error 
2016-07-10T14:34:40: ReadUntilComplete with timeout 15 
2016-07-10T14:34:39: Bogus position: FD005444 
2016-07-10T14:34:39: TTY error detected: Timeout error 
2016-07-10T14:34:24: ReadUntilComplete with timeout 15 
2016-07-10T14:34:23: Bogus position: FD005444 
2016-07-10T14:34:23: TTY error detected: Timeout error 
2016-07-10T14:34:08: ReadUntilComplete with timeout 15 
2016-07-10T14:34:07: Bogus position: FD005444 
2016-07-10T14:34:07: TTY error detected: Timeout error 
2016-07-10T14:33:52: ReadUntilComplete with timeout 15 
2016-07-10T14:33:52: Focuser is moving to position 5441 
2016-07-10T14:33:52: RES (0X46 0X44 0X30 0X30 0X35 0X34 0X34 0X31 0XFFFFFFB8) 
2016-07-10T14:33:52: Moving... with buf[0]=(I) 
2016-07-10T14:33:52: CMD (0X46 0X47 0X30 0X30 0X35 0X34 0X34 0X31 0XFFFFFFBB) 
...
2016-07-10T14:33:49: RES (0X46 0X44 0X30 0X30 0X35 0X34 0X34 0X34 0XFFFFFFBB) 
2016-07-10T14:33:49: CMD (0X46 0X47 0X30 0X30 0X30 0X30 0X30 0X30 0XFFFFFFAD) 
2016-07-10T14:33:48: ReadUntilComplete is complete. Bytes read: -1075482776 
2016-07-10T14:33:48: buf[0]=0X46 
2016-07-10T14:33:48: ReadUntilComplete with timeout 15 
2016-07-10T14:33:48: Focuser is moving to position 5444 
2016-07-10T14:33:48: Checksum: Wrong (IIIIIIIII,9), 48 != 49 
2016-07-10T14:33:48: RES (0X49 0X49 0X49 0X49 0X49 0X49 0X49 0X49 0X49) 
2016-07-10T14:33:48: Moving... with buf[0]=(I) 
2016-07-10T14:33:47: CMD (0X46 0X47 0X30 0X30 0X35 0X34 0X34 0X34 0XFFFFFFBE) 
...
2016-07-10T14:33:45: RES (0X46 0X44 0X30 0X30 0X35 0X34 0X35 0X33 0XFFFFFFBB) 
2016-07-10T14:33:44: CMD (0X46 0X47 0X30 0X30 0X30 0X30 0X30 0X30 0XFFFFFFAD) 
2016-07-10T14:33:43: ReadUntilComplete is complete. Bytes read: -1075482776 
2016-07-10T14:33:43: buf[0]=0X46 
2016-07-10T14:33:43: buf[0]=0X4F 
2016-07-10T14:33:43: buf[0]=0X4F 
2016-07-10T14:33:43: buf[0]=0X4F 
2016-07-10T14:33:43: ReadUntilComplete with timeout 15 
2016-07-10T14:33:43: Focuser is moving to position 5453 
2016-07-10T14:33:43: Checksum: Wrong (OOOOOOOOO,9), 78 != 4f 
2016-07-10T14:33:43: RES (0X4F 0X4F 0X4F 0X4F 0X4F 0X4F 0X4F 0X4F 0X4F) 
2016-07-10T14:33:43: Moving... with buf[0]=(O) 
2016-07-10T14:33:43: CMD (0X46 0X47 0X30 0X30 0X35 0X34 0X35 0X33 0XFFFFFFBE) 
...
2016-07-10T14:33:40: RES (0X46 0X44 0X30 0X30 0X35 0X34 0X34 0X31 0XFFFFFFB8) 
2016-07-10T14:33:40: CMD (0X46 0X47 0X30 0X30 0X30 0X30 0X30 0X30 0XFFFFFFAD) 
2016-07-10T14:33:39: ReadUntilComplete is complete. Bytes read: -1075482776 
2016-07-10T14:33:39: buf[0]=0X46 
2016-07-10T14:33:39: buf[0]=0X49 
...
2016-07-10T14:33:39: buf[0]=0X49 
2016-07-10T14:33:39: ReadUntilComplete with timeout 15 
2016-07-10T14:33:39: Focuser is moving to position 5441 
2016-07-10T14:33:39: Checksum: Wrong (IIIIIIIII,9), 48 != 49 
2016-07-10T14:33:39: RES (0X49 0X49 0X49 0X49 0X49 0X49 0X49 0X49 0X49) 
2016-07-10T14:33:39: Moving... with buf[0]=(I) 
2016-07-10T14:33:39: CMD (0X46 0X47 0X30 0X30 0X35 0X34 0X34 0X31 0XFFFFFFBB) 
...
2016-07-10T14:33:36: RES (0X46 0X44 0X30 0X30 0X35 0X34 0X36 0X38 0XFFFFFFC1) 
2016-07-10T14:33:36: CMD (0X46 0X47 0X30 0X30 0X30 0X30 0X30 0X30 0XFFFFFFAD) 
2016-07-10T14:33:35: ReadUntilComplete is complete. Bytes read: -1075482776 
2016-07-10T14:33:35: buf[0]=0X46 
2016-07-10T14:33:35: buf[0]=0X4F 
...
2016-07-10T14:33:35: buf[0]=0X4F 
2016-07-10T14:33:35: ReadUntilComplete with timeout 15 
2016-07-10T14:33:35: Focuser is moving to position 5468 
2016-07-10T14:33:35: Checksum: Wrong (OOOOOOOOO0X4*30 0X30 0X35 0X3,32), 78 != 4f 
2016-07-10T14:33:35: RES (0X4F 0X4F 0X4F 0X4F 0X4F 0X4F 0X4F 0X4F 0X4F) 
2016-07-10T14:33:35: Moving... with buf[0]=(O) 
2016-07-10T14:33:34: CMD (0X46 0X47 0X30 0X30 0X35 0X34 0X36 0X38 0XFFFFFFC4) 
...
2016-07-10T14:33:31: RES (0X46 0X44 0X30 0X30 0X35 0X34 0X34 0X38 0XFFFFFFBF) 
2016-07-10T14:33:31: CMD (0X46 0X47 0X30 0X30 0X30 0X30 0X30 0X30 0XFFFFFFAD) 
2016-07-10T14:33:30: ReadUntilComplete is complete. Bytes read: -1075482776 
2016-07-10T14:33:30: buf[0]=0X46 
2016-07-10T14:33:30: buf[0]=0X4F 
...
2016-07-10T14:33:30: buf[0]=0X4F 
2016-07-10T14:33:30: ReadUntilComplete with timeout 15 
2016-07-10T14:33:30: Focuser is moving to position 5448 
2016-07-10T14:33:30: Checksum: Wrong (OOOOOOOOO,9), 78 != 4f 
2016-07-10T14:33:30: RES (0X4F 0X4F 0X4F 0X4F 0X4F 0X4F 0X4F 0X4F 0X4F) 
2016-07-10T14:33:30: Moving... with buf[0]=(O) 
2016-07-10T14:33:30: CMD (0X46 0X47 0X30 0X30 0X35 0X34 0X34 0X38 0XFFFFFFC2) 
2016-07-10T14:33:30: RES (0X46 0X44 0X30 0X30 0X35 0X34 0X32 0X38 0XFFFFFFBD) 
...
2016-07-10T14:33:11: RES (0X46 0X44 0X30 0X30 0X35 0X34 0X32 0X38 0XFFFFFFBD) 
2016-07-10T14:33:11: CMD (0X46 0X47 0X30 0X30 0X30 0X30 0X30 0X30 0XFFFFFFAD) 
2016-07-10T14:33:10: Session log file /tmp/indi_robo_focus_2016-07-10T14:31:13.log 
2016-07-10T14:33:10: Toggle Logging Level -- Driver Debug 
2016-07-10T14:33:10: RES (0X46 0X44 0X30 0X30 0X35 0X34 0X32 0X38 0XFFFFFFBD) 
2016-07-10T14:33:10: CMD (0X46 0X47 0X30 0X30 0X30 0X30 0X30 0X30 0XFFFFFFAD) 
2016-07-10T14:33:10: Toggle Debug Level -- Driver Debug 
2016-07-10T14:33:08: Debug is enabled. 
2016-07-10T14:32:24: Device configuration applied. 
2016-07-10T14:32:24: Backlash is now    0 
2016-07-10T14:32:24: Motor settings are now    1   1   1 
2016-07-10T14:32:24: Loading device configuration... 
2016-07-10T14:32:23: Robofocus is online. Getting focus parameters... 


if you need more informations, ask me

Gaetan
The following user(s) said Thank You: Jasem Mutlaq, Meister Wolf
7 years 8 months ago #9236

Please Log in or Create an account to join the conversation.

Thanks. I actually have a RoboFocus unit collecting dust somewhere, so I'll find it and test it myself today.
7 years 8 months ago #9241

Please Log in or Create an account to join the conversation.

  • Posts: 38
  • Thank you received: 2
Hello,

I want to know if you have the same problem with your Robofocus ?

Thank's again for all your work.
7 years 8 months ago #9279

Please Log in or Create an account to join the conversation.

Been extremely busy, but I promise I'll test it tonight.
7 years 8 months ago #9281

Please Log in or Create an account to join the conversation.

So I fixed a few minor problems in the driver and improved its speed but I still didn't have any of the timeout issues ever. I suggest you try again tomorrow, but it looks like this is a hardware issue:

1. Change USB Cable
2. Change USB port
3. Check the RoboFocus unit has enough power. If powered from battery, try using a 12 DC power supply.
4. Check that the Cat5 cable is connected to the "PC" port in the unit and that all wires are connected fine. Check that the RS232 to USB adapter is connected to the DB9 of the Cat5 cable.
5. Check that the DB9 cables between unit and focuser are OK.
6. Check using another application.
The following user(s) said Thank You: gaetan
7 years 8 months ago #9286

Please Log in or Create an account to join the conversation.

Time to create page: 1.256 seconds