I am right in the midst of switching from RPi 4 8GB to a Mele Quieter 3Q mini PC. I noticed some people earlier on in the thread mention HDMI dummy plugs. Are they necessary? What am I missing out on by not using one of those? I seem to be able to remote into the Quieter just fine. Could it help speed things up even more? Is it perhaps a Linux thing, since I have only dabbled with Windows so far?
Well, here's an update on where I am at at the moment:
Being too dense to solve the issue stated a few posts back I went back to TJ's Allsky instead, worked from the get go. Maybe I will give this one another try if I ever get a camera not supported by TJ's offering.
Thank you, that sorted that problem out.
Now, here's where I am stuck at the moment:
What am I missing here? Some settings and additional configuration to be made?
Just installed this, on my Raspberry Pi 4 2 GB with a Pi HQ camera.
It won't allow me to save any any changes made in config tab. I just get the message: "Please fix the errors above. And the issues then seems to be that it says that IMX477 is an invalid camera interface. No pictures seem to be taken.
What do I do?
I do not think Stellarmate is based on Ubuntu any more. Seems like it used to be, but since 1.5.0 it has been based on Raspbian, as mentioned
I now have tried out Ubuntu Mate, fetching Kstars/ekos/INDI worked very well there using the PPA. However, as I need to control it remotely, I installed VNC, and it was an extremely sluggish experience. This coupled with me being unable to use the previously mentioned instructions for getting the INDI drivers for my Astrolink 4 Pi up and running, I feel like this is yet another trench that I don't have the competency or patience to dig myself out of. Is there a prefered way to remotely operate an RPI running ubuntu mate that is not super slow? As the INDI drivers for the Astrolink 4 Pi only is coupled with instructions for Astroberry and Stellarmate, could it be the case that the drivers do not work on Ubuntu Mate? Would they need to be modified? Do I need to have the maker of the Astrolink make modifications on the drivers for it to support Ubuntu Mate?
But which firmware is actually on your Sesto Senso 2 right now? On mine I have the 03.03.07 and it does not show this bug in SM 1.7.5. Granted, it is not a fresh install, but an upgrade from freshly installed 1.7.0.
I have considered Ubuntu Mate for that very reason. What has been stopping me is that I have a device called Astrolink 4 Pi. It is a power distribution box, dew heater controller, housing my Raspberry Pi 4. For it to work, and to be able to control it, I need to install the INDI software for it, and the instructions that I have access to only is for either Astroberry or Stellarmate. And I do believe the Stellarmate instructions also work for any Raspbian Bullseye installation. But again, I may even have got that part wrong. The instructions and software for the device can be found at
. Perhaps it is not very difficult to get that running on Ubuntu Mate as well?
Let me explain why I am trying to do this in the first place. I have been using Astroberry before, a few crashes every session, but I have learned some things not to do, in order to not provoke the crashing and it has been working OK. But still, I considered going the Windows route instead, using my small Mele Quieter 3Q mini PC. Turned out I needed to upgrade the firmware of my Sesto Senso 2 in order to get that working with Ascom. Upgrading the firmware, in turn, broke the compatability with INDI for the focuser in Astroberry. New INDI drivers have been released that reinstates have been released. Astroberry, which is a bit behind now, have not had these new drivers added, hence I have been looking for other options. I have not getting everything I need for going Windows yet, so I need to use the Astrolink 4 Pi for a while still.
Followed that advice of yours, I could not get anything to run. The kstars-bulid folder is quite small. a few hundred KB and only a couple of objects. I feel like there should be more there?
It took well over an hour for the Pi to run the script through, or whatever it did do. But I guess that stuff was built, and it did not only set up the folders.
I did quickly look through of everything written in the terminal, but given that there were probably thousands of rows and I actually did not really not know what to look for there could very well possible be tons of problem that I missed. Is it possible everything stated in the terminal while running the script is saved somewhere so that one can look through it afterwards?
Sure, it is possible that it simply did not manage to create desktop shortcuts. If so, how do I create them myself?
I also have an SD card setup with Astroberry. So, for reference, I booted that up and looked where the kstars shortcut in Astroberry pointed to on the SD. The target folder was a folder called "application" which contained a type of object(again I do not know the proper terminology) for each of the programs installed in Astroberry, that is kstars, PHD2, internet browser and what not. The corresponding folder on my new installation had all the Raspbian regulars but all of the program that was supposed to be installed by the script were missing.
I am a Windows guy and pretty much completely Linux illiterate and I do not really have a clue how to proceed.
I have tried this script on a Raspberry Pi 4 running Raspbian Bullseye 64-bit. One issue is that it messes up my wifi and lan connections, network manager never starts on its own. This I can easily fix myself.
However, a more devestating problem is that none of the astrophotgraphy related software seems to be built/installed(or whatever the terminology is) correctly. A folder containing several gigabytes of data called Astroroot is created which does contain a set of folders named after the various astrophotography software. But I can not find any way of running them. There are no icons created either on the desktop or in the "start menu". How do I find out what has gone wrong so that I can fix it?
Thanks for the input, but I have not had any issues with wifi like that. In fact, I am not using wifi at all, instead going the ethernet cable route.
I will try out using RealVNC instead. I have been unsuccesful in setting my Stellarmate installation to BETA, nothing happens and it does not seem do switch when I press the button.
Had a go at Stellarmate. Using the Stellarmate software updater did not do the trick though, entering the correct commands into the terminal I finally did manage to get the new drivers and my Sesto Senso 2 seemed to work perfectly. However, in the process something else broke and my imaging camera(ZWO ASI533MC) and guide camera(SVBONY SV305M Pro) stopped working as their drivers instantly crashed upon starting the INDI server in Ekos.
But... The worst part is how horribly slow Stellarmate was to use over VNC compared to using Astroberry over VNC, which is incredibly snappy whereas Stellarmate is more like watching a laggy and non-responsive slideshow.
So, if I could get my Astroberry installation up to snuff, that would be great.
Yeah, I might have to go for downgrading the firmware in my device. Although I would also like to be able to also use my small Windows PC for controlling my gear, and there ASCOM requires the latest firmware on the Sesto Senso 2.
All of this fiddling with different software, drivers and firmware to even get things to work is so incredibly frustrating.
I still have not managed to implement these changes into my Astrobery installation, and I am therefore considering abandoning Astroberry. Does anyone know if Stellarmate have these changes, or will recieve them soon?
Is there someone who could help aid me in adding these fixes to my Astroberry installation? My Sesto Senso 2 is just sitting there, unused.
Another Sesto Senso 2 user here, suffering from the same issue. I am totally illiterate when it comes to these thing so I would need a lot of help and guidance if I were to try and be of any help in solving this.