I have a Raspberry Pi 2B, so hardware may be part of the problem. Yesterday I couldn't even upgrade to ubuntu 18.04. Maybe time to upgrade to at least a 3B+, or even a Rock Pi.
@pch : I have Ubuntu 16.04. The RPi hasn't been used for a while. I'll do a release upgrade and try again. Thanks
I tried to install the deb package, but got a dependency error. I don't have astroberry installed so I downloaded the deb from the link provided. Upon installation I got the following dependency that was not met:
python3-paho-mqtt , which isn't available (tried sudo apt install python3-paho-mqtt)
How can I resolve this error?
I connected my ASI main camera and ASI guide camera plus the ASI filter wheel to my Rock64 sbc. Telescope and Focuser were simulators. I then started Ekos and all settings were fine. The guide camera loops happily at bin 2x2 while the main camera shoots away at bin 1x1. Unlike the ccd simulator driver, the ZWO CCD driver has no Guide Head tab (as is correct). Bin states of the main camera and guide camera are maintained when shutting down and restarting Ekos. It seems that the bin state issue is with the Guide/CCD simulator driver only.
I just had a look at the source code, and as you noted, the names are hard coded into the driver. Right now, I'm not too keen on rewriting that driver. But if I pursue this and get serious about automating my observatory, I might just do that.
I've made a meteostation and a SQM-meter that both act as a web server. The SQM-meter creates a webpage that shows a time stamp and the light level (in Mpsas) in a format that the Weather Watcher driver in Ekos can read.
These values are read by the meteostation, which combines the light value with other measurements (temperature, cloud, pressure, humidity, and dew point) and publishes the result also on a simple web page.
I read the output from the meteostation into Ekos via the Weather Watcher driver. The problem is that the driver doesn't use the same parameters that my station reports. I can of course change labels in the options tab of the driver, but that doesn't change much. It will just result in that "light" is reported as "Wind", for example.
Is it possible to customise the parameters in the driver, eg through a skeleton file? If so, how do I do this? Or can/should I use another driver for my weather station? I like the fact that the station is stand alone, and doesn't need to be connected to my INDI computer, and I would like to keep it that way.
Here's what the output from the meteostation looks like:
I just got a simple weather station working. It's based on the ESP32 wifi board and the software is written in microPython.
I uploaded all the files to GitHub
The hardware is very simple. An IR detector (mlx90614 temperature sensor) and an environmental sensor (BME280) are connected through I2C to an Espressif ESP32 board which has microPython loaded.
I used Thonny to program the device ( https://thonny.org/https://thonny.org/ )
Libraries for the sensors are readily available on line. The only minor issues I had were figuring out the connection to INDI. I decided to use the Weather Watcher INDI driver. This allows me to use the temperature and forecast/Weather parameters to control my observatory (once that's finished).
And a screenshot of how it looks in Ekos
The issue resolved itself:
I had forgotten to add "http://" before the ip address.
Now I just have to figure out how to use the meteo data...
I'm developing a weather station using an ESP32 board and BME280/mlx90614 sensors
I got the sensors collecting data and can either send it to a simple web server that doesn't use web files, or I can write the data to a text file.
Now I want to connect my station to INDI, using the Weather Watcher driver. The question is: how do I do that?
The ESP32 is connected to my home network and has a static ip address.
And I did confirm that the guide head in the simulator works ok. But I'm not sure that other camera drivers have a guide head tab.
Due to recent knee surgery I haven't been able to any testing with my ASI cameras, but I may get them out of storage and just hook them up to my computer. Maybe it's just the simulator driver that has this issue.