I just don’t get it.
I have installed “phd2logviewer” besides the SM OS on a RPi 4b. The logging in SM for guiding is enabled as verbose level.
But if I load the logfile into the phd2logview … there is nothing.
Do I misunderstand the concept?
Thanks for any hint
and how to use it with EKOS internal guiders logs?
here ist the logfile. In my profile are only the telescope simulator and the Canaon 700d connected via standard USB cable.
Thank you for you help.
Yes, I will send the Logs gut this camera has Bad a Problem Top Connect. All of the sudden is will Not work anymore. ????
Talk to you later
Again me, strangely enough gphoto recognizes the EOS but indi not.
same thing here with a Canon EOS 700D. Cabeling and power all good, I can’t get it.
I tried with Sequence Generator Pro and it worked. Again, I have invested so much effort and I really like the concept but I’m about to resign.
Sorry for this but I need a working system. I still believe in STELLARMATE, but give me a hint.
did you consider a resistor heating for freezing protection for the sensor?
thank you for your ideas. I also thought about chaining but was not so sure if it works well. Please see this, indilib.org/support/tutorials/159-indi-on-multiple-devices.html
is that what you are talking about? Is it necassary to run on both RPi's Kstarts, Ekos etc? And how important is it have ssh running flawlessly?
It works on my mashines but not to 100% reliable. Could you provide please the startup script?
Also interesting is the direkt Ethernet idea. You menshion the cross over cable. In the docs I only find regular LAN cables but plugged direct from Pi to Laptop or so.
Have a great New Years Eve.
I have an unresolved issue with my Stellarmate clients and servers. Please find a slide attached in order to help to explain what my goals and issues are.
First of all the goal:
I would like to create a robotic observatory. So far so good.
I use to control the devices one RPi4B named RPI41w. All the physical devices are plugged in there. In addition to that I startup indi_watchdog, indi_Weatherradio and indi_Skysafary as non physical devices on RPI41w. The major job of the other RPi4B, called "allsky" is to run and process allsky camera (github.com/thomasjacquin/allsky). In addition to that have connected a NodeMCU 8266 (wireless minicontroller (192.168.178.75) powered by a USB connection) to "allsky". The minicontroller collects weather, cloud and SQM data (indi_duino 3rd-party driver by Sterne-Jaeger: github.com/indilib/indi-3rdparty/tree/master/indi-duino). That works fine and reports those data into the indi driver and they show up in the indi-panel of the Kstars client "Astrolin".
Now here is the problem. I do not run kstars, ekos etc on allsky. I start "indiserver -v indi_dome_script as a systemd/systemctl in a unit script.
pi@allsky:/etc/systemd/system $ cat indi-dome_script.service
Description=INDI server for weatherradio,domescripting_ gw,watchdog
When I add two more lines for the other drivers I receive an error message.
I really would appreciate any hint.
best regards Gunter
I hope you had a nice and peaceful Christmas and you stay well.
I have studied you roof scripts with this USB relais. It is quite straight forward and I can understand it quite easily. Only thing I could not understand is how did you connect the limit switches ot the relais or to a Pi? In your unpark.py script is a comment about a Pin 2 connection but seems to be controlled by the relais driver.
I ordered 4 limit switches and a electronic lock to keep the roof tide and secured against gusts and rain. I try to incorporate this into the unpark and park scripts.
Have a good New Years Eve.
best regards Gunter