Recently Browsing 0 members
- No registered users viewing this page.
Hi, first post so please bear with me, having issues with autoguiding, looked at numerous forum threads and cannot find the issue specific to my setup and the issue I am having.
Equipment in question:
ZWO 224 using as guide camera plugged into raspberry pi running Astroberry via USB3,
Lynx Astro EQDIR cable plugged from USB on raspberry pi into hand controller port on AZ GTI.
Synscan android app successfully connected to AZ GTI via wifi and can control via mobile phone,
AZ GTI setup to connect to raspberry pi (so it's on the raspberry pi network) AZ GTI connected successfully as it is recognised in PHD2 and EKOS,
In PHD2 the mount is setup as INDI mount (AZ-GTI) and connects.
PHD2 is unable to guide in either RA or declination (see screenshot error showing up), it is always one or the other. I have tried setting up multiple times, tried using the network cable which came with the camera directly from the camera into the hand controller port and setup in PHD2 as "on camera" (I suspect this setup is wrong anyway and was one of the first I tried). Polar alignment has been checked multiple times, the end result is always the same, the star field within PHD2 window will always drift in one direction so any star chosen will eventually disappear out the field of view as the mount isn't moving to follow it.
Looking at the PHD2 graph I know it is trying to send pulses to the mount but either the movement is too much for the mount to move or something isn't happening as it should, in the example screenshot provided I tried this indoors on a fairly fast (compared to in the field) rotating star field looking at a screen so it will fail, though the mount didn't adjust at all, no matter how I've setup prior the AZ GTI refuses to adjust to follow a guide star. I have tried manually moving the mount in PHD2 and it doesn't seem to move in any direction, manually moving however does work in EKOS so the hardware seems to be plugged in correctly. EKOS even knows where the mount is pointing and can issue go-tos (although it is slightly off target at the moment).
I am kind of at my wits end to why autoguiding isn't working, if anyone can help please assist.
On another note if someone can advise how to configure PHD2 so the off yellow warning box colour can be changed so the error message can be read clearly - I know theres a line of code I can use in the terminal window which refers to a resource file to change to the default PHD2 colours and launches the software but the changes are never saved.
I have a triple imaging rig with 3 RPi boards and using wired LAN to the house. Indoors the rig is controlled by KStars/Ekos running in Linux Mint on my tower system.
All was working fine a few nights ago but then on a later night I kept getting "Broken pipe" errors and network disconnection. This wasn't all at once but one system at a time with a few minutes in between.
LAN consists of router plus one network switch indoors and a second network switch on the rig. Both Netgear 5 port units. I also have a WiFi LAN if that's relevant.
On the rig are 2 RPi 3B boards running Raspian and indiserver with drivers plus an RPi 4B running Astroberry Server. The first RPi 3B controls the EQ8 mount and has 2 CMOS cameras, ASI 1600MM-Cool for imaging and ASI 178MM for guiding. The other RPi boards run imaging only. Except that I also have remote focus for the imaging cameras using the Astroberry Focuser driver. The remote systems run servers and the Mint machine runs 3 instances of KStars/Ekos as clients, controlling everything via 3 individual SSH channels.
Cable to obsy is CAT6 outdoors rated cable allowing gigabit data rate.
Nothing has changed between the night the kit worked and later when it lost networking. The only thing I can think of is that it got warmer. I have fan cooling through the box with the 3 RPi boards and HATs. The main obsy power of 13.8v feeds the rig with a 12/24v to 5v 10A voltage dropper/regulator feeding the RPi boards. 1000µF electrolytic and 0.1µF ceramic capacitors are connected across the incoming power connector.
Any thoughts on what could have gone wrong and/or what I can do to fix it would be much appreciated. Lots of clear night skies and kit problems!!! Frustration unlimited!!
I have setup Astroberry on my RPi and set it to connect via ethernet cable to my laptop running linux. So the RPi gets assigned a 169.254.x.x address. If I enable the Wifi on the RPi and connect it to my home Wifi I am able to connect to the INDI webmanager from Kstars/Ekos profile. But if I disable the Wifi on the RPi so its only connected via ethernet cable to my laptop, I cant get Ekos to find the INDI webmanager. So my guess is that the webmanager is NOT listening to requests from the 169.254.x.x address??
How can I get this fixed?
I developed an Android app - Telescope.Touch - capable of connecting and controlling INDI/INDIGO devices, for those of you who use Raspberry/Astroberry/StellarMate.
It's really powerful, and a lot of new features are in the works.
Mobile planetarium derived from the Sky Map project Mount and focuser controller with directional pads and speed controls Receive images from INDI CCDs Database full of objects to which you can point the telescope directly from the app INDI control panel compatible with every device Aladin Sky Atlas preview and altitude graphs Astronomy utilities: polaris hour angle, compass, red flashlight Languages: English, Italian and French. Sky maps are translated in almost every language. It is available on Google Play: https://play.google.com/store/apps/details?id=io.github.marcocipriani01.telescopetouch
A Pro version is also available, mainly to support the app's development: https://play.google.com/store/apps/details?id=io.github.marcocipriani01.telescopetouchpro
I hope you enjoy it! I'm open to feedback and improvements!