×

INDI Library v1.9.8 Released (29 Sep 2022)

Bi-monthly INDI Library released with new drivers and bug fixes.

ZWO AM5 Harmonic Drive Mount

  • Posts: 10
  • Thank you received: 1
Thank you for this! How do I do the equivalent command of update_indi_core,
update_indi_drivers on Astroberry?
From looking online, it seems I have to build from source. I followed some instructions but I'm not sure I did that correctly because the firmware version is from Aug 4 and still the errors persist.
Could you please link to the correct instructions in this case?
3 months 1 week ago #85519

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

  • Posts: 10
  • Thank you received: 1
Ok quick update, by stopping and starting the drivers from the browser webpage (astroberry.local's left side panel) and then starting the indi server on EKOS, I saw that the driver for the AM5 had changed to indi_lx200am5 version 1. So I think that's the newest driver I need.
Also, not sure if it helped, but in indi options, I changed the location of indiserver to the new indi-core folder I created when building indi drivers from source (instructions to build from source from github.com/indilib/indi).

Slewing seems to work fine now without having to mess about with align in the AM5 app.
I have not yet tested in the field, but so far, the two issues related to slewing I reported previously seem to have been fixed. I will post an update later after I try out the capture and slew function under the stars.

The remaining issue is the +1h time that gets added to KStars when selecting "Mount updates KStars" option. Please let me know if there's any way I can help with resolving this.
3 months 1 week ago #85555

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

  • Posts: 10
  • Thank you received: 1
Actually, now the capture function seems messed up. Whenever I try to capture a pic using either the guide cam (ASI120mm) or primary cam (QHY183m), it says capturing... but the only thing that happens is that the indi control panel opens up for some reason (capture module continues trying to capture). Stopping capture and trying again causes a crash of kstars.
So basically, can't do polar align or take images. I wonder if the above steps to get the updated AM5 driver is responsible. Note, I am using the 'Remote' option under device profile in ekos. 'Local' kept showing the old AM5 driver.
Can someone let me know how to get the nightly AM5 driver and what paths I should use for indiserver exe and indi driver xml folder? currently I've changed the paths for these from default to /home/astroberry/Projects/build/indi-core/indiserver and /home/astroberry/Projects/indi because I thought it made sense to point to the folder that has the new indi drivers built from source.
Alternatively, A simple guide on how to just update to a nightly driver on astroberry would be much appreciated.
3 months 1 week ago #85574

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

  • Posts: 10
  • Thank you received: 1
@Jasem were you able to do polar align and capture?
3 months 1 week ago #85575

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

  • Posts: 2
  • Thank you received: 0
I’ve updated but my AM5 driver is still “indi_lx200autostar”. How can I change it to “indi_lx200am5”? Many thanks.
3 months 1 week ago #85583

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

  • Posts: 10
  • Thank you received: 1
I thought maybe the problem would be solved by buying Stellarmate OS and trying on that. But even then the driver still says lx200autostar after doing update_indi_core and update_indi_drivers. It seems indi is still looking at the old driver folder?? Anything else we need to do before or after those 2 commands?
Help us please!!
3 months 6 days ago #85622

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

  • Posts: 346
  • Thank you received: 69

Replied by Giles on topic ZWO AM5 Harmonic Drive Mount

I think Jasem said it is fixed in nightly. So you either move to the nightly (beta test) build, or wait for the next stable release.

Look at the "Get INDI" menu for instructions on how to change to the nightly build (e.g. under Ubuntu), or build INDI from source after pulling the latest from Github.

If you now have Stellarmate then you can open a support ticket with them.
__
I blog my progress: www.coochey.net
3 months 6 days ago #85623

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

In StellarMate, indi_lx200am5 is available after you run update_indi_core, just not in KStars since KStars uses an internal driver list. For now you can start the driver on console:

indiserver -v indi_lx200am5 ind_asi_ccd indi_qhy_ccd

Then update the equipment profile to select "remote", and keep everything as is. Just specify "ZWO AM5" in the mount box and then you can connect. When KStars 3.6.1 is released, it should have the AM5 entry.

EDIT: I found the reason why KStars is still using the older name. Would release a KStars fix to KStars later tonight so that the above is not necessary.
Jasem Mutlaq
Support INDI & Ekos; Get StellarMate Astrophotography Gadget.
How to Submit Logs when you have problems?
Add your observatory info
Last edit: 3 months 6 days ago by Jasem Mutlaq.
3 months 6 days ago #85624

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

  • Posts: 2
  • Thank you received: 0
Many thanks. It works for me. And also looking forward to the new update tonight. Thanks.
3 months 5 days ago #85648

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

  • Posts: 10
  • Thank you received: 1
I was able to test under the stars yesterday and indeed I can confirm the above reported issues are gone. Thank you Jasem for the quick fix!
I did notice another weird issue though. Guiding (or tracking?) Stopped somewhere around meridian (i had meridian flip off because I didnt nees it). Need to test again to confirm but anyone else noticed it?
3 months 3 days ago #85789

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

  • Posts: 20
  • Thank you received: 0
I ran into this trying to use my astroberry to control my AM5 mount. The error messages were, from first to last,

"Couldn't get date format string from device"
then
Error setting UTC offset
followed by the errors in slewing; something to the effect that "Couldn't slew to <<RA, DEC>> JNow (I don't recall the exact words), so I assume the error in getting the date cascaded into an error computing the slew target coordinates.
My astroberry is up to date with respect to the astroberry repositories (but not, of course, with kstars-bleeding)
2 months 4 days ago #86604

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

Time to create page: 1.007 seconds