×
INDI Library v2.0.7 is Released (01 Apr 2024)
Bi-monthly release with minor bug fixes and improvements
[Kstars 3.6.9][INDI][Sesto Senso 2] AF Overscan not working correctly
Replied by Edoardo on topic Re:[Kstars 3.6.9] AF Overscan not working correctly
Hi John,
yeah, I'm using the INDI driver. I've only installed indi-full and gsc, other than the needed dependencies to build kstars.
Just to be sure, here my indi server panel:
Cheers,
Edoardo
yeah, I'm using the INDI driver. I've only installed indi-full and gsc, other than the needed dependencies to build kstars.
Just to be sure, here my indi server panel:
Cheers,
Edoardo
Attachments:
Please Log in or Create an account to join the conversation.
Replied by Edoardo on topic Re:[Kstars 3.6.9] AF Overscan not working correctly
Hi John,
I've already tried yesterday to implement the change you proposed, but it didn't work.
Now, I think I made something wrong with the compilation of the drivers.
I've followed the building guide and did:but KStars could not start the indi server correctly, it get stuck when trying to start the indi services
This is the problematic part:It happens for any connected device. If I install indi from apt the devices are detected correctly.
I've tried to install indi through apt and swap only the sestosenso2 driver with the compiled one; I've succeded starting the server and connected to the focuser, but the behaviour was the same.
That's why I think I've made some mistake along the path.
Now I try to pull and compile Jasem change and try again and report back.
On a side note, since I'm not that versed in c++, how do I uninstall the drivers after the sudo make install?
Cheers,
Edoardo
EDIT: Ok, I've installed indi-full from the bleeding-edge.
The server startup correctly and the devices connects correctly, too.
To be sure that the driver installed is the one with the fix, I've built it and replaced the one installed.
To be even more sure I'm using the compiled driver, I've added a log line that prints an unique string so I'm sure the correct one is loaded.
The fix is not working tho:
Looks like Ekos starts the undoing of the overscan before indi reports that the focuser reached the requested position, so it still use the starting position as the starting point for the subrasction of the overscan value.
I've already tried yesterday to implement the change you proposed, but it didn't work.
Now, I think I made something wrong with the compilation of the drivers.
I've followed the building guide and did:
cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=Debug ~/Projects/indi
make -j4
sudo make install
This is the problematic part:
[2024-02-17T09:53:34.816 CET DEBG ][ org.kde.kstars.indi] - Sesto Senso 2 : "[DEBUG] Connecting to /dev/serial/by-id/usb-Silicon_Labs_CP2102N_USB_to_UART_Bridge_Controller_12e4c43b6a6beb11866a242eb44045d7-if00-port0 @ 115200 "
[2024-02-17T09:53:34.824 CET INFO ][ org.kde.kstars.indi] - Sesto Senso 2 : "[ERROR] Failed to connect to port (/dev/serial/by-id/usb-Silicon_Labs_CP2102N_USB_to_UART_Bridge_Controller_12e4c43b6a6beb11866a242eb44045d7-if00-port0). Error: Port failure Error: Input/output error. Check if device is connected to this port. "I've tried to install indi through apt and swap only the sestosenso2 driver with the compiled one; I've succeded starting the server and connected to the focuser, but the behaviour was the same.
That's why I think I've made some mistake along the path.
Now I try to pull and compile Jasem change and try again and report back.
On a side note, since I'm not that versed in c++, how do I uninstall the drivers after the sudo make install?
Cheers,
Edoardo
EDIT: Ok, I've installed indi-full from the bleeding-edge.
The server startup correctly and the devices connects correctly, too.
To be sure that the driver installed is the one with the fix, I've built it and replaced the one installed.
To be even more sure I'm using the compiled driver, I've added a log line that prints an unique string so I'm sure the correct one is loaded.
The fix is not working tho:
[2024-02-17T11:06:35.294 CET DEBG ][ org.kde.kstars.ekos.focus] - "Linear: extending outward movement by overscan 100"
[2024-02-17T11:06:35.294 CET INFO ][ org.kde.kstars.ekos.focus] - "Focusing outward by 188 steps..."
[2024-02-17T11:06:35.419 CET INFO ][ org.kde.kstars.indi] - Sesto Senso 2 : "[INFO] Focuser is moving to position 2988 "
[2024-02-17T11:06:35.420 CET DEBG ][ org.kde.kstars.ekos.focus] - "autoFocusProcessPositionChange called with state 2 (Busy), focuserAdditionalMovement=100, inAutoFocus=0, captureInProgress=0, currentPosition=2800"
[2024-02-17T11:06:35.458 CET DEBG ][ org.kde.kstars.ekos.focus] - Focuser position 2800 and state: Busy unchanged
[2024-02-17T11:06:35.984 CET DEBG ][ org.kde.kstars.ekos.focus] - Focuser position 2800 and state: Busy unchanged
[2024-02-17T11:06:36.509 CET DEBG ][ org.kde.kstars.ekos.focus] - "Undoing overscan extension. Moving back in by 100 ticks in 0s"
[2024-02-17T11:06:36.510 CET INFO ][ org.kde.kstars.indi] - Sesto Senso 2 : "[INFO] Focuser reached requested position. "
[2024-02-17T11:06:36.510 CET INFO ][ org.kde.kstars.ekos.focus] - "Focusing inward by 100 steps..."
[2024-02-17T11:06:36.601 CET INFO ][ org.kde.kstars.indi] - Sesto Senso 2 : "[INFO] Focuser is moving to position 2700 "
[2024-02-17T11:06:36.601 CET DEBG ][ org.kde.kstars.ekos.focus] - "autoFocusProcessPositionChange called with state 2 (Busy), focuserAdditionalMovement=0, inAutoFocus=0, captureInProgress=0, currentPosition=2800"
[2024-02-17T11:06:36.635 CET DEBG ][ org.kde.kstars.ekos.focus] - Focuser position 2800 and state: Busy unchanged
[2024-02-17T11:06:37.162 CET DEBG ][ org.kde.kstars.ekos.focus] - Focuser position 2800 and state: Busy unchanged
[2024-02-17T11:06:37.693 CET INFO ][ org.kde.kstars.indi] - Sesto Senso 2 : "[INFO] Focuser reached requested position. "
[2024-02-17T11:06:37.898 CET DEBG ][ org.kde.kstars.ekos.focus] - Abs Focuser position changed to 2700 State: OkLooks like Ekos starts the undoing of the overscan before indi reports that the focuser reached the requested position, so it still use the starting position as the starting point for the subrasction of the overscan value.
Attachments:
Please Log in or Create an account to join the conversation.
Time to create page: 0.614 seconds
© 2003-2022 by INDI Library. All rights reserved.