So I did this recently after the 20.10 release. It was a bit a a game. I ended up installing all of the dependencies as per the git hub recommendations separately and ended up with about two that would not install so I went looking for the older packages in the ubuntu package directory. The Groovy Gorilla has the libcfitio9 installed but you can get the io8 version from the ubuntu packages repository ( packages.ubuntu.com/focal/libcfitsio8 ) and install it as a deb package. It will solve some of the dependency issues. I still was unable to install indi-full however. However this is not really needed.
I ended up doing sudo apt-get install kstars-bleeding on it's own. Then installing libindi1 as a separate package and indi-bin I think. Then I just chose the individual drivers that I needed for my set up (asi, myfocuserpro2 and eqmod). I had a few crashes with eqmod but then it all settled down and now appears to work. I keep seeing the gsc not found but this could now be part of kstars bleeding but I am just guessing as the KStars ekos/limited indi appears to work ok now.
I did this purely for "fun" there is no way I would trust it this early on. Clear nights are a rarity at the moment.

Cheers,

Mike

Read More...

Hi
Check out this thread that covers two ASI cameras not being recognised. It is likely that your problem is not driver related. I use the same set up and had similar problems. Editing the rules files as per this thread sorted out the problem. indilib.org/forum/stellarmate/7374-no-as...ct-port-mapping.html
I dont think that you need to bother winding back the kernel now so dont follow those instructions at the start of the thread. Look to the end of the thread and change the rules file (just missing some backslashes) then see if you can connect.

Mike

Read More...

My bad,
I thought that I had the latest nightly but that was incorrect. This issue has been fixed in nightly build.
My apologies.

Mike

Read More...

Hi,

I recently did a reworking of my raspberry pi4 using Ubuntu20.04.1 and am using the Kstars 3.5 beta version with latest nightly build. Last night I had some problems with focusing and noticed that focusing in and out were reversed. Using the "enable reverse direction" tab in the indi driver did not have any effect. I checked using the Windows based stand alone focuser application and this worked fine.
I have checked through the forum and cannot find anyone else with this problem. However I did find a reference in github from Rob Brown that this was a problem and there was a commit to change. Can anyone tell me if this fix has made it into nightly build? BTW I have the latest firmware for the myfocuserpro2 loaded.

Cheers

Mike

Read More...

Michael Hamilton replied to the topic 'Wifi Issues' in the forum. 4 months ago

Glad to hear you found a solution!

Mike

Read More...

Michael Hamilton replied to the topic 'Wifi Issues' in the forum. 4 months ago

Hi astrodd,

I have a similar situation. My observing location is right down the bottom of the garden in a fenced off pool area with metal fencing all around. I have a pretty powerful router in the house but have found the best connection has been using a Netgear EXT6200 extender. This is dual band. It has the advantage of being able to be powered by a 12 v dc supply rather than needing a power plug like many extenders on the market.
I connect to the Netgear using the 5GHz band from the Pi (Static IP). Then the Netgear connects to the house network via 2.4GHz. I have used ethernet from the Pi to the Netgear but I have not found this to be better. Less cables the better. I then connect to the Pi headless via Real VNC (I use Astroberry).
I use this extender in the field too (peer to peer) as it gives enough range to image from a club house or car using a laptop if very cold.

Hope this helps.

Mke

Read More...

Hi

Make sure that you have disabled virtual GPS service by running
sudo systemctl stop virtualgps && systemctl disable virtualgps
in your terminal just in case it is trying to pull data from two sources.

Mike

Read More...

Michael Hamilton replied to the topic 'Zippity.' in the forum. 5 months ago

Hi lhoujin,

Thanks for the warning. I was looking into overclocking the gpu and I have the same GPS so glad I resisted the temptation!
I did come across this overclocking resource.
www.raspberrypi.org/documentation/config...-txt/overclocking.md
It suggests that just changing the gpu_freq in config.txt may result in failure to boot etc.
The relevant section is in the "specific to Pi4B" section.
You might try changing the individual settings as described and see if that lets the GPS be unaffected.
I have decided to leave my gpu alone and just take the gains from arm overclock and SSD boot up.

Cheers

Mike

Read More...

Michael Hamilton replied to the topic 'USB3 / WIFI' in the forum. 5 months ago

Hi amendolajamie,
Looking at Doug's post there may be some RF interference with HDMI when connecting through 2.4GHz wifi (if I read correctly). Try using the installed VNC in Astroberry and connect headless. This is really easy and stable. Just downlaod VNC on your PC or laptop and find out the IP address of the Pi then connect by using that IP in the VNC address. I would check what the IP address your Nest wifi is assigning and lock that in as a static IP.
I don't know much about Google Nest but my wifi's "smarts" changes from 2.4 to 5GHz to find the best signal. This is a pain. This is OK when using a laptop but may cause issues with the Pi. Try to ensure that the Pi connects with a static ip and preferentially to either 2.4 or 5GHz. Limit the choices. You can do this in wifi and network preferences in Astroberry by assigning a number (I think that this is between 0 and 100). I seem to remember that the default is 0. So if you put 99 this will be the WiFi freq and network that is tried first. If you have other freq or networks that you use you can assign these lesser prominence.
If your Mate set up works headless then there is a chance it is the HDMI connection that is the problem. Doug's post may shed some light on this issue.

See how you go with those suggestions and let us know how you get on.

Mike

Read More...

Michael Hamilton replied to the topic 'USB3 / WIFI' in the forum. 5 months ago

Hi,

You need to give more information about your equipment and configuration. Are you using a USB hub? Is it powered? Or are you plugging direct into the Pi? What other equipment are you plugging in at the same time and what USBs are these occupying (2 or 3)? What wifi network are you trying to connect to 2.4 or 5GHz? What version of Astroberry are you using and what version of KStars/Indi are you using if you have updated separately. What equipment are you trying to connect and what actual problem are you experiencing?
All these things may have a bearing on wifi and USB3 compatibility.

Plenty of people here can help as connectivity issues are quite common especially after upgrading.

Cheers

Mike

Read More...

Hi,

I have just got my Rpi4 booting Astroberry from SSD. As I run headless and the pi is in an enclosure so not easily accessible it was a little difficult to troubleshoot. I recently had to get a larger SSD for my desktop pc so I had a spare 120GB SSD "lying around" so thought that I would see if I could speed up my RPi.
However I followed all the instructions about changing the EEPROM etc but still the Pi would not boot up and would not appear on my network to VNC into..
After a while I found references to issues with some of the sata to usb adapters.
Of course the one that I had bought that came with a nice little enclosure (JMicron) was one that was reputed not to work :(.

Anyway here is a link to a video. www.youtube.com/watch?v=9HV4C0Llktk (The same submitter of the video also has videos on the setting up of the SSD for the RPi so I would recommned looking at those too.)
The sata adapter that I have is pretty common (bought from Jaycar in Australia - www.jaycar.com.au/usb-3-0-to-2-5-inch-sa...r-with-case/p/XC4152 ) so if you find yourself in my position try this work around.

Once you have done the eeprom update and changed the eeprom status to "stable" and flashed the image of your SD card to the SSD (you can use SD copier or pull the SD out and use Win32 Diskimager). Once the SSD is flashed, go into the boot directory of the SSD
and alter the cmdline.txt file and put the following text right at the start of the line of text (there is only 1 line).
usb-storage.quirks=152d:0578:u
Leave a space after the "u" at the end then save the file. Shutdown and pull out the SD card and reboot using just the SSD (mine is plugged into a powered USB hub). It really flies and is easier than sending the adapter back.

Hope this makes things a little easier when making this change.

Mike

Read More...