Hi Radek, After a couple of days of 'playing', I have noted a few things which are not so much issues, but perhaps missing FAQs to help the first time user:
I happen to use a Swiss French keyboard layout so the default password is 'astroberrz' - easy enough to cope with until you can log into the raspi-config tab menus. I also happen to use an iPad as my client terminal so I didn't see the sliding panel in the iOS Firefox browser implementation. I did see this when I swapped over to a Windows 10 laptop, and immediately understood about the sliding panel, although not all functions perfectly (yet).
I confirmed that the gpsd daemon was active and so tried to use my GPS dongle, after editing /etc/default/gpsd to include the device as dev/ttyACM0. The GPS Satellite Map did pick up several satellites, but never at enough signal strength to influence the GPS info Lat and Longitude. The same dongle normally works very well in EKOS/Indi with a full 3D fix in seconds. Is there some extra constraint in the Astroberry implementation which requires a higher signal strength (I wouldn't have thought so)?
My normal configuration involves being in the field away from home WiFi and therefore the Internet, and using the RPi as a WiFi HotSpot. This does work, but the lack of Internet means that some functionality, such as the Weather App, and the location setting, are a bit redundant.
I'll keep on trying things out as I find time!
Thanks again, Ed
Hi Radek, and many thanks for your efforts in preparing Astroberry 2.0.0!
Of course some of us are going to have some tiny issues in the coming days, and the one that is stumping me is to do with the 'Weather Plugin'. The first couple of times I attempted to set it up I was running in HotSpot mode and when I realized this, I hit 'Cancel' in the Weather Preferences dialogue box. This closed not only the dialogue box but also the whole task bar disappeared. I didn't have the skills to get it going again, so had to carry out a brutal physical power down/power up to recover. Happily this didn't damage the SD card image.
I tried updating the Weather Preferences again this time with Internet connection and was successful. However my location data was not saved on shutdown however so it seems this is a burden of each power up routine.
I have subsequently added a GPS dongle (installed GPSD etc) and wondered if the GPS data could be used to establish my location coordinates?
Doing the same here (with fingers crossed!) I'm not getting the best speed of download from the Indi website.
rlancaste wrote: Ok my pull request just got merged. Please test it to see if this fixed the build problem
Morning here so I reran your script on the Pi4. The Drivers for the cameras and GPSD have all returned. However there is another more serious problem now. Every time I try to launch Ekos with any equipment profile, KStars crashes. The Indiserver is left running, apparently, so waking up KStars brings up a message about closing down the Indiserver before starting up Ekos, but everything just crashes when you do this.
Hi Rob, I thought I'd make up a fresh SD Card installation and so this wet evening I've also run the new version of the your script under Raspbian. I also have found that the cameras available in the drop down list when setting up your equipment profile are very restricted in number with the ones I am interested in (Canon DSLR and ZWO) missing. Also under the Aux drop down list, GPSD is no longer present although GPSUSB and GPS Simulator remain. I guess this is due to the build of KStars which was cloned tonight?
You may find it helpful to see the thread 'AstroPi3 Scripts Revised' which follows the history of Rob's 'rlancaste' excellent scripts for installing a whole package set including on Raspian Buster on the RPi4 (no need to reinvent the wheel!)
Not a silly question until you have learned the technique!
Whilst still in VNC Viewer with the RPi in Hotspot mode open the Utilities folder on the desktop, and double click on StartNMService.desktop Enter the RPi user password and return, and the WiFi will switch off the hotspot and search for (and find) your home network. You will be knocked off the hotspot so you should connect with VNC Viewer again using your home WiFi settings.
Last night I had a successful session with my usual setup having switched back to my Canon 450D. At first I tried my 550D, but on each of two times I tried to Polar Align, KStars/Ekos would crash just before showing the Alignment Frame I.e. at the end of the 3 plate solves. Back with the 450D and no crashes. I noted a significant difference in the solving times between the two cameras 9 secs for the 12Mpixel 450D, twice as long for the 18Mpixel 550D. Next clear night I’ll try out my RPi4 4GB rather than my 2GB, although the latter is housed in a flirc case and stays very cool outside with no fan.
Raspbian Buster in my case. The crashes only seem to occur when I am actively clicking on a button. When KStars minimises as I minimise Ekos, it is always possible to restore things from the Tab strip at the top of the screen.
Otherwise I haven’t suffered any random crashes, although I haven’t run any all night sessions like you.
Running KStars/Ekos/Indi on my Raspberry Pi 4 headless as a WiFi hotspot, and linking in through VNC Viewer on an iPad. Most of the things I want to do work well (better not say ‘perfectly’!) but there are occasional crashes. Specifically in Polar Alignment I have been struggling to better see the reference star against the cross hairs at the end of the correction vector. I tried the ‘zoom to fit’ button in the Alignment Vector window, and this shut down KStars and Ekos, leaving behind ‘an Indi Server’ still running. Of course this means Parking the mount and running the process again.
I subsequently located the ‘full screen’ button in the main Alignment window, and found that this does change the size of the Alignment Vector window, but not the size of the image within it, although tapping a couple of times on the ‘zoom in’ button makes the Alignment Vector window content a good size for the adjustment operation.
I’m not sure if there’s a further bug in the way the Ekos ‘minimise window’ button also minimises the main KStars window?
Many thanks to the authors for this great software!