I understand that you connect your mount with EQDIRECT cable to Raspberry Pi. Just to be sure, you are connecting it directly and you don't use synscan hand controller, right? And you use EQMod Mount driver, right?
It seems that another device is claiming /dev/ttyUSB0 port used by EQMod Mount driver. You need to identify which one it is. Disconnect all devices and connect only the mount, then connect other devices one by one and observe the logs.
GPSD is a generic, system wide service providing location to various system components. It can use various sources of location data, namely a gps receiver connected locally (most often as a serial device), gps receiver over network (eg. from your mobile) or virtualgps provided by Astroberry (static location configured in /etc/location.conf). Make sure that you don't set gpsd config to use the same serial port as your mount as this would cause problems. Leave gpsd configuration default in /etc/default/gps unless you know what you're doing. If your gps is connected to USB, it should be automatically picked by gpsd service. If using real gps, disable virtualgps service.
Astroberry does not use Privoxy
Your're obviously missing libqhy, which is part of indi-3rdparty sources
Just to let you know... an INDI driver for this board is on its way!
Thanks Kevin. I will give it a closer look then to add support for this device to Astroberry DIY
Hi Kevin, I'm glad you found my
driver inspiring and base for your project. Great work!
I have just purchased Waveshare motor HAT and given it a try with Astroberry DIY , which is much more advanced focuser driver than Astroberry AMH.
It supports DRV8834 and A4988 stepper controllers, supports custom GPIO pins, uses kernel native libgpiod instead of bcm2835 or wiringpi, remembers focuser position between runs and provides focuser temperature compensation with DS18B20 sensor.
It uses typical DIR, STEP, SLEEP, M0, M1, M2 pins connected to Raspberry GPIO so I tested it with Waveshare motor HAT. Well, it works but I faced some issues with microstepping and sleeping a motor.
As you probably have much more experience with this device, I've got two questions:
1) It looks like the device does not handle software microstepping without touching hardware i.e. dip-switches. Am I right saying that you cannot control microstepping with software only?
2) Another issue is related to sleeping a stepper motor. Apparently hardware designers did not wired SLEEP pin of DRV8825 to any of Raspberry GPIO. Does ENABLE pin cut off step motor power circuit so it does not get hot?
xthestreams wrote: Glad to hear it! BUT remember the first rule of astronomy club, we talk don't about how much our equipment ACTUALLY cost us in public forums just in case our partners find out!
"no really, this guy sold it to me for $100, I couldn't believe it EITHER, besides, the kids don't REALLY need new clothes those old ones fit them just fine"