seletek does not work with autofocus #712
Comments
|
Same issue here. If I move the focuser via Indi Control Panel, it reports Ok when position is reached (log window). I started 2 instances of indi_armadillo_focus (two different users at os level on different ports, separated .indi folder). One instance control the focuser of first telescope via "Main" port, the second instance control the focuser of the second telescope via "Exp" port. I connect to each instance over network from two RPI controlling devices on each telescope. The behaviour described occurs with both instances, and this behaviour is the same even if I use/start only one (Main port) instance, or if I connect from local computer (where de server driver is running). I updated the "Armadillo 2" firmware, nothing changes. Mastria. |
|
Enable logging and then attach log. Does the LED light for the position property become "Green" or remains at "Yellow"? |
I can't replicate this right now (weather conditions). Maybe only the next weekend. It's a valid test if I use a "simulator CCD" with "real armadillo focuser"? I think this doesn't make sense (as a valid test). |
|
I regret not having written before, I am moving from home and I have the telescope dismantled. |
|
indi_armadillo_focus_22:45:32.log This log have several moves because I commanded each move "manually", take a snapshot, and moved again and again. I think (not sure) that this first block was auto-focus that failed, no clues:
The other moves was commanded by me:
When the weather permits, I'll try a better log. But yes, the green light works OK, and message that focuser reached position works too. Maybe an important information: Few months ago, the auto-focus worked perfectly "only" one time. today: When worked: I use the Main port of Armadillo for main focuser on the east telescope and the Exp port of the same Armadillo for main focuser on the west telescope (second telescope). This way of use is not related with the problem. Today configuration on "Other Raspberry Pi" - where Armadillo is connected on USB port:
Today configuration on "first" RaspberryPi that I connect from Ekos on MacOs:
Mastria. |
|
Seems INDI driver is working fine, and the problem is with Ekos. Turn on verbose logging in Ekos , make sure "Focus" is selected and then attach log. We should probably move this to bugs.kde.org |
|
Hi.
Are you saying that you connected the Armadillo directly to the computer and it worked? I always connect the cable to a USB hub together with other devices, ccd, etc ... and connect it to the computer. I can ask a friend of mine to try the direct connection. Greetings. |
|
Quilex, there's 2 scenarios here: 1 - Armadillo connected to computer where Ekos is running (with or without usb-hub) Your scenario is the 1st. My scenario "today" is 2nd. What I said is that auto-focus worked one time only, and, by coincidence or not, it was connected on the USB port of computer that was running Ekos (scenario 1). When the weather permits and I'll try several scenarios to se if I can identify at least one situation that auto-focus works. If I can do that, with logs running in all scenarios, I can post here something that really helps knro to identify the problem. Mastria |
|
Ok, ty Mastria. |
|
Today I could take some tests. Attached some logs and pictures. I indetified what happening, but not why. There's 4 tests in log file: The problem occur only when Ekos send "move" command to indi. The driver moves and in driver log there's information about "reached position", but not in Ekos log on screen. In this situation, the "Absolute Position" ligth stays YELLOW. (see below).
The "trick" I used was, after each focuser move, I manually sent 1 tick move. After this, the YELLOW ligth change to GREEN and Ekos continues the autofocus procedure. Doing this after each Ekos move command to focuser and finally I got the focus. (see below)...
So the problem is, when Ekos send a "move" command, the light stays YELLOW, when I send a "move" command from Control Panel, the ligth changes to GREEN. I hope these logs and report help to solve the problem. Thanks, |
|
Thanks, I just checked the code and fixed an issue where it doesn't update the client that its status is OK. Please either compile the driver from GIT, or wait until the nightly PPA update later tonight and try there. |
|
I could test tonight, it worked perfectly (I tested only "main" focuser, but I believe that the "exp" will work too). You can close this issue. Thanks again! |
|
Tnx Mmastria and Knro for help. I can try next week. |
Hi.
Sorry mi bad English.
Web traslator.
When trying to perform autofocus, with ekos, the camera makes the first capture, seletek moves the focuser and the process remains stopped.
It is as if the camera is waiting for Seletek to notify him that he has finished moving the focus.
It does not produce any error that I see.
Tested on 2 computers; (Mint 19)
Thanks in advance.
Al intentar realizar autofoco, con ekos, la camara realiza la primera captura, seletek mueve el enfocador y el proceso se queda parado.
Es como si la camara se quedara esperando a que seletek le avise que termino de mover el foco.
No produce ningun error que yo vea.
Probado en 2 ordenadores; (Mint 19)
Gracias anticipadas.
The text was updated successfully, but these errors were encountered: