Ok I've been thinking that the additional INDI server only runs the weather driver (and perhaps any power controlling drivers), but not dome/mount..etc.
Now, it could be Ekos Scheduler module itself or a separate process that monitors weather and commands the scheduler to shutdown or startup. The current "Park Wait" implementation is fine for short periods, but inefficient for long periods of inactivity, and therefore a complete power-off shutdown would be the way to go (given you don't cut off power from weather station!). The dedicated process or Ekos can then start the scheduler when the weather improves. The scheduler has no idea and would start as it would have been started by a human operator. That intelligence just acts as the decision maker. It's not just weather, for could be used perhaps for the holy grail we've been seeking for a long time: multi-night scheduling.
Read More...
Yes I agree. We need to consider all the various scenarios as well to accommodate different requirements for each. So this would be a completely separate external process?
Read More...
Right, the weather properties need to be added there (any volunteers?). Basically, the "Weather" could be either a binary "Clear"/"Cloudy" variable or a range "Clear/Hazy/Foggy/Cloudy/Thunderstorm"...etc. It's a general description of the sky conditions.
It would be great if someone can step in to document the properties properly in the documentation, let me know if you can contribute the updates.
Read More...
Alright, we're getting there! Check my signature on how to enable logging and then share the logs.
Read More...
Yes, this would be an awesome idea to have. Currently, it goes into total shutdown mode. Maybe with the right switch, it can also go into the current Park Wait mode. Park Wait is exactly this, it parks but doesn't shutdown, but this is used now when the next job is far away. Maybe it can be re-used for 'suspend' on bad weather if the option is set. However, looking at my own observatory, Park Wait would not suspend power or shutdown INDI , so you could end up in a situation where your equipment is wasting power. My shutdown script actually includes a Python script to turn off the power completely. Also, by the end of the shutdown, it would shutdown INDI server itself. At this stage, the scheduler has no idea what the weather is since the driver is down.
Perhaps one idea is to have the weather driver on in its own INDI server always running regardless. Or ... Ekos can be smart enough about this and requests shutdown of everything except the weather driver (INDI server is essentially running in protected mode) which it then listens to intently to monitor the weather conditions and upon favorable conditions, it runs the startup sequence again. Though at this time, instead of running a new INDI server, you will just request the startup of the drivers you previously shut down.
Read More...
Hello Omar & Welcome to INDI forums!
I actually just purchased a Nikon D3500 yesterday so I can troubleshoot the issues with Nikon support on INDI/StellarMate, so hopefully within a couple of weeks I'll try to work out any major issues with Nikon support.
Read More...
This is simply the effect of text wrapping in the cell. @rlancaster is the one behind it so maybe he can suggest a workaround? There is probably a way to make the cell auto adjust its height to compensate?
Read More...
Can you please enable debug logging and attach the logs? Then we can try to identify the issue. Thanks!
Read More...
