Hi!
I'm currently using Astroberry on a RPi 4 which works great. I've configured a Lattepanda 3 Delta single board computer, installed Ubuntu Mate and the latest stable release of IndiLib and EKOS. Installation worked like a charm and I've just started to copy profiles from my Pi to the Panda and this is where the problem arise:( According to a video by Jasem I should be presented by a "trains dialog" after starting my Indi-profile. Unfortunately I'm not, leaving everything such as downloading index files a "no go". I usually use a "Telescope simulator" together with the scope/guidescope in the profile editor and this has been working excellent for this purpose. I'm reluctant to mount/dismount my setup just to download, say, download index files. Is there a limitation ("bug"?) in Indi which doesn't enable trains when using the telescope simulator?
The concept of trains in EKOS is new to me although I fully understand it's purpose.
Any help here is very much appreciated as I'm stuck with the Panda 
Read More...
Hi Thomas!
The cables are good quality BUT I'll definitely visit the Pegasus store after this "incident" Very annoying indeed but now my Avalon is purring like a cat so I'm a happy camper!
Cheers
Read More...
Hi Gilles!
Thanks for chiming in! I think I found the issue and it had nothing to do with the mount and I've updated my post to reflect this.
The mount is just fine. Phew
Cheers
Read More...
Hi!
I'm running a Raspberry PI4B with Astroberry v2.0.4 and Indilib v1.9.7. Connected I have:
- Avalon Zero Obs with StarGo connected over USB (Using the Indilib StarGo driver)
- Atik Horizon II
- QHY CCD5LII
Recently my mount started to behave erratic and says "Could not get the motor status from mount (err: -4)" or something like that. I've checked the logs and that is the only error reported. This usually shows after 3-4 and sometimes after up to 7 slews. After that the mount becomes very slow in its responses and it fails to report back the position to EKOS thus not updating the scope position in KStars. I can see that Ekos/Indilib sends :34# and then waits for 2 seconds which results in:
- Failed to receive full reponse: Timeout error. (Return code: -4)
- Failed to parse motor state response ''.
- Failed to parse motor state. Retrying...
And this goes on and on...
I've tried three different Avalon FW:s
- 6.20SP6
- 6.56B2
- 7.?
All of them behaves in the same way. Anybody else having the same behavior?
Cheers
Read More...
I thought I'd post a clarification here in case somebody else should stumble upon this. The problem with the Avalon's regarding the polar alignment tool has to do with misinterpretation of east/west by the mount and resides (my assumption) in the Avalon's FW and/or the Indilib driver. I was thankfully directed to these threads here by a fellow Avalon owner:
Avalon ForumAvalon Forum
Indilib Forum
Cheers
Read More...
Hi!
Thanks for your reply! I thought there was another setting where you may map 'find = 256x, max = 512x' etc. When I use the Avalon mount those speed selections are not numerical - instead the menu reads 'find, max' etc which in turn are mapped to a numerical equivalent. I don't think this is the issue here.
Cheers
Read More...
Hi!
I have the following:
- 90mm/F6 APO with 0.8x reducer/flattener
- Edge HD 8 with v4 Hyperstar
- Avalon Zero Obs FW 7.?
- All index files needed downloaded
- Astroberry 2.0.4 running on RPi 4
Suddenly the PAT stopped working with my setup! I upgraded to 2.0.4 and the polar alignment tool fails to work. If I select the "Find" speed and click start the mount starts to slew but very slowly and seems to time out. If I select max the mount slews but the operation fails without an error - it just says to place the scope in the home position and restart the process. Plate solving works perfectly though. It seems that the PAT fails to get a proper reading from my mount. This has worked very well in earlier versions but fails miserably in EKOS 2.0.4.
I've read somewhere that it should be possible to specify the speed in x * sidereal, say, 256x but I have no such setting in EKOS/Indilib control panel.
Has anybody else seen this behavior?
Cheers
Read More...
Hi!
I'm running KStars 3.5.9 in the latest Astroberry build on a RPi 4 with 8GB RAM. I'm connecting an Atik Horizon II Color camera using a USB 3.1 Cable and when firing up Indi the camera gets connected and showing I'm using v2.9 of the inid_atik_ccd driver. When switching to the EKOS Capture module I'm unable to capture live video. Is this a known behavior and/or do I need to make some additional adjustments in order to get this to work? "Ordinary" exposures works fine.
I also tried to launch oaCapture but it doesn't recognize my Atik camera.
Feeling lost... Anybody out there having any ideas?
Cheers
Read More...
Hi Eric!
Good to know! I'm thinking of getting the color Horizon II - feel like skipping mono + filter wheels initially
Cheers
Read More...
I'm planning on purchasing one of these and would like to know if they're supported by any indilib drivers before jumping aboard...
Thanks in advance
Read More...