Remove the netplan stuff, it is in the way when you just want to use ifupdown and /dev/network/interfaces to control your networking.
I did it like I described here: http://atm.udjat.nl/stepper/Remote%20Control%20-%20EN.pdf
As you know, the Pi4 has reshuffled the connectors, so I had to print a new front for this box. I will include the correct images when I make the final version, after testing full functionality.
On AliB you can find many step-down converters. The one I used is sealed and converts 8-52 down to 5V at 3A. For the Pi4 it is plenty, but I'm not sure about the USB peripherals.
For the Canon I found a battery adapter. When empty it has plenty space to add electronics to convert the 12V down to 7.2 or so.
I really should add some fuses to the 12V outlets, especially for the case I use a battery instead of net power supply.
I attach the box with velcro to the RA housing of my NEQ6, all that is left routing off-mount is one power cable!
For those who want to install the whole setup on a Pi 4, I have updated my step-by-step description:
File Attachment:File Name: RemoteControlv11-EN.pdf
File Size: 1,009 KB
Caveat: I still need to test in the field, but until now all looks good! It runs very smoothly.
No, I wasusing 2.9.8 from the latest stable build....
Could it be that this has the same issue?
Thanks, I will try in the weekend.
Just reinstalled my EKOS/KStars/INDI on Ubuntu on RPi3 according to
, but when I start my photo session and want to preview what's actually in view, often the FITS viewer crashes and brings down KStars and INDI as well.
What can this problem be? I doubt it is a memory problem since I have many 100s of MB left over.
Closing the preview window (if it hasn't crashed yet) also takes a long time, tens of seconds.
Possibly related question: When INDI is started from KStars, should I use local, client or both for image storage? I remember there was a -m 200 option needed for the comms to the (Canon) camera driver, is this still the case?
Not sure if it is related, but when I close the CCD preview window, EKOS/KStars/Indiserver crash.
This happens after I updated everything yesterday, presumably including the new driver...
I am running everything on a Pi3, did not get to viewing the post mortem logs.
Not sure what I am dong wrong, this used to work fine before...
Setup is EKOS/KStars/Indi running on a Pi3 (Ubuntu 16.10); EQMod mount (NEQ6) and a Joystick.
When all is tracking nicely I get to the eyepiece and fine tune where it is pointing with the joystick. Doing this, the tracking stops immediately and I can only slew.
Looking in the EKOS EQMod tab, I see that Tracking indeed is switched off.
Is there a setting I accidentally hit, that determines this behavior?
If not, what else can be causing this?
Apart from that, your Pi3 power supply also needs to cater for this 1.2A, on top of the usage of the Pi itself (anothe 1A or so?). Better select a beefy PSU then that can also handle the peak currents.
An update of the document describing my setup can be found
Currently I have installed Ubuntu Mate 16.04.2 together with the latest INDI (1.5)/KSTARS package on a 64GB SDHC card, and all seems to run very well. VNC uses vino as server and a TightVNC client on the laptop. A big improvement has been to take out the two network legs of my home WLAN, and configure the Pi as an access point. Any VNC client can now directly connect to the Pi through WiFi, and the virtual desktop operates a lot smoother.