Anybody using Astroberry Server. I have promised an update to the distro some time ago. Long time ago actually... My assumption was to release the new version based on Ubuntu Mate 18.04 instead Ubuntu Mate 16.04. The reason being Ubuntu Mates 16.04 is going to loose it's support in March 2019.
Unfortunately Ubuntu Mate team has not released the version 18.04 yet - even though it was planned to be released in July 2018. This holds me from the major update. I do not want to use a custom build of Ubuntu Mate 18.04 for compatibility issues which might arise when the official 18.04 release is available. I hope you all can wait a bit longer to get the new version of Astroberry Server. Especially that the new version will be based on LTS (long term support) distro, which will be supported until 2021. I can assure it will be released as soon as official distro from Ubuntu Mate is available. In the meantime take a look how an imaging session looks like with the current version of Astroberry Server (1.0.4) - youtu.be/4Qy4jkQZ82A

Read More...

I do not have any knowledge of Celestron Evolution 8 whatsoever so maybe somebody who uses it can help... BUT
First, 192.168.10.10 is a static IP assigned to astroberry access point so you CANNOT use it on any other device connecting to astroberry access point. Use for example 192.168.10.11 or anything within 192.168.10.x network.
Second, gateway = 192.168.10.255 is wrong for sure. The gateway for your mount is astroberry so you should use gateway = 192.168.10.10 instead. However it only applies to accessing the INternet from your mount through astroberry access point. If you don't need to access the Internet from your mount it does not make any difference. Anyway gateway = 192.168.10.255 is not what you can use because 192.168.10.255 is reserved as broadcast address for entire 192.168.10.x network. It comes from IP network specification not astroberry itself (it's the IP networking rule).
Try this out and let us know how it works. Good luck!

Read More...

Planetary Imager distributed with Astroberry Server has been compiled from source. At the time the latest Astroberry Server was released there were no binary versions available. Why don't you use oaCapture? It supports ASI cameras natively.

I'm planning to release the new version based on the latest Ubuntu Mate 18.04... however it's still not available for Raspberry Pi. It was supposed to be released in July... and I'm still waiting for Mate dev team. The new version will include major bug fixes and improvements as well as support form Raspberry 3B+

Read More...

RTIMULib has always been a requirement for indi_altimu driver, part of Astroberry drivers suit.

Requirements
============
* INDI available here http://indilib.org/download.html
* RTIMULib (for Astroberry AltIMU) available here https://github.com/RPi-Distro/RTIMULib
* bcm2835 (for Astroberry Focuser and Astroberry Board) available here http://www.airspayce.com/mikem/bcm2835/

################ Astroberry AltIMU ################

#set(indi_rpialtimu_SRCS
#        ${CMAKE_CURRENT_SOURCE_DIR}/rpi_altimu.cpp
#   )

#add_executable(indi_rpialtimu ${indi_rpialtimu_SRCS})
#target_link_libraries(indi_rpialtimu indidriver RTIMULib)
#install(TARGETS indi_rpialtimu RUNTIME DESTINATION bin )
#install(FILES indi_rpialtimu.xml DESTINATION ${INDI_DATA_DIR})

This driver uses submodules, which are downloaded to /home/steve/astroberry-amh/build/libs/AdafruitStepperMotorHAT_CPP
Just delete the /home/steve/astroberry-amh/build/libs directory and rerun make install

Read More...

The issue has been hotfixed in the last commit. Please redownload the code and recompile.

Read More...

I don't think there is a binary package available. You have to compile it yourself from sources

Read More...

What do you mean by saying "GPIOs 13, 19, and 26 are not linked to BCM2835"? Did you change GPIO mapping in the driver's code? If so, did you use proper numbering? Check this (RPiGPIOPin specifically) to reconfirm this.

Read More...

petarm wrote: Hi Kaczorek, yep i did all that, gpsmon in a terminal tells me the gps adapter is connect and working and acquiring gps data. But when i then run gpsd in kstars/ekos, it was not populating UTC, it was using the time from the asus tinker board.

// Update time regardless having gps fix.
// We are using system time assuming the system is synced with the gps
// by gpsd using chronyd or ntpd.