Ok, I wasn‘t aware of the difference between the Telescope Simulator and the EqMod driver. Thanks for making this clear.



Hi Gonzothegreat :-)

Thanks for the reply. I understand that the telescope has to be pointed to the "regular" park position (counter weight down, looking north) precisely first, as described in your post. I just don't see how to proceed from there. Using the Kstars/Ekos telescope simulator, the telescope should be perfectly aligned with the earth's rotation axis. Slewing to a point near or on the northern horizon and setting this as new park position only updates the RA/DEC coordinates unter INDI control panel -> Telescope Simulator -> Site Management. These coordinates are also found in .indi/ParkData.xml. However, positions in the sky described by RA/DEC coordinates move with time. What I need is to define ALT/AZ coordinates here, I guess. How did you fix that problem?



Hi Gonzothegreat!

Actually I have read your and Magnus Eriksen‘s Blog on how to build a box observatory quite extensively over the last years. Thanks for the documentation of your work. It is a great project and I had students of mine contribute some parts (Roof opening, motorised dust cover, ventilation and weather station).

The link you provided seems to explain how to precisely set a park position using the hand controller of the mount. I am not using the hand controller but only KStars/Ekos. I probably wasn‘t precise enough in my post. So I think my question is:

How do you define a park position where the telescope is pointing to the nothern horizon using KStars/Ekos.




I have built an "observatory in a box" (www.angelaschule-os.de/wie-noch-eine-sternwarte/) and hence have to define a park position where the telescope is pointing at northern hoirzon (alt = 0°, az = 0°, counterweight bar leveled horizontally) in order to avoid collision with the roof. I am using a SkyWatcher EQ6-R Pro mount. I have searched through older threats in the indilib.org forum and found that I need to slew the telescope to the desired position in the sky and set this as new park position. I have tried that procedure using the telescope simulator but found that as time procedes, the park position "moves with the stars" and changes over night. 

I am probably just missing something in my workflow. I am sure there are people out there who have done just what I need and can help me.




a student of mine has built an Arduino Meteostation following the instructions here: github.com/magnue/induino_meteostation_h...onfigure-print-build

The ambient and IR temperatures in the sketch (github.com/indilib/indi-3rdparty/blob/ma...O/indiduinoMETEO.ino) are divided by 100.

  if (mlxSuccess) { Tir = mlx.readAmbientTempC() / 100.0; 
  IR = mlx.readObjectTempC() / 100.0; 
} else if (mlxSuccess = mlx.begin()) { 
  // Retrymlx.begin(), and clear MLX sensor fail flag 

It seems, that these are also the values shown in the INDI Control Panel under Raw Sensors. Both values are 0.20 inside an the IR temperaure goes up to 0.30 when holding a hand over the sensor. As a result the Sky Temperature inside is -7.70 C which is obviously wrong.

So I asked myself, why the temps of the MLX Sensor are divided by 100 and if the Sky Temperature ist calculated correctly.

Grateful for any help,


Ok, I experimented with the starup script and scheduler but still need some help. This is what I did:

1) Created a startup script:

# -*- coding: utf-8 -*-
import os
import time
import sys
print "Start indiserver in FIFO mode..."
os.system('mkfifo /tmp/myFIFO')
os.system('indiserver -v -f /tmp/myFIFO')
print "Start mount simulator driver"
os.system('echo "start indi_simulator_telescope" > /tmp/myFIFO')

print "Start ccd simulator driver"
os.system('echo "start indi_simulator_ccd" > /tmp/myFIFO') 

2) I started the scheduler with a simple esq file and the startup script. I did not start Ekos (hit the play button on the Ekos setup page) before launging the scheduler, because I wanted the startup script to start indiserver and the (simulation) drivers.
3) This is the output:
2021-01-09T12:51:38 Mount already unparked.
2021-01-09T12:51:36 INDI devices connected.
2021-01-09T12:51:35 Ekos started.
2021-01-09T12:51:05 Start ccd simulator driver
2021-01-09T12:49:34 Start mount simulator driver
2021-01-09T12:49:29 Start indiserver in FIFO mode...
2021-01-09T12:49:29 Executing script /home/sternwarte/Schreibtisch/startup_script.py...
2021-01-09T12:49:27 Scheduler started.

4) So the startup script is starting the indiserver in FIFO mode and the drivers. But after executing the startup script, Ekos is starting the selected profile and tells me, that another indiserver is already running (the one I started with the script, I guess).
5) The devices are only showing up in the INDI Control panel after Ekos starts the profile and not when I start the devices in the startup script.

Can anyone please tell me what I am doing wrong? Thanks a lot!



Hi Jasem,

thanks for your reply!

knro wrote: Hello Simon,

That's great to here. Please share some photos of this observatory with us.

I have attached some pics. The observatory is pretty much set up and the rig is waiting in a box to be put up in the obsy. But first I have to make sure, that it is rain tight ;-) The design of the housing is a close adoption of Magnus Eriksens project (Thanks Magnus for the great blog on Stargazers Lounge).

I am a little worried about polar alignment (the lid of the obsy is blocking the view of the north celestial pole -> so I guess I have to use the legacy polar alignment tool), but that is a different story ...

knro wrote: I am doing exactly the same thing in my home observatory, so I'm not using the Pegasus, since I built my observatory back in 2015 and went to Digital Loggers Power Switch to turn on/off the equipment when the observatory is started/closed. To answer you question:

1. Yes, it's possible, you can use indi_setprop to toggle UPB ports on/off. Though that means that A) Pegasus has to be powered at all times, and B) indiserver running UPB must be up and running.

Yes, I was thinking the same. Ekos will run on a Raspberry Pi 4 and hopefully the UPB can cope with being powered on all the time.

knro wrote: mkfifo /tmp/indififo
indiserver -v -f /tmp/indififo

This starts INDI server in FIFO mode.

Then open another console

echo "start indi_pegasus_upb" > /tmp/indififo

This would case the INDI server to start this driver. Next you'd use indi_setprop to toggle the 12v for them on/off. Say, you turned power for the QHY camera, then you'd this:

echo "start indi_qhy_ccd" > /tmp/indififo

Then that would start is on the server and so forth. I hope this helps.

Okay, let me make sure I get this right. I will start Ekos (graphically on the RPi 4). Then I will feed the scheduler with a sequence file, weather data and startup script. When the target is visible and weather is appropriate, the startup script starts indiserver in fifo mode and connects 1) the UPB, 2) turns on the 12V outlets of the UPB to power on the other devices and 3) starts the drivers for the other devices, right?

Above you say something about opening another console. How is that taken care of in a startup script? Just by using a new "os.system(echo "start indi_***_***" > /tmp/indififo)" call in my python script?

Thank you for the help. This is really exciting.



we have built and set up a small observatory on our school roof. The observatory is supposed to be automated using the Ekos scheduler. The power for the mount, CCD, guiding cam, filter wheel and dew heater bands is delivered by a PegasusAstro Ultimate Powerbox v2. In order to reduce power consumption, I would like to turn on the power for and connect the above named devices using a startup script to be executed in the scheduler when an observation is about to start.

So my questions are:

1. Is it possible to turn on the 12V power outlets on the UPB with a command that can be executed via a startup script?
2. Is it possible to connect devices (once they are powered up) with a command that can be executed via a startup script?

May be someone is already doing this and could provide their startup script so I can cheat a little bit ;-)



Hi wotalota,

thanks for your reply. I wasn't planning on using the whole WH4000 weather station but only the replacement anemometer. But Weather Radio seems great. I think I will give that a try.



Hi G_Ganon,

thanks for the reply and the info. I wasn't aware of Weather Radio but it sounds very nice. We are using a BMP180, a DHT22, a MLX90614 and a photo resistor in the Induino Meteostation together with a PRO Trinket 5V. Maybe we can adopt the Weather Radio code to work with these sensors and the wind speed sensor www.froggit.de/product_info.php?language...080-1090-wh4000.html . If that doesn't work, I will just get a new set of sensors and give it a new try. The all sky camera seems very promising as well :-)




we have built and set up a small observatory on our school roof (see picture). The observatory is supposed to be automated using the Ekos scheduler. One of my students has built an Induino Meteostation according to the manual by Magnus Eriksen. Since the observatory is in an exposed location and has a quite large attack surface when the roof is open, we would like to expand the Meteostation to measuring wind and gust using a sensor like this: www.froggit.de/product_info.php?language...080-1090-wh4000.html

Has anyone expanded their Meteostation to measuring wind and gust and can give advice on how to modify the INDI Meteostation driver?

I would be thankful for any help,

P.S.: My solution for now is to use the Induino Meteostation together with OpenWeatherMap data through the Weather Meta driver. However, the wind data is not measured locally at the observatory.


Thanks, that solved the problem.