Just install INDI Web Manager on each Pi. It will start automatically and you can configure profiles with different sets of drivers, autostart one of the profiles and manage it via a web browser from your client
PHD2 recently changed its native ASI driver to use trigger mode in place of streaming mode. I wonder if there is a compatibility issue with your camera operating in trigger mode.
Even if I set Cooler Off and save in my config, whenever I start up INDI the cooler comes on and seems to be setting to 0 degrees.
I *think* what is happening (from a quick look at the code) is that when the ZWO driver starts up it loads the Cooler Off switch config but the temperature defaults to zero. And setting the temperature always turns the Cooler On, overriding the switch.
I like to have the cooler off at first to reduce the load on the power supply at startup but there is no way I can make this happen without unplugging the cooler power.
The first thing that comes to mind is flexure in the guide scope causing it to follow a non-circular path as you rotate.
Running Kstars/Ekos 3.0.0 on Windows 10 x64.
Last night got a bad alignment. I was aligning on NGC2775 but after alignment I was off by about 15 arcmin in RA and NGC2775 was on the edge of the FOV.
I've had something similar before and it was due to Ansvr being set to J2000 instead of JNow. So I checked that it was set correctly.
I've attached the Kstars log and the Ansvr log. The problem is apparent at 21:22:20 (line 20718 of Kstars log and line 1662 of Ansvr)
Target Ra/Dec in JNOW is 9h 11m 21s RA, 6d 57m 33s Dec or in decimal degrees 137.8375, 6.95916666666667
Ansvr returns JNOW solver result of 137.585347251, 7.038789885
Near enough to dec 0 so I make that approx 16 arcmin
Ekos confirms the solver coords on line 20718 but on line 20719 reports them as RA 09h 11m 21s DEC 06d 57m 33s and determines that is within the acceptable range. It looks like Ekos is treating the Jnow coordinates as J2000
Is there a setting somewhere I've changed by mistake?
File Attachment:File Name: log_21-03-26.zip
File Size: 593 KB
File Attachment:File Name: ansvr_2019-02-08_204945.log
File Size: 101 KB
I think when using manual rotation, three points would be needed instead of two; as the direction of rotation is unknown.
I'd be interested to hear what specifically the OP needs to do outside.
I run INDI on a SBC (not RPi) at the scope. I manage the indiserver via indiwebmanager which starts indiserver automatically at startup. I run EKOS on a desktop in the observatory and when running wireless I save the images to local i.e the SBC which is essentially instantaneous as the SBC has USB3. For platesolving and focussing I usually use ROI or bin the images to reduce latency when transferring to the client. I run PHD2 directly on the SBC. Since the obsy can get cold I monitor EKOS and PHD2 from my laptop via VNC. So I am running two clients on INDI (EKOS and PHD2) and don't need to restart indiserver. My main issue is a dodgy wifi dongle which loses connection from time to time. When that happens INDI and PHD2 keep running but EKOS loses control. I then have to run to the obsy, unpug/replug the dongle and restart EKOS.
So my take on this is that the cleint-server architecture of INDI works exactly as it should. The EKOS client has an understandable limitation in not being able to coordinate between multiple EKOS clients. And it has a minor (and known) issue when it loses connection with INDI.
Maybe the answer is a new kind of driver that acts as the hub for the other drivers. So EKOS could talk to that one driver and have it route the requests to each of the connected drivers.
I finally got around to trying this out. I started with the Avalon mount which for me is on COM7.
I first did an apt-get install indi-full, then started indiserver.
To get access to the COM port I had to chmod 666 /dev/ttyS7
Then fired up Ekos (and PHD2) and connected to the mount, slewed, parked etc...
I also installed astrometry.net and ansvr and got it 90% working from the Ekos alignment module. That is it solved an image behind the scenes but the ansvr Jnow converter failed (it was compiled for Cygwin). I've reached out to Andy to see if something can be done so fingers crossed.
So what we need now is either libusb support or some way to bridge across to Windows
I got your message and replied. Let me know if you got it or not.
Also found I can send a message by clicking on a name in the forum. Just can't create one from scratch inside the inbox.