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?
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!!
@Jasem were you able to do polar align and capture?
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.
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.
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?
Note, I did apt update apt upgrade just yesterday so everything should be the latest version
Man, I wish I knew how to debug drivers. Would love to be able to contribute to such efforts.(Is it easy for someone with some c language code debugging experience??). Hopefully, posting logs and documenting problems counts as contribution.
Anyways, it seems like only minor fixes may be required though. Fingers crossed, there is a developer out there with an AM5 who can fix it. I am happy to help in any way possible.
The main problems I'm seeing:
1. Local Time Mismatch:
There is an option in KStars to get local time data from the mount (which in turn gets the info from the smartphone wifi or local wifi network to which it is connected to). However, the time is always extra 1 hour compared to actual local time. I'm guessing this is related to the "time format" error that crops up when starting the indi server (both logs below show this error). So, basically daylight savings seems to be added once in the AM5 app and once more in KStars (cannot modify UTC time offset in the mount's indi control panel and cannot modify the time in the AM5 app to compensate).
2. Slew Error:
I get a slew error message whenever I try to do a GoTo without first doing a 1-star align using the AM5 app. This is the first log attached below. I did the following sequence of actions: Start indi server-->try GoTo on some star (deneb I think)-->See Slew Error-->Try sync on some star-->Try slew again-->Slew Error.
I've been spending some time with astroberry EKOS and the AM5 and here's my update/observations. Hope more people can add their experiences and tips here.
First of all, yes INDI already shows ZWO>AM5 as a selectable mount. So driver is technically ready to use if you have the latest indi update. The driver seems to be the same one used for Meade lx200 autostar.
That said, there are some quirks that I felt need fixing in future driver updates.
Firstly, the above problem of slew error does not occur if I first do a 1 star align using the ASI mount app. Once I do an align on a random spot in the sky and then do goto on kstars sky map it goes to the object. But it doesnt work fully. Once the slew is technically done, ekos still thinks it is slewing. So even after I can see that the mount is stopped, ekos says it is slewing and most buttons in different modules are disabled. The band aid fix is to open the mount control window and click on STOP after which the mount shows that it is idle. Also, another related issue is that the Park button does not work. It says 'Parking' but mount doesn't move.
Secondly, kstars has an option to update its time and location using the mount. However, the Time is always +1hr extra because the UTC data downloaded from the mount seems to include +1hr probably due to Daylight saving added. This needs to be fixed in kstars because the mount app has no option to adjust daylight saving info. Until then I'll be using GPS dongle which takes a while to get a fix.
Guiding, polar align works well in conjunction with above band aid solutions.
I welcome any qs anyone may have. Will probably create a new thread with logs for troubleshooting above issues.
Anyone have any luck with Astroberry EKOS + AM5?
I am trying to get the mount to slew to a target but I get : [ERROR] slew failed (-1)
I'm able to control the mount using the Mount Control arrows, and Kstars updates position of the mount as well. Just not able to use GOTO function. (have not tried anything else like guiding/platesolving/polar alignment yet, only trying to point to some target to start with)
Any ideas to fix it? Attaching the log file if that helps.