That should have fixed it.
Perhaps you did not execute the git command to fetch the changed code?
You could start over.
You need to follow the INSTALL directions again to rebuild the driver to be compatible with the release.
There have been changes to the way weather alerts are handled to park the mount and close the roof.
You will need to change over to use the watchdog driver. Watch out that your mount park switch locking of roof movement does not interfere with the software checks. If the roof locked light is on it will not respond to movement requests. By the time the park roof request is received the roof lock should have been released, but it needs testing.
Congratulations on getting it all figured out and working. When you update to KStars 3.4.3 and INDI 1.8.6 there will be an error from the roof driver. The roof driver build procedure will need to be repeated. I just made the correction today, it was using a routine which is no longer available to check for a weather alert before opening the roof. The watchdog driver now provides improved handling to protect the observatory against bad weather.
If you wish, I can add your Arduino sketch and any notes about the motor control you provide as another example in the git repository.
When testing the weather alert with the observatory protection using simulators and the watchdog with the following settings checked.
Watchdog: Park Mount, Park Dome, Weather, Mount Locks
Observatory: Alert, Park
Dome (Rolloff simulator): Mount Locks
Mount: Dome Locks
The weather alert and safe parking of the mount and dome worked fine.
Two things that seem different.
When the weather is bad and a weather alert is already in effect it is possible to unpark the dome. I don't think that could be done before when the dome was checking the weather.
If the mount is using Dome Locks. An attempt to unpark the mount when the dome is parked will result in a driver warning message and the mount will remain parked. However KStars and Ekos will change the mount status to unparked and be out of sync with the driver. But they can be brought back together by first unparking the Dome and then use the driver to unpark the mount.
git clone github.com/indilib/indi.git
mkdir -p build/indi
cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=Debug ~/Projects/indi
sudo make install
indiserver -v examples/tutorial_one/tutorial_one
joshua@Cheops:~/indi/libindi/examples/tutorial_one$ ls -l
You are in what looks like a source files directory.
If you just run indiserver without any parameters it will output the version of indi you are running.
Assuming you have done a build to get the examples. The instructions above are what I find on the web site.
There you would find the executable under ~/Projects/build/indi.
set default to your home directory and issue the following command it might help you locate the build/output directory and the executable.
find . -name tutorial_one
Tried the WatchDog with simulators.
Attempted to remove the roof snooping on the weather so it would not be involved in detection. The set on the weather
field did not move the right field value into the left field. Should confirm in some way that with different weather delay thresholds between the roof and the watchdog there is only a single weather detection and park request.
The WatchDog continues to show a green status after the weather alert is raised.
First test was with telescope policy set to ignore dome, the dome policy set to ignore telescope.
The WatchDog to park both which it does. As before without the WatchDog, the mount and the roof park together.
The WatchDog outputs the "Shutdown" complete message when the roof completes parking, the telescope is still in the process of parking.
Second test was with the Dome Policy set to telescope locks. The behavior is as before without the WatchDog the telescope parks and the roof blocks with warning messages at the indi level. When the telescope has parked, the lock is removed,the roof remains open. When the roof is later manually closed the WatchDog outputs Shutdown complete and the status light on the Shutdown line turns from yellow to green. When the weather alert clears the WatchDog outputs message.
This meets expectations of detecting weather alerts and being able to effect park commands.
Is your default directory location set to the build area, it just looks like it can not find the executable.
From your example `ls -l examples/tutorial_one/` should show you an executable file tutorial_one.
To clarify, your description is what is seen if, telescope blocks dome is used, and just indi participating. The dome is blocked by the telescope. Wolfgang's request to do a test was to involve the client by using the scheduler's weather alert detection to initiate both telescope and roof parking. Your description did not mention the scheduler.
In my case it is a rolloff roof, so you have the additional complexity of the dome to deal with. Not clear about how the shutter relates to the roof open/close and the dome park/unpark.
Sorry about that should read it before posting. Yes it parked the roof after the mount had been parked as part of handling the alert. I kind of expected the Observatory to interfere but it did not seem to make a difference. Only ran once through each combo but hopefully results can be consistenly reproduced.
I ran a 2 tests using the scheduler and simulators. Both test were run twice once with the Observatory set to park dome on alert and once with that unchecked. I did not see a difference whether or not the Observatory was involved.
Test 1 the telescope used the "Dome Parks" policy and the dome used the "Ignore Telescope" property. With this combination when the alert was triggered both telescope and roof parked together. So that was the same result as
when the scheduler was not involved.
Test 2 the dome was changed to telescope blocks. With this combination the when the scheduler sensed the alert the telescope started parking and the roof output a warning that it could not park. Same as the none scheduler case, but when the telescope had parked the roof driver output a message indicating a changed of telescope status had been sensed. I then proceeded to park the roof as hoped for.
So using the scheduler along with policy combination worked well to provide whichever behavior was wanted.
Not extensive testing but promising.
Being able to make a phone call would be valuable, thinking about failures or weather alerts while sleeping. I briefly looked into VOIP and Google voice earlier this week, but didn't see anything obvious that could make use of the closed system VOIP I use. But it seems like there should be something there. For now I'm just going to do something that results in a simple ` play /usr/share/sounds/KDE-Im-Phone-Ring.ogg` to wake me up.
If changes were to be made to the indi Dome code, having a third telescope option would be useful: ignore wait or block.
Park both dome and mount at the same time or wait on the telescope might depend on what is mounted. With a small refractor I have no collision issue, with an SCT it needs protecting.