Hi all,

For context:
Mount - EQ5
Guide Cam - QHY5-L-II
Image Camera - Modded 1100D

The issue I'm having is that my captured images alternate between 4290x2856 and 4272x2848 with each exposure. which is leading to problems with stacking. Until I started plate solving, I;d never noticed this issue before, and during an imaging session last night, I noticed it happening again so decided to do some tests.

Plate solving seems to be the trigger - if I run a set of images after platesolving, they alternate - if i restart after platesolving, all runs as expected.

What is happening here? It's not a critical fault, as I can get around it by restarting, but if I forget, I effectively lose half my data,



Thanks for that Jon. I'm planning on a reinstall on a shiny new Pi4 so will try again once things are up and running.


Hi all,

I'm at a loss as to how to install additional indi drivers. I have downloaded and complied the driver on github, however I cannot find a .xml file relating to the driver.

Can someone please give me a blow by blow procedure as to how I can go about installing this driver?

I am using a RPi 3a running Astroberry.

Thanks in advance.


Well I cracked it.

sudo mkdir /usr/lib/i386-linux-gnu

sudo cp /usr/lib/arm-linux-gnueabihf/libnova-0.14.so.0 /usr/lib/i386-linux-gnu

Hopefully this may help someone else out



Apologies, I'm fairly new to Linux and this may be a dumb question.

I'm trying to install the ardust4goto driver, however when I try to compile using cmake, it fails as follows:

astroberry@astroberry:~/ardust4goto $ make
make[2]: *** No rule to make target '/usr/lib/i386-linux-gnu/libnova-0.14.so.0', needed by 'arduino_st4go'. Stop.
make[1]: *** [CMakeFiles/Makefile2:73: CMakeFiles/arduino_st4go.dir/all] Error 2
make: *** [Makefile:130: all] Error 2

From what I understand, the make file references a non-existent libnova.0.14.0 file, where I currently have libnova0.16.0 installed. I cannot find any file with an .so extension associated with libnova.

I have checked for the specific folder it references and it doesn't exist, I have also searched high and low for libnova.0.14.0 however it's not on Apt-get and running dpkg on a file from SourceForge hasn't solved it.

What am I doing wrong here? Could someone offer some guidance as to how I can get this working?


Now that I have everything satisfactorily running on a Pi3a, albeit slowly, I'm looking to upgrade to something more suited myself.

I'm leaning towards the Asus Tinkerboard mainly for the "SSD Like" 16gb onboard memory, and a 4x increase in RAM vs. the Pi3.



I am trying to work out what my best option for guiding on my humble imaging rig would be. (Please, no comments regarding the spc900nc's guiding capabilities, I am fully aware that without an LX modification, I'll struggle to find guide stars, it's next on my list I promise.)

I have moved over from using an intervalometer for cam control and lin_guider for guiding to a full Astroberry installation, and figured you fine people would be able to advise me on the best method of guiding.

For context, my equipment is as follows:

Camera: Canon 1100D (modified)
Guide Camera: Philips spc900nc (unmodified)
Imaging Scope: Ian King Ikaharus (sp?) 80mm/560mm
Guide Scope: Generic Amazon Buy - 50mm/190mm
Mount: Old, black EQ5 with dual axis motor kit and "improved" handset, with ST4 socket

Guide Computer - Raspberry Pi3 running Astroberry and lin_guider.

Guiding is currently carried out by lin_guider, using the GPIO pulse driver option, .I have wired the GPIO pins to a 4 channel relay connected to an ST4 cable, which is plugged into the handset. I have used this set up with moderate success so far.

So, onto my question.

I know it is possible to utilise the guiding panel within EKOS, while still guiding with lin_guider, and the guide plot is displayed within the EKOS panel, however there is no guide image, as this webcam is being used by lin_guider so cannot be connected to EKOS . Can this guide image be displayed by EKOS? Or preferably, is it possible to use the internal guiding module to send the appropriate adjustments to lin_guider

Sorry for the waffle, I find context is key.

Thanks in advance for your replies.