I also think this would be a nice feature where one could select the collimation star, EKOS/Indi would move the mount to center it, collimation adjustments would be performed and EKOS/Indi would be told to re-center it and the procedure would be performed again until collimation is done. As this way to collimate would require a camera (re-centering and collimation evaluation), I wonder if a camera is adequate for this task, compared to the human eye/brain. The nice thing about this though is that collimation could be performed at the collimating screws end of the telescope, with the aid of a display (tablet...).
Good to read that all is OK now. Note that if you are using the BME280 (not BMP280), you do not need the DHT22 sensor as the BME provides the humidity value.
As the Holidays are behind us now, I will be able to look into updating the documentation to reflect the recent changes.
I tested mine (updated firmware, with TSL2591, MLX90614 and BME280) with release 3.3.8 as well as 3.3.9 and everything is fine.
In your post, you mention TSL2992 and TSL2095 as sensors being used in your MeteoStation. As those sensors are not used in the Indiduino MeteoStation firmware, I did a Google search on them but Google did not return anything on those so I wonder what types of sensors they are.
I am currently fighting the end of a Holidays unsolicited gift, AKA a cold, but I will try to look at the firmware and xml files soon,just in case.
If you tried using the INDIduino MeteoStation SQM driver with the mySQMPRO firmware, it won't work as interaction between the driver and firmware will be different. INDIduino MeteoStation (legacy or SQM) are based on the Firmata firmware and, as such, you need to flash your Arduino with the INDIduino MeteoStation firmware found in the 3rdparty branch of the INDI software. More specifically in ".../indi/3rdparty/indi-duino/devices/Firmwares/indiduinoMETEO/indiduinoMETEO.ino".
If you want to give it a try, do not forget to uncomment the appropriate #define for your sensors, and comment those that you don't use, in indiduinoMETEO.ino.
I will try to make the documentation as simple as possible and, as you suggest, document the Arduino part as well as the firmware. As you mention, an Arduino (e.g. Arduino Nano) with USB connection would be easier to use for most but as I was using the 3D printed enclosure as presented by Magnus Eriksen in
, I used an Arduino Pro Mini that is small enough to fit in the 3D printed enclosure but do not have a USB connection. I use a USB to FTDI cable to connect. Different enclosures may be more adequate for larger Arduino parts.
From a system I found on the web, I have a prototype ESP8266 based WiFi weather station that provides daily weather logs in csv format as well as in HTML format but I do not have an INDI driver for it. Its meant to be autonomous and solar powered. If major modifications are made from the original MeteoStation, we could look into writing an INDI driver for it.
Anyway, a lot to think about and, depending on people's interest, it may direct our choices.
Thanks for your encouraging comments, they are very much appreciated.
Jasem has asked me to work on the MeteoStation documentation which would benefit from a refresh and an up-to-date upgrade, given the possibility of new/different sensors. I am thinkering on that while working on my automated observatory, based on Gonzo the Great's idea and concept. So time is shared between family and many projects and things don't get done as quickly and efficiently as I would wish.
Back to your suggestions, the users who embark on building the indiduino MeteoStation need to specify whatever sensors they intend to use so there is no easy way around configuring the firmware. Maybe we could put the sensor configuration elements (sensors related #define) in an include file instead of the actual "indiduinoMETEO.ino" file. The users would only have to edit that "indiduinMETEO.h" file and we could put enough info in it to make it simple to configure. the INDI skeleton files should not require modification if you use the appropriate 'virtual' driver (Arduino MeteoStation or Arduino MeteoStation SQM) but I can take a look at that to make sure. Concerning the HTML page and python scripts, not having much experience there, I can't unfortunately be of much help, even though I can have a look.
As far as reducing the Arduino firmware and shifting calculations to the INDI driver, as the firmware is based on the Arduino firmata sketch, I am not sure this can be done easily. I am far from being an expert (more like novice) with firmata so I do not really know what is involved in that change. Furthermore, except for the SQM sensor which adjust its gain and integration time in the firmware, all the other sensors just provide values that are scaled and sent to the /usr/bin/indi_duino driver. I will take a closer look at what we can do to make things easier but can't promise much yet.
Thanks again for your ideas/suggestions/comments.
I guess my problem is related to the one mentioned in #45977 re: libraw.so.19. I will follow that topic then.
As the subject says, I did a software update today, through the "Software Updater" and KStars won't start anymore. I get a "kstars: error while loading shared libraries: libraw.so.18: cannot open shared object file: No such file or directory" error message. I still have a copy of 'a' libraw.so.18 library in "/usr/lib/x86_64-linux-gnu/" but I don't know if I can use it to solve the issue.
I'm running Ubuntu 18.04LTS.
Thanks for any insight.
Thanks Jasem, I'll give the UPB a try again, hopefully soon.