×

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

Bi-monthly release with minor bug fixes and improvements

Avalon StarGo RA Tracking Adj Feature Request

  • Posts: 11
  • Thank you received: 3
Hello Wolfgang,

Thank you for the very fast response. From the look of the screenshots it's exactly what I need.

I've run into some difficulty installing the new driver; largely, I think, due to my ignorance and inexperience. I've never done any C coding and have never used cmake.

I followed the INSTALL instructions on branch: stargo-1.9 and after typing cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=Debug ../../3rdparty/indi-avalon
Got the message: "bash: cmake: command not found"
Without changing directory (I didn't think of changing until later), I installed cmake
sudo apt-get install cmake
this appeared to install OK

I then ran the INSTALL cmake command again cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=Debug ../../3rdparty/indi-avalon
"CMake Error: The source directory "/home/astroberry/indi/3rdparty/indi-avalon" does not exist.

I then followed these instructions at indilib.org/download.html to make sure I had indilib installed

Stable Release
INDI Library is available for Raspbian Buster. To install stable INDI Library, run the following commands:

wget -O - www.astroberry.io/repo/key | sudo apt-key add -
sudo su -c "echo 'deb www.astroberry.io/repo/ buster main' > /etc/apt/sources.list.d/astroberry.list"
sudo apt update

No errors were reported. It appeared to install cleanly.

I then went back to your INSTALL instructions and to avoid the error with not finding the 3rd party/avalon-indi directory, I ran

cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=Debug
Cmake started to run but after 24 or so lines of print-out said

-- CFITSIO not found.
-- CFITSIO not found.
"CMake Error at cmake_modules/FindNova.cmake :49 (message):
libnova not found. Please install libnova development package."

File Attachment:

File Name: CMakeError.log
File Size:3 KB

File Attachment:

File Name: CMakeOutput.log
File Size:49 KB

Also CMakeOutput.log and CMakeError.log files were created, but I don't understand what they're trying to tell me.

I searched for cmake libnova and did not find information that I could use to install libnova.

I'm afraid I'm not being of much help, but I'm willing to keep trying if you can point me in the right direction.

Perhaps this is all too much for the forum and we should take it off line?

Dave
4 years 2 weeks ago #50723
Attachments:

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

  • Posts: 1957
  • Thank you received: 420
Dave, libnova-dev is missing.

Wolfgang, you need to create a pull request so Jasem can merge the changes into the main branch.
The following user(s) said Thank You: David Kreiton
4 years 2 weeks ago #50729

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

  • Posts: 1185
  • Thank you received: 370
Hi Dave,
it looks like you need to install the libraries needed as pre-requisites:
github.com/indilib/indi-3rdparty#building
github.com/indilib/indi#building

If that doesn't help, send me a PN.

@Wouter: Sure, the PR will follow. Since Dave asked for the feature it would be great if he could test it before I publish it.

- Wolfgang
The following user(s) said Thank You: David Kreiton
4 years 2 weeks ago #50732

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

  • Posts: 11
  • Thank you received: 3
Just to close the loop for those who might be following this thread, I finally managed to make and install the modified driver and it appears to work. Unfortunately, the weather has turned cloudy for a few days so I won't be able to test it under the stars until later this week. Many thanks to Wolfgang for his patience and kind suggestions to help me navigate through unfamiliar territory.

David
4 years 1 week ago #50801

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

  • Posts: 11
  • Thank you received: 3
Further update.
The sky finally cleared and I was able to test the RA Tracking Adjust. It works great. Thank you, Wolfgang

David
The following user(s) said Thank You: Wolfgang Reissenberger
4 years 1 week ago #50947

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

  • Posts: 1185
  • Thank you received: 370
Hi David,
I changed the implementation slightly, since there is a feature of StarGO to store the adjustment in its firmware. The new version is available for testing as stargo-1.10 on my indi-3rdparty fork.

It would be great if you could double check it whether it is working as expected.

- Wolfgang
4 years 4 days ago #51079

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

  • Posts: 11
  • Thank you received: 3
Hi Wolfgang,

Thanks. The Clear Sky Chart looks pretty good for tonight. I'll try to get 1.10 built today and try it out tonight.

David
4 years 4 days ago #51084

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

  • Posts: 11
  • Thank you received: 3
Hi Wolfgang,

I built and installed StarGo 1.10 and verified by inspecting the file manager date/time that it was built.

I've tested this indoors and the RA Tracking Adjust value does not appear to be saved by the mount over a shut down & start up sequence. This appears to be consistent with the reply that I received from Stefano at Avalon in response to my question on this same topic on the Avalon Instruments forum prior to my posting this request.

Here's my testing procedure:
1. Start Kstars/Ekos and automatically connect to mount.
2. Set Tracking to -1.08 on INDI CP/Avalon StarGo/RA/Dec tab
3. Save Configuration on Options tab.
4. Load Device Configuration/Never on Kstars/Configure/Ekos/General tab
5. Disconnect equipment on Ekos and Stop Ekos
6. Exit Kstars/Ekos
7. Start Kstars/Ekos and automatically connect to mount.
8. Reported value of Tracking is 0.00 on INDI CP/Avalon StarGo/RA/Dec tab

If I Set Tracking to -1.08, Save Configuration and change to Load Device Configuration/On Connection on Kstars/Configure/Ekos/General tab and then shut down and restart the reported value of Tracking is -1.08.

Perhaps I am missing something? I'm certainly no expert at this. :-)
One thing I have not found is a way to Load Device Configuration at any time other than On Connection.

Hope this has been helpful.

Regards,
David
4 years 4 days ago #51110

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

  • Posts: 1185
  • Thank you received: 370
Hi David,
thanks for the test, I have to verify it. I did not shut down the mount between the tests, so I do not know whether the stored value survives a shutdown.

But I tested whether the mount remembers the value at least while it is turned on. This is the case, so connecting, setting the value, disconnecting, connecting and reading the value returns the value that has been set.

Now my mount is running, M108 is in focus, so I have to wait until tomorrow.

Wolfgang
4 years 4 days ago #51123

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

  • Posts: 11
  • Thank you received: 3
Hi Wolfgang,

I think I was not clear in my previous post. I did not power down the mount but performed the same test that you did. I found that if the if the Load Configuration was set to Never, then a value of 0.00 was returned from which I concluded that the mount was not remembering the value. If the Load Configuration was set to On Connection, then the correct value was loaded into the mount and displayed on the RA/Dec panel.

Perhaps I'm not testing this correctly? Or maybe I didn't do the make properly?

Regards,
David
4 years 4 days ago #51128

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

  • Posts: 1185
  • Thank you received: 370
Hm, OK, now I got your point. Are you sure that you are testing the 1.10 version? Because one of the changes I made was that the tracking adjustment is no longer stored in the config file but it remains inside of the firmware.

I indeed made the mistake and forgot to call a "make install" so that my mount is currently still running on the 1.9 version, where the adjustment parameter is stored in the client.

I just pushed an update to the 1.10 version so that the new version number is visible in the INDI client. If you pull it, rebuild and restart the driver, you should be able to check whether you are on the right version.

I will do the same in a couple of minutes. Fortunately, it's not too complicated to restart capturing: stop the scheduler, disconnect from the driver, restart it, connect back and restart the scheduler. Should be a matter of 5 min.

Wolfgang
4 years 4 days ago #51129

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

  • Posts: 1185
  • Thank you received: 370
OK, now I retested it with the right version. For me it looks good, the mount reacts on the parameter changes. I could see drifts either west or east, depending on a positive or a negative adjustment.

The parameter is also no longer stored in the config file. The only thing that I would like to check during daytime is whether the parameter survives a power off.

Good night
Wolfgang
4 years 4 days ago #51130

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

Moderators: Radek Kaczorek
Time to create page: 0.731 seconds